mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Danny Brow <fms@istop.com>
To: Kernel-Maillist <linux-kernel@vger.kernel.org>
Subject: Re: 2.4.23 Boot failure
Date: Fri, 12 Dec 2003 15:57:50 -0500	[thread overview]
Message-ID: <1071262670.19921.1.camel@zeus.fullmotionsolutions.com> (raw)
In-Reply-To: <1071260218.13287.46.camel@bubbles.imr-net.com>

I have this problem with an acer laptop, if you have apic selected you
will never get passed the uncompressing Linux screen. If you have frame
buffer support compiled in you could try to append vga=normal to lilo to
see if there are any errors.

Dan.

On Fri, 2003-12-12 at 15:16, Joshua Schmidlkofer wrote:
> 2.4.23 Hangs just after the boot loader.
> 
> This is what I get:
>  
> Uncompressing Linux... Ok, booting the kernel.
> 
> 
> Then nothing.   I have never seen this before.  I do not get any errors,
> it just hangs.  
> 
> I have been trying to upgrade my server from 2.4.20 to 2.4.23.  This
> server is running the xfs patches from SGI.
> 
> It is a Dual PIII 800
> 1.1GB Ram
> 
> Storage:
>    cpqarry - Compaq Smart Array 431 Controller
>      RAID5 array [5 disks.]
>    sym53c8xx
>      4 independent scsi disk - Boot drive here.
> 
> 
> Attached is my .config, 
> 
> Please let me know if there is anything else.  I have tried make
> mrproper, then rebuilding, and I have changed a few options, etc.
> 
> Note:  2.4.21, and 2.4.22 both started booting, but would hang on the
> sym53c8xx controller.  I did not devote time to the issue to sort it
> out.  I need to update because of the brk() vuln, and I would rather
> just move to 2.4.23.  
> 
> I am using 2.4.23 + xfs patches.
> 
> thanks,
>   Joshua


      parent reply	other threads:[~2003-12-12 20:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-12 20:16 Joshua Schmidlkofer
2003-12-12 20:25 ` Richard B. Johnson
2003-12-12 20:57 ` Danny Brow [this message]

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=1071262670.19921.1.camel@zeus.fullmotionsolutions.com \
    --to=fms@istop.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

all inboxes | Powered by JetHome®