Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!harbinger.cc.monash.edu.au!bunyip.cc.uq.oz.au!munnari.oz.au!uunet!usc!howland.reston.ans.net!gatech!newsxfer.itd.umich.edu!caen!night.primate.wisc.edu!relay!news From: bgosse@nswc.navy.mil (Bruce Gosse) Subject: Re: FreeBSD and Adaptec 1542CF SCSI Message-ID: <1994Dec2.165109.29237@relay.nswc.navy.mil> Sender: news@relay.nswc.navy.mil Reply-To: bgosse@nswc.navy.mil Organization: NSWCDD N52 References: <3bng94$iaf@Mars.mcs.com> Date: Fri, 2 Dec 1994 16:51:09 GMT Lines: 44 I have been using an Adaptec 1542B board since 386bsd drivers were first available and have been using the same hardware configuration and cables since then and proceeded through all freeBSD releases on my system. No problems until now. I experienced installation problems with 2.0A when I left the install program to do the loading of the system from tape. I only got errors trying to access the tape with the Archive 150 reporting unknown command problem. (sorry I didn't get it written down, but it can be recreated). I then had errors reported on sd0 and the system hung up. After several attempts I stopped. I successfully installed 2.0R also doing the manual route from the tape. Observed some problems on the SCSI devices until I rebuilt my own kernel with no extra devices or cpu's supported. I actually had sd0 become non-accessible with the GENERICAH driver. The system was running but I could not access the drive to even do a shutdown. I now observe that if a tape is loaded in the drive when the system is booted, it will have received something over the interface to place it in a hung state. This can be cleared by unloading the tape and reloading it. I am starting to look at the problem. My impression is that something is different in the SCSI driver for 1542 boards from all previous releases, and that kernels that support multiple CPU types may make the problem more sever. my system is simple: 386 25MHz Adaptec 1542B with sd0 and st0 wd2 wd0 exists but is only DRDOS for by kids. I configured the kernel to only support 386 CPU's which seems to have eliminated the SCSI problems, except for tape access if loaded before booting. Otherwise, a great system, I have enjoyed in for years, and learned much. --- ========================================================================== Bruce Gosse "expressing personnel opinions, but working for" Naval Surface Warfare Center Dahlgren Division, Code N52 bgosse@relay.nswc.navy.mil Phone: (703) 663-6250