public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nathan <wfilardo@fuse.net>
To: linux-kernel@vger.kernel.org
Subject: 2.4 Unable to boot on Cyrix box?
Date: Sat, 12 Jan 2002 12:02:25 -0500	[thread overview]
Message-ID: <3C406C21.3050208@fuse.net> (raw)

Hi.

I have an old recycled box playing firewall for me which stubbornly 
refuses to run 2.4.  2.2.17,18,19,20 and a handful of -pre* patches have 
run just fine.

The system just hangs after 2.4 prints out:
SIS5513: IDE controller on PCI bus 00 dev 09
SIS5513: not 100% native mode: will probe irqs later
    ide0: BM-DMA at 0x4000-0x4007, BIOS settings: hda:pio, hdb:pio
    ide1: BM-DMA at 0x4008-0x400f, BIOS settings: hdc:pio, hdd:pio
hda: Maxtor 90320D2, ATA DISK drive
hdb: CD-ROM CDU76E, ATAPI CDROM drive
ide0 at 0x1f0-0x1f7,0x3f6 on irq 14

2.2 continues fine.  But 2.4 appears to hang here forever.  No panic, no 
keyboard control, C-A-D does nothing.

hda: Maxtor 90320D2, 3079MB w/256kB Cache, CHS=782/128/63
Partition check:
 hda: hda1 hda2 hda3
VFS: Mounted root (ext2 filesystem) readonly.

Relevant system specs:
Cyrix 233MHz processor
64M PC-100 RAM (1 dimm)
SIS5513 IDE chipset
    LSPCI reports: 00:01.1 IDE interface: Silicon Integrated Systems 
[SiS] 5513 [IDE] (rev d0)


I have the kernel built for a 386, PCI and EISA support enabled (and 
their respective PNP) all Y, SIS5513 support included in the kernel... 
 What am I missing, here?

More information available if needed.

Thanks in advance,
--Nathan



             reply	other threads:[~2002-01-12 17:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-12 17:02 Nathan [this message]
2002-01-13 19:34 ` 2.4 Unable to boot on Cyrix box? Lionel Bouton
2002-01-16 19:05   ` robert w hall
  -- strict thread matches above, loose matches on Subject: below --
2002-01-13  9:57 Zwane Mwaikambo

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=3C406C21.3050208@fuse.net \
    --to=wfilardo@fuse.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