From owner-freebsd-scsi Sun May 25 00:56:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA13896 for freebsd-scsi-outgoing; Sun, 25 May 1997 00:56:09 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca9-14.ix.netcom.com [207.93.143.78]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA13880; Sun, 25 May 1997 00:56:04 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id AAA11668; Sun, 25 May 1997 00:55:50 -0700 (PDT) Date: Sun, 25 May 1997 00:55:50 -0700 (PDT) Message-Id: <199705250755.AAA11668@silvia.HIP.Berkeley.EDU> To: albast@magigimmix.xs4all.nl CC: Questions@FreeBSD.org, SCSI@FreeBSD.org, ISP@FreeBSD.org, jh@Twiddle.COM In-reply-to: <199705242342.BAA20385@smtp1.xs4all.nl> (albast@magigimmix.xs4all.nl) Subject: Re: Some advice needed From: asami@FreeBSD.org (Satoshi Asami) Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk * I have a question regarding some server setup; * I'm planning to use the Adaptec AHA-3940UW PCI adapter in combination * with two Quantum AtlasII QM34550ALSW 4.5 GB UW SCSI-3 harddisks. 3940UW and Atlas-II is a great combination. Just one thing you need to be careful, make sure you get the LXY4 firmware of the AII. You won't be able to find firmware upgrades if you gut LXQ1 or LXY1 (the only firmware upgrades found on ftp.quantum.com are for narrow AIIs). If you get LXQ1 like me, expect data losses and other unpleasant consequences under heavy load. (I called Quantum tech support, they said they'll let a technician call me but they never did....) Satoshi From owner-freebsd-scsi Sun May 25 18:59:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA21486 for freebsd-scsi-outgoing; Sun, 25 May 1997 18:59:39 -0700 (PDT) Received: from cicerone.uunet.ca (cicerone.uunet.ca [142.77.1.11]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA21477 for ; Sun, 25 May 1997 18:59:34 -0700 (PDT) Received: from why.whine.com ([205.150.249.1]) by mail.uunet.ca with ESMTP id <115296-16811>; Sun, 25 May 1997 21:57:26 -0400 Received: from why (why [205.150.249.1]) by why.whine.com (8.8.5/8.7.3) with SMTP id VAA02457; Sun, 25 May 1997 21:57:18 -0400 (EDT) Date: Sun, 25 May 1997 21:57:17 -0400 From: Andrew Herdman X-Sender: andrew@why To: Joerg Wunsch cc: scsi@FreeBSD.ORG, Andrew Herdman Subject: Re: Oddness with NCR53C810 In-Reply-To: <19970524102943.GO37893@uriah.heep.sax.de> 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 Sat, 24 May 1997, J Wunsch wrote: > As Andrew Herdman wrote: > > > ncr0 rev 17 int a irq 12 on pci0:11:0 > > ncr0 waiting for scsi devices to settle > > scbus1 at ncr0 bus 0 > > ^^^^^ > > This is it... it stops here. > > Do you have scbus1 hardwired to ncr0 in your kernel? > > ncr0 rev 18 int a irq 12 on pci0:9:0 > scbus0 at ncr0 bus 0 > ... > ncr1 rev 2 int a irq 11 on pci0:12:0 > scbus1 at ncr1 bus 0 Yes, this is the relevant kernel config: controller bt0 controller ncr0 controller scbus0 at bt0 controller scbus1 at ncr0 > Mine are working. scbus1 used to be on an AHA2940 until i had to free > up the Adaptec for other purposes. Interesting, i never noticed i've > got two different NCRs until now. :) > > Maybe boot -v would show you some more messages. Boot -v does show more information, but the hang still happens at the exact same spot. Thanks Andrew From owner-freebsd-scsi Sun May 25 20:56:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA25451 for freebsd-scsi-outgoing; Sun, 25 May 1997 20:56:28 -0700 (PDT) Received: from r74h25.res.gatech.edu (ken@r74h25.res.gatech.edu [128.61.74.25]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA25419; Sun, 25 May 1997 20:56:17 -0700 (PDT) Received: (from ken@localhost) by r74h25.res.gatech.edu (8.8.5/8.8.5) id XAA28280; Sun, 25 May 1997 23:56:03 -0400 (EDT) From: "Kenneth D. Merry" Message-Id: <199705260356.XAA28280@r74h25.res.gatech.edu> Subject: Re: Some advice needed In-Reply-To: <199705250755.AAA11668@silvia.HIP.Berkeley.EDU> from Satoshi Asami at "May 25, 97 00:55:50 am" To: asami@FreeBSD.ORG (Satoshi Asami) Date: Sun, 25 May 1997 23:56:03 -0400 (EDT) Cc: albast@magigimmix.xs4all.nl, Questions@FreeBSD.ORG, SCSI@FreeBSD.ORG, ISP@FreeBSD.ORG, jh@Twiddle.COM X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Satoshi Asami wrote: > * I have a question regarding some server setup; > * I'm planning to use the Adaptec AHA-3940UW PCI adapter in combination > * with two Quantum AtlasII QM34550ALSW 4.5 GB UW SCSI-3 harddisks. > 3940UW and Atlas-II is a great combination. Just one thing you need to > be careful, make sure you get the LXY4 firmware of the AII. You > won't be able to find firmware upgrades if you gut LXQ1 or LXY1 (the > only firmware upgrades found on ftp.quantum.com are for narrow AIIs). > If you get LXQ1 like me, expect data losses and other unpleasant > consequences under heavy load. Really? I loaded the LXY4 firmware upgrade on my ultra-wide 4G Atlas II, and it's working fine. (I believe I used Dagnlxy4.fup) I started out with LXQ1 firmware. old dmesg: (ahc0:0:0): "QUANTUM XP34550W LXQ1" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 4341MB (8890760 512 byte sectors) new dmesg: sd0 at scbus0 target 0 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 4341MB (8890760 512 byte sectors) Ken -- Kenneth Merry ken@r74h25.res.gatech.edu Disclaimer: I don't speak for GTRI, GT, or Elvis. From owner-freebsd-scsi Mon May 26 04:30:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA12743 for freebsd-scsi-outgoing; Mon, 26 May 1997 04:30:35 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA12733 for ; Mon, 26 May 1997 04:30:28 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-6.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA01856 (5.67b/IDA-1.5 for ); Mon, 26 May 1997 13:30:16 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id NAA14841; Mon, 26 May 1997 13:30:09 +0200 (CEST) X-Face: " Date: Mon, 26 May 1997 13:30:09 +0200 From: Stefan Esser To: Andrew Herdman Cc: Joerg Wunsch , scsi@FreeBSD.ORG Subject: Re: Oddness with NCR53C810 References: <19970524102943.GO37893@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.73 In-Reply-To: ; from Andrew Herdman on Sun, May 25, 1997 at 09:57:17PM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 25, Andrew Herdman wrote: > On Sat, 24 May 1997, J Wunsch wrote: > > > As Andrew Herdman wrote: > > > > > ncr0 rev 17 int a irq 12 on pci0:11:0 > > > ncr0 waiting for scsi devices to settle > > > scbus1 at ncr0 bus 0 > > > ^^^^^ > > > This is it... it stops here. > > > > Do you have scbus1 hardwired to ncr0 in your kernel? > > > > ncr0 rev 18 int a irq 12 on pci0:9:0 > > scbus0 at ncr0 bus 0 > > ... > > ncr1 rev 2 int a irq 11 on pci0:12:0 > > scbus1 at ncr1 bus 0 > > Yes, this is the relevant kernel config: > > controller bt0 > controller ncr0 > controller scbus0 at bt0 > controller scbus1 at ncr0 I guess the SCSI code somewhere assumes that scbus0 is probed before scbus1, and because of the wired names, this assumption may not hold for your system. You could try exchanging the NCR and BusLogic cards, this could make a difference. I do not expect the NCR driver to be the culprit, but will look into this later (don't have the time right now, sorry). Regards, STefan From owner-freebsd-scsi Mon May 26 04:43:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA13147 for freebsd-scsi-outgoing; Mon, 26 May 1997 04:43:08 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA13141 for ; Mon, 26 May 1997 04:43:05 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-16.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA02470 (5.67b/IDA-1.5 for ); Mon, 26 May 1997 13:43:00 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id NAA14882; Mon, 26 May 1997 13:42:12 +0200 (CEST) X-Face: " Date: Mon, 26 May 1997 13:42:12 +0200 From: Stefan Esser To: Ollivier Robert Cc: scsi@FreeBSD.ORG Subject: Re: Oddness with NCR53C810 References: <19970524102943.GO37893@uriah.heep.sax.de> <19970524124625.07596@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.73 In-Reply-To: <19970524124625.07596@keltia.freenix.fr>; from Ollivier Robert on Sat, May 24, 1997 at 12:46:25PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > The NCR810a is an Ultra-capable version of the NCR810 I think. No, sorry, not quite :) The NCR/Symbios SCSI chips are: 810 the original, 8bit, FAST 810a improved version of the 810, more efficent on the PCI bus 815 810 with BIOS support 860 810a with Ultra-SCSI support 820 810 with support for WIDE SCSI 825 improved 820 with BIOS support 825a improved 825 with on-chip 4KB RAM 875 825a with Ultra-SCSI support 876 dual 875 895 875 with Ultra-2 support (40MHz sync. + LVD) There are quite a number of cards with WIDE SCSI chips, but only an 8bit bus (the Symbios Sym8250S or Sym8750S and the Tekram DC-390U, for example). Only very few WIDE NCR cards support differential bus signals (the Sym8250D and Sym8751D do). The Sym53c876 allows to put two Ultra-WIDE SCSI channels on one PCI card, without the need for a PCI to PCI bridge. This is better than an Adaptec 3940 with two SCSI chips behind a PPB, since it is cheaper and avoids the latency and complexity introduced by the PPB ... Regards, STefan From owner-freebsd-scsi Mon May 26 08:47:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA24832 for freebsd-scsi-outgoing; Mon, 26 May 1997 08:47:37 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA24818; Mon, 26 May 1997 08:47:22 -0700 (PDT) Received: from shasta.altavista-software.com (Cust101.Max3.Boston.MA.MS.UU.NET [153.35.70.229]) by mail.cdsnet.net (8.8.5/8.7.3) with SMTP id IAA19698; Mon, 26 May 1997 08:47:18 -0700 (PDT) Message-Id: <3.0.1.32.19970526113205.00715fc4@ranier.altavista-software.com> X-Sender: 3ampop@ranier.altavista-software.com X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Mon, 26 May 1997 11:32:05 -0400 To: Stefan Esser From: Matt Thomas Subject: Re: Oddness with NCR53C810 Cc: scsi@FreeBSD.ORG In-Reply-To: <19970526134212.20835@x14.mi.uni-koeln.de> References: <19970524124625.07596@keltia.freenix.fr> <19970524102943.GO37893@uriah.heep.sax.de> <19970524124625.07596@keltia.freenix.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 01:42 PM 5/26/97 +0200, Stefan Esser wrote: >The NCR/Symbios SCSI chips are: > >810 the original, 8bit, FAST >810a improved version of the 810, more efficent on the PCI bus >815 810 with BIOS support >860 810a with Ultra-SCSI support > >820 810 with support for WIDE SCSI >825 improved 820 with BIOS support >825a improved 825 with on-chip 4KB RAM >875 825a with Ultra-SCSI support >876 dual 875 885 multifunction 875 and fast ethernet (10/100) >895 875 with Ultra-2 support (40MHz sync. + LVD) > >The Sym53c876 allows to put two Ultra-WIDE SCSI channels on one PCI >card, without the need for a PCI to PCI bridge. This is better than >an Adaptec 3940 with two SCSI chips behind a PPB, since it is cheaper >and avoids the latency and complexity introduced by the PPB ... The Sym53c885 uses the same philosophy and puts a Fast Ethernet and UltraWide SCSI on one PCI chip. (I'm going to write a driver for the Fast Ethernet function.) -- Matt Thomas Internet: matt@3am-software.com 3am Software Foundry WWW URL: http://www.3am-software.com/bio/matt.html Westford, MA Disclaimer: I disavow all knowledge of this message From owner-freebsd-scsi Mon May 26 09:33:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA27272 for freebsd-scsi-outgoing; Mon, 26 May 1997 09:33:38 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA27255; Mon, 26 May 1997 09:33:33 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-1.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA06539 (5.67b/IDA-1.5); Mon, 26 May 1997 18:33:30 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id SAA01942; Mon, 26 May 1997 18:33:27 +0200 (CEST) X-Face: " Date: Mon, 26 May 1997 18:33:27 +0200 From: Stefan Esser To: Matt Thomas Cc: scsi@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: NCR SCSI + 100TX Ethernet chip References: <19970524124625.07596@keltia.freenix.fr> <19970524102943.GO37893@uriah.heep.sax.de> <19970524124625.07596@keltia.freenix.fr> <3.0.1.32.19970526113205.00715fc4@ranier.altavista-software.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.73 In-Reply-To: <3.0.1.32.19970526113205.00715fc4@ranier.altavista-software.com>; from Matt Thomas on Mon, May 26, 1997 at 11:32:05AM -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 26, Matt Thomas wrote: > >876 dual 875 > 885 multifunction 875 and fast ethernet (10/100) > >895 875 with Ultra-2 support (40MHz sync. + LVD) > > > >The Sym53c876 allows to put two Ultra-WIDE SCSI channels on one PCI > >card, without the need for a PCI to PCI bridge. This is better than > >an Adaptec 3940 with two SCSI chips behind a PPB, since it is cheaper > >and avoids the latency and complexity introduced by the PPB ... > > The Sym53c885 uses the same philosophy and puts a Fast Ethernet > and UltraWide SCSI on one PCI chip. (I'm going to write a driver > for the Fast Ethernet function.) I had only seen the 53c885 announcemt, but wasn't aware of any cards that use that chip. The combination of SCSI and Ethernet on one PCI card is most interesting, since there are just to few slots, always :) Does the Ethernet chip in the 885 share the problem of the DEC Ethernet chips, that requires copying of received packets (due to alignment constraints in the DMA engine, if I understand the problem correctly) ? Anyway: It's great that you are working on a driver for that chip! Regards, STefan From owner-freebsd-scsi Mon May 26 11:55:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA04947 for freebsd-scsi-outgoing; Mon, 26 May 1997 11:55:22 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA04929; Mon, 26 May 1997 11:55:13 -0700 (PDT) Received: from shasta.altavista-software.com (Cust101.Max3.Boston.MA.MS.UU.NET [153.35.70.229]) by mail.cdsnet.net (8.8.5/8.7.3) with SMTP id LAA13453; Mon, 26 May 1997 11:55:05 -0700 (PDT) Message-Id: <3.0.1.32.19970526145406.006d0124@ranier.altavista-software.com> X-Sender: 3ampop@ranier.altavista-software.com X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Mon, 26 May 1997 14:54:06 -0400 To: Stefan Esser From: Matt Thomas Subject: Re: NCR SCSI + 100TX Ethernet chip Cc: scsi@freebsd.org, hardware@freebsd.org In-Reply-To: <19970526183327.13556@x14.mi.uni-koeln.de> References: <3.0.1.32.19970526113205.00715fc4@ranier.altavista-software.com> <19970524124625.07596@keltia.freenix.fr> <19970524102943.GO37893@uriah.heep.sax.de> <19970524124625.07596@keltia.freenix.fr> <3.0.1.32.19970526113205.00715fc4@ranier.altavista-software.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 06:33 PM 5/26/97 +0200, Stefan Esser wrote: >I had only seen the 53c885 announcemt, but wasn't aware of any >cards that use that chip. The combination of SCSI and Ethernet >on one PCI card is most interesting, since there are just to few >slots, always :) The eval cards with it should be out next month. I've been able (I think) to get one reserved to me. >Does the Ethernet chip in the 885 share the problem of the DEC >Ethernet chips, that requires copying of received packets (due >to alignment constraints in the DMA engine, if I understand the >problem correctly) ? No idea. I'm waiting for the programming info to show up. I'm hoping it doesn't. -- Matt Thomas Internet: matt@3am-software.com 3am Software Foundry WWW URL: http://www.3am-software.com/bio/matt.html Westford, MA Disclaimer: I disavow all knowledge of this message From owner-freebsd-scsi Mon May 26 15:16:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA14429 for freebsd-scsi-outgoing; Mon, 26 May 1997 15:16:39 -0700 (PDT) Received: from giga.bga.com (root@giga.realtime.net [205.238.128.46]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA14424 for ; Mon, 26 May 1997 15:16:37 -0700 (PDT) Received: from urchin.bga.com (khym@urchin.realtime.net [205.238.128.41]) by giga.bga.com (8.6.5/8.6.12) with ESMTP id RAA22995; Mon, 26 May 1997 17:16:33 -0500 Received: from localhost (khym@localhost) by urchin.bga.com (8.6.12/8.6.10) with SMTP id RAA09223; Mon, 26 May 1997 17:16:32 -0500 X-Authentication-Warning: urchin.bga.com: khym owned process doing -bs Date: Mon, 26 May 1997 17:16:31 -0500 (CDT) From: Dave Huang To: freebsd-scsi@freebsd.org, current-users@netbsd.org Subject: ncr driver working well with 53c875? 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 Hi, I was thinking of getting some sort of 53c875 based card, probably either an Asus SC875 or Tekram DC390F, and I wanted to make sure that the ncr driver works well with it. I'm running NetBSD, but since it uses the FreeBSD driver, everything should be the same :) I'll be running a 2gig Wide Quantum Atlas and a 4gig Wide Atlas off the card... Any recommendation on whether I should get the Asus or the Tekram? I notice the driver has some code to read the Tekram's EPROM; what does that do? :) Thanks... -- Name: Dave Huang | Mammal, mammal / their names are called / INet: khym@bga.com | they raise a paw / the bat, the cat / FurryMUCK: Dahan | dolphin and dog / koala bear and hog -- TMBG Dahan: Hani G Y+C 21 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++ From owner-freebsd-scsi Mon May 26 20:45:31 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA24258 for freebsd-scsi-outgoing; Mon, 26 May 1997 20:45:31 -0700 (PDT) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA24252 for ; Mon, 26 May 1997 20:45:29 -0700 (PDT) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.5/8.8.5) with UUCP id VAA28278; Mon, 26 May 1997 21:45:16 -0600 (MDT) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id VAA10069; Mon, 26 May 1997 21:45:54 -0600 (MDT) Date: Mon, 26 May 1997 21:45:54 -0600 (MDT) From: Marc Slemko To: Dave Huang cc: freebsd-scsi@FreeBSD.ORG, current-users@netbsd.org Subject: Re: ncr driver working well with 53c875? 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 I have run both a DC-390U (ultra) and a DC-390F (ultra wide) under FreeBSD without any real problems. The U isn't wide, but still uses the 875 chipset. Note that the Tekram's BIOS doesn't like disks partitioned using FreeBSD's dedicated mode and will hang on boot if it sees one. The only problem I had was when attaching a wide drive to the narrow controller (390U) , the code kept thinking it could talk over a wide bus (the chip on the contoller is a 875, which is wide, the drive is wide, but the connection is narrow) and blew up horribly. To work around this I just used the appropriate define to force the NCR driver to only talk narrow. On Mon, 26 May 1997, Dave Huang wrote: > Hi, I was thinking of getting some sort of 53c875 based card, probably > either an Asus SC875 or Tekram DC390F, and I wanted to make sure that the > ncr driver works well with it. I'm running NetBSD, but since it uses the > FreeBSD driver, everything should be the same :) I'll be running a 2gig > Wide Quantum Atlas and a 4gig Wide Atlas off the card... > > Any recommendation on whether I should get the Asus or the Tekram? I > notice the driver has some code to read the Tekram's EPROM; what does that > do? :) > From owner-freebsd-scsi Mon May 26 23:34:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA29598 for freebsd-scsi-outgoing; Mon, 26 May 1997 23:34:50 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA29344 for ; Mon, 26 May 1997 23:29:14 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA23679; Tue, 27 May 1997 08:28:59 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA00700; Tue, 27 May 1997 08:07:27 +0200 (MET DST) Message-ID: <19970527080727.YB12431@uriah.heep.sax.de> Date: Tue, 27 May 1997 08:07:27 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.ORG, current-users@netbsd.org Subject: Re: ncr driver working well with 53c875? References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Marc Slemko on May 26, 1997 21:45:54 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Marc Slemko wrote: > Note that the Tekram's BIOS doesn't like disks partitioned using FreeBSD's > dedicated mode and will hang on boot if it sees one. Argl! That's the second BIOS i know that chokes on them. The first one is the newer HP BIOS from the Vectras and (ick!) the Netservers. They simply ignore the disk, go on to the floppy drive, and yell: No boot disk! Anyway, with HP, all bets are off, no doubt. They are a dinosaur. But Tekram has even contributed the SCSI driver to FreeBSD, so it might not be in vain asking them to fix this. The BIOS should not try to justify the feasibility of an MBR, it should just load and execute it. Stefan, do you have a connection to Tekram? I think BSD/OS employs a similar mode like FreeBSD's dedicated mode if you tell them to occupy the entire disk. They don't even pretend to fake an fdisk table at all (while FreeBSD does it out of tradition). -- 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. ;-) From owner-freebsd-scsi Tue May 27 04:02:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA07938 for freebsd-scsi-outgoing; Tue, 27 May 1997 04:02:00 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA07932 for ; Tue, 27 May 1997 04:01:55 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-9.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA21420 (5.67b/IDA-1.5 for ); Tue, 27 May 1997 13:01:51 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id NAA00733; Tue, 27 May 1997 13:01:49 +0200 (CEST) X-Face: " Date: Tue, 27 May 1997 13:01:49 +0200 From: Stefan Esser To: Dave Huang Cc: freebsd-scsi@FreeBSD.ORG, current-users@netbsd.org Subject: Re: ncr driver working well with 53c875? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Dave Huang on Mon, May 26, 1997 at 05:16:31PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 26, Dave Huang wrote: > Hi, I was thinking of getting some sort of 53c875 based card, probably > either an Asus SC875 or Tekram DC390F, and I wanted to make sure that the > ncr driver works well with it. I'm running NetBSD, but since it uses the > FreeBSD driver, everything should be the same :) I'll be running a 2gig > Wide Quantum Atlas and a 4gig Wide Atlas off the card... I don't know the state of the NCR driver in NetBSD, but do assume that the 875 is supported. Let me know, if you have any trouble with it ... > Any recommendation on whether I should get the Asus or the Tekram? I > notice the driver has some code to read the Tekram's EPROM; what does that > do? :) I have a Tekram DC-390F and a Symbios Sym8751S, and I do prefer the Symbios. Tekram wrote a FreeBSD driver that is specific to their card and published the sources. I did appreciate this, and it was one of the reasons I bought the DC-390F. But I do not like the Tekram SCSI BIOS. I found no way to obtain a more recent version than came with my card, and that one sometimes just hangs on reboot. It is also slow to probe the devices, it seems longer before the Tekram starts to probe for the first SCSI target than the Symbios needs to complete the bus scan. I used the Tekram sources to add code that dumps the config settings stored in Flash ROM. The generic SCSI code in FreeBSD is currently being reworked, and I plan to make the driver use the card's configuration as soon as the new SCSI code is available. There will also be support for the SDMS config NVRAM, then. Since I never saw an ASUS SC-875, I can't comment on that card. It is currently sold at very attractive prices over here, but I didn't check whether it comes with an internal WIDE SCSI cable (the Tekram does!). I have heard, that ASUS uses yet another SCSI BIOS of their own, not SDMS, but don't really know ... My typical setup is internal WIDE and external 8bit drives, but nearly all l875 based cards come with an external WIDE connector. Tyan seems to have build cards with internal WIDE SCSI and an external high density SCSI II connector (non-WIDE), and I definitely will try to get such a card, next time ... Be sure to check out which SCSI cables are supplied with the SCSI card, when comparing prices. An internal WIDE SCSI cable may cost an additional $50, if you buy it seperately. Regards, STefan From owner-freebsd-scsi Tue May 27 04:07:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA08186 for freebsd-scsi-outgoing; Tue, 27 May 1997 04:07:29 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA08170 for ; Tue, 27 May 1997 04:07:23 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-9.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA21501 (5.67b/IDA-1.5 for ); Tue, 27 May 1997 13:06:52 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id NAA00761; Tue, 27 May 1997 13:06:52 +0200 (CEST) X-Face: " Date: Tue, 27 May 1997 13:06:51 +0200 From: Stefan Esser To: Marc Slemko Cc: Dave Huang , freebsd-scsi@FreeBSD.ORG, current-users@netbsd.org Subject: Re: ncr driver working well with 53c875? References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Marc Slemko on Mon, May 26, 1997 at 09:45:54PM -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 26, Marc Slemko wrote: > I have run both a DC-390U (ultra) and a DC-390F (ultra wide) under FreeBSD > without any real problems. The U isn't wide, but still uses the 875 > chipset. > > Note that the Tekram's BIOS doesn't like disks partitioned using FreeBSD's > dedicated mode and will hang on boot if it sees one. Well, it will write a nasty complaint, and will pause for some 10 seconds, but will eventually continue the SCSI bus scan ... > The only problem I had was when attaching a wide drive to the narrow > controller (390U) , the code kept thinking it could talk over a wide bus > (the chip on the contoller is a 875, which is wide, the drive is wide, but > the connection is narrow) and blew up horribly. To work around this I > just used the appropriate define to force the NCR driver to only talk > narrow. There is not much that can be done about the problem of WIDE drives connected to a WIDE host adapter with an 8bit SCSI cable. The driver should fall back to non-WIDE mode if WIDE transfers fail because of the cable, but I have never tested that feature. One more point for the ToDo list ... :) Regards, STefan From owner-freebsd-scsi Tue May 27 04:13:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA08369 for freebsd-scsi-outgoing; Tue, 27 May 1997 04:13:27 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA08363 for ; Tue, 27 May 1997 04:13:16 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-9.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA21629 (5.67b/IDA-1.5 for ); Tue, 27 May 1997 13:13:08 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id NAA00787; Tue, 27 May 1997 13:13:08 +0200 (CEST) X-Face: " Date: Tue, 27 May 1997 13:13:08 +0200 From: Stefan Esser To: Joerg Wunsch Cc: freebsd-scsi@FreeBSD.ORG, current-users@netbsd.org Subject: Re: ncr driver working well with 53c875? References: <19970527080727.YB12431@uriah.heep.sax.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <19970527080727.YB12431@uriah.heep.sax.de>; from J Wunsch on Tue, May 27, 1997 at 08:07:27AM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 27, J Wunsch wrote: > Anyway, with HP, all bets are off, no doubt. They are a dinosaur. > But Tekram has even contributed the SCSI driver to FreeBSD, so it > might not be in vain asking them to fix this. The BIOS should not try > to justify the feasibility of an MBR, it should just load and execute > it. Well, the Tekram complains about the MBR, but eventually (after too long a delay) proceeds with the values it did just wine about ... > Stefan, do you have a connection to Tekram? No, not really. I know the mail address of some developer there, and had planned to send him the fixes I applied to the AMD SCSI driver (the low-end Tekram cards use the AMD chip, but share most of the driver code). > I think BSD/OS employs a similar mode like FreeBSD's dedicated mode if > you tell them to occupy the entire disk. They don't even pretend to > fake an fdisk table at all (while FreeBSD does it out of tradition). Maybe the controller is less worried when it does not see any MBR, than when it finds one with values it does not like ... :) Regards, STefan From owner-freebsd-scsi Tue May 27 05:24:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA10919 for freebsd-scsi-outgoing; Tue, 27 May 1997 05:24:14 -0700 (PDT) Received: from sand.sentex.ca (sand.sentex.ca [206.222.77.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA10914; Tue, 27 May 1997 05:24:06 -0700 (PDT) Received: from gravel (gravel.sentex.ca [205.211.165.210]) by sand.sentex.ca (8.8.5/8.8.3) with SMTP id IAA11232; Tue, 27 May 1997 08:29:28 -0400 (EDT) Message-Id: <3.0.1.32.19970527082652.00a53320@sentex.net> X-Sender: mdtancsa@sentex.net X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Tue, 27 May 1997 08:26:52 -0400 To: Stefan Esser , Dave Huang From: Mike Tancsa Subject: Re: ncr driver working well with 53c875? Cc: freebsd-scsi@FreeBSD.ORG, current-users@netbsd.org In-Reply-To: <19970527130149.33023@x14.mi.uni-koeln.de> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Be sure to check out which SCSI cables are supplied with the >SCSI card, when comparing prices. An internal WIDE SCSI cable >may cost an additional $50, if you buy it seperately. My ASUS PC-875 came with an internal Narrow cable. I assume its standard wherever sold. ---Mike ********************************************************************** Mike Tancsa (mike@sentex.net) * To do is to be -- Nietzsche Sentex Communications Corp, * To be is to do -- Sartre Cambridge, Ontario * Do be do be do -- Sinatra (http://www.sentex.net/~mdtancsa) * From owner-freebsd-scsi Tue May 27 07:53:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA16561 for freebsd-scsi-outgoing; Tue, 27 May 1997 07:53:07 -0700 (PDT) Received: from scanner.worldgate.com (scanner.worldgate.com [198.161.84.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA16555; Tue, 27 May 1997 07:52:58 -0700 (PDT) Received: from znep.com (uucp@localhost) by scanner.worldgate.com (8.8.5/8.8.5) with UUCP id IAA11201; Tue, 27 May 1997 08:52:52 -0600 (MDT) Received: from localhost (marcs@localhost) by alive.znep.com (8.7.5/8.7.3) with SMTP id IAA12512; Tue, 27 May 1997 08:52:03 -0600 (MDT) Date: Tue, 27 May 1997 08:52:02 -0600 (MDT) From: Marc Slemko Reply-To: Marc Slemko To: Stefan Esser cc: freebsd-scsi@freebsd.org, current-users@netbsd.org Subject: Re: ncr driver working well with 53c875? In-Reply-To: <19970527130651.56313@x14.mi.uni-koeln.de> 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, 27 May 1997, Stefan Esser wrote: > On May 26, Marc Slemko wrote: > > I have run both a DC-390U (ultra) and a DC-390F (ultra wide) under FreeBSD > > without any real problems. The U isn't wide, but still uses the 875 > > chipset. > > > > Note that the Tekram's BIOS doesn't like disks partitioned using FreeBSD's > > dedicated mode and will hang on boot if it sees one. > > Well, it will write a nasty complaint, and will pause for > some 10 seconds, but will eventually continue the SCSI bus > scan ... Perhaps with newer BIOSes it is fixed. I get a nasty complaint if the geometry isn't what it thinks it should be and it then continues, but with the version I was using if I used the dedicated mode it just hangs. From owner-freebsd-scsi Tue May 27 10:53:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA24978 for freebsd-scsi-outgoing; Tue, 27 May 1997 10:53:08 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA24954 for ; Tue, 27 May 1997 10:52:52 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA01659; Tue, 27 May 1997 19:52:20 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id TAA02255; Tue, 27 May 1997 19:28:59 +0200 (MET DST) Message-ID: <19970527192859.WW56689@uriah.heep.sax.de> Date: Tue, 27 May 1997 19:28:59 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@freebsd.org, current-users@netbsd.org Subject: Re: ncr driver working well with 53c875? References: <19970527080727.YB12431@uriah.heep.sax.de> <19970527131308.62693@x14.mi.uni-koeln.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970527131308.62693@x14.mi.uni-koeln.de>; from Stefan Esser on May 27, 1997 13:13:08 +0200 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Stefan Esser wrote: > > Stefan, do you have a connection to Tekram? > > No, not really. I know the mail address of some developer > there, and had planned to send him the fixes I applied to > the AMD SCSI driver (the low-end Tekram cards use the AMD > chip, but share most of the driver code). Well, please bug him about the BIOS bug. ;-) > Maybe the controller is less worried when it does not see > any MBR, than when it finds one with values it does not > like ... :) No such thing like ``no MBR''. The MBR is by definition the very first 512-byte record of a bootable drive. It needs to have a 0x55aa signature at the end in order to be recognized by the BIOS. Some BIOSes apparently try to be `smarter', and wanna imply more semantics than this signature. (Normally, the BIOS should just load an MBR that has this signature onto address 0x7c0:0, and execute it.) -- 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. ;-) From owner-freebsd-scsi Wed May 28 10:17:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA22256 for freebsd-scsi-outgoing; Wed, 28 May 1997 10:17:00 -0700 (PDT) Received: from gaia.coppe.ufrj.br (root@[146.164.5.200]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA22247 for ; Wed, 28 May 1997 10:16:53 -0700 (PDT) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.5/8.7.3) id OAA16552 for scsi@freebsd.org; Wed, 28 May 1997 14:16:20 -0300 (EST) From: Joao Carlos Mendes Luis Message-Id: <199705281716.OAA16552@gaia.coppe.ufrj.br> Subject: ZIP drive eject To: scsi@freebsd.org Date: Wed, 28 May 1997 14:16:20 -0300 (EST) X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I noted that it's possible to eject a ZIP disk even when it's mounted. I'm using an external ZIP, attached to a 1542 SCSI adapter. My kernel is a 2.2.1-R with a patch to recognize the ZIP as an "od" device. Does somebody know if it's a hardware problem with the drive, or a software problem with FreeBSD or the "od" patch ? Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 ( Job ) jonny@cisi.coppe.ufrj.br Network Manager UFRJ/COPPE/CISI Universidade Federal do Rio de Janeiro From owner-freebsd-scsi Wed May 28 12:54:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA28930 for freebsd-scsi-outgoing; Wed, 28 May 1997 12:54:41 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA28908; Wed, 28 May 1997 12:54:29 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.5/8.7.3) with SMTP id MAA23810; Wed, 28 May 1997 12:54:28 -0700 (PDT) Date: Wed, 28 May 1997 12:54:26 -0700 (PDT) From: Jaye Mathisen To: scsi@freebsd.org, hackers@freebsd.org Subject: Boot problems/sd1/I'm sorry, I think ahc is acting funky. 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 posted this a few days ago, but now it's really biting me in the butt, and I'd like to see if it's fixable before I throw out the baby and the bathwater. I have a box with a 3940UW and 2940AU. In the BIOS scan of the PCI bus, it finds the 3940 first, then the 2940. Swapping cards in the PCI slots confirms this order. *however*, when FreeBSD boots, it *always* finds the 2940 first, and assigns it as ahc0, and the 3940 as ahc1 and ahc2. This is broke I think. This is problematic, as when booting (since I have a JAZ drive on the 2940), It assigns sd0 to the JAZ, *and* makes me type: 0:sd(1,a)/kernel to the boot blocks to boot each time, which is a major drag. This behaviour seems specific to FreeBSD, as other OS's find them in the same order as the BIOS scan. IS this easily fixable? From owner-freebsd-scsi Wed May 28 13:11:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA29882 for freebsd-scsi-outgoing; Wed, 28 May 1997 13:11:45 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA29865; Wed, 28 May 1997 13:11:40 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.5/8.7.3) with SMTP id NAA26168; Wed, 28 May 1997 13:11:39 -0700 (PDT) Date: Wed, 28 May 1997 13:11:39 -0700 (PDT) From: Jaye Mathisen To: scsi@freebsd.org, hackers@freebsd.org Subject: More ahc0 driver problems. 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 # uname -a FreeBSD yyy.cdsnet.net 2.2.2-RELEASE FreeBSD 2.2.2-RELEASE #0: Fri May 26 22:27:17 PDT 1995 root@yyy.cdsnet.net:/usr/src/sys/compile/SCHIZO2 i386 Under bonnie to a ccd of sd2, sd3 (WD 4.1GB Enterprise drives): # bonnie -s 1000 File './Bonnie.333', size: 1048576000 Writing with putc()...May 28 13:08:12 yyy /kernel: sd4(ahc2:1:0): SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0xe6 May 28 13:08:12 yyy /kernel: sd4(ahc2:1:0): SCB 0x2 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0xe6 May 28 13:08:12 yyy /kernel: SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x27 SSTAT1 = 0xb May 28 13:08:12 yyy /kernel: SEQADDR = 0x4 SCSISEQ = 0x12 SSTAT0 = 0x27 SSTAT1 = 0xb May 28 13:08:12 yyy /kernel: Ordered Tag queued May 28 13:08:12 yyy /kernel: Ordered Tag queued May 28 13:08:12 yyy /kernel: Ordered Tag sent May 28 13:08:12 yyy /kernel: Ordered Tag sent May 28 13:08:12 yyy /kernel: sd4(ahc2:1:0): no longer in timeout May 28 13:08:12 yyy /kernel: sd4(ahc2:1:0): no longer in timeout May 28 13:08:22 yyy /kernel: sd4(ahc2:1:0): SCB 0x3 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0xe6 May 28 13:08:22 yyy /kernel: sd4(ahc2:1:0): SCB 0x3 - timed out while idle, LAST Reams and reams of them. WHen it gets to the rewriting phase, it quiets down. How do I turn on write caching in my drive? I assume I have to edit some mode page, but heck if I know which one. From owner-freebsd-scsi Wed May 28 14:09:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA03122 for freebsd-scsi-outgoing; Wed, 28 May 1997 14:09:45 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA03094; Wed, 28 May 1997 14:09:33 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-45.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA16525 (5.67b/IDA-1.5); Wed, 28 May 1997 23:09:30 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id XAA11010; Wed, 28 May 1997 23:09:25 +0200 (CEST) X-Face: " Date: Wed, 28 May 1997 23:09:24 +0200 From: Stefan Esser To: Jaye Mathisen Cc: scsi@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Boot problems/sd1/I'm sorry, I think ahc is acting funky. References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Jaye Mathisen on Wed, May 28, 1997 at 12:54:26PM -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 28, Jaye Mathisen wrote: > > I posted this a few days ago, but now it's really biting me in the butt, > and I'd like to see if it's fixable before I throw out the baby and the > bathwater. Well, yes, there might be a way if you are running -current ... > I have a box with a 3940UW and 2940AU. In the BIOS scan of the PCI bus, > it finds the 3940 first, then the 2940. Swapping cards in the PCI slots > confirms this order. This is a very bogus scan order, except if you requested it in some BIOS setup! PCI bus 0 is always scanned first (with different motherboards using either ascending or descending slot number order). Only after bus 0 is completed, the scan descends down to devices behind PCI to PCI bridges. This order is REQUIRED for all buses > bus 0 (because of the active address decode principle in PCI), but it obviously does not make much sense to have a different probe order for buses directly connected to bus 0 and buses that are themselves connected through a bridge. > *however*, when FreeBSD boots, it *always* finds the 2940 first, and > assigns it as ahc0, and the 3940 as ahc1 and ahc2. This is broke I think. No. Not at all! And there would be MANY more complaints, if I changeed the probe order in the way you suggest! > This is problematic, as when booting (since I have a JAZ drive on the > 2940), It assigns sd0 to the JAZ, *and* makes me type: > > 0:sd(1,a)/kernel > > to the boot blocks to boot each time, which is a major drag. You know about the boot.config file ? (Again assuming you got a reasonably recent kernel). > This behaviour seems specific to FreeBSD, as other OS's find them in the > same order as the BIOS scan. Hmmm, well, I could use the PCI BIOS to scan by supported PCI device ID, instead of by bus topology, but this introduces other problems which I'd prefer to avoid. > IS this easily fixable? There IS nothing to fix, actually ... Either put a reasonable boot command line into /boot.config, or locate the definion of "pci_wireddevs" in /sys/pci/pci_compat.c and add a line reading: { "ahc", 2, 0, SLOT, 0, 0 }, with the SLOT number of the 2940 filled in. (You didn't send the verbose boot message log I need to give more detailed instructions.) You can also remove the other lines (except the last), since they are only left overs from tests I performed before commiting that code ... Let me know if neither approach works for you. Regards, STefan From owner-freebsd-scsi Wed May 28 14:23:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA03758 for freebsd-scsi-outgoing; Wed, 28 May 1997 14:23:38 -0700 (PDT) Received: from dyson.iquest.net (dyson.iquest.net [198.70.144.127]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA03736; Wed, 28 May 1997 14:23:32 -0700 (PDT) Received: (from root@localhost) by dyson.iquest.net (8.8.5/8.8.5) id QAA14153; Wed, 28 May 1997 16:23:19 -0500 (EST) From: "John S. Dyson" Message-Id: <199705282123.QAA14153@dyson.iquest.net> Subject: Re: More ahc0 driver problems. In-Reply-To: from Jaye Mathisen at "May 28, 97 01:11:39 pm" To: mrcpu@cdsnet.net (Jaye Mathisen) Date: Wed, 28 May 1997 16:23:19 -0500 (EST) Cc: scsi@FreeBSD.ORG, hackers@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > How do I turn on write caching in my drive? I assume I have to edit some > mode page, but heck if I know which one. > scsi -f /dev/rsdX.ctl -m 8 -e The flag that you want to set is WCE. John From owner-freebsd-scsi Wed May 28 14:27:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA03959 for freebsd-scsi-outgoing; Wed, 28 May 1997 14:27:42 -0700 (PDT) Received: from darius.concentric.net (darius.concentric.net [207.155.184.79]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA03951; Wed, 28 May 1997 14:27:37 -0700 (PDT) Received: from mcfeely.concentric.net (mcfeely.concentric.net [207.155.184.83]) by darius.concentric.net (8.8.5/(97/05/21 3.30)) id RAA23872; Wed, 28 May 1997 17:27:34 -0400 (EDT) [1-800-745-2747 The Concentric Network] Received: from athena (ts001d01.sal-ut.concentric.net [206.173.156.13]) by mcfeely.concentric.net (8.8.5) id RAA14523; Wed, 28 May 1997 17:27:31 -0400 (EDT) Message-ID: <338CA310.1E013B5B@concentric.net> Date: Wed, 28 May 1997 15:26:40 -0600 From: Joshua Fielden Organization: Shaggy Enterprises X-Mailer: Mozilla 4.0b5 [en] (WinNT; I) MIME-Version: 1.0 To: Jaye Mathisen CC: scsi@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: More ahc0 driver problems. X-Priority: 3 (Normal) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Jaye Mathisen wrote: > How do I turn on write caching in my drive? I assume I have to edit some > mode page, but heck if I know which one. Write-Cache enabled, (WCE) is in mode page 8. I forget the hex of the page off-hand..... JF From owner-freebsd-scsi Wed May 28 14:29:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA04137 for freebsd-scsi-outgoing; Wed, 28 May 1997 14:29:14 -0700 (PDT) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA04112; Wed, 28 May 1997 14:29:08 -0700 (PDT) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.5/8.7.3) id OAA06506; Wed, 28 May 1997 14:28:48 -0700 (PDT) Date: Wed, 28 May 1997 14:28:48 -0700 (PDT) Message-Id: <199705282128.OAA06506@vader.cs.berkeley.edu> To: ken@r74h25.res.gatech.edu CC: albast@magigimmix.xs4all.nl, Questions@FreeBSD.ORG, SCSI@FreeBSD.ORG, ISP@FreeBSD.ORG, jh@Twiddle.COM In-reply-to: <199705260356.XAA28280@r74h25.res.gatech.edu> (ken@r74h25.res.gatech.edu) Subject: Re: Some advice needed From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * Really? I loaded the LXY4 firmware upgrade on my ultra-wide * 4G Atlas II, and it's working fine. (I believe I used Dagnlxy4.fup) * * I started out with LXQ1 firmware. Thanks to all those replied. I finally summoned my courage and downloaded the firmware to my wide AII. It warned me that the type doesn't match but it is working fine (even says "34550W" like Ken's) since then with a 2940UW. Satoshi From owner-freebsd-scsi Wed May 28 15:32:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA07855 for freebsd-scsi-outgoing; Wed, 28 May 1997 15:32:14 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA07831; Wed, 28 May 1997 15:32:09 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id QAA02632; Wed, 28 May 1997 16:31:59 -0600 (MDT) Message-Id: <199705282231.QAA02632@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Jaye Mathisen cc: scsi@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Boot problems/sd1/I'm sorry, I think ahc is acting funky. In-reply-to: Your message of "Wed, 28 May 1997 12:54:26 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 May 1997 17:29:23 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > >IS this easily fixable? > Hardwire your scsi busses. See scsi.4 for details. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Wed May 28 15:40:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA08467 for freebsd-scsi-outgoing; Wed, 28 May 1997 15:40:16 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA08447; Wed, 28 May 1997 15:40:07 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id QAA02847; Wed, 28 May 1997 16:40:04 -0600 (MDT) Message-Id: <199705282240.QAA02847@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Jaye Mathisen cc: scsi@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: More ahc0 driver problems. In-reply-to: Your message of "Wed, 28 May 1997 13:11:39 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 28 May 1997 17:37:28 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Under bonnie to a ccd of sd2, sd3 (WD 4.1GB Enterprise drives): ... >Reams and reams of them. WHen it gets to the rewriting phase, it quiets >down. This problem has been mentioned many times before on this list. You are doing sufficient I/O local to one area of the drives that the drive is "starving" transactions that would require a long seek to complete for as long as 10 second. That's the reason the ordered tagged transaction (which basically means complete everything else before you run me) clears up the condition. Some changes coming down the line that turn synchronous writes into async, ordered writes will help to mitigate this problem as there will be an occasional ordered tagged transaction in the stream being sent to the driver. Of course, if you mount your filesystem async, this wouldn't happen. The Linux Buslogic driver works around this problem by simply sending an ordered tag "every once in a while". I don't really like that solution much. >How do I turn on write caching in my drive? I assume I have to edit some >mode page, but heck if I know which one. man 8 scsi. You should also look at /usr/share/misc/scsi_modes. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Wed May 28 17:30:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA13527 for freebsd-scsi-outgoing; Wed, 28 May 1997 17:30:18 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA13521 for ; Wed, 28 May 1997 17:30:14 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.5/8.7.3) with SMTP id RAA14209; Wed, 28 May 1997 17:30:05 -0700 (PDT) Date: Wed, 28 May 1997 17:30:03 -0700 (PDT) From: Jaye Mathisen To: "Justin T. Gibbs" cc: scsi@FreeBSD.ORG Subject: Re: More ahc0 driver problems. In-Reply-To: <199705282240.QAA02847@pluto.plutotech.com> 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 Hmmmm, I'm not sure I understand this. Under iostat, the drives maintain a constant 6000-7000 blocks writing, and there are no seizures/freezeups of any kind, just the constant stream of "errors". Also, it's on a ccd, which should be splitting up the I/O's over both drives. Will write-caching help or hinder this problem? And lastly, would it be possible (since it's not really an error then), the big blast of messages suppressed, or only printed via a config variable? On Wed, 28 May 1997, Justin T. Gibbs wrote: > >Under bonnie to a ccd of sd2, sd3 (WD 4.1GB Enterprise drives): > > ... > > >Reams and reams of them. WHen it gets to the rewriting phase, it quiets > >down. > > This problem has been mentioned many times before on this list. You are > doing sufficient I/O local to one area of the drives that the drive is > "starving" transactions that would require a long seek to complete for as > long as 10 second. That's the reason the ordered tagged transaction (which > basically means complete everything else before you run me) clears up the > condition. Some changes coming down the line that turn synchronous writes > into async, ordered writes will help to mitigate this problem as there will > be an occasional ordered tagged transaction in the stream being sent to the > driver. Of course, if you mount your filesystem async, this wouldn't > happen. > > The Linux Buslogic driver works around this problem by simply sending an > ordered tag "every once in a while". I don't really like that solution > much. From owner-freebsd-scsi Wed May 28 17:30:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA13578 for freebsd-scsi-outgoing; Wed, 28 May 1997 17:30:51 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA13552; Wed, 28 May 1997 17:30:42 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.5/8.7.3) with SMTP id RAA14311; Wed, 28 May 1997 17:30:39 -0700 (PDT) Date: Wed, 28 May 1997 17:30:39 -0700 (PDT) From: Jaye Mathisen To: "Justin T. Gibbs" cc: scsi@FreeBSD.ORG, hackers@FreeBSD.ORG Subject: Re: Boot problems/sd1/I'm sorry, I think ahc is acting funky. In-Reply-To: <199705282231.QAA02632@pluto.plutotech.com> 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 In the words of the master: Duh!. On Wed, 28 May 1997, Justin T. Gibbs wrote: > > > >IS this easily fixable? > > > > Hardwire your scsi busses. See scsi.4 for details. > > -- > Justin T. Gibbs > =========================================== > FreeBSD: Turning PCs into workstations > =========================================== > > From owner-freebsd-scsi Wed May 28 19:07:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA16902 for freebsd-scsi-outgoing; Wed, 28 May 1997 19:07:00 -0700 (PDT) Received: from giga.bga.com (root@giga.realtime.net [205.238.128.46]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id TAA16885; Wed, 28 May 1997 19:06:52 -0700 (PDT) Received: from urchin.bga.com (khym@urchin.realtime.net [205.238.128.41]) by giga.bga.com (8.6.5/8.6.12) with ESMTP id VAA27529; Wed, 28 May 1997 21:06:46 -0500 Received: from localhost (khym@localhost) by urchin.bga.com (8.6.12/8.6.10) with SMTP id VAA25649; Wed, 28 May 1997 21:06:44 -0500 X-Authentication-Warning: urchin.bga.com: khym owned process doing -bs Date: Wed, 28 May 1997 21:06:43 -0500 (CDT) From: Dave Huang To: Stefan Esser cc: freebsd-scsi@freebsd.org, current-users@netbsd.org Subject: Re: ncr driver working well with 53c875? In-Reply-To: <19970527130149.33023@x14.mi.uni-koeln.de> 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'd like to thank everyone for their replies, btw :) On Tue, 27 May 1997, Stefan Esser wrote: > I have heard, that ASUS uses yet another SCSI BIOS of their > own, not SDMS, but don't really know ... I don't actually know either, but from looking at their BIOS/driver updates, I get the impression that ASUS does use the Symbios SDMS. Anyone with an SC875 wish to confirm/deny? :) > My typical setup is internal WIDE and external 8bit drives, > but nearly all l875 based cards come with an external WIDE > connector. Tyan seems to have build cards with internal WIDE > SCSI and an external high density SCSI II connector (non-WIDE), > and I definitely will try to get such a card, next time ... I don't currently have any external devices, but if I ever get any, they'll probably be narrow. I've already got an ASUS SC200 (53c810) that I'm planning on keeping though, so I'll just use that for external things... BTW, the Diamond FirePort 40 is another 875-based card with an external narrow connector. > Be sure to check out which SCSI cables are supplied with the > SCSI card, when comparing prices. An internal WIDE SCSI cable > may cost an additional $50, if you buy it seperately. Yeah, wide cables seem to be quite expensive :( Does the Tekram's wide cable have enough connectors for two drives? (i.e. at least three connectors total). If it's only a single drive cable, I'll have to get another cable anyways... Thanks for the info! :) -- Name: Dave Huang | Mammal, mammal / their names are called / INet: khym@bga.com | they raise a paw / the bat, the cat / FurryMUCK: Dahan | dolphin and dog / koala bear and hog -- TMBG Dahan: Hani G Y+C 21 Y++ L+++ W- C++ T++ A+ E+ S++ V++ F- Q+++ P+ B+ PA+ PL++ From owner-freebsd-scsi Wed May 28 23:04:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA26979 for freebsd-scsi-outgoing; Wed, 28 May 1997 23:04:32 -0700 (PDT) Received: from kithrup.com (kithrup.com [205.179.156.40]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA26974 for ; Wed, 28 May 1997 23:04:30 -0700 (PDT) Received: (from sef@localhost) by kithrup.com (8.6.8/8.6.6) id XAA01349 for scsi@freebsd.org; Wed, 28 May 1997 23:04:29 -0700 Date: Wed, 28 May 1997 23:04:29 -0700 From: Sean Eric Fagan Message-Id: <199705290604.XAA01349@kithrup.com> To: scsi@freebsd.org Subject: ARCHIVE Python 00072-0014.BT Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk That's what my tape drive identifies itself as. Does anyone know how to change tapes (it's got an autoloader) through software? Thanks... Sean. From owner-freebsd-scsi Wed May 28 23:51:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA29214 for freebsd-scsi-outgoing; Wed, 28 May 1997 23:51:08 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id XAA29209 for ; Wed, 28 May 1997 23:51:05 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA05906; Thu, 29 May 1997 08:50:56 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA03174; Thu, 29 May 1997 08:27:47 +0200 (MET DST) Message-ID: <19970529082747.DK34680@uriah.heep.sax.de> Date: Thu, 29 May 1997 08:27:47 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: scsi@FreeBSD.ORG Cc: jonny@mailhost.coppe.ufrj.br (Joao Carlos Mendes Luis) Subject: Re: ZIP drive eject References: <199705281716.OAA16552@gaia.coppe.ufrj.br> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199705281716.OAA16552@gaia.coppe.ufrj.br>; from Joao Carlos Mendes Luis on May 28, 1997 14:16:20 -0300 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Joao Carlos Mendes Luis wrote: > I noted that it's possible to eject a ZIP disk even when it's > mounted. I'm using an external ZIP, attached to a 1542 SCSI adapter. > My kernel is a 2.2.1-R with a patch to recognize the ZIP as an "od" > device. This probably means your drive is ignoring the PREVENT ALLOW MEDIUM REMOVAL command issued by the driver. (All our drivers do this.) Maybe there's a jumper or such for it? -- 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. ;-) From owner-freebsd-scsi Thu May 29 00:59:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA01818 for freebsd-scsi-outgoing; Thu, 29 May 1997 00:59:39 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA01809 for ; Thu, 29 May 1997 00:59:35 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA06476; Thu, 29 May 1997 09:59:29 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA03469; Thu, 29 May 1997 09:57:30 +0200 (MET DST) Message-ID: <19970529095730.OB32639@uriah.heep.sax.de> Date: Thu, 29 May 1997 09:57:30 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: scsi@FreeBSD.ORG Cc: sef@Kithrup.COM (Sean Eric Fagan) Subject: Re: ARCHIVE Python 00072-0014.BT References: <199705290604.XAA01349@kithrup.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199705290604.XAA01349@kithrup.com>; from Sean Eric Fagan on May 28, 1997 23:04:29 -0700 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Sean Eric Fagan wrote: > That's what my tape drive identifies itself as. > > Does anyone know how to change tapes (it's got an autoloader) through > software? Add it to the list of known devices that don't have a broken LUN recognition in sys/scsi/scsiconf.c. Well, i wonder whether we could add all ARCHIVE Pythons there, this would make the matters simpler. Perhaps i'll give it a try, and see whether somebody yells. After this, use chio(1). -- 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. ;-) From owner-freebsd-scsi Thu May 29 09:33:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA24801 for freebsd-scsi-outgoing; Thu, 29 May 1997 09:33:47 -0700 (PDT) Received: from gaia.coppe.ufrj.br (root@[146.164.5.200]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA24793 for ; Thu, 29 May 1997 09:33:43 -0700 (PDT) Received: (from jonny@localhost) by gaia.coppe.ufrj.br (8.8.5/8.7.3) id NAA02476; Thu, 29 May 1997 13:33:34 -0300 (EST) From: Joao Carlos Mendes Luis Message-Id: <199705291633.NAA02476@gaia.coppe.ufrj.br> Subject: Re: ZIP drive eject To: joerg_wunsch@uriah.heep.sax.de Date: Thu, 29 May 1997 13:33:34 -0300 (EST) Cc: scsi@FreeBSD.ORG, jonny@mailhost.coppe.ufrj.br In-Reply-To: <19970529082747.DK34680@uriah.heep.sax.de> from J Wunsch at "May 29, 97 08:27:47 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk #define quoting(J Wunsch) // As Joao Carlos Mendes Luis wrote: // // > I noted that it's possible to eject a ZIP disk even when it's // > mounted. I'm using an external ZIP, attached to a 1542 SCSI adapter. // > My kernel is a 2.2.1-R with a patch to recognize the ZIP as an "od" // > device. // // This probably means your drive is ignoring the PREVENT ALLOW MEDIUM // REMOVAL command issued by the driver. (All our drivers do this.) I cannot manually eject it. Only computer generated eject commands have this behaviour. // Maybe there's a jumper or such for it? None that I know about. :) Jonny -- Joao Carlos Mendes Luis jonny@gta.ufrj.br +55 21 290-4698 ( Job ) jonny@cisi.coppe.ufrj.br Network Manager UFRJ/COPPE/CISI Universidade Federal do Rio de Janeiro From owner-freebsd-scsi Thu May 29 09:34:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA24981 for freebsd-scsi-outgoing; Thu, 29 May 1997 09:34:48 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA24940 for ; Thu, 29 May 1997 09:34:33 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id SAA28033; Thu, 29 May 1997 18:32:51 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id SAA14887; Thu, 29 May 1997 18:32:25 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id HAA14232; Thu, 29 May 1997 07:21:54 +0200 (CEST) Message-ID: <19970529072154.35358@keltia.freenix.fr> Date: Thu, 29 May 1997 07:21:54 +0200 From: Ollivier Robert To: scsi@FreeBSD.ORG Cc: Jaye Mathisen Subject: Re: More ahc0 driver problems. References: <199705282123.QAA14153@dyson.iquest.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67 In-Reply-To: <199705282123.QAA14153@dyson.iquest.net>; from John S. Dyson on Wed, May 28, 1997 at 04:23:19PM -0500 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3332 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [ restricted to scsi ] According to John S. Dyson: > scsi -f /dev/rsdX.ctl -m 8 -e > > The flag that you want to set is WCE. Don't forget to add "-P 3" in order to save the parameters as default. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #10: Fri May 23 22:47:39 CEST 1997 From owner-freebsd-scsi Thu May 29 10:21:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA26816 for freebsd-scsi-outgoing; Thu, 29 May 1997 10:21:33 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA26810 for ; Thu, 29 May 1997 10:21:28 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id TAA12970; Thu, 29 May 1997 19:20:48 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id SAA04765; Thu, 29 May 1997 18:58:22 +0200 (MET DST) Message-ID: <19970529185822.ZU26528@uriah.heep.sax.de> Date: Thu, 29 May 1997 18:58:22 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: scsi@FreeBSD.ORG Cc: jonny@mailhost.coppe.ufrj.br (Joao Carlos Mendes Luis) Subject: Re: ZIP drive eject References: <19970529082747.DK34680@uriah.heep.sax.de> <199705291633.NAA02476@gaia.coppe.ufrj.br> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <199705291633.NAA02476@gaia.coppe.ufrj.br>; from Joao Carlos Mendes Luis on May 29, 1997 13:33:34 -0300 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Joao Carlos Mendes Luis wrote: > // This probably means your drive is ignoring the PREVENT ALLOW MEDIUM > // REMOVAL command issued by the driver. (All our drivers do this.) > > I cannot manually eject it. Only computer generated eject commands > have this behaviour. Ah, understood. That's a bugfeature of the driver, copied from the CD-ROM driver. It would probably be a simple matter to fix it in od(4), but more complicated to fix it in cd(4). The various CD players basically rely on the misconception that they can eject a CD while the device is open. -- 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. ;-) From owner-freebsd-scsi Thu May 29 14:04:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA09283 for freebsd-scsi-outgoing; Thu, 29 May 1997 14:04:44 -0700 (PDT) Received: from whqvax.picker.com (whqvax.picker.com [144.54.1.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA09273 for ; Thu, 29 May 1997 14:04:40 -0700 (PDT) Received: from ct.picker.com by whqvax.picker.com with SMTP; Thu, 29 May 1997 17:04:01 -0400 (EDT) Received: from elmer.ct.picker.com ([144.54.57.34]) by ct.picker.com (4.1/SMI-4.1) id AA13375; Thu, 29 May 97 17:04:00 EDT Received: by elmer.ct.picker.com (SMI-8.6/SMI-SVR4) id RAA08067; Thu, 29 May 1997 17:02:49 -0400 Message-Id: <19970529170249.26384@ct.picker.com> Date: Thu, 29 May 1997 17:02:49 -0400 From: Randall Hopper To: J Wunsch Cc: scsi@FreeBSD.ORG Subject: Re: ZIP drive eject References: <199705281716.OAA16552@gaia.coppe.ufrj.br> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199705281716.OAA16552@gaia.coppe.ufrj.br>; from Joao Carlos Mendes Luis on Wed, May 28, 1997 at 02:16:20PM -0300 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk J Wunsch: |Joao Carlos Mendes Luis: | | I noted that it's possible to eject a ZIP disk even when it's | |mounted. I'm using an external ZIP, attached to a 1542 SCSI adapter. | |My kernel is a 2.2.1-R with a patch to recognize the ZIP as an "od" | |device. | | I cannot manually eject it. Only computer generated eject commands | | have this behaviour. | |Ah, understood. That's a bugfeature of the driver, copied from the |CD-ROM driver. It would probably be a simple matter to fix it in |od(4), but more complicated to fix it in cd(4). The various CD |players basically rely on the misconception that they can eject a CD |while the device is open. Is it possible to eject a ZIP via S/W when using the "sd" driver? Randall Hopper From owner-freebsd-scsi Thu May 29 14:51:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA11822 for freebsd-scsi-outgoing; Thu, 29 May 1997 14:51:28 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA11817 for ; Thu, 29 May 1997 14:51:24 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id XAA17828 for scsi@FreeBSD.ORG; Thu, 29 May 1997 23:51:09 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id XAA05612; Thu, 29 May 1997 23:37:00 +0200 (MET DST) Message-ID: <19970529233700.VT43737@uriah.heep.sax.de> Date: Thu, 29 May 1997 23:37:00 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: scsi@FreeBSD.ORG Subject: Re: ZIP drive eject References: <199705281716.OAA16552@gaia.coppe.ufrj.br> <19970529170249.26384@ct.picker.com> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970529170249.26384@ct.picker.com>; from Randall Hopper on May 29, 1997 17:02:49 -0400 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Randall Hopper wrote: > Is it possible to eject a ZIP via S/W when using the "sd" driver? No. -- 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. ;-) From owner-freebsd-scsi Thu May 29 15:30:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA13386 for freebsd-scsi-outgoing; Thu, 29 May 1997 15:30:06 -0700 (PDT) Received: from mail.calweb.com (mail.calweb.com [208.131.56.11]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA13381 for ; Thu, 29 May 1997 15:30:03 -0700 (PDT) Received: by mail.calweb.com (8.8.5/8.8.5) with ESMTP id PAA01749; Thu, 29 May 1997 15:29:47 -0700 (PDT) Received: (from cslye@localhost) by web1.calweb.com (8.8.5/8.8.5) id PAA19387; Thu, 29 May 1997 15:15:03 -0700 (PDT) Message-Id: <199705292215.PAA19387@web1.calweb.com> Subject: Re: ARCHIVE Python 00072-0014.BT To: sef@Kithrup.COM (Sean Eric Fagan) Date: Thu, 29 May 1997 15:15:03 -0700 (PDT) From: "Cameron Slye" Cc: freebsd-scsi@freebsd.org In-Reply-To: <199705290604.XAA01349@kithrup.com> from "Sean Eric Fagan" at May 28, 97 11:04:29 pm X-Mailer: ELM [version 2.4 PL25 ME8b] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > > That's what my tape drive identifies itself as. > > Does anyone know how to change tapes (it's got an autoloader) through > software? You need to use something called ch. Do a "man ch". Also you will need to compile a ch drive in your kernel. You might need to edit some src to make it see your drive as a changer. From owner-freebsd-scsi Thu May 29 18:05:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA19751 for freebsd-scsi-outgoing; Thu, 29 May 1997 18:05:04 -0700 (PDT) Received: from elvis.mu.org (elvis.mu.org [206.156.230.205]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA19743 for ; Thu, 29 May 1997 18:05:01 -0700 (PDT) Received: (from paul@localhost) by elvis.mu.org (8.8.5/8.8.5) id UAA00297 for freebsd-scsi@freebsd.org; Thu, 29 May 1997 20:04:51 -0500 (CDT) From: Paul Saab Message-Id: <199705300104.UAA00297@elvis.mu.org> Subject: Adaptec 2940 To: freebsd-scsi@freebsd.org Date: Thu, 29 May 1997 20:04:51 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Is it true that you can only use 2 of the connectors on the Adaptec 2940UW? I have 1 wide drive on the wide bus, 1 narrow drive on the narrow bus and 1 external tape backup. Can I use all three of these drive on all three connectors or do I have to put the tape on a different system? Paul Saab From owner-freebsd-scsi Thu May 29 18:29:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA21374 for freebsd-scsi-outgoing; Thu, 29 May 1997 18:29:51 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA21364 for ; Thu, 29 May 1997 18:29:49 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id TAA27776; Thu, 29 May 1997 19:29:43 -0600 (MDT) Message-Id: <199705300129.TAA27776@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Paul Saab cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Adaptec 2940 In-reply-to: Your message of "Thu, 29 May 1997 20:04:51 CDT." <199705300104.UAA00297@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 29 May 1997 20:26:54 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Is it true that you can only use 2 of the connectors on the Adaptec >2940UW? I have 1 wide drive on the wide bus, 1 narrow drive on >the narrow bus and 1 external tape backup. Can I use all three of >these drive on all three connectors or do I have to put the tape >on a different system? > >Paul Saab Yes it is true, but if you buy a narrow->wide adaptor for your narrow drive, you can have your cake and eat it too. I know that Adaptec sells converters that it considers up to spec. Check their web page. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Thu May 29 18:36:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA21795 for freebsd-scsi-outgoing; Thu, 29 May 1997 18:36:30 -0700 (PDT) Received: from iworks.InterWorks.org (deischen@iworks.interworks.org [128.255.18.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA21789 for ; Thu, 29 May 1997 18:36:27 -0700 (PDT) Received: (from deischen@localhost) by iworks.InterWorks.org (8.7.5/) id UAA15483; Thu, 29 May 1997 20:38:19 -0500 (CDT) Message-Id: <199705300138.UAA15483@iworks.InterWorks.org> Date: Thu, 29 May 1997 20:38:19 -0500 (CDT) From: "Daniel M. Eischen" To: freebsd-scsi@FreeBSD.ORG, paul@mu.org Subject: Re: Adaptec 2940 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Is it true that you can only use 2 of the connectors on the Adaptec > 2940UW? I have 1 wide drive on the wide bus, 1 narrow drive on > the narrow bus and 1 external tape backup. Can I use all three of > these drive on all three connectors or do I have to put the tape > on a different system? Yep, you can only use 2 of the three connectors. What I do is buy an internal SCSI-2 to external MD-50 SCSI-2 adapter. It'll either mount in an unused punch-out in the back of your chasis or it can mount in a plate at an unused slot on your motherboard. You run the _end_ of your internal 50-pin ribbon cable over to this adapter. This gives you a dense 50-pin externel SCSI connection. We get our specialty SCSI cables and adapters from C.S. Electronics. You want the SCSI-2 Ribbon Adaptor, see http://www.scsi-cables.com/line/adapt.htm for more info. Dan Eischen deischen@iworks.InterWorks.org From owner-freebsd-scsi Thu May 29 22:08:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA29329 for freebsd-scsi-outgoing; Thu, 29 May 1997 22:08:02 -0700 (PDT) Received: from charon.finall.com (charon.finall.com [206.246.160.131]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA29280 for ; Thu, 29 May 1997 22:07:59 -0700 (PDT) Received: from exchange.finall.com (exchange.finall.com [206.246.160.132]) by charon.finall.com (8.8.6.Beta3/8.6.12) with SMTP id BAA14755 for ; Fri, 30 May 1997 01:07:50 -0400 (EDT) Received: by exchange.finall.com with Microsoft Exchange (IMC 4.0.837.3) id <01BC6C95.E4EAA0C0@exchange.finall.com>; Fri, 30 May 1997 01:07:50 -0400 Message-ID: From: "Jung, Michael" To: "'scsi@freebsd.org'" Subject: FW: Brain dead issue...... Date: Fri, 30 May 1997 01:07:48 -0400 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.837.3 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Here is my hardware: Dual P120 Adapater 394X Barracuda Boot (Wide) Iomega Jaz dive (SCSI-II) Some background.... I have been using the boot loader to support multiple drives/partitions (NT for work) and (BSD for work :).... My secondary drive died at home and my employeror provided me with a Jaz drive (and a zillion disks!!).... However I cannot get the boot loader to start BSD (Free/Net/Open or Linux) of the Jaz drive...... What gives.... ????? TIA --mikej Michael Jung mikej@finall.com mikej@mikej.com >---------- >From: Steve Passe[SMTP:smp@csn.net] >Sent: Friday, May 30, 1997 1:01 AM >To: Jung, Michael >Subject: Re: Brain dead issue...... > >Hi, > >>(Since this seems to be a bootloader issue where would you suggest I go >>?) > >scsi@freebsd.org > >-- >Steve Passe | powered by >smp@csn.net | Symmetric MultiProcessor FreeBSD > > > From owner-freebsd-scsi Fri May 30 00:21:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA03822 for freebsd-scsi-outgoing; Fri, 30 May 1997 00:21:05 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA03805 for ; Fri, 30 May 1997 00:21:01 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA23226 for scsi@FreeBSD.ORG; Fri, 30 May 1997 09:20:53 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA07316; Fri, 30 May 1997 08:53:45 +0200 (MET DST) Message-ID: <19970530085345.AB01517@uriah.heep.sax.de> Date: Fri, 30 May 1997 08:53:45 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: scsi@FreeBSD.ORG Subject: Re: ZIP drive eject References: <199705281716.OAA16552@gaia.coppe.ufrj.br> <19970529170249.26384@ct.picker.com> <19970529233700.VT43737@uriah.heep.sax.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: <19970529233700.VT43737@uriah.heep.sax.de>; from J Wunsch on May 29, 1997 23:37:00 +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As J Wunsch wrote: > > Is it possible to eject a ZIP via S/W when using the "sd" driver? > > No. Ooops. Of course, i forgot about scsi(8). scsi -f /dev/rsdX.ctl -s 30 -c "1b 0 0 0 0:b6 v:b1 v:b1 0" $loej $start with $loej $start action 0 0 stop, don't eject medium 1 0 stop & eject 0 1 start, but don't try to load medium 1 1 start & load medium The command is optional, and not all combinations need to be supported -- obviously. A DAT or caddy CD-ROM drive would support ejecting, but not loading. -- 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. ;-) From owner-freebsd-scsi Fri May 30 02:39:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA08263 for freebsd-scsi-outgoing; Fri, 30 May 1997 02:39:15 -0700 (PDT) Received: from robkaos.ruhr.de (robkaos.ruhr.de [141.39.227.87]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id CAA08258 for ; Fri, 30 May 1997 02:39:11 -0700 (PDT) Received: by robkaos.ruhr.de (/\oo/\ Smail3.1.29.1 #29.1) id ; Fri, 30 May 97 11:38 MET DST Message-Id: From: robsch@robkaos.ruhr.de (Robert Schien) Subject: How to turn off DAT compression To: freebsd-scsi@freebsd.org Date: Fri, 30 May 1997 11:38:26 +0200 (MET DST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have an Archive Python DAT drive (28388-XXX.494) and want to turn off the compression mode. The reason is I get NCR timeout messages (there is a SC-200 in my P6NP5 system) when I write files to tape which are highly compressible. BTW, when this happens the DAT is winded back and forth wildly and data which are on earlier sessions (or partitions or volumes, I don't know what the correct term is when you have miltiple parts on a tape) are destroyed. Two DAT tapes I have were so heavily trashed that the DAT drive refused even to to erase them. Here are some of the error messages: May 29 13:46:21 robkaos /kernel: ncr0: have to clear fifos. May 29 13:46:21 robkaos /kernel: ncr0: restart (fatal error). May 29 13:46:21 robkaos /kernel: st1: COMMAND FAILED (9 ff) @f0637800. May 29 13:46:27 robkaos /kernel: ncr0: timeout ccb=f0637800 (skip) May 29 13:47:24 robkaos /kernel: ncr0: timeout ccb=f0658e00 (skip) May 29 13:47:25 robkaos /kernel: st1: 5.0 MB/s (200 ns, offset 8) May 29 13:47:25 robkaos /kernel: sd1: 10.0 MB/s (100 ns, offset 8) May 29 13:50:29 robkaos /kernel: ncr0: timeout ccb=f0658e00 (skip) May 29 13:50:30 robkaos /kernel: st1: MEDIUM ERROR asc:3,2 Excessive write errors BTW, the DAT cartrdges ware brand new (Verbatim). Robert P.S.: The system is -current (2 weeks old). From owner-freebsd-scsi Fri May 30 04:15:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA11305 for freebsd-scsi-outgoing; Fri, 30 May 1997 04:15:03 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA11289; Fri, 30 May 1997 04:14:53 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-40.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA13095 (5.67b/IDA-1.5); Fri, 30 May 1997 13:14:45 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id NAA03457; Fri, 30 May 1997 13:14:45 +0200 (CEST) X-Face: " Date: Fri, 30 May 1997 13:14:44 +0200 From: Stefan Esser To: Robert Schien Cc: freebsd-scsi@FreeBSD.ORG, Stefan Esser Subject: Re: How to turn off DAT compression References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Robert Schien on Fri, May 30, 1997 at 11:38:26AM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 30, Robert Schien wrote: > > I have an Archive Python DAT drive (28388-XXX.494) and want to turn > off the compression mode. The reason is I get NCR timeout messages > (there is a SC-200 in my P6NP5 system) when I write files to tape > which are highly compressible. BTW, when this happens the DAT Hmmm, I don't see how that could cause any problems! I'm using an HP1533 DAT with compression enabled for all my backups, and it never showed the lightest problems ... > is winded back and forth wildly and data which are on earlier This winding forward and backward may indicate a drive problem. Did you remember to clean the R/W head with a cleaning cartridge, at least every 50 hours of use ? (That may be 20 to 50 full backups, depending on your system's specifics ...) > sessions (or partitions or volumes, I don't know what the correct > term is when you have miltiple parts on a tape) are destroyed. Two DAT tapes I > have were so heavily trashed that the DAT drive refused even to to > erase them. Here are some of the error messages: > > May 29 13:46:21 robkaos /kernel: ncr0: have to clear fifos. > May 29 13:46:21 robkaos /kernel: ncr0: restart (fatal error). There should have been some (cryptic :) error message above, which I guess might help. > May 29 13:46:21 robkaos /kernel: st1: COMMAND FAILED (9 ff) @f0637800. > May 29 13:46:27 robkaos /kernel: ncr0: timeout ccb=f0637800 (skip) > May 29 13:47:24 robkaos /kernel: ncr0: timeout ccb=f0658e00 (skip) > May 29 13:47:25 robkaos /kernel: st1: 5.0 MB/s (200 ns, offset 8) > May 29 13:47:25 robkaos /kernel: sd1: 10.0 MB/s (100 ns, offset 8) You got an IBM disk drive ? :) > May 29 13:50:29 robkaos /kernel: ncr0: timeout ccb=f0658e00 (skip) > May 29 13:50:30 robkaos /kernel: st1: MEDIUM ERROR asc:3,2 Excessive write errors Well, this is not a driver message, but a message sent by your drive !!! > BTW, the DAT cartrdges ware brand new (Verbatim). > > Robert > > P.S.: The system is -current (2 weeks old). And the DAT drive ? :) Guess you should first try cleaning your drive's heads. As long as you get the MEDIUM ERROR messages, there is no way I could do anything for you ... Gruss, STefan From owner-freebsd-scsi Fri May 30 09:31:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA23659 for freebsd-scsi-outgoing; Fri, 30 May 1997 09:31:18 -0700 (PDT) Received: from robkaos.ruhr.de (robkaos.ruhr.de [141.39.227.87]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA23644; Fri, 30 May 1997 09:31:03 -0700 (PDT) Received: by robkaos.ruhr.de (/\oo/\ Smail3.1.29.1 #29.1) id ; Fri, 30 May 97 18:30 MET DST Message-Id: From: robsch@robkaos.ruhr.de (Robert Schien) Subject: Re: How to turn off DAT compression In-Reply-To: <19970530131444.53612@x14.mi.uni-koeln.de> from Stefan Esser at "May 30, 97 01:14:44 pm" To: se@freebsd.org (Stefan Esser) Date: Fri, 30 May 1997 18:30:18 +0200 (MET DST) Cc: freebsd-scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > This winding forward and backward may indicate a drive > problem. Did you remember to clean the R/W head with > a cleaning cartridge, at least every 50 hours of use ? > (That may be 20 to 50 full backups, depending on your > system's specifics ...) Yes, I tried a cleaning cartridge. Unfortunately, the DAT drive ejected it 10 seconds after loading :-( > > > sessions (or partitions or volumes, I don't know what the correct > > term is when you have miltiple parts on a tape) are destroyed. Two DAT tapes I > > > May 29 13:46:21 robkaos /kernel: st1: COMMAND FAILED (9 ff) @f0637800. > > May 29 13:46:27 robkaos /kernel: ncr0: timeout ccb=f0637800 (skip) > > May 29 13:47:24 robkaos /kernel: ncr0: timeout ccb=f0658e00 (skip) > > May 29 13:47:25 robkaos /kernel: st1: 5.0 MB/s (200 ns, offset 8) > > May 29 13:47:25 robkaos /kernel: sd1: 10.0 MB/s (100 ns, offset 8) > > You got an IBM disk drive ? :) No, Conner 2105S. > > > May 29 13:50:29 robkaos /kernel: ncr0: timeout ccb=f0658e00 (skip) > > May 29 13:50:30 robkaos /kernel: st1: MEDIUM ERROR asc:3,2 Excessive write errors > > Well, this is not a driver message, but a message sent > by your drive !!! > > > BTW, the DAT cartrdges ware brand new (Verbatim). > > > > Robert > > > > P.S.: The system is -current (2 weeks old). > > And the DAT drive ? :) Two years! > > Guess you should first try cleaning your drive's heads. > As long as you get the MEDIUM ERROR messages, there is > no way I could do anything for you ... > I don't think that the MEDIUM ERROR message is 'real'. Under normal conditions (i.e. transfering files which are not easily compressible like audio files) there isn't the slightest problem with the drive. ONLY when transfering files which can be shrinked to 1/10th of their original size by gzip the DAT drive gets crazy. My theory is that there is some problem with the data transfer rate: when reading or writing compressible data the transfer rate increases from a few hundred kb/s to MB/s and my slow PPro-200 isn't capable to transfer the data :-) Robert From owner-freebsd-scsi Fri May 30 10:06:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA26102 for freebsd-scsi-outgoing; Fri, 30 May 1997 10:06:12 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA26092 for ; Fri, 30 May 1997 10:06:07 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-40.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA19495 (5.67b/IDA-1.5 for ); Fri, 30 May 1997 19:04:30 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id TAA04892; Fri, 30 May 1997 19:04:30 +0200 (CEST) X-Face: " Date: Fri, 30 May 1997 19:04:29 +0200 From: Stefan Esser To: Robert Schien Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: How to turn off DAT compression References: <19970530131444.53612@x14.mi.uni-koeln.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Robert Schien on Fri, May 30, 1997 at 06:30:18PM +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 30, Robert Schien wrote: > Yes, I tried a cleaning cartridge. Unfortunately, the DAT > drive ejected it 10 seconds after loading :-( Hmmm, that may be normal behaviour ... Did the information supplied with the cartridge indicate the cleaning would take longer ? > > > May 29 13:50:30 robkaos /kernel: st1: MEDIUM ERROR asc:3,2 Excessive write errors > > > > Well, this is not a driver message, but a message sent > > by your drive !!! > > And the DAT drive ? :) > Two years! Depending on the number of backups performed, the head may have been worn out and may need to be replaced ... Early DAT drives had head life times in the low thousands of hours. If you do daily backups of 2GB total, the drive will be busy for some 2 hours a day. 1000 operating hours are reached after 1.5 years, if the drive is only used for the backups ... You may find some information on claimed head life time in your drives docs ... > I don't think that the MEDIUM ERROR message is 'real'. Under normal Well, how could it NOT be real ? You've got to understand the way this message originated: The driver issued a write request, the drive didn't succeed executing it, and returned an error status. The generic SCSI driver than sent an INQUIRY command to find out about the reason for the failure, and the drive was very specific in pointing out a MEDIUM ERROR. > conditions (i.e. transfering files which are not easily compressible like > audio files) there isn't the slightest problem with the drive. > ONLY when transfering files which can be shrinked to 1/10th of their > original size by gzip the DAT drive gets crazy. My theory is that > there is some problem with the data transfer rate: when reading or > writing compressible data the transfer rate increases from a few > hundred kb/s to MB/s and my slow PPro-200 isn't capable to transfer > the data :-) No, there should never be a problem because of too low a data rate. The drive will stop streaming, and will wait for more data to arrive before it begins writing again. If your drive got an 1MB buffer, and that buffer contains uncompressed data, then writing the buffer will take some 1.5 seconds (assuming the best case compression factor of 4). The drive may start/stop in 1.5 second periods, but that should not cause it to wind the tape forward and backward. If it does, then I suspect mechanical problems in the drive. You may try without data compression, anyway, but I would not trust any backup created under this conditions! Did you check, whether tapes written on that drive can be read back on another one ? Gruss, STefan From owner-freebsd-scsi Fri May 30 12:17:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA02883 for freebsd-scsi-outgoing; Fri, 30 May 1997 12:17:17 -0700 (PDT) Received: from destiny.erols.com (someone@destiny.erols.com [207.96.73.65]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA02865; Fri, 30 May 1997 12:16:51 -0700 (PDT) Received: from destiny.erols.com (someone@destiny.erols.com [207.96.73.65]) by destiny.erols.com (8.8.5/8.6.12) with SMTP id PAA21788; Fri, 30 May 1997 15:16:33 -0400 (EDT) Date: Fri, 30 May 1997 15:16:33 -0400 (EDT) From: John Dowdal To: Robert Schien cc: Stefan Esser , freebsd-scsi@FreeBSD.ORG Subject: Re: How to turn off DAT compression 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 On Fri, 30 May 1997, Robert Schien wrote: > > > > This winding forward and backward may indicate a drive > > problem. Did you remember to clean the R/W head with > > a cleaning cartridge, at least every 50 hours of use ? > > (That may be 20 to 50 full backups, depending on your > > system's specifics ...) > Yes, I tried a cleaning cartridge. Unfortunately, the DAT > drive ejected it 10 seconds after loading :-( This is exactly what the drive is supposed to do. It detects that it is a cleaning cartridge, and "does the right thing" (move about a foot of tape through the drive) John From owner-freebsd-scsi Fri May 30 12:57:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA04164 for freebsd-scsi-outgoing; Fri, 30 May 1997 12:57:49 -0700 (PDT) Received: from elvis.mu.org ([206.156.230.205]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA04158 for ; Fri, 30 May 1997 12:57:46 -0700 (PDT) Received: (from paul@localhost) by elvis.mu.org (8.8.5/8.8.5) id OAA20004 for freebsd-scsi@freebsd.org; Fri, 30 May 1997 14:57:33 -0500 (CDT) From: Paul Saab Message-Id: <199705301957.OAA20004@elvis.mu.org> Subject: CDROM strangeness To: freebsd-scsi@freebsd.org Date: Fri, 30 May 1997 14:57:32 -0500 (CDT) X-Mailer: ELM [version 2.4ME+ PL31H (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Here is the output from dmesg. What is funny is that I have 6 other machine exactly like this and this is the only one that gives me these errors on bootup. The only thing I changed on these machines was to disable the SCAM support on the controller and set the SCSI ID's on the drives. Anyway, what I am asking is what do the messages on the CDROM mean? Paul Saab Copyright (c) 1992-1996 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.1-RELEASE #0: Wed May 7 19:00:54 CDT 1997 root@henon.math.missouri.edu:/usr/src/sys/compile/rich CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xf9ff,MTRR,PGE,MCA,CMOV> real memory = 67108864 (65536K bytes) avail memory = 62660608 (61192K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 ahc0 rev 0 int a irq 10 on pci0:11 ahc0: aic7880 Wide Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "SEAGATE ST32155W 0362" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2049MB (4197405 512 byte sectors) (ahc0:1:0): "SEAGATE ST32155W 0362" type 0 fixed SCSI 2 sd1(ahc0:1:0): Direct-Access 2049MB (4197405 512 byte sectors) ahc0:A:5: refuses WIDE negotiation. Using 8bit transfers (ahc0:5:0): Unexpected busfree. LASTPHASE == 0x40 SEQADDR == 0x127 ahc0: board is not responding cmd fail (ahc0:5:0): SCB 0x0 - timed out in datain phase, SCSISIGI == 0x0 SEQADDR == 0x0 (ahc0:5:0): SCB 0: Yucky Immediate reset. Flags = 0x401 (ahc0:5:0): no longer in timeout ahc0: Issued Channel A Bus Reset. 1 SCBs aborted ahc0:A:5: refuses WIDE negotiation. Using 8bit transfers (ahc0:5:0): "MATSHITA CD-ROM CR-506 8S05" type 5 removable SCSI 2 cd0(ahc0:5:0): CD-ROM cd present [400000 x 2048 byte records] vx0 <3COM 3C905 Fast Etherlink XL PCI> rev 0 int a irq 9 on pci0:15 mii[*mii*] address 00:60:97:90:74:f4 vga0 rev 1 int a irq 11 on pci0:17 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface psm0 at 0x60-0x64 irq 12 on motherboard psm0: device ID 0 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in npx0 on motherboard npx0: INT 16 interface sd1(ahc0:1:0): UNIT ATTENTION asc:29,0 sd1(ahc0:1:0): Power on, reset, or bus device reset occurred field replaceable unit: 1 , retries:2 ----- End of forwarded message from Charlie Root ----- From owner-freebsd-scsi Fri May 30 13:17:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA05681 for freebsd-scsi-outgoing; Fri, 30 May 1997 13:17:08 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA05629 for ; Fri, 30 May 1997 13:15:42 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-40.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA21558 (5.67b/IDA-1.5 for ); Fri, 30 May 1997 22:12:05 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id WAA05746; Fri, 30 May 1997 22:12:02 +0200 (CEST) X-Face: " Date: Fri, 30 May 1997 22:12:02 +0200 From: Stefan Esser To: Dave Huang Cc: freebsd-scsi@FreeBSD.ORG, current-users@netbsd.org Subject: Re: ncr driver working well with 53c875? References: <19970527130149.33023@x14.mi.uni-koeln.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Dave Huang on Wed, May 28, 1997 at 09:06:43PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On May 28, Dave Huang wrote: > I don't actually know either, but from looking at their BIOS/driver > updates, I get the impression that ASUS does use the Symbios SDMS. > Anyone with an SC875 wish to confirm/deny? :) The SC-200 used SDMS in the system BIOS. The rumour I heard was, that the 875 comes with its own BIOS, which is not based on SDMS. But I don't know ... > I don't currently have any external devices, but if I ever get any, > they'll probably be narrow. I've already got an ASUS SC200 (53c810) that > I'm planning on keeping though, so I'll just use that for external > things... BTW, the Diamond FirePort 40 is another 875-based card with an > external narrow connector. I have heard about the Diamond FirePort using some variant of the 53c875 with a different PCI device ID. If somebody got such a card, I'd like to hear from you! > Yeah, wide cables seem to be quite expensive :( Does the Tekram's wide > cable have enough connectors for two drives? (i.e. at least three > connectors total). If it's only a single drive cable, I'll have to get > another cable anyways... The Tekram came with a WIDE cable for at least the controller and 2 drives (possibly for more, but I had to open my computer to tell you for sure and can't do that right now). Regards, STefan From owner-freebsd-scsi Fri May 30 13:35:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA06786 for freebsd-scsi-outgoing; Fri, 30 May 1997 13:35:14 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA06773 for ; Fri, 30 May 1997 13:35:04 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id OAA16662; Fri, 30 May 1997 14:34:59 -0600 (MDT) Message-Id: <199705302034.OAA16662@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Paul Saab cc: freebsd-scsi@FreeBSD.ORG Subject: Re: CDROM strangeness In-reply-to: Your message of "Fri, 30 May 1997 14:57:32 CDT." <199705301957.OAA20004@elvis.mu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 30 May 1997 15:32:01 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Here is the output from dmesg. What is funny is that I have 6 >other machine exactly like this and this is the only one that gives >me these errors on bootup. The only thing I changed on these machines >was to disable the SCAM support on the controller and set the SCSI >ID's on the drives. Anyway, what I am asking is what do the messages >on the CDROM mean? It means that the you should disable wide negotiation to your CDROM drive in SCSI-Select. > >Paul Saab -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Sat May 31 09:22:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA27710 for freebsd-scsi-outgoing; Sat, 31 May 1997 09:22:00 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id JAA27701 for ; Sat, 31 May 1997 09:21:57 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id SAA23882 for freebsd-scsi@FreeBSD.ORG; Sat, 31 May 1997 18:21:47 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id SAA21407; Sat, 31 May 1997 18:18:34 +0200 (MET DST) Message-ID: <19970531181833.SW30703@uriah.heep.sax.de> Date: Sat, 31 May 1997 18:18:33 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.ORG Subject: Re: How to turn off DAT compression References: X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Robert Schien on May 30, 1997 11:38:26 +0200 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Robert Schien wrote: > I have an Archive Python DAT drive (28388-XXX.494) and want to turn > off the compression mode. Not sure, i've never seen it really work, but did you ever try `mt comp'? The man page mentions it as being not implemented, but it's actually implemented. -- 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. ;-) From owner-freebsd-scsi Sat May 31 12:57:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA09709 for freebsd-scsi-outgoing; Sat, 31 May 1997 12:57:19 -0700 (PDT) Received: from robkaos.ruhr.de (robkaos.ruhr.de [141.39.227.87]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA09698 for ; Sat, 31 May 1997 12:57:13 -0700 (PDT) Received: by robkaos.ruhr.de (/\oo/\ Smail3.1.29.1 #29.1) id ; Sat, 31 May 97 21:54 MET DST Message-Id: From: robsch@robkaos.ruhr.de (Robert Schien) Subject: Re: How to turn off DAT compression In-Reply-To: <19970531181833.SW30703@uriah.heep.sax.de> from J Wunsch at "May 31, 97 06:18:33 pm" To: joerg_wunsch@uriah.heep.sax.de Date: Sat, 31 May 1997 21:54:48 +0200 (MET DST) Cc: freebsd-scsi@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > As Robert Schien wrote: > > > I have an Archive Python DAT drive (28388-XXX.494) and want to turn > > off the compression mode. > > Not sure, i've never seen it really work, but did you ever try `mt > comp'? The man page mentions it as being not implemented, but it's > actually implemented. > > -- Unfortunately, 'mt comp' replies with the usage help :-( Robert From owner-freebsd-scsi Sat May 31 15:33:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA20168 for freebsd-scsi-outgoing; Sat, 31 May 1997 15:33:04 -0700 (PDT) Received: from vodka.sublink.org (root@vodka.sublink.ORG [194.184.73.88]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA20162 for ; Sat, 31 May 1997 15:32:59 -0700 (PDT) Received: from nameron by vodka.sublink.org via rmail with uucp id for freebsd-scsi@freebsd.org; Sun, 1 Jun 1997 00:32:22 +0200 (MET DST) (Smail-3.2.0.94 1997-Apr-22 #1 built DST-Apr-23) Received: from hp-dyno.smd by nameron.smd.sublink.org with smtp (Smail3.1.28.1 #17) id m0wXwf2-0008EkC; Sun, 1 Jun 97 00:30 MET DST Received: by hp-dyno.smd (Smail3.1.28.1 #8) id m0wXxam-000JKwC; Sun, 1 Jun 97 00:29 MET Received: from luppolo.lpds.sublink.org (luppolo.lpds.sublink.org [192.9.200.50]) by radikkio.lpds.sublink.org (8.6.12/8.6.9) with ESMTP id PAA29685 for ; Fri, 30 May 1997 15:54:42 +0200 Received: (from wcp@localhost) by luppolo.lpds.sublink.org (8.6.12/8.6.9) id QAA00614; Fri, 30 May 1997 16:11:48 +0200 Date: Fri, 30 May 1997 16:11:48 +0200 Message-Id: <199705301411.QAA00614@luppolo.lpds.sublink.org> From: wcp@luppolo.lpds.sublink.org (Walter C. Pelissero) X-Attribution: WcP To: freebsd-scsi@freebsd.org Subject: ahc0 panic on cd mount Comments: Hyperbole mail buttons accepted, v3.18.5. Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can anyone explain me what this panic means? ahc0: target 0, lun 0 (sd0) timed out cd0(ahc0:2:0) BUS DEVICE RESET message queued. ahc0: target 0, lun 0 (sd0) timed out ahc0: Issued Channel A Bus Reset #2. 0 SCBs aborted panic: ahcintr: AWAITING_MSG for an SCB thatdoes not have a waiting message syncing disks... 6 6 6 6 6 6 6 6 6 6 6 6 6 giving up This happened on a Pentium PRO with and Adaptec 2940 running FreeBSD 2.1-RELEASE, during a mount of a probably faulty CD-ROM. Thanks. From owner-freebsd-scsi Sat May 31 15:35:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA20365 for freebsd-scsi-outgoing; Sat, 31 May 1997 15:35:35 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA20357; Sat, 31 May 1997 15:35:27 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA20779 (5.67b/IDA-1.5); Sun, 1 Jun 1997 00:35:49 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.7.5/8.6.12) id TAA01227; Sat, 31 May 1997 19:39:21 +0200 (MET DST) From: Wilko Bulte Message-Id: <199705311739.TAA01227@yedi.iaf.nl> Subject: Re: How to turn off DAT compression To: se@FreeBSD.ORG (Stefan Esser) Date: Sat, 31 May 1997 19:39:21 +0200 (MET DST) Cc: robsch@robkaos.ruhr.de, freebsd-scsi@FreeBSD.ORG In-Reply-To: <19970530190429.35326@x14.mi.uni-koeln.de> from "Stefan Esser" at May 30, 97 07:04:29 pm X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Stefan Esser wrote... > On May 30, Robert Schien wrote: > > Yes, I tried a cleaning cartridge. Unfortunately, the DAT > > drive ejected it 10 seconds after loading :-( > You've got to understand the way this message originated: [deleted] > The driver issued a write request, the drive didn't succeed > executing it, and returned an error status. The generic SCSI > driver than sent an INQUIRY command to find out about the A REQUEST SENSE I suppose. > reason for the failure, and the drive was very specific in > pointing out a MEDIUM ERROR. Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl - Arnhem, The Netherlands |/|/ / / /( (_) Do, or do not. There is no 'try' - Yoda -------------------------------------------------------------------------- From owner-freebsd-scsi Sat May 31 17:15:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA24461 for freebsd-scsi-outgoing; Sat, 31 May 1997 17:15:05 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA24456 for ; Sat, 31 May 1997 17:15:02 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id SAA11679; Sat, 31 May 1997 18:14:57 -0600 (MDT) Message-Id: <199706010014.SAA11679@pluto.plutotech.com> To: wcp@luppolo.lpds.sublink.org (Walter C. Pelissero) cc: freebsd-scsi@FreeBSD.ORG Subject: Re: ahc0 panic on cd mount In-reply-to: Your message of "Fri, 30 May 1997 16:11:48 +0200." <199705301411.QAA00614@luppolo.lpds.sublink.org> Date: Sat, 31 May 1997 19:11:46 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Can anyone explain me what this panic means? It means you should be running 2.1-stable not 2.1R. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Sat May 31 17:21:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA24762 for freebsd-scsi-outgoing; Sat, 31 May 1997 17:21:50 -0700 (PDT) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA24754 for ; Sat, 31 May 1997 17:21:47 -0700 (PDT) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id CAA01026 for freebsd-scsi@freebsd.org; Sun, 1 Jun 1997 02:21:42 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id CAA02278; Sun, 1 Jun 1997 02:04:47 +0200 (MET DST) Message-ID: <19970601020447.NP40641@uriah.heep.sax.de> Date: Sun, 1 Jun 1997 02:04:47 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@freebsd.org Subject: Re: How to turn off DAT compression References: <19970531181833.SW30703@uriah.heep.sax.de> X-Mailer: Mutt 0.60_p2-3,5,8-9 Mime-Version: 1.0 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 Reply-To: joerg_wunsch@uriah.heep.sax.de (Joerg Wunsch) In-Reply-To: ; from Robert Schien on May 31, 1997 21:54:48 +0200 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Robert Schien wrote: > > Not sure, i've never seen it really work, but did you ever try `mt > > comp'? The man page mentions it as being not implemented, but it's > > actually implemented. > Unfortunately, 'mt comp' replies with the usage help :-( Sure. It requires an argument, 0 to turn compression off, 1 to turn it on. -- 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. ;-)