| Summary: | gnome-base/gdm-2.20.11 won't start with ati-drivers due unproper GdmXserverTimeout default | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Enrique Domínguez <enrique_pinos> |
| Component: | [OLD] GNOME | Assignee: | Gentoo Linux Gnome Desktop Team <gnome> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | enrico.tagliavini, lu_zero, x11 |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | AMD64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
xdm success start with another instance of X running in :1 vt8
xdm failed without any instance of X running startx as user (as usual) dmesg when gdm start (two X instances) dmesg when gdm failed |
||
|
Description
Enrique Domínguez
2011-08-11 12:25:29 UTC
This bug cannot be diagnosed without additional information. Please attach /var/log/Xorg.0.log files that are generated when: 1. gdm fails to start 2. gdm starts successfully 3. startx starts successfully. Also, please attach dmesg output. Created attachment 283227 [details]
xdm success start with another instance of X running in :1 vt8
Created attachment 283229 [details]
xdm failed without any instance of X running
Created attachment 283231 [details]
startx as user (as usual)
Sure! Please feel free requesting all you need; I would like to find one solution for this annoying behavior. I have attached Xorg.0.log in those three cases. I haven't got this notebook here, so I attaching dmesg later. I couldn't find any significant error (is not first time I setting up gnome) in success xdm: fglrx(0): PPLIB: PP_Initialize() failed. while in failed and startx: fglrx(0): Unable to register ADL handler for 0x00C00000 No idea at all. Thanks for replies. I can't see anything in the logs that would explain why startx works for you and gdm doesn't. I am CCing the x11 herd in the hope that they might be able to help. The main difference seems to be: - (EE) fglrx(0): PPLIB: PP_Initialize() failed. + (WW) fglrx(0): Unable to register ADL handler for 0x00C00000 And then differences in addresses, EDID... I'd say it's because the other X instance has locked the gfx card and a few things failed. But what is happening, I really don't know. Maybe a log of the failing pre-last X restart would be useful. I guess that would be Xorg.0.log.old after failing gdm start. Thanks for replies, It's true, nothing in log is useful for finding trouble :S diff between xdm start and xdm start with another instance of X was: < (==) Log file: "/var/log/Xorg.0.log", Time: Tue Aug 16 14:02:08 2011 --- > (==) Log file: "/var/log/Xorg.0.log", Time: Tue Aug 16 13:58:44 2011 246c246 < (WW) fglrx(0): Unable to register ADL handler for 0x00C00000 --- > (EE) fglrx(0): PPLIB: PP_Initialize() failed. 384c384 < (II) fglrx(0): FBADPhys: 0xf00000000 FBMappedSize: 0x009c4000 --- > (II) fglrx(0): FBADPhys: 0xf01040000 FBMappedSize: 0x009c4000 407c407 < (II) fglrx(0): X context handle = 0x1 --- > (II) fglrx(0): X context handle = 0x3 562,581c562,567 < (II) Power Button: Close < (II) UnloadModule: "evdev" < (II) Unloading evdev < (II) Power Button: Close < (II) UnloadModule: "evdev" < (II) Unloading evdev < (II) Sleep Button: Close < (II) UnloadModule: "evdev" < (II) Unloading evdev < (II) Genius Optical Mouse: Close < (II) UnloadModule: "evdev" < (II) Unloading evdev < (II) AT Translated Set 2 keyboard: Close < (II) UnloadModule: "evdev" < (II) Unloading evdev < (II) fglrx(0): Shutdown CMMQS < (II) fglrx(0): [uki] removed 1 reserved context for kernel < (II) fglrx(0): [uki] unmapping 8192 bytes of SAREA 0x81000 at 0x7fb90e29d000 < (II) fglrx(0): Interrupt handler Shutdown. < (II) fglrx(0): Interrupt handler Shutdown. --- > (II) fglrx(0): Restoring Recent Mode via PCS is not supported in RANDR 1.2 capable environments > (II) AIGLX: Suspending AIGLX clients for VT switch > (II) fglrx(0): Backup framebuffer data. > (II) fglrx(0): Backup complete. > (II) fglrx(0): Backup framebuffer data. > (II) fglrx(0): Backup complete. Hi Michał, there is no difference between Xorg.0.log and Xorg.0.log.old when xdm fails to start. I have seen another strange behavior, if xdm service was started and I recompile gdm, when compiling was ended, gdm greeter is showed without restarting services at all. I have done 'emerge -e world' but nothing helped. Thanks a lot for replies and sorry for my delay answering. Created attachment 283617 [details]
dmesg when gdm start (two X instances)
Created attachment 283619 [details]
dmesg when gdm failed
What gdm version are you using? Does "gdm" command work ok when manually running it instead of /etc/init.d/xdm? Have you tried with other display managers like "xdm" or "kdm"? dmesg output shows some problems probably related with ati-drivers, what version of them are you using? To be honest i don't see something wrong with ati-drivers, but it might be worth to try ati-drivers-11.8. Version 11.7 and 11.8 got a lot of fixes, so trying them is worth. Unles your chipset is not supported, I stronly suggest running with xf86-video-radeon. (In reply to comment #13) > Unles your chipset is not supported, I stronly suggest running with > xf86-video-radeon. Disclaimer: this is not a flame war or something :) I don't agree. It is true fglrx is a bit more problematic then radeon, but it has many advantages, like 3d performance, really better powersave and better new hardware support. Nevertheless a test run with radeon is worth to understand if fglrx is the really bad component here (and from what i read there is no hint it is). Btw does gdm have some log? It might have some additional information. Under /var/log/gdm you have logs for X when started with gdm I have read /usr/share/gdm/defaults.conf and found "# How long gdm should wait before it assumes a started Xserver is defunct and # kills it. 10 seconds should be long enough for X, but Xgl may need 20 or 25. GdmXserverTimeout=10" so I set /etc/X11/gdm/custom.conf in [daemon] like this, GdmXserverTimeout=25 and all worked finally (first time I having to touch there) Thanks all for replies. For reference: gnome-base/gdm-2.20.11 x11-drivers/ati-drivers-11.6 Others display manager does work nice (I have tried slim) but logs (debug included) won't help me. We should probably increase default timeout value then as it shouldn't hurt other setups and I guess you are not using Xgl (that is pretty dead) (In reply to comment #17) > We should probably increase default timeout value then as it shouldn't hurt > other setups and I guess you are not using Xgl (that is pretty dead) Sure, I'm not using Xgl. No idea, maybe installing a file for committing with dispatch-conf when people installing ati-drivers? I have worked with a lot of drivers and never have had to change such param :S +*gdm-2.20.11-r1 (11 Sep 2011) + + 11 Sep 2011; Pacho Ramos <pacho@gentoo.org> +gdm-2.20.11-r1.ebuild: + Wait more before assuming Xserver is defunct (bug #378765 by Enrique + Domínguez), this change also solves a problem I was suffering for ages where + gdm had problems to restart on systems under heavy load. Also drop .la files + (bug #362961 by Stéphane Pagnon). + |
