From owner-freebsd-hardware Sun Apr 20 22:48:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id WAA17386 for hardware-outgoing; Sun, 20 Apr 1997 22:48:57 -0700 (PDT) Received: from gateway.minvenw.nl (ns.minvenw.nl [195.108.63.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id WAA17377 for ; Sun, 20 Apr 1997 22:48:50 -0700 (PDT) From: bultman@rikz.rws.minvenw.nl Message-Id: <199704210548.WAA17377@freefall.freebsd.org> Received: from mailhost.minvenw.nl by gateway.minvenw.nl with SMTP (1.38.193.5/16.2) id AA14276; Mon, 21 Apr 1997 07:54:46 +0200 Received: from [131.237.8.12] by edsvas01.icim.nl with SMTP (1.38.193.5/16.2) id AA02976; Mon, 21 Apr 1997 07:37:29 +0200 Received: from gwdcal.dgw.rws.nl by gwdcac.dgw.rws.nl with SMTP (1.37.109.4/16.2) id AA02340; Mon, 21 Apr 97 07:37:28 +0200 Received: by gwdcal.dgw.rws.nl (1.38.193.5/16.2) id AA01419; Mon, 21 Apr 1997 07:37:26 +0200 Subject: HD light stays on To: freebsd-hardware@freebsd.org Date: Mon, 21 Apr 1997 07:37:25 +0100 (METDST) X-Mailer: ELM [version 2.4 PL21] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've just upgraded my HP Vectra Pentium/133 system to FreeBSD 2.2.1 and everything works fine. But the Hard disk light stays on all the time? Does that matter and if so, how do I prevent it? Thanks for any and all help. (Please mail me direct, as I do not subscribe to this list) -- o Gert Bultman o / | \ SNAILMAIL: National Institute for Coastal & Marine Manage- / | \ o--o--o ment, P.O.Box 20907, 2500 EX The Hague, The Netherlands o--o--o \ | / ( ----- Please mark your envelope "PERSOONLIJK" ----- ) \ | / o [Old Address: bultman@dgw.rws.nl] Phone (..31) 70 3114297 o From owner-freebsd-hardware Mon Apr 21 18:57:13 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id SAA05191 for hardware-outgoing; Mon, 21 Apr 1997 18:57:13 -0700 (PDT) Received: from nexgen.hiwaay.net (max21-154.HiWAAY.net [208.147.153.154]) by freefall.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA05186 for ; Mon, 21 Apr 1997 18:57:10 -0700 (PDT) Received: from nexgen (localhost [127.0.0.1]) by nexgen.hiwaay.net (8.8.5/8.8.4) with ESMTP id UAA14739; Mon, 21 Apr 1997 20:56:58 -0500 (CDT) Message-Id: <199704220156.UAA14739@nexgen.hiwaay.net> X-Mailer: exmh version 1.6.9 8/22/96 To: bultman@rikz.rws.minvenw.nl cc: freebsd-hardware@freebsd.org From: dkelly@hiwaay.net Subject: Re: HD light stays on In-reply-to: Message from bultman@rikz.rws.minvenw.nl of "Mon, 21 Apr 1997 07:37:25 BST." <199704210548.WAA17377@freefall.freebsd.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 21 Apr 1997 20:56:56 -0500 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I've just upgraded my HP Vectra Pentium/133 system to FreeBSD 2.2.1 > and everything works fine. But the Hard disk light stays on all the > time? Does that matter and if so, how do I prevent it? My *IDE* HD led stays on all the time. Ever since the IDE drive was removed. Still have an ATAPI CDROM on the IDE cable. -- 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-hardware Tue Apr 22 00:17:19 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.5/8.8.5) id AAA20107 for hardware-outgoing; Tue, 22 Apr 1997 00:17:19 -0700 (PDT) Received: from milehigh.denver.net (jdc@milehigh.denver.net [204.144.180.2]) by freefall.freebsd.org (8.8.5/8.8.5) with SMTP id AAA20088; Tue, 22 Apr 1997 00:17:15 -0700 (PDT) Received: (from jdc@localhost) by milehigh.denver.net (8.6.12/8.6.12) id BAA06416; Tue, 22 Apr 1997 01:18:18 -0600 Date: Tue, 22 Apr 1997 01:18:18 -0600 (MDT) From: John-David Childs To: hardware@freebsd.org cc: questions@freebsd.org Subject: Yet another Adaptec 2940UW problem :( Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I recently purchased a Pentium-Pro 200 (I found back in September that Jordan made mention of "PPRO 200Mhz and new Intel 82440fx problems"...which is to a T the system I have), 64MB parity RAM, Adaptec 2940UW SCSI controller, 2 IBM Ultrastar 4.3GB Ultrawide SCSI drives, a Jaz drive, IDE CD-ROM (why for god's sake I did that instead of a SCSI CD-ROM I can't figure out ;( etc. for use as a server...and spent all day trying to get the darn thing working with 2.1.7 FreeBSD! If only I'd read the archives *before* spending $5000 on a server :( The biggest problem I had seems to be a common one with the Adaptec 2940... reference kern/3312 and kern/1296 for adaptec 2940 "timeout while {devicein, deviceout, idle}". Searching through the mailing-list archives, I found recommendations to 1) disable sync, 2) disable disconnect, 3) slow the MB/sec transfer rate, 4) disable wide negotiation, 5)turn of "ultra" negotiation, and of course 6)check cabling,termination. I also formatted/verified the drives via the Adaptec BIOS SCSI-Select Utility. I also tried adjusting the Jaz drive's MB/sec, and disabling ultra/wide transfers as appropriate for that device while leaving the other settings for the IBM UW drives alone....no luck. I've done all of the above. The server isn't even in "real" use yet and panicked five times today during relatively light transfers. Any suggestions on a replacement SCSI controller which works better?? Hellp!!! I hate looking like a fool and having my employers whine about "they should have gone with..." -- John-David Childs (JC612) http://www.denver.net System Administrator jdc@denver.net & Network Engineer Think, Listen, Look, then ACT! "A verbal contract isn't worth the paper it's written on" - Louis B Mayer From owner-freebsd-hardware Tue Apr 22 01:21:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA01700 for hardware-outgoing; Tue, 22 Apr 1997 01:21:03 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA01680; Tue, 22 Apr 1997 01:20:55 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id RAA14482; Tue, 22 Apr 1997 17:50:46 +0930 (CST) From: Michael Smith Message-Id: <199704220820.RAA14482@genesis.atrad.adelaide.edu.au> Subject: Re: Yet another Adaptec 2940UW problem :( In-Reply-To: from John-David Childs at "Apr 22, 97 01:18:18 am" To: jdc@denver.net (John-David Childs) Date: Tue, 22 Apr 1997 17:50:46 +0930 (CST) Cc: hardware@freebsd.org, questions@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk John-David Childs stands accused of saying: > > I've done all of the above. The server isn't even in "real" use yet and > panicked five times today during relatively light transfers. > Any suggestions on a replacement SCSI controller which works better?? > Hellp!!! I hate looking like a fool and having my employers whine about > "they should have gone with..." How about just updating your kernel sources to the current 2.1-STABLE point? > John-David Childs (JC612) http://www.denver.net -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Tue Apr 22 02:15:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA03556 for hardware-outgoing; Tue, 22 Apr 1997 02:15:12 -0700 (PDT) Received: from hawk.gnome.co.uk (gnome.gw.cerbernet.co.uk [193.243.224.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA03535; Tue, 22 Apr 1997 02:15:06 -0700 (PDT) Received: from hawk.gnome.co.uk (localhost [127.0.0.1]) by hawk.gnome.co.uk (8.8.5/8.8.5) with ESMTP id KAA02067; Tue, 22 Apr 1997 10:14:56 +0100 (BST) Message-Id: <199704220914.KAA02067@hawk.gnome.co.uk> X-Mailer: exmh version 2.0gamma 1/27/96 To: John-David Childs cc: hardware@freebsd.org, questions@freebsd.org Subject: Re: Yet another Adaptec 2940UW problem :( In-reply-to: Your message of "Tue, 22 Apr 1997 01:18:18 MDT." Mime-Version: 1.0 Content-Type: text/plain Date: Tue, 22 Apr 1997 10:14:56 +0100 From: Chris Stenton Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I am using the NCR875 controller with the Utrastar 4.5GB drive on a PPro 200 and that is working fine. The device driver as yet does not support SCSI III but the throughput seems fine to me. I also stuck my external DAT and CDROM on a separate NCR810 controller so as to keep the cables nice and short for the Disk drive. Chris From owner-freebsd-hardware Tue Apr 22 05:30:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA12219 for hardware-outgoing; Tue, 22 Apr 1997 05:30:29 -0700 (PDT) Received: from buffnet4.buffnet.net (buffnet4.buffnet.net [205.246.19.13]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA12196; Tue, 22 Apr 1997 05:30:02 -0700 (PDT) Received: from buffnet11.buffnet.net (shovey@buffnet11.buffnet.net [205.246.19.55]) by buffnet4.buffnet.net (8.7.5/8.7.3) with SMTP id IAA01601; Tue, 22 Apr 1997 08:30:09 -0400 (EDT) Date: Tue, 22 Apr 1997 08:30:09 -0400 (EDT) From: Steve To: John-David Childs cc: hardware@freebsd.org, questions@freebsd.org Subject: Re: Yet another Adaptec 2940UW problem :( In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have a pentium 133 (or is it a 166) I forget, with that scsi controller and I have no problems under 2.1.5. I did have problems with lockups and panics when I first put it together - the mother board is a triton HX, and there was a cmos jobber I had to turn off - I cant remember exactly what it as called. Something to the effect of Enable HX special features - or something close - the 'special features' apparently are what was doing me. I have 2 2940UW controllers, each running 2 4 wide giggers on a high volume news server - they do not run any non wide units, or non disks. On Tue, 22 Apr 1997, John-David Childs wrote: > I recently purchased a Pentium-Pro 200 (I found back in September that > Jordan made mention of "PPRO 200Mhz and new Intel 82440fx > problems"...which is to a T the system I have), 64MB parity RAM, Adaptec > 2940UW SCSI controller, 2 IBM Ultrastar 4.3GB Ultrawide SCSI drives, a Jaz > drive, IDE CD-ROM (why for god's sake I did that instead of a SCSI CD-ROM > I can't figure out ;( etc. for use as a server...and spent all day trying > to get the darn thing working with 2.1.7 FreeBSD! If only I'd read the > archives *before* spending $5000 on a server :( > > The biggest problem I had seems to be a common one with the Adaptec 2940... > reference kern/3312 and kern/1296 for adaptec 2940 "timeout while > {devicein, deviceout, idle}". Searching through the mailing-list > archives, I found recommendations to 1) disable sync, 2) disable disconnect, > 3) slow the MB/sec transfer rate, 4) disable wide negotiation, 5)turn of > "ultra" negotiation, and of course 6)check cabling,termination. I also > formatted/verified the drives via the Adaptec BIOS SCSI-Select Utility. > > I also tried adjusting the Jaz drive's MB/sec, and disabling ultra/wide > transfers as appropriate for that device while leaving the other settings > for the IBM UW drives alone....no luck. > > I've done all of the above. The server isn't even in "real" use yet and > panicked five times today during relatively light transfers. > Any suggestions on a replacement SCSI controller which works better?? > Hellp!!! I hate looking like a fool and having my employers whine about > "they should have gone with..." > -- > > John-David Childs (JC612) http://www.denver.net > System Administrator jdc@denver.net > & Network Engineer Think, Listen, Look, then ACT! > "A verbal contract isn't worth the paper it's written on" - Louis B Mayer > > > From owner-freebsd-hardware Tue Apr 22 08:36:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA20513 for hardware-outgoing; Tue, 22 Apr 1997 08:36:22 -0700 (PDT) Received: from theta.pair.com (theta.pair.com [207.86.128.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA20506 for ; Tue, 22 Apr 1997 08:36:19 -0700 (PDT) Received: from adam.netsonic.com (gb_noc30.sparknet.net [207.250.20.30]) by theta.pair.com (8.8.5/8.6.12) with SMTP id LAA11351 for ; Tue, 22 Apr 1997 11:32:27 -0400 (EDT) X-Envelope-To: Message-Id: <3.0.32.19970422104116.00696c14@mail.netsonic.com> X-Sender: adam@mail.netsonic.com X-Mailer: Windows Eudora Pro Version 3.0 (32) Date: Tue, 22 Apr 1997 10:41:18 -0500 To: freebsd-hardware@freebsd.org From: "Adam L. Simpson" Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk subscribe adam@netsonic.com From owner-freebsd-hardware Tue Apr 22 09:33:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA23252 for hardware-outgoing; Tue, 22 Apr 1997 09:33:53 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA23232; Tue, 22 Apr 1997 09:33:48 -0700 (PDT) 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 KAA04863; Tue, 22 Apr 1997 10:33:46 -0600 (MDT) Message-Id: <199704221633.KAA04863@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: John-David Childs cc: hardware@FreeBSD.ORG, questions@FreeBSD.ORG Subject: Re: Yet another Adaptec 2940UW problem :( In-reply-to: Your message of "Tue, 22 Apr 1997 01:18:18 MDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Apr 1997 10:32:15 -0600 From: "Justin T. Gibbs" Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >I recently purchased a Pentium-Pro 200 (I found back in September that >Jordan made mention of "PPRO 200Mhz and new Intel 82440fx >problems"...which is to a T the system I have), 64MB parity RAM, Adaptec >2940UW SCSI controller, 2 IBM Ultrastar 4.3GB Ultrawide SCSI drives, a Jaz >drive, IDE CD-ROM (why for god's sake I did that instead of a SCSI CD-ROM >I can't figure out ;( etc. for use as a server...and spent all day trying >to get the darn thing working with 2.1.7 FreeBSD! If only I'd read the >archives *before* spending $5000 on a server :( You should try installing from releng22.FreeBSD.org as that has the latest version of the aic7xxx driver which should fix most of your problems. This latest snap is very similar to what is running on wcarchive and should be fairly stable for you needs. If you really want to run a 2.1+ system, you can always CVSup the src tree once you have something where you can perform the build as these changes were committed to the 2.1.0 branch as well. >John-David Childs (JC612) http://www.denver.net Looks like you are in my back yard. >System Administrator jdc@denver.net > & Network Engineer Think, Listen, Look, then ACT! >"A verbal contract isn't worth the paper it's written on" - Louis B Mayer -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hardware Tue Apr 22 10:31:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA27086 for hardware-outgoing; Tue, 22 Apr 1997 10:31:34 -0700 (PDT) Received: from lariat.lariat.org ([129.72.251.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA27033; Tue, 22 Apr 1997 10:31:25 -0700 (PDT) Received: from solo.lariat.org ([129.72.251.10]) by lariat.lariat.org (8.8.5/8.8.5) with SMTP id LAA17588; Tue, 22 Apr 1997 11:30:45 -0600 (MDT) Message-Id: <3.0.1.32.19970422113008.006fe914@lariat.org> X-Sender: brett@lariat.org X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Tue, 22 Apr 1997 11:30:08 -0600 To: gibbs@plutotech.com, jdc@denver.net From: Brett Glass Subject: Re: Yet another Adaptec 2940UW problem :( Cc: hardware@freebsd.org, questions@freebsd.org In-Reply-To: <88256481.005E93A1.00@IWND1.infoworld.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 10:32 AM 4/22/97 -0500, gibbs@plutotech.com wrote: >You should try installing from releng22.FreeBSD.org as that has the latest >version of the aic7xxx driver which should fix most of your problems. Is this the version of the Adaptec driver included in 2.2.1-R? Or is there yet a newer version of the SCSI code with still more fixes? I've got one machine without any SCSI drives running 2.2.1-R, but I'm waiting to hear that Adaptec SCSI support is rock solid before using 2.2.X on a machine with SCSI drives. So far, I've seen complaints of problems with SCSI CD-ROMs, so I've held back. Is there a 2.2-STABLE branch yet? When is the next 2.2.X release likely to occur? Finally (I know I'm full of questions this morning), why are there so many problems with the Adaptec 29XX series of adapters and motherboard chips on all platforms (not just FreeBSD)? With all the bug reports involving this chip on Linux, FreeBSD, NT, Windows, etc. I'm getting wary of purchasing them, despite their popularity. --Brett Glass From owner-freebsd-hardware Tue Apr 22 10:37:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA27590 for hardware-outgoing; Tue, 22 Apr 1997 10:37:01 -0700 (PDT) Received: from pluto.plutotech.com (root@pluto100.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA27570; Tue, 22 Apr 1997 10:36:55 -0700 (PDT) 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 LAA06226; Tue, 22 Apr 1997 11:36:50 -0600 (MDT) Message-Id: <199704221736.LAA06226@pluto.plutotech.com> X-Mailer: exmh version 2.0beta 12/23/96 To: Brett Glass cc: gibbs@plutotech.com, jdc@denver.net, hardware@freebsd.org, questions@freebsd.org Subject: Re: Yet another Adaptec 2940UW problem :( In-reply-to: Your message of "Tue, 22 Apr 1997 11:30:08 MDT." <3.0.1.32.19970422113008.006fe914@lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 22 Apr 1997 11:35:16 -0600 From: "Justin T. Gibbs" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >At 10:32 AM 4/22/97 -0500, gibbs@plutotech.com wrote: > >>You should try installing from releng22.FreeBSD.org as that has the latest >>version of the aic7xxx driver which should fix most of your problems. > >Is this the version of the Adaptec driver included in 2.2.1-R? Or is there >yet a newer version of the SCSI code with still more fixes? This is newer. >I've got one machine without any SCSI drives running 2.2.1-R, but I'm >waiting to hear that Adaptec SCSI support is rock solid before using 2.2.X >on a machine with SCSI drives. So far, I've seen complaints of problems >with SCSI CD-ROMs, so I've held back. > >Is there a 2.2-STABLE branch yet? When is the next 2.2.X release likely to >occur? The 2.2 branch will become (or is?) 2.2-stable and is what is used to build the daily snapshots available on releng22.FreeBSD.org. >Finally (I know I'm full of questions this morning), why are there so many >problems with the Adaptec 29XX series of adapters and motherboard chips on >all platforms (not just FreeBSD)? With all the bug reports involving this >chip on Linux, FreeBSD, NT, Windows, etc. I'm getting wary of purchasing >them, despite their popularity. Take a look at the driver. It's a complicated state engine. The Linux, FreeBSD and NetBSD driver are all based on the same work (mine), so they have similar problems/features. Another thing that contributes to problems with the "free" drivers is that Adaptec doesn't give out engineering contacts to "little guys". >--Brett Glass -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hardware Tue Apr 22 10:50:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA28434 for hardware-outgoing; Tue, 22 Apr 1997 10:50:37 -0700 (PDT) Received: from lariat.lariat.org ([129.72.251.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA28403; Tue, 22 Apr 1997 10:50:15 -0700 (PDT) Received: from solo.lariat.org ([129.72.251.10]) by lariat.lariat.org (8.8.5/8.8.5) with SMTP id LAA17813; Tue, 22 Apr 1997 11:49:47 -0600 (MDT) Message-Id: <3.0.1.32.19970422114918.006ad8d8@lariat.org> X-Sender: brett@lariat.org X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Tue, 22 Apr 1997 11:49:18 -0600 To: "Justin T. Gibbs" From: Brett Glass Subject: Re: Yet another Adaptec 2940UW problem :( Cc: gibbs@plutotech.com, jdc@denver.net, hardware@freebsd.org, questions@freebsd.org In-Reply-To: <199704221736.LAA06226@pluto.plutotech.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 11:35 AM 4/22/97 -0600, Justin T. Gibbs wrote: >Another thing that contributes to problems >with the "free" drivers is that Adaptec doesn't give out engineering >contacts to "little guys". Maybe you should contact their marketing department and note that, between Linux, FreeBSD, and NetBSD, your work goes to a HUGE share of their market and an overwhelming s hare of the Internet world (since so many Web, news, and mail servers run these OSes). With luck, they'll recognize the importance of this code and put you in touch with the engineers. --Brett Glass From owner-freebsd-hardware Tue Apr 22 11:21:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA00558 for hardware-outgoing; Tue, 22 Apr 1997 11:21:42 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA00538; Tue, 22 Apr 1997 11:21:37 -0700 (PDT) Received: from mail.cdsnet.net (mail.cdsnet.net [204.118.244.5]) by mail.cdsnet.net (8.8.5/8.7.3) with SMTP id LAA29805; Tue, 22 Apr 1997 11:21:07 -0700 (PDT) Date: Tue, 22 Apr 1997 11:21:05 -0700 (PDT) From: Jaye Mathisen To: Brett Glass cc: "Justin T. Gibbs" , jdc@denver.net, hardware@freebsd.org, questions@freebsd.org Subject: Re: Yet another Adaptec 2940UW problem :( In-Reply-To: <3.0.1.32.19970422114918.006ad8d8@lariat.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Or contact somebody like PC Week, since they're using Linux and FreeBSD in more of their tests, and encourage them to maybe sneak a note in an editorial about lack of support for what is potentially a huge market base... On Tue, 22 Apr 1997, Brett Glass wrote: > At 11:35 AM 4/22/97 -0600, Justin T. Gibbs wrote: > > >Another thing that contributes to problems > >with the "free" drivers is that Adaptec doesn't give out engineering > >contacts to "little guys". > > Maybe you should contact their marketing department and note that, > between Linux, FreeBSD, and NetBSD, your work goes to a HUGE share > of their market and an overwhelming s hare of the Internet world (since > so many Web, news, and mail servers run these OSes). With luck, they'll > recognize the importance of this code and put you in touch with the > engineers. > > --Brett Glass > From owner-freebsd-hardware Tue Apr 22 12:09:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA04319 for hardware-outgoing; Tue, 22 Apr 1997 12:09:32 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA04242; Tue, 22 Apr 1997 12:09:24 -0700 (PDT) Received: from time.cdrom.com (localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id MAA26128; Tue, 22 Apr 1997 12:08:31 -0700 (PDT) To: Brett Glass cc: gibbs@plutotech.com, jdc@denver.net, hardware@freebsd.org, questions@freebsd.org Subject: Re: Yet another Adaptec 2940UW problem :( In-reply-to: Your message of "Tue, 22 Apr 1997 11:30:08 MDT." <3.0.1.32.19970422113008.006fe914@lariat.org> Date: Tue, 22 Apr 1997 12:08:31 -0700 Message-ID: <26125.861736111@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Is this the version of the Adaptec driver included in 2.2.1-R? Or is there > yet a newer version of the SCSI code with still more fixes? It's a newer version. See also the announcement I *just* posted. > Is there a 2.2-STABLE branch yet? When is the next 2.2.X release likely to > occur? Yes, there is a 2.2-STABLE branch now (it's called RELENG_2_2) and it's from these branches that the releng22.freebsd.org snapshots are being made on a daily basis. Jordan From owner-freebsd-hardware Tue Apr 22 12:32:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA10323 for hardware-outgoing; Tue, 22 Apr 1997 12:32:33 -0700 (PDT) Received: from pegasus.com (pegasus.com [140.174.243.13]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA10237; Tue, 22 Apr 1997 12:32:18 -0700 (PDT) Received: by pegasus.com (8.6.8/PEGASUS-2.2) id JAA05638; Tue, 22 Apr 1997 09:31:23 -1000 Date: Tue, 22 Apr 1997 09:31:23 -1000 From: richard@pegasus.com (Richard Foulk) Message-Id: <199704221931.JAA05638@pegasus.com> In-Reply-To: Jaye Mathisen "Re: Yet another Adaptec 2940UW problem :(" (Apr 22, 11:21am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Jaye Mathisen , Brett Glass Subject: Re: Yet another Adaptec 2940UW problem :( Cc: "Justin T. Gibbs" , jdc@denver.net, hardware@freebsd.org, questions@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk } Or contact somebody like PC Week, since they're using Linux and FreeBSD in } more of their tests, and encourage them to maybe sneak a note in an } editorial about lack of support for what is potentially a huge market } base... } Try to exhaust the quiet approach first. The public ones can tend to make us look bad too. Richard From owner-freebsd-hardware Tue Apr 22 12:54:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA20235 for hardware-outgoing; Tue, 22 Apr 1997 12:54:51 -0700 (PDT) Received: from gw1.asacomputers.com (root@gw1.asacomputers.com [204.69.220.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA20205 for ; Tue, 22 Apr 1997 12:54:49 -0700 (PDT) Received: by gw1.asacomputers.com id JAA29972; Tue, 22 Apr 1997 09:54:09 -0700 (PDT) Message-Id: <2.2.32.19970422195831.008ab994@gw1> X-Sender: rajadnya@gw1 X-Mailer: Windows Eudora Pro Version 2.2 (32) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Tue, 22 Apr 1997 12:58:31 -0700 To: Brett Glass From: Kedar Subject: Re: Yet another Adaptec 2940UW problem :( Cc: hardware@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Finally (I know I'm full of questions this morning), why are there so many >problems with the Adaptec 29XX series of adapters and motherboard chips on >all platforms (not just FreeBSD)? I'm not sure that this has been covered, so please forgive me if it has. Adaptec apparently has 2 models out: Model: AHA-2940AU BIOS Version: 1.21 Max Disk Read Bytes Second: 4MB. Model: AHA-2940 Ultra/Ultra Wide BIOS Version 1.23 Max Disk Read Bytes Second: 8MB. We have had a *lot* of difficulty with the former. If the chip says 2940AU, it would be wise to stay away for the moment. This info is from about a month back. Things might have changed. Regards, Kedar. From owner-freebsd-hardware Tue Apr 22 13:44:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA02905 for hardware-outgoing; Tue, 22 Apr 1997 13:44:51 -0700 (PDT) Received: from sand.sentex.ca (sand.sentex.ca [206.222.77.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA02899 for ; Tue, 22 Apr 1997 13:44:47 -0700 (PDT) Received: from gravel (gravel.sentex.ca [205.211.165.210]) by sand.sentex.ca (8.8.5/8.8.3) with SMTP id QAA00396; Tue, 22 Apr 1997 16:47:51 -0400 (EDT) Message-Id: <3.0.1.32.19970422164742.00af0c80@sentex.net> X-Sender: mdtancsa@sentex.net X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Tue, 22 Apr 1997 16:47:42 -0400 To: Kedar , Brett Glass From: Mike Tancsa Subject: Re: Yet another Adaptec 2940UW problem :( Cc: hardware@freebsd.org In-Reply-To: <2.2.32.19970422195831.008ab994@gw1> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 12:58 PM 4/22/97 -0700, Kedar wrote: >>Finally (I know I'm full of questions this morning), why are there so many >>problems with the Adaptec 29XX series of adapters and motherboard chips on >>all platforms (not just FreeBSD)? > > I'm not sure that this has been covered, so please forgive me if it >has. Adaptec apparently has 2 models out: > Model: AHA-2940AU > BIOS Version: 1.21 > Max Disk Read Bytes Second: 4MB. > > Model: AHA-2940 Ultra/Ultra Wide > BIOS Version 1.23 > Max Disk Read Bytes Second: 8MB. > > We have had a *lot* of difficulty with the former. If the chip says >2940AU, it would be wise to stay away for the moment. This info is from >about a month back. Things might have changed. I found that enabling the "Plug and Play SCAM support" in the card's BIOS (even if your devices dont necessarily support it), helps a lot for that model... ---Mike ********************************************************************** Mike Tancsa (mike@sentex.net) * To do is to be -- Nietzsche Sentex Communications Corp, * To be is to do -- Sartre Cambridge, Ontario * Do be do be do -- Sinatra (http://www.sentex.net/~mdtancsa) * From owner-freebsd-hardware Tue Apr 22 19:05:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA25351 for hardware-outgoing; Tue, 22 Apr 1997 19:05:14 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA25331; Tue, 22 Apr 1997 19:05:04 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id LAA18577; Wed, 23 Apr 1997 11:34:01 +0930 (CST) From: Michael Smith Message-Id: <199704230204.LAA18577@genesis.atrad.adelaide.edu.au> Subject: Re: Yet another Adaptec 2940UW problem :( In-Reply-To: <3.0.1.32.19970422113008.006fe914@lariat.org> from Brett Glass at "Apr 22, 97 11:30:08 am" To: brett@lariat.org (Brett Glass) Date: Wed, 23 Apr 1997 11:34:00 +0930 (CST) Cc: gibbs@plutotech.com, jdc@denver.net, hardware@freebsd.org, questions@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Brett Glass stands accused of saying: > At 10:32 AM 4/22/97 -0500, gibbs@plutotech.com wrote: > > >You should try installing from releng22.FreeBSD.org as that has the latest > >version of the aic7xxx driver which should fix most of your problems. > > Is this the version of the Adaptec driver included in 2.2.1-R? Or is there > yet a newer version of the SCSI code with still more fixes? 2.2.1 went out the door in the middle of a bugfix cycle in the 'ahc' driver. The server at releng22.freebsd.org actually builds 2.2-STABLE snapshots every day, so it is guaranteed to have the most current working code. > Finally (I know I'm full of questions this morning), why are there so many > problems with the Adaptec 29XX series of adapters and motherboard chips on > all platforms (not just FreeBSD)? With all the bug reports involving this > chip on Linux, FreeBSD, NT, Windows, etc. I'm getting wary of purchasing > them, despite their popularity. I was discussing this with some people last night; we know that Justin and the other 2940 driver authors aren't stupid, but similar SCSI drivers (like those for the NCR parts, f.e.) don't go through the same grief. We concluded that the Adaptec parts must be more of a bitch to work with, and/or harder to get accurate data on. Certainly some of their newer parts (eg. the aic7860) appear fairly braindead. > --Brett Glass -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Tue Apr 22 19:43:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA27785 for hardware-outgoing; Tue, 22 Apr 1997 19:43:54 -0700 (PDT) Received: from lariat.lariat.org ([129.72.251.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA27771 for ; Tue, 22 Apr 1997 19:43:41 -0700 (PDT) Received: from solo.lariat.org ([129.72.251.10]) by lariat.lariat.org (8.8.5/8.8.5) with SMTP id UAA22932; Tue, 22 Apr 1997 20:42:51 -0600 (MDT) Message-Id: <3.0.1.32.19970422204203.006d7994@lariat.org> X-Sender: brett@lariat.org X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Tue, 22 Apr 1997 20:42:03 -0600 To: Michael Smith From: Brett Glass Subject: Re: Yet another Adaptec 2940UW problem :( Cc: gibbs@plutotech.com, jdc@denver.net, hardware@freebsd.org In-Reply-To: <199704230204.LAA18577@genesis.atrad.adelaide.edu.au> References: <3.0.1.32.19970422113008.006fe914@lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 11:34 AM 4/23/97 +0930, Michael Smith wrote: >We concluded that the Adaptec parts must be more of a bitch >to work with, and/or harder to get accurate data on. Certainly some of >their newer parts (eg. the aic7860) appear fairly braindead. Isn't the AIC7860 one of the ASICs they "inherited" when they bought Future Domain? This may have something to do with the problem. In the meantime, which is the fastest PCI adapter for which there's really solid code? Oh.... And is there any code in the SCSI drivers for target mode? Just got a call to do a fairly fancy SCSI peripheral, and a stripped-down FreeBSD would be just the thing to run it. --Brett From owner-freebsd-hardware Wed Apr 23 00:42:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA13683 for hardware-outgoing; Wed, 23 Apr 1997 00:42:47 -0700 (PDT) Received: from hydrogen.nike.efn.org (metriclient-12.uoregon.edu [128.223.172.12]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA13678 for ; Wed, 23 Apr 1997 00:42:43 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.4/8.8.4) id AAA29253; Wed, 23 Apr 1997 00:42:33 -0700 (PDT) Message-ID: <19970423004233.64736@hydrogen.nike.efn.org> Date: Wed, 23 Apr 1997 00:42:33 -0700 From: John-Mark Gurney To: Brett Glass Cc: hardware@FreeBSD.org Subject: Re: Yet another Adaptec 2940UW problem :( References: <3.0.1.32.19970422113008.006fe914@lariat.org> <3.0.1.32.19970422204203.006d7994@lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <3.0.1.32.19970422204203.006d7994@lariat.org>; from Brett Glass on Tue, Apr 22, 1997 at 08:42:03PM -0600 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2-960801-SNAP i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk Brett Glass scribbled this message on Apr 22: > Oh.... And is there any code in the SCSI drivers for target mode? Just got > a call to do a fairly fancy SCSI peripheral, and a stripped-down FreeBSD > would be just the thing to run it. you probably want pt0 which stands for processor target... if I remeber correctly the hpscan software uses this so it can do direct data transfers and that sort of thing... enjoy! ttyl.. -- John-Mark Cu Networking Modem/FAX: +1 541 683 6954 Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hardware Wed Apr 23 02:10:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA18355 for hardware-outgoing; Wed, 23 Apr 1997 02:10:36 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [207.198.1.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA18349 for ; Wed, 23 Apr 1997 02:10:32 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id EAA29830; Wed, 23 Apr 1997 04:56:09 -0400 (EDT) From: Peter Dufault Message-Id: <199704230856.EAA29830@hda.hda.com> Subject: Re: Yet another Adaptec 2940UW problem :( In-Reply-To: <19970423004233.64736@hydrogen.nike.efn.org> from John-Mark Gurney at "Apr 23, 97 00:42:33 am" To: gurney_j@resnet.uoregon.edu Date: Wed, 23 Apr 1997 04:56:09 -0400 (EDT) Cc: brett@lariat.org, hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Brett Glass scribbled this message on Apr 22: > > Oh.... And is there any code in the SCSI drivers for target mode? Just got > > a call to do a fairly fancy SCSI peripheral, and a stripped-down FreeBSD > > would be just the thing to run it. > > you probably want pt0 which stands for processor target... if I remeber > correctly the hpscan software uses this so it can do direct data transfers > and that sort of thing... enjoy! The hpscan addresses a peripheral as an initiator using processor read/write. As far as I know it is still only the AHA1542 that supports processor target mode. I suggest adding NCR support. Peter -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-hardware Wed Apr 23 02:45:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA19759 for hardware-outgoing; Wed, 23 Apr 1997 02:45:16 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA19750 for ; Wed, 23 Apr 1997 02:45:10 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.4/8.8.4) id CAA01378; Wed, 23 Apr 1997 02:44:49 -0700 (PDT) Message-ID: <19970423024448.50549@hydrogen.nike.efn.org> Date: Wed, 23 Apr 1997 02:44:48 -0700 From: John-Mark Gurney To: Peter Dufault Cc: brett@lariat.org, hardware@freebsd.org Subject: Re: Yet another Adaptec 2940UW problem :( References: <19970423004233.64736@hydrogen.nike.efn.org> <199704230856.EAA29830@hda.hda.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <199704230856.EAA29830@hda.hda.com>; from Peter Dufault on Wed, Apr 23, 1997 at 04:56:09AM -0400 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2-960801-SNAP i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Peter Dufault scribbled this message on Apr 23: > > Brett Glass scribbled this message on Apr 22: > > > Oh.... And is there any code in the SCSI drivers for target mode? Just got > > > a call to do a fairly fancy SCSI peripheral, and a stripped-down FreeBSD > > > would be just the thing to run it. > > > > you probably want pt0 which stands for processor target... if I remeber > > correctly the hpscan software uses this so it can do direct data transfers > > and that sort of thing... enjoy! > > The hpscan addresses a peripheral as an initiator using processor > read/write. I've always wanted to do IP over SCSI.... but right now there is a problem with FreeBSD scsi card drivers being hard coded to a certain id for the card... of course I don't think I would ever get around writing it either... but a UW "network" would be quite nice... (esspecially for high bandwidth requirements such as nfs :) )... > As far as I know it is still only the AHA1542 that supports processor > target mode. I suggest adding NCR support. actually... now that I think about it... there is always the uk device... you can perform ioctl's against a uk device to send it custom scsi commands... I haven't ever used it before... but it is force compiled into every kernel.. that way if there is a scsi device that the subsystem doesn't understand.. it will have a driver for it... take a look at /usr/include/scsi.h and /usr/include/sys/scsiio.h for more info... the man pages aren't very helpful in this department... hmm... more man page writing for me.. :) -- John-Mark Cu Networking Modem/FAX: +1 541 683 6954 Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hardware Wed Apr 23 03:39:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA22119 for hardware-outgoing; Wed, 23 Apr 1997 03:39:51 -0700 (PDT) Received: from critter.dk.tfs.com ([140.145.230.252]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA22108; Wed, 23 Apr 1997 03:39:26 -0700 (PDT) Received: from critter (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.5/8.8.5) with ESMTP id MAA00709; Wed, 23 Apr 1997 12:37:45 +0200 (CEST) To: John-Mark Gurney cc: Peter Dufault , brett@lariat.org, hardware@FreeBSD.org From: Poul-Henning Kamp Subject: Re: Yet another Adaptec 2940UW problem :( In-reply-to: Your message of "Wed, 23 Apr 1997 02:44:48 PDT." <19970423024448.50549@hydrogen.nike.efn.org> Date: Wed, 23 Apr 1997 12:37:45 +0200 Message-ID: <707.861791865@critter> Sender: owner-hardware@FreeBSD.org X-Loop: FreeBSD.org Precedence: bulk In message <19970423024448.50549@hydrogen.nike.efn.org>, John-Mark Gurney write s: >I've always wanted to do IP over SCSI.... but right now there is a Yes, me too. How about it, nice little project with a RFC on the encoding as a side-effect... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-hardware Wed Apr 23 04:36:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA25105 for hardware-outgoing; Wed, 23 Apr 1997 04:36:18 -0700 (PDT) Received: from gatekeeper.acucobol.ie (gatekeeper.acucobol.ie [194.125.135.194]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA25098 for ; Wed, 23 Apr 1997 04:36:14 -0700 (PDT) Received: (from daemon@localhost) by gatekeeper.acucobol.ie (8.8.5/8.8.5) id MAA25848; Wed, 23 Apr 1997 12:34:06 +0100 (BST) Received: from guinness.acucobol.ie(194.125.135.195) by gatekeeper.acucobol.ie via smap (V2.0beta) id xma025810; Wed, 23 Apr 97 12:33:56 +0100 Received: from guinness (localhost [127.0.0.1]) by guinness.acucobol.ie (8.8.5/8.8.5) with ESMTP id MAA03501; Wed, 23 Apr 1997 12:35:35 +0100 (BST) Message-Id: <199704231135.MAA03501@guinness.acucobol.ie> From: John McLaughlin To: Mike Tancsa Cc: hardware@freebsd.org Subject: Re: Yet another Adaptec 2940UW problem :( In-reply-to: Your message of "Tue, 22 Apr 1997 16:47:42 EDT." <3.0.1.32.19970422164742.00af0c80@sentex.net> Date: Wed, 23 Apr 1997 12:35:34 +0100 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >> We have had a *lot* of difficulty with the former. If the chip >> says 2940AU, it would be wise to stay away for the moment. This >> info is from about a month back. Things might have changed. > I found that enabling the "Plug and Play SCAM support" in the > card's BIOS (even if your devices dont necessarily support it), > helps a lot for that model... I tried that on one for a 2.2.1-RELEASE install (I'd always used 2940's before with much joy), but with no success, so it doesn't appear to be a general workaround. I replaced it with a Tekram 390U, which made both the kernel and me happier. I would say avoid, unless it's been sorted out in the latest snapshot, though it does still appear to be severly crippled in comparison to previous 2940s. John From owner-freebsd-hardware Wed Apr 23 05:30:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA27463 for hardware-outgoing; Wed, 23 Apr 1997 05:30:19 -0700 (PDT) Received: from sand.sentex.ca (sand.sentex.ca [206.222.77.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA27453 for ; Wed, 23 Apr 1997 05:30:15 -0700 (PDT) Received: from gravel (gravel.sentex.ca [205.211.165.210]) by sand.sentex.ca (8.8.5/8.8.3) with SMTP id IAA00302; Wed, 23 Apr 1997 08:34:32 -0400 (EDT) Message-Id: <3.0.1.32.19970423083418.00a95210@sentex.net> X-Sender: mdtancsa@sentex.net X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Wed, 23 Apr 1997 08:34:18 -0400 To: John McLaughlin From: Mike Tancsa Subject: Re: Yet another Adaptec 2940UW problem :( Cc: hardware@FreeBSD.ORG In-Reply-To: <199704231135.MAA03501@guinness.acucobol.ie> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 12:35 PM 4/23/97 +0100, John McLaughlin wrote: > >>> We have had a *lot* of difficulty with the former. If the chip >>> says 2940AU, it would be wise to stay away for the moment. This >>> info is from about a month back. Things might have changed. > > > I found that enabling the "Plug and Play SCAM support" in the > > card's BIOS (even if your devices dont necessarily support it), > > helps a lot for that model... > > I tried that on one for a 2.2.1-RELEASE install (I'd always >used 2940's before with much joy), but with no success, so it doesn't >appear to be a general workaround. I replaced it with a Tekram 390U, >which made both the kernel and me happier. I would say avoid, unless >it's been sorted out in the latest snapshot, though it does still >appear to be severly crippled in comparison to previous 2940s. I should have qualified that with "... helps mostly for the situations where at a soft reboot, the card refuses to see the disk drives"... Yeah, we too are giving up on Adeptec. Currently I am experimenting with a ASUS 875... For about $80 Canadian less than the regular Adaptec (I bought it for $160 CDN), I get an Ultra Wide controller, that so far seems very stable. ---Mike ********************************************************************** Mike Tancsa (mike@sentex.net) * To do is to be -- Nietzsche Sentex Communications Corp, * To be is to do -- Sartre Cambridge, Ontario * Do be do be do -- Sinatra (http://www.sentex.net/~mdtancsa) * From owner-freebsd-hardware Wed Apr 23 08:00:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA04271 for hardware-outgoing; Wed, 23 Apr 1997 08:00:05 -0700 (PDT) Received: from tlk.com (bE4IvV1cNigUChkbb89ksGl0x8IuxLWi@solar.tlk.com [194.97.84.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA04266 for ; Wed, 23 Apr 1997 08:00:02 -0700 (PDT) Received: from ramsey.tb.9715.org(really [194.97.84.65]) by tlk.com via sendmail with esmtp (ident root using rfc1413) id for ; Wed, 23 Apr 1997 16:59:52 +0200 (CEST)) Received: by ramsey.tb.9715.org via sendmail with stdio id for gurney_j@resnet.uoregon.edu; Wed, 23 Apr 1997 16:59:58 +0200 (CEST) Message-Id: From: torstenb@ramsey.tb.9715.org (Torsten Blum) Subject: Re: Yet another Adaptec 2940UW problem :( In-Reply-To: <199704230856.EAA29830@hda.hda.com> from Peter Dufault at "Apr 23, 97 04:56:09 am" To: dufault@hda.com (Peter Dufault) Date: Wed, 23 Apr 1997 16:59:58 +0200 (CEST) Cc: gurney_j@resnet.uoregon.edu, brett@lariat.org, hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL31 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Peter Dufault wrote: > As far as I know it is still only the AHA1542 that supports processor > target mode. I suggest adding NCR support. Hm, I have a box here with an Adaptec 2940 and my HP Scanjet is recognized as an processor type target: ahc0 rev 0 int a irq 12 on pci0:10 ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs ahc0:A:5: refuses synchronous negotiation. Using asynchronous transfers (ahc0:5:0): "HP C2500A 3332" type 3 fixed SCSI 2 pt0(ahc0:5:0): Processor -tb From owner-freebsd-hardware Wed Apr 23 09:04:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA06807 for hardware-outgoing; Wed, 23 Apr 1997 09:04:16 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA06797 for ; Wed, 23 Apr 1997 09:04:13 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id BAA22181; Thu, 24 Apr 1997 01:33:06 +0930 (CST) From: Michael Smith Message-Id: <199704231603.BAA22181@genesis.atrad.adelaide.edu.au> Subject: Re: Yet another Adaptec 2940UW problem :( In-Reply-To: from Torsten Blum at "Apr 23, 97 04:59:58 pm" To: torstenb@ramsey.tb.9715.org (Torsten Blum) Date: Thu, 24 Apr 1997 01:33:05 +0930 (CST) Cc: dufault@hda.com, gurney_j@resnet.uoregon.edu, brett@lariat.org, hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Torsten Blum stands accused of saying: > Peter Dufault wrote: > > > As far as I know it is still only the AHA1542 that supports processor > > target mode. I suggest adding NCR support. > > Hm, I have a box here with an Adaptec 2940 and my HP Scanjet is recognized > as an processor type target: You don't understand what Brett wants. His aim is to have the _BSD_system_ be a target. > -tb > -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Wed Apr 23 09:21:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA07813 for hardware-outgoing; Wed, 23 Apr 1997 09:21:39 -0700 (PDT) Received: from lariat.lariat.org ([129.72.251.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA07798 for ; Wed, 23 Apr 1997 09:21:31 -0700 (PDT) Received: from solo.lariat.org ([129.72.251.10]) by lariat.lariat.org (8.8.5/8.8.5) with SMTP id KAA29752; Wed, 23 Apr 1997 10:19:52 -0600 (MDT) Message-Id: <3.0.1.32.19970423101930.006a67b4@lariat.org> X-Sender: brett@lariat.org X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Wed, 23 Apr 1997 10:19:30 -0600 To: torstenb@ramsey.tb.9715.org, dufault@hda.com From: Brett Glass Subject: Re: Yet another Adaptec 2940UW problem :( Cc: gurney_j@resnet.uoregon.edu, hardware@freebsd.org In-Reply-To: <88256482.005607DF.00@IWND1.infoworld.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This isn't the same thing.... I don't think. This looks as if the FreeBSD system is still the initiator and the scanner is a target (of the catch-all "processor" type). I'd like to make the FreeBSD system act as a target. (And, no, that doesn't mean I'd like to throw it in the air and shoot at it.... ;-) --Brett At 04:59 PM 4/23/97 +0300, torstenb@ramsey.tb.9715.org wrote: >Peter Dufault wrote: > >> As far as I know it is still only the AHA1542 that supports processor >> target mode. I suggest adding NCR support. > >Hm, I have a box here with an Adaptec 2940 and my HP Scanjet is recognized >as an processor type target: > >ahc0 rev 0 int a irq 12 on pci0:10 >ahc0: aic7870 Single Channel, SCSI Id=7, 16 SCBs > >ahc0:A:5: refuses synchronous negotiation. Using asynchronous transfers >(ahc0:5:0): "HP C2500A 3332" type 3 fixed SCSI 2 >pt0(ahc0:5:0): Processor > > -tb From owner-freebsd-hardware Wed Apr 23 16:35:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA00554 for hardware-outgoing; Wed, 23 Apr 1997 16:35:41 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [207.198.1.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA00549 for ; Wed, 23 Apr 1997 16:35:38 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id TAA01712; Wed, 23 Apr 1997 19:22:20 -0400 (EDT) From: Peter Dufault Message-Id: <199704232322.TAA01712@hda.hda.com> Subject: Re: Yet another Adaptec 2940UW problem :( In-Reply-To: <3.0.1.32.19970423101930.006a67b4@lariat.org> from Brett Glass at "Apr 23, 97 10:19:30 am" To: brett@lariat.org (Brett Glass) Date: Wed, 23 Apr 1997 19:22:19 -0400 (EDT) Cc: torstenb@ramsey.tb.9715.org, dufault@hda.com, gurney_j@resnet.uoregon.edu, hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > This isn't the same thing.... I don't think. This looks as if the FreeBSD > system is still the initiator and the scanner is a target (of the catch-all > "processor" type). I'd like to make the FreeBSD system act as a target. > (And, no, that doesn't mean I'd like to throw it in the air and shoot at > it.... ;-) Right - I believe only the 1542 can do what you want. You don't configure a pt device you configure an "sctarg" device. Getting a 1542 may be a way to prototype. -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-hardware Wed Apr 23 16:56:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA01486 for hardware-outgoing; Wed, 23 Apr 1997 16:56:57 -0700 (PDT) Received: from lariat.lariat.org ([129.72.251.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA01470 for ; Wed, 23 Apr 1997 16:56:50 -0700 (PDT) Received: from solo.lariat.org ([129.72.251.10]) by lariat.lariat.org (8.8.5/8.8.5) with SMTP id RAA04147; Wed, 23 Apr 1997 17:55:58 -0600 (MDT) Message-Id: <3.0.1.32.19970423175524.006f61c4@lariat.org> X-Sender: brett@lariat.org X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Wed, 23 Apr 1997 17:55:24 -0600 To: Peter Dufault From: Brett Glass Subject: Re: Yet another Adaptec 2940UW problem :( Cc: torstenb@ramsey.tb.9715.org, dufault@hda.com, gurney_j@resnet.uoregon.edu, hardware@freebsd.org In-Reply-To: <199704232322.TAA01712@hda.hda.com> References: <3.0.1.32.19970423101930.006a67b4@lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 07:22 PM 4/23/97 -0400, Peter Dufault wrote: >Right - I believe only the 1542 can do what you want. According to their Web site, this is a bus mastering *ISA* adapter, which means you can't transfer data to or from just anyplace in RAM. Does the target driver use the OS's "bounce buffer" hack, or would I have to work around this myself? Also, the adapter is claimed to transfer up to 10 MBps. I know of no ISA adapter that actually goes this fast! Is there something that uses a faster bus interface? I'd like to be able to serve data faster, at least for some transfers. >You don't configure a >pt device you configure an "sctarg" device. Getting a 1542 may be >a way to prototype. Well, ultimately, the machine may be replicated a few hundred times, so I'd like something I could use for "production" as well as prototyping. Is there a reason (other than the bus interface) that the board might be unsuited for production application? If the drivers only support target mode on this one adapter, is there a register-compatible model from another manufacturer that runs faster, has a better bus interface, or is perhaps Fast/Wide or Ultra? I know that BusTek used to have adapters that were register-compatible with Adaptec, but don't know if they have kept this up in more recent models on faster buses. --Brett From owner-freebsd-hardware Thu Apr 24 02:51:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA27484 for hardware-outgoing; Thu, 24 Apr 1997 02:51:49 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [207.198.1.121]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA27478 for ; Thu, 24 Apr 1997 02:51:46 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id FAA02994; Thu, 24 Apr 1997 05:38:12 -0400 (EDT) From: Peter Dufault Message-Id: <199704240938.FAA02994@hda.hda.com> Subject: Re: Yet another Adaptec 2940UW problem :( In-Reply-To: <3.0.1.32.19970423175524.006f61c4@lariat.org> from Brett Glass at "Apr 23, 97 05:55:24 pm" To: brett@lariat.org (Brett Glass) Date: Thu, 24 Apr 1997 05:38:11 -0400 (EDT) Cc: hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > >You don't configure a > >pt device you configure an "sctarg" device. Getting a 1542 may be > >a way to prototype. > > Well, ultimately, the machine may be replicated a few hundred times, so I'd > like something I could use for "production" as well as prototyping. Is > there a reason (other than the bus interface) that the board might be > unsuited for production application? Expensive, old, and from Adaptec. Adaptec will not support documented features of their boards even after convincing an OEM to use a board in a product selling several hundred per year. The documented 17xx target operations are broken and buggy and won't be fixed, and I have a statement from Adaptec that they don't support target ops on any of their boards - ignore the documentation and anything you hear from pre-sales OEM marketing. I recommend that you stay FAR away from Adaptec's board side of the business - I'm sure their chip side is more OEM friendly. Now I remember that it is even worse - note that aha1542.c is only enabling target ops for the 1542B since the 1542C locks up the bus. Use a 1542B only to remove the lack of another adapter as a block in the software development path, and only use 16MB of memory if you do that. I strongly recommend the NCR where you'll have multiple vendors and control over the firmware. I wouldn't try the 1542 clones unless you can get a happy reference from a customer buying several hundred per year. Peter -- Peter Dufault (dufault@hda.com) Realtime Machine Control and Simulation HD Associates, Inc. Voice: 508 433 6936 From owner-freebsd-hardware Thu Apr 24 06:30:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA06196 for hardware-outgoing; Thu, 24 Apr 1997 06:30:20 -0700 (PDT) Received: from info.tva.gov (info.tva.gov [152.85.3.3]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id GAA06190 for ; Thu, 24 Apr 1997 06:30:18 -0700 (PDT) Received: from topaz.cha.tva.gov by info.tva.gov (SMI-8.6/TVA-info.960408) id JAA11555; Thu, 24 Apr 1997 09:33:32 -0400 Received: from chachaois2b.cha.tva.gov (chachaois2b.cha.tva.gov [152.85.66.29]) by topaz.cha.tva.gov (8.7.5/8.7.3/tva.topaz) with SMTP id JAA15522 for ; Thu, 24 Apr 1997 09:30:11 -0400 (EDT) Received: by chachaois2b.cha.tva.gov with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.994.63) id <01BC5092.1D4B6960@chachaois2b.cha.tva.gov>; Thu, 24 Apr 1997 09:30:14 -0400 Message-ID: From: "Swanson, Toby J." To: "'freebsd-hardware@freebsd.org'" Subject: iomega tape drives Date: Thu, 24 Apr 1997 09:29:31 -0400 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.994.63 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone successfully installed and used an iomega ditto tape drive with FreeBSD? Any comments from someone who has set up one will be appreciated. Thanks in advance. Toby From owner-freebsd-hardware Thu Apr 24 07:42:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA09493 for hardware-outgoing; Thu, 24 Apr 1997 07:42:57 -0700 (PDT) Received: from bigbrother (bigbrother.rstcorp.com [206.99.251.67]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA09488 for ; Thu, 24 Apr 1997 07:42:53 -0700 (PDT) Received: (from uucp@localhost) by bigbrother (8.6.12/8.6.9) id KAA03342 for ; Thu, 24 Apr 1997 10:37:58 -0400 Received: from atp.rstcorp.com(206.99.251.77) by bigbrother.rstcorp.com via smap (V2.0) id xma003340; Thu, 24 Apr 97 10:37:20 -0400 Received: from hazard (hazard [206.99.251.71]) by rstcorp.com (8.8.1/8.8.1) with SMTP id KAA18623 for ; Thu, 24 Apr 1997 10:41:33 -0400 (EDT) Date: Thu, 24 Apr 1997 10:40:55 -0400 (EDT) From: "David H. Hovemeyer" X-Sender: daveho@hazard To: hardware@freebsd.org Subject: building an NFS server Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Howdy, The company I work for is going to buy a PC to serve as an NFS (and Samba) server for about 40 workstations and PCs. We're planning on using FreeBSD as the server's OS. The approximate hardware configuration we have in mind is: - P6, 200 MHz - 64MB RAM - Ultra Wide SCSI - 4GB SCSI hard drive - 100BaseTx ethernet I am interested in recommendations on what hardware to use, especially for the motherboard, SCSI controller, and network card. Stability, performance, and compatability with FreeBSD are the main concerns. I would also be interested in hearing recommendations for vendors, especially those who could offer a complete system. Also: are there any NFS-related issues that we should expect by using FreeBSD as the NFS server? We have a variety of client OS's, including SunOS 4.1.x, Solaris 2.x, IRIX, and HP-UX. For example, does FreeBSD support NFS locking? Please CC me, as I'm not subscribed to this list. Thanks, Dave -- David Hovemeyer daveho@rstcorp.com Reliable Software Technologies http://www.rstcorp.com/~daveho From owner-freebsd-hardware Thu Apr 24 08:09:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA10620 for hardware-outgoing; Thu, 24 Apr 1997 08:09:02 -0700 (PDT) Received: from hirame.wwa.com (hirame.wwa.com [198.49.174.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA10613 for ; Thu, 24 Apr 1997 08:08:59 -0700 (PDT) Received: from sokie.kae.net [207.241.60.124] by hirame.wwa.com with smtp (Smail3.1.29.WWA) id m0wKQ8n-000VZMC@hirame.wwa.com; Thu, 24 Apr 97 10:09 CDT Date: Thu, 24 Apr 1997 10:08:56 -0500 (CDT) From: Rory Imua Lampert X-Sender: rory@sokie.kae.net To: "Swanson, Toby J." cc: "'freebsd-hardware@freebsd.org'" Subject: Re: iomega tape drives In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I've set up my IOMega 3200 tape drive..sort of..by adding this line to the kernel config: tape ft0 at fdc0 drive 2 Now, on boot it recognizes the drive fine, but unfortunately there is no support for QIC-3020 tape formats in the driver, or TR-3 (which is what the format of my only tape is). If you look at /usr/src/sys/i386/isa/ft.c, you will find a table of tape geometries. It is under my impression that it is just a matter of adding the geometry for QIC-3020 and TR-3 tapes to this table to get a funtioning driver. I have sent e-mail to several newsgroups, mailing-lists and manufacturers asking if anyone has these parameters, to no avail. Also I downloaded Linux's ftape program and scoured the source for tape parameters to QIC 3020, but didn't find anything useful. Unfortunateley no one has updated the table for 2.2.1, or probably 3.0 for that matter. If you or anyone can find out the parameters to these tape formats, let me know, I would like to be able to back up my machine sometime. Or perhaps the information is easily found but I didn't use my calculator correctly. :> -Rory Imua Lampert rory@wwa.com On Thu, 24 Apr 1997, Swanson, Toby J. wrote: > Has anyone successfully installed and used an iomega ditto tape drive > with FreeBSD? Any comments from someone who has set up one will be > appreciated. > > Thanks in advance. > > Toby > > > From owner-freebsd-hardware Thu Apr 24 10:44:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA20277 for hardware-outgoing; Thu, 24 Apr 1997 10:44:10 -0700 (PDT) Received: from lariat.lariat.org ([129.72.251.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA20227 for ; Thu, 24 Apr 1997 10:44:03 -0700 (PDT) Received: from solo.lariat.org ([129.72.251.10]) by lariat.lariat.org (8.8.5/8.8.5) with SMTP id LAA12904; Thu, 24 Apr 1997 11:43:12 -0600 (MDT) Message-Id: <3.0.1.32.19970424112814.0070acb4@lariat.org> X-Sender: brett@lariat.org X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Thu, 24 Apr 1997 11:28:14 -0600 To: Peter Dufault From: Brett Glass Subject: Re: Yet another Adaptec 2940UW problem :( Cc: hardware@freebsd.org In-Reply-To: <199704240938.FAA02994@hda.hda.com> References: <3.0.1.32.19970423175524.006f61c4@lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk At 05:38 AM 4/24/97 -0400, Peter Dufault wrote: >Use a 1542B only to remove the lack of another adapter as a block >in the software development path, and only use 16MB of memory if >you do that. I strongly recommend the NCR where you'll have multiple >vendors and control over the firmware. But can I use FreeBSD in the embedded system? Is there a target mode driver for any of the NCR chips? --Brett From owner-freebsd-hardware Fri Apr 25 04:36:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA09234 for hardware-outgoing; Fri, 25 Apr 1997 04:36:21 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca33-03.ix.netcom.com [199.35.209.99]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA09229 for ; Fri, 25 Apr 1997 04:36:19 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id EAA28311; Fri, 25 Apr 1997 04:36:09 -0700 (PDT) Date: Fri, 25 Apr 1997 04:36:09 -0700 (PDT) Message-Id: <199704251136.EAA28311@silvia.HIP.Berkeley.EDU> To: daveho@rstcorp.com CC: hardware@FreeBSD.ORG In-reply-to: (daveho@rstcorp.com) Subject: Re: building an NFS server From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * Also: are there any NFS-related issues that we should expect by * using FreeBSD as the NFS server? We have a variety of client * OS's, including SunOS 4.1.x, Solaris 2.x, IRIX, and HP-UX. * For example, does FreeBSD support NFS locking? If you are using NFS, I recommend using an NCR-based controller. We have had lots of problems with Adaptec recently. Satoshi From owner-freebsd-hardware Fri Apr 25 07:12:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA17549 for hardware-outgoing; Fri, 25 Apr 1997 07:12:41 -0700 (PDT) Received: from elwood.pionet.net (ELWOOD.pionet.net [199.120.116.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA17522 for ; Fri, 25 Apr 1997 07:12:31 -0700 (PDT) Received: from pm3_176.pionet.net by elwood.pionet.net (5.65v3.2/1.1.10.5/25Oct96-0835PM) id AA20143; Fri, 25 Apr 1997 09:15:19 -0500 Message-Id: <3360AC2C.5FDA@pionet.net> Date: Fri, 25 Apr 1997 09:05:48 -0400 From: Tyson Boellstorff X-Mailer: Mozilla 2.02E (OS/2; I) Mime-Version: 1.0 To: Satoshi Asami Cc: hardware@freebsd.org Subject: Re: building an NFS server References: <199704251136.EAA28311@silvia.HIP.Berkeley.EDU> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Satoshi Asami wrote: > If you are using NFS, I recommend using an NCR-based controller. > We have had lots of problems with Adaptec recently. > > Satoshi Wasn't that "lots of problems" with a particular model of Adaptec controller? So far, my only problem with the OEM versions of the controllers I work with has been resolved by disabling SCAM support, and verifying the BIOS rev of the controller. I guess we must just be living clean. ;-) Tyson From owner-freebsd-hardware Fri Apr 25 07:15:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA17753 for hardware-outgoing; Fri, 25 Apr 1997 07:15:40 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (silvia.HIP.Berkeley.EDU [136.152.64.181]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA17743 for ; Fri, 25 Apr 1997 07:15:34 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.5/8.6.9) id HAA14590; Fri, 25 Apr 1997 07:15:07 -0700 (PDT) Date: Fri, 25 Apr 1997 07:15:07 -0700 (PDT) Message-Id: <199704251415.HAA14590@silvia.HIP.Berkeley.EDU> To: tysonb@pionet.net CC: hardware@freebsd.org In-reply-to: <3360AC2C.5FDA@pionet.net> (message from Tyson Boellstorff on Fri, 25 Apr 1997 09:05:48 -0400) Subject: Re: building an NFS server From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * Wasn't that "lots of problems" with a particular model of Adaptec * controller? So far, my only problem with the OEM versions of the * controllers I work with has been resolved by disabling SCAM support, and * verifying the BIOS rev of the controller. I guess we must just be living * clean. ;-) Well, that particular "model" is called the 2940/3940 series. Your mileage may vary, but chances are that you can't use them under very heavy load. Satoshi From owner-freebsd-hardware Fri Apr 25 08:12:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA21657 for hardware-outgoing; Fri, 25 Apr 1997 08:12:37 -0700 (PDT) Received: from mccomm.nl (root@gateppp.mccomm.nl [193.67.87.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA21650 for ; Fri, 25 Apr 1997 08:12:34 -0700 (PDT) Received: from hpserver.mccomm.nl (hpserver.mccomm.nl [193.67.87.13]) by mccomm.nl (8.7.5/8.7.3) with SMTP id RAA07693 for ; Fri, 25 Apr 1997 17:12:22 +0200 Message-Id: <199704251512.RAA07693@mccomm.nl> Received: by hpserver.mccomm.nl (1.38.193.5/16.2) id AA01545; Fri, 25 Apr 1997 17:12:21 +0200 From: Rob Schofield Subject: SCSI controller To: freebsd-hardware@freebsd.org (Hardware list at FreeBSD) Date: Fri, 25 Apr 97 17:12:20 METDST Mailer: Elm [revision: 70.85.2.1] Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi there. Can anyone recommend a *good*, bus-mastering 32-bit EISA SCSI controller host adaptor supported by FBSD2.x onwards? Ideas on price/availability etc. would be welcome. Additionally, anyone have any knowledge of BIOS bugs relating to synchronous data transfer negotioation in the AHA-1742? Rob Schofield -- Witticisms are hard to define on Monday mornings... schofiel@xs4all.nl http://www.xs4all.nl/~schofiel rschof@mccomm.nl From owner-freebsd-hardware Fri Apr 25 13:10:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA08793 for hardware-outgoing; Fri, 25 Apr 1997 13:10:34 -0700 (PDT) Received: from root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA08788 for ; Fri, 25 Apr 1997 13:10:32 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id NAA16660; Fri, 25 Apr 1997 13:11:47 -0700 (PDT) Message-Id: <199704252011.NAA16660@root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: asami@vader.cs.berkeley.edu (Satoshi Asami) cc: tysonb@pionet.net, hardware@freebsd.org Subject: Re: building an NFS server In-reply-to: Your message of "Fri, 25 Apr 1997 07:15:07 PDT." <199704251415.HAA14590@silvia.HIP.Berkeley.EDU> From: David Greenman Reply-To: dg@root.com Date: Fri, 25 Apr 1997 13:11:47 -0700 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > * Wasn't that "lots of problems" with a particular model of Adaptec > * controller? So far, my only problem with the OEM versions of the > * controllers I work with has been resolved by disabling SCAM support, and > * verifying the BIOS rev of the controller. I guess we must just be living > * clean. ;-) > >Well, that particular "model" is called the 2940/3940 series. Your >mileage may vary, but chances are that you can't use them under very >heavy load. I wouldn't characterize the load on wcarchive as "light", and I haven't had any problems with the driver since Justin's recent fixes. It's been completely stable. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hardware Sat Apr 26 12:56:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA05757 for hardware-outgoing; Sat, 26 Apr 1997 12:56:27 -0700 (PDT) Received: from dfw-ix2.ix.netcom.com (dfw-ix2.ix.netcom.com [206.214.98.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA05752 for ; Sat, 26 Apr 1997 12:56:24 -0700 (PDT) Received: (from smap@localhost) by dfw-ix2.ix.netcom.com (8.8.4/8.8.4) id OAA26317; Sat, 26 Apr 1997 14:55:06 -0500 (CDT) Received: from sjx-ca53-03.ix.netcom.com(206.214.106.35) by dfw-ix2.ix.netcom.com via smap (V1.3) id smad26252; Sat Apr 26 14:54:55 1997 Received: (from asami@localhost) by blimp.mimi.com (8.8.5/8.6.9) id CAA02373; Sat, 26 Apr 1997 02:15:49 -0700 (PDT) Date: Sat, 26 Apr 1997 02:15:49 -0700 (PDT) Message-Id: <199704260915.CAA02373@blimp.mimi.com> To: dg@root.com CC: tysonb@pionet.net, hardware@freebsd.org In-reply-to: <199704252011.NAA16660@root.com> (message from David Greenman on Fri, 25 Apr 1997 13:11:47 -0700) Subject: Re: building an NFS server From: asami@vader.cs.berkeley.edu (Satoshi Asami) Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk * I wouldn't characterize the load on wcarchive as "light", and I haven't * had any problems with the driver since Justin's recent fixes. It's been * completely stable. I'll be more than glad to be corrected. Hey, are there any NFS servers using ahc out there? If you can post success/failure stories, it will be great. Satoshi From owner-freebsd-hardware Sat Apr 26 16:22:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA16130 for hardware-outgoing; Sat, 26 Apr 1997 16:22:01 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA16119 for ; Sat, 26 Apr 1997 16:21:55 -0700 (PDT) Received: from brasil.brainstorm.eu.org (brasil.brainstorm.fr [193.56.58.33]) by mexico.brainstorm.eu.org (8.8.4/8.8.4) with ESMTP id BAA02542 for ; Sun, 27 Apr 1997 01:21:49 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.4/8.6.12) with UUCP id BAA05073 for freebsd-hardware@freebsd.org; Sun, 27 Apr 1997 01:21:44 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.5/keltia-uucp-2.9) id BAA09087; Sun, 27 Apr 1997 01:00:11 +0200 (CEST) Message-ID: <19970427010011.04449@keltia.freenix.fr> Date: Sun, 27 Apr 1997 01:00:11 +0200 From: Ollivier Robert To: Hardware list at FreeBSD Subject: Re: SCSI controller References: <199704251512.RAA07693@mccomm.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.67 In-Reply-To: <199704251512.RAA07693@mccomm.nl>; from Rob Schofield on Fri, Apr 25, 1997 at 05:12:20PM +0000 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3245 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk According to Rob Schofield: > Can anyone recommend a *good*, bus-mastering 32-bit EISA SCSI > controller host adaptor supported by FBSD2.x onwards? Ideas on > price/availability etc. would be welcome. Until recently I was using a Buslogic BT-747S (along with an Adaptec 1740A) in my machine, now upgraded to a dual NCR-810 P133... I've used the BT-747S with great success for more than 3 years without problem. Probing for devices on the EISA bus bt0: at 0x330-0x333, 0x3c00-0x3cff irq 11 bt0: on eisa0 slot 3 bt0: Bt747 / 0-(32bit) bus bt0: reading board settings, busmastering, int=11 bt0: version 3.37, fast sync, parity, 32 mbxs, 32 ccbs > Additionally, anyone have any knowledge of BIOS bugs relating to > synchronous data transfer negotioation in the AHA-1742? My Adaptec either didn't have this bugs or I wasn't aware of them. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #7: Sat Apr 26 17:13:26 CEST 1997