On start-up, the screen goes temporarily black and eventually switches back to normal text mode. This is, probably, the same as bug 2087, though I don't get video lock-up. The video card works fine with the XFree86 server and driver, so it's not terminally broken. As a temporary work-around, I'm using that, though I'd prefer going to the X.org server, if at all possible.
Created attachment 5008 [details] X.org server logfile
Partial output from "lspci -v": 0000:00:14.0 VGA compatible controller: ATI Technologies Inc 264VT [Mach64 VT] (rev 40) (prog-if 00 [VGA]) Subsystem: ATI Technologies Inc Mach64VT Reference Flags: VGA palette snoop, stepping, medium devsel Memory at fc000000 (32-bit, prefetchable) [size=16M] I/O ports at f400 [size=256] Expansion ROM at 20130000 [disabled] [size=64K]
Can you try my probably very hairy and hacky atimisc clean-up? Hope to have it sit in xorg/driver/ somewhere this week, but this is quite definitely 7.2 material. http://people.freedesktop.org/~libv/xf86-video-mach64-20060321.tar.bz2
It doesn't look as if this is the driver crashing though. Could you try running X through gdb and backtracing it?
From memory, when I tried hard-coding the memory ranges that "lspci" gives me, it starts complaining about "bogus ranges" (or something similar) and changes IO-base and memory range, then complains about memory allocations, with the same end result. When I'm home, I can see if I can get the X.Org and XF86 server co-existing and see if I can try both the atimisc route and gdb, then run a backtrace.
Is this a duplicate of bug 5825? I've downgraded back to XFree86 because I couldn't downgrade to xorg 6.8.? when XOrg was last working for me. I use Debian unstable, and although I'm not a developer, I think I could help debug this. Though I don't know what mailing list we should move this discussion to. I would like to reinstall XOrg. But I'll need the sources.list entry for getting XOrg 7. and then instructions about where to install the atimisc module. I also suppose I'd like to wait until April, after my Dad has done his month end bill payments. Ivan.
Possibly a duplicate. I was (possibly overly so) restricting my bug search to 264VT. It looks very familiar, I must say. If worst comes to worst, I'll try a "from pristine source" build, should help keeping things separate, I guess.
Hm. Doing a source-build was a bit more painful than I thought.
Any update on the situation?
I'm trying to get the Debian-packaged X.Org X server installed in a chroot, so I can then run it under gdb, so I can get a proper backtrace. My attempts from building from source ran into "this is not nearly as trivial as I would've expected" (last I built X11 from source it was early 90s, things have certainly moved on from there).
Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Is this still a problem?
Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.