From: Alistair John Strachan <alistair@devzero.co.uk>
To: "Robert Moss" <robert.von.moss@gmail.com>,
"H. Peter Anvin" <hpa@zytor.com>
Cc: "Samuel Thibault" <samuel.thibault@ens-lyon.org>,
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 13:22:15 +0100 [thread overview]
Message-ID: <200810231322.15257.alistair@devzero.co.uk> (raw)
In-Reply-To: <6ffd69180810230421v1508664bgc6e454cde792154f@mail.gmail.com>
On Thursday 23 October 2008 12:21:09 Robert Moss wrote:
> I also want to note, that I downloaded 2.6.27.3 and compiled, with
> CONFIG_FB_VESA=Y, and still get excactly the same response as from
> 2.6.26
Useful info, and I checked your configs and they enable the right options.
Looks like you've found a real bug.
IIRC, a lot of real mode assembler (including the x86 vga/vesa stuff, iirc)
was rewritten a year or so ago, in C. This might have been the time that this
bug was introduced. I've added hpa to CC since I believe he was the author of
these changes.
(Summary of the original report is that vga= vesa mode selection seems to have
broken for Robert since at least 2.6.26, and after 2.6.24. From what I can see
he has the right vesafb options enabled.)
> Screen unavailable [or not found, im not sure] 317. (which i believe
> is 0x317 = 791)
I grepped the tree for "Screen unavailable" and "Screen not found" and found
nothing. Could you please reproduce the message and confirm which exactly it
is?
--
Cheers,
Alistair.
next prev parent reply other threads:[~2008-10-23 12:22 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
2008-10-23 11:21 ` Robert Moss
2008-10-23 12:22 ` Alistair John Strachan [this message]
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=200810231322.15257.alistair@devzero.co.uk \
--to=alistair@devzero.co.uk \
--cc=hpa@zytor.com \
--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 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).