1 |
Dale <rdalek1967@×××××.com> [10-12-18 09:52]: |
2 |
> meino.cramer@×××.de wrote: |
3 |
> >Hi, |
4 |
> > |
5 |
> >For my MSI GT430 (nvidia) graphics card I am using |
6 |
> >the x11-drivers/nvidia-drivers-260.19.29. |
7 |
> > |
8 |
> >But there seems to be something wrong: |
9 |
> >When playing videos with faster movements |
10 |
> >I see heavy distortions around these parts |
11 |
> >of the screen. |
12 |
> > |
13 |
> >Previously I fixed this for another nvidia |
14 |
> >card by enabling different sync options |
15 |
> >in the nvidia-setting dialog and was happy |
16 |
> >that these distortion dont come back, when |
17 |
> >I switched to this newer card. |
18 |
> > |
19 |
> >Now: There're back despite my hopes... |
20 |
> > |
21 |
> >I started glxgears and got this output |
22 |
> >on the console: |
23 |
> > |
24 |
> > Running synchronized to the vertical refresh. The framerate |
25 |
> >should be |
26 |
> > approximately the same as the monitor refresh rate. |
27 |
> > 74062 frames in 5.0 seconds = 14812.268 FPS |
28 |
> > 77502 frames in 5.0 seconds = 15500.350 FPS |
29 |
> > XIO: fatal IO error 11 (Resource temporarily unavailable) on X |
30 |
> >server ":0.0" |
31 |
> > after 57 requests (57 known processed) with 0 events |
32 |
> >remaining. |
33 |
> > |
34 |
> > |
35 |
> >The second sentence say, that there is a syncing active and will get |
36 |
> >the refresh rate of the monitor (a LCD screen) back. This wouild be |
37 |
> >around 60Hz as far as I know. |
38 |
> > |
39 |
> >And then, the measurements show 15500.350 FPS... |
40 |
> > |
41 |
> >Which slightl above 60 Hz.... |
42 |
> > |
43 |
> >To sync or not to sync, that seems to be the question... |
44 |
> > |
45 |
> >By the way: Distortion can be watched as when using mplayer |
46 |
> >as with vlc. I recompiled both just to get sure, but it does |
47 |
> >not help. The machine is definetly fast enough to play videos |
48 |
> >(AMD Phenom II X6 1090T).... |
49 |
> > |
50 |
> >How can I get back the undistorted screen? |
51 |
> > |
52 |
> >Thank you very much in advance for any help ! |
53 |
> >Best regards, |
54 |
> >mcc |
55 |
> > |
56 |
> > |
57 |
> |
58 |
> I would check the log files and see if they shed some light on this. I |
59 |
> would check dmesg, messages and Xorg.0.log as well. The last one may |
60 |
> show the best clues. If nothing there points to anything good, I would |
61 |
> post the xorg.conf and Xorg.0.log as attachments. |
62 |
> |
63 |
> I have a CPU like yours except 4 core and a little GT-220 card, wimpy |
64 |
> compared to yours. What you see about the refresh rates is displayed |
65 |
> on my machine too. The last part appears because you hit the close |
66 |
> window X instead of doing a ctrl c to stop glxgears. If you start |
67 |
> glxgears and do a ctrl c to stop it, the last part won't be there. I |
68 |
> mention this because that *may* have nothing to do with the problem you |
69 |
> are having. This is what happens when I run glxgears: |
70 |
> |
71 |
> fireball ~ # glxgears |
72 |
> Running synchronized to the vertical refresh. The framerate should be |
73 |
> approximately the same as the monitor refresh rate. |
74 |
> 27770 frames in 5.0 seconds = 5553.918 FPS |
75 |
> 9783 frames in 5.0 seconds = 1955.847 FPS |
76 |
> 3084 frames in 5.0 seconds = 616.716 FPS |
77 |
> 3085 frames in 5.0 seconds = 616.942 FPS |
78 |
> 3105 frames in 5.0 seconds = 620.981 FPS |
79 |
> XIO: fatal IO error 11 (Resource temporarily unavailable) on X server |
80 |
> ":0.0" |
81 |
> after 42 requests (42 known processed) with 0 events remaining. |
82 |
> fireball ~ # glxgears |
83 |
> Running synchronized to the vertical refresh. The framerate should be |
84 |
> approximately the same as the monitor refresh rate. |
85 |
> 14932 frames in 5.0 seconds = 2985.639 FPS |
86 |
> 3011 frames in 5.0 seconds = 602.125 FPS |
87 |
> ^C |
88 |
> fireball ~ # |
89 |
> |
90 |
> The last one was stopped with a ctrl c as you can see. The first was |
91 |
> closed by hitting the close window button. |
92 |
> |
93 |
> If this doesn't help, at least you know to post the files so we can |
94 |
> look them over. Maybe someone will notice something out of place. |
95 |
> |
96 |
> Dale |
97 |
> |
98 |
> :-) :-) |
99 |
> |
100 |
|
101 |
Hi Dale, |
102 |
|
103 |
thank you for your in deep explanations ! :) |
104 |
|
105 |
The distortions I saw on my screen look identical to |
106 |
those I recognizeed with my old nvidia card before using |
107 |
the sync settings...so i /thought/ (read: "dont know for sure" ;) ) |
108 |
it would by a syncing problem again. |
109 |
|
110 |
But it wan't. |
111 |
|
112 |
For reasons I dont know in the nvidia-settings there was "GPU scaling" |
113 |
activate. May be someone sitting in front of my computer the same time |
114 |
I use to has fiddled with this setting without informing me... ;) |
115 |
|
116 |
The trick is: When watching a video in its native resolution, the |
117 |
problem does not occur. |
118 |
|
119 |
When watching the video full screen, the GPU was instructed to scale |
120 |
it up (instead of mplayer or vlc doing this job in software). |
121 |
Problem with this is (I thinkt), that there is one-pixel-border around |
122 |
the full-screen window of mplayer/vlc so the GPU is instructed to |
123 |
scale it to 1918x1199 pixel. Then this is thrown into my LCD monitor |
124 |
and .... rubish... |
125 |
|
126 |
First I deatcivated "GPU scaling" and then spoke some serious words |
127 |
to this guy, who uses my computer always the same I do and ... I am |
128 |
happy again to have a clean video playing. |
129 |
|
130 |
Thanks a lot for your explanations! (will store them for later use... |
131 |
who knows what things I will encounter next....;) |
132 |
|
133 |
Have a nice weekend! |
134 |
Best regards |
135 |
mcc |