From: Alistair John Strachan <alistair@devzero.co.uk>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: Robert Moss <robert.von.moss@gmail.com>, linux-kernel@vger.kernel.org
Subject: Re: Framebuffer issues in 2.6.26 with uvesafb and vesafb. Linux is about choice!
Date: Thu, 23 Oct 2008 10:17:15 +0100 [thread overview]
Message-ID: <200810231017.16126.alistair@devzero.co.uk> (raw)
In-Reply-To: <20081023080459.GC5073@const.bordeaux.inria.fr>
On Thursday 23 October 2008 09:04:59 Samuel Thibault wrote:
> Robert Moss, le Thu 23 Oct 2008 00:54:56 -0700, a écrit :
> > Anyhow, I noticed that vesafb is no longer a part of the kernel.
>
> That's not true. It works nicely on my laptop (though I don't get
> the native 1280x800 resolution).
>
> > vga=791 still gave a mode not found.
>
> Then that's a bug, which is a completely different thing. Could you
> check that the output of vga=ask and typing scan at the boot prompt is
> the same between 2.6.24 and 2.6.25/26 ?
It simply isn't true that the vesafb driver has been removed or disabled. Nor
is it true that the vga= video mode selection has been removed or is broken.
I've been using vga=791, too, for years, and on 2.6.26 and 2.6.27 it continues
to work as it always did.
The OP needs to post his config before creating a fuss about removed features
and "lack of choice". From what I can see, such statements simply aren't true.
At worst there is a bug here on one particular system that needs to be fixed.
--
Cheers,
Alistair.
next prev parent reply other threads:[~2008-10-23 9:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-23 7:54 Framebuffer issues in 2.6.26 with uvesafb and vesafb. Linux is about choice! Robert Moss
2008-10-23 8:04 ` Samuel Thibault
2008-10-23 9:17 ` Alistair John Strachan [this message]
2008-10-23 11:21 ` Robert Moss
2008-10-23 12:22 ` Alistair John Strachan
2008-10-23 15:26 ` H. Peter Anvin
2008-10-24 9:24 ` Samuel Thibault
2008-10-25 20:22 ` Robert Moss
2008-10-25 21:23 ` H. Peter Anvin
2008-10-23 11:26 ` Robert Moss
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=200810231017.16126.alistair@devzero.co.uk \
--to=alistair@devzero.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=robert.von.moss@gmail.com \
--cc=samuel.thibault@ens-lyon.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.