From: Daniel B. <ipa...@gm...> - 2006-04-27 15:37:30
|
Hoi! I recently updated my X to xorg7 and since then I keep having strange behaviour of OpenGL apps (especially glxgears and 3ddesktop). A friend of mine said that it might be a bug in mesa, so I subscribed to this list to see what other people think. When I run glxgears, the gears window pops up and the gears start spinning as normal (no errors or so, everything works fine with DRI active). However, as soon as another window gets infront of the glxgears window, the gears suddenly pop out of the center of the window half over the left edge of the window, so only the right half of the construct remains visible. As soon as the glxgears window is moved the gears pop back in into their normal position. 3ddesktop happens to be victim of the same bug. The "virtual desktop space" is offset to the left, so that only the right half of the space is visible. glxdemo and glxheads seem to have the same problems. Greets Daniel |
From: Brian P. <bri...@tu...> - 2006-04-27 16:42:06
|
Daniel Baulig wrote: > Hoi! > > I recently updated my X to xorg7 and since then I keep having strange > behaviour of OpenGL apps (especially glxgears and 3ddesktop). > A friend of mine said that it might be a bug in mesa, so I subscribed to > this list to see what other people think. > > When I run glxgears, the gears window pops up and the gears start > spinning as normal (no errors or so, everything works fine with DRI > active). However, as soon as another window gets infront of the glxgears > window, the gears suddenly pop out of the center of the window half over > the left edge of the window, so only the right half of the construct > remains visible. As soon as the glxgears window is moved the gears pop > back in into their normal position. > > 3ddesktop happens to be victim of the same bug. The "virtual desktop > space" is offset to the left, so that only the right half of the space > is visible. > > glxdemo and glxheads seem to have the same problems. Sounds like a clipping bug in the driver. Which DRI driver are you using? -Brian |
From: Daniel B. <ipa...@gm...> - 2006-04-28 16:46:09
|
Hoi Brian! > Sounds like a clipping bug in the driver. Which DRI driver are you using? I'm not sure how to figure out which DRI driver I'm using - actually I'm not even sure what the DRI driver is. Here is some info I was able to figure out about DRI and some connected stuff: cat /var/log/Xorg.0.log | grep DRI (II) LoadModule: "dri" (II) Loading /usr/lib/xorg/modules/extensions/libdri.so (II) Module dri: vendor="X.Org Foundation" (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so ABI class: X.Org XInput driver, version 0.5 ABI class: X.Org XInput driver, version 0.5 ABI class: X.Org XInput driver, version 0.5 (II) ATI: ATI driver (version 6.5.7) for chipsets: ati, ativga (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: node name is /dev/dri/card0 drmOpenDevice: node name is /dev/dri/card0 (II) RADEON(0): [drm] loaded kernel module for "radeon" driver (II) RADEON(0): [drm] created "radeon" driver at busid "pci:0000:01:00.0" (WW) RADEON(0): [dri] color tiling disabled because of version mismatch. [dri] radeon.o kernel module version is 1.11.0 but 1.14.0 or later is required for color tiling. (II) RADEON(0): [dri] Visual configs initialized libdri.so is from the packet xserver-xorg-core which is installed in the version 1.0.2-6 I hooe I provided the information you requested, if not please give me a hint how to obtain it. Thanks a lot! Greets Daniel |
From: Brian P. <bri...@tu...> - 2006-04-28 16:48:38
|
Daniel Baulig wrote: > Hoi Brian! > >> Sounds like a clipping bug in the driver. Which DRI driver are you >> using? > > > I'm not sure how to figure out which DRI driver I'm using - actually I'm > not even sure what the DRI driver is. Here is some info I was able to > figure out about DRI and some connected stuff: > > cat /var/log/Xorg.0.log | grep DRI > > (II) LoadModule: "dri" > (II) Loading /usr/lib/xorg/modules/extensions/libdri.so > (II) Module dri: vendor="X.Org Foundation" > (II) Loading /usr/lib/xorg/modules/drivers/ati_drv.so > ABI class: X.Org XInput driver, version 0.5 > ABI class: X.Org XInput driver, version 0.5 > ABI class: X.Org XInput driver, version 0.5 > (II) ATI: ATI driver (version 6.5.7) for chipsets: ati, ativga > (II) Loading /usr/lib/xorg/modules/drivers/radeon_drv.so > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: node name is /dev/dri/card0 > drmOpenDevice: node name is /dev/dri/card0 > (II) RADEON(0): [drm] loaded kernel module for "radeon" driver > (II) RADEON(0): [drm] created "radeon" driver at busid "pci:0000:01:00.0" > (WW) RADEON(0): [dri] color tiling disabled because of version mismatch. > [dri] radeon.o kernel module version is 1.11.0 but 1.14.0 or later is > required for color tiling. > (II) RADEON(0): [dri] Visual configs initialized > > libdri.so is from the packet xserver-xorg-core which is installed in the > version 1.0.2-6 > > I hooe I provided the information you requested, if not please give me a > hint how to obtain it. Thanks a lot! Looks like the radeon driver. Another way is to run 'glxinfo' and look for GL_RENDERER. -Brian |
From: Daniel B. <ipa...@gm...> - 2006-04-28 18:12:10
|
Hoi! Brian Paul wrote: > Looks like the radeon driver. Another way is to run 'glxinfo' and look > for GL_RENDERER. glxinfo gave me this on info regarding OpenGL rendering: OpenGL vendor string: Tungsten Graphics, Inc. OpenGL renderer string: Mesa DRI Radeon 20050528 AGP 1x TCL OpenGL version string: 1.2 Mesa 6.4.1 Greets Daniel |