Re: Rivafb won't work with DVI connector

["Antonino A. Daplas" <adaplas@hotpop.com>]

On Wednesday 24 November 2004 02:01, Andrew Walrond wrote:
> On Tuesday 23 Nov 2004 17:07, Antonino A. Daplas wrote:
> > Okay, I think I this should fix the dvi misdetection, and I think it
> > should also fix the preferred timing of 1600x1200 even if both dsub and
> > dvi are attached.  Try the attached patch.
>
> Not quite, but close...
>
> With just dsub and no params, we get a perfect 1600x1200 (200x75) console

Great.

>
> With both dsub and dvi, another perfect 1600x1200 console. (first EDID

Great :-)

> truncated due to dmesg log not big enough; I can fix this if you need)

No need.  The first EDID block is for dvi, the second is for dsub.

>
> With dvi connection and no params, I get a fully working console, but at
> 1024x768 (128x48)

Okay, this is what I wanted to fix.  Note that the preferred timing when
dvi is attached is 1024x768. When dsub, it's 1600x1200.  You see this
in your dmesg "First DETAILED Timing is preferred", and without options
the first detailed timing block will be used.

>
> With DVI and video=nvidiafb:1600x1200-32@60 I get a kernel hang like this
> (copied by hand and shortened in places)

Okay, this is expected.  Since the panel size is only 1024x768, using a mode
of 1600x1200 failed.  So the framebuffer exited initialization with an error which
caused an oops.

Note, that you may not be able to force resolutions > panel size.  You can
try, all you need to do is remove this code in
drivers/video/nvidia/nvidia.c:nvidiafb_check_var:

	if (par->fpWidth && par->fpHeight && (par->fpWidth < var->xres ||
					      par->fpHeight < var->yres))
		return -EINVAL;

But I don't know if your display can tolerate that.

For now, I'll add checks during the initializatiion that will refuse modes
greater than the panel size.

Unfortunately, without any docs on how to adjust the default panel size,
you will be limited to this resolution only.

Does vesafb work in x86_64?  If it does you can add this in your
commandline:

vga=0x307 

0x306 is the code for 1280x1024, see Documentation/fb/vesafb.txt.

Then check your dmesg if the panel size also changed.  If it did, then
you can do this:

vga=0x307 video=nvidiafb:1280x1024@60.

>
> Decompressing linux
> Bootdata ok (command line is root=... video=nvidiafb:1600x1200-32@60)
> Linux version 2.6.10-rc2 ...
> BIOS-provided physical map
> Scanning NUMA topology in Northbridge 24
> Number of nodes 2 (10010)
> Node 0 using interleaving mode 1/0
> No NUMA configuration found
>
>
> and thats as far as it gets.
>
> Getting closer by the hour :)

Yes.

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/