Return to BSD News archive
Xref: sserve comp.os.386bsd.misc:1328 comp.os.386bsd.questions:6279 Newsgroups: comp.os.386bsd.misc,comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!geraldo.cc.utexas.edu!portal.austin.ibm.com!awdprime.austin.ibm.com!radha From: radha@austin.ibm.com (Radha Krishnan) Subject: Re: FreeBSD installation problem [still unsuccessful!] Originator: radha@worf.cet.austin.ibm.com Sender: news@austin.ibm.com (News id) Message-ID: <CFKuEH.1Iy9@austin.ibm.com> Date: Wed, 27 Oct 1993 22:27:52 GMT References: <CFGELv.1Hv@latcs1.lat.oz.au> <CFIHt1.E1F@latcs1.lat.oz.au> Organization: IBM Austin Lines: 78 In article <CFIHt1.E1F@latcs1.lat.oz.au>, wongm@latcs1.lat.oz.au (M.C. Wong) writes: > In article <CFGELv.1Hv@latcs1.lat.oz.au> wongm@latcs1.lat.oz.au (M.C. Wong) writes: > > > >Hi, > > During my last installation of FreeBSD, I got to the step where I ahve > >finished with 3rd floppy, ie cpio-floppy, and let FreeBSD boot itself up > >off the hard disk (wd0), upon the first boot, it complains about 4 fsck errors > >as is mentioned in install notes, and boots itself up for the 2nd time, and > >supposed to be with a clean filesystem this time, but I got the following > >error messages. > > > >Automatic reboot in progress ... > >Bus error > >Unkown error in reboot > >Automatic reboot in progress ... > >Bus error > >Unkown error in reboot > >. > >. > >. [repeated!] > > > > ANd I realized where the problem was, ie fsck -p in .profile! So, I > >experimented booting up from kcopy-aha-floppy, and did fsck on /dev/wd0a > >and /dev/wd0e, and the conclusion is sometimes fsck fails, sometimes > >it doesn't. But most of the time when I boot up from hard disk, the fsck > >fails quite often, so I copy the fsck from kcopy-aha-floppy, and try it > >out and the conclusion was as before, sometimes it works, sometimes it > >complaints a Bus error (core dumped). I figured out that when the / is still > >read-only, a core dumped is not possible, and I am left with ambiguous error > >of Bus error, looks very much like hardware problem! So, I finally get to the > >point to copy a new fsck onto my FreeBSD /sbin, and let boot up use the new > >(fresh) fsck does its job, and I read in all of the binary and source > >distribution, and get them extracted in to proper places. But when I start up > >the system, I still have the following 2 problems : > > > > 1) fsck complains about Bus error, looks like transient problem to me , > > why ? Can I make this problem go away permanently ? > > > > 2) Upon starting up network (from /etc/rc), I get a panic message : > > > > Starting network > > vm_fault (fe11e0000, fe345000, 3, 0)->1 type c, code 2 > > trap type 12 code = 2 eip = fe02287d cs = 8 eflags = 10202 cr2 fe345000 > > cpl 1a > > panic : trap > > Syncing disks ... > > > > I tried rebooting a few times, but I keep getting problem 2), can someone > >help please ? > > > > Well, I have been persistent enough to stay up with FreeBSD so far, and I > >hope you guys can just get me onto the right path, by baring with my > >unsuccessful installtion, and I will be right! > > > > Thanks in advance, and email replies please! > > > >- wongm@latcs1.lat.oz.au (M.C Wong) > >-- > >- wongm@latcs1.lat.oz.au > You are not alone. The solution seems to lie in getting the "Correct" set of diskettes that have just the right "kernel" as the GENERICXX Kernel. I had similar problems, and after three days of futile attempts, using the floppy images under "floppies.10xxxx" on FreeBSD.cdrom.com, I reverted to one of the old Set of diskettes that had lying around since the "GAMMA" Days and, that sure enough cured the problem. I had no further problem. I could send you the copies / Images if you need and you could give that a try. I've been meaning to "post" a bug-report to FreeBSD-BUGS@freefall.cdrom.com; Am yet to get around to it!! Radha Krishnan - IBM , Customer Environment Technology Tel. (512)-838-3720 Email: radha@austin.ibm.com Tel. Tie line 678-3720