From: Dave Jones <davej@codemonkey.org.uk>
To: Daniel Taylor <dtaylor@vocalabs.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Boot failure, VIA chipset.
Date: Thu, 1 May 2003 16:32:49 +0100 [thread overview]
Message-ID: <20030501153249.GA19001@suse.de> (raw)
In-Reply-To: <Pine.LNX.4.44.0305010547210.1739-100000@dante.vocalabs.com>
On Thu, May 01, 2003 at 05:53:53AM -0400, Daniel Taylor wrote:
> > CONFIG_INPUT=y
> > CONFIG_VT=y
> > CONFIG_VT_CONSOLE=y
> >
> All enabled, and I tried last night with a stripped down 386 only kernel.
>
> No dice, dies hard even before printing the Kernel ID.
>
> It is probably a BIOS compatability issue, but it works OK with 2.4. Since
> the system actually works as it sits I've been taking my time debugging
> the 2.5 issues.
The only other outstanding hang that I've seen was caused by ACPI.
Does it boot with acpi=off ?
Dave
next prev parent reply other threads:[~2003-05-01 15:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-04-30 16:11 Boot failure, VIA chipset Daniel Taylor
2003-04-30 21:48 ` Dave Jones
2003-05-01 9:53 ` Daniel Taylor
2003-05-01 15:32 ` Dave Jones [this message]
2003-05-01 10:41 ` Daniel Taylor
[not found] <20030430171909.GA9529@localhost.localdomain>
2003-04-30 16:31 ` Daniel Taylor
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=20030501153249.GA19001@suse.de \
--to=davej@codemonkey.org.uk \
--cc=dtaylor@vocalabs.com \
--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