From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Andrew Nelless <andrew@nelless.net>
Cc: linux-kernel@vger.kernel.org, linux-acpi@vger.kernel.org
Subject: Re: 2.6.21-rc1: framebuffer/console boot failure
Date: Mon, 26 Feb 2007 20:41:37 +0800 [thread overview]
Message-ID: <1172493697.20842.6.camel@daplas> (raw)
In-Reply-To: <34578.86.7.220.119.1172401665.squirrel@wmbeta.mxes.net>
On Sun, 2007-02-25 at 11:07 +0000, Andrew Nelless wrote:
> On Sat, February 24, 2007 11:30 pm, Antonino A. Daplas wrote:
> >
> > How about booting with just vga=normal?
> >
> >
> > Tony
> >
>
> That seems to work too. I've rebooted about 20 times in a row
> and it hasn't done it again yet. Why would this only occur
> at higher modes?
>
> In the 2.6.20 dmesg log it reads "Nvidia board detected.
> Ignoring ACPI timer override." whereas in 2.6.21-rc1 it doesn't.
> Could this be the culprit?
>
I don't know, probably the ACPI code can now probably detect the
presence or absence of the HPET timer.
Can you remove CONFIG_FB_VESA support from your kernel config but boot
as if you have vesafb (ie with vga=<VESA mode number>). Your machine may
boot to completion but you will have a blank screen. But you should be
able to have an output in netconsole and you can start X. I wanted to
know if the lockup is related to the framebuffer.
Tony
next prev parent reply other threads:[~2007-02-26 12:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-23 13:35 2.6.21-rc1: framebuffer/console boot failure Andrew
2007-02-23 16:05 ` Andrew
2007-02-28 1:35 ` Bill Davidsen
2007-02-24 11:09 ` Andrew Morton
2007-02-24 22:57 ` Andrew Nelless
2007-02-24 23:00 ` Andrew Nelless
2007-02-24 23:30 ` Antonino A. Daplas
2007-02-25 11:07 ` Andrew Nelless
2007-02-26 12:41 ` Antonino A. Daplas [this message]
2007-02-26 18:48 ` Andrew Nelless
2007-02-26 23:09 ` Antonino A. Daplas
2007-03-04 14:52 ` Andrew Nelless
2007-03-05 6:12 ` Antonino A. Daplas
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=1172493697.20842.6.camel@daplas \
--to=adaplas@gmail.com \
--cc=andrew@nelless.net \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.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