1 |
meino.cramer@×××.de wrote: |
2 |
> Hi, |
3 |
> |
4 |
> For my MSI GT430 (nvidia) graphics card I am using |
5 |
> the x11-drivers/nvidia-drivers-260.19.29. |
6 |
> |
7 |
> But there seems to be something wrong: |
8 |
> When playing videos with faster movements |
9 |
> I see heavy distortions around these parts |
10 |
> of the screen. |
11 |
> |
12 |
> Previously I fixed this for another nvidia |
13 |
> card by enabling different sync options |
14 |
> in the nvidia-setting dialog and was happy |
15 |
> that these distortion dont come back, when |
16 |
> I switched to this newer card. |
17 |
> |
18 |
> Now: There're back despite my hopes... |
19 |
> |
20 |
> I started glxgears and got this output |
21 |
> on the console: |
22 |
> |
23 |
> Running synchronized to the vertical refresh. The framerate should be |
24 |
> approximately the same as the monitor refresh rate. |
25 |
> 74062 frames in 5.0 seconds = 14812.268 FPS |
26 |
> 77502 frames in 5.0 seconds = 15500.350 FPS |
27 |
> XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0.0" |
28 |
> after 57 requests (57 known processed) with 0 events remaining. |
29 |
> |
30 |
> |
31 |
> The second sentence say, that there is a syncing active and will get |
32 |
> the refresh rate of the monitor (a LCD screen) back. This wouild be |
33 |
> around 60Hz as far as I know. |
34 |
> |
35 |
> And then, the measurements show 15500.350 FPS... |
36 |
> |
37 |
> Which slightl above 60 Hz.... |
38 |
> |
39 |
> To sync or not to sync, that seems to be the question... |
40 |
> |
41 |
> By the way: Distortion can be watched as when using mplayer |
42 |
> as with vlc. I recompiled both just to get sure, but it does |
43 |
> not help. The machine is definetly fast enough to play videos |
44 |
> (AMD Phenom II X6 1090T).... |
45 |
> |
46 |
> How can I get back the undistorted screen? |
47 |
> |
48 |
> Thank you very much in advance for any help ! |
49 |
> Best regards, |
50 |
> mcc |
51 |
> |
52 |
> |
53 |
|
54 |
I would check the log files and see if they shed some light on this. I |
55 |
would check dmesg, messages and Xorg.0.log as well. The last one may |
56 |
show the best clues. If nothing there points to anything good, I would |
57 |
post the xorg.conf and Xorg.0.log as attachments. |
58 |
|
59 |
I have a CPU like yours except 4 core and a little GT-220 card, wimpy |
60 |
compared to yours. What you see about the refresh rates is displayed on |
61 |
my machine too. The last part appears because you hit the close window |
62 |
X instead of doing a ctrl c to stop glxgears. If you start glxgears and |
63 |
do a ctrl c to stop it, the last part won't be there. I mention this |
64 |
because that *may* have nothing to do with the problem you are having. |
65 |
This is what happens when I run glxgears: |
66 |
|
67 |
fireball ~ # glxgears |
68 |
Running synchronized to the vertical refresh. The framerate should be |
69 |
approximately the same as the monitor refresh rate. |
70 |
27770 frames in 5.0 seconds = 5553.918 FPS |
71 |
9783 frames in 5.0 seconds = 1955.847 FPS |
72 |
3084 frames in 5.0 seconds = 616.716 FPS |
73 |
3085 frames in 5.0 seconds = 616.942 FPS |
74 |
3105 frames in 5.0 seconds = 620.981 FPS |
75 |
XIO: fatal IO error 11 (Resource temporarily unavailable) on X server |
76 |
":0.0" |
77 |
after 42 requests (42 known processed) with 0 events remaining. |
78 |
fireball ~ # glxgears |
79 |
Running synchronized to the vertical refresh. The framerate should be |
80 |
approximately the same as the monitor refresh rate. |
81 |
14932 frames in 5.0 seconds = 2985.639 FPS |
82 |
3011 frames in 5.0 seconds = 602.125 FPS |
83 |
^C |
84 |
fireball ~ # |
85 |
|
86 |
The last one was stopped with a ctrl c as you can see. The first was |
87 |
closed by hitting the close window button. |
88 |
|
89 |
If this doesn't help, at least you know to post the files so we can look |
90 |
them over. Maybe someone will notice something out of place. |
91 |
|
92 |
Dale |
93 |
|
94 |
:-) :-) |