Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA2120 ; Thu, 25 Feb 93 15:17:19 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!saimiri.primate.wisc.edu!usenet.coe.montana.edu!nate From: nate@cs.montana.edu (Nate Williams) Subject: Re: 386BSD scsi problem Message-ID: <1993Feb24.203614.22362@coe.montana.edu> Sender: usenet@coe.montana.edu (USENET News System) Organization: Dept. of Computer Science, MSU, Bozeman Mt 59717 References: <1993Feb16.220610.274@jcn.w.open.de> <C2yo1r.2pn@flatlin.ka.sub.org> Date: Wed, 24 Feb 1993 20:36:14 GMT Lines: 21 In article <C2yo1r.2pn@flatlin.ka.sub.org> bad@flatlin.ka.sub.org (Christoph Badura) writes: >In <1993Feb16.220610.274@jcn.w.open.de> azell@jcn.w.open.de (Andreas Zell) writes: >>if i try to boot the dist.fs floppy from 386BSD, i got the >>following message: >>as0b: controller error 0x16 reading fsbn0 >>scsi sense: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 >>My systemconfiguration is: >>Adaptec 1542A > >The stock 386BSD 0.1 SCSI driver doesn't work with the 1542A. You need >a 1542B. Or get a patched kernel and bootblocks that support the 1542A, which patch00601 does. The kernel in the patchkit bootables has the kernel fixes, but the bootblocks did not get updated, unfortunately. Nate -- opjnw@terra.oscs.montana.edu | Still trying to find a good reason for nate@cs.montana.edu | these 'computer' things. Personally, home #: (406) 586-0579 | I don't think they'll catch on - Don H.