When starting X the computer locks up with a garbled screen. I will attach a picture of it. The screen also "flashes" at a high frequenzy. I cannot get the computer to respond in anyway other than shutting it off with the button (holding for a few seconds). This only happens when booting the kernel i915.modeset=1. Without KMS everything works as expected. Hardware is a IBM Thinkpad R51 with 855GM. 00:02.0 VGA compatible controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) 00:02.1 Display controller: Intel Corporation 82852/855GM Integrated Graphics Device (rev 02) Software: kernel-2.6.29-rc2 xf86-video-intel-2.6.0 libdrm-2.4.3 xorg-server-1.5.99.901 mesa-7.3_rc2 With kernel version 2.6.29-rc1 this does not happen (there are other problems but i could still start X).
Created attachment 22048 [details] xorg configuration
Created attachment 22049 [details] Screenshot of failing X
Can you attach your X log? Or is the machine totally dead (i.e. you can't even login to it from the network)? Also, does -rc3 work?
The machine is totally dead i'm afraid. I tried removing the xorg log file before starting X but it wasn't there after a restart. This issue is still happening with: kernel-2.6.29-rc3 xf86-video-intel-2.6.1 libdrm-2.4.4 xorg-server-1.5.99.901 mesa-7.3 A note: I think one of the drm fixes between rc1 and rc2 involved some pointer fixes. In rc1 i had a corrupt cursor, it was a 64x64 (my perception of it's size) square with lots of bright pixels some transparent.
I managed to get my system to save the Xorg.0.log file by mounting root with mount option sync. I will attach it. Since this bug was registrered I have updated my xorg.conf file but it still has the same problem. I will replace the attached xorg.conf if possible, otherwise i will create a new one. I will also attach dmesg.
Created attachment 22416 [details] xorg log file of failing X
Created attachment 22417 [details] xorg configuration
Created attachment 22418 [details] dmesg with i915.modeset=1 (2.6.29-rc3)
Another thing came to mind: With 2.6.29-rc1 and kernel modesetting xrandr reported 1024x1024 as the only available resolution. Sorry for the "spamming".
I get the same error with 2.6.29-rc4, with two exceptions. The machine doesn't hardlock, i can ssh to it and shut it down in a correct way. The log file is also missing a few lines from the end if you compare it to the previous ones.
Created attachment 22765 [details] Xorg log 2.6.29-rc4
Steve fixed some memory corruption, can you give this patch a try? http://lists.freedesktop.org/archives/intel-gfx/2009-February/001359.html
Applying the patch makes the screen corruption go away, i can now enter X. I still have the other problems i had in rc1 (wrong resolution, hangs when changing vt/closing x) export for pointer corruption. I will file separate bugs for these unless they already exist.
I'm getting something very similar to this but after X would work for a while - so yes it's awful, since the laptop freezes in the middle of work. Kernel: 2.6.29-rc7 (i915.modeset=1) xf86-video-intel: 2.6.3 xorg-server: 1.6.0 libdrm: 2.4.5 Hardware: 945gm (Thinkpad X60s) I don't use compoziting nor 3D (I use awesome). So the problem is, the computer freezes and I get very strange patterns on the screen... not random noise, but still nothing eligible. Disableing KMS seems to prevent the lockup ... except, if it only postpones it for much later, dunno.
Latest kernel should have a fix for this, can you confirm?
Have you had a chance to test yet?
Hmm, i though i replied, oh well. This does not happen for me anymore, it works as it should in 2.6.29. I do have another problem preventing me from using KMS reliably (which i haven't reported yet, due to my laziness). //Markus
Yeah seems to be working for me as well. Closing.
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.