Created attachment 46090 [details] Screenshot showing corrupt GL rendering in glxgears as an example Hi, I was asked there (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=622299#67) to report this bug upstream. GL rendering is currently corrupt on IA-64 with Gallium r300 driver (cf. attached screenshot with running glxgears as an example). Classic driver renders display correctly. Regards, Émeric
Does current Git master work better? At least some of the Gallium code was not detecting the endianness of this architecture correctly.
Created attachment 50365 [details] Screenshot showing correct GL rendering in glxgears with current Git master (7.12-devel (git-ccecc08))
(In reply to comment #1) > Does current Git master work better? At least some of the Gallium code was not > detecting the endianness of this architecture correctly. Hi Michel, Sorry for the very late reply! But it was worth waiting for it: I just finished recompiling current Git master (Mesa 7.12-devel (git-ccecc08)). As you can see in the attached screenshot, glxgears now renders correctly :-) I don't know though if 3D hardware acceleration is fully working: I get no particular warning/error in dmesg or Xorg.0.log, but glxgears FPS seem very low to me (~85 FPS). Émeric
(In reply to comment #3) > I don't know though if 3D hardware acceleration is fully working: I get no > particular warning/error in dmesg or Xorg.0.log, but glxgears FPS seem very low > to me (~85 FPS). As the glxgears output explains, it synchronizes to the refresh rate by default, so that may be okay. Check the glxinfo output, and maybe try vblank_mode=0 glxgears to disable synchronization.
(In reply to comment #4) > As the glxgears output explains, it synchronizes to the refresh rate by > default, so that may be okay. Check the glxinfo output, and maybe try > > vblank_mode=0 glxgears > > to disable synchronization. That's it. Without synchronization, I'm getting ~1700 FPS. I also gave ioQuake3-based Debian "Wheezy" Testing quake3 a try. Ran flawlessly.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.