Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA1915 ; Tue, 23 Feb 93 15:03:54 EST Newsgroups: comp.os.386bsd.bugs Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!boulder!ucsu!spot.Colorado.EDU!kolar From: kolar@spot.Colorado.EDU (Jennifer Lynn Kolar) Subject: Re: BSD will not boot now Message-ID: <kolar.730405393@spot.Colorado.EDU> Sender: news@ucsu.Colorado.EDU (USENET News System) Nntp-Posting-Host: spot.colorado.edu Organization: University of Colorado, Boulder References: <kolar.730373883@spot.Colorado.EDU> Date: Mon, 22 Feb 1993 18:23:13 GMT Lines: 28 kolar@spot.Colorado.EDU (Jennifer Lynn Kolar) writes: >Hi, solved the com driver problems, but now I have a new problem. I installed >the XFree86 distribution, and it complained about not having the X stuff in >the kernel. I traced it down to using syscons, so I deinstalled it, and reused >the pccons driver. Rebuilt the kernel, and rebooted after installing the new >kernel, and now the machine just will not boot. I get a page full of errors >that scroll too fast to read, but have something to do with wd: hard errors >and then the machine reboots. I tried to boot off the 0.2 dist and fixit >disks, but it hangs after I get the copyrights (it never probes). I can boot >off of the dist 0.1 floppy, but when I tried to copy the kernel from the fd to >the hd and reboot, it fails with same errors. I can get the 0.2 dist floppy to >boot on another machine,so I guess it is bombing on my clone ide controller? >iI had thought that at first, but I recall the first probe to be the console... Ok, solved the problem. Here's the work-around: The 0.1 dist boot did not have fsck on it, so /dev/rwd0a was unable to properly mount, thus when 386bsd was copied onto the mounted filesystem, it was in a rather sad state. I booted 0.1 on fd0, and mounted 0.2 fix_it on fd1. I ran fsck on /dev/rwd0a, and cleaned up the filesystem, mounted /dev/wd0a, and removed the zero byte 386bsd and 386bsd.old files, and then copied /386bsd to the hd. I synced the filesystem and rebooted. 0.2 kernel will not boot, because of the A20 reset problems mentioned in eariler posts. After I was able to boot off the hd, I backed out patch00083, rm'd pccons.o, and rebuilt the kernel. Rebooted the machine, and all is well. Hope this helps anyone with a similar problem. J