Re: [PATCH] GeForce 5200 on rivafb

[Junio C Hamano <junkio@cox.net>]

>>>>> "AAD" == Antonino A Daplas <adaplas@hotpop.com> 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
anymore; it safely defaults to CRTCNumber 0.  Overall, it is as
if I am using your nvidiafb driver without nvidia-i2c ;-).

Boot time kernel message is attached here.

----------------------------------------------------------------

nvidiafb: nVidia device/chipset 10DE0110
nvidiafb: nVidia Corporation NV11 [GeForce2 MX/MX 400]
fbmon: The EDID Block of Manufacturer: VSC Model: 0x5a44 is known to be broken,
fbmon: trying to fix input type
fbmon: The EDID Block of Manufacturer: VSC Model: 0x5a44 is known to be broken,
fbmon: trying to fix input type
nvidiafb: EDID found from BUS1
fbmon: The EDID Block of Manufacturer: VSC Model: 0x5a44 is known to be broken,
fbmon: trying to fix input type
fbmon: The EDID Block of Manufacturer: VSC Model: 0x5a44 is known to be broken,
fbmon: trying to fix input type
========================================
Display Information (EDID)
========================================
   EDID Version 1.2
   Manufacturer: VSC
   Model: 5a44
   Serial#: 2694881440
   Year: 2150 Week 14
   Serial Number: DZ01401434
   Monitor Name: PF775
   Display Characteristics:
      Monitor Operating Limits: From EDID
           H: 30-97KHz V: 50-180Hz DCLK: 200MHz
      Analog Display Input: Input Voltage - 0.714V/0.286V
      Sync: 
      Max H-size in cm: 160
      Max V-size in cm: 160
      Gamma: 2.60
      DPMS: Active yes, Suspend yes, Standby yes
      RGB Color Display
      Chroma
         RedX:     0.627 RedY:     0.342
         GreenX:   0.289 GreenY:   0.605
         BlueX:    0.150 BlueY:    0.070
         WhiteX:   0.283 WhiteY:   0.298
      First DETAILED Timing is preferred
      Display is GTF capable
fbmon: The EDID Block of Manufacturer: VSC Model: 0x5a44 is known to be broken,
fbmon: trying to fix input type
fbmon: The EDID Block of Manufacturer: VSC Model: 0x5a44 is known to be broken,
fbmon: trying to fix input type
   Supported VESA Modes
      720x400@70Hz
      640x480@60Hz
      800x600@72Hz
      800x600@75Hz
      832x624@75Hz
      1024x768@87Hz Interlaced
      1024x768@60Hz
      1024x768@70Hz
      1024x768@75Hz
      1280x1024@75Hz
      1152x870@75Hz
      Manufacturer's mask: 0
   Standard Timings
      640x480@85Hz
      800x600@85Hz
      1528x1146@75Hz
      1280x960@60Hz
      1280x960@85Hz
      1280x1024@85Hz
      1528x1222@60Hz
      1600x1200@75Hz
   Detailed Timings
      94 MHz 1024 1072 1168 1376 768 769 772 808 +HSync +VSync

========================================
nvidiafb: Unable to detect which CRTCNumber...
...Defaulting to CRTCNumber 0
nvidiafb: Using CRT on CRTC 0
nvidiafb: MTRR set to ON
Console: switching to colour frame buffer device 128x48
nvidiafb: PCI nVidia NV11 framebuffer (64MB @ 0xD8000000)
Real Time Clock Driver v1.12
Linux agpgart interface v0.100 (c) Dave Jones
agpgart: Detected VIA Twister-K/KT133x/KM133 chipset
agpgart: Maximum main memory to use for agp memory: 690M
agpgart: AGP aperture is 128M @ 0xd0000000





-------------------------------------------------------
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/