Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP
id AA5450 ; Thu, 24 Dec 92 11:14:02 EST
Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!sdd.hp.com!zaphod.mps.ohio-state.edu!cs.utexas.edu!gateway
From: DS1437@acspr1.acs.brockport.edu
Newsgroups: comp.unix.bsd
Subject: 386BSD Kernel hang problems on Gateway 2000 486/DX2
Date: 22 Dec 1992 12:19:39 -0600
Organization: UTexas Mail-to-News Gateway
Lines: 49
Sender: daemon@cs.utexas.edu
Message-ID: <9212221819.AA18464@deepthought.cs.utexas.edu>
NNTP-Posting-Host: cs.utexas.edu
I am trying to install 386bsd on a GateWay 2000 486 50Mhz DX/2. The
system has a 205 Mb IDE Drive. I can run the install disk fine, however
when I boot off the hard drive the screen looks like this:
pc0<color> at 0x60 irq 1 on isa
com1 at 0x3f8 irq 4 on isa
com2 at 0x2f8 irq 3 on isa
/* There is a sufficient long delay here for some reason */
fd0 drives 0:1.44M, 1:1.2M at 0x3f0 irq 6 drq 2 on isa
ne0 ethernet address 02:00:00:00:14:e4 at 0x300 irq 9 on isa
npx0 at 0xf0 irq 13 on isa
PANIC: Cannont mount root
trap type 12 code=fe060000 eip=fe01278a cs=8 eflags=10282 cr2 14 cpl a
PANIC: trap
/* It then says something about dumping the memory to the device and */
/* Gets a --device bad message */
Notice that the hard drive controller was never listed in the list,
however when I boot from the fixit or install disk it looks the exact same
except where the delay occurs I get a line like:
wd0 <WDC AC2200F> at 0x1f0 irq 14 on isa
If I boot with the fixit disk, I then can mount the hard drive without
a problem. I tried copying the kernel from the fixit to the hard drive,
and even tried changing the device files still it did it.
I downloaded the unofficial fixes which claim that wd.c was fixed, and that
still did not change a thing. (In directory newbootables)
I have not tried the compaq bootable fixed yet, however what I have
been told by Adrian@rachel.ibmpcug.co.uk that the compaq fix is something
totally different, and that fix would not work in this case.
Do anyone have any incling why the kernel is not initializing the
hard drive controller correctly as that looks like the problem to me?
****************************************************************************
Name: Donald L. Schleede Snail-Mail:
Call: KB2LZF (kb2lzf@wb2wxq.ny.na.usa) Dept. Earth Sciences
E-mail Addresses: SUNY Brockport
ds1437@acspr1.acs.brockport.edu Brockport, NY 14420
dschleede@unidata.ucar.edu Twisted Pair:
root@kb2lzf.UUCP (716) 395-5718
Planet: Earth
****************************************************************************