public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: David van Hoose <davidvh@cox.net>
To: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [2.5.69] Fails on "Uncompressing Kernel" (detailed)
Date: Tue, 06 May 2003 08:34:57 -0500	[thread overview]
Message-ID: <3EB7BA01.2000206@cox.net> (raw)
In-Reply-To: <3EB7B578.4000005@cox.net>

David van Hoose wrote:
> I've managed to get 2.5.69 to boot *once*. Not trusting the kernel to 
> report the numerous problems until I can boot the kernel more than once. 
> I lost my config so I can't figure out what I managed to do so right. I 
> have tried a couple other configs that I normally use for 2.4.x, but 
> with the new 2.5.x options. Those I have attached.
> All I get is the "Uncompressing Linux" and then no more output. However, 
> it appears that my system is booting anyway as if it is on another TTY. 
> I can even tell when kudzu kicks in. I have no input (keyboard/mouse) or 
> output (monitor) though.
> 
> Hardware:
> Northwood Pentium 4 2.53GHz
> Motherboard is an Asus P4S8X
>  SiS648 Northbridge / SiS963 Southbridge
> nVidia GeForce2 MX 400
> 
> Software:
> RedHat 9 w/ all updates
> Using Rusty's module-init-tools-0.9.12-pre1
> Kernel 2.5.69 as stated
> 
> How can I get this beast to boot?

Running GRUB 0.93 as released by RedHat. I just got the messages for the 
other thread. I've gotten it to boot once, so I don't think it is Grub.

Thanks,
David


  reply	other threads:[~2003-05-06 13:22 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-06 13:15 [2.5.69] Fails on "Uncompressing Kernel" (detailed) David van Hoose
2003-05-06 13:34 ` David van Hoose [this message]
2003-05-06 14:18   ` David van Hoose
     [not found] <fa.athqjpk.133cvik@ifi.uio.no>
2003-05-06 15:24 ` walt
2003-05-06 18:27   ` Bill Davidsen
2003-05-06 18:33   ` David van Hoose

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=3EB7BA01.2000206@cox.net \
    --to=davidvh@cox.net \
    --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