Am Donnerstag 10 Mai 2007 schrieb Brice Goglin: > Hi Martin, > > Thanks you for your answers, but it is not clear for me whether the > initial bug report is fixed on not. So: > Does Xorg still hang on logout ? even with EXA *disabled* ? Hello Brice! Yes. It also hangs with XAA disabled. > > Well, no, KDM doesn't start at all. X is running, but the garbled > > display actually was tty1. Rebooted now. > Why would KDM refuse to start at all if X is running? Or is KDM running > but not displaying anything because of a problem in X? > What about this problem if EXA is *disabled*? > Are you talking of KDM right after logout, or KDM after reboot? KDM after reboot is working correctly. Its about KDM after logout. It doesn't display a login screen then. I was logged into the machine via SSH to be able to do some diagnostics and I tried /etc/init.d/kdm restart in order to get a login screen. Then it told me that KDM was not running before it tried to start it again. Starting it again didn't work also. I have to reboot the machine twice cause of that. > > Anyway, EXA does not seem to be usable. > > This looks like a different issue, we should open a new bug about this. > Some screen corruptions on savage with EXA have been reported upstream > at [1]. Does the screenshot [2] look like what you are seeing? Not quite... I attached a screenshot to my last mail to this bug report. Should I open a new bug report or should we clone this one? Actually I had this screen corruption even without EXA. But it just happened once I tried to logout and tried to restart KDM or when I tried to switch between TTY1 and X after I tried to logout. It has gotten worse, cause with the older version I restarting KDM brought the login screen back. Now I get that complete screen garbage and have to reboot the machine as soon as I need more than a SSH login to it. I am using VESA framebuffer driver, not the Savage one, cause I read von savage mailinglist that the framebuffer driver and the X.org one do not handle resetting registers gracefully. I am using this self compiled kernel martin@deepdance:~> cat /proc/version Linux version 2.6.21.1-tp23-cfs-v11-sws2-2.2.9.13 (martin@deepdance) (gcc version 4.1.2 20061115 (prerelease) (Debian 4.1.1-21)) #1 PREEMPT Thu May 10 14:40:21 CEST 2007 with these kernel options: root=/dev/sda5 ro resume2=swap:/dev/sda7 resume=/dev/sda7 vga=792 atapi_enabled=1 I did my testing after a fresh boot, so there has not been a snapshot cycle before that. I sent a mail to upstream mailinglist, mentioning my bug report. I am a bit unsure on how to go on. It seems there are several issues and it would be good to isolate them and put them into different bug reports. There are a lot of different combinations to test and it will be difficult for me to take enough time to do this testing. That said, the issues are not really urgent to me - so we could go through it step by them and take the time it needs. Since I got an T42 my T23 mainly serves as Amarok based music jukebox and as long as graphics display works after a snapshot cycle it will work for me. I only need 2D graphics anyway. I just could use a bit of guidance on how to proceed with testing and reporting and I will take the time to do so as could as I can without neglecting higher priority stuff. Regards, -- Martin 'Helios' Steigerwald - http://www.Lichtvoll.de GPG: 03B0 0D6C 0040 0710 4AFA B82F 991B EAAC A599 84C7
Attachment:
pgpFDWvXILUsU.pgp
Description: PGP signature