From owner-freebsd-scsi Sun Mar 30 17:27:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA01632 for freebsd-scsi-outgoing; Sun, 30 Mar 1997 17:27:44 -0800 (PST) Received: from fcom.com (daemon@flamingo1.fcom.com [204.252.66.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id RAA01617 for ; Sun, 30 Mar 1997 17:27:41 -0800 (PST) Received: by fcom.com (8.6.13/FCOM-1.22) id RAA15873; Sun, 30 Mar 1997 17:27:34 -0800 Received: from flamingo1.fcom.com(204.252.66.1) by flamingo1.fcom.com via smap (V2.0beta) id xma015870; Sun, 30 Mar 97 17:27:27 -0800 Date: Sun, 30 Mar 1997 17:27:26 -0800 (PST) From: SubSolar To: scsi@freebsd.org Subject: Future Domain 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 Hey, what's the keyword to compile Future Domain SCSI controllers in FreeBSD kernel? Thanx. From owner-freebsd-scsi Sun Mar 30 23:52:53 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id XAA25241 for freebsd-scsi-outgoing; Sun, 30 Mar 1997 23:52:53 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id XAA25236 for ; Sun, 30 Mar 1997 23:52:49 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id JAA07055; Mon, 31 Mar 1997 09:52:17 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id JAA09224; Mon, 31 Mar 1997 09:50:20 +0200 (MET DST) Message-ID: <19970331095019.KN57727@uriah.heep.sax.de> Date: Mon, 31 Mar 1997 09:50:19 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: scsi@freebsd.org Cc: subsolar@flamingo1.fcom.com (SubSolar) Subject: Re: Future Domain 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 SubSolar on Mar 30, 1997 17:27:26 -0800 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As SubSolar wrote: > Hey, what's the keyword to compile Future Domain SCSI controllers in > FreeBSD kernel? Thanx. options NONEXISTENT :-) The FD-[89]50 are supported, they clone the Seagate ST-01 chips (the `sea' driver). Nothing very useful. The TMC-18xx family ain't supported yet. I've got a contribution by somebody who ported a driver from NetBSD/PAO to FreeBSD, but i didn't find the time to think over the file structure yet (some of the files don't fit quite into the FreeBSD tree), thus it's not imported yet. I will do this ``RSN''. (This is a PCI-only driver, is this what you want?) -- 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 Mon Mar 31 00:14:09 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA26131 for freebsd-scsi-outgoing; Mon, 31 Mar 1997 00:14:09 -0800 (PST) Received: from caliban.dihelix.com (caliban.mrtc.org [199.4.33.251]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA26121; Mon, 31 Mar 1997 00:14:05 -0800 (PST) Received: (from langfod@localhost) by caliban.dihelix.com (8.8.5/8.8.3) id WAA15500; Sun, 30 Mar 1997 22:14:02 -1000 (HST) Message-Id: <199703310814.WAA15500@caliban.dihelix.com> Subject: Problem with ccdconfig on 2.2 To: questions@freebsd.org, scsi@freebsd.org Date: Sun, 30 Mar 1997 22:14:02 -1000 (HST) From: "David Langford" X-blank-line: This space intentionaly left blank. 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 I am having a problem getting ccd's configured on the most recent 2.2 sup. Is MAKEDEV messed up? Thanks, -David Langford | langfod@dihelix.com # cd /dev # rm *ccd* # ./MAKEDEV ccd0 # ccdconfig -vc ccd0 128 0 /dev/sd2c /dev/sd3c ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Inappropriate file type or format Here is my dev listing, I dont know what is up with rccd0.ctl 0 brw-r----- 1 root wheel 21, 0 Mar 30 22:07 ccd0a 0 brw-r----- 1 root wheel 21, 1 Mar 30 22:07 ccd0b 0 brw-r----- 1 root wheel 21, 2 Mar 30 22:07 ccd0c 0 brw-r----- 1 root wheel 21, 3 Mar 30 22:07 ccd0d 0 brw-r----- 1 root wheel 21, 4 Mar 30 22:07 ccd0e 0 brw-r----- 1 root wheel 21, 5 Mar 30 22:07 ccd0f 0 brw-r----- 1 root wheel 21, 6 Mar 30 22:07 ccd0g 0 brw-r----- 1 root wheel 21, 7 Mar 30 22:07 ccd0h 0 crw------- 1 root wheel 74, 0x20000000 Mar 30 22:07 rccd0.ctl 0 crw-r----- 1 root wheel 74, 0 Mar 30 22:07 rccd0a 0 crw-r----- 1 root wheel 74, 1 Mar 30 22:07 rccd0b 0 crw-r----- 1 root wheel 74, 2 Mar 30 22:07 rccd0c 0 crw-r----- 1 root wheel 74, 3 Mar 30 22:07 rccd0d 0 crw-r----- 1 root wheel 74, 4 Mar 30 22:07 rccd0e 0 crw-r----- 1 root wheel 74, 5 Mar 30 22:07 rccd0f 0 crw-r----- 1 root wheel 74, 6 Mar 30 22:07 rccd0g 0 crw-r----- 1 root wheel 74, 7 Mar 30 22:07 rccd0h # dmesg 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-STABLE #1: Fri Mar 28 08:42:14 HST 1997 root@kedar:/usr/src/sys/compile/BADKEDAR CPU: Pentium Pro (199.43-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x619 Stepping=9 Features=0xfbff,MTRR,PGE,MCA,CMOV> real memory = 67108864 (65536K bytes) avail memory = 63553536 (62064K 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 de0 rev 18 int a irq 9 on pci0:11 de0: DE500-XA 21140 [10-100Mb/s] pass 1.2 de0: address 00:00:f8:03:0a:8d de0: enabling 10baseT port de1 rev 18 int a irq 10 on pci0:12 de1: DE500-XA 21140 [10-100Mb/s] pass 1.2 de1: address 00:00:f8:02:e5:af de1: enabling 10baseT port chip3 rev 1 on pci0:13 chip4 rev 1 on pci0:14 Probing for devices on PCI bus 1: ahc0 rev 0 int a irq 15 on pci1:4 ahc0: aic7880 Wide Channel A, SCSI Id=7, 16 SCBs ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "SEAGATE ST32171W 0338" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2061MB (4222640 512 byte sectors) sd0(ahc0:0:0): with 5168 cyls, 5 heads, and an average 163 sectors/track (ahc0:5:0): "ARCHIVE Python 28849-XXX 4.BT" type 1 removable SCSI 2 st0(ahc0:5:0): Sequential-Access density code 0x13, drive empty (ahc0:5:1): "ARCHIVE Python 28849-XXX 4.BT" type 8 removable SCSI 2 ch0(ahc0:5:1): Medium-Changer 4 slots, 1 drive, 1 picker probe0(ahc0:9:0): scsi_cmd probe0(ahc0:9:0): scsi_done (ahc0:9:0): command: 0,0,0,0,0,0-[0 bytes] probe0(ahc0:9:0): scsi_cmd probe0(ahc0:9:0): scsi_done (ahc0:9:0): command: 12,0,0,0,2c,0-[44 bytes] ------------------------------ 000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 016: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 032: 00 00 00 00 00 00 00 00 00 00 00 00 ------------------------------ ahc1 rev 0 int a irq 11 on pci1:5 ahc1: aic7880 Wide Channel B, SCSI Id=7, 16 SCBs ahc1: target 0 Tagged Queuing Device (ahc1:0:0): "SEAGATE ST34371W 0484" type 0 fixed SCSI 2 sd1(ahc1:0:0): Direct-Access 4148MB (8496884 512 byte sectors) sd1(ahc1:0:0): with 5172 cyls, 10 heads, and an average 164 sectors/track probe0(ahc1:9:0): scsi_cmd probe0(ahc1:9:0): scsi_done (ahc1:9:0): command: 0,0,0,0,0,0-[0 bytes] probe0(ahc1:9:0): scsi_cmd probe0(ahc1:9:0): scsi_done (ahc1:9:0): command: 12,0,0,0,2c,0-[44 bytes] ------------------------------ 000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 016: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 032: 00 00 00 00 00 00 00 00 00 00 00 00 ------------------------------ Probing for devices on PCI bus 2: ahc2 rev 0 int a irq 11 on pci2:4 ahc2: aic7880 Wide Channel A, SCSI Id=7, 16 SCBs ahc2: target 0 Tagged Queuing Device (ahc2:0:0): "SEAGATE ST34371W 0484" type 0 fixed SCSI 2 sd2(ahc2:0:0): Direct-Access 4148MB (8496884 512 byte sectors) sd2(ahc2:0:0): with 5172 cyls, 10 heads, and an average 164 sectors/track probe0(ahc2:9:0): scsi_cmd probe0(ahc2:9:0): scsi_done (ahc2:9:0): command: 0,0,0,0,0,0-[0 bytes] probe0(ahc2:9:0): scsi_cmd probe0(ahc2:9:0): scsi_done (ahc2:9:0): command: 12,0,0,0,2c,0-[44 bytes] ------------------------------ 000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 016: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 032: 00 00 00 00 00 00 00 00 00 00 00 00 ------------------------------ ahc3 rev 0 int a irq 10 on pci2:5 ahc3: aic7880 Wide Channel B, SCSI Id=7, 16 SCBs ahc3: target 0 Tagged Queuing Device (ahc3:0:0): "SEAGATE ST34371W 0484" type 0 fixed SCSI 2 sd3(ahc3:0:0): Direct-Access 4148MB (8496884 512 byte sectors) sd3(ahc3:0:0): with 5172 cyls, 10 heads, and an average 164 sectors/track probe0(ahc3:9:0): scsi_cmd probe0(ahc3:9:0): scsi_done (ahc3:9:0): command: 0,0,0,0,0,0-[0 bytes] probe0(ahc3:9:0): scsi_cmd probe0(ahc3:9:0): scsi_done (ahc3:9:0): command: 12,0,0,0,2c,0-[44 bytes] ------------------------------ 000: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 016: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 032: 00 00 00 00 00 00 00 00 00 00 00 00 ------------------------------ Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <10 virtual consoles, flags=0x0> 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 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A 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 ccd0-3: Concatenated disk drivers pid 628 (sort), uid 65534 on /: file system full st0(ahc0:5:0): NOT READY asc:3a,0 Medium not present ----- End of forwarded message from Charlie Root ----- From owner-freebsd-scsi Mon Mar 31 03:28:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id DAA10672 for freebsd-scsi-outgoing; Mon, 31 Mar 1997 03:28:22 -0800 (PST) Received: from dfw-ix2.ix.netcom.com (dfw-ix2.ix.netcom.com [206.214.98.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA10645; Mon, 31 Mar 1997 03:28:14 -0800 (PST) Received: (from smap@localhost) by dfw-ix2.ix.netcom.com (8.8.4/8.8.4) id FAA04104; Mon, 31 Mar 1997 05:27:42 -0600 (CST) Received: from wck-ca7-10.ix.netcom.com(204.31.231.42) by dfw-ix2.ix.netcom.com via smap (V1.3) id sma004004; Mon Mar 31 05:26:23 1997 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id DAA01199; Mon, 31 Mar 1997 03:22:27 -0800 (PST) Date: Mon, 31 Mar 1997 03:22:27 -0800 (PST) Message-Id: <199703311122.DAA01199@silvia.HIP.Berkeley.EDU> To: langfod@dihelix.com CC: questions@freebsd.org, scsi@freebsd.org In-reply-to: <199703310814.WAA15500@caliban.dihelix.com> (langfod@dihelix.com) Subject: Re: Problem with ccdconfig on 2.2 From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * # ccdconfig -vc ccd0 128 0 /dev/sd2c /dev/sd3c * ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Inappropriate file type or format Try "man 4 ccd" or read the FAQ. Satoshi From owner-freebsd-scsi Mon Mar 31 09:02:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA27281 for freebsd-scsi-outgoing; Mon, 31 Mar 1997 09:02:07 -0800 (PST) Received: from Campino.Informatik.RWTH-Aachen.DE (campino.Informatik.RWTH-Aachen.DE [137.226.116.240]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA27260; Mon, 31 Mar 1997 09:02:02 -0800 (PST) Received: from gilberto.physik.RWTH-Aachen.DE (gilberto.physik.rwth-aachen.de [137.226.31.2]) by Campino.Informatik.RWTH-Aachen.DE (RBI-Z-5/8.6.12) with ESMTP id TAA00837; Mon, 31 Mar 1997 19:02:00 +0200 (MET DST) Received: (from kuku@localhost) by gilberto.physik.RWTH-Aachen.DE (8.8.5/8.6.9) id TAA14285; Mon, 31 Mar 1997 19:15:14 +0200 (MET DST) From: Christoph Kukulies Message-Id: <199703311715.TAA14285@gilberto.physik.RWTH-Aachen.DE> Subject: Re: Problem with ccdconfig on 2.2 In-Reply-To: <199703310814.WAA15500@caliban.dihelix.com> from David Langford at "Mar 30, 97 10:14:02 pm" To: langfod@dihelix.com (David Langford) Date: Mon, 31 Mar 1997 19:15:12 +0200 (MET DST) Cc: questions@freebsd.org, scsi@freebsd.org Reply-To: Christoph Kukulies 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 am having a problem getting ccd's configured on the most recent 2.2 sup. > Is MAKEDEV messed up? > > Thanks, > -David Langford | langfod@dihelix.com > > # cd /dev > # rm *ccd* > # ./MAKEDEV ccd0 > > # ccdconfig -vc ccd0 128 0 /dev/sd2c /dev/sd3c > ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Inappropriate file type or format The disklabel -r results of the respective disks (sd2 sd3) would be interesting,too. I suspect they don't have a 4.2BSD entry. > > -- Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de From owner-freebsd-scsi Mon Mar 31 13:00:15 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA09861 for freebsd-scsi-outgoing; Mon, 31 Mar 1997 13:00:15 -0800 (PST) Received: from caliban.dihelix.com (caliban.mrtc.org [199.4.33.251]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA09856; Mon, 31 Mar 1997 13:00:11 -0800 (PST) Received: (from langfod@localhost) by caliban.dihelix.com (8.8.5/8.8.3) id KAA17468; Mon, 31 Mar 1997 10:58:56 -1000 (HST) Message-Id: <199703312058.KAA17468@caliban.dihelix.com> Subject: Re: Problem with ccdconfig on 2.2 In-Reply-To: <199703311715.TAA14285@gilberto.physik.RWTH-Aachen.DE> from Christoph Kukulies at "Mar 31, 97 07:15:12 pm" To: kuku@gilberto.physik.RWTH-Aachen.DE Date: Mon, 31 Mar 1997 10:58:56 -1000 (HST) Cc: langfod@dihelix.com, questions@freebsd.org, scsi@freebsd.org From: "David Langford" X-blank-line: This space intentionaly left blank. 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 Christoph Kukulies >> I am having a problem getting ccd's configured on the most recent 2.2 sup. >> Is MAKEDEV messed up? >> -David Langford | langfod@dihelix.com >> >> ccdconfig: ioctl (CCDIOCSET): /dev/ccd0c: Inappropriate file type or format > >The disklabel -r results of the respective disks (sd2 sd3) would be >interesting,too. >I suspect they don't have a 4.2BSD entry. >Christoph P. U. Kukulies kuku@gil.physik.rwth-aachen.de Yup, that was it. Silly me for thinking that since I had previously had the drive newfs'ed and mounted that disklabel would be okay :) I was concerned about MAKEDEV since the rccd0.ctl file had such different values from 2.1.7 to 2.2 and I didnt knwo what was really wrong. Thanks alot. Now I just need to figure out what interleave values to use. -David Langford langfod@dihelix.com From owner-freebsd-scsi Mon Mar 31 13:35:41 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA12062 for freebsd-scsi-outgoing; Mon, 31 Mar 1997 13:35:41 -0800 (PST) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id NAA12054; Mon, 31 Mar 1997 13:35:27 -0800 (PST) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA26553; Mon, 31 Mar 1997 13:35:27 -0800 Date: Mon, 31 Mar 1997 13:35:27 -0800 (PST) From: "Brian N. Handy" To: freebsd-scsi@freebsd.org Cc: joerg@freebsd.org Subject: Philips CDwriter Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Heya Folks, Just picked up a Philips CDD 2600 today to test out with the CD writer software, and I have a minor problem. It probes thusly: FreeBSD 2.2.1-RELEASE #0: Wed Mar 26 11:36:10 PST 1997 [...] (ncr0:2:0): "PHILIPS CDD2600 1.07" type 5 removable SCSI 2 cd0(ncr0:2:0): CD-ROM can't get the size Ummm...I have a feeling this needs to probe as worm0 instead of cd0. Any ideas here? Thanks, Brian From owner-freebsd-scsi Mon Mar 31 15:15:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA16549 for freebsd-scsi-outgoing; Mon, 31 Mar 1997 15:15:18 -0800 (PST) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA16520; Mon, 31 Mar 1997 15:15:01 -0800 (PST) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA18489; Mon, 31 Mar 1997 15:15:01 -0800 Date: Mon, 31 Mar 1997 15:15:00 -0800 (PST) From: "Brian N. Handy" Reply-To: "Brian N. Handy" To: freebsd-scsi@freebsd.org Cc: joerg@freebsd.org Subject: Re: Philips CDwriter In-Reply-To: Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi again! [Re: I have a Philips CDD2600 CD writer on my machine.] I've figured out that I need an entry in scsiconf.c for my driver, so for the moment I've zero'ed out the entry for the CDD2000 writer and replaced it with the probe message for my CDR. So OK, now we have: (ncr0:2:0): "PHILIPS CDD2600 1.07" type 5 removable SCSI 2 worm0(ncr0:2:0): Write-Once Which is cool! I don't quite know what has to happen to *add* another entry for this, I'm a pretty lame programmer so far. Anyway, the problem now happens when I try to access the drive: # scsi -f /dev/rworm0.ctl -c "0 0 0 0 0 0" >/dev/null 2>&1 # wormcontrol select PHILIPS CDD2600 wormcontrol: open(/dev/rworm0): Device not configured # (I presume the above select is looking for the string out of worm.c, which I've changed to match this as well.) So...again, I'm stuck, just a bit further along. What next? Thanks, Brian From owner-freebsd-scsi Mon Mar 31 15:55:18 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA19992 for freebsd-scsi-outgoing; Mon, 31 Mar 1997 15:55:18 -0800 (PST) Received: from vodka.sublink.org (root@vodka.sublink.ORG [194.184.73.88]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA19981 for ; Mon, 31 Mar 1997 15:55:14 -0800 (PST) Received: from nameron by vodka.sublink.org with uucp (Smail3.1.29.1 #3) id m0wBquu-001bhOC; Tue, 1 Apr 97 01:55 MET DST Received: from hp-dyno.smd by nameron.smd.sublink.org with smtp (Smail3.1.28.1 #17) id m0wBqsE-0008EYC; Tue, 1 Apr 97 01:52 MET DST Received: by hp-dyno.smd (Smail3.1.28.1 #8) id m0wBrnX-000JKpC; Tue, 1 Apr 97 01:51 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 TAA06423 for ; Mon, 31 Mar 1997 19:07:33 +0200 Received: (from wcp@localhost) by luppolo.lpds.sublink.org (8.6.12/8.6.9) id TAA08807; Mon, 31 Mar 1997 19:41:48 +0200 Date: Mon, 31 Mar 1997 19:41:48 +0200 Message-Id: <199703311741.TAA08807@luppolo.lpds.sublink.org> From: wcp@luppolo.lpds.sublink.org (Walter C. Pelissero) X-Attribution: WcP To: freebsd-scsi@freebsd.org Subject: wrong reads from CD-ROM Reply-to: wcp@lpds.sublink.org Comments: Hyperbole mail buttons accepted, v3.18.5. Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does anybody know why my Goldstar CD-ROM (GCD-R320) start to read wrongly without any complain from the device driver? I simply cp /cdrom/some.file /var/tmp and then cmp /cdrom/some.file /var/tmp/some.file and files differ. No error from cp nor from the device driver. The CD-ROM reader is hooked on an Adaptec 2940 and on the same scsi bus there is a Quantum Fireball1080S hard disk and a HP C1533A DAT, both working well. So I belive it shouldn't be a termination problem. Any help will be appreciated. From owner-freebsd-scsi Mon Mar 31 16:29:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA23521 for freebsd-scsi-outgoing; Mon, 31 Mar 1997 16:29:57 -0800 (PST) Received: from dfw-ix14.ix.netcom.com (dfw-ix14.ix.netcom.com [206.214.98.14]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA23514; Mon, 31 Mar 1997 16:29:53 -0800 (PST) Received: (from smap@localhost) by dfw-ix14.ix.netcom.com (8.8.4/8.8.4) id SAA18119; Mon, 31 Mar 1997 18:28:27 -0600 (CST) Received: from wck-ca7-10.ix.netcom.com(204.31.231.42) by dfw-ix14.ix.netcom.com via smap (V1.3) id sma018082; Mon Mar 31 18:27:54 1997 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id QAA03196; Mon, 31 Mar 1997 16:27:47 -0800 (PST) Date: Mon, 31 Mar 1997 16:27:47 -0800 (PST) Message-Id: <199704010027.QAA03196@silvia.HIP.Berkeley.EDU> To: langfod@dihelix.com CC: kuku@gilberto.physik.RWTH-Aachen.DE, langfod@dihelix.com, questions@freebsd.org, scsi@freebsd.org In-reply-to: <199703312058.KAA17468@caliban.dihelix.com> (langfod@dihelix.com) Subject: Re: Problem with ccdconfig on 2.2 From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * Thanks alot. Now I just need to figure out what interleave values to use. man 4 ccd? :) Satoshi From owner-freebsd-scsi Mon Mar 31 17:21:39 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA26289 for freebsd-scsi-outgoing; Mon, 31 Mar 1997 17:21:39 -0800 (PST) Received: from caliban.dihelix.com (caliban.mrtc.org [199.4.33.251]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA26284; Mon, 31 Mar 1997 17:21:35 -0800 (PST) Received: (from langfod@localhost) by caliban.dihelix.com (8.8.5/8.8.3) id PAA18175; Mon, 31 Mar 1997 15:21:03 -1000 (HST) Message-Id: <199704010121.PAA18175@caliban.dihelix.com> Subject: Re: Problem with ccdconfig on 2.2 In-Reply-To: <199704010027.QAA03196@silvia.HIP.Berkeley.EDU> from Satoshi Asami at "Mar 31, 97 04:27:47 pm" To: asami@vader.cs.berkeley.edu (Satoshi Asami) Date: Mon, 31 Mar 1997 15:21:02 -1000 (HST) Cc: langfod@dihelix.com, kuku@gilberto.physik.RWTH-Aachen.DE, questions@freebsd.org, scsi@freebsd.org From: "David Langford" X-blank-line: This space intentionaly left blank. 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 > * Thanks alot. Now I just need to figure out what interleave values to use. > >man 4 ccd? :) >Satoshi I have RTFM'ed :) Doesn't mean I am unconfused though :-/ The problems I run into are: in the man page it talks about ther being a difference between striping for reads versus writes. I dont see this being possible when I look at ccdconfig. Also the way sysinstall configured my disk they only have one track. I dont think I want my interleave factor to be 4 million blocks. So far I have been doing different interleaves and then running iozone to see which it likes best. Thanks, -David Langford langfod@dihelix.com From owner-freebsd-scsi Mon Mar 31 18:58:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA02497 for freebsd-scsi-outgoing; Mon, 31 Mar 1997 18:58:40 -0800 (PST) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id SAA02487; Mon, 31 Mar 1997 18:58:27 -0800 (PST) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA21059; Mon, 31 Mar 1997 18:58:27 -0800 Date: Mon, 31 Mar 1997 18:58:27 -0800 (PST) From: "Brian N. Handy" To: freebsd-scsi@freebsd.org Cc: joerg@freebsd.org Subject: Re: Philips CDwriter In-Reply-To: Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk OK, one last time ... I've been all through sys/scsi/scsiconf.c and worm.c and made the appropriate changes so that my drive is recognized as a worm drive. Then this happens: # wormcontrol select PHILIPS CDD2600 wormcontrol: open(/dev/rworm0): Device not configured # So, I think to myself...."OK, my drive must want a different set of SCSI commands to drive it. Sure is weird they'd go with something different from the CDD 521 series though..." Finally this seemed weird enough I actually looked through the docs that came with the drive. Sure enough, I see this: "The CDD 2600 is compatible with old Philips CDD 522's and 521's..." [paraphrased] Which means I probably have something else screwed up. I can't figure out what the problem is. I've done the following: ./sh MAKEDEV worm I've put this line in my kernel config file: device worm0 at scbus? # SCSI worm There's just not much else I can do! Joerg! Help! What else could I have messed up? Thanks..... Brian From owner-freebsd-scsi Mon Mar 31 19:43:00 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA05213 for freebsd-scsi-outgoing; Mon, 31 Mar 1997 19:43:00 -0800 (PST) Received: from dfw-ix16.ix.netcom.com (dfw-ix16.ix.netcom.com [206.214.98.16]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA05196; Mon, 31 Mar 1997 19:42:53 -0800 (PST) Received: (from smap@localhost) by dfw-ix16.ix.netcom.com (8.8.4/8.8.4) id VAA28794; Mon, 31 Mar 1997 21:42:09 -0600 (CST) Received: from wck-ca7-10.ix.netcom.com(204.31.231.42) by dfw-ix16.ix.netcom.com via smap (V1.3) id sma028667; Mon Mar 31 21:41:34 1997 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id TAA03903; Mon, 31 Mar 1997 19:40:32 -0800 (PST) Date: Mon, 31 Mar 1997 19:40:32 -0800 (PST) Message-Id: <199704010340.TAA03903@silvia.HIP.Berkeley.EDU> To: chuckr@glue.umd.edu CC: freebsd-hardware@freebsd.org, scsi@freebsd.org Reply-to: scsi@freebsd.org In-reply-to: (message from Chuck Robey on Mon, 31 Mar 1997 21:30:01 -0500 (EST)) Subject: Re: Hard disk problems From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk [crossposted to SCSI, with reply set to there] * [I sent this message to hackers, where it got no response, so maybe I * should have sent it here. Apologies to those who will have seen it * twice.] I don't read hackers because the noise level is so high. ;) * I was wondering if someone can explain the error message I'm suddenly * seeing on bootup of one of my systems. It hangs with the message: * * ncr0: SCSI phase error fixup: CCB already dequeued (0xf2467200) * ncr0 timeout ccb=f2466600 skip * ncr0 timeout ccb=f2466800 skip * ncr0 timeout ccb=f2466a00 skip * ncr0 timeout ccb=f2467200 skip * (hangs here) I have seen something very similar on my system. The Micropolis 3243WT (which I got as a replacement to an older 3243W) doesn't boot 3 out of 4 times with "ncr0 timeout" messages (I don't get the "already dequeued" part, though). The other two disks (Atlas I and II) don't have this problem. Also, removing the CDROM (the only narrow device in the system) alleviated the symptoms somewhat (booted 3 out of 4 times). * I need to know what it means, and if there's any way to recover from it * without having to lose the whole disk (my boot disk, darn it!) I get this * error on the system after it does the full fsck (successfully), and the * system has (in total) 2 - 2G disks (this is the first one), 1 - 200 meg * disk, and one cdrom, all scsi, all hooked to one ncr 825 controller * (Tyan). Well, when I moved the Micropolis to an Adaptec 2940UW, everything started working again. ;) Satoshi From owner-freebsd-scsi Mon Mar 31 22:24:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA13341 for freebsd-scsi-outgoing; Mon, 31 Mar 1997 22:24:13 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id WAA13336 for ; Mon, 31 Mar 1997 22:24:09 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA23253; Tue, 1 Apr 1997 08:23:34 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA14564; Tue, 1 Apr 1997 08:13:10 +0200 (MET DST) Message-ID: <19970401081310.FQ14306@uriah.heep.sax.de> Date: Tue, 1 Apr 1997 08:13:10 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@FreeBSD.ORG Cc: handy@sag.space.lockheed.com (Brian N. Handy) Subject: Re: Philips CDwriter 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 Brian N. Handy on Mar 31, 1997 15:15:00 -0800 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Brian N. Handy wrote: > (ncr0:2:0): "PHILIPS CDD2600 1.07" type 5 removable SCSI 2 > worm0(ncr0:2:0): Write-Once > > Which is cool! I don't quite know what has to happen to *add* another > entry for this, I'm a pretty lame programmer so far. Anyway, the problem > now happens when I try to access the drive: It would probably have been sufficient to turn the CDD2000 entry into "CDD*". I assume "CDD" is Philips's term for a CD-R drive. -- 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 Mon Mar 31 22:24:33 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA13382 for freebsd-scsi-outgoing; Mon, 31 Mar 1997 22:24:33 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id WAA13360 for ; Mon, 31 Mar 1997 22:24:23 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id IAA23260; Tue, 1 Apr 1997 08:24:15 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id IAA14595; Tue, 1 Apr 1997 08:20:07 +0200 (MET DST) Message-ID: <19970401082007.ZO53870@uriah.heep.sax.de> Date: Tue, 1 Apr 1997 08:20:07 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@freebsd.org Cc: handy@sag.space.lockheed.com (Brian N. Handy) Subject: Re: Philips CDwriter 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 Brian N. Handy on Mar 31, 1997 18:58:27 -0800 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Brian N. Handy wrote: > I've been all through sys/scsi/scsiconf.c and worm.c and made the > appropriate changes so that my drive is recognized as a worm drive. > > Then this happens: > > # wormcontrol select PHILIPS CDD2600 > wormcontrol: open(/dev/rworm0): Device not configured > # You have also changed the string in worm.c? This wasn't necessary. You could have used `wormcontrol select PHILIPS CDD2000', or even `wormcontrol select HP 4020i' (which is effectively the same). The obvious question: there is a medium in the drive when you do the above? It fails even when issued repeatedly? If all else fails, you gotta turn on SCSIDEBUG, and see on which SCSI command it chokes. -- 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 Apr 1 06:40:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA04482 for freebsd-scsi-outgoing; Tue, 1 Apr 1997 06:40:51 -0800 (PST) Received: from silver.sms.fi (silver.sms.fi [194.111.122.17]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA04463 for ; Tue, 1 Apr 1997 06:40:43 -0800 (PST) Received: (from pete@localhost) by silver.sms.fi (8.8.5/8.7.3) id RAA00409; Tue, 1 Apr 1997 17:40:40 +0300 (EEST) Date: Tue, 1 Apr 1997 17:40:40 +0300 (EEST) Message-Id: <199704011440.RAA00409@silver.sms.fi> From: Petri Helenius To: freebsd-scsi@freebsd.org Subject: CDDA battles, round three Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm trying (still) to get the CDD program working, now with: FreeBSD silver.sms.fi 2.2-STABLE FreeBSD 2.2-STABLE #0: Tue Apr 1 09:47:44 EEST 1997 pete@silver.sms.fi:/usr/src/sys/compile/SILVER i386 This time the messages are more informative, however since the machine hung after spitting them, I don't have exact reproduction but just notes on the paper. They go like this: SCB 0x0: Timed out while idle LASTPHASE=0x1, SCSISIG=0x0, SFOADDR=0x8 Queuing abort SCB SCB 0x0: Timed out while idle LASTPHASE=0x1, SCSISIG=0xe6, SFOADDR=0x8 no longer in timeout Issuing channel A reset, 2 SCBs Clearing bus reset Clearing in-reset flag SCB 0x3: Timed out while idle LASTPHASE=0x1, SCSISIG=0xe6, SFOADDR=0x4 SCB immediate reset, flags=0x401 Anyone have any clue about this? All my previous queries have come up empty! Pete From owner-freebsd-scsi Tue Apr 1 10:01:06 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA16614 for freebsd-scsi-outgoing; Tue, 1 Apr 1997 10:01:06 -0800 (PST) Received: from sag.space.lockheed.com (sag.space.lockheed.com [192.68.162.134]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA16583 for ; Tue, 1 Apr 1997 10:00:33 -0800 (PST) Received: from localhost by sag.space.lockheed.com; (5.65v3.2/1.1.8.2/21Nov95-0423PM) id AA14647; Tue, 1 Apr 1997 09:59:06 -0800 Date: Tue, 1 Apr 1997 09:59:06 -0800 (PST) From: "Brian N. Handy" To: Joerg Wunsch Cc: freebsd-scsi@freebsd.org Subject: Re: Philips CDwriter In-Reply-To: <19970401082007.ZO53870@uriah.heep.sax.de> Message-Id: X-Files: The truth is out there Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >As Brian N. Handy wrote: > >> # wormcontrol select PHILIPS CDD2600 >> wormcontrol: open(/dev/rworm0): Device not configured > >The obvious question: there is a medium in the drive when you do >the above? It fails even when issued repeatedly? I finally sorted it out -- the problem was the damn media was bad. I tried another disk and it worked fine. :-/ As for the changes to worm.c, you're right - not necessary. However I did add another entry to scsiconf.c since the probe has changed fairly drastically. The old philips probes as IMS CDD2000, the new one probes as PHILIPS CDD2600. In order to make the entry vague enough to work, I'd have to do something like "*", "CDD2*"....which might pick up some other SCSI stuff down the road and declare it a WORM device! I think another entry is in order. Here's the patch, if anyone's interested. Happy Trails, Brian ---------------------------------------------------------------------- *** sys/scsi/scsiconf.c~ Mon Mar 10 12:53:16 1997 --- sys/scsi/scsiconf.c Tue Apr 1 09:26:17 1997 *************** *** 393,398 **** --- 393,403 ---- T_READONLY, T_WORM, T_REMOV, "IMS", "CDD2000*", "*", "worm", SC_ONE_LU }, + { + /* Here's another Philips drive... */ + T_READONLY, T_WORM, T_REMOV, "PHILIPS", "CDD2*", "*", + "worm", SC_ONE_LU + }, /* * The Plasmon's are dual-faced: they appear as T_WORM if the * drive is empty, or a CD-R medium is in the drive, and they From owner-freebsd-scsi Tue Apr 1 11:30:31 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA23200 for freebsd-scsi-outgoing; Tue, 1 Apr 1997 11:30:31 -0800 (PST) Received: from sax.sax.de (sax.sax.de [193.175.26.33]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA23177 for ; Tue, 1 Apr 1997 11:30:20 -0800 (PST) Received: (from uucp@localhost) by sax.sax.de (8.6.12/8.6.12-s1) with UUCP id VAA04793; Tue, 1 Apr 1997 21:30:06 +0200 Received: (from j@localhost) by uriah.heep.sax.de (8.8.5/8.8.5) id VAA16406; Tue, 1 Apr 1997 21:12:45 +0200 (MET DST) Message-ID: <19970401211244.BI32132@uriah.heep.sax.de> Date: Tue, 1 Apr 1997 21:12:44 +0200 From: j@uriah.heep.sax.de (J Wunsch) To: freebsd-scsi@freebsd.org Cc: handy@sag.space.lockheed.com (Brian N. Handy) Subject: Re: Philips CDwriter References: <19970401082007.ZO53870@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 Brian N. Handy on Apr 1, 1997 09:59:06 -0800 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk As Brian N. Handy wrote: > >The obvious question: there is a medium in the drive when you do > >the above? It fails even when issued repeatedly? > > I finally sorted it out -- the problem was the damn media was bad. I > tried another disk and it worked fine. :-/ Du-oh. This yielded a `device not ready' from the drive, which in turn causes the wormopen() to fail. > Here's the patch, if anyone's interested. Thank's, i'll integrate 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 Tue Apr 1 15:19:05 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA11740 for freebsd-scsi-outgoing; Tue, 1 Apr 1997 15:19:05 -0800 (PST) Received: from po1.glue.umd.edu (root@po1.glue.umd.edu [129.2.128.44]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA11734 for ; Tue, 1 Apr 1997 15:19:01 -0800 (PST) Received: from skipper.eng.umd.edu (skipper.eng.umd.edu [129.2.103.24]) by po1.glue.umd.edu (8.8.5/8.8.5) with ESMTP id SAA26444 for ; Tue, 1 Apr 1997 18:18:44 -0500 (EST) Received: from localhost (chuckr@localhost) by skipper.eng.umd.edu (8.8.5/8.6.4) with SMTP id SAA30171 for ; Tue, 1 Apr 1997 18:18:42 -0500 (EST) X-Authentication-Warning: skipper.eng.umd.edu: chuckr owned process doing -bs Date: Tue, 1 Apr 1997 18:18:41 -0500 (EST) From: Chuck Robey X-Sender: chuckr@skipper.eng.umd.edu To: scsi@freebsd.org Subject: Re: Hard disk problems In-Reply-To: <199704010340.TAA03903@silvia.HIP.Berkeley.EDU> 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 Mon, 31 Mar 1997, Satoshi Asami wrote: > [crossposted to SCSI, with reply set to there] > > * [I sent this message to hackers, where it got no response, so maybe I > * should have sent it here. Apologies to those who will have seen it > * twice.] > > I don't read hackers because the noise level is so high. ;) > > * I was wondering if someone can explain the error message I'm suddenly > * seeing on bootup of one of my systems. It hangs with the message: > * > * ncr0: SCSI phase error fixup: CCB already dequeued (0xf2467200) > * ncr0 timeout ccb=f2466600 skip > * ncr0 timeout ccb=f2466800 skip > * ncr0 timeout ccb=f2466a00 skip > * ncr0 timeout ccb=f2467200 skip > * (hangs here) > > I have seen something very similar on my system. The Micropolis > 3243WT (which I got as a replacement to an older 3243W) doesn't boot 3 > out of 4 times with "ncr0 timeout" messages (I don't get the "already > dequeued" part, though). The other two disks (Atlas I and II) don't > have this problem. Also, removing the CDROM (the only narrow device > in the system) alleviated the symptoms somewhat (booted 3 out of 4 > times). > > * I need to know what it means, and if there's any way to recover from it > * without having to lose the whole disk (my boot disk, darn it!) I get this > * error on the system after it does the full fsck (successfully), and the > * system has (in total) 2 - 2G disks (this is the first one), 1 - 200 meg > * disk, and one cdrom, all scsi, all hooked to one ncr 825 controller > * (Tyan). > > Well, when I moved the Micropolis to an Adaptec 2940UW, everything > started working again. ;) Oh, you're saying it's more likely to be a drive/controller problem than a drive problem? Makes me wish I had an extra controller handy. Did, couple months ago, but I sent it to a friend (I hate seeing hardware go to waste). I was hoping maybe Justin would comment, but maybe he's busy. Hmm, well, I guess I have to go looking through the SCSI sources for some kinda tip as to what's causing it. The system has been in operating shape now for 3 months. Check out http://www/aprilfools.com. Trust me, do it today. It's only an April fools gag today :-) > > Satoshi > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 9120 Edmonston Ct #302 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-scsi Wed Apr 2 01:49:11 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id BAA19228 for freebsd-scsi-outgoing; Wed, 2 Apr 1997 01:49:11 -0800 (PST) Received: from cats.ucsc.edu (rumpleteazer.UCSC.EDU [128.114.129.45]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA19223 for ; Wed, 2 Apr 1997 01:49:08 -0800 (PST) Received: from cats-po-1 (root@cats-po-1.UCSC.EDU [128.114.129.22]) by cats.ucsc.edu (8.8.5/8.8.4.cats-athena) with SMTP id BAA20758 for ; Wed, 2 Apr 1997 01:49:08 -0800 (PST) Received: from bifrost.wireless by cats-po-1 (8.6.13/4.8) id BAA17309; Wed, 2 Apr 1997 01:49:05 -0800 Message-ID: <33422B94.167EB0E7@cats.ucsc.edu> Date: Wed, 02 Apr 1997 01:49:08 -0800 From: Tom Organization: No Organization in Particular X-Mailer: Mozilla 3.01 (X11; I; FreeBSD 2.1.6-RELEASE i386) MIME-Version: 1.0 To: scsi@freebsd.org Subject: More fun with iomega... Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk (no this is not an april fools joke, although it seems like it) I've been reading through the mailing list archives for similar problems, but I haven't seen any.. My first problem. I took somsones advice and used scsiformat -w sd0 on my jaz disk. It went find for about 20 minutes, then stopped. The process was hung, didn't respond to a kill -9 or -15 I rebooted. After a couple tries to format the disk, I gave up and went to format it on another machine(Mac), and it worked fine there. Since I'm an irc nut, I decided to ask a couple people on #freebsd seeing as how I hang out there a fair amount. Someone suggested using sysinstall to edit the partitions and that kind of thing. So I attempted, and it failed apparently. Next time I run sysinstall, I get this messages.... Apr 1 21:17:33 bifrost /kernel: sd0: error reading primary partition table reading fsbn 0 (sd0 bn 0; cn 0 tn 0 sn 0) I'm stuck...the cartridge seems to work with dos/mac, but I really bought it for use with FreeBSD... My big problem seems to be that things hang when I use them on my jaz, I'm going to check the termination and all that, but I'm not sure what I can do... Anyone in the Santa Cruz or SF bay area want to format this disk for me? I can pay, I'm desparate :) here's my SCSI related dmesg output.. There is no media in the drive at the moment... --- ncr0 rev 2 int a irq 10 on pci0:15 (ncr0:4:0): "iomega jaz 1GB H.72" type 0 removable SCSI 2 sd0(ncr0:4:0): Direct-Access sd0(ncr0:4:0): FAST SCSI-2 100ns (10 Mb/sec) offset 8. sd0(ncr0:4:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd0 could not mode sense (4). Using ficticious geometry sd0(ncr0:4:0): NOT READY asc:3a,0 Medium not present sd0: could not get size 0MB (0 512 byte sectors) --- From owner-freebsd-scsi Wed Apr 2 02:03:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA19982 for freebsd-scsi-outgoing; Wed, 2 Apr 1997 02:03:29 -0800 (PST) Received: from trifork.gu.net (trifork.gu.net [194.93.190.194]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA19976; Wed, 2 Apr 1997 02:03:21 -0800 (PST) Received: from localhost (localhost.gu.kiev.ua [127.0.0.1]) by trifork.gu.net (8.8.5/8.8.5) with SMTP id NAA01228; Wed, 2 Apr 1997 13:03:26 +0300 (EEST) Date: Wed, 2 Apr 1997 13:03:25 +0300 (EEST) From: Andrew Stesin Reply-To: stesin@gu.net To: hackers@freebsd.org, scsi@freebsd.org Subject: 2 PCI busses, 2 AIC chips, 2.2.1. Howto ? Message-ID: X-NCC-RegID: ua.gu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The box: Intel XXpress-, 2 AIC7870 chips onboard, EISA bus present. neither of AICs are recognized at boot. ??? I have the following guesses: 1. neither of the 2 SCSI busses has anything attached yet (disk drives will come in a day or two, they ordered drives separately, and no Wide drives here to try). 2. SCSI BIOSes for 2 chips aren't configured correctly (just now it has "BIOS enabled" in SCSIconfig for the first chip and "BIOS disabled" for the second, should be Ok?) 3. 2.2.1 has some problem with two PCI busses? (while both AICs are on the second bus??? or on EISA???) What I see at boot after the "Probing devices on the pci:0 bus" message: chip0 \ rev 2 on pci0:0 chip1 rev 5 on pci0:14 pci0:15:0: Intel Corporation device=0x0008, class=0xff, subclass=0x00 \ [no driver assigned] ...^^^^.... This last message is repeated exactly for all pci0:15:[0-7] values. What I am missing? Any comments and explanations are appreciated! Thanks a lot for your help! Best regards, Andrew Stesin nic-hdl: ST73-RIPE From owner-freebsd-scsi Wed Apr 2 02:41:35 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id CAA22064 for freebsd-scsi-outgoing; Wed, 2 Apr 1997 02:41:35 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (wck-ca16-19.ix.netcom.com [207.94.231.83]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA22043; Wed, 2 Apr 1997 02:41:25 -0800 (PST) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id CAA03124; Wed, 2 Apr 1997 02:41:05 -0800 (PST) Date: Wed, 2 Apr 1997 02:41:05 -0800 (PST) Message-Id: <199704021041.CAA03124@silvia.HIP.Berkeley.EDU> To: stesin@gu.net CC: hackers@freebsd.org, scsi@freebsd.org In-reply-to: (message from Andrew Stesin on Wed, 2 Apr 1997 13:03:25 +0300 (EEST)) Subject: Re: 2 PCI busses, 2 AIC chips, 2.2.1. Howto ? From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * 1. neither of the 2 SCSI busses has anything attached yet (disk drives will * come in a day or two, they ordered drives separately, and no Wide * drives here to try). This shouldn't matter. * 2. SCSI BIOSes for 2 chips aren't configured correctly (just now * it has "BIOS enabled" in SCSIconfig for the first chip and * "BIOS disabled" for the second, should be Ok?) This shouldn't matter either. You will never have to enable BIOS unless you plan to boot from a disk on that bus. * 3. 2.2.1 has some problem with two PCI busses? (while both AICs are * on the second bus??? or on EISA???) What I see at boot * after the "Probing devices on the pci:0 bus" message: It might be that it can't recognize the PCI-PCI bridge. What do the markings on the chip say? I know FreeBSD can deal with DEC and IBM chips. * chip0 \ * rev 2 on pci0:0 * chip1 rev 5 on pci0:14 * pci0:15:0: Intel Corporation device=0x0008, class=0xff, subclass=0x00 \ * [no driver assigned] Boot with "-v" and send the output to se@freebsd.org. You may want to hack /sys/pci/pcisupport.c by yourself (grep for "IBM") to see if you can get it to work. * ....^^^^.... * This last message is repeated exactly for all pci0:15:[0-7] * values. This is quite weird though. Sounds like a multi-function chip misprobed. Satoshi From owner-freebsd-scsi Wed Apr 2 06:29:55 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id GAA02049 for freebsd-scsi-outgoing; Wed, 2 Apr 1997 06:29:55 -0800 (PST) Received: from trifork.gu.net (trifork.gu.net [194.93.190.194]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA02034; Wed, 2 Apr 1997 06:29:48 -0800 (PST) Received: from localhost (localhost.gu.kiev.ua [127.0.0.1]) by trifork.gu.net (8.8.5/8.8.5) with SMTP id RAA02371; Wed, 2 Apr 1997 17:29:42 +0300 (EEST) Date: Wed, 2 Apr 1997 17:29:42 +0300 (EEST) From: Andrew Stesin Reply-To: stesin@gu.net To: Satoshi Asami cc: hackers@freebsd.org, scsi@freebsd.org Subject: Re: 2 PCI busses, 2 AIC chips, 2.2.1. Howto ? In-Reply-To: <199704021041.CAA03124@silvia.HIP.Berkeley.EDU> Message-ID: X-NCC-RegID: ua.gu MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, thanks for comments. On Wed, 2 Apr 1997, Satoshi Asami wrote: > * 3. 2.2.1 has some problem with two PCI busses? (while both AICs are > * on the second bus??? or on EISA???) What I see at boot > * after the "Probing devices on the pci:0 bus" message: > > It might be that it can't recognize the PCI-PCI bridge. What do the > markings on the chip say? I know FreeBSD can deal with DEC and IBM > chips. Unfortunately (or vice versa? ;) I have no access to the box' internals, I'm not authorized to open the case and look inside. But: the box is "genuine Intel", the model is Magellan W/15", base board (kinda of backplane) is XXpress 15" Rel 2, with 1 P166 CPU module. I'll try to find what the bridge chip is. But what is the chance that _both_ AIC chips are "on the other side of the bridge", anyway? > * chip0 \ > * rev 2 on pci0:0 > * chip1 rev 5 on pci0:14 > * pci0:15:0: Intel Corporation device=0x0008, class=0xff, subclass=0x00 \ > * [no driver assigned] > > Boot with "-v" and send the output to se@freebsd.org. You may want to > hack /sys/pci/pcisupport.c by yourself (grep for "IBM") to see if you > can get it to work. Yep, I got the idea. > * ....^^^^.... > * This last message is repeated exactly for all pci0:15:[0-7] > * values. > > This is quite weird though. Sounds like a multi-function chip > misprobed. Gmmm... > > Satoshi > Best regards, Andrew Stesin nic-hdl: ST73-RIPE From owner-freebsd-scsi Wed Apr 2 07:11:02 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA03781 for freebsd-scsi-outgoing; Wed, 2 Apr 1997 07:11:02 -0800 (PST) Received: from pluto.plutotech.com (root@pluto.plutotech.com [206.168.67.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA03776; Wed, 2 Apr 1997 07:10:57 -0800 (PST) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id IAA01337; Wed, 2 Apr 1997 08:10:35 -0700 (MST) Message-Id: <199704021510.IAA01337@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: stesin@gu.net, davidg@FreeBSD.org cc: Satoshi Asami , hackers@FreeBSD.org, scsi@FreeBSD.org Subject: Re: 2 PCI busses, 2 AIC chips, 2.2.1. Howto ? In-reply-to: Your message of "Wed, 02 Apr 1997 17:29:42 +0300." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Apr 1997 08:08:34 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk > I'll try to find what the bridge chip is. Don't XXpress motherboards have two PCI->Host bridges? I think that David ran into this same problem on an earlier incarnation of Wcarchive and solved it by telling the PCI code to go find more than 1 primary PCI bus. > But what is the chance that _both_ AIC chips are "on the > other side of the bridge", anyway? Very, very high. This is how the motherboard Wcarchive used to use was configured. -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Wed Apr 2 08:29:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA07731 for freebsd-scsi-outgoing; Wed, 2 Apr 1997 08:29:37 -0800 (PST) Received: from huron.wrs.com (unknown-46-2.wrs.com [147.11.46.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id IAA07726 for ; Wed, 2 Apr 1997 08:29:35 -0800 (PST) Received: by huron.wrs.com id AA01222 (5.65c/IDA-1.4.4 for freebsd-scsi@freebsd.org); Wed, 2 Apr 1997 08:29:39 -0800 From: "Dinesh D. Singh" Message-Id: <199704021629.AA01222@huron.wrs.com> Subject: Adaptec 7880 SCSI To: freebsd-scsi@freebsd.org Date: Wed, 2 Apr 1997 08:29:39 -0800 (PST) Cc: dinesh@wrs.com (Dinesh D. Singh) X-Mailer: ELM [version 2.4 PL24 PGP3] 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 am Dinesh at WindRiver Systems. I woull like to know the web location where I could access the source code for the Adaptec 7880 SCSI driver. Any help will be greatly appreciated. - Dinesh From owner-freebsd-scsi Wed Apr 2 09:13:40 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA10920 for freebsd-scsi-outgoing; Wed, 2 Apr 1997 09:13:40 -0800 (PST) Received: from chess.inetspace.com ([206.50.163.14]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA10905 for ; Wed, 2 Apr 1997 09:13:30 -0800 (PST) Received: (from kgor@localhost) by chess.inetspace.com (8.8.5/8.7.3) id LAA00228; Wed, 2 Apr 1997 11:12:01 -0600 (CST) Date: Wed, 2 Apr 1997 11:12:01 -0600 (CST) Message-Id: <199704021712.LAA00228@chess.inetspace.com> From: "Kent S. Gordon" To: freebsd-scsi@freebsd.org Subject: Hang on boot in recent -current kernels Mime-Version: 1.0 (generated by tm-edit 7.105) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have not been able to boot -current kernels using sources after about March 23. The boot hangs after getting the message scbus0 at bt0 bus 0. What suggests do people have for me to try in debugging this problem. I have attached below the output of the boot from the latest working kernel that I have plus my kernel config file. Apr 2 11:03:23 chess /kernel.good: Copyright (c) 1992-1997 FreeBSD Inc. Apr 2 11:03:23 chess /kernel.good: Copyright (c) 1982, 1986, 1989, 1991, 1993 Apr 2 11:03:23 chess /kernel.good: The Regents of the University of California. All rights reserved. Apr 2 11:03:23 chess /kernel.good: FreeBSD 3.0-CURRENT #0: Thu Mar 20 06:10:23 CST 1997 Apr 2 11:03:23 chess /kernel.good: root@chess.inetspace.com:/usr/src/sys/compile/CHESS Apr 2 11:03:23 chess /kernel.good: CPU: i486DX (486-class CPU) Apr 2 11:03:23 chess /kernel.good: real memory = 16777216 (16384K bytes) Apr 2 11:03:23 chess /kernel.good: avail memory = 14794752 (14448K bytes) Apr 2 11:03:24 chess /kernel.good: Probing for devices on the ISA bus: Apr 2 11:03:24 chess /kernel.good: sc0 at 0x60-0x6f irq 1 on motherboard Apr 2 11:03:24 chess /kernel.good: sc0: VGA color <16 virtual consoles, flags=0x0> Apr 2 11:03:24 chess /kernel.good: ed0 at 0x300-0x31f irq 5 on isa Apr 2 11:03:24 chess /kernel.good: ed0: address 00:00:e8:cb:ac:1a, type NE2000 (16 bit) Apr 2 11:03:24 chess /kernel.good: sio0 at 0x3f8-0x3ff irq 4 on isa Apr 2 11:03:24 chess /kernel.good: sio0: type 16550A Apr 2 11:03:24 chess /kernel.good: sio1 at 0x2f8-0x2ff irq 3 on isa Apr 2 11:03:24 chess /kernel.good: sio1: type 16550A Apr 2 11:03:24 chess /kernel.good: lpt0 at 0x378-0x37f irq 7 on isa Apr 2 11:03:24 chess /kernel.good: lpt0: Interrupt-driven port Apr 2 11:03:24 chess /kernel.good: lp0: TCP/IP capable interface Apr 2 11:03:25 chess /kernel.good: fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa Apr 2 11:03:25 chess /kernel.good: fdc0: NEC 765 Apr 2 11:03:25 chess /kernel.good: fd0: 1.44MB 3.5in Apr 2 11:03:25 chess /kernel.good: fd1: 1.2MB 5.25in Apr 2 11:03:25 chess /kernel.good: bt0: Bt445S/ 0-ISA(24bit) bus Apr 2 11:03:25 chess /kernel.good: bt0: Your card cannot DMA above 16MB boundary. Bounce buffering enabled. Apr 2 11:03:25 chess /kernel.good: bt0: reading board settings, dma=5, int=11 Apr 2 11:03:25 chess /kernel.good: bt0: version 3.36, fast sync, parity, 32 mbxs, 32 ccbs Apr 2 11:03:25 chess /kernel.good: bt0: targ 0 sync rate=10.00MB/s(100ns), offset=15 Apr 2 11:03:25 chess /kernel.good: bt0: targ 1 sync rate=10.00MB/s(100ns), offset=15 Apr 2 11:03:25 chess /kernel.good: bt0: Using Strict Round robin scheme Apr 2 11:03:25 chess /kernel.good: bt0 at 0x330 irq 11 drq 5 on isa Apr 2 11:03:26 chess /kernel.good: bt0: waiting for scsi devices to settle Apr 2 11:03:26 chess /kernel.good: scbus0 at bt0 bus 0 Apr 2 11:03:26 chess /kernel.good: sd0 at scbus0 target 0 lun 0 Apr 2 11:03:26 chess /kernel.good: sd0: type 0 fixed SCSI 2 Apr 2 11:03:26 chess /kernel.good: sd0: Direct-Access 1908MB (3907911 512 byte sectors) Apr 2 11:03:26 chess /kernel.good: sd1 at scbus0 target 1 lun 0 Apr 2 11:03:26 chess /kernel.good: sd1: type 0 fixed SCSI 2 Apr 2 11:03:26 chess /kernel.good: sd1: Direct-Access 1006MB (2061108 512 byte sectors) Apr 2 11:03:26 chess /kernel.good: npx0 on motherboard Apr 2 11:03:26 chess /kernel.good: npx0: INT 16 interface Apr 2 11:03:26 chess /kernel.good: changing root device to sd0a # # GGZOO -- Cyrix 586/100 with BT controller # # For more information read the handbook part System Administration -> # Configuring the FreeBSD Kernel -> The Configuration File. # The handbook is available in /usr/share/doc/handbook or online as # latest version from the FreeBSD World Wide Web server # # # An exhaustive list of options and more detailed explanations of the # device lines is present in the ./LINT configuration file. If you are # in doubt as to the purpose or necessity of a line, check first in LINT. # # $Id: GENERIC,v 1.78 1996/11/16 01:09:17 gibbs Exp $ machine "i386" #cpu "I386_CPU" cpu "I486_CPU" cpu "I586_CPU" cpu "I686_CPU" ident GGZOO maxusers 10 #options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options NFS #Network Filesystem options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] #options SCSI_DELAY=15 #Be pessimistic about Joe SCSI device options SCSI_DELAY=5 #Be pessimistic about Joe SCSI device options BOUNCE_BUFFERS #include support for DMA bounce buffers options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor options SYSVSHM options SYSVSEM options SYSVMSG options "AUTO_EOI_1" #faster interrupts config kernel root on wd0 controller isa0 #I have a VLB, but no aha28xx cards, that think they are on a eisa bus. #controller eisa0 #controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 vector fdintr disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 #tape ft0 at fdc0 drive 2 #controller wdc0 at isa? port "IO_WD1" bio irq 14 vector wdintr #disk wd0 at wdc0 drive 0 #disk wd1 at wdc0 drive 1 #controller wdc1 at isa? port "IO_WD2" bio irq 15 vector wdintr #disk wd2 at wdc1 drive 0 #disk wd3 at wdc1 drive 1 #options ATAPI #Enable ATAPI support for IDE bus #options ATAPI_STATIC #Don't do it as an LKM #device wcd0 #IDE CD-ROM # A single entry for any of these controllers (ncr, ahb, ahc) is sufficient # for any number of installed devices. #controller ncr0 #controller ahb0 #controller ahc0 controller bt0 at isa? port "IO_BT0" bio irq ? vector bt_isa_intr #controller uha0 at isa? port "IO_UHA0" bio irq ? drq 5 vector uhaintr #controller aha0 at isa? port "IO_AHA0" bio irq ? drq 5 vector ahaintr #controller aic0 at isa? port 0x340 bio irq 11 vector aicintr #controller nca0 at isa? port 0x1f88 bio irq 10 vector ncaintr #controller nca1 at isa? port 0x350 bio irq 5 vector ncaintr #controller sea0 at isa? bio irq 5 iomem 0xc8000 iosiz 0x2000 vector seaintr controller scbus0 device sd0 device od0 #See LINT for possible `od' options. device st0 device cd0 #Only need one of these, the code dynamically grows #device wt0 at isa? port 0x300 bio irq 5 drq 1 vector wtintr #device mcd0 at isa? port 0x300 bio irq 10 vector mcdintr #controller matcd0 at isa? port 0x230 bio #device scd0 at isa? port 0x230 bio # syscons is the default console driver, resembling an SCO console device sc0 at isa? port "IO_KBD" tty irq 1 vector scintr # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? port "IO_KBD" tty irq 1 vector pcrint #options PCVT_FREEBSD=210 # pcvt running on FreeBSD >= 2.0.5 #options XSERVER # include code for XFree86 #options FAT_CURSOR # start with block cursor # If you have a ThinkPAD, uncomment this along with the rest of the PCVT lines #options PCVT_SCANSET=2 # IBM keyboards are non-std # Mandatory, don't remove device npx0 at isa? port "IO_NPX" irq 13 vector npxintr # # Laptop support (see LINT for more options) # #device apm0 at isa? disable # Advanced Power Management #options APM_BROKEN_STATCLOCK # Workaround some buggy APM BIOS # PCCARD (PCMCIA) support #controller crd0 #device pcic0 at crd? #device pcic1 at crd? device sio0 at isa? port "IO_COM1" tty irq 4 vector siointr device sio1 at isa? port "IO_COM2" tty irq 3 vector siointr #device sio2 at isa? disable port "IO_COM3" tty irq 5 vector siointr #device sio3 at isa? disable port "IO_COM4" tty irq 9 vector siointr device lpt0 at isa? port? tty irq 7 vector lptintr #device lpt1 at isa? port? tty #device mse0 at isa? port 0x23c tty irq 5 vector mseintr #device psm0 at isa? disable port "IO_KBD" conflicts tty irq 12 vector psmintr # Order is important here due to intrusive probes, do *not* alphabetize # this list of network interfaces until the probes have been fixed. # Right now it appears that the ie0 must be probed before ep0. See # revision 1.20 of this file. #device de0 #device fxp0 #device vx0 #device ed0 at isa? port 0x280 net irq 5 iomem 0xd8000 vector edintr #device ed1 at isa? port 0x300 net irq 5 iomem 0xd8000 vector edintr device ed0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector edintr #device ie0 at isa? port 0x360 net irq 7 iomem 0xd0000 vector ieintr #device ep0 at isa? port 0x300 net irq 10 vector epintr #device fe0 at isa? port 0x300 net irq ? vector feintr #device ix0 at isa? port 0x300 net irq 10 iomem 0xd0000 iosiz 32768 vector ixintr #device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 vector le_intr #device lnc0 at isa? port 0x280 net irq 10 drq 0 vector lncintr #device ze0 at isa? port 0x300 net irq 5 iomem 0xd8000 vector zeintr #device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 vector zpintr pseudo-device loop pseudo-device ether pseudo-device log #pseudo-device sl 1 # ijppp uses tun instead of ppp device #pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 32 pseudo-device bpfilter 4 #Berkeley packet filter pseudo-device gzip # Exec gzipped a.out's # KTRACE enables the system-call tracing facility ktrace(2). # This adds 4 KB bloat to your kernel, and slightly increases # the costs of each syscall. options KTRACE #kernel tracing Kent S. Gordon Senior Software Engineer INetSpace Co. voice: (972)851-3494 fax:(972)702-0384 e-mail:kgor@inetspace.com From owner-freebsd-scsi Wed Apr 2 09:20:50 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id JAA11263 for freebsd-scsi-outgoing; Wed, 2 Apr 1997 09:20:50 -0800 (PST) Received: from pluto.plutotech.com (root@pluto.plutotech.com [206.168.67.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA11258 for ; Wed, 2 Apr 1997 09:20:45 -0800 (PST) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id KAA04022; Wed, 2 Apr 1997 10:20:45 -0700 (MST) Message-Id: <199704021720.KAA04022@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: "Dinesh D. Singh" cc: freebsd-scsi@freebsd.org Subject: Re: Adaptec 7880 SCSI In-reply-to: Your message of "Wed, 02 Apr 1997 08:29:39 PST." <199704021629.AA01222@huron.wrs.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 02 Apr 1997 10:18:42 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Hi: > >I am Dinesh at WindRiver Systems. I woull like to know the web location >where I could access the source code for the Adaptec 7880 SCSI driver. > >Any help will be greatly appreciated. > >- Dinesh ftp://ftp.cdrom.com/pub/FreeBSD/FreeBSD-curret/src/sys/dev/aic7xxx/* ftp://ftp.cdrom.com/pub/FreeBSD/FreeBSD-curret/src/sys/i386/scsi/aic7xxx* ftp://ftp.cdrom.com/pub/FreeBSD/FreeBSD-curret/src/sys/i386/scsi/93cx6.* ftp://ftp.cdrom.com/pub/FreeBSD/FreeBSD-curret/src/sys/i386/eisa/aic7770.c ftp://ftp.cdrom.com/pub/FreeBSD/FreeBSD-curret/src/sys/pci/aic7870.c I am the author of this driver if you have any questions. I would have thought that WindRiver would be using the Adaptec supplied code for OEMs though. It's always interesting to find out where bits of FreeBSD wind up. 8-) -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Wed Apr 2 11:13:52 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA17182 for freebsd-scsi-outgoing; Wed, 2 Apr 1997 11:13:52 -0800 (PST) Received: from adam.adonai.net ([205.182.92.2]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA17176 for ; Wed, 2 Apr 1997 11:13:45 -0800 (PST) Received: from localhost (leec@localhost) by adam.adonai.net (8.8.5/8.7.3) with SMTP id NAA24618; Wed, 2 Apr 1997 13:14:31 -0600 (CST) Date: Wed, 2 Apr 1997 13:14:31 -0600 (CST) From: "Lee Crites (AEI)" To: "Dinesh D. Singh" cc: freebsd-scsi@freebsd.org Subject: Re: Adaptec 7880 SCSI In-Reply-To: <199704021629.AA01222@huron.wrs.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 =>Hi: => =>I am Dinesh at WindRiver Systems. I woull like to know the web location =>where I could access the source code for the Adaptec 7880 SCSI driver. Is this the vxworks WindRiver systems? Is your membership in a FreeBSD mailing list indicative of a movement of vxworks, and it's rtos, towards FreeBSD? Lee From owner-freebsd-scsi Thu Apr 3 11:13:29 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA09834 for freebsd-scsi-outgoing; Thu, 3 Apr 1997 11:13:29 -0800 (PST) Received: from prozac.neuron.net (prozac.neuron.net [165.254.1.213]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA09825 for ; Thu, 3 Apr 1997 11:13:23 -0800 (PST) Received: (from amir@localhost) by prozac.neuron.net (8.7.5/8.6.12) id OAA03185; Thu, 3 Apr 1997 14:19:07 -0500 (EST) Message-ID: <19970403141907.64067@prozac.neuron.net> Date: Thu, 3 Apr 1997 14:19:07 -0500 From: "Amir Y. Rosenblatt" To: scsi@freebsd.org Subject: Baracuda BIOS levels Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67 Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a pair of year-old ST32550W's in my freebsd box and have heard mentions of needing current BIOS to be able to handle the tagged command queueing stuff. What BIOS version should I be up to for this? -Amir -- / \ Pumpin' up the morphine metronome... | Amir Y. Rosenblatt /<@>\ | amir@neuron.net / \ FNORD | http://www.neuron.net/~amir _/_______\____________________________________|____________________________ From owner-freebsd-scsi Thu Apr 3 21:20:59 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id VAA16832 for freebsd-scsi-outgoing; Thu, 3 Apr 1997 21:20:59 -0800 (PST) Received: from silvia.HIP.Berkeley.EDU (wck-ca14-09.ix.netcom.com [207.92.174.73]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA16826 for ; Thu, 3 Apr 1997 21:20:52 -0800 (PST) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id VAA11444; Thu, 3 Apr 1997 21:20:40 -0800 (PST) Date: Thu, 3 Apr 1997 21:20:40 -0800 (PST) Message-Id: <199704040520.VAA11444@silvia.HIP.Berkeley.EDU> To: amir@neuron.net CC: scsi@freebsd.org In-reply-to: <19970403141907.64067@prozac.neuron.net> (amir@neuron.net) Subject: Re: Baracuda BIOS levels From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * I have a pair of year-old ST32550W's in my freebsd box and have heard * mentions of needing current BIOS to be able to handle the tagged command * queueing stuff. What BIOS version should I be up to for this? Dunno about ST32550W's, but the ones we have: SEAGATE ST15150W 0023 appears to be working fine with tagged queuing. (I.e., the system crashes from time to time with ahc, but it also happens without tagged queuing.) Satoshi From owner-freebsd-scsi Fri Apr 4 13:06:21 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id NAA03366 for freebsd-scsi-outgoing; Fri, 4 Apr 1997 13:06:21 -0800 (PST) Received: from roundtable.cif.rochester.edu (sadmin@roundtable.cif.rochester.edu [128.151.220.14]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA03352 for ; Fri, 4 Apr 1997 13:06:14 -0800 (PST) Received: (from sadmin@localhost) by roundtable.cif.rochester.edu (8.8.5/8.8.3) id QAA18369 for scsi@freebsd.org; Fri, 4 Apr 1997 16:05:48 -0500 (EST) From: Security Administrator Message-Id: <199704042105.QAA18369@roundtable.cif.rochester.edu> Subject: exabyte problems To: scsi@freebsd.org (FreeBSD Scsi) Date: Fri, 4 Apr 1997 16:05:48 -0500 (EST) 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 Howdy, I have an Exabyte 8500 and it is NOT working properly. I was assured by its previous owner that the drive was in perfect working condition, but the moment that I added it to my SCSI chain on my FreeBSD 2.2.1 system, it barfed. To be specific, I have an Adaptec 2940UW card with two SCSI-III drives on one chain and the SCSI-I tape drive off another ribbon cable. Whenever I try to write to the drive, it has a slew of write errors that kill whatever process is trying use the device. Neither dump nor tar are immune. I made sure that the Adaptec negotiates with the drive for 8-bit operation, and the tape drive comes up perfectly at boot time, ie., it is properly identified at the right LUN and with the right name. I have tried a little experiment. I happen to have an Adaptec 1542B kicking around, and I tried to integrate that into my system. With that card, there is a new problem. The card comes up fine... unique IRQ, DRQ, and AT port addresses and numbers. As far as I can tell, there are NO conflicts and the OS talks to the card fine. At boot time, the card recognizes the tape drive on the scsi chain perfectly. HOWEVER, whenever I try to read/write to the drive, the read/write operation times out. I also can not execute a scsi -f /dev/rst0 -p command... It times out. I originally thought that this was due to an IRQ or DRQ conflict, but the settings are unique and there ARE NO CONFLICTS. Also, whenever I try to terminate the tape drive, the SCSI bus can't locate the 8500. Since the tape drive isn't the last device on the bus connected to the 2940UW, this isn't a problem. But, I thought that the tape SHOULD be properly terminated on the 1542B bus. If anyone has any advice or ideas, I would really appreciate it. Thanks in advance, Josh Pincus -- System Security Administrator Computer Interest Floor University of Rochester Rochester, NY 14627 sadmin@roundtable.cif.rochester.edu From owner-freebsd-scsi Fri Apr 4 16:06:56 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id QAA12447 for freebsd-scsi-outgoing; Fri, 4 Apr 1997 16:06:56 -0800 (PST) Received: from vodka.sublink.org (root@vodka.sublink.ORG [194.184.73.88]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id QAA12435 for ; Fri, 4 Apr 1997 16:06:51 -0800 (PST) Received: from nameron by vodka.sublink.org with uucp (Smail3.1.29.1 #3) id m0wDJ0J-001bgwC; Sat, 5 Apr 97 02:06 MET DST Received: from hp-dyno.smd by nameron.smd.sublink.org with smtp (Smail3.1.28.1 #17) id m0wDIjM-0008EZC; Sat, 5 Apr 97 01:49 MET DST Received: by hp-dyno.smd (Smail3.1.28.1 #8) id m0wDJeb-000JKuC; Sat, 5 Apr 97 01:48 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 MAA25193 for ; Fri, 4 Apr 1997 12:43:13 +0200 Received: (from wcp@localhost) by luppolo.lpds.sublink.org (8.6.12/8.6.9) id UAA00344; Thu, 3 Apr 1997 20:34:51 +0200 Date: Thu, 3 Apr 1997 20:34:51 +0200 Message-Id: <199704031834.UAA00344@luppolo.lpds.sublink.org> From: wcp@luppolo.lpds.sublink.org (Walter C. Pelissero) X-Attribution: WcP To: freebsd-scsi@freebsd.org Subject: bus device reset Comments: Hyperbole mail buttons accepted, v3.18.5. Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Sorry for the ignorance, but what is going wrong when this message come up? Apr 3 20:24:58 luppolo /kernel: ahc0: target 0, lun 0 (sd0) timed out Apr 3 20:24:58 luppolo /kernel: sd0(ahc0:0:0): BUS DEVICE RESET message queued. Apr 3 20:24:58 luppolo /kernel: sd0(ahc0:0:0): UNIT ATTENTION asc:29,0 Apr 3 20:24:58 luppolo /kernel: sd0(ahc0:0:0): Power on, reset, or bus device reset occurred Apr 3 20:24:58 luppolo /kernel: , retries:4 This on FreeBSD 2.1.0-RELEASE, a 1GB Quantum Fireball (sd0) and an Adaptec 2940. From owner-freebsd-scsi Fri Apr 4 19:36:08 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA18450 for freebsd-scsi-outgoing; Fri, 4 Apr 1997 19:36:08 -0800 (PST) Received: from gargoyle.bazzle.com (gargoyle.bazzle.com [206.103.246.190]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA18442 for ; Fri, 4 Apr 1997 19:36:04 -0800 (PST) Received: from gargoyle.bazzle.com (net2.bazzle.com [206.103.246.189]) by gargoyle.bazzle.com (8.8.5/8.6.12) with SMTP id WAA06504; Fri, 4 Apr 1997 22:36:04 -0500 (EST) Date: Fri, 4 Apr 1997 22:36:04 -0500 (EST) From: "Eric J. Chet" To: gibbs@plutotech.com cc: freebsd-scsi@FreeBSD.ORG Subject: ahc errors after lite2 upgrade 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 Hello I just upgraded my machine from pre-lite2 to post lite2 -current. I'm seeing some errors I have never seen before. Apr 4 09:33:43 gargoyle /kernel: sd0: RECOVERED ERROR info:47e446 asc:18,1 Apr 4 09:33:43 gargoyle /kernel: sd0: Recovered data with error correction & retries applied field replaceable unit: d0 sks:80,2 Apr 4 09:33:43 gargoyle /kernel: , retries:4 Apr 4 15:03:01 gargoyle /kernel: sd0: RECOVERED ERROR info:47e446 asc:18,1 Apr 4 15:03:01 gargoyle /kernel: sd0: Recovered data with error correction & retries applied field replaceable unit: d0 sks:80,3 Apr 4 15:03:01 gargoyle /kernel: , retries:4 Apr 4 15:03:01 gargoyle /kernel: sd0: RECOVERED ERROR info:47e446 asc:17,1 Recovered data with retries field replaceable unit: d0 sks:80,1 Apr 4 15:03:01 gargoyle /kernel: , retries:3 Apr 4 15:03:02 gargoyle /kernel: sd0: RECOVERED ERROR info:47e446 asc:17,1 Recovered data with retries field replaceable unit: d0 sks:80,1 Apr 4 15:03:02 gargoyle /kernel: , retries:2 Apr 4 15:03:02 gargoyle /kernel: sd0: RECOVERED ERROR info:47e446 asc:18,1 Apr 4 15:03:02 gargoyle /kernel: sd0: Recovered data with error correction & retries applied field replaceable unit: d0 sks:80,2 Apr 4 15:03:02 gargoyle /kernel: , retries:1 Apr 4 16:18:42 gargoyle /kernel: sd0: RECOVERED ERROR info:47e446 asc:18,1 Apr 4 16:18:42 gargoyle /kernel: sd0: Recovered data with error correction & retries applied field replaceable unit: d0 sks:80,2 Apr 4 16:18:42 gargoyle /kernel: , retries:4 Should I be alarmed? What can I do to help track down this problem? I will include a dmesg below. Thanks, Eric J. Chet - ejc@naserver1.cb.lucent.com - ejc@bazzle.com Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.0-CURRENT #0: Fri Apr 4 08:26:03 EST 1997 root@gargoyle..bazzle.com:/var/usr/src/sys/compile/gargoyle CPU: Pentium (133.64-MHz 586-class CPU) Origin = "GenuineIntel" Id = 0x526 Stepping=6 Features=0x3bf real memory = 100663296 (98304K bytes) avail memory = 96538624 (94276K bytes) bdevsw_add_generic: adding D_DISK flag for device 15 Probing for devices on PCI bus 0: chip0 rev 1 on pci0:0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 vga0 rev 0 int a irq 11 on pci0:8:0 ahc0 rev 0 int a irq 9 on pci0:12:0 ahc0: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs ahc0: waiting for scsi devices to settle scbus0 at ahc0 bus 0 sd2 at scbus0 target 0 lun 0 sd2: type 0 fixed SCSI 2 sd2: Direct-Access 49MB (102171 512 byte sectors) sd2: with 1219 cyls, 2 heads, and an average 41 sectors/track sd1 at scbus0 target 1 lun 0 sd1: type 0 fixed SCSI 2 sd1: Direct-Access 234MB (479350 512 byte sectors) sd1: with 1818 cyls, 4 heads, and an average 65 sectors/track ahc0:A:2: refuses synchronous negotiation. Using asynchronous transfers cd0 at scbus0 target 2 lun 0 cd0: type 5 removable SCSI 2 cd0: CD-ROM cd present [257675 x 2048 byte records] ahc0: target 8 Tagged Queuing Device sd0 at scbus0 target 8 lun 0 sd0: type 0 fixed SCSI 2 sd0: Direct-Access 4095MB (8388315 512 byte sectors) sd0: with 3712 cyls, 21 heads, and an average 107 sectors/track 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 psm0 at 0x60-0x64 irq 12 on motherboard psm0: device ID 0, 3 buttons lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in 1 3C5x9 board(s) on ISA found at 0x300 ep0 at 0x300-0x30f irq 10 on isa ep0: aui/utp[*UTP*] address 00:60:8c:be:95:13 npx0 on motherboard npx0: INT 16 interface From owner-freebsd-scsi Fri Apr 4 19:46:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id TAA18641 for freebsd-scsi-outgoing; Fri, 4 Apr 1997 19:46:07 -0800 (PST) Received: from pluto.plutotech.com (root@pluto.plutotech.com [206.168.67.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA18636 for ; Fri, 4 Apr 1997 19:46:04 -0800 (PST) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id UAA09792; Fri, 4 Apr 1997 20:46:06 -0700 (MST) Message-Id: <199704050346.UAA09792@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: "Eric J. Chet" cc: gibbs@plutotech.com, freebsd-scsi@FreeBSD.ORG Subject: Re: ahc errors after lite2 upgrade In-reply-to: Your message of "Fri, 04 Apr 1997 22:36:04 EST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Apr 1997 20:43:43 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is your drive trying to tell you that it is starting to go bad. It had to retry a few times in order to get either a read or write to complete successfully. This doesn't have anything to do with the ahc driver other then that it is properly retrieving the sense codes when your drive reports an error. >Hello > I just upgraded my machine from pre-lite2 to post lite2 -current. >I'm seeing some errors I have never seen before. > >Apr 4 09:33:43 gargoyle /kernel: sd0: RECOVERED ERROR info:47e446 >asc:18,1 >Apr 4 09:33:43 gargoyle /kernel: sd0: Recovered data with error >correction & retries applied field replaceable unit: d0 sks:80,2 -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Sat Apr 5 04:10:22 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id EAA03863 for freebsd-scsi-outgoing; Sat, 5 Apr 1997 04:10:22 -0800 (PST) Received: from gargoyle.bazzle.com (gargoyle.bazzle.com [206.103.246.190]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA03857 for ; Sat, 5 Apr 1997 04:10:16 -0800 (PST) Received: from gargoyle.bazzle.com (net2.bazzle.com [206.103.246.189]) by gargoyle.bazzle.com (8.8.5/8.6.12) with SMTP id HAA08749; Sat, 5 Apr 1997 07:10:17 -0500 (EST) Date: Sat, 5 Apr 1997 07:10:17 -0500 (EST) From: "Eric J. Chet" To: "Justin T. Gibbs" cc: freebsd-scsi@freebsd.org Subject: Re: ahc errors after lite2 upgrade In-Reply-To: <199704050346.UAA09792@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 Justin Thank you for the conformation, this was my first guest. I was hoping it was just an anomaly in the latest driver. Another 'Cuda' about to bite the dust, it's 1.5 years old and has been running 24x7. Thanks, Eric J. Chet - ejc@naserver1.cb.lucent.com - ejc@bazzle.com From owner-freebsd-scsi Sat Apr 5 07:08:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id HAA12015 for freebsd-scsi-outgoing; Sat, 5 Apr 1997 07:08:51 -0800 (PST) Received: from ami.tom.computerworks.net (root@AMI.RES.CMU.EDU [128.2.95.1]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id HAA12010 for ; Sat, 5 Apr 1997 07:08:47 -0800 (PST) Received: from bonkers.taronga.com by ami.tom.computerworks.net with smtp (Smail3.1.29.1 #1) id m0wDX4W-0021UoC; Sat, 5 Apr 97 10:08 EST Received: (from peter@localhost) by bonkers.taronga.com (8.6.11/8.6.9) id JAA21124; Sat, 5 Apr 1997 09:08:54 -0600 Date: Sat, 5 Apr 1997 09:08:54 -0600 From: peter@taronga.com (Peter da Silva) Message-Id: <199704051508.JAA21124@bonkers.taronga.com> To: sadmin@roundtable.cif.rochester.edu, scsi@freebsd.org Subject: Re: exabyte problems Newsgroups: taronga.freebsd.scsi In-Reply-To: <199704042105.QAA18369@roundtable.cif.rochester.edu> Organization: none Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've had problems with Adaptec controllers and Exabytes too. I've tried everything short of tearing the drive open and playing ROM version games. Several people have recommended that solution, I'm just too short on time. From owner-freebsd-scsi Sat Apr 5 08:07:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id IAA14236 for freebsd-scsi-outgoing; Sat, 5 Apr 1997 08:07:48 -0800 (PST) Received: from phoenix.volant.org (phoenix.volant.org [205.179.79.193]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id IAA14231 for ; Sat, 5 Apr 1997 08:07:44 -0800 (PST) From: patl@Phoenix.Volant.ORG Received: from asimov.Phoenix.Volant.ORG [205.179.79.65] by phoenix.volant.org with smtp (Exim 1.59 #1) id 0wDY07-0000xi-00; Sat, 5 Apr 1997 08:07:35 -0800 Received: from localhost by asimov.Phoenix.Volant.ORG (5.x/SMI-SVR4) id AA09311; Sat, 5 Apr 1997 08:07:37 -0800 Date: Sat, 5 Apr 1997 08:07:37 -0800 (PST) Reply-To: patl@Phoenix.Volant.ORG Subject: Forwarded: [Density codes for EXB-8505 tape drive] To: freebsd-scsi@freebsd.org 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 sent the following to -questions a week ago; and have recieved no response. I have also been unable to find anything helpful in the Exabyte Web site or the FreeBSD mail archives. ] I just bought a reconditioned Exabyte EXB-8505 8mm tape drive. Unfortunately, it didn't come with an Owner's Manual; and I'm having some trouble identifying the appropriate density codes to use with it. The default appears to be 0x8c. According to the lights, that is a compressed format; and I would assume it is the highest supported base density (5G). But what are the codes for uncompressed 5G, and both compressed and uncompressed 2.5G modes? On a related note, what is the 'right' way to bind the supported densities to the four tape modes at boot time? (I would guess it's just an 'mt' command for each ctl device, somewhere in the rc files. But I'm hoping that I'm overlooking some more elegant hook provided for exactly this purpose...) Thanks, -Pat From owner-freebsd-scsi Sat Apr 5 10:44:37 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id KAA21606 for freebsd-scsi-outgoing; Sat, 5 Apr 1997 10:44:37 -0800 (PST) Received: from salmon.maths.tcd.ie (mmdf@salmon.maths.tcd.ie [134.226.81.11]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id KAA21598 for ; Sat, 5 Apr 1997 10:44:34 -0800 (PST) Received: from gosset.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id aa25109; 5 Apr 97 19:44 +0100 To: freebsd-scsi@freebsd.org Subject: SCSI freezes in 2.2-STABLE Date: Sat, 05 Apr 1997 19:44:31 +0100 From: David Malone Message-ID: <9704051944.aa25109@salmon.maths.tcd.ie> Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've just upgraded a machine from 2.1.7.1 to 2.2-STABLE ( up to ctm level 224 ) - I've been getting some nasty SCSI damage. Here is the most recent hang - the lines may be a bit messed up 'cos the machine hung again while I was writing this mail, and I had to use the scroll back buffer to get them. The machine has 2 2940's, on the first one there is a CD Rom, and 2 connor file pro's. On the second is a conor file pro, and a Quantum Atlas. I've upgraded the firmware on the atlas incase that is the problem, but it still fell over. TAGed stuff is off. I've tried MEMIO both on and off, and neither seems to solve the problem. I'm going to try the 2 new CTM patches next. David. Apr 5 11:47:40 synge /kernel: sd9(ahc1:1:0): Direct-Access 4101MB (8399520 Apr 5 11:47:40 synge /kernel: (ahc1:1:0): "Quantum XP34300 L915" type 0 fix Apr 5 11:47:40 synge /kernel: sd8(ahc1:0:0): Direct-Access 2048MB (4194304 Apr 5 11:47:40 synge /kernel: (ahc1:0:0): "CONNER CFP2107S 2.14GB 1420" ty Apr 5 11:47:40 synge /kernel: ahc1: aic7870 Single Channel, SCSI Id=7, 16 S Apr 5 11:47:40 synge /kernel: ahc1 rev 3 irq 10 on pci0:19 Apr 5 11:47:40 synge /kernel: cd0(ahc0:3:0): CD-ROM can't get the size Apr 5 11:47:40 synge /kernel: (ahc0:3:0): "TOSHIBA CD-ROM XM-5301TA 0925" t Apr 5 11:47:40 synge /kernel: sd1(ahc0:1:0): Direct-Access 2048MB (4194304 Apr 5 11:47:40 synge /kernel: (ahc0:1:0): "CONNER CFP2107S 2.14GB 1420" ty Apr 5 11:47:40 synge /kernel: sd0(ahc0:0:0): Direct-Access 2048MB (4194304 Apr 5 11:47:40 synge /kernel: (ahc0:0:0): "CONNER CFP2107S 2.14GB 1420" ty Apr 5 11:47:40 synge /kernel: ahc0: aic7870 Single Channel, SCSI Id=7, 16 S Apr 5 11:23:26 synge /kernel: sd8(ahc1:0:0): SCB 0x2 timedout while recovery Apr 5 11:23:26 synge /kernel: sd9(ahc1:1:0): SCB 0x3 timedout while recovery Apr 5 11:23:26 synge /kernel: sd8(ahc1:0:0): SCB 0x1 timedout while recovery Apr 5 11:23:26 synge /kernel: sd9(ahc1:1:0): abort message in message buffer Apr 5 11:23:26 synge /kernel: SEQADDR == 0x143 se, SCSISIGI == 0x86 Apr 5 11:23:26 synge /kernel: sd9(ahc1:1:0): SCB 0x0 - timed out in command Apr 5 11:22:44 synge last message repeated 7 times From owner-freebsd-scsi Sat Apr 5 11:17:07 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id LAA22753 for freebsd-scsi-outgoing; Sat, 5 Apr 1997 11:17:07 -0800 (PST) Received: from salmon.maths.tcd.ie (mmdf@salmon.maths.tcd.ie [134.226.81.11]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id LAA22748 for ; Sat, 5 Apr 1997 11:17:05 -0800 (PST) Received: from graves.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id aa27005; 5 Apr 97 20:17 +0100 To: freebsd-scsi@freebsd.org Subject: SCSI freezes in 2.2-STABLE In-reply-to: <9704051944.aa25109@salmon.maths.tcd.ie> Date: Sat, 05 Apr 1997 20:17:03 +0100 From: David Malone Message-ID: <9704052017.aa27005@salmon.maths.tcd.ie> Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If it helps any these occured just before the last hang. David. Apr 5 19:30:06 synge /kernel: ahc1: ahc_intr - referenced scb not valid during scsiint 0x8b scb(255) Apr 5 19:30:06 synge /kernel: SIMODE0 = 0x0, SIMODE1 = 0xa4, SSTAT0 = 0x37 Apr 5 19:30:06 synge /kernel: SEQADDR = 0x5 Apr 5 19:30:15 synge /kernel: sd9(ahc1:1:0): SCB 0x2 - timed out while idle, LA STPHASE == 0x1, SCSISIGI == 0xe6 Apr 5 19:30:15 synge /kernel: SEQADDR == 0x5 Apr 5 19:30:15 synge /kernel: sd9(ahc1:1:0): Queueing an Abort SCB From owner-freebsd-scsi Sat Apr 5 14:08:44 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id OAA29964 for freebsd-scsi-outgoing; Sat, 5 Apr 1997 14:08:44 -0800 (PST) Received: from pluto.plutotech.com (root@pluto.plutotech.com [206.168.67.1]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA29951 for ; Sat, 5 Apr 1997 14:08:41 -0800 (PST) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.3) with ESMTP id PAA26098; Sat, 5 Apr 1997 15:08:38 -0700 (MST) Message-Id: <199704052208.PAA26098@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: David Malone cc: freebsd-scsi@freebsd.org Subject: Re: SCSI freezes in 2.2-STABLE In-reply-to: Your message of "Sat, 05 Apr 1997 20:17:03 +0100." <9704052017.aa27005@salmon.maths.tcd.ie> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 05 Apr 1997 15:06:08 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >If it helps any these occured just before the last hang. Actually, it helps quite a bit. I just fixed one bug in the selection timeout handler of the driver that will remove the "referenced scb not valid..." message, but doesn't explain why you got a selection timeout in the first place. The second bit of interesting information here is that even though we had been reselected (SELDI is true in SSTAT0), the driver didn't see it since the current sequencer address shows we're still looking for work to do. I made a change to the sequencer that may affect that problem since the poll for work loop was the only place in the driver where we attempted to test for more than a single bit in that register at a time. Its a shot in the dark, but it may solve this problem. Let me know how these changes fair for you. I don't know when the next CTM delta will be generated though... > David. > >Apr 5 19:30:06 synge /kernel: ahc1: ahc_intr - referenced scb not valid durin >g >scsiint 0x8b scb(255) > >Apr 5 19:30:06 synge /kernel: SIMODE0 = 0x0, SIMODE1 = 0xa4, SSTAT0 = 0x37 > >Apr 5 19:30:06 synge /kernel: SEQADDR = 0x5 > >Apr 5 19:30:15 synge /kernel: sd9(ahc1:1:0): SCB 0x2 - timed out while idle, >LA >STPHASE == 0x1, SCSISIGI == 0xe6 > >Apr 5 19:30:15 synge /kernel: SEQADDR == 0x5 > >Apr 5 19:30:15 synge /kernel: sd9(ahc1:1:0): Queueing an Abort SCB -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-scsi Sat Apr 5 15:58:30 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id PAA09540 for freebsd-scsi-outgoing; Sat, 5 Apr 1997 15:58:30 -0800 (PST) Received: from salmon.maths.tcd.ie (mmdf@salmon.maths.tcd.ie [134.226.81.11]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id PAA09532 for ; Sat, 5 Apr 1997 15:58:25 -0800 (PST) Received: from graves.maths.tcd.ie by salmon.maths.tcd.ie with SMTP id aa08317; 6 Apr 97 0:58 +0100 To: "Justin T. Gibbs" cc: freebsd-scsi@freebsd.org, nops@maths.tcd.ie Subject: Re: SCSI freezes in 2.2-STABLE In-reply-to: Your message of "Sat, 05 Apr 1997 15:06:08 PDT." <199704052208.PAA26098@pluto.plutotech.com> Date: Sun, 06 Apr 1997 00:58:21 +0100 From: David Malone Message-ID: <9704060058.aa08317@salmon.maths.tcd.ie> Sender: owner-freebsd-scsi@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Actually, it helps quite a bit. I just fixed one bug in the selection > timeout handler of the driver that will remove the "referenced scb not > valid..." message, but doesn't explain why you got a selection timeout in > the first place. The second bit of interesting information here is that > even though we had been reselected (SELDI is true in SSTAT0), the driver > didn't see it since the current sequencer address shows we're still > looking for work to do. I made a change to the sequencer that may affect > that problem since the poll for work loop was the only place in the driver > where we attempted to test for more than a single bit in that register at > a time. Its a shot in the dark, but it may solve this problem. Let me > know how these changes fair for you. I don't know when the next CTM delta > will be generated though... I'll grab the delta as soon as it appears. Going up to CTM delta 226 helped a bit, the machine can now atleast fsck the disks when it reboots ( so far ). We've had two more crashes, I've a vmcore for the first of them, if its of any interest. The panic reason was "Couldn't find busy SCB". Here is the log messages for the second. Apr 5 22:58:37 synge /kernel: ahc1: ahc_intr - referenced scb not valid during scsiint 0x8b scb(255) Apr 5 22:58:37 synge /kernel: SIMODE0 = 0x0, SIMODE1 = 0xa4, SSTAT0 = 0x37 Apr 5 22:58:37 synge /kernel: SEQADDR = 0x5 Apr 5 22:58:47 synge /kernel: sd9(ahc1:1:0): SCB 0x1 - timed out while idle, LASTPHASE == 0x1, SCSISIGI == 0xe6 Apr 5 22:58:47 synge /kernel: SEQADDR == 0x5 Apr 5 22:58:47 synge /kernel: sd9(ahc1:1:0): Queueing an Abort SCB Apr 5 22:58:47 synge /kernel: sd8(ahc1:0:0): SCB 0x2 timedout while recovery in progress Apr 5 22:58:47 synge /kernel: sd9(ahc1:1:0): SCB 0x0 timedout while recovery in progress Apr 5 22:58:47 synge /kernel: sd8(ahc1:0:0): SCB 0x3 timedout while recovery in progress The machine seems to pretty quickly, so we've stopped accepting news for the moment. David. From owner-freebsd-scsi Sat Apr 5 17:25:48 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA13403 for freebsd-scsi-outgoing; Sat, 5 Apr 1997 17:25:48 -0800 (PST) Received: from nexgen.hiwaay.net (max2-145.HiWAAY.net [208.147.145.145]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA13397 for ; Sat, 5 Apr 1997 17:25:44 -0800 (PST) Received: from nexgen (localhost [127.0.0.1]) by nexgen.hiwaay.net (8.8.5/8.8.4) with ESMTP id TAA12270; Fri, 4 Apr 1997 19:43:29 -0600 (CST) Message-Id: <199704050143.TAA12270@nexgen.hiwaay.net> X-Mailer: exmh version 1.6.9 8/22/96 To: Security Administrator cc: scsi@FreeBSD.ORG (FreeBSD Scsi) From: dkelly@hiwaay.net Subject: Re: exabyte problems In-reply-to: Message from Security Administrator of "Fri, 04 Apr 1997 16:05:48 EST." <199704042105.QAA18369@roundtable.cif.rochester.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Apr 1997 19:43:29 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Howdy, > > I have an Exabyte 8500 and it is NOT working properly. I was assured > by its previous owner that the drive was in perfect working condition, > but the moment that I added it to my SCSI chain on my FreeBSD 2.2.1 > system, it barfed. To be specific, I have an Adaptec 2940UW card with > two SCSI-III drives on one chain and the SCSI-I tape drive off another > ribbon cable. Whenever I try to write to the drive, it has a slew of > write errors that kill whatever process is trying use the device. > Neither dump nor tar are immune. Whenever I've had any kind of problems like you describe ("worked perfectly for me") with Exabyte tape drives the magic bullet was to download new firmware from Exabyte. Recently moved an 8500 from a Sun 4/470 to an SGI Crimson. It didn't quite work on the SGI. Would run for a while then the somebody got confused and the SGI would reset the SCSI bus after waiting 4 minutes. Of course it worked perfectly on the Sun. New firmware from Exabyte was a pain to figure out how/what to download from their site (seems like you need 3 sets of firmware, CPU, servos, and something else). And then I had to find a Windows host (with an Adaptec's DOS standard driver, ASPI?) to apply the firmware updates. Actually I think I used a DOS updater, not the Windows one. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. From owner-freebsd-scsi Sat Apr 5 17:25:51 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id RAA13419 for freebsd-scsi-outgoing; Sat, 5 Apr 1997 17:25:51 -0800 (PST) Received: from nexgen.hiwaay.net (max2-145.HiWAAY.net [208.147.145.145]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id RAA13399 for ; Sat, 5 Apr 1997 17:25:47 -0800 (PST) Received: from nexgen (localhost [127.0.0.1]) by nexgen.hiwaay.net (8.8.5/8.8.4) with ESMTP id TAA12247 for ; Fri, 4 Apr 1997 19:29:06 -0600 (CST) Message-Id: <199704050129.TAA12247@nexgen.hiwaay.net> X-Mailer: exmh version 1.6.9 8/22/96 To: scsi@FreeBSD.ORG From: dkelly@hiwaay.net Subject: Re: Baracuda BIOS levels In-reply-to: Message from asami@vader.cs.berkeley.edu (Satoshi Asami) of "Thu, 03 Apr 1997 21:20:40 PST." <199704040520.VAA11444@silvia.HIP.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 04 Apr 1997 19:29:06 -0600 Sender: owner-freebsd-scsi@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > * I have a pair of year-old ST32550W's in my freebsd box and have heard > * mentions of needing current BIOS to be able to handle the tagged command > * queueing stuff. What BIOS version should I be up to for this? > > Dunno about ST32550W's, but the ones we have: > > SEAGATE ST15150W 0023 > > appears to be working fine with tagged queuing. (I.e., the system > crashes from time to time with ahc, but it also happens without tagged > queuing.) > > Satoshi This works pretty good for me. Had a problem with the tape back in the -GAMMA days and haven't taken time to see if its fixed now or not. ahc0 rev 0 int a irq 11 on pci0:6 ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle ahc0: target 0 Tagged Queuing Device (ahc0:0:0): "SEAGATE ST32550N 0021" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2047MB (4194058 512 byte sectors) (ahc0:6:0): "ARCHIVE ANCDA 2750 28077 -003" type 1 removable SCSI 2 st0(ahc0:6:0): Sequential-Access density code 0x15, 512-byte blocks, write-protected -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system.