Created attachment 30047 [details] Xorg.0.log After the first start of KDM and during normal use of KDE 4.3.1 I can switch between the text console and KDE session without any problem. However, after logging out from the KDE4 session and returning to the KDM login screen, when I switch to the text console, it is not restored. Instead, I see a white screen with some remnant of the KDM screen. Currently I am using xorg-server 1.6.3.901, libdrm-2.4.13, xf86-video-ati-6.12.4, and mesa-7.5.1 (the "stable" stack for Gentoo), but the problem appeared with older versions since the support for R600 was introduced. When using driver xf86-video-radeonhd-1.2.5 with the same setup, the text console can be restored after logging out from the KDE4 session. The hardware is laptop ASUS M50SA with graphics 1GB Mobility Radeon HD 3650. I have 4GB of system memory. uname -a: Linux acrux 2.6.30-gentoo-r5 #1 SMP PREEMPT Sun Oct 4 17:34:29 BRT 2009 x86_64 Intel(R) Core(TM)2 Duo CPU T9300 @ 2.50GHz GenuineIntel GNU/Linux I'll attach the lspci output, Xorg.0.log, xorg.conf, and a screenshot.
Created attachment 30048 [details] lspci
Created attachment 30049 [details] xorg.conf
Created attachment 30050 [details] dmesg
Created attachment 30051 [details] screenshot of the text console
I forgot to mention that I can still switch between the KDM screen and text console, and normally login and use KDE. The console looks always as shown in the screenshot though.
I checked the following options in xorg.conf: Option "DRI" "off" Option "AccelMethod" "XAA" Option "RenderAccel" "disable" Option "EXANoComposite" "on" Option "EXANoUploadToScreen" "on" Option "EXANoDownloadFromScreen" "on" Option "EXAOptimizeMigration" "off" These suppose to turn off the acceleration, but unfortunately my problem still exists, so it seems that this issue is not related to EXA.
Created attachment 30059 [details] Xorg.0.log with EXA turned off
Sounds like the server may be crashing when you log out which prevents the text mode from getting restored. kdm promptly restarts when the server crashes so it may be hard to tell. Ideally you'd attach to the server with gdb and look for a backtrace when logging out. See this page for more info: http://wiki.x.org/wiki/Development/Documentation/ServerDebugging
Created attachment 30086 [details] gdb log and backtrace during logging out
Thanks for pointing this out. Indeed, it looks like the server hangs due to some reason. I just attached the full gdb log with backtrace while logging out from KDE4 session. I hope this will give us some clue.
Ok, it looks like this SIGHUP in the gdb log is intencional and it means that the server received a signal for resetting. Correct me if I am wrong. I have no deep understanding of xorg-server. Nevertheless, I have tested the same setup with xdm and without loging to KDE, i.e. with xterm running only (no WM), and after logging out I observe the same behavior after switching to the text console. When I use radeonhd, everything works well with this setup.
I don't have that notebook anymore. Since it is an old bug and not valid anymore, I am closing it.
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.