On Sam, 2010-03-20 at 23:32 +0100, Cédric Boutillier wrote: > > > Can you provide the full dmesg, or at least the output of > > > dmesg|grep -e drm -e radeon > > Here is the output of dmesg|grep -e drm -e radeon for the first 60 > seconds. The rest is full of messages about sleep mode. > > ------8<------------------ > [ 0.000000] Kernel command line: root=/dev/mapper/pomme-root ro quiet > radeon.modeset=1 > [ 0.961495] radeonfb 0000:00:10.0: enabling device (0006 -> 0007) > [ 1.157118] radeonfb 0000:00:10.0: Invalid ROM contents > [ 1.157136] radeonfb (0000:00:10.0): Invalid ROM signature 0 should be > 0xaa55 > [ 1.157144] radeonfb: Retrieved PLL infos from Open Firmware > [ 1.157151] radeonfb: Reference=27.00 MHz (RefDiv=12) Memory=183.00 Mhz, > System=210.00 MHz > [ 1.157155] radeonfb: PLL min 12000 max 35000 > [ 1.913919] radeonfb: Monitor 1 type LCD found > [ 1.913922] radeonfb: EDID probed > [ 1.913926] radeonfb: Monitor 2 type no found > [ 1.913937] radeonfb: Using Firmware dividers 0x00020074 from PPLL 0 > [ 1.913998] radeonfb: Dynamic Clock Power Management enabled > [ 1.954679] radeonfb: Backlight initialized (radeonbl0) > [ 1.954684] radeonfb (0000:00:10.0): ATI Radeon 4e56 "NV" > [ 22.160205] [drm] Initialized drm 1.1.0 20060810 > [ 22.276152] [drm] radeon kernel modesetting enabled. > [ 61.858874] radeonfb 0000:00:10.0: Invalid ROM contents > [ 61.859073] radeonfb 0000:00:10.0: Invalid ROM contents > ------>8------------------
As I suspected, radeonfb is active. You'll have to disable that, otherwise it prevents KMS from taking ownership of the GPU. -- Earthling Michel Dänzer | http://www.vmware.com Libre software enthusiast | Debian, X and DRI developer -- To UNSUBSCRIBE, email to debian-powerpc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/1269371097.16545.13.ca...@thor.local
