Arch Linux

Gullible Jones

Member

Registered: 2004-12-29

Posts: 4,863

Does LIBGL_ALWAYS_INDIRECT still work for you?

Those of you who have AIGLX-capable video hardware: can you still force accelerated indirect rendering for OpenGL stuff, using LIBGL_ALWAYS_INDIRECT=1, without X freezing solid? Or does LIBGL_ALWAYS_INDIRECT cause a lockup?

kth5

Member

Registered: 2004-04-29

Posts: 657

Website

Re: Does LIBGL_ALWAYS_INDIRECT still work for you?

Hmm, so this might be a little late to ask but I never really understood what actually happens when the driver detects AIGLX capable hardware and displays somehting like this in Xorg.0.log:

(II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/r200_dri.so
(II) GLX: Initialized DRI GL provider for screen 0

Does it use AIGLX or the regular DRI preferably? What about these btw:

drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: Searching for BusID pci:0000:00:10.0
drmOpenDevice: node name is /dev/dri/card0
drmOpenDevice: open result is 8, (OK)
drmOpenByBusid: drmOpenMinor returns 8
drmOpenByBusid: drmGetBusid reports pci:0000:00:10.0
(WW) AIGLX: 3D driver claims to not support visual 0x23
(WW) AIGLX: 3D driver claims to not support visual 0x24
(WW) AIGLX: 3D driver claims to not support visual 0x25
(WW) AIGLX: 3D driver claims to not support visual 0x26
(WW) AIGLX: 3D driver claims to not support visual 0x27
(WW) AIGLX: 3D driver claims to not support visual 0x28
(WW) AIGLX: 3D driver claims to not support visual 0x29
(WW) AIGLX: 3D driver claims to not support visual 0x2a
(WW) AIGLX: 3D driver claims to not support visual 0x2b
(WW) AIGLX: 3D driver claims to not support visual 0x2c
(WW) AIGLX: 3D driver claims to not support visual 0x2d
(WW) AIGLX: 3D driver claims to not support visual 0x2e
(WW) AIGLX: 3D driver claims to not support visual 0x2f
(WW) AIGLX: 3D driver claims to not support visual 0x30
(WW) AIGLX: 3D driver claims to not support visual 0x31
(WW) AIGLX: 3D driver claims to not support visual 0x32
(II) AIGLX: Loaded and initialized /usr/lib/xorg/modules/dri/r200_dri.so
(II) GLX: Initialized DRI GL provider for screen 0
(**) Option "Protocol" "IMPS/2"
(**) Mouse1: Device: "/dev/input/mice"
(**) Mouse1: Protocol: "IMPS/2"
(**) Option "CorePointer"
(**) Mouse1: Core Pointer
(**) Option "Device" "/dev/input/mice"

Sorry, also want to ask someone before I go diggin in myself once.

Most importantly, yes LIBGL_ALWAYS_INDIRECT=1does still affects the Xserver. It is switching to indirect rendering as glxinfo suggests while most OpenGL apps such as neverball run just fine still. Sorry, didn't try beryl or anything heh. This is on a mac though using archppc, similar setup what goes for versions though.

---

I recognize that while theory and practice are, in theory, the same, they are, in practice, different. -Mark Mitchell

Gullible Jones

Member

Registered: 2004-12-29

Posts: 4,863

Re: Does LIBGL_ALWAYS_INDIRECT still work for you?

Thanks... I'm on Arch-32 though. Have to find out whether this is driver-related or a problem with all video cards.

Gullible Jones

Member

Registered: 2004-12-29

Posts: 4,863

Re: Does LIBGL_ALWAYS_INDIRECT still work for you?

Sorry for the bump, but I'd really like it if someone could confirm this for 32-bit Arch. It's starting to look like some update broke AIGLX for Unichrome.

hacosta

Member

From: Mexico

Registered: 2006-10-22

Posts: 423

Re: Does LIBGL_ALWAYS_INDIRECT still work for you?

yeah it crashed on me too..

..crashed hard