Return to BSD News archive
Newsgroups: comp.os.386bsd.questions Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!zaphod.mps.ohio-state.edu!cs.utexas.edu!uunet!world!hd From: hd@world.std.com (HD Associates) Subject: Re: Elusive SCSI problems (Adaptec 1542C) <snarl!> Message-ID: <C6x3v7.Eyv@world.std.com> Keywords: Adaptec 1542C, Quantum, SCSI, 386bsd Organization: The World Public Access UNIX, Brookline, MA References: <1993May12.023959.20121@sophia.smith.edu> Date: Wed, 12 May 1993 14:21:06 GMT Lines: 36 In article <1993May12.023959.20121@sophia.smith.edu> jfieber@sophia.smith.edu (J Fieber) writes: >All ye out in netland, I hope some kind soul can help me >with a little problem... > >Supposedly the Adaptec 1542C works fine with 386bsd with >the 0.2.3 patchkit. Others have testified here that it does. > ... I am using the Adaptec 1542C with 386bsd pk0.2.3 and a Micronics 486DX266VL motherboard. Everything worked fine with a 1542B. To get it to work reliably I had to 1. Replace the external cable to my tape drive with a "nice" one (from the typical internal grey flat cable to a commercial round one). 2. Replace the internal cable to one with no overhang off the end (I used to have one more place to hook up a drive beyond the last terminated disk). 3. ILLEGALLY turn on termination on the 1542C. Each step would improve things. I would see read errors during the boot (using Julian's boot blocks you see when it retries). I now have (with TERM the terminator): TERM QIC tape <---> 1542B <--> 1542C TERM <--> DISK0 <--> DISK1 TERM Removing the 1542B (I've been doing target mode work) doesn't affect things. I have to leave the 1542C terminated. This has been working fine for several weeks. Incidentally, the 1542C does not seem to work in target mode.