Thinkpad T60 [1680x1050], ATIx1400, no X on Gutsy, Hardy
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-restricted-modules-2.6.24 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
When using 8.45.4 driver direct from ATI ( Build Date: Jan 16 2008 10:42:57). This happens on both of the following distros (both on a Thinkpad T60, ATI Technologies Inc Radeon Mobility X1400)
===== separator =====
1 - on a dist-upgrade from feisty to gutsy, using kernel2.
The log has given me a number of errors, none of which appear to be fatal, but clearly something is.
Currently, the warnings or errors from X are as follows:
(WW) The directory "/usr/share/
(WW) The directory "/usr/share/
(WW) The directory "/usr/share/
(WW) The directory "/usr/share/
(WW) `fonts.dir' not found (or not valid) in "/var/lib/
(WW) Including the default font path /usr/share/
(WW) fglrx(0): GetVBEMode failed
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(WW) fglrx(0): Only one display is connnected,so single mode is enabled
(WW) fglrx(0): Option "UseFBDev" is not used
(WW) fglrx(0): Option "VendorName" is not used
(WW) fglrx(0): Option "ModelName" is not used
so no Errors and the warnings do not seem to be all that horrible.
Some errors in the past dealt with not being able to load 'glcore' and 'font1' modules, but I've commented those out without complaint.
syslog gives me the following fglrx-related errs
[fglrx:
[fglrx:
[fglrx:
but then on rerunning startx, I only get these in a repeating fglrx message block:
[fglrx] PCIe has already been initialized. Reinitializing ...
[fglrx] Reserve Block - 0 offset = 0X7ffb000 length = 0X5000
[fglrx] Reserve Block - 1 offset = 0X0 length = 0X1000000
[fglrx] Reserve Block - 2 offset = 0X7fbb000 length = 0X40000
[fglrx] interrupt source 10000000 successfully enabled
[fglrx] enable ID = 0x00000008
[fglrx] Receive enable interrupt message with irqEnableMask: 10000000
[fglrx] interrupt source 10000000 successfully disabled!
[fglrx] enable ID = 0x00000000
[fglrx] Receive disable interrupt message with irqEnableMask: 10000000; dwIRQEnableId:
===== separator =====
2 - on Hardy (apt-get current as of Jan 21, 2008). (same result with the fglrx patch released today [fglrx 8.43.2] as well as the brand new one direct from ATI [8.45.4] ).
The conditions are just about identical: Same behavior for the initial login, then when I try to login via console, I get a brief flicker of the base X11 screen (movable X cursor for a few seonds and then a crash back to the console.
I have the following additions to my xorg.conf based on other postings:
-----
Section "Extensions"
Option "Composite" "0" # or "Disable"
EndSection
Section "ServerFlags"
Option "AIGLX" "off"
EndSection
-----
With those additions, the warnings or errors from X are as follows:
(WW) `fonts.dir' not found (or not valid) in "/var/lib/
(WW) fglrx(0): GetVBEMode failed
(WW) fglrx(0): board is an unknown third party board, chipset is supported
(WW) fglrx(0): Only one display is connnected,so single mode is enabled
(EE) fglrx(0): === [swlDalHelperAd
(WW) fglrx(0): could not detect X server version (query_status=-3)
(EE) fglrx(0): [drm] failed to remove DRM signal handler
The last EE is embedded in the last few lines of the log:
...
(II) fglrx(0): Shutdown CMMQS
(EE) fglrx(0): [drm] failed to remove DRM signal handler
(II) fglrx(0): [drm] removed 1 reserved context for kernel
(II) fglrx(0): [drm] unmapping 8192 bytes of SAREA 0x35000 at 0xb7fb0000
(II) fglrx(0): [drm] Closed DRM master.
FreeFontPath: FPE "/usr/share/
Neither dmesg nor syslog has any indications of errors.
Changed in linux-restricted-modules-2.6.24: | |
status: | New → Invalid |
Solved (mostly). Sorry about the confusion. This bug (?) apparently was caused by a misconfiguration somewhere in the depths of my '.kde' directory tree. My kmail had begun to act strangely which is why I tried to upgrade to gutsy. The mistake was revealed when I created a new user and logged in to test this possibility and all of a sudden, X started to work perfectly. I experimented with copying various suspicious files and directories and the .kde dir caused the glitch. Somewhere in there is a file that corrupts X, but I haven't found it yet.
ALSO!! Power suspend-to-RAM / recover now works work, and trying to run google earth causes a crash, but I'll deal with that later. Just glad to be seeing my laptop alive again. The Synaptics touch pad works as it's supposed to.