None of tested nvidia drivers work (pixel clock detection issue?)

[XnR'rn]

I am using an one of the older DFP monitors (namely Viewsonic VPA150, optimal 1024x768NI resolution) and Geforce2 MX 400 on Athlon 1500XP. And trying to get the drivers to work in xorg. For the reference, the hsync and vertrefresh as set in xorg.conf are correct (that is, same as in the manitor's manual).

I've tried most possible combinations of kernel compile options, options in xorg.conf and whatnot (generaly there were some EE or WW things in the logs, but I gradualy got rid of them). The only persistant thing in the logs is the fubar in pixelclock department. Apparently the drivers don't detect it correctly, so none of the resolutions are used. The results ranged from blank screen and X server hanging (responding only to the ctrl+alt+del, not ctrl+alt+backspace) to so much ascii noise shown on the screen with same results, to screen flashing once and staying blank from there.
Drivers: 5335-r4, 6111 and an some earlier drivers from 6 series (6105?)
Distro: Gentoo (kernels 2.4.26-gentoo-r9, 2.6.5-gentoo-r1, 2.6.7-gentoo-r14, 2.6.8-gentoo-r1). I haven't tried that on Slackware 10 (kernel 2.4.26), but from what I seen I bet that it is going to be the same.
Video BIOS: No idea (no /proc/driver/nvidia/ in slackware, and the X makes it impossible to look in gentoo)

If any other information is required, I'll post, thats all I can think of at the moment.

[XnR'rn]

Shameless bump.

[XnR'rn]

No luck with it? Damn, I don't wish changing graphics card or monitor. I tried it with an old Riva TNT2, and it gives the same errors. Should I bugrep it?

[_jones]

Got any news? Did you fix it? It is quite similar to my problem: http://www.nvnews.net/vbulletin/showthread.php?t=36147

[augury]

try with: (depending on the connector you use)
Option "ConnectedMonitor" "CRT-0"
or
Option "ConnectedMonitor" "DFP-0"
and

Option "UseEdidFreqs" "1"

and (depending on monitor)
Option "FlatPanel" "True"

[augury]

also if you comment out HorizSync it'll start up in 800x600. looks like ****, but its a start. it if does start up it prob. means your timings are off. if you call view sonic they will tell you what timings the monitor takes. (cant find the # sorry) you may have to explain that you need both sets of numbers, not all CSR's realize this.

[XnR'rn]

Nope, none of the options worked.
Commenting hsync does nothing, and X just hangs there just like that.
Apparently drivers ignore Edid or can't detect it, even if explictly told to use it.
I switched to an old 3dfx voodoo 4500, but no success with having a hardware acceleration there yet, but I do get higher fps at glxgears with it...
Apparently I'll have to invest in a new monitor sometime.