Return to BSD News archive
Path: sserve!manuel.anu.edu.au!munnari.oz.au!hp9000.csc.cuhk.hk!saimiri.primate.wisc.edu!zaphod.mps.ohio-state.edu!magnus.acs.ohio-state.edu!usenet.ins.cwru.edu!cleveland.Freenet.Edu!cc465
From: cc465@cleveland.Freenet.Edu (Steven M Ratliff)
Newsgroups: comp.unix.bsd
Subject: Re: [386BSD] Infinite reboot with partitioned IDE drive
Date: 18 Nov 1992 19:43:53 GMT
Organization: Case Western Reserve University, Cleveland, OH (USA)
Lines: 32
Message-ID: <1ee6dpINNkjc@usenet.INS.CWRU.Edu>
References: <1992Nov17.201554.21921@cs.mun.ca>
Reply-To: cc465@cleveland.Freenet.Edu (Steven M Ratliff)
NNTP-Posting-Host: slc10.ins.cwru.edu
In a previous article, paul8@odie.cs.mun.ca (Paul Manuel) says:
>
>Problem: Machine goes into an infinite reboot when running
> 386BSD with the disk having BSD and MSDOS partitions.
>
>Machine Specs: Processor: 486DX/33Mhz
> RAM: 8MB
> Cache: 128K
> Disk: 100MB Kalok KL3100
> Chip Set: UMC (UM82C480)
> VGA Card: Cardinal VGA 16bit, 1MB
>
>Success: I've had success getting 386bsd running using the Kalok
> drive if I use the entire volume for BSD but I have to
> keep a msdos partition>
I have the same problem with a 33 Mhz 386DX 4MB RAM 128K cache and
a Connor Peripherals cp30104 120MB IDE drive. Both the stock Dist.fs and the
CGD patched Dist.fs go into the infinite hard reboot cycle when partitioned
with Dos and both work just fine if installed on the entire volume. When they
are partioned with DOS the banner comes up and then the kernel panics. Un-
fortunately it reboots far to fast to be able to read the diagnostic messages.
The best I could make out was a kernel panic trap and then something about
dumping RAM to disk.
The install does put all the files out there and wd0a can be mounted
from the fixit or dist floppy on /mnt and files can be manipulated on the
drive. Is there a way to boot from a floppy and then mount wd0a on /?
I can live with this as a temporary workaround.
--
cc465@cleveland.freenet.edu <Steve Ratliff>