|
|
#13 | |
|
Registered User
Join Date: Oct 2003
Posts: 4
|
Well I shall try the latest CVS, but I do not have a digital flat panel. I am currently using a HP ergo 1600 at a res of 1600x1200
|
|
|
|
|
|
|
#14 | |
|
Registered User
Join Date: Jun 2004
Posts: 2
|
Is there any fix for this? I have the same problem with
$ cat /proc/driver/nvidia/version NVRM version: NVIDIA Linux x86 NVIDIA Kernel Module 1.0-5336 Wed Jan 14 18:29:26 PST 2004 GCC version: gcc version 3.3.2 20031022 (Red Hat Linux 3.3.2-1) on my $ cat /proc/driver/nvidia/cards/0 Model: GeForce FX 5600XT IRQ: 16 Video BIOS: 04.31.20.69.00 Card Type: AGP Especially with xawdecode in grabdisplay mode. |
|
|
|
|
|
|
#15 |
|
Registered User
Join Date: Jul 2004
Posts: 1
|
Yeah I have the same problem. I'm using v6106 for AMD 64.
I have a Samsung LCD at 1280x1024 connected via DVI I find that if I switch to 60Hz it fixes the problem. And I don't have the problem with RTCW: Enemy Territory or anything else, just when I use Xine with the hardware accelerated output plugin. (The software output plugin doesn't have any problems). It must be an interaction between the video module and the drivers, and it has something to do with the interlacing. I'm sure it could probably be fixed quite easily, but I don't know how. |
|
|
|
|
|
#16 | |
|
Registered User
|
a combinations of frequencies and interlacing, especially for TVout is it a problem...
but then even in fb there are frequency problems.... I feel that nvidia should allow more frequencies and frequency changes they are deciding what frequency to be used, so they should do i right. the whole frequency/resolution/interlacing/... should be rewritten in the nvidia driver, the more they change things, the worse it gets... (I remember the one before 4363 as having absolutely no problems whatsoever...!) (except that some cards were not supported and 2.6.x was not an option...)
__________________
Alien is my name and headbiting is my game. |
|
|
|
|
|
|
#17 |
|
Registered User
Join Date: May 2003
Posts: 8
|
Hi all, found a workaround/fix (thanks to joback), at least that works for me, and it sort of does make some sense. I simple edited my XF86Config-4 file and modified the "VertRefresh" option. According to the manual for my ViewSonic, the display can handle signals in the range 50Hz-75Hz, so that's what I had for my VertRefresh. I changed this just to
VertRefresh 60 since that is really the only frequency at which the flat display actually displays things in, and I have no more corruption. I'm guessing what this does is pick a different set of modelines for when choosing lower resolutions; whereas previously it chose a resolution that was at some non-60Hz frequency, now it chooses an alternative that is 60Hz, and everything is golden. |
|
|
|
![]() |
| Thread Tools | |
|
|