Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!howland.reston.ans.net!darwin.sura.net!haven.umd.edu!umd5.umd.edu!roissy.umd.edu!mark From: mark@roissy.umd.edu (Mark Sienkiewicz) Newsgroups: comp.os.386bsd.questions Subject: Re: Recent tar_files/sys.tar.z distribution. Date: 29 Jun 1993 20:59:11 GMT Organization: University of Maryland Lines: 21 Distribution: world Message-ID: <20qaev$asm@umd5.umd.edu> References: <20knemINNciu@crcnis1.unl.edu> NNTP-Posting-Host: roissy.umd.edu In article <20knemINNciu@crcnis1.unl.edu> rse@cse.unl.edu (robert ellsworth) writes: > 2) I can no longer boot my machine with the newly compiled kernel. > When it goes through the displaying of your system configuration, > it doesn't include my 2 IDE drives (Conner 170M, and Seagate 157A), > does a panic: trap, and reboot my machine. But.. If I was to turn > the turbo switch off, it recognizes the disks, but then I receive > ISA strayintr 7's. In wdprobe() it calls wdcommand() to try to WDC_DIAGNOSE. I found that if I don't check the error return, it finds my controller but not the disks. If I slow the machine down, it finds the disks too. I saw some discussion of timing problems related to this on the mailing list. I notice that wd.c is changed quite a bit from the old barsoom driver. Anyway, I got the kludged kernel to boot, and it said "panic: init died". I don't think it is really running /sbin/init-- I put code in icode[] in locore.s to open the console and write to it and I never saw that either. I'm running a 0.8 kernel right now... :)