From owner-freebsd-scsi Mon Feb 21 0:49:10 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from procsys.com (PPP-190-187.bng.vsnl.net.in [203.197.190.187]) by hub.freebsd.org (Postfix) with SMTP id C8F3137BBE5 for ; Mon, 21 Feb 2000 00:47:39 -0800 (PST) (envelope-from nanda@procsys.com) Received: from nanda ([192.168.1.70]) by procsys.com with SMTP; Mon, 21 Feb 2000 13:23:06 +0800 Message-ID: <38B0EF77.61E2@procsys.com> Date: Mon, 21 Feb 2000 13:25:35 +0530 From: Nanda Kumar Reply-To: nanda@procsys.com X-Mailer: Mozilla 3.01Gold (Win95; I) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.org Subject: Regarding SCSI block device driver Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have to write a SCSI block device driver for one RAID controller we have designed. Can anyone tell me how to go about it ? We have already one Windows miniport driver working for the same card. Please tell me a good sample driver to go through and if any document is available regarding how to write a SCSI block device driver and how it interacts with the system. I am quite new to the unix world. Thanks in advance, Nandan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 21 22:27:50 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from procsys.com (PPP-190-172.bng.vsnl.net.in [203.197.190.172]) by hub.freebsd.org (Postfix) with SMTP id 68AA837B5D5 for ; Mon, 21 Feb 2000 22:27:32 -0800 (PST) (envelope-from nanda@procsys.com) Received: from nanda ([192.168.1.70]) by procsys.com with SMTP; Tue, 22 Feb 2000 11:53:40 +0800 Message-ID: <38B22C09.2B7A@procsys.com> Date: Tue, 22 Feb 2000 11:56:17 +0530 From: Nanda Kumar Reply-To: nanda@procsys.com X-Mailer: Mozilla 3.01Gold (Win95; I) MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.org Subject: Help to write a SCSI block driver Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have to write a SCSI block device driver for one RAID controller we have designed. Can anyone tell me how to go about it ? We have already one Windows miniport driver working for the same card. Please tell me a good sample driver to go through and if any document is available regarding how to write a SCSI block device driver and how it interacts with the system. I am quite new to the unix world. Thanks in advance, Nandan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 21 22:53:20 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 0475237B642 for ; Mon, 21 Feb 2000 22:53:18 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id XAA16975; Mon, 21 Feb 2000 23:52:53 -0700 (MST) (envelope-from ken) Date: Mon, 21 Feb 2000 23:52:53 -0700 From: "Kenneth D. Merry" To: Nanda Kumar Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Help to write a SCSI block driver Message-ID: <20000221235253.A16855@panzer.kdm.org> References: <38B22C09.2B7A@procsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38B22C09.2B7A@procsys.com>; from nanda@procsys.com on Tue, Feb 22, 2000 at 11:56:17AM +0530 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Feb 22, 2000 at 11:56:17 +0530, Nanda Kumar wrote: > > I have to write a SCSI block device driver for one RAID controller we > have designed. Can anyone tell me how to go about it ? We have already > one Windows miniport driver working for the same card. Please tell me a > good sample driver to go through and if any document is available > regarding how to write a SCSI block device driver and how it interacts > with the system. I am quite new to the unix world. Well, the device model you use will really depend on what sort of interface your RAID controller presents. There are two basic categories that other RAID controllers fall into right now: - controllers that can function as a standard SCSI controller, as well as a RAID controller. (e.g. you could put a CDROM drive on the controller, and access it with standard SCSI commands) The DPT cards fall into this category. - controllers that function primarily as a RAID controller, and don't allow direct SCSI acess to devices on their busses. The AMI, Mylex, and Compaq SmartRAID controllers fall into this category. Controllers that fall into the first category would probably be best written as HBA drivers under the CAM SCSI layer. General documentation on CAM is located here: http://www.t10.org/drafts.htm#SWLAY Controllers that fall into the second category should probably written as block device drivers, like the AMI, Mylex, and Compaq drivers. The other RAID drivers are located in the following places in the FreeBSD source tree: DPT: src/sys/dev/dpt AMI: src/sys/dev/amr Mylex: src/sys/dev/mlx Compaq: src/sys/dev/ida If you want to look at plain SCSI card drivers, there are plenty to choose from as well. Here are a few samples: Adaptec AIC 7xxx chips: src/sys/dev/aic7xxx Advansys chips: src/sys/dev/advansys Symbios/LSI chips: src/sys/dev/sym Adaptec 154x-type boards: src/sys/dev/aha Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Mon Feb 21 23:27: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (castles543.castles.com [208.214.165.107]) by hub.freebsd.org (Postfix) with ESMTP id 1313537B5E3 for ; Mon, 21 Feb 2000 23:27:03 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id XAA08488; Mon, 21 Feb 2000 23:39:13 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002220739.XAA08488@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Kenneth D. Merry" Cc: Nanda Kumar , freebsd-scsi@FreeBSD.ORG Subject: Re: Help to write a SCSI block driver In-reply-to: Your message of "Mon, 21 Feb 2000 23:52:53 MST." <20000221235253.A16855@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Feb 2000 23:39:13 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > On Tue, Feb 22, 2000 at 11:56:17 +0530, Nanda Kumar wrote: > > > > I have to write a SCSI block device driver for one RAID controller we > > have designed. Can anyone tell me how to go about it ? We have already > > one Windows miniport driver working for the same card. Please tell me a > > good sample driver to go through and if any document is available > > regarding how to write a SCSI block device driver and how it interacts > > with the system. I am quite new to the unix world. > > Well, the device model you use will really depend on what sort of interface > your RAID controller presents. > > There are two basic categories that other RAID controllers fall into right > now: > > - controllers that can function as a standard SCSI controller, as well as > a RAID controller. (e.g. you could put a CDROM drive on the controller, > and access it with standard SCSI commands) The DPT cards fall into this > category. > > - controllers that function primarily as a RAID controller, and don't > allow direct SCSI acess to devices on their busses. The AMI, Mylex, and > Compaq SmartRAID controllers fall into this category. This is not actually correct; all of these adapters have SCSI passthrough interfaces (except perhaps the Compaq controller, which I haven't looked at that closely). However, excluding the DPT (which I am not familiar with), none of these controllers present an interface which looks anything at all like a SCSI disk between a managed array and the system, and thus it's not appropriate to use CAM and the 'da' driver to talk to them. The Mylex driver, at least, will be growing a CAM passthrough for non-disk devices at some point in time. -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 22 2:26:31 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from procsys.com (PPP-190-123.bng.vsnl.net.in [203.197.190.123]) by hub.freebsd.org (Postfix) with SMTP id B3D6537B55E for ; Tue, 22 Feb 2000 02:26:02 -0800 (PST) (envelope-from nanda@procsys.com) Received: from nanda ([192.168.1.70]) by procsys.com with SMTP; Tue, 22 Feb 2000 15:57:38 +0800 Message-ID: <38B2653A.41C5@procsys.com> Date: Tue, 22 Feb 2000 16:00:18 +0530 From: Nanda Kumar Reply-To: nanda@procsys.com X-Mailer: Mozilla 3.01Gold (Win95; I) MIME-Version: 1.0 To: "Kenneth D. Merry" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Help to write a SCSI block driver References: <38B22C09.2B7A@procsys.com> <20000221235253.A16855@panzer.kdm.org> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, The card that i am using is a RAID adapter and the RAID functionality is implemented in the firmware running on the adapter. Hence it can be treated as a normal SCSI adapter as far as the driver is concerned. So i think i can write the device driver as SCSI block device driver. Is there any documentation available on how the SCSI block device driver interacts with the system ? Thanks a lot Regards, Nandan >Kenneth D. Merry wrote: > > On Tue, Feb 22, 2000 at 11:56:17 +0530, Nanda Kumar wrote: > > > > I have to write a SCSI block device driver for one RAID controller we > > have designed. Can anyone tell me how to go about it ? We have already > > one Windows miniport driver working for the same card. Please tell me a > > good sample driver to go through and if any document is available > > regarding how to write a SCSI block device driver and how it interacts > > with the system. I am quite new to the unix world. > > Well, the device model you use will really depend on what sort of interface > your RAID controller presents. > > There are two basic categories that other RAID controllers fall into right > now: > > - controllers that can function as a standard SCSI controller, as well as > a RAID controller. (e.g. you could put a CDROM drive on the controller, > and access it with standard SCSI commands) The DPT cards fall into this > category. > > - controllers that function primarily as a RAID controller, and don't > allow direct SCSI acess to devices on their busses. The AMI, Mylex, and > Compaq SmartRAID controllers fall into this category. > > Controllers that fall into the first category would probably be best > written as HBA drivers under the CAM SCSI layer. General documentation on > CAM is located here: > > http://www.t10.org/drafts.htm#SWLAY > > Controllers that fall into the second category should probably written as > block device drivers, like the AMI, Mylex, and Compaq drivers. > > The other RAID drivers are located in the following places in the FreeBSD > source tree: > > DPT: src/sys/dev/dpt > AMI: src/sys/dev/amr > Mylex: src/sys/dev/mlx > Compaq: src/sys/dev/ida > > If you want to look at plain SCSI card drivers, there are plenty to choose > from as well. Here are a few samples: > > Adaptec AIC 7xxx chips: src/sys/dev/aic7xxx > Advansys chips: src/sys/dev/advansys > Symbios/LSI chips: src/sys/dev/sym > Adaptec 154x-type boards: src/sys/dev/aha > > Ken > -- > Kenneth Merry > ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 22 9:23:28 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 724CC37B6F0 for ; Tue, 22 Feb 2000 09:23:24 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id KAA20369; Tue, 22 Feb 2000 10:23:14 -0700 (MST) (envelope-from ken) Date: Tue, 22 Feb 2000 10:23:14 -0700 From: "Kenneth D. Merry" To: Nanda Kumar Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Help to write a SCSI block driver Message-ID: <20000222102314.A20290@panzer.kdm.org> References: <38B22C09.2B7A@procsys.com> <20000221235253.A16855@panzer.kdm.org> <38B2653A.41C5@procsys.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38B2653A.41C5@procsys.com>; from nanda@procsys.com on Tue, Feb 22, 2000 at 04:00:18PM +0530 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, Feb 22, 2000 at 16:00:18 +0530, Nanda Kumar wrote: > > The card that i am using is a RAID adapter and the RAID functionality is > implemented in the firmware running on the adapter. Hence it can be > treated as a normal SCSI adapter as far as the driver is concerned. So i > think i can write the device driver as SCSI block device driver. Is > there any documentation available on how the SCSI block device driver > interacts with the system ? So I could put tape drives, CDROM drives, DVD drives, etc. on your controller and expect to access them normally? Does the RAID array appear as a disk on the SCSI bus? There are several documents describing the general design of the CAM subsystem. See the CAM specs here: > >Kenneth D. Merry wrote: > > Controllers that fall into the first category would probably be best > > written as HBA drivers under the CAM SCSI layer. General documentation on > > CAM is located here: > > > > http://www.t10.org/drafts.htm#SWLAY Also, see Justin's presentation on CAM from USENIX '98: http://www.freebsd.org/~gibbs/ Some example SCSI drivers to look at are here: > > If you want to look at plain SCSI card drivers, there are plenty to choose > > from as well. Here are a few samples: > > > > Adaptec AIC 7xxx chips: src/sys/dev/aic7xxx > > Advansys chips: src/sys/dev/advansys > > Symbios/LSI chips: src/sys/dev/sym > > Adaptec 154x-type boards: src/sys/dev/aha If you've got more questions on the interaction between the CAM transport layer (XPT) and hardware adapter drivers (SIM layer), just send mail to this list. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Tue Feb 22 10:49:17 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 51FB737B73A; Tue, 22 Feb 2000 10:49:15 -0800 (PST) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id LAA66028; Tue, 22 Feb 2000 11:35:46 -0700 (MST) Date: Tue, 22 Feb 2000 11:35:46 -0700 (MST) From: "Justin T. Gibbs" Message-Id: <200002221835.LAA66028@narnia.plutotech.com> To: Mike Smith Cc: scsi@FreeBSD.ORG Subject: Re: Help to write a SCSI block driver X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <200002220739.XAA08488@mass.cdrom.com> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > This is not actually correct; all of these adapters have SCSI passthrough > interfaces (except perhaps the Compaq controller, which I haven't looked > at that closely). > > However, excluding the DPT (which I am not familiar with), none of these > controllers present an interface which looks anything at all like a SCSI > disk between a managed array and the system, and thus it's not appropriate > to use CAM and the 'da' driver to talk to them. > > The Mylex driver, at least, will be growing a CAM passthrough for > non-disk devices at some point in time. This always seemed to be the correct approach to me. I don't know why the orginal DPT driver was not first written as a block driver with an extra translation layer for "other" SCSI devices on the bus, but I don't know much about the DPT architecture. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 23 19:50:21 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mail2.netcologne.de (mail2.netcologne.de [194.8.194.103]) by hub.freebsd.org (Postfix) with ESMTP id 6CDC737B99E; Wed, 23 Feb 2000 19:50:16 -0800 (PST) (envelope-from van.woerkom@netcologne.de) Received: from oranje.my.domain (dial7-163.netcologne.de [195.14.235.163]) by mail2.netcologne.de (8.9.3/8.9.3) with ESMTP id EAA25768; Thu, 24 Feb 2000 04:50:09 +0100 (MET) Received: (from marc@localhost) by oranje.my.domain (8.9.3/8.9.3) id EAA27316; Thu, 24 Feb 2000 04:50:24 +0100 (CET) (envelope-from van.woerkom@netcologne.de) Date: Thu, 24 Feb 2000 04:50:24 +0100 (CET) Message-Id: <200002240350.EAA27316@oranje.my.domain> X-Authentication-Warning: oranje.my.domain: marc set sender to van.woerkom@netcologne.de using -f From: Marc van Woerkom To: lamaster@nren.nasa.gov Cc: freebsd-scsi@FreeBSD.ORG, se@FreeBSD.ORG In-reply-to: (message from Hugh LaMaster on Mon, 14 Feb 2000 16:32:28 -0800 (PST)) Subject: Re: SC200/ncr53c810 problems Reply-To: van.woerkom@netcologne.de References: Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > Now I believe the SC200 card sucks for some unknown reason. > > I've used an early SC200 for years; haven't seen any problem > on a system that was pre-CAM (was 3.0-current as of last > March or so?), hasn't been updated since. I'm hoping that > it will still work fine when I go to 3.4-STABLE ... > > Anyway, it isn't a bad card, although it doesn't have IRQ > flexibility. (That reminds me: can any/all FreeBSD PCI drivers > share IRQ's? I'm running out (SCSI controller, EIDE, Audio, > Video card, ... ) If so, any pointers to documentation? I replaced the SC200 (ncr810) with a Tekram DC-390F (ncr875) controler, after seing it recommended by Stefan and that company supporting FreeBSD sym0: <875> port 0x6900-0x69ff mem 0xe2000000-0xe2000fff,0xe2002000-0xe20020ff irq 11 at device 13.0 on pci0 sym0: Tekram NVRAM, ID 7, Fast-20, SE, parity checking da0 at sym0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI-2 device da0: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da0: 2068MB (4235629 512 byte sectors: 255H 63S/T 263C) da1 at sym0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI-2 device da1: 40.000MB/s transfers (20.000MHz, offset 15, 16bit) da1: 4134MB (8467200 512 byte sectors: 255H 63S/T 527C) da2 at sym0 bus 0 target 2 lun 0 da2: Fixed Direct Access SCSI-2 device da2: 20.000MB/s transfers (20.000MHz, offset 15), Tagged Queueing Enabled da2: 2063MB (4226725 512 byte sectors: 255H 63S/T 263C) and now the system is stable again. I did a lot of simultaneous disk shuffling, audio playback, network access and accelerated OpenGL .. everything worked fine! Regards, Marc To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Wed Feb 23 22: 5: 2 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ns.smr.ru (ns.smr.ru [62.76.47.1]) by hub.freebsd.org (Postfix) with ESMTP id 65DB637BAC1 for ; Wed, 23 Feb 2000 22:04:58 -0800 (PST) (envelope-from adm@smr.ru) Received: from smr.ru (localhost [127.0.0.1]) by ns.smr.ru (8.9.3/8.9.3) with ESMTP id KAA95033 for ; Thu, 24 Feb 2000 10:07:54 +0400 (SAMT) (envelope-from adm@smr.ru) Message-ID: <38B4CABA.21FA2CD3@smr.ru> Date: Thu, 24 Feb 2000 10:07:54 +0400 From: Vladimir Kravchuk Organization: IPSI & SSAU X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: ru, en MIME-Version: 1.0 To: freebsd-scsi@FreeBSD.ORG Subject: Mylex DAC1164P driver for UP2000/DP264 Content-Type: text/plain; charset=koi8-r Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Where can I get Mylex eXtremeRAID DAC1164P driver for UP2000/DP264? -- Vladimir Kravchuk. e-mail:adm@smr.ru Phone:+7(8462)322-763 Fax:+7(8462)322-763 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 24 4:13:17 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from matrix.eurocontrol.fr (matrix.eurocontrol.fr [147.196.254.254]) by hub.freebsd.org (Postfix) with ESMTP id 5F73937BBBC for ; Thu, 24 Feb 2000 04:13:11 -0800 (PST) (envelope-from harald.weis@eurocontrol.fr) Received: from rigel.eurocontrol.fr (rigel.eurocontrol.fr [147.196.5.151]) by matrix.eurocontrol.fr (Postfix) with ESMTP id 0E91531F5 for ; Thu, 24 Feb 2000 13:13:10 +0100 (CET) (envelope-from harald.weis@eurocontrol.fr) Received: from eurocontrol.fr (localhost [127.0.0.1]) by rigel.eurocontrol.fr (Postfix) with ESMTP id 63BDC42C3 for ; Thu, 24 Feb 2000 13:13:09 +0100 (MET) Message-ID: <38B5203D.ACB5B5A0@eurocontrol.fr> Date: Thu, 24 Feb 2000 13:12:45 +0100 From: Harald Weis Organization: EUROCONTROL X-Mailer: Mozilla 4.61 [en] (X11; I; FreeBSD 3.3-RELEASE i386) X-Accept-Language: en MIME-Version: 1.0 To: freebsd-scsi@freebsd.org Subject: cdrecord package in FreeBSD 3.3 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear Sir, Can you please tell me whether the CD-writers HP 920i (8/4/32) and/or Plextor PX-W124TSi (12/4/32) are or will be supported by the cdrecord package ? Thank you in advance and best regards, Harald Weis PS: The SCSI controller will be the ASUS SC-200 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 24 7:18: 1 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ns.proteusweb.com (ns.proteusweb.com [213.38.19.130]) by hub.freebsd.org (Postfix) with ESMTP id 084F637BD6F for ; Thu, 24 Feb 2000 07:17:57 -0800 (PST) (envelope-from tris@proteusweb.com) Received: from rhino.proteusweb.com (tris@rhino.proteusweb.com [192.168.0.99]) by ns.proteusweb.com (8.8.5/8.8.5) with ESMTP id PAA19509 for ; Thu, 24 Feb 2000 15:23:59 GMT Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 24 Feb 2000 15:19:52 -0000 (GMT) From: Tristan Aston To: freebsd-scsi@freebsd.org Subject: RAID options Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ..I remember reading somewhere that you cant boot from a RAID device. Can anyone confirm this ? cheers, tristan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 24 7:21:17 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from richard2.pil.net (richard2.pil.net [207.8.164.9]) by hub.freebsd.org (Postfix) with SMTP id 3233E37BC02 for ; Thu, 24 Feb 2000 07:21:14 -0800 (PST) (envelope-from up@3.am) Received: (qmail 91159 invoked by uid 1825); 24 Feb 2000 15:21:11 -0000 Received: from localhost (sendmail-bs@127.0.0.1) by localhost with SMTP; 24 Feb 2000 15:21:11 -0000 Date: Thu, 24 Feb 2000 10:21:11 -0500 (EST) From: X-Sender: up@richard2.pil.net To: Tristan Aston Cc: freebsd-scsi@freebsd.org Subject: Re: RAID options In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, 24 Feb 2000, Tristan Aston wrote: > ..I remember reading somewhere that you > cant boot from a RAID device. > > Can anyone confirm this ? It depends on the RAID card...you can't boot from vinum volumes, IIRC... James Smallacombe PlantageNet, Inc. CEO and Janitor up@3.am http://3.am ========================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 24 7:55:44 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 5C27537BB42 for ; Thu, 24 Feb 2000 07:55:41 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id IAA38185; Thu, 24 Feb 2000 08:55:32 -0700 (MST) (envelope-from ken) Date: Thu, 24 Feb 2000 08:55:32 -0700 From: "Kenneth D. Merry" To: Harald Weis Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: cdrecord package in FreeBSD 3.3 Message-ID: <20000224085532.A38155@panzer.kdm.org> References: <38B5203D.ACB5B5A0@eurocontrol.fr> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38B5203D.ACB5B5A0@eurocontrol.fr>; from harald.weis@eurocontrol.fr on Thu, Feb 24, 2000 at 01:12:45PM +0100 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Feb 24, 2000 at 13:12:45 +0100, Harald Weis wrote: > Dear Sir, > > Can you please tell me whether the CD-writers > HP 920i (8/4/32) and/or Plextor PX-W124TSi (12/4/32) > are or will be supported by the cdrecord package ? > > Thank you in advance and best regards, > > Harald Weis > > PS: > The SCSI controller will be the ASUS SC-200 See the cdrecord web page for a list of supported drives: http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 24 14:14:51 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from eeyore.med.wayne.edu (eeyore.med.wayne.edu [146.9.3.19]) by hub.freebsd.org (Postfix) with ESMTP id 5370E37B925 for ; Thu, 24 Feb 2000 14:14:40 -0800 (PST) (envelope-from wroberts@med.wayne.edu) Received: from walt (pm589-46.dialip.mich.net [207.74.111.152]) by eeyore.med.wayne.edu (8.9.3/8.9.3) with ESMTP id RAA02864 for ; Thu, 24 Feb 2000 17:14:35 -0500 (EST) Message-ID: <004301bf7f15$5a0e7180$986f4acf@walt> From: "Walter A. Roberts" To: Subject: Fw: Adaptec 1542c and Exabyte 8200/tar: Device not config Date: Thu, 24 Feb 2000 17:20:19 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Dear folks: I was referred to this list for possible help on the problems with a recent installation of 3.2 BSD related to a need for SCSI. I swapped out my adaptec 1502 cheapie for a 1542c since the CAM drivers don't support the 1502 and I had the 1542c on the shelf, thinking this would be easy. Sigh. I would be willing to write a driver for the 1502, but I've never written UNIX drivers, just VMS drivers so I'm not sure how steep the learning curve would be, but if any of you'd be willing to coach a little I could give it a whack. I mainly (actually only) need the scsi on the UNIX side to read a tar file off an EXABYTE EXB-8200 scsi drive. If there's no hope for the present situation, if anyone knew of a way to get the stuff on the MS side onto other media (via the 1502/EXB), without a lot of contortions that would work too, although I know this part is way off the track of this list. Thanks for any help you can be. Technical details follow. At witts end, Walt Roberts >> >> Problem: Swapped ADAPTEC 1502 out to use ADAPTEC 1542C after installing >> 3.3.x and can't get tar (or mount or mt) to access the EXABYTE 8200 >> (scsi device 4) to read the device. >> >> History: Since no device drivers appeared to be available for the 1502 >> and I have tarred stuff on 8 mm (DEC ULTRIX tarred files), I tried to >> install the AHA-1542C board and an EXABYE-8200 (taken from the VAX) to >> read the files. >> >> The AHA installed and appeared to be properly identified by FreeBSD at >> all the right spots. During boot it tickled the exabyte numerous times >> (slowly), and came up fine. >> >> Camcontrol dev will show the aha1542 device on scbus0 but no devices. >> Camcontrol periph will show the aha1542 likewise. >> Camcontrol scan will then show the exabyte-8200 and hangs at this >> point. Kill -9 won't make this process go away. Only reboot does. >> >> Tar commands tried: >> tar -tf /dev/rsa0-6 >> (likewise mount and mt) > >Could you post the dmesg(8) output? >-- >Crist J. Clark cjclark@home.com Crist, Here are the dmesg, kernel config parms and camcontrol devlist -v outputs. Thanks for your interest and assistance. Walt wroberts@med.wayne.edu dmesg Copyright (c) 1992-1999 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 3.2-RELEASE #1: Sun Feb 20 10:30:35 EST 2000 root@research.pvt:/usr/src/sys/compile/RESEARCH Timecounter "i8254" frequency 1193182 Hz CPU: AMD-K6tm w/ multimedia extensions (233.87-MHz 586-class CPU) Origin = "AuthenticAMD" Id = 0x562 Stepping=2 Features=0x8001bf real memory = 67043328 (65472K bytes) config> di zp0 config> di ze0 config> di lnc0 config> di le0 config> di ie0 config> di fe0 config> di ex0 config> di ep0 config> di cs0 config> di wt0 config> di scd0 config> di mcd0 config> di matcdc0 config> di bt0 No such device: bt0 Invalid command or syntax. Type `?' for help. config> di adv0 No such device: adv0 Invalid command or syntax. Type `?' for help. config> q avail memory = 62033920 (60580K bytes) Preloaded elf kernel "kernel" at 0xc0308000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc030809c. Probing for devices on PCI bus 0: chip0: rev 0x03 on pci0.0.0 chip1: rev 0x00 on pci0.1.0 chip2: rev 0x41 on pci0.7.0 ide_pci0: rev 0x06 on pci0.7.1 chip3: rev 0x10 on pci0.7.3 ed1: rev 0x00 int a irq 11 on pci0.10.0 ed1: address 00:e0:29:18:a6:74, type NE2000 (16 bit) Probing for devices on PCI bus 1: vga0: rev 0x01 int a irq 4 on pci1.0.0 Probing for PnP devices: Probing for devices on the ISA bus: sc0 on isa sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa psm0 irq 12 on isa psm0: model Generic PS/2 mouse, device ID 0 sio0: configured irq 4 not in bitmap of probed irqs 0 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 8250 sio1: configured irq 3 not in bitmap of probed irqs 0 sio1 not found at 0x2f8 fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S wdc0: unit 1 (wd1): wd1: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (atapi): , removable, accel, dma, iordy acd0: drive speed 687 - 6187KB/sec, 128KB cache acd0: supported read types: CD-R, CD-RW, CD-DA acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: CD-ROM 120mm data disc loaded, unlocked ppc0 at 0x3bc irq 7 flags 0x40 on isa ppc0: Generic chipset (NIBBLE-only) in COMPATIBLE mode lpt0: on ppbus 0 lpt0: Interrupt-driven port ppi0: on ppbus 0 plip0: on ppbus 0 lpt0: on ppbus 0 lpt0: Interrupt-driven port aha0 at 0x330-0x333 irq 9 drq 5 on isa aha0: AHA-1542C FW Rev. 0.1 (ID=44) SCSI Host Adapter, SCSI ID 7, 16 CCBs vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa npx0 on motherboard npx0: INT 16 interface Waiting 5 seconds for SCSI devices to settle (probe0:aha0:0:0:0): CCB 0xc3cd5508 - timed out (probe0:aha0:0:0:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe6:aha0:0:6:0): CCB 0xc3cd5508 - timed out (probe6:aha0:0:6:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe0:aha0:0:0:0): CCB 0xc3cd5508 - timed out (probe0:aha0:0:0:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe6:aha0:0:6:0): CCB 0xc3cd5508 - timed out (probe6:aha0:0:6:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe0:aha0:0:0:0): CCB 0xc3cd5508 - timed out (probe0:aha0:0:0:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe6:aha0:0:6:0): CCB 0xc3cd5508 - timed out (probe6:aha0:0:6:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe0:aha0:0:0:0): CCB 0xc3cd5508 - timed out (probe0:aha0:0:0:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe6:aha0:0:6:0): CCB 0xc3cd5508 - timed out (probe6:aha0:0:6:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe0:aha0:0:0:0): CCB 0xc3cd5508 - timed out (probe0:aha0:0:0:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe6:aha0:0:6:0): CCB 0xc3cd5508 - timed out (probe6:aha0:0:6:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe1:aha0:0:1:0): CCB 0xc3cd5508 - timed out (probe1:aha0:0:1:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe5:aha0:0:5:0): CCB 0xc3cd5508 - timed out (probe5:aha0:0:5:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe1:aha0:0:1:0): CCB 0xc3cd5508 - timed out (probe1:aha0:0:1:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe5:aha0:0:5:0): CCB 0xc3cd5508 - timed out (probe5:aha0:0:5:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe1:aha0:0:1:0): CCB 0xc3cd5508 - timed out (probe1:aha0:0:1:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe5:aha0:0:5:0): CCB 0xc3cd5508 - timed out (probe5:aha0:0:5:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe1:aha0:0:1:0): CCB 0xc3cd5508 - timed out (probe1:aha0:0:1:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe5:aha0:0:5:0): CCB 0xc3cd5508 - timed out (probe5:aha0:0:5:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe1:aha0:0:1:0): CCB 0xc3cd5508 - timed out (probe1:aha0:0:1:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe5:aha0:0:5:0): CCB 0xc3cd5508 - timed out (probe5:aha0:0:5:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe2:aha0:0:2:0): CCB 0xc3cd5508 - timed out (probe2:aha0:0:2:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe4:aha0:0:4:0): CCB 0xc3cd5508 - timed out (probe4:aha0:0:4:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe2:aha0:0:2:0): CCB 0xc3cd5508 - timed out (probe2:aha0:0:2:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe4:aha0:0:4:0): CCB 0xc3cd5508 - timed out (probe4:aha0:0:4:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe2:aha0:0:2:0): CCB 0xc3cd5508 - timed out (probe2:aha0:0:2:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe4:aha0:0:4:0): CCB 0xc3cd5508 - timed out (probe4:aha0:0:4:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe2:aha0:0:2:0): CCB 0xc3cd5508 - timed out (probe2:aha0:0:2:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe4:aha0:0:4:0): CCB 0xc3cd5508 - timed out (probe4:aha0:0:4:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe2:aha0:0:2:0): CCB 0xc3cd5508 - timed out (probe2:aha0:0:2:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe4:aha0:0:4:0): CCB 0xc3cd5508 - timed out (probe4:aha0:0:4:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe3:aha0:0:3:0): CCB 0xc3cd5508 - timed out (probe3:aha0:0:3:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe3:aha0:0:3:0): CCB 0xc3cd5508 - timed out (probe3:aha0:0:3:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe3:aha0:0:3:0): CCB 0xc3cd5508 - timed out (probe3:aha0:0:3:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe3:aha0:0:3:0): CCB 0xc3cd5508 - timed out (probe3:aha0:0:3:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout (probe3:aha0:0:3:0): CCB 0xc3cd5508 - timed out (probe3:aha0:0:3:0): CCB 0xc3cd5508 - timed out aha0: No longer in timeout changing root device to wd0s1a kernel configuration file: # # GENERIC -- Generic machine with WD/AHx/NCR/BTx family disks # # 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.143.2.12 1999/05/14 15:12:26 jkh Exp $ machine "i386" cpu "I386_CPU" cpu "I486_CPU" cpu "I586_CPU" cpu "I686_CPU" ident GENERIC maxusers 32 options MATH_EMULATE #Support for x87 emulation options INET #InterNETworking options FFS #Berkeley Fast Filesystem options FFS_ROOT #FFS usable as root device [keep this!] options MFS #Memory Filesystem options MFS_ROOT #MFS usable as root device, "MFS" req'ed options NFS #Network Filesystem options NFS_ROOT #NFS usable as root device, "NFS" req'ed options MSDOSFS #MSDOS Filesystem options "CD9660" #ISO 9660 Filesystem options "CD9660_ROOT" #CD-ROM usable as root. "CD9660" req'ed options PROCFS #Process filesystem options "COMPAT_43" #Compatible with BSD 4.3 [KEEP THIS!] options SCSI_DELAY=5000 #Be less pessimistic Joe SCSI device options UCONSOLE #Allow users to grab the console options FAILSAFE #Be conservative options USERCONFIG #boot -c editor options VISUAL_USERCONFIG #visual boot -c editor config kernel root on wd0 # To make an SMP kernel, the next two are needed #options SMP # Symmetric MultiProcessor Kernel #options APIC_IO # Symmetric (APIC) I/O # Optionally these may need tweaked, (defaults shown): #options NCPU=2 # number of CPUs #options NBUS=4 # number of busses #options NAPIC=1 # number of IO APICs #options NINTR=24 # number of INTs controller isa0 controller pnp0 controller eisa0 controller pci0 controller fdc0 at isa? port "IO_FD1" bio irq 6 drq 2 disk fd0 at fdc0 drive 0 disk fd1 at fdc0 drive 1 options "CMD640" # work around CMD640 chip deficiency controller wdc0 at isa? port "IO_WD1" bio irq 14 disk wd0 at wdc0 drive 0 disk wd1 at wdc0 drive 1 controller wdc1 at isa? port "IO_WD2" bio irq 15 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 acd0 #IDE CD-ROM device wfd0 #IDE Floppy (e.g. LS-120) # 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 isp0 # This controller offers a number of configuration options, too many to # document here - see the LINT file in this directory and look up the # dpt0 entry there for much fuller documentation on this. controller dpt0 #controller adv0 at isa? port ? cam irq ? #controller adw0 #controller bt0 at isa? port ? cam irq ? controller aha0 at isa? port ? cam irq ? #only scsi around controller scbus0 at aha0 tape sa0 device pass0 device cd0 #Only need one of these, the code dynamically grows device wt0 at isa? port 0x300 bio irq 5 drq 1 device mcd0 at isa? port 0x300 bio irq 10 controller matcd0 at isa? port 0x230 bio device scd0 at isa? port 0x230 bio # atkbdc0 controlls both the keyboard and the PS/2 mouse controller atkbdc0 at isa? port IO_KBD tty device atkbd0 at isa? tty irq 1 device psm0 at isa? tty irq 12 device vga0 at isa? port ? conflicts # splash screen/screen saver pseudo-device splash # syscons is the default console driver, resembling an SCO console device sc0 at isa? tty # Enable this and PCVT_FREEBSD for pcvt vt220 compatible console driver #device vt0 at isa? tty #options XSERVER # support for X server #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 device npx0 at isa? port IO_NPX irq 13 # # Laptop support (see LINT for more options) # device apm0 at isa? disable flags 0x31 # Advanced Power Management # PCCARD (PCMCIA) support #controller card0 #device pcic0 at card? #device pcic1 at card? device sio0 at isa? port "IO_COM1" flags 0x10 tty irq 4 device sio1 at isa? port "IO_COM2" tty irq 3 device sio2 at isa? disable port "IO_COM3" tty irq 5 device sio3 at isa? disable port "IO_COM4" tty irq 9 # Parallel port device ppc0 at isa? port? flags 0x40 net irq 7 controller ppbus0 device lpt0 at ppbus? device plip0 at ppbus? device ppi0 at ppbus? #controller vpo0 at ppbus? # # The following Ethernet NICs are all PCI devices. # device ax0 # ASIX AX88140A device de0 # DEC/Intel DC21x4x (``Tulip'') device fxp0 # Intel EtherExpress PRO/100B (82557, 82558) device mx0 # Macronix 98713/98715/98725 (``PMAC'') device pn0 # Lite-On 82c168/82c169 (``PNIC'') device rl0 # RealTek 8129/8139 device tl0 # Texas Instruments ThunderLAN device tx0 # SMC 9432TX (83c170 ``EPIC'') device vr0 # VIA Rhine, Rhine II device vx0 # 3Com 3c590, 3c595 (``Vortex'') device wb0 # Winbond W89C840F device xl0 # 3Com 3c90x (``Boomerang'', ``Cyclone'') # 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 ed0 at isa? port 0x280 net irq 10 iomem 0xd8000 device ie0 at isa? port 0x300 net irq 10 iomem 0xd0000 device ep0 at isa? port 0x300 net irq 10 device ex0 at isa? port? net irq? device fe0 at isa? port 0x300 net irq ? device le0 at isa? port 0x300 net irq 5 iomem 0xd0000 device lnc0 at isa? port 0x280 net irq 10 drq 0 device ze0 at isa? port 0x300 net irq 10 iomem 0xd8000 device zp0 at isa? port 0x300 net irq 10 iomem 0xd8000 device cs0 at isa? port 0x300 net irq ? pseudo-device loop pseudo-device ether pseudo-device sl 1 pseudo-device ppp 1 pseudo-device tun 1 pseudo-device pty 16 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 # This provides support for System V shared memory and message queues. # options SYSVSHM options SYSVMSG options SYSVSEM # The `bpfilter' pseudo-device enables the Berkeley Packet Filter. Be # aware of the legal and administrative consequences of enabling this # option. The number of devices determines the maximum number of # simultaneous BPF clients programs runnable. #pseudo-device bpfilter 4 #Berkeley packet filter camcontrol devlist -v [on startup] scbus-1 on xpt0 bus 0: < > at scbus-1 target -1 lun -1 (xpt0) scbus0 on aha0 bus 0: < > at scbus0 target -1 lun -1 () camcontrol devlist -v [after issuing camcontrol rescan scbus0] scbus-1 on xpt0 bus 0: < > at scbus-1 target -1 lun -1 (xpt0) scbus0 on aha0 bus 0: at scbus0 target 0 lun 0 (probe0) < > at scbus0 target -1 lun -1 () -----Original Message----- From: Crist J. Clark To: Walt Roberts Cc: freebsd-questions@FreeBSD.ORG Date: Sunday, February 20, 2000 16:29 PM Subject: Re: Adaptec 1542c and Exabyte 8200/tar: Device not config >On Sun, Feb 20, 2000 at 11:43:25AM -0500, Walt Roberts wrote: >> I've run out of patience and your help would be greatly, graciously >> appreciated! >> >> Problem: Swapped ADAPTEC 1502 out to use ADAPTEC 1542C after installing >> 3.3.x and can't get tar (or mount or mt) to access the EXABYTE 8200 >> (scsi device 4) to read the device. >> >> History: Since no device drivers appeared to be available for the 1502 >> and I have tarred stuff on 8 mm (DEC ULTRIX tarred files), I tried to >> install the AHA-1542C board and an EXABYE-8200 (taken from the VAX) to >> read the files. >> >> The AHA installed and appeared to be properly identified by FreeBSD at >> all the right spots. During boot it tickled the exabyte numerous times >> (slowly), and came up fine. >> >> Camcontrol dev will show the aha1542 device on scbus0 but no devices. >> Camcontrol periph will show the aha1542 likewise. >> Camcontrol scan will then show the exabyte-8200 and hangs at this >> point. Kill -9 won't make this process go away. Only reboot does. >> >> Tar commands tried: >> tar -tf /dev/rsa0-6 >> (likewise mount and mt) > >Could you post the dmesg(8) output? >-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Thu Feb 24 17: 1:54 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id D8BB837BCDE for ; Thu, 24 Feb 2000 17:01:50 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id LAA19434; Fri, 25 Feb 2000 11:31:57 +1030 (CST) Date: Fri, 25 Feb 2000 11:31:57 +1030 From: Greg Lehey To: up@3.am Cc: Tristan Aston , freebsd-scsi@FreeBSD.ORG Subject: Re: RAID options Message-ID: <20000225113157.A19404@freebie.lemis.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thursday, 24 February 2000 at 10:21:11 -0500, up@3.am wrote: > On Thu, 24 Feb 2000, Tristan Aston wrote: > >> ..I remember reading somewhere that you >> cant boot from a RAID device. >> >> Can anyone confirm this ? > > It depends on the RAID card...you can't boot from vinum volumes, > IIRC... Vinum root is now running, and may even be in 4.0. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 25 0:27:47 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from majestix.cmr.no (majestix.cmr.no [129.177.31.53]) by hub.freebsd.org (Postfix) with ESMTP id 8F68A37BD56 for ; Fri, 25 Feb 2000 00:27:43 -0800 (PST) (envelope-from tl@cmr.no) Received: from shark.cmr.no (shark.cmr.no [129.177.31.34]) by majestix.cmr.no (8.9.3/8.9.3) with ESMTP id JAA29316; Fri, 25 Feb 2000 09:27:07 +0100 (CET) Date: Fri, 25 Feb 2000 09:27:07 +0100 (CET) From: Tom Lislegaard To: "Walter A. Roberts" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Fw: Adaptec 1542c and Exabyte 8200/tar: Device not config In-Reply-To: <004301bf7f15$5a0e7180$986f4acf@walt> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Just an idea but, could this be a cabling/termination problem? I recently needed to read some files from an old 8200 and had problems similar to you (timeouts/hangs). The problem disappeared when I opened the exabyte and ripped out the internal termination. Mind you, this was a slightly different config - 3.3-Stable, adaptec 2940, the exabyte + a DDS4 drive with external termination. -tom To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 25 6:10:48 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ns.proteusweb.com (ns.proteusweb.com [213.38.19.130]) by hub.freebsd.org (Postfix) with ESMTP id 1D73F37BD2E for ; Fri, 25 Feb 2000 06:10:40 -0800 (PST) (envelope-from tris@proteusweb.com) Received: from rhino.proteusweb.com (tris@rhino.proteusweb.com [192.168.0.99]) by ns.proteusweb.com (8.8.5/8.8.5) with ESMTP id OAA01250 for ; Fri, 25 Feb 2000 14:16:57 GMT Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Fri, 25 Feb 2000 14:12:37 -0000 (GMT) From: Tristan Aston To: freebsd-scsi@freebsd.org Subject: booting from RAID devices Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org ...I have a system running FreeBSD 4, and I would like to be able to boot from an AMI megaraid device ...anyone know if this can be done ? tris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 25 7:13:42 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from ns.proteusweb.com (ns.proteusweb.com [213.38.19.130]) by hub.freebsd.org (Postfix) with ESMTP id C76C037B7C4 for ; Fri, 25 Feb 2000 07:13:39 -0800 (PST) (envelope-from tris@proteusweb.com) Received: from rhino.proteusweb.com (tris@rhino.proteusweb.com [192.168.0.99]) by ns.proteusweb.com (8.8.5/8.8.5) with ESMTP id PAA04409 for ; Fri, 25 Feb 2000 15:19:56 GMT Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Fri, 25 Feb 2000 15:15:35 -0000 (GMT) From: Tristan Aston To: freebsd-scsi@freebsd.org Subject: RE: booting from RAID devices Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 25-Feb-00 Tristan Aston wrote: > > ...I have a system running FreeBSD 4, > and I would like to be able to boot from > an AMI megaraid device ...anyone know > if this can be done ? ...it seems it can :P tris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 25 10:14:18 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from mass.cdrom.com (castles536.castles.com [208.214.165.100]) by hub.freebsd.org (Postfix) with ESMTP id EF7CB37BBBE for ; Fri, 25 Feb 2000 10:14:12 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Received: from mass.cdrom.com (localhost [127.0.0.1]) by mass.cdrom.com (8.9.3/8.9.3) with ESMTP id KAA02650; Fri, 25 Feb 2000 10:13:13 -0800 (PST) (envelope-from msmith@mass.cdrom.com) Message-Id: <200002251813.KAA02650@mass.cdrom.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Tristan Aston Cc: freebsd-scsi@freebsd.org Subject: Re: booting from RAID devices In-reply-to: Your message of "Fri, 25 Feb 2000 14:12:37 GMT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 25 Feb 2000 10:13:13 -0800 From: Mike Smith Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > > ...I have a system running FreeBSD 4, > and I would like to be able to boot from > an AMI megaraid device ...anyone know > if this can be done ? It works on some systems, but there are issues with others; I haven't been able to characterise the problem well enough to be confident in saying any more than "it might work for you". -- \\ Give a man a fish, and you feed him for a day. \\ Mike Smith \\ Tell him he should learn how to fish himself, \\ msmith@freebsd.org \\ and he'll hate you for a lifetime. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Fri Feb 25 11:56: 5 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from panzer.kdm.org (panzer.kdm.org [216.160.178.169]) by hub.freebsd.org (Postfix) with ESMTP id 2F43F37BAFC for ; Fri, 25 Feb 2000 11:55:59 -0800 (PST) (envelope-from ken@panzer.kdm.org) Received: (from ken@localhost) by panzer.kdm.org (8.9.3/8.9.1) id MAA48924; Fri, 25 Feb 2000 12:55:43 -0700 (MST) (envelope-from ken) Date: Fri, 25 Feb 2000 12:55:43 -0700 From: "Kenneth D. Merry" To: "Walter A. Roberts" Cc: freebsd-scsi@FreeBSD.ORG Subject: Re: Fw: Adaptec 1542c and Exabyte 8200/tar: Device not config Message-ID: <20000225125543.A48858@panzer.kdm.org> References: <004301bf7f15$5a0e7180$986f4acf@walt> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <004301bf7f15$5a0e7180$986f4acf@walt>; from wroberts@med.wayne.edu on Thu, Feb 24, 2000 at 05:20:19PM -0500 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Thu, Feb 24, 2000 at 17:20:19 -0500, Walter A. Roberts wrote: > Dear folks: > > I was referred to this list for possible help on the problems with a recent > installation of 3.2 BSD related to a need for SCSI. I swapped out my > adaptec 1502 cheapie for a 1542c since the CAM drivers don't support the > 1502 and I had the 1542c on the shelf, thinking this would be easy. Sigh. > > I would be willing to write a driver for the 1502, but I've never written > UNIX drivers, just VMS drivers so I'm not sure how steep the learning curve > would be, but if any of you'd be willing to coach a little I could give it a > whack. FreeBSD 3.4 and FreeBSD-current have a driver for the AIC-6260 and 6360 chips that are on the 1502, so you don't need to write a driver. :) > I mainly (actually only) need the scsi on the UNIX side to read a tar file > off an EXABYTE EXB-8200 scsi drive. If there's no hope for the present > situation, if anyone knew of a way to get the stuff on the MS side onto > other media (via the 1502/EXB), without a lot of contortions that would work > too, although I know this part is way off the track of this list. > > Thanks for any help you can be. Technical details follow. It should be possible to use an Exabyte 8200. They're known to be rather cantankerous, though. > >> Problem: Swapped ADAPTEC 1502 out to use ADAPTEC 1542C after installing > >> 3.3.x and can't get tar (or mount or mt) to access the EXABYTE 8200 > >> (scsi device 4) to read the device. > >> > >> History: Since no device drivers appeared to be available for the 1502 > >> and I have tarred stuff on 8 mm (DEC ULTRIX tarred files), I tried to > >> install the AHA-1542C board and an EXABYE-8200 (taken from the VAX) to > >> read the files. > >> > >> The AHA installed and appeared to be properly identified by FreeBSD at > >> all the right spots. During boot it tickled the exabyte numerous times > >> (slowly), and came up fine. > >> > >> Camcontrol dev will show the aha1542 device on scbus0 but no devices. > >> Camcontrol periph will show the aha1542 likewise. > >> Camcontrol scan will then show the exabyte-8200 and hangs at this > >> point. Kill -9 won't make this process go away. Only reboot does. Does camcontrol rescan hang the whole system, or is it just that process that is hung, or what? > >> Tar commands tried: > >> tar -tf /dev/rsa0-6 > >> (likewise mount and mt) > > > >Could you post the dmesg(8) output? > >-- > >Crist J. Clark cjclark@home.com [ ... ] > aha0 at 0x330-0x333 irq 9 drq 5 on isa > aha0: AHA-1542C FW Rev. 0.1 (ID=44) SCSI Host Adapter, SCSI ID 7, 16 CCBs > vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa > npx0 on motherboard > npx0: INT 16 interface > Waiting 5 seconds for SCSI devices to settle > (probe0:aha0:0:0:0): CCB 0xc3cd5508 - timed out > (probe0:aha0:0:0:0): CCB 0xc3cd5508 - timed out > aha0: No longer in timeout > (probe6:aha0:0:6:0): CCB 0xc3cd5508 - timed out > (probe6:aha0:0:6:0): CCB 0xc3cd5508 - timed out [ ... ] > options SCSI_DELAY=5000 #Be less pessimistic Joe SCSI device I would suggest increasing this to at least 30 seconds. Exabyte 8200's take a long time to recover from a reset. If 30 seconds doesn't work, try 60 seconds. The delay above is in milliseconds, so it'll need to be 30000 or 60000, respectively. > camcontrol devlist -v [on startup] > > scbus-1 on xpt0 bus 0: > < > at scbus-1 target -1 lun -1 (xpt0) > scbus0 on aha0 bus 0: > < > at scbus0 target -1 lun -1 () > > camcontrol devlist -v [after issuing camcontrol rescan scbus0] > > scbus-1 on xpt0 bus 0: > < > at scbus-1 target -1 lun -1 (xpt0) > scbus0 on aha0 bus 0: > at scbus0 target 0 lun 0 (probe0) > < > at scbus0 target -1 lun -1 () That definitely looks like a bug. Essentially the probe peripheral isn't going away for some reason, and the device isn't getting announced to any of the other peripherals. Ken -- Kenneth Merry ken@kdm.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message From owner-freebsd-scsi Sat Feb 26 16:20:42 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by hub.freebsd.org (Postfix) with ESMTP id BB12337BF57 for ; Sat, 26 Feb 2000 16:20:35 -0800 (PST) (envelope-from grog@freebie.lemis.com) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id KAA40207; Sun, 27 Feb 2000 10:50:48 +1030 (CST) Date: Sun, 27 Feb 2000 10:50:48 +1030 From: Greg Lehey To: "Kenneth D. Merry" Cc: "Walter A. Roberts" , freebsd-scsi@FreeBSD.ORG Subject: Re: Fw: Adaptec 1542c and Exabyte 8200/tar: Device not config Message-ID: <20000227105047.C39462@freebie.lemis.com> References: <004301bf7f15$5a0e7180$986f4acf@walt> <20000225125543.A48858@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0pre2i In-Reply-To: <20000225125543.A48858@panzer.kdm.org> WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Friday, 25 February 2000 at 12:55:43 -0700, Kenneth D. Merry wrote: > On Thu, Feb 24, 2000 at 17:20:19 -0500, Walter A. Roberts wrote: >> Dear folks: >> >> I was referred to this list for possible help on the problems with a recent >> installation of 3.2 BSD related to a need for SCSI. I swapped out my >> adaptec 1502 cheapie for a 1542c since the CAM drivers don't support the >> 1502 and I had the 1542c on the shelf, thinking this would be easy. Sigh. >> >> I would be willing to write a driver for the 1502, but I've never written >> UNIX drivers, just VMS drivers so I'm not sure how steep the learning curve >> would be, but if any of you'd be willing to coach a little I could give it a >> whack. > > FreeBSD 3.4 and FreeBSD-current have a driver for the AIC-6260 and 6360 > chips that are on the 1502, so you don't need to write a driver. :) > >> I mainly (actually only) need the scsi on the UNIX side to read a tar file >> off an EXABYTE EXB-8200 scsi drive. If there's no hope for the present >> situation, if anyone knew of a way to get the stuff on the MS side onto >> other media (via the 1502/EXB), without a lot of contortions that would work >> too, although I know this part is way off the track of this list. >> >> Thanks for any help you can be. Technical details follow. > > It should be possible to use an Exabyte 8200. They're known to be rather > cantankerous, though. I have a couple of 8200s which don't work on current versions of FreeBSD. They have a marginally different command set which doesn't understand certain basic SCSI commands; they probe like this: sa1 at sym0 bus 0 target 5 lun 0 sa1: Removable Sequential Access SCSI-CCS device sa1: 3.300MB/s transfers The microcode revision (254A) is the key here. They don't understand mode sense correctly, so just about any attempt to access them gives the messages: Feb 27 10:46:48 panic /kernel: (sa1:sym0:0:5:0): MODE SENSE(06). CDB: 1a 0 0 0 c 0 Feb 27 10:46:48 panic /kernel: (sa1:sym0:0:5:0): ILLEGAL REQUEST info?:1fff Don't worry about the "panic": that's the name of my test machine :-) >>>> Problem: Swapped ADAPTEC 1502 out to use ADAPTEC 1542C after installing >>>> 3.3.x and can't get tar (or mount or mt) to access the EXABYTE 8200 >>>> (scsi device 4) to read the device. >>>> >>>> History: Since no device drivers appeared to be available for the 1502 >>>> and I have tarred stuff on 8 mm (DEC ULTRIX tarred files), I tried to >>>> install the AHA-1542C board and an EXABYE-8200 (taken from the VAX) to >>>> read the files. >>>> >>>> The AHA installed and appeared to be properly identified by FreeBSD at >>>> all the right spots. During boot it tickled the exabyte numerous times >>>> (slowly), and came up fine. That's the Exabyte that's being slow. They take forever to load and get started. >>>> Camcontrol dev will show the aha1542 device on scbus0 but no devices. >>>> Camcontrol periph will show the aha1542 likewise. >>>> Camcontrol scan will then show the exabyte-8200 and hangs at this >>>> point. Kill -9 won't make this process go away. Only reboot does. > > Does camcontrol rescan hang the whole system, or is it just that process > that is hung, or what? I haven't seen this on any combination I've tried. >> scbus0 on aha0 bus 0: >> at scbus0 target 0 lun 0 (probe0) >> < > at scbus0 target -1 lun -1 () It's possible that this microcode version will be OK. Greg -- Finger grog@lemis.com for PGP public key See complete headers for address and phone numbers To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message