All of lore.kernel.org
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Robert Moss <robert.von.moss@gmail.com>
Cc: Samuel Thibault <samuel.thibault@ens-lyon.org>,
	linux-kernel@vger.kernel.org, alistair@devzero.co.uk
Subject: Re: Framebuffer issues in 2.6.26 with uvesafb and vesafb. Linux is about choice!
Date: Sat, 25 Oct 2008 14:23:12 -0700	[thread overview]
Message-ID: <49038E40.2070300@zytor.com> (raw)
In-Reply-To: <6ffd69180810251322n350b6f6dqf496d7e5972165f5@mail.gmail.com>

Robert Moss wrote:
> ok, this morning, I turned on my computer, and it gave me the error
> message again:
> 
> Undefined video mode number: 317

Your VESA BIOS seems to have some serious braindamage (the fact that the 
modes don't list at all is evidence of that), but finding out what can 
be done to help it would be useful.

Again, a git bisect between v2.6.24 and v2.6.26 would be best:

git clone \
     git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux-2.6.git
cd linux-2.6.git
git bisect start
git bisect bad v2.6.26
git bisect good v2.6.24
<build and test kernel>
git bisect <good,bad>
<keep going until one commit shows up>

If a commit doesn't build or otherwise exhibit a different problem 
(meaning "no info available"), use "git bisect skip".

	-hpa

  reply	other threads:[~2008-10-25 21:23 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
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 [this message]
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=49038E40.2070300@zytor.com \
    --to=hpa@zytor.com \
    --cc=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.