linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Antonino A. Daplas" <adaplas@hotpop.com>
To: linux-fbdev-devel@lists.sourceforge.net,
	Andrew Walrond <andrew@walrond.org>
Subject: Re: Rivafb won't work with DVI connector
Date: Fri, 26 Nov 2004 22:09:16 +0800	[thread overview]
Message-ID: <200411262209.17558.adaplas@hotpop.com> (raw)
In-Reply-To: <200411251527.15141.andrew@walrond.org>

On Thursday 25 November 2004 23:27, Andrew Walrond wrote:
> On Thursday 25 Nov 2004 00:07, Antonino A. Daplas wrote:
> > 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.
>
> vesafb 'scan' can only find 80xwhatever text modes with dvi connnection,
> and upto 132xwhatever text modes with dsub. It does not display any
> graphics modes at all, and rejects them if I try. (I also tried with vesafb
> only, nvidafb removed - same result).

You can also try this.  1600x1200 is not a standard VESA mode but is most
probably supported by your card as an OEM mode.  However, we do not know the
mode id of 1600x1200 since it's different from vendor to vendor.  

You can use X though to find out what modes are supported by your Video
BIOS.  

1. Boot with DVI attached
2. Change the X driver to 'vesa' (instead of probably 'nv')
3. Launch X
4. Check /var/log/XFree86.?.log
5. Find the mode id you want, add 0x200 and use it in your 'vga='
   boot line

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/

  parent reply	other threads:[~2004-11-26 14:09 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-25  0:07 Rivafb won't work with DVI connector Antonino A. Daplas
2004-11-25 15:27 ` Andrew Walrond
2004-11-25 21:16   ` Antonino A. Daplas
2004-11-26 14:09   ` Antonino A. Daplas [this message]
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=200411262209.17558.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).