linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcus Better <marcus@better.se>
To: linux-fbdev-devel@lists.sourceforge.net
Subject: Re: intelfb not working on Thinkpad R60
Date: Fri, 09 Feb 2007 11:16:05 +0100	[thread overview]
Message-ID: <eqhhl5$esr$1@sea.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.0702081850460.7686@pentafluge.infradead.org

James Simmons wrote:
>>*First, if I compile intelfb and fbcon into the kernel, and no other
>>frame buffer modules, I don't think the "vga" parameter is ever
>>processed.

> That is correct vga= is only used by vga console or vesafb.

Some people claim that the boot loader (Grub or Lilo?) is supposed to
interpret the vga= parameter and set the video mode through BIOS.

And what is this text doing in Documentation/fb/intelfb.txt:

  If setting this parameter doesn't work (you stay in a 80x25 text-mode),   
  you might need to set the "vga=<mode>" parameter too - see vesafb.txt in 
  this directory.

> I bet the mode you can passing is incomplete. Please try
> something like this
> 
> video=intelfb:mode:1024x768-8@75

I suppose you mean "video=intelfb:mode=1024x768-8@75"? That doesn't help
either. I get the VGA console or vesafb, depending on whether the "vga="
option was given. Besides the depth and refresh rate parameters are
supposed to be optional.

Regards,

Marcus



-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642

      reply	other threads:[~2007-02-09 10:16 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-08 10:34 intelfb not working on Thinkpad R60 Marcus Better
2007-02-08 18:56 ` James Simmons
2007-02-09 10:16   ` Marcus Better [this message]

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='eqhhl5$esr$1@sea.gmane.org' \
    --to=marcus@better.se \
    --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).