From: Pavel Roskin <proski@gnu.org>
To: The development of GRUB 2 <grub-devel@gnu.org>
Subject: Re: [PATCH] Video mode fixes in linux loader
Date: Mon, 13 Apr 2009 11:41:36 -0400 [thread overview]
Message-ID: <1239637296.3549.9.camel@mj> (raw)
In-Reply-To: <20090413144558.GA22165@thorin>
On Mon, 2009-04-13 at 16:45 +0200, Robert Millan wrote:
> On Mon, Apr 13, 2009 at 04:16:57PM +0200, Robert Millan wrote:
> > > The default VGA mode is now GRUB_LINUX_VID_MODE_NORMAL, not the mode of
> > > the kernel we tried to load before.
> >
> > Ok, BUT if we're already in vesa mode, and we know it works (since we're using
> > it), there's no point in wasting time only to get a worse mode.
> >
> > We should just make sure subsequent calls to "linux" command override the
> > previous one.
>
> I think this should do it. Can you confirm this works for you?
I actually installed GRUB with gfxterm on a laptop that has Intel
framebuffer support. Now the kernel starts in VESA mode and then the
screen goes blank because intelfb cannot deal with it. Sure, intelfb
should be fixed, but we should be liberal in what we accept. Some
kernels may not support VESA modes at all.
Adding vga=0 to the kernel command line didn't fix it. That's bad.
"vga=0" means text mode 80x25. Adding "vga=1" fixed the problem. The
text mode was 80x25, not 80x50, so that's another issue.
"vga=ask" is not a warning now. It causes "error: You need to load the
kernel first", apparently from initrd. In other words, the "linux"
command fails and there is no visible warning.
--
Regards,
Pavel Roskin
next prev parent reply other threads:[~2009-04-13 15:41 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-06 15:34 [PATCH] Video mode fixes in linux loader Pavel Roskin
2009-04-07 0:31 ` Yoshinori K. Okuji
2009-04-07 0:49 ` Pavel Roskin
2009-04-07 7:31 ` phcoder
2009-04-07 22:04 ` Pavel Roskin
2009-04-12 19:11 ` phcoder
2009-04-12 20:43 ` Pavel Roskin
2009-04-13 14:16 ` Robert Millan
2009-04-13 14:45 ` Robert Millan
2009-04-13 15:41 ` Pavel Roskin [this message]
2009-04-13 19:05 ` Robert Millan
2009-04-13 23:20 ` Pavel Roskin
2009-04-14 0:02 ` phcoder
2009-05-02 11:38 ` Robert Millan
2009-05-02 11:31 ` Robert Millan
2009-05-02 15:32 ` Robert Millan
2009-05-03 0:03 ` BandiPat
2009-05-03 15:53 ` Robert Millan
2009-05-04 15:15 ` BandiPat
2009-05-04 16:01 ` Robert Millan
2009-05-04 18:16 ` BandiPat
2009-05-04 18:16 ` Felix Zielcke
2009-05-04 20:30 ` Robert Millan
2009-05-04 21:59 ` BandiPat
2009-05-13 20:47 ` Robert Millan
2009-05-04 18:04 ` Robert Millan
2009-05-03 13:18 ` Isaac Dupree
2009-05-03 15:50 ` Robert Millan
2009-04-13 15:16 ` Pavel Roskin
2009-04-13 18:59 ` Robert Millan
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=1239637296.3549.9.camel@mj \
--to=proski@gnu.org \
--cc=grub-devel@gnu.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.