Bug#570466: not fixed after all

2010-03-08 Thread Michel Dänzer
On Mon, 2010-03-08 at 00:32 +0100, Rémi Letot wrote: 
 Hello,
 
 the stability of my laptop was apparently due to a missing firmware file
 (R600_rlc.bin), which prevented DRI2 to work. Now that I have that file
 back (I also upgraded to latest 2.6.33 kernel from experimental), I have
 problems again with KMS/DRI2.
 
 However the problem evolved, as my laptop does not completely crash
 anymore. Only the screen randomly turns blank and doesn't come back.
 
 For example, I can still switch to a VT. The screen somehow flickers but
 remains blank, but I can blindly login and issue commands or reboot. I
 suspect that my X session is still useable, but of course without
 knowing where my pointer is, it's quite complicated to prove :-)
 
 I logged in through ssh, and X is no longer using 100% CPU. I have no
 error in syslog or the Xorg log, so it seems that the beast is blind but
 didn't notice anything unusual.
 
 Tell me if I can help further.

Please post your Xorg.0.log and dmesg output from when the problem
occurs.


-- 
Earthling Michel Dänzer   |http://www.vmware.com
Libre software enthusiast |  Debian, X and DRI developer



--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org



Bug#570466: not fixed after all

2010-03-07 Thread Rémi Letot
Hello,

the stability of my laptop was apparently due to a missing firmware file
(R600_rlc.bin), which prevented DRI2 to work. Now that I have that file
back (I also upgraded to latest 2.6.33 kernel from experimental), I have
problems again with KMS/DRI2.

However the problem evolved, as my laptop does not completely crash
anymore. Only the screen randomly turns blank and doesn't come back.

For example, I can still switch to a VT. The screen somehow flickers but
remains blank, but I can blindly login and issue commands or reboot. I
suspect that my X session is still useable, but of course without
knowing where my pointer is, it's quite complicated to prove :-)

I logged in through ssh, and X is no longer using 100% CPU. I have no
error in syslog or the Xorg log, so it seems that the beast is blind but
didn't notice anything unusual.

Tell me if I can help further.

Thanks,
-- 
Rémi



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org