Return to BSD News archive
Newsgroups: comp.unix.bsd Path: sserve!manuel!munnari.oz.au!uunet!mcsun!sun4nl!eur.nl!pk From: pk@cs.few.eur.nl (Paul Kranenburg) Subject: Re: Again: 386BSD-0.1 booting problem ..... Message-ID: <1992Jul18.101122.14743@cs.few.eur.nl> Sender: news@cs.few.eur.nl Reply-To: pk@cs.few.eur.nl Organization: Erasmus University Rotterdam References: <5454@umriscc.isc.umr.edu> <5458@umriscc.isc.umr.edu> Date: Sat, 18 Jul 1992 10:11:22 GMT Lines: 36 In <5458@umriscc.isc.umr.edu> jlu@mcs213i.cs.umr.edu (Eric Jui-Lin Lu) writes: >In article <5454@umriscc.isc.umr.edu> jlu@cs.umr.edu (Eric Jui-Lin Lu) writes: >Other sugguestions????? Somebody! >>Boot hang: >> >>386BSD banner msg and >>pc0<color> at 0x60 irq 1 on isa >>com1 at 0x3f8 irq 4 on isa >>com2 at 0x2f8 irq 3 on isa >BEEP here >>wd0 <DW9 0344A-( 4 0BM) > at 0x1f0 irq 14 on isa >>fd0 drives 0:1.2M, 1:1.44M at 0x3f0 irq 6 drq 2 on isa >>changing root device to fd0a >>(then period) >> We have got the same disk, the same BEEP, the same disk Id report and the same hang... Booting while the disk is not in the CMOS configuration succeeds, but a subsequent attempt to run "install" fails with all sorts of seek errors. I am inclined to believe that the disk geometry is not read correctly when autoconfiguring. I brought up version 0.0 again, mounted the version 0.1 boot floppy (eg. "mount /dev/fd0a /mnt") and then proceeded to twiddle various bits by hand (copy the 0.1 kernel, init, ifconfig, etc...). The system now boots 0.1 from the HD. I am not convinced that all is well now, this particular disk needs a more thorough inspection. Cheers, -pk