On Wed, 2006-06-14 at 21:09 +0200, ruben wrote: > > Jun 14 20:11:07 guava kernel: [drm] Initialized drm 1.0.1 20051102 > Jun 14 20:11:07 guava kernel: [drm] Initialized radeon 1.24.0 20060225 on > minor 0 > Jun 14 20:11:19 guava kernel: agpgart: Putting AGP V2 device at 0000:00:0b.0 > into 1x mode > Jun 14 20:11:19 guava kernel: agpgart: Putting AGP V2 device at 0000:00:10.0 > into 1x mode > Jun 14 20:11:19 guava kernel: [drm] Setting GART location based on old memory > map
This looks like you could be hitting http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=369167 . Also beware of http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=363120 , so one has to make sure suspend/resume switches to console. > Jun 14 20:11:19 guava kernel: [drm] Loading R300 Microcode > Jun 14 20:11:19 guava kernel: [drm] writeback test failed > > Normally, that last line looks like this: > Jun 14 20:19:43 guava kernel: [drm] writeback test succeeded in 1 usecs > > I don't know whether that's important... It could be a symptom of the underlying problem. > it seems one can disable writeback with a parameter for the radeon module. It'll be disabled automatically if the test fails. -- Earthling Michel Dänzer | http://tungstengraphics.com Libre software enthusiast | Debian, X and DRI developer
