From owner-freebsd-scsi Sun Dec 28 04:27:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA08715 for freebsd-scsi-outgoing; Sun, 28 Dec 1997 04:27:33 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from colossus.dyn.ml.org (root@206-18-115-184.la.inreach.net [206.18.115.184]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA08685; Sun, 28 Dec 1997 04:27:21 -0800 (PST) (envelope-from dburr@POBoxes.com) Received: from control.colossus.dyn.ml.org (dburr@control.colossus.dyn.ml.org [192.160.60.1]) by colossus.dyn.ml.org (8.8.7/8.8.7) with SMTP id EAA29749; Sun, 28 Dec 1997 04:32:06 -0800 (PST) (envelope-from dburr@POBoxes.com) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 Date: Sun, 28 Dec 1997 04:29:38 -0800 (PST) Organization: Starfleet Command From: Donald Burr To: FreeBSD SCSI To: FreeBSD SCSI , FreeBSD Questions Subject: Source of cheap NCR/SymBIOS PCI SCSI adapters? Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- I'd like to get a new PCI SCSI adapter. I've heard good things about the NCR/SymBIOS ones, and would like to obtain one. I don't have any Ultra or Wide devices, so I don't need an adapter with all the bells and whistles. (all I'll be driving is a CD-ROM and a Jaz drive) Where's the cheapest I can get these (either a store or mail-order outfit), and how much should I expect to pay? Please respond by email to . Thanks! - --- Donald Burr - Ask me for my PGP key | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNKZGxPjpixuAwagxAQG/LAP/cLgxvDoqx0cFc0G55EkA6sV3SBaLGFdB 5+5BfUdkUgJ5HPfY6/yyMJOBgP/oWg2SJSXPNvYB3EZJrHNKxCVn7LZDsilezzcr CBqdAkep79r3mAeq4O3WVkswPHpCrIihL/460iviT78dBu/EbcL3R+d2BS7nK1ym ZUZXUSvdadU= =L9X0 -----END PGP SIGNATURE----- From owner-freebsd-scsi Sun Dec 28 12:53:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA04471 for freebsd-scsi-outgoing; Sun, 28 Dec 1997 12:53:16 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from bob.tri-lakes.net (BOB.tri-lakes.net [207.3.81.6]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id MAA04452 for ; Sun, 28 Dec 1997 12:53:10 -0800 (PST) (envelope-from cdillon@tri-lakes.net) Received: from [207.3.81.136] by bob.tri-lakes.net (NTMail 3.02.13) with ESMTP id ua394206 for ; Sun, 28 Dec 1997 14:52:29 -0600 Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: Date: Sun, 28 Dec 1997 14:49:21 -0600 (CST) From: Chris Dillon To: Donald Burr Subject: RE: Source of cheap NCR/SymBIOS PCI SCSI adapters? Cc: FreeBSD Questions Cc: FreeBSD Questions , FreeBSD SCSI Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 28-Dec-97 Donald Burr wrote: >I'd like to get a new PCI SCSI adapter. I've heard good things about the >NCR/SymBIOS ones, and would like to obtain one. I don't have any Ultra or >Wide devices, so I don't need an adapter with all the bells and whistles. >(all I'll be driving is a CD-ROM and a Jaz drive) Where's the cheapest I >can get these (either a store or mail-order outfit), and how much should I >expect to pay? Please respond by email to . Thanks! Go ahead and get the Ultra-Wide version anyway. It'll just be a good excuse to buy devices of that type in the future. The Tekram DC-390F, NCR 53c875 based, cost me $115 from 5-O'Clock Computers (www.5oclock.com) plus shipping. I am VERY happy with this controller, as it was very simple to set up (full in-BIOS setup routines). --- Chris Dillon --- cdillon@tri-lakes.net --- Powered by FreeBSD, the best operating system on the planet for Intel x86 based computers. ---- (http://www.freebsd.org) From owner-freebsd-scsi Mon Dec 29 00:26:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA17991 for freebsd-scsi-outgoing; Mon, 29 Dec 1997 00:26:08 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from revolution.3-cities.com (root@revolution.3-cities.com [204.203.224.155]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA17979 for ; Mon, 29 Dec 1997 00:26:03 -0800 (PST) (envelope-from msmith@3-cities.com) Received: from mark (bigtca710.3-cities.com [204.203.232.43]) by revolution.3-cities.com (8.8.5/8.7.3) with SMTP id AAA29662 for ; Mon, 29 Dec 1997 00:20:58 -0800 (PST) Message-ID: <34A75A25.46BD@3-cities.com> Date: Mon, 29 Dec 1997 00:07:01 -0800 From: Mark Smith Reply-To: msmith@3-cities.com Organization: Organization? What's that?!? X-Mailer: Mozilla 3.03Gold (Win95; U) MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: Re: DAT question/problem! References: <34A3530D.590@3-cities.com> <19971226162002.29967@uriah.heep.sax.de> <34A49B87.6C60@3-cities.com> <19971227092711.09423@uriah.heep.sax.de> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > This is REAL fun testing this kind of code on a 90m tape on an > > older DDS-1 10M/min drive! 200 minutes (3 hours 20 min) write > > then the same for a read. > > Ain't a new cassette cheaper than 6 hours of work? ;-) Well, when I have access to about a dozen DDS-1 DAT drives, I'll just slap a tape in each one, kick of the verify in the morning and do it again before I go home. A grand total of 15 minutes actual work. Mark From owner-freebsd-scsi Mon Dec 29 14:15:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA16319 for freebsd-scsi-outgoing; Mon, 29 Dec 1997 14:15:03 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from base486.home.org (imdave@imdave.pr.mcs.net [205.164.3.77]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA16306 for ; Mon, 29 Dec 1997 14:14:46 -0800 (PST) (envelope-from imdave@mcs.net) Received: (from imdave@localhost) by base486.home.org (8.8.8/8.8.8) id QAA05496 for freebsd-scsi@freebsd.org; Mon, 29 Dec 1997 16:14:41 -0600 (CST) Date: Mon, 29 Dec 1997 16:14:41 -0600 (CST) From: Dave Bodenstab Message-Id: <199712292214.QAA05496@base486.home.org> To: freebsd-scsi@freebsd.org Subject: Is there any support for this card? Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk A while ago I posted this on freebsd-questions and got no response. I'm wondering if this card is supported any longer, and if so, what further steps I can take to try to get it working. Thanks. Dave Bodenstab imdave@mcs.net ==== To: questions@FreeBSD.org Subject: nca SCSI driver problems I've got a Trantor SCSI controller -- which is supposed to be supported -- but I can't get it working on FreeBSD 2.2.5. The card came with a ``NEC SCSI interface'' booklet. I see three chips on the board: the bios, a motorola chip, and one marked: TRANTOR T101 S9406AJ (c) NSC 1992 The only device I have attached is a NEC external CDROM. It works from dos, and it seemed to probe fine from FreeBSD. However as soon as I try to mount a cdrom, I get a kernel panic. It appears that the panic is due to the initialization code in the driver failing to undo something -- it leaves the driver in a partially configured state -- so the panic isn't the crucial problem. Before I go further, here are the kernel config lines and the boot probe messages: controller nca0 at isa? port 0x360 bio irq 10 vector ncaintr device cd0 at scbus0 target 1 device sd0 device st0 Nov 16 23:53:29 base586 /kernel: nca0 at 0x360-0x36f irq 10 on isa Nov 16 23:53:29 base586 /kernel: nca0: type NCR-53C400 Nov 16 23:53:29 base586 /kernel: (nca0:1:0): "NEC CD-ROM DRIVE:501 2.0" type 5 removable SCSI 2 Nov 16 23:53:29 base586 /kernel: cd0(nca0:1:0): CD-ROM cd present [36059 x 2048 byte records] With a ``mount -t cd9660 /dev/cd0a /mnt'', I get: Nov 17 00:03:23 base586 /kernel: nca0/1/0 (cd0) timed out and then a panic (page not present). Next, I compiled the driver with DEBUG enabled, and then got this on the boot: Nov 20 00:53:29 base586 /kernel.nca: nca: invalid bsr[0x365]=ff Nov 20 00:53:29 base586 /kernel.nca: nca0 at 0x360-0x36f irq 10 on isa Nov 20 00:53:29 base586 /kernel.nca: nca0: type NCR-53C400 Nov 20 00:53:29 base586 /kernel.nca: nca0/0/0 target does not respond Nov 20 00:53:29 base586 last message repeated 3 times Nov 20 00:53:29 base586 /kernel.nca: nca0 send command (6 bytes) -0-0-0-0-0-0 Nov 20 00:53:30 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x2 Nov 20 00:53:30 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Nov 20 00:53:30 base586 /kernel.nca: nca0 send command (6 bytes) -3-0-0-0-20-0 Nov 20 00:53:30 base586 /kernel.nca: nca (DATAIN) got 18 bytes Nov 20 00:53:30 base586 /kernel.nca: nca0 sense 70-0-6-0-0-0-0-a Nov 20 00:53:30 base586 /kernel.nca: nca0 send command (6 bytes) -12-0-0-0-2c-0 Nov 20 00:53:30 base586 /kernel.nca: nca (DATAIN) got 36 bytes Nov 20 00:53:30 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Nov 20 00:53:30 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Nov 20 00:53:30 base586 /kernel.nca: (nca0:1:0): "NEC CD-ROM DRIVE:501 2.0" type 5 removable SCSI 2 Nov 20 00:53:30 base586 /kernel.nca: cd0(nca0:1:0): CD-ROM nca0 send command (10 bytes) -25-0-0-0-0-0-0-0-0-0 Nov 20 00:53:30 base586 /kernel.nca: nca (DATAIN) got 8 bytes Nov 20 00:53:30 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Nov 20 00:53:30 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Nov 20 00:53:30 base586 /kernel.nca: cd present [36059 x 2048 byte records] Nov 20 00:53:30 base586 /kernel.nca: nca0/2/0 target does not respond Nov 20 00:53:30 base586 last message repeated 3 times Nov 20 00:53:30 base586 /kernel.nca: nca0/3/0 target does not respond Nov 20 00:53:30 base586 last message repeated 3 times Nov 20 00:53:30 base586 /kernel.nca: nca0/4/0 target does not respond Nov 20 00:53:30 base586 last message repeated 3 times Nov 20 00:53:30 base586 /kernel.nca: nca0/5/0 target does not respond Nov 20 00:53:31 base586 last message repeated 3 times Nov 20 00:53:31 base586 /kernel.nca: nca0/6/0 target does not respond Nov 20 00:53:31 base586 last message repeated 3 times Nov 20 00:55:10 base586 /kernel.nca: nca0 send command (6 bytes) -0-0-0-0-0-0 Nov 20 00:55:10 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Nov 20 00:55:10 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Nov 20 00:55:10 base586 /kernel.nca: nca0 send command (6 bytes) -1b-0-0-0-1-0 Nov 20 00:55:10 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x4 Nov 20 00:55:11 base586 /kernel.nca: nca0/1/0 disconnected Nov 20 00:55:11 base586 /kernel.nca: nca0/1/0 command queued Nov 20 00:55:20 base586 /kernel.nca: nca0/1/0 (cd0) timed out Nov 20 00:55:20 base586 /kernel.nca: nca0/1/0 no arbitration progress, bsr=10 csbr=7 The first message above is the first indication that things are not working. It causes nca_init() to exit -- I think -- prematurly which eventually results in the later panic. (BTW, I tried running the driver in its non-interrupt mode, but the results are the same.) I then went into the driver and hacked away... I increased timeouts, ignored error returns in nca_init() and nca_select() just to see if I could get any more info -- I figured that if it was just the initial probe that wasn't quite right, maybe things would settle down during normal operation. Well, it now looks like the driver just can't talk to this card successfully. Running the driver in interrupt mode, there are so many boot messages that dmesg can't save them all. Running the driver in poll mode, here are some log messages from my brutally hacked driver while trying the mount: Dec 21 22:04:22 base586 /kernel.nca: nca0 at 0x360-0x36f on isa Dec 21 22:04:22 base586 /kernel.nca: nca0: type NCR-53C400 Dec 21 22:04:22 base586 /kernel.nca: nca0/0/0 target does not respond Dec 21 22:04:22 base586 last message repeated 3 times Dec 21 22:04:22 base586 /kernel.nca: nca0 send command (6 bytes) -0-0-0-0-0-0 Dec 21 22:04:22 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x2 Dec 21 22:04:22 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 21 22:04:22 base586 /kernel.nca: nca0 send command (6 bytes) -3-0-0-0-20-0 Dec 21 22:04:22 base586 /kernel.nca: nca (DATAIN) got 18 bytes Dec 21 22:04:22 base586 /kernel.nca: nca0 sense 70-0-6-0-0-0-0-a Dec 21 22:04:22 base586 /kernel.nca: nca0 send command (6 bytes) -12-0-0-0-2c-0 Dec 21 22:04:22 base586 /kernel.nca: nca (DATAIN) got 36 bytes Dec 21 22:04:22 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Dec 21 22:04:22 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 21 22:04:22 base586 /kernel.nca: (nca0:1:0): "NEC CD-ROM DRIVE:501 2.0" type 5 removable SCSI 2 Dec 21 22:04:22 base586 /kernel.nca: cd0(nca0:1:0): CD-ROM nca0 send command (10 bytes) -25-0-0-0-0-0-0-0-0-0 Dec 21 22:04:22 base586 /kernel.nca: nca (DATAIN) got 8 bytes Dec 21 22:04:22 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Dec 21 22:04:22 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 21 22:04:23 base586 /kernel.nca: cd present [36059 x 2048 byte records] Dec 21 22:04:23 base586 /kernel.nca: nca0/2/0 target does not respond Dec 21 22:04:23 base586 last message repeated 3 times Dec 21 22:04:23 base586 /kernel.nca: nca0/3/0 target does not respond Dec 21 22:04:23 base586 last message repeated 3 times Dec 21 22:04:23 base586 /kernel.nca: nca0/4/0 target does not respond Dec 21 22:04:23 base586 last message repeated 3 times Dec 21 22:04:23 base586 /kernel.nca: nca0/5/0 target does not respond Dec 21 22:04:23 base586 last message repeated 3 times Dec 21 22:04:23 base586 /kernel.nca: nca0/6/0 target does not respond Dec 21 22:04:23 base586 last message repeated 3 times Dec 21 22:04:49 base586 /kernel.nca: nca0 send command (6 bytes) -0-0-0-0-0-0 Dec 21 22:04:49 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Dec 21 22:04:49 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 21 22:04:49 base586 /kernel.nca: nca0 send command (6 bytes) -1b-0-0-0-1-0 Dec 21 22:04:49 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x4 Dec 21 22:04:49 base586 /kernel.nca: nca0/1/0 disconnected Dec 21 22:04:49 base586 /kernel.nca: nca0/1/0 command queued Dec 21 22:04:50 base586 /kernel.nca: nca0 (MSG_INPUT) got 0x80 Dec 21 22:04:50 base586 /kernel.nca: nca0/1/0 reselect done Dec 21 22:04:50 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Dec 21 22:04:50 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 21 22:05:20 base586 /kernel.nca: nca0 send command (6 bytes) -0-0-0-0-0-0 Dec 21 22:05:20 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Dec 21 22:05:21 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 21 22:05:21 base586 /kernel.nca: nca0 send command (6 bytes) -1e-0-0-0-1-0 Dec 21 22:05:21 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Dec 21 22:05:21 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 21 22:05:21 base586 /kernel.nca: nca0 send command (10 bytes) -43-0-0-0-0-0-0-0-4-0 Dec 21 22:05:21 base586 /kernel.nca: nca (DATAIN) got 4 bytes Dec 21 22:05:21 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Dec 21 22:05:21 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 21 22:05:21 base586 /kernel.nca: nca0 send command (10 bytes) -43-0-0-0-0-0-0-0-4-0 Dec 21 22:05:21 base586 /kernel.nca: nca (DATAIN) got 4 bytes Dec 21 22:05:21 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Dec 21 22:05:21 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 21 22:05:21 base586 /kernel.nca: nca0 send command (10 bytes) -43-0-0-0-0-0-1-0-c-0 Dec 21 22:05:21 base586 /kernel.nca: nca (DATAIN) got 12 bytes Dec 21 22:05:21 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Dec 21 22:05:21 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 21 22:05:21 base586 /kernel.nca: nca0 send command (6 bytes) -1e-0-0-0-0-0 Dec 21 22:05:21 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Dec 21 22:05:21 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 21 22:05:21 base586 /kernel.nca: hbrdy,shintr> Dec 21 22:05:21 base586 /kernel.nca: nca (DATAIN) got 0 bytes Dec 21 22:05:21 base586 /kernel.nca: nca0: reset: pseudo-dma incomplete, csr=c Dec 21 22:05:26 base586 /kernel.nca: nca (DATAIN) got 0 bytes Dec 21 22:05:26 base586 /kernel.nca: nca0/1/0 unexpected target disconnect Dec 21 22:05:26 base586 /kernel.nca: nca0/1/0 (cd0) timed out Dec 21 22:05:26 base586 /kernel.nca: nca0/1/0 target does not respond Dec 21 22:05:26 base586 /kernel.nca: nca0/1/0 command queued Dec 21 22:05:26 base586 /kernel.nca: nca0/1/0 (cd0) timed out Dec 21 22:05:26 base586 /kernel.nca: nca0/1/0 (cd0) timed out Dec 22 01:27:45 base586 /kernel.nca: nca0 send command (6 bytes) -0-0-0-0-0-0 Dec 22 01:27:45 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x2 Dec 22 01:27:45 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 22 01:27:45 base586 /kernel.nca: nca0 send command (6 bytes) -3-0-0-0-20-0 Dec 22 01:27:45 base586 /kernel.nca: nca (DATAIN) got 18 bytes Dec 22 01:27:45 base586 /kernel.nca: nca0 sense 70-0-6-0-0-0-0-a Dec 22 01:27:45 base586 /kernel.nca: nca0 send command (6 bytes) -1b-0-0-0-1-0 Dec 22 01:27:45 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x4 Dec 22 01:27:45 base586 /kernel.nca: nca0/1/0 disconnected Dec 22 01:27:45 base586 /kernel.nca: nca0/1/0 command queued Dec 22 01:27:46 base586 /kernel.nca: nca0 (MSG_INPUT) got 0x80 Dec 22 01:27:46 base586 /kernel.nca: nca0/1/0 reselect done Dec 22 01:27:46 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Dec 22 01:27:46 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 22 01:27:46 base586 /kernel.nca: nca0 send command (6 bytes) -0-0-0-0-0-0 Dec 22 01:28:17 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Dec 22 01:28:17 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 22 01:28:17 base586 /kernel.nca: nca0 send command (6 bytes) -1e-0-0-0-1-0 Dec 22 01:28:17 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Dec 22 01:28:17 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 22 01:28:17 base586 /kernel.nca: nca0 send command (10 bytes) -25-0-0-0-0-0-0-0-0-0 Dec 22 01:28:17 base586 /kernel.nca: nca (DATAIN) got 8 bytes Dec 22 01:28:17 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Dec 22 01:28:17 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 22 01:28:17 base586 /kernel.nca: nca0 send command (10 bytes) -43-0-0-0-0-0-0-0-4-0 Dec 22 01:28:17 base586 /kernel.nca: nca (DATAIN) got 4 bytes Dec 22 01:28:17 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Dec 22 01:28:17 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 22 01:28:17 base586 /kernel.nca: nca0 send command (10 bytes) -43-0-0-0-0-0-0-0-4-0 Dec 22 01:28:17 base586 /kernel.nca: nca (DATAIN) got 4 bytes Dec 22 01:28:17 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Dec 22 01:28:17 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 22 01:28:17 base586 /kernel.nca: nca0 send command (10 bytes) -43-0-0-0-0-0-1-0-c-0 Dec 22 01:28:17 base586 /kernel.nca: nca (DATAIN) got 12 bytes Dec 22 01:28:17 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Dec 22 01:28:17 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 22 01:28:17 base586 /kernel.nca: nca0 send command (6 bytes) -1e-0-0-0-0-0 Dec 22 01:28:17 base586 /kernel.nca: nca0/1/0 (STATIN) got 0x0 Dec 22 01:28:17 base586 /kernel.nca: nca0/1/0 (MSGIN) got 0x0 Dec 22 01:28:18 base586 /kernel.nca: hbrdy,shintr> Dec 22 01:28:18 base586 /kernel.nca: nca (DATAIN) got 0 bytes Dec 22 01:28:18 base586 /kernel.nca: nca0: reset: pseudo-dma incomplete, csr=c Dec 22 01:28:22 base586 /kernel.nca: nca (DATAIN) got 0 bytes Dec 22 01:28:22 base586 /kernel.nca: nca0/1/0 unexpected target disconnect Dec 22 01:28:22 base586 /kernel.nca: nca0/1/0 (cd0) timed out Dec 22 01:28:22 base586 /kernel.nca: nca0/1/0 target does not respond Dec 22 01:28:22 base586 /kernel.nca: nca0/1/0 command queued Dec 22 01:28:22 base586 /kernel.nca: nca0/1/0 (cd0) timed out Dec 22 01:28:22 base586 /kernel.nca: nca0/1/0 (cd0) timed out I do see the ``busy'' indicator turn on on the cdrom drive, but it seems as tho the driver just can't talk to the board correctly.... So where can I go from here? Should I write a PR? Does anyone support this driver? Should I dump the card and try to find an inexpensive NCR/symbios? controller -- if so, what are they called now? From owner-freebsd-scsi Mon Dec 29 17:54:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA05087 for freebsd-scsi-outgoing; Mon, 29 Dec 1997 17:54:12 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from m-net.arbornet.org (root@m-net.arbornet.org [209.142.209.161]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA05069; Mon, 29 Dec 1997 17:54:06 -0800 (PST) (envelope-from kb8rjy@m-net.arbornet.org) Received: from localhost (kb8rjy@localhost) by m-net.arbornet.org (8.8.5/8.8.6) with SMTP id UAA12685; Mon, 29 Dec 1997 20:48:37 -0500 (EST) Date: Mon, 29 Dec 1997 20:48:36 -0500 (EST) From: "Shaun Q." To: Bernard.Steiner@de.uu.net cc: freebsd-hardware@FreeBSD.ORG, matt@nmedia.net, ppbus@smith.net.au, freebsd-scsi@FreeBSD.ORG, Nicolas.Souchu@prism.uvsq.fr Subject: Re: zip drive problems In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Well, I just spent 2 and a half hours on the phone with Iomega, and found out that they have changed the ROM chip in the parallel zip. I'm working on getting the correct specifications for the new chip but I'm having problems finding anyone who knows what they are talking about. If anyone finds a solution for this problem I would be incredibly grateful. Thanks Shaun Q. kb8rjy@arbornet.org BTW, does anyone feel like paying my phone bill for that call? :) j/k From owner-freebsd-scsi Mon Dec 29 19:43:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA14563 for freebsd-scsi-outgoing; Mon, 29 Dec 1997 19:43:26 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from colossus.dyn.ml.org (root@199-170-160-104.la.inreach.net [199.107.160.104]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA14513; Mon, 29 Dec 1997 19:43:13 -0800 (PST) (envelope-from dburr@POBoxes.com) Received: from control.colossus.dyn.ml.org (dburr@control.colossus.dyn.ml.org [192.160.60.1]) by colossus.dyn.ml.org (8.8.7/8.8.7) with SMTP id TAA08522; Mon, 29 Dec 1997 19:47:51 -0800 (PST) (envelope-from dburr@POBoxes.com) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Mon, 29 Dec 1997 19:45:10 -0800 (PST) Organization: Starfleet Command From: Donald Burr To: "Shaun Q." Subject: Re: zip drive problems Cc: Nicolas.Souchu@prism.uvsq.fr, freebsd-scsi@FreeBSD.ORG, ppbus@smith.net.au, matt@nmedia.net, freebsd-hardware@FreeBSD.ORG, Bernard.Steiner@de.uu.net Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk -----BEGIN PGP SIGNED MESSAGE----- My secret spy satellite informs me that on 30-Dec-97, Shaun Q. wrote: >Well, I just spent 2 and a half hours on the phone with Iomega, and found >out that they have changed the ROM chip in the parallel zip. I'm working >on getting the correct specifications for the new chip but I'm having >problems finding anyone who knows what they are talking about. > > >If anyone finds a solution for this problem I would be incredibly >grateful. You might want to talk to Grant , or view his Linux Parallel Port homepage . He handles all of the parallel port type hardware for Linux, and in fact did the Linux driver for the Zip drive. He may have the current information you are seeking, or be able to help you out otherwise. - --- Donald Burr - Ask me for my PGP key | PGP: Your WWW HomePage: http://DonaldBurr.base.org/ ICQ #1347455 | right to Address: P.O. Box 91212, Santa Barbara, CA 93190-1212 | 'Net privacy. Phone: (805) 957-9666 FAX: (800) 492-5954 | USE IT. -----BEGIN PGP SIGNATURE----- Version: 2.6.2 iQCVAwUBNKhu5PjpixuAwagxAQF80gP/Ygjn/fdN7Do0J4zHO5yH0Y0/fLvBiWUp plXDeMBgCDHlt/Z2D59bKkC3d1JvV0j5jPUm8NAc0+7kiLB6UOE6E1sQzyFhmFpD Jb6Xice7EG8yKK3OkCr/Ll4bL/vwPF/Dkc0rd+a/juCMNx/SOHNKGaAwkU54ekDu BW3sVy2n3NI= =YC9q -----END PGP SIGNATURE----- From owner-freebsd-scsi Mon Dec 29 20:24:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA18065 for freebsd-scsi-outgoing; Mon, 29 Dec 1997 20:24:39 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from word.smith.net.au (vh1.gsoft.com.au [203.38.152.122]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA18047; Mon, 29 Dec 1997 20:24:32 -0800 (PST) (envelope-from mike@word.smith.net.au) Received: from word (localhost [127.0.0.1]) by word.smith.net.au (8.8.8/8.8.5) with ESMTP id OAA00295; Tue, 30 Dec 1997 14:48:16 +1030 (CST) Message-Id: <199712300418.OAA00295@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Shaun Q." cc: Bernard.Steiner@de.uu.net, freebsd-hardware@FreeBSD.ORG, matt@nmedia.net, ppbus@smith.net.au, freebsd-scsi@FreeBSD.ORG, Nicolas.Souchu@prism.uvsq.fr Subject: Re: zip drive problems In-reply-to: Your message of "Mon, 29 Dec 1997 20:48:36 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Dec 1997 14:48:16 +1030 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Well, I just spent 2 and a half hours on the phone with Iomega, and found > out that they have changed the ROM chip in the parallel zip. I'm working > on getting the correct specifications for the new chip but I'm having > problems finding anyone who knows what they are talking about. Changing the ROM itself shouldn't cause any problems. It sounds though as if they have changed a great deal more than just the ROM. > If anyone finds a solution for this problem I would be incredibly > grateful. Indeed. If you *do* have any luck with this, please let us know! -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ Remember, the race is long, \\ msmith@freebsd.org \\ and in the end it's only with yourself. \\ From owner-freebsd-scsi Tue Dec 30 14:29:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA02899 for freebsd-scsi-outgoing; Tue, 30 Dec 1997 14:29:23 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from mail.netcetera.dk (root@sleipner.netcetera.dk [194.192.207.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA02874 for ; Tue, 30 Dec 1997 14:29:16 -0800 (PST) (envelope-from leifn@image.dk) Received: (from uucp@localhost) by mail.netcetera.dk (8.8.8/8.8.8) with UUCP id XAA12997 for freebsd-scsi@freebsd.org; Tue, 30 Dec 1997 23:24:35 +0100 Received: by swimsuit.swimsuit.roskildebc.dk (0.99.970109) id AA08184; 30 Dec 97 23:25:01 +0100 From: leifn@image.dk (Leif Neland) Date: 30 Dec 97 22:42:18 +0100 Subject: Re: zip drive problems Message-ID: <77b_9712302325@swimsuit.swimsuit.roskildebc.dk> Organization: Fidonet: UNIX-sysadm søger job To: freebsd-scsi@freebsd.org Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 30 Dec 97 05:18:16 Mike Smith wrote regarding Re: zip drive problems MS> Changing the ROM itself shouldn't cause any problems. It sounds MS> though as if they have changed a great deal more than just the MS> ROM. Yes, they probably changed the contents of the ROM too. :-) Surely a change in the firmware in the zip-drive could require changes in the driver on fbsd. Leif Neland leifn@image.dk --- |Fidonet: Leif Neland 2:234/49 |Internet: leifn@image.dk From owner-freebsd-scsi Tue Dec 30 15:23:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA06690 for freebsd-scsi-outgoing; Tue, 30 Dec 1997 15:23:56 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA06684 for ; Tue, 30 Dec 1997 15:23:51 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id SAA13288 for ; Tue, 30 Dec 1997 18:23:22 -0500 (EST) Date: Tue, 30 Dec 1997 18:23:22 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: FreeBSD-SCSI@freebsd.org Subject: odd 875 problem Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm scratching my head on this one .... Here's the scenario ... Tyan Tomcat I, Pentium/166 with 32M, Asus 875 controller. Installed FreeBSD on the 2 each 2G Fujitsum drives on the wide connector, no problem. Needed Win95 for a project, so took a borrowed narrow 2 G drive, address 0 on the narrow connector, and put Win95 on it. Again, no problem yet. At the end of the install, I booted Win95 via floppy, and used the driver disks that came with the Asus 875 controller to put the right drivers into Win 95. At the end of the 875 disk setup procedure, I used the offered option to reboot the system. That was the last it worked. During the 875 boot, at the end of the SCAM protocol, the 875 BIOS always printed a banner that gave the drive info, but it flashed up on screen for less than a second, so I could never read it. Note that printing this banner is the last thing the system did before accessing the disks or floppies for boot. Well, I can read it now, because the controller hangs at this point with the red LED on the card burning solid. I have on this thing 2 drives on the wide connector, and a cdrom and a drive on the narrow connector, and none of the drive access lights come on. I have tried all different combinations of drives (just the wide connector, just the narrow one, just the wide with one drive only, etc, etc) and the failure mode doesn't change. The only way the 875 gets past the SCAM protocol still living is if there is no connector (wide or narrow) installed at all. Doesn't even get to the floppy. BTW, that banner that the 875 hangs just after printing? It's been completely correct, no matter how I change the drives. What makes this more confusing is, I have a 825 here, and it works ok on that machine. I've tried swapping the 875 for a different one, the trouble stays the same. I've tried zeroing out the cmos memory, no change. I've tried all different combinations of use for the two PCI slots (one video, one the 875) no change. The Tyan MB's onboard IDEs are disabled. Anyone got any silly suggestions as to what I could try next? ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-scsi Tue Dec 30 17:09:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA14544 for freebsd-scsi-outgoing; Tue, 30 Dec 1997 17:09:13 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from Chicago (mail.chicagonet.net [207.252.246.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA14538 for ; Tue, 30 Dec 1997 17:09:00 -0800 (PST) (envelope-from reptco@chicagonet.net) From: reptco@chicagonet.net Received: from mail.chicagonet.net ([207.252.247.243]) by Chicago with SMTP (IPAD 2.0) id 8181100 ; Tue, 30 Dec 1997 18:37:37 EST To: scsi@freebsd.org Priority: Normal X-Mailer: Post Road Mailer for OS/2 (Green Edition Ver 3.0) Date: Tue, 30 Dec 1997 18:43:30 CST Reply-To: Wayne Berryman Subject: BSD Tape Drive Drivers??? Message-Id: <199712302337.8181100@Chicago> Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In trying to install FreeBSD 2.2.5, I kept getting this ach0 error. I thought it was the actual Adaptec card it didn't like. Turns out it doesn't like my SCSI tape drive. If I take the tape drive off BSD installs fine. Now that I have FreeBSD on my system, I put the tape drive back on. I run into the same problem I had as installing when with the SCSI tape drive attached. I need to find a driver for SCSI Tape drive for FreeBSD that will work with my Seagate Tapestore drive (most software recognizes it as a CTT8000-S drive). Has anyone else had this problem? Has anyone found a driver that will work? Does anyone have any ideas on where I can get this driver, and documentation on how to install a driver for a device after I have BSD installed on my system? Thanks in advance!! Wayne reptco@chicagonet.net From owner-freebsd-scsi Tue Dec 30 17:22:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA15793 for freebsd-scsi-outgoing; Tue, 30 Dec 1997 17:22:38 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA15768 for ; Tue, 30 Dec 1997 17:22:27 -0800 (PST) (envelope-from dkelly@nospam.hiwaay.net) Received: from nospam.hiwaay.net (max7-233.HiWAAY.net [208.147.145.233]) by fly.HiWAAY.net (8.8.8/8.8.6) with ESMTP id TAA16319; Tue, 30 Dec 1997 19:22:19 -0600 (CST) Received: from localhost (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.8/8.8.4) with ESMTP id TAA10564; Tue, 30 Dec 1997 19:22:15 -0600 (CST) Message-Id: <199712310122.TAA10564@nospam.hiwaay.net> X-Mailer: exmh version 2.0zeta 7/24/97 To: Chuck Robey cc: FreeBSD-SCSI@freebsd.org From: David Kelly Subject: Re: odd 875 problem In-reply-to: Message from Chuck Robey of "Tue, 30 Dec 1997 18:23:22 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 30 Dec 1997 19:22:15 -0600 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Chuck Robey writes: > Well, I can read it now, because the controller hangs > at this point with the red LED on the card burning solid. Well, at least we know the LED is supposed to work. The other day when I decided to try overclocking my PPro I got really radical and thought to hook an external LED to my Asus SC-875. First I noticed the LED on the card did work. Neither did an external LED. Duh. Can't see its worth my effort to bother returning the card under warranty. Sorry I'm not more help. But thought you'd like to know your LED works better than mine. :-) -- David Kelly N4HHE, dkelly@nospam.hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. From owner-freebsd-scsi Tue Dec 30 17:51:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA18234 for freebsd-scsi-outgoing; Tue, 30 Dec 1997 17:51:00 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from picnic.mat.net (picnic.mat.net [206.246.122.117]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA18211 for ; Tue, 30 Dec 1997 17:50:52 -0800 (PST) (envelope-from chuckr@glue.umd.edu) Received: from localhost (chuckr@localhost) by picnic.mat.net (8.8.8/8.8.5) with SMTP id UAA14021; Tue, 30 Dec 1997 20:38:14 -0500 (EST) Date: Tue, 30 Dec 1997 20:38:14 -0500 (EST) From: Chuck Robey X-Sender: chuckr@localhost To: David Kelly cc: FreeBSD-SCSI@freebsd.org Subject: Re: odd 875 problem In-Reply-To: <199712310122.TAA10564@nospam.hiwaay.net> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 30 Dec 1997, David Kelly wrote: > Chuck Robey writes: > > > Well, I can read it now, because the controller hangs > > at this point with the red LED on the card burning solid. > > Well, at least we know the LED is supposed to work. The other day when I > decided to try overclocking my PPro I got really radical and thought to > hook an external LED to my Asus SC-875. First I noticed the LED on the > card did work. Neither did an external LED. Duh. Can't see its worth my > effort to bother returning the card under warranty. > > Sorry I'm not more help. But thought you'd like to know your LED works > better than mine. :-) On my other, SMP machine, the 875 there, with the external LED connected, works just fine. If you get any wild ideas, tho, remember me. > > -- > David Kelly N4HHE, dkelly@nospam.hiwaay.net > ===================================================================== > The human mind ordinarily operates at only ten percent of its > capacity -- the rest is overhead for the operating system. > > > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@glue.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-scsi Tue Dec 30 18:34:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA21134 for freebsd-scsi-outgoing; Tue, 30 Dec 1997 18:34:45 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA21121 for ; Tue, 30 Dec 1997 18:34:36 -0800 (PST) (envelope-from grog@lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.8.7/8.8.5) with ESMTP id NAA13278; Wed, 31 Dec 1997 13:04:26 +1030 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.8.8/8.8.7) id NAA15812; Wed, 31 Dec 1997 13:04:25 +1030 (CST) (envelope-from grog) Message-ID: <19971231130425.44774@lemis.com> Date: Wed, 31 Dec 1997 13:04:25 +1030 From: Greg Lehey To: Wayne Berryman Cc: scsi@FreeBSD.ORG Subject: Re: BSD Tape Drive Drivers??? References: <199712302337.8181100@Chicago> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.84e In-Reply-To: <199712302337.8181100@Chicago>; from reptco@chicagonet.net on Tue, Dec 30, 1997 at 06:43:30PM -0600 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, Dec 30, 1997 at 06:43:30PM -0600, reptco@chicagonet.net wrote: Please limit your message width to less than 80 characters. Many people have difficulty reading wider lines. I've reformatted your text to fit. > In trying to install FreeBSD 2.2.5, I kept getting this ach0 error. If you get an error message, please reproduce it. I don't know "this ach0 error". ach0 sounds like a device name, but we don't have a device with that name. Could it be that you have an Adaptec 2940 (which uses the ahc0 driver)? In any case, this is just the device reporting the error. You've omitted everything that can give us information about what the error is. > I thought it was the actual Adaptec card it didn't like. Turns out > it doesn't like my SCSI tape drive. If I take the tape drive off > BSD installs fine. Now that I have FreeBSD on my system, I put the > tape drive back on. I run into the same problem I had as installing > when with the SCSI tape drive attached. > I need to find a driver for SCSI Tape drive for FreeBSD that will > work with my Seagate Tapestore drive (most software recognizes it as > a CTT8000-S drive). There's only one driver for the Adaptec 2940/3940 series. > Has anyone else had this problem? I can't even guess. > Has anyone found a driver that will work? Sure. It's part of the kernel. Since you have your disk working, it appears to be running. > Does anyone have any ideas on where I can get this driver, and > documentation on how to install a driver for a device after I have > BSD installed on my system? It's on your system. I suppose I'm being a little hard on you. Your approach to this problem is pretty typical of people who come from a Microsoft background, where you don't have proper debug tools, and where the system itself isn't complete and requires drivers from other sources. FreeBSD has neither of these problems. The first debug tool is the error message. It may look like gibberish to you, but it tells us what the problem is. It could be as simple as an incorrect device ID. The other feature of FreeBSD is that it already contains the drivers you need, so you don't have to go worrying about finding other ones. Here's what to do: reconnect the tape drive, try to boot, and write down the exact text of the error message. Send it to me, and we'll be a whole lot further. Greg From owner-freebsd-scsi Tue Dec 30 23:55:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA10342 for freebsd-scsi-outgoing; Tue, 30 Dec 1997 23:55:23 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from m-net.arbornet.org (root@m-net.arbornet.org [209.142.209.161]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA10334 for ; Tue, 30 Dec 1997 23:55:17 -0800 (PST) (envelope-from kb8rjy@m-net.arbornet.org) Received: from localhost (kb8rjy@localhost) by m-net.arbornet.org (8.8.5/8.8.6) with SMTP id AAA14087; Wed, 31 Dec 1997 00:01:50 -0500 (EST) Date: Wed, 31 Dec 1997 00:01:50 -0500 (EST) From: "Shaun Q." To: Leif Neland cc: freebsd-scsi@freebsd.org Subject: Re: zip drive problems In-Reply-To: <77b_9712302325@swimsuit.swimsuit.roskildebc.dk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk To clarify the subject: I was on the phone with Iomega last night and they have admitted that they changed the ROM on the latest zip (the rom version seems to be J.03) I don't know if anything else was changed, but the rom was definately changed. Anyone come up with anything yet? Thanks! Shaun q. On 30 Dec 1997, Leif Neland wrote: > At 30 Dec 97 05:18:16 Mike Smith wrote regarding Re: zip drive problems > > MS> Changing the ROM itself shouldn't cause any problems. It sounds > MS> though as if they have changed a great deal more than just the > MS> ROM. > > Yes, they probably changed the contents of the ROM too. :-) > > Surely a change in the firmware in the zip-drive could require changes in the > driver on fbsd. > > > Leif Neland > leifn@image.dk > > --- > |Fidonet: Leif Neland 2:234/49 > |Internet: leifn@image.dk > From owner-freebsd-scsi Wed Dec 31 00:51:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id AAA12653 for freebsd-scsi-outgoing; Wed, 31 Dec 1997 00:51:40 -0800 (PST) (envelope-from owner-freebsd-scsi) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id AAA12648 for ; Wed, 31 Dec 1997 00:51:35 -0800 (PST) (envelope-from j@uriah.heep.sax.de) Received: (from uucp@localhost) by sax.sax.de (8.8.8/8.8.8) with UUCP id JAA09886; Wed, 31 Dec 1997 09:51:26 +0100 (CET) (envelope-from j@uriah.heep.sax.de) Received: (from j@localhost) by uriah.heep.sax.de (8.8.8/8.8.5) id JAA08967; Wed, 31 Dec 1997 09:45:21 +0100 (MET) Message-ID: <19971231094521.28847@uriah.heep.sax.de> Date: Wed, 31 Dec 1997 09:45:21 +0100 From: J Wunsch To: scsi@FreeBSD.ORG Cc: Wayne Berryman Subject: Re: BSD Tape Drive Drivers??? Reply-To: Joerg Wunsch References: <199712302337.8181100@Chicago> <19971231130425.44774@lemis.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88 In-Reply-To: <19971231130425.44774@lemis.com>; from Greg Lehey on Wed, Dec 31, 1997 at 01:04:25PM +1030 X-Phone: +49-351-2012 669 X-PGP-Fingerprint: DC 47 E6 E4 FF A6 E9 8F 93 21 E0 7D F9 12 D6 4E Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Greg Lehey wrote: > > I need to find a driver for SCSI Tape drive for FreeBSD that will > > work with my Seagate Tapestore drive (most software recognizes it as > > a CTT8000-S drive). > > There's only one driver for the Adaptec 2940/3940 series. > > > Has anyone else had this problem? > > I can't even guess. Then you didn't follow this list very closely, Greg. ;-) These drives aren't really SCSI, despite of their 50-pin connector looking like SCSI. They violate the SCSI-2 specs. The violation might be benign for you or not, but we've had several cases here. The last i can remember is that it rejects the WRITE FILEMARKS command which is mandatory per the standard. > > Has anyone found a driver that will work? > > Sure. It's part of the kernel. Well, he's talking about the st(4) driver, most likely. Anyway, without seeing the exact SCSI error message, it's indeed hard to guess. -- cheers, J"org joerg_wunsch@uriah.heep.sax.de -- http://www.sax.de/~joerg/ -- NIC: JW11-RIPE Never trust an operating system you don't have sources for. ;-)