About the monitor - it's a sony oem'd for sun and some of sun cards run faster than 210MHz so I didn't worry about that too much. The cable is a reasonably good coax cable. I know I said ghosting but maybe I was using the wrong words. I know what a bad cable looks like and that's what I usually call ghosting. This looks quite different. Here's a better description of what specifying Modes "2048x1536" produces: Very simple startup screen using twm so it puts the window name "login" in upper left corner and because auto placement is turned off, I have an outline of the xterm in the middle of the screen waiting for me to hit the button and place the window. What I see is in the upper left a good login label, then 3 more striped login labels evenly across the top of the screen. Each striped label looks like 1-4 (can't really tell) good lines, then 1-4 blank lines, repeating so the login label looks greyed-out and the 2nd one is actually flickering a little bit. The xterm outline is more interesting. With the cursor in the leftmost quarter of the screen (draw 3 vertical lines to divide the screen), I get one outline in the correct spot, following the cursor but the upper right corner of the outline is flickering. I also get another outline in the 2nd quarter of the screen, aligned vertically with the correct one but with the left side flickering, then in the 3rd and 4th quarters I get partial outlines that don't flicker. Moving the cursor to the 2nd quarter produced a partial outline in the 2nd quarter that flickers a lot and a solid outline offset from the cursor in the 3rd quarter. Moving the cursor to the 3rd quarter puts one solid outline in the 4th quarter offset from the cursor and nothing else. Moving the cursor to the 4th quarter produces 4 partial outlines with the one in the 1st quarter flickering. Is there any chance the nv driver is trying to do something like run the DAC faster than 300M in 24 bit mode? The reason I ask is that I just tried specifying 2048x1536 depth 8 and it looks ok and according to the documentation the DAC should be able to run to 350M in 8 bit mode.
I tried downgrading the nvidia driver with no luck but I may have had some finger problems - I'll give it a try and be more careful this time to make sure I really have the older driver.
Thanks, Malcolm
On Saturday, March 22, 2003, at 10:02 PM, Mark Vojkovich wrote:
I've just tried these modes on my GeForce2 MX:
2048x1536 @ 60 Hz (266.9 MHz) 1920x1440 @ 60 Hz (234.0 MHz)
and both worked fine with the "nv" driver for me. You're saying they work fine for you in the "nvidia" driver but not "nv"? Are they the same refresh rate in both cases? Note that your monitor claims it doesn't have enough bandwidth for either of these modes (max 210 pixel clock).
(II) NV(0): Ranges: V min: 48 V max: 160 Hz, H min: 30 H max: 121 kHz, PixClock max 210 MHz
I could see the case where the "nvidia" driver would lower the
refresh rate automatically because of that but the "nv" driver wouldn't.
The ghosting you are describing is typical of the monitor or
monitor cable not being able to support such high frequencies, leading
to artifacts. My monitor claims to have 250 MHz bandwidth. It
looks OK in both these modes.
Mark.
On Sat, 22 Mar 2003, Malcolm Stevens wrote:
Regarding: nv driver misbehaves on geforce 2 MX @ greater than 1600x1200
Email: [EMAIL PROTECTED]
_______________________________________________ XFree86 mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xfree86
