Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!news.ecn.uoknor.edu!news.ysu.edu!news.radio.cz!newsbastard.radio.cz!news.radio.cz!CESspool!nntp.uio.no!news.maxwell.syr.edu!dispatch.news.demon.net!demon!fido.news.demon.net!demon!newsgate.unisource.nl!news.unisource.nl!xs4all!not-for-mail From: "Taco Scargo" <taco@pulse.nl> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: Kernel panic after bootup Date: 1 Apr 1997 17:46:54 GMT Organization: Pulse Interactive Sender: pulse@compaq.webguide.nl Message-ID: <01bc3ec4$ad0613a0$f629e5c2@compaq.webguide.nl> References: <859601445.4199@dejanews.com> <01bc3c33$09de6620$e8206dc2@taco> <01bc3d27$b78fba40$1b618bd0@nevin.shadowave.com> <5hp9cl$2k2$1@news1.xs4all.nl> NNTP-Posting-Host: compaq.webguide.nl X-XS4ALL-Date: Tue, 01 Apr 1997 19:46:54 CEST X-XS4ALL-User: pulse@xs4all.nl on compaq.webguide.nl X-Newsreader: Microsoft Internet News 4.70.1155 Lines: 36 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:38208 That's nice for you, but I only have 1 (one) SCSI disk in the damned machine > Hi > > I got the same problem.... I solved it by putting my hard-disk at IDE > slot 0. On many boards, you can choose between IDE 0 and IDE 1. Make > sure your boot disk is at IDE 0 and it should work. > > Vince > > Vincent Ossewaarde <vincento@knoware.nl> wrote in article <5hp9cl$2k2$1@news1.xs4all.nl>... > "Nevin K Ng" <nevin@iname.com> wrote: > > >I have the same problem too, when I successfully installed 2.1.6-RELEASE > >on my second HD, it just can't mount the root and reboot. If I type > >1:wd(2,a)/kernel during the boot prompt, then everythings went ok... > >I have tried to modify the biosboot makefile that included the harddisk > >bias > >flag and compile it again, and it still does works...any help? > > > >Taco Scargo <taco@pulse.nl> 次寫入到主題 > ><01bc3c33$09de6620$e8206dc2@taco>... > >> If you look at my message a few messages below, I've got exactly the same > >> problem. > >> > >> I can't work it out either .... > >> If you get a reply, let me know, I'll let you know when I fix my problem. >