[ltp] Re: Fwd: Working 3D acceleration on IBM ThinkPad T23 ;-)
Alex Deucher
linux-thinkpad@linux-thinkpad.org
Fri, 6 Jan 2006 09:15:40 -0500
On 1/6/06, Eric Van Buggenhaut <eric@sindominio.net> wrote:
> On Fri, Jan 06, 2006 at 02:35:31PM +0100, Eric Van Buggenhaut wrote:
> > On Fri, Jan 06, 2006 at 01:20:53PM +0100, Eric Van Buggenhaut wrote:
> > > On Fri, Jan 06, 2006 at 11:23:19AM +0100, Martin Steigerwald wrote:
> > > > Am Freitag 06 Januar 2006 01:04 schrieb Eric Van Buggenhaut:
> > > >
> > > > > Thanks for the details. Do you know what I have to do after insta=
lling
> > > > > libgl1-mesa-dri to have X using the r300_dri.so module ?
> > > >
> > > > Hello Eric,
> > > >
> > > > almost everything has been said in this thread already:
> > > >
> > > > Run "glxgears" and save its output somewhere, if you want to find o=
ut the
> > > > difference between 3D acceleration or no 3D acceleration.
> > > >
> > > > Have a kernel with savage DRM module. Since Linux 2.6.14 its in the
> > > > mainstream kernel source. You can use the official debian sid/etch =
kernel
> > > > packages or create your own kernel package. If you happen to have a=
IBM
> > > > ThinkPad T23 I can give you a suitable config ;-) and instructions =
to get
> > > > it set up with Software Suspend 2 ;-), but I also have a config whi=
ch
> > > > only uses software suspend as in the kernel.
> > > >
> > > > Have X.org 6.9 from sid (there is also a backport for sarge users a=
lready:
> > > > http://www.backports.org).
> > > >
> > > > Install the savage DRI driver, either from the snapshot archive or =
just
> > > > install the package libgl1-mesa-dri ;-)
> > > >
> > > > Make sure the DRI module is loaded in /etc/X11/xorg.conf
> > > >
> > > > Section "Module"
> > > > [...]
> > > > Load "dri"
> > > > [...]
> > > > EndSection
> > > >
> > > > Restart X.org and try
> > > >
> > > > glxinfo | grep -i direct
> > > >
> > > > It should return:
> > > > direct rendering: Yes
> > > >
> > > > When it gives a segmentation fault, reboot your machine completely =
and try
> > > > again.
> > > >
> > > > Try "glxgears". It should report a higher framerate now.
> > > >
> > >
> > > Working now, thanks a lot ! I get this:
> > >
> > > [eric@atto:~]$ glxinfo |grep -i direct
> > > *********************************WARN_ONCE***************************=
******
> > > File r300_state.c function r300Enable line 456
> > > TODO - double side stencil !
> > > *********************************************************************=
******
> > > No ctx->FragmentProgram._Current!!
> > > direct rendering: Yes
> > >
> > > [eric@atto:~]$ [eric@atto:~]$ glxgears
> > > *********************************WARN_ONCE***************************=
******
> > > File r300_state.c function r300Enable line 456
> > > TODO - double side stencil !
> > > *********************************************************************=
******
> > > No ctx->FragmentProgram._Current!!
> > > *********************************WARN_ONCE***************************=
******
> > > File r300_render.c function r300_get_num_verts line 188
> > > user error: Need more than 2 vertices to draw primitive QS !
> > > *********************************************************************=
******
> > > 3902 frames in 5.0 seconds =3D 780.400 FPS
> > > 4430 frames in 5.0 seconds =3D 886.000 FPS
> > > 4433 frames in 5.0 seconds =3D 886.600 FPS
> > >
> > > Is this a reasonable rate ?
> > >
> > > Regards,
> > >
> >
> > I guess I messed things up, acceleration is gone now and I can't get it
> > back :((
> >
> > [eric@atto:~]$ glxinfo |grep -i render
> > direct rendering: No
> > OpenGL renderer string: Mesa GLX Indirect
> >
> >
> > I just restarted X and it's gone... I probably changed some packages
> > on the system and broke the good config. Now I'm lost, I can't direct
> > rendering either with:
> >
> > ii libgl1-mesa-dri 6.3.2-2
> > rc xlibmesa-gl 6.9.0.dfsg.1-1
> > rc xlibmesa-dri 6.9.0.dfsg.1-1
> > ii xlibmesa-glu 6.8.2-10
> >
> > installed, nor with
> >
> > rc libgl1-mesa-dri 6.3.2-2
> > ii xlibmesa-dri 6.9.0.dfsg.1-1
> > ii xlibmesa-gl 6.9.0.dfsg.1-1
> > ii xlibmesa-glu 6.8.2-10
> >
> > I have to add that I didn't touch /etc/X11/xorg.conf
> >
> > At which point did I go wrong ?
> >
>
> This thing is driving me nuts. I had direct rendering working fine
> again after rebooting the laptop:
>
> (II) RADEON(0): [drm] DRM interface version 1.2
> (II) RADEON(0): [drm] created "radeon" driver at busid "pci:0000:01:00.0"
> (II) RADEON(0): [drm] added 8192 byte SAREA at 0xf99f1000
> (II) RADEON(0): [drm] mapped SAREA 0xf99f1000 to 0xb7fd6000
> (II) RADEON(0): [drm] framebuffer handle =3D 0xe0000000
> (II) RADEON(0): [drm] added 1 reserved context for kernel
> (II) RADEON(0): [agp] Mode 0x1f000211 [AGP 0x8086/0x3340; Card 0x1002/0x4=
e50]
> (II) RADEON(0): [agp] 8192 kB allocated with handle 0x00000001
> (II) RADEON(0): [agp] ring handle =3D 0xd0000000
> (II) RADEON(0): [agp] Ring mapped at 0xb3770000
> (II) RADEON(0): [agp] ring read ptr handle =3D 0xd0101000
> (II) RADEON(0): [agp] Ring read ptr mapped at 0xb376f000
> (II) RADEON(0): [agp] vertex/indirect buffers handle =3D 0xd0102000
> (II) RADEON(0): [agp] Vertex/indirect buffers mapped at 0xb356f000
> (II) RADEON(0): [agp] GART texture map handle =3D 0xd0302000
> (II) RADEON(0): [agp] GART Texture map mapped at 0xb308f000
> (II) RADEON(0): [drm] register handle =3D 0xc0100000
> (II) RADEON(0): [dri] Visual configs initialized
> (II) RADEON(0): Depth moves disabled by default
> (II) RADEON(0): CP in BM mode
> (II) RADEON(0): Using 8 MB GART aperture
> (II) RADEON(0): Using 1 MB for the ring buffer
> (II) RADEON(0): Using 2 MB for vertex/indirect buffers
> (II) RADEON(0): Using 5 MB for GART textures
> [...]
> (II) RADEON(0): [DRI] installation complete
> (II) RADEON(0): [drm] Added 32 65536 byte vertex/indirect buffers
> (II) RADEON(0): [drm] Mapped 32 vertex/indirect buffers
> (II) RADEON(0): [drm] dma control initialized, using IRQ 11
> (II) RADEON(0): [drm] Initialized kernel GART heap manager, 5111808
> (II) RADEON(0): Direct rendering enabled
> (=3D=3D) RandR enabled
>
> then I logged out and relaunched X:
>
> (II) RADEON(0): [drm] DRM interface version 1.2
> (II) RADEON(0): [drm] created "radeon" driver at busid
> "pci:0000:01:00.0"
> (II) RADEON(0): [drm] drmAddMap failed
> (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI.
> (II) RADEON(0): Depth moves disabled by default
> (II) RADEON(0): Memory manager initialized to (0,0) (1408,8191)
> (II) RADEON(0): Reserved area from (0,1050) to (1408,1052)
> (II) RADEON(0): Largest offscreen area available: 1408 x 7139
> (II) RADEON(0): Render acceleration unsupported on Radeon 9500/9700
> and newer.
> (II) RADEON(0): Render acceleration disabled
> [...]
> (II) RADEON(0): [drm] DRM interface version 1.2
> (II) RADEON(0): [drm] created "radeon" driver at busid "pci:0000:01:00.0"
> (II) RADEON(0): [drm] drmAddMap failed
> (EE) RADEON(0): [dri] DRIScreenInit failed. Disabling DRI.
>
>
> Does it mean a problem with radeon kernel module rather than X ?
>
looks like a problem with the drm. what version are you using? also
what drm messages show up in dmesg? does unloading and reloading the
drm help? also make sure the genreic drm layer and the radeon drm
module are loaded.
Alex
> --
> Eric VAN BUGGENHAUT
> Eric.VanBuggenhaut@AdValvas.be