1 |
James <wireless <at> tampabay.rr.com> writes: |
2 |
|
3 |
> |
4 |
> ========================== |
5 |
> > $ glxgears |
6 |
> > libGL warning: 3D driver claims to not support visual 0x4b |
7 |
> > 2446 frames in 5.0 seconds = 489.111 FPS |
8 |
> > 2441 frames in 5.0 seconds = 488.094 FPS |
9 |
> > 2448 frames in 5.0 seconds = 489.509 FPS |
10 |
> > 2438 frames in 5.0 seconds = 487.576 FPS |
11 |
> > 2445 frames in 5.0 seconds = 488.976 FPS |
12 |
> > 2442 frames in 5.0 seconds = 488.238 FPS |
13 |
> > 2439 frames in 5.0 seconds = 487.720 FPS |
14 |
> > ================================================== |
15 |
> |
16 |
> under 2.6.17-gentoo-r8 I get (glxgears): |
17 |
> 6751 frames in 5.0 seconds = 1350.118 FPS |
18 |
> 7174 frames in 5.0 seconds = 1434.668 FPS |
19 |
> 6596 frames in 5.0 seconds = 1319.182 FPS |
20 |
> 6946 frames in 5.0 seconds = 1389.107 FPS |
21 |
> 6582 frames in 5.0 seconds = 1316.222 FPS |
22 |
> 5700 frames in 5.0 seconds = 1139.907 FPS |
23 |
> 7038 frames in 5.0 seconds = 1407.494 FPS |
24 |
> 6879 frames in 5.0 seconds = 1375.700 FPS |
25 |
> 6737 frames in 5.0 seconds = 1347.254 FPS |
26 |
> 7072 frames in 5.0 seconds = 1414.338 FPS |
27 |
> 7027 frames in 5.0 seconds = 1405.366 FPS |
28 |
> |
29 |
> > ================================================== |
30 |
|
31 |
under 2.6.18-gentoo-r2: |
32 |
|
33 |
7790 frames in 5.0 seconds = 1557.990 FPS |
34 |
57673 frames in 5.0 seconds = 11534.464 FPS |
35 |
57865 frames in 5.0 seconds = 11572.907 FPS |
36 |
56563 frames in 5.0 seconds = 11312.441 FPS |
37 |
54164 frames in 5.0 seconds = 10832.644 FPS |
38 |
53139 frames in 5.0 seconds = 10627.705 FPS |
39 |
56300 frames in 5.0 seconds = 11259.851 FPS |
40 |
54578 frames in 5.0 seconds = 10915.574 FPS |
41 |
55864 frames in 5.0 seconds = 11172.672 FPS |
42 |
|
43 |
|
44 |
looks improved? |
45 |
|
46 |
|
47 |
> > $ glxinfo |
48 |
> > name of display: :0.0 |
49 |
> > libGL warning: 3D driver claims to not support visual 0x4b |
50 |
> > display: :0 screen: 0 |
51 |
> > direct rendering: Yes |
52 |
> > ================================================== |
53 |
> |
54 |
> under glxinfo (2.6.17-gentoo-r8): |
55 |
> |
56 |
> name of display: :0.0 |
57 |
> display: :0 screen: 0 |
58 |
> direct rendering: Yes |
59 |
> server glx vendor string: SGI |
60 |
> server glx version string: 1.2 |
61 |
> <snip very long listing of info> |
62 |
|
63 |
|
64 |
name of display: :0.0 |
65 |
display: :0 screen: 0 |
66 |
direct rendering: Yes |
67 |
server glx vendor string: SGI |
68 |
server glx version string: 1.2 |
69 |
|
70 |
|
71 |
> > While you're looking at this I would appreciate if you could |
72 |
> > tell me why I am |
73 |
> > getting this libGL warning (and how to fix it)? |
74 |
> |
75 |
> > Finally, I am also getting this mtrr overlap at boot: |
76 |
> > ================================================== |
77 |
> > mtrr: 0x48000000,0x8000000 overlaps existing 0x48000000,0x1000000 |
78 |
> > mtrr: 0x48000000,0x8000000 overlaps existing 0x48000000,0x1000000 |
79 |
> > mtrr: 0x48000000,0x8000000 overlaps existing 0x48000000,0x1000000 |
80 |
> > mtrr: 0x48000000,0x8000000 overlaps existing 0x48000000,0x1000000 |
81 |
> > mtrr: 0x48000000,0x8000000 overlaps existing 0x48000000,0x1000000 |
82 |
> > agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. |
83 |
> > agpgart: Putting AGP V2 device at 0000:00:00.0 into 4x mode |
84 |
> > agpgart: Putting AGP V2 device at 0000:01:00.0 into 4x mode |
85 |
> > [drm] Setting GART location based on new memory map |
86 |
> > [drm] writeback test succeeded in 1 usecs |
87 |
> > ==== |
88 |
> |
89 |
> under glxinfo (2.6.17-gentoo-r8) && greping dmesg for9 gl drm agp) I get: |
90 |
> [drm] Initialized drm 1.0.1 20051102 |
91 |
> [drm] Initialized radeon 1.24.0 20060225 on minor 0 |
92 |
> [drm] Setting GART location based on new memory map |
93 |
> [drm] Loading R200 Microcode |
94 |
> [drm] writeback test succeeded in 1 usecs |
95 |
> |
96 |
> agpgart: Detected SiS 646 chipset |
97 |
> agpgart: AGP aperture is 64M <at> 0xe8000000 |
98 |
> agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. |
99 |
> agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode |
100 |
> agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode |
101 |
> |
102 |
> Does look suspicious.... |
103 |
|
104 |
|
105 |
dmesg | grep drm |
106 |
[drm] Initialized drm 1.0.1 20051102 |
107 |
[drm] Initialized radeon 1.25.0 20060524 on minor 0 |
108 |
[drm] Setting GART location based on new memory map |
109 |
[drm] Loading R200 Microcode |
110 |
[drm] writeback test succeeded in 1 usecs |
111 |
|
112 |
|
113 |
dmesg | grep agp |
114 |
Linux agpgart interface v0.101 (c) Dave Jones |
115 |
agpgart: Detected SiS 646 chipset |
116 |
agpgart: AGP aperture is 64M @ 0xe8000000 |
117 |
agpgart: Found an AGP 2.0 compliant device at 0000:00:00.0. |
118 |
agpgart: Putting AGP V2 device at 0000:00:00.0 into 1x mode |
119 |
agpgart: Putting AGP V2 device at 0000:01:00.0 into 1x mode |
120 |
|
121 |
|
122 |
I'm not sure what all of this means, but, bzflag |
123 |
crashed once before using this 2.6.18-gentoo-r2 |
124 |
kernel...... |
125 |
|
126 |
hth, |
127 |
|
128 |
|
129 |
James |
130 |
|
131 |
|
132 |
|
133 |
|
134 |
|
135 |
-- |
136 |
gentoo-user@g.o mailing list |