On Tuesday 14 December 2004 15:51, Junio C Hamano wrote:

quoted

quoted

quoted

quoted

quoted

"AAD" == Antonino A Daplas [off-list ref] writes:

AAD> Can you try this patch and enable nvidiafb-i2c. It adds your monitor
model AAD> to the database of displays with broken edid's and attempts a
fix. It AAD> checks first if the monitor is GTF capable, and if it is, sets
the input AAD> type from digital to analog. (I don't think digital inputs
can be GTF AAD> capable).

AAD> Apply this patch too, I forgot to adjust the checksum.

Thanks as always for a quick help.

With those two patches, your fixup message appears in the boot
log 6 times (is it expected?).  The monitor does not go blank

Yes, it should be printed only once. 

anymore; it safely defaults to CRTCNumber 0.  Overall, it is as
if I am using your nvidiafb driver without nvidia-i2c ;-).

No, of course not.  There are certain advantages:

1. Without boot options, your display will automatically go to
   1024x768@85 Hz, since this is the preferred timing.

2. The driver will refuse modes that exceeds the monitor's operating.

3.  Because your display is GTF capable, all you need to do is:

fbset -xres 1600 -yres 1200 /* xres and yres can be any value */

and as long as #2 is satisfied, the modeline for 1600x1200 at the highest
refresh rate will be computed, no need to enter a modline in /etc/fb.modes.

Tony




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. 
http://productguide.itmanagersjournal.com/