========================== > $ glxgears > libGL warning: 3D driver claims to not support visual 0x4b > 2446 frames in 5.0 seconds = 489.111 FPS > 2441 frames in 5.0 seconds = 488.094 FPS > 2448 frames in 5.0 seconds = 489.509 FPS > 2438 frames in 5.0 seconds = 487.576 FPS > 2445 frames in 5.0 seconds = 488.976 FPS > 2442 frames in 5.0 seconds = 488.238 FPS > 2439 frames in 5.0 seconds = 487.720 FPS > ==================================================
under 2.6.17-gentoo-r8 I get (glxgears): 6751 frames in 5.0 seconds = 1350.118 FPS 7174 frames in 5.0 seconds = 1434.668 FPS 6596 frames in 5.0 seconds = 1319.182 FPS 6946 frames in 5.0 seconds = 1389.107 FPS 6582 frames in 5.0 seconds = 1316.222 FPS 5700 frames in 5.0 seconds = 1139.907 FPS 7038 frames in 5.0 seconds = 1407.494 FPS 6879 frames in 5.0 seconds = 1375.700 FPS 6737 frames in 5.0 seconds = 1347.254 FPS 7072 frames in 5.0 seconds = 1414.338 FPS 7027 frames in 5.0 seconds = 1405.366 FPS > ================================================== > $ glxinfo > name of display: :0.0 > libGL warning: 3D driver claims to not support visual 0x4b > display: :0 screen: 0 > direct rendering: Yes > ================================================== under glxinfo (2.6.17-gentoo-r8): name of display: :0.0 display: :0 screen: 0 direct rendering: Yes server glx vendor string: SGI server glx version string: 1.2 <snip very long listing of info> > > While you're looking at this I would appreciate if you could tell me why I am > getting this libGL warning (and how to fix it)? > Finally, I am also getting this mtrr overlap at boot: > ================================================== > mtrr: 0x48000000,0x8000000 overlaps existing 0x48000000,0x1000000 > mtrr: 0x48000000,0x8000000 overlaps existing 0x48000000,0x1000000 > mtrr: 0x48000000,0x8000000 overlaps existing 0x48000000,0x1000000 > mtrr: 0x48000000,0x8000000 overlaps existing 0x48000000,0x1000000 > mtrr: 0x48000000,0x8000000 overlaps existing 0x48000000,0x1000000 > agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. > agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode > agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode > [drm] Setting GART location based on new memory map > [drm] writeback test succeeded in 1 usecs > ==== under glxinfo (2.6.17-gentoo-r8) && greping dmesg for9 gl drm agp) I get: [drm] Initialized drm 1.0.1 20051102 [drm] Initialized radeon 1.24.0 20060225 on minor 0 [drm] Setting GART location based on new memory map [drm] Loading R200 Microcode [drm] writeback test succeeded in 1 usecs agpgart: Detected SiS 646 chipset agpgart: AGP aperture is 64M @ 0xe8000000 agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode Does look suspicious.... Now I'm off to test my new 2.6.18-gentoo-r2 kernel James -- gentoo-user@gentoo.org mailing list
