1 |
On Mon, Oct 25, 2010 at 11:55 PM, Dale <rdalek1967@×××××.com> wrote: |
2 |
> Dale wrote: |
3 |
>> |
4 |
>> Well, at least we know there is a problem and it isn't just us. If you |
5 |
>> find something, let us know. I would hate to know I had to try to watch a |
6 |
>> DVD right now. I doubt it would even start up. o_O |
7 |
>> |
8 |
>> BTW, hal is disabled on xorg here. It's enabled on other things but not |
9 |
>> xorg. |
10 |
>> |
11 |
>> Dale |
12 |
>> |
13 |
>> :-) :-) |
14 |
>> |
15 |
> |
16 |
> I have a update. Check this out: |
17 |
> |
18 |
> root@smoker / # glxgears |
19 |
> Running synchronized to the vertical refresh. The framerate should be |
20 |
> approximately the same as the monitor refresh rate. |
21 |
> 1380 frames in 5.0 seconds = 275.147 FPS |
22 |
> 242 frames in 5.0 seconds = 48.345 FPS |
23 |
> 241 frames in 5.0 seconds = 48.191 FPS |
24 |
> 246 frames in 5.0 seconds = 49.056 FPS |
25 |
> 240 frames in 5.0 seconds = 47.902 FPS |
26 |
> 238 frames in 5.0 seconds = 47.453 FPS |
27 |
> 238 frames in 5.0 seconds = 47.566 FPS |
28 |
> 240 frames in 5.0 seconds = 47.839 FPS |
29 |
> 244 frames in 5.0 seconds = 48.577 FPS |
30 |
> 242 frames in 5.0 seconds = 48.257 FPS |
31 |
> 241 frames in 5.0 seconds = 48.196 FPS |
32 |
> 242 frames in 5.0 seconds = 48.380 FPS |
33 |
> 238 frames in 5.0 seconds = 47.573 FPS |
34 |
> 238 frames in 5.0 seconds = 47.596 FPS |
35 |
> 241 frames in 5.0 seconds = 48.168 FPS |
36 |
> XIO: fatal IO error 22 (Invalid argument) on X server ":0.0" |
37 |
> after 900 requests (900 known processed) with 0 events remaining. |
38 |
> root@smoker / # |
39 |
> |
40 |
> |
41 |
> What did I do you ask? Well, I did this: |
42 |
> |
43 |
> root@smoker / # eselect opengl list |
44 |
> Available OpenGL implementations: |
45 |
> [1] nvidia * |
46 |
> [2] xorg-x11 |
47 |
> root@smoker / # eselect opengl set 1 |
48 |
> Switching to nvidia OpenGL interface... done |
49 |
> root@smoker / # |
50 |
> |
51 |
> Yea, it SAID it was already set but I told it to set it again anyway. Now I |
52 |
> get some good frame rates again. Excuse me while I go watch some videos I |
53 |
> been wanting to watch but got tired of the spit and sputter. lol |
54 |
> |
55 |
> YEPPIE ! ! ! It breathes again. |
56 |
> |
57 |
> Dale |
58 |
> |
59 |
> :-) :-) |
60 |
> |
61 |
> P. S. Bonus points if someone can explain why that worked. o_O |
62 |
|
63 |
It's been a while since I last had X + accelerated 3D on any of my |
64 |
systems here (my gaming box's running W7), but it would be my guess |
65 |
that, while Nvidia's libraries *were* configured as the GL |
66 |
implementation to be used, in the process of the last driver upgrade |
67 |
they got overwritten with upgraded versions, running things that |
68 |
should have referenced them failed and defaulted to mesa's libraries, |
69 |
and you got stuck with CPU based 3D rendering. Upon using eselect to |
70 |
set it to Nvidia's again, however, you refreshed the links to the |
71 |
proper, updated, libraries and things started using the GPU again. |
72 |
|
73 |
This is, of course, entirely a guess, and is at least moderately |
74 |
broken by this from glxinfo: |
75 |
|
76 |
server glx vendor string: NVIDIA Corporation |
77 |
|
78 |
Still... it's the best guess I have at 1:17 AM here, my time. |
79 |
|
80 |
-- |
81 |
Poison [BLX] |
82 |
Joshua M. Murphy |