From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: Andrew Walrond <andrew@walrond.org>,
linux-fbdev-devel@lists.sourceforge.net
Subject: Re: Rivafb won't work with DVI connector
Date: Thu, 25 Nov 2004 08:07:29 +0800 [thread overview]
Message-ID: <200411250807.32040.adaplas@hotpop.com> (raw)
--- Andrew Walrond <andrew@walrond.org> wrote:
> On Tuesday 23 Nov 2004 18:26, Antonino A. Daplas
> wrote:
> >
> > 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.
> >
>
> If I did this right, it doesn't help. I built in the
> vesafb as well as your
> new nvidafb, then booted with the commandline
>
> vga=0x31b video=nvidiafb:1280x1024-32@60
That's assuming 0x31b is supported by your card. Why not
try:
vga=ask
Choose 'scan', choose the highest size, and check if the panel
size changed again.
>
> It looks like the nvidafb got the first bite of the
> cherry:
No, vesafb will always get the first bite, it's initialized when the OS is in
real mode.
>
> ...
> nvidiafb: CRTC 1 is currently programmed for DFP
> nvidiafb: Using DFP on CRTC 1
> Panel size is 1024 x 768
> nvidiafb: MTRR set to ON
> Console: switching to colour frame buffer device
> 128x48
> nvidiafb: PCI nVidia NV25 framebuffer (128MB @
> 0xE0000000)
> vesafb: probe of vesafb0 failed with error -6
> ...
>
>
> Do you know if the nvidia developers lurk on lkml? I
I did not subscribe to lkml. But I do occassionally look at the archives.
> seem to remember somebody
> saying that they do. If so, is it worth asking them
> for a bit of help with
> this? I know they're not about to open source their
> binary driver due to ip
> license problems, but the information we require to
> overcome this problem in
> the fb driver is probably quite trivial in nature. I
Well, checking the latest Xorg again, it seems that the nv driver also
depends on the BIOS for the panel size. And they are the people who does
have access to the docs.
> assume they have been
> forthcoming in the past wrt the open source X
> driver.
>
> What do you think? Worth asking?
Sure, no harm in asking. But I would rather ask the Xorg people first. If
we can't get the vga=ask to work, then I really don't know what to do,
besides perhaps experimenting with VBE calls. I can do that, but I do not
have any flatpanel to test on.
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/
next reply other threads:[~2004-11-25 0:07 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-25 0:07 Antonino A. Daplas [this message]
2004-11-25 15:27 ` Rivafb won't work with DVI connector Andrew Walrond
2004-11-25 21:16 ` Antonino A. Daplas
2004-11-26 14:09 ` Antonino A. Daplas
2004-11-27 12:40 ` Andrew Walrond
2004-11-27 18:29 ` Michel Dänzer
2004-11-27 22:35 ` Andrew Walrond
2004-11-27 22:43 ` Antonino A. Daplas
-- strict thread matches above, loose matches on Subject: below --
2004-11-19 11:37 Andrew Walrond
2004-11-19 22:08 ` Antonino A. Daplas
2004-11-20 15:52 ` Andrew Walrond
2004-11-22 0:11 ` Antonino A. Daplas
2004-11-22 9:23 ` Andrew Walrond
2004-11-22 9:43 ` Andrew Walrond
2004-11-22 22:13 ` Antonino A. Daplas
2004-11-22 23:47 ` Andrew Walrond
2004-11-22 23:54 ` Andrew Walrond
2004-11-23 1:50 ` Antonino A. Daplas
2004-11-23 12:32 ` Andrew Walrond
2004-11-23 14:28 ` Antonino A. Daplas
2004-11-23 15:09 ` Andrew Walrond
2004-11-23 15:18 ` Antonino A. Daplas
2004-11-23 16:08 ` Andrew Walrond
2004-11-23 17:07 ` Antonino A. Daplas
2004-11-23 18:01 ` Andrew Walrond
2004-11-23 18:26 ` Antonino A. Daplas
2004-11-23 19:00 ` Andrew Walrond
2004-11-23 19:07 ` Andrew Walrond
2004-11-23 19:23 ` Andrew Walrond
2004-11-23 19:59 ` Geert Uytterhoeven
2004-11-23 20:53 ` Andrew Walrond
2004-11-23 22:44 ` Antonino A. Daplas
2004-11-23 23:59 ` Andrew Walrond
2004-11-24 22:38 ` Andrew Walrond
2004-11-23 20:21 ` Chad Daelhousen
2004-11-24 23:01 ` Andrew Walrond
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200411250807.32040.adaplas@hotpop.com \
--to=adaplas@hotpop.com \
--cc=andrew@walrond.org \
--cc=linux-fbdev-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).