Re: [PATCH] GeForce 5200 on rivafb

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

Thanks for a quick response.

>>>>> "AAD" == Antonino A Daplas <adaplas@hotpop.com> writes:

AAD> Dec 10 19:04:40 siamese kernel:       Display is GTF capable
AAD> Dec 10 19:04:40 siamese kernel: nvidiafb: Unable to detect which 
AAD> CRTCNumber...
AAD> Dec 10 19:04:40 siamese kernel: ...Defaulting to CRTCNumber 1
AAD> Dec 10 19:04:40 siamese kernel: nvidiafb: Using DFP on CRTC 1
AAD> Dec 10 19:04:40 siamese kernel: Panel size is 1 x 1

AAD> Panel size of 1x1 is a bad sign.  (Panel size is set by video BIOS).

What should it say normally?  The monitor is a CRT (ViewSonic
PF775a) connected via a DSub connector.  I have rebuilt the
kernel without I2C support and the boot log says "Defaulting to
CRTCNumber 0".  With this, I get a working framebuffer console
and fbdev X works on it.

Dec 10 23:10:22 siamese kernel: nvidiafb: nVidia device/chipset 10DE0110
Dec 10 23:10:22 siamese kernel: nvidiafb: nVidia Corporation NV11 [GeForce2 MX/MX 400]
Dec 10 23:10:22 siamese kernel: nvidiafb: Unable to detect display type...
Dec 10 23:10:22 siamese kernel: ...Using default of CRT
Dec 10 23:10:22 siamese kernel: nvidiafb: Unable to detect which CRTCNumber...
Dec 10 23:10:22 siamese kernel: ...Defaulting to CRTCNumber 0
Dec 10 23:10:22 siamese kernel: nvidiafb: Using CRT on CRTC 0
Dec 10 23:10:22 siamese kernel: nvidiafb: MTRR set to ON
Dec 10 23:10:22 siamese kernel: Console: switching to colour frame buffer device 200x75
Dec 10 23:10:22 siamese kernel: nvidiafb: PCI nVidia NV11 framebuffer (64MB @ 0xD8000000)

AAD> Can you try the following:
AAD> 1. Change this line in drivers/video/fbmon.c

AAD> #undef DEBUG
AAD> to 
AAD> #define DEBUG

Will do, but I have one question.  The last time I tried
turning debugging on on rivafb-i2c it was very unpleasant;
eventually the driver ended up reporting scrolling events on the
console which caused further scrolling which is reported on the
console which caused further scrolling ... ;-).  I could not get
the control back even with SysRQ.  Is there a trick to avoid
this kind of trouble and still have debugging enabled?

AAD> 2. Experiment with the following boot options:

AAD> So you can try this, for a start:
AAD> video=nvidiafb:forceCRTC:1

I presume I should use forceCRTC:0 to match the working "sans
i2c" case.

Is it possible that EDID is not being read correctly in my
configuration?  Could it be a hardware problem (either the card,
the monitor, or the connecting cable)?  If so, how would I
determine if it indeed is a hardware problem?

Thanks.



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