| 1 |
========================== |
| 2 |
> $ glxgears |
| 3 |
> libGL warning: 3D driver claims to not support visual 0x4b |
| 4 |
> 2446 frames in 5.0 seconds = 489.111 FPS |
| 5 |
> 2441 frames in 5.0 seconds = 488.094 FPS |
| 6 |
> 2448 frames in 5.0 seconds = 489.509 FPS |
| 7 |
> 2438 frames in 5.0 seconds = 487.576 FPS |
| 8 |
> 2445 frames in 5.0 seconds = 488.976 FPS |
| 9 |
> 2442 frames in 5.0 seconds = 488.238 FPS |
| 10 |
> 2439 frames in 5.0 seconds = 487.720 FPS |
| 11 |
> ================================================== |
| 12 |
|
| 13 |
|
| 14 |
under 2.6.17-gentoo-r8 I get (glxgears): |
| 15 |
6751 frames in 5.0 seconds = 1350.118 FPS |
| 16 |
7174 frames in 5.0 seconds = 1434.668 FPS |
| 17 |
6596 frames in 5.0 seconds = 1319.182 FPS |
| 18 |
6946 frames in 5.0 seconds = 1389.107 FPS |
| 19 |
6582 frames in 5.0 seconds = 1316.222 FPS |
| 20 |
5700 frames in 5.0 seconds = 1139.907 FPS |
| 21 |
7038 frames in 5.0 seconds = 1407.494 FPS |
| 22 |
6879 frames in 5.0 seconds = 1375.700 FPS |
| 23 |
6737 frames in 5.0 seconds = 1347.254 FPS |
| 24 |
7072 frames in 5.0 seconds = 1414.338 FPS |
| 25 |
7027 frames in 5.0 seconds = 1405.366 FPS |
| 26 |
|
| 27 |
> ================================================== |
| 28 |
> $ glxinfo |
| 29 |
> name of display: :0.0 |
| 30 |
> libGL warning: 3D driver claims to not support visual 0x4b |
| 31 |
> display: :0 screen: 0 |
| 32 |
> direct rendering: Yes |
| 33 |
> ================================================== |
| 34 |
|
| 35 |
under glxinfo (2.6.17-gentoo-r8): |
| 36 |
|
| 37 |
name of display: :0.0 |
| 38 |
display: :0 screen: 0 |
| 39 |
direct rendering: Yes |
| 40 |
server glx vendor string: SGI |
| 41 |
server glx version string: 1.2 |
| 42 |
<snip very long listing of info> |
| 43 |
|
| 44 |
> |
| 45 |
> While you're looking at this I would appreciate if you could tell me why I am |
| 46 |
> getting this libGL warning (and how to fix it)? |
| 47 |
|
| 48 |
> Finally, I am also getting this mtrr overlap at boot: |
| 49 |
> ================================================== |
| 50 |
> mtrr: 0x48000000,0x8000000 overlaps existing 0x48000000,0x1000000 |
| 51 |
> mtrr: 0x48000000,0x8000000 overlaps existing 0x48000000,0x1000000 |
| 52 |
> mtrr: 0x48000000,0x8000000 overlaps existing 0x48000000,0x1000000 |
| 53 |
> mtrr: 0x48000000,0x8000000 overlaps existing 0x48000000,0x1000000 |
| 54 |
> mtrr: 0x48000000,0x8000000 overlaps existing 0x48000000,0x1000000 |
| 55 |
> agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. |
| 56 |
> agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode |
| 57 |
> agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode |
| 58 |
> [drm] Setting GART location based on new memory map |
| 59 |
> [drm] writeback test succeeded in 1 usecs |
| 60 |
> ==== |
| 61 |
|
| 62 |
under glxinfo (2.6.17-gentoo-r8) && greping dmesg for9 gl drm agp) I get: |
| 63 |
[drm] Initialized drm 1.0.1 20051102 |
| 64 |
[drm] Initialized radeon 1.24.0 20060225 on minor 0 |
| 65 |
[drm] Setting GART location based on new memory map |
| 66 |
[drm] Loading R200 Microcode |
| 67 |
[drm] writeback test succeeded in 1 usecs |
| 68 |
|
| 69 |
agpgart: Detected SiS 646 chipset |
| 70 |
agpgart: AGP aperture is 64M @ 0xe8000000 |
| 71 |
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. |
| 72 |
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode |
| 73 |
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode |
| 74 |
|
| 75 |
Does look suspicious.... |
| 76 |
|
| 77 |
Now I'm off to test my new 2.6.18-gentoo-r2 kernel |
| 78 |
|
| 79 |
|
| 80 |
James |
| 81 |
|
| 82 |
-- |
| 83 |
gentoo-user@g.o mailing list |
Archives