Re: [PATCH] GeForce 5200 on rivafb

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

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

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;

AAD> No :-), this is not for nvidiafb but for the EDID parser, and it will give
AAD> you a very descriptive parsing of the EDID block.

Will try.  Thanks.

AAD> So, with a broken EDID block, I guess your best workaround is to disable
AAD> i2c in your kernel config.

Again, thanks.

AAD> BTW:  Why can't you use the 'nv' driver with X? And does rivafb work with
AAD> your card?

The rivafb driver up to 2.6.7 or so used to give me framebuffer
console, and let me run X on fbdev, but more recent ones does
not seem to work.  I just get blank screen (even without EDID
detection via riva-i2c).  Around the timeframe when 2.6.3 or so
was current, XFree86 'nv' used to work without any kernel side
framebuffer device, but the more recent one from Debian
'testing' does not work anymore; I am suspecting this is a
problem with XFree86 not rivafb or nvidiafb framebuffer problem
so it may not be of interest to this list.



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