On Tue, Jan 25, 2011 at 9:31 AM, Ken Moffat <[email protected]> wrote: > On Tue, Jan 25, 2011 at 05:21:01AM -0800, Dan Nicholson wrote: >> On Sun, Jan 23, 2011 at 1:35 PM, Ken Moffat <[email protected]> >> wrote: >> >> >> > I'm more interested in how useful, or not, it turns out to be. >> > Maybe it's just my old hardware, but on the box with a radeon 7500 >> > I've built a full desktop with Mesa-7.9 and mesa-demos looks nice, >> > but glxgears is less than useful - it crashes if I try to move or >> > maximize its window. On that box, glxinfo works ok. Both multictx >> > and offset look nice, but no "mine's bigger than yours" numbers (and >> > in any case everything should now run at the screen's refresh rate >> > according to the glxgears text from 7.8.2). Other visual demos >> > report failed assertions in the radeon code. Xscreensaver works >> > fine. >> >> This is why glxgears _is_ useful. It's an extremely simple 3d program >> that lets you know if your driver can actually put pixels on the >> screen. When a new driver is being developed for mesa, the "hey >> everybody I got this working" moment is usually when gears can run >> without crashing. Clearly your driver is broken if it's crashing. All >> glxinfo does is load the driver and check extensions and visuals. Very >> important info, but not the same as actually running anything. >> > Thanks, Dan. > > Follow up question(s), sorry for venturing O/T for this list - > > Is it reasonable for me to raise either of the following two > problems as Mesa bugs, or should I raise them against mesa-demos ? > BTW, I haven't tested against Mesa-7.9 plus dj's patch to add these > progs. I guess that might be my next step, but I'm severely lacking > in available time at the moment. > > (a) radeon 7500 - > > with Mesa-7.9, glxgears works, but crashes if I try to resize its > window (both clicking on the maximize window control, and dragging > its borders). > > (b) radeon 9200se - > > with both Mesa-7.9 and 7.10, and mesa-demos-8.0.1, glxgears does > not produce the window with the gears and dies after reporting > Error: Unable to find RGB, Z, double-buffered visual > > In both cases, the same version of the ati driver and xorg-server, > with Mesa-7.8.2 (which includes the demos), work without problems.
Those both have to be driver stack bugs. glxgears is an incredibly simple program that hasn't changed in a long time. There are basically two important parts of the 3d stack when doing direct rendering - the mesa driver and the kernel driver. The xorg driver (xf86-video-ati) and server could certainly interact poorly, but most likely this is somewhere flowing down from libGL -> r*00_dri/radeon_dri -> libdrm/libdrm_radeon -> radeon.ko. So, you can try booting different kernels to see if the bug is in the drm driver. What kernel are you using? Does dmesg say anything interesting? Or, you can build an older version of mesa, set LIBGL_DRIVERS_PATH=$builddir/lib (might have the envvar wrong), and keep the kernel the same. Although, the error about missing visual could be a server interaction through glx. I don't know if you can get a backtrace on the 7500 crash, but that would be valuable. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
