From: Thomas Molina <tmolina@cox.net>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Bug 328] New: The computer seems to hang after the kernel has uncompressed and starts to boot.
Date: Sat, 8 Feb 2003 15:00:43 -0600 (CST) [thread overview]
Message-ID: <Pine.LNX.4.44.0302081456180.3031-100000@localhost.localdomain> (raw)
In-Reply-To: <20980000.1044736584@[10.10.2.4]>
On Sat, 8 Feb 2003, Martin J. Bligh wrote:
>
> http://bugme.osdl.org/show_bug.cgi?id=328
>
> Summary: The computer seems to hang after the kernel has
> uncompressed and starts to boot.
> Kernel Version: 2.5.59
> Status: NEW
> Severity: normal
> Owner: bugme-janitors@lists.osdl.org
> Submitter: di00enad@ing.hj.se
>
>
> Distribution: RedHat 8.0
> Hardware Environment: Acer Aspire 1300 laptop
> Software Environment: RedHat 8.0, GCC 3.2, LILO
> Problem Description: When I have compiled the kernel without problems and
> restart the computer the only two lines that are printed are:
>
> Booting 2.5.59
> Uncompressing the kernel, Ok booting the kernel
>
> then there is no more text printed out and the keyboard do not work. But I
> can see some activity on the harddisk for about 10 seconds. When I reset
> the computer fsck is run because the disk was not cleanly unmounted. It
> seems like the system can almost boot but I can't see anything on the
> screen.
I began to see this bug this weekend myself. I'm not sure of the cause,
but it can be worked around by configuring the kernel for built-in (not
modular) support of virtual terminals (CONFIG_VT) and support for console
on virtual terminals (CONFIG_VT_CONSOLE).
next prev parent reply other threads:[~2003-02-08 20:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-08 20:36 [Bug 328] New: The computer seems to hang after the kernel has uncompressed and starts to boot Martin J. Bligh
2003-02-08 21:00 ` Thomas Molina [this message]
2003-02-08 22:18 ` Andries Brouwer
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=Pine.LNX.4.44.0302081456180.3031-100000@localhost.localdomain \
--to=tmolina@cox.net \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
/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).