Brice Goglin a écrit : > > Can you try with a 2.6.33-rc kernel ? Ok, sorry for the delay but this is quite high voodoo for me :-)
I recompiled 2.6.33-rc8 with latest svn.debian.org patches, found and downloaded a missing firmware file here : http://people.freedesktop.org/~agd5f/radeon_ucode/R600_rlc.bin Now the symptom is different : the screen goes black, the system is unreachable on the network (even ping), and my harddrive completely stops moving. Which indicates a complete crash, not only the X part. As the system is completely crashed, I have nothing in syslog. Of course I can't be sure that the cause is the same because it is completely random and the symptom is different, but the frequency of the crashes is very similar. And it still works fine (but without dri2) without kms. By the way I have other problems with 2.6.33 and kms that are not present with 2.6.32 : my second screen never lights up (it does receive a signal, and is configurable in the gnome screen configuration panel, but it stays black), and there are artifacts in the titlebars of windows under gnome-shell (not in metacity). In the meantime I upgraded mesa to 7.7-4, but it still crashes. As there is never too much info, here is how I get kms (I might do something wrong) : I boot without X (which loads radeon without kms), login as root, modprobe -r radeon drm, modprobe radeon modeset=1, and then only start gdm. Maybe the system would react differently if radeon was loaded directly with kms enabled, but I don't know how to selectively achieve that at boot time. > By the way, your bug reports seem to have always the same wrongly > formatted From: line. Yes I just noticed this, it must come from the mail configuration on my laptop, but I already had a look and have absolutely no idea where it comes from. I'll investigate asap... Thanks, -- Rémi -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/4b879fa0.4070...@poukram.net
