From owner-freebsd-hardware Sun Sep 14 02:09:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA02087 for hardware-outgoing; Sun, 14 Sep 1997 02:09:21 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA02078 for ; Sun, 14 Sep 1997 02:09:14 -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 LAA27275 for ; Sun, 14 Sep 1997 11:09:24 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id LAA21354 for hardware@FreeBSD.ORG; Sun, 14 Sep 1997 11:08:53 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-uucp-2.10/nospam) id CAA21355; Sun, 14 Sep 1997 02:43:48 +0200 (CEST) Message-ID: <19970914024348.21276@keltia.freenix.fr> Date: Sun, 14 Sep 1997 02:43:48 +0200 From: Ollivier Robert To: hardware@FreeBSD.ORG Subject: Re: Fwd: K6 Linux Re-Compile Issue References: <199709131748.NAA09633@sabre.goldsword.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <199709131748.NAA09633@sabre.goldsword.com>; from John T. Farmer on Sat, Sep 13, 1997 at 01:48:44PM -0400 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3634 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to John T. Farmer: > When you get yours & verify that the problem is fixed, _please_ forward > details such as rev. numbers & stepping so that we can be sure to get > the new ones... AFAIK, K6 with a revision # higher than 9730 should be good. Look at for details. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #31: Sat Sep 6 21:58:17 CEST 1997 From owner-freebsd-hardware Sun Sep 14 07:42:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA12384 for hardware-outgoing; Sun, 14 Sep 1997 07:42:28 -0700 (PDT) Received: from nemesis.idirect.com (root@nemesis.idirect.com [207.136.80.40]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA12364; Sun, 14 Sep 1997 07:42:24 -0700 (PDT) Received: from thor.idirect.com (jlixfeld@thor.idirect.com [207.136.80.105]) by nemesis.idirect.com (8.8.5/8.8.4) with SMTP id KAA29246; Sun, 14 Sep 1997 10:42:23 -0400 (EDT) Received: from localhost (jlixfeld@localhost) by thor.idirect.com (8.6.12/8.6.12) with SMTP id KAA04065; Sun, 14 Sep 1997 10:42:21 -0400 X-Authentication-Warning: thor.idirect.com: jlixfeld owned process doing -bs Date: Sun, 14 Sep 1997 10:42:21 -0400 (EDT) From: Jason Lixfeld To: freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: DLINK 21140 Card Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I have FreeBSD 2.2.2, DLink DEC Tulip 21140AE REV-2C Chipset with the if_de.c from Matt Thomas' site, 3am-software.com. I have tried with the 21140AC REV-1B Chipset, and am getting the same problems: It's fine on a bootup, but after a few hours, the ethernet just stops responding. Their is still a link light on my hub, put it is not pingable, and tests from the console are useless. ifconfig de0 shows the interface as being up, however I'm seeing a flag "OACTIVE" and I'm not sure that is supposed to be there. Has anyone had trouble with these cards/driver before, and does anyone have a solution? TiA.. From owner-freebsd-hardware Sun Sep 14 08:16:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA13806 for hardware-outgoing; Sun, 14 Sep 1997 08:16:44 -0700 (PDT) Received: from mailhost.pi.net (root@mailhost.pi.net [145.220.3.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA13799 for ; Sun, 14 Sep 1997 08:16:42 -0700 (PDT) Received: from kinchenna (asd132.pi.net [145.220.192.132]) by mailhost.pi.net (8.8.3/8.7.1) with SMTP id RAA21471; Sun, 14 Sep 1997 17:16:31 +0200 (MET DST) Posted-Date: Sun, 14 Sep 1997 17:16:31 +0200 (MET DST) Date: Sun, 14 Sep 1997 16:50:55 +0100 From: Guido Kollerie Subject: Re: Micropolis Runs Too HOT! To: freebsd-hardware@freebsd.org Cc: Tom Jackson X-Mailer: Z-Mail Pro 6.1 (Win32 - 021297) Evaluation Copy, NetManage Inc. X-Priority: 3 (Normal) References: <19970913143722.25435@my.domain> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > The long and short of it is now I am running my computer > with the case off and a fan blowing on the hard disk bay. > The hot mic is the bottom one in the bay. There is a drive > space before the next drive, also a Micropolis 2 gig, 5400 > rpm drive (it runs cool). > > Has anyone seen a problem like this and do you have any > suggestions. http://www.baycooler.com/ I have one and it keeps my harddrive cool. Note: one of the two fans of the first kit I received stopped working within two weeks. I rma'ed it to Granite Digital Inc. (http://www.scsipro.com/) and received a replacement which still works fine. However I have only been using it for three weeks now. -- Guido Kollerie From owner-freebsd-hardware Sun Sep 14 12:31:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA25180 for hardware-outgoing; Sun, 14 Sep 1997 12:31:02 -0700 (PDT) Received: from persprog.com (root@persprog.com [204.215.255.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA25168 for ; Sun, 14 Sep 1997 12:30:54 -0700 (PDT) Received: by persprog.com (8.7.5/4.10) id NAA22254; Sun, 14 Sep 1997 13:34:31 -0500 Received: from dave.ppi.com(192.2.2.6) by cerberus.ppi.com via smap (V1.3) id sma022252; Sun Sep 14 14:34:06 1997 Message-ID: <341C2E1A.EE58EA81@persprog.com> Date: Sun, 14 Sep 1997 14:34:02 -0400 From: Dave Alderman Reply-To: dave@persprog.com Organization: Personalized Programming, Inc X-Mailer: Mozilla 4.0 [en] (Win95; U) MIME-Version: 1.0 To: Tom Jackson CC: freebsd-hardware@FreeBSD.ORG Subject: Re: Micropolis Runs Too HOT! X-Priority: 3 (Normal) References: <19970913143722.25435@my.domain> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tom Jackson wrote: > > Hi all, > > Just started using a Micropolis Tomahawk, 7200 rpm 4.5 gb > hard disk about a week ago. All was well until yesterday > when starting getting scb messages and system froze. > Killed system (no shutdown,turn power off) and when trying > to startup again, the scsi bios did not see the disk at > scsi id 0. Took case off and the disk was hot to very hot > to the touch. Cooled it off with a fan and turned air > conditioning on. ... > Has anyone seen a problem like this and do you have any > suggestions. I have contacted the Micropolis web site but > have not heard anything back yet. Many 7200 RPM drives require forced air cooling. Most PC cases do not have adequate ventilation in the drive bay area for 7200RPM drives. One thing you could try is one of those replacement bay covers that has little fans built into it. "Just Cooler" is one brand I have seen. Of course these only fit in a 5.25" drive bay (which is a good place to put hot drives anyhow). A cheaper trick is to simply cable-tie a muffin fan in front of the overheating drive if there is enough room in the case for it. Unfortunately, the thermal stress your drive encountered may have caused permanent damage to the drive. I found out the hard way that you need to pay close attention to the thermal specs for drives before installing them, especially if they are high performance drives meant for the server market since server cabinets often (but not always!) have good ventilation around the drive bays. We had an RS6000 cabinet in at work (a J-series, I think) that seemed to have a small breeze coming out of the entire surface of its perforated back. A quick investigation revealed fans over much of the front surface of the cabinet that provided this air flow. I wish someone would male a PC case like that for a reasonable price. -- "Going down to South Park - going to leave my woes behind..." David W. Alderman dave@persprog.com From owner-freebsd-hardware Sun Sep 14 18:17:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA17033 for hardware-outgoing; Sun, 14 Sep 1997 18:17:53 -0700 (PDT) Received: from peeper.my.domain ([208.128.8.69]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA17028 for ; Sun, 14 Sep 1997 18:17:47 -0700 (PDT) Received: (from tom@localhost) by peeper.my.domain (8.8.5/8.8.5) id UAA01032; Sun, 14 Sep 1997 20:17:05 -0500 (CDT) Message-ID: <19970914201705.14663@my.domain> Date: Sun, 14 Sep 1997 20:17:05 -0500 From: Tom Jackson To: freebsd-hardware@FreeBSD.ORG Subject: Re: Micropolis Runs Too HOT! References: <19970913143722.25435@my.domain> <341C2E1A.EE58EA81@persprog.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <341C2E1A.EE58EA81@persprog.com>; from Dave Alderman on Sun, Sep 14, 1997 at 02:34:02PM -0400 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thanks for all the relies to my delime. I am trying to get the drive returned and replaced with a Fujitsu M2954S. They have an excellent -no excuses- return policy that I have had occasion to use once, so that takes most of the fear factor out of these situations. I'm also ordering one of the 5-1/4 inch cooler fans as added insurance. All of my other drives are 5400's 1-2gb-Micropolis and 2-1gb-Fujitsu with only the one mentioned problem. I appreciated the suggestions on cooling requirements and only wish the manufacture and resellers were as informative. I hope this mess may help prevent the same problem with others. Tom From owner-freebsd-hardware Sun Sep 14 22:07:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA29170 for hardware-outgoing; Sun, 14 Sep 1997 22:07:04 -0700 (PDT) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA29165 for ; Sun, 14 Sep 1997 22:07:02 -0700 (PDT) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id WAA05355; Sun, 14 Sep 1997 22:03:19 -0700 (PDT) Date: Sun, 14 Sep 1997 22:03:19 -0700 (PDT) From: Jim Shankland Message-Id: <199709150503.WAA05355@biggusdiskus.flyingfox.com> To: jlixfeld@idirect.com Subject: Re: DLINK 21140 Card Cc: freebsd-hardware@freebsd.org Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Try reducing the value of TULIP_TXDESCS from 128 to 32, recompile the driver, and see if that helps; please report back either way. Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-hardware Mon Sep 15 06:07:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA27793 for hardware-outgoing; Mon, 15 Sep 1997 06:07:49 -0700 (PDT) Received: from nemesis.idirect.com (root@nemesis.idirect.com [207.136.80.40]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA27784 for ; Mon, 15 Sep 1997 06:07:45 -0700 (PDT) Received: from thor.idirect.com (jlixfeld@thor.idirect.com [207.136.80.105]) by nemesis.idirect.com (8.8.5/8.8.4) with SMTP id JAA12245; Mon, 15 Sep 1997 09:07:36 -0400 (EDT) Received: from localhost (jlixfeld@localhost) by thor.idirect.com (8.6.12/8.6.12) with SMTP id JAA15316; Mon, 15 Sep 1997 09:07:35 -0400 X-Authentication-Warning: thor.idirect.com: jlixfeld owned process doing -bs Date: Mon, 15 Sep 1997 09:07:35 -0400 (EDT) From: Jason Lixfeld To: Jim Shankland cc: freebsd-hardware@freebsd.org Subject: Re: DLINK 21140 Card In-Reply-To: <199709150503.WAA05355@biggusdiskus.flyingfox.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm not sure if it will work or not, but I'm going to change it to match TULIP_RXDESCS. That is set to 48. I'm not sure if it will let me, or if it will even run. If you think not, let me know. If I should change it to 32, should I not change RX to 32 from 48 just to keep things symmetrical?! On Sun, 14 Sep 1997, Jim Shankland wrote: > Try reducing the value of TULIP_TXDESCS from 128 to 32, recompile the > driver, and see if that helps; please report back either way. > > Jim Shankland > Flying Fox Computer Systems, Inc. > From owner-freebsd-hardware Mon Sep 15 07:08:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA00927 for hardware-outgoing; Mon, 15 Sep 1997 07:08:17 -0700 (PDT) Received: from news.nacamar.de (news.nacamar.de [194.162.162.210]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA00918 for ; Mon, 15 Sep 1997 07:08:13 -0700 (PDT) Received: from newsfeed (newsfeed.nacamar.de [194.162.162.196]) by news.nacamar.de (8.8.7/8.8.6) with SMTP id QAA15526 for ; Mon, 15 Sep 1997 16:08:07 +0200 (CEST) Message-Id: <3.0.3.32.19970915160712.00b69930@mail.nacamar.de> X-Sender: petzi@mail.nacamar.de X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Mon, 15 Sep 1997 16:07:12 +0200 To: hardware@freebsd.org From: Michael Beckmann Subject: Parity trouble with Asus mainboard Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, I had installed 8 x 32 MB parity SIMMs in an Asus P65UP5 Rev. 2.04 mainboard with Pentium Pro card P6ND in it. The system is equipped with one PPro 200 CPU. Unfortunately, when I install 4, 6 or 8 of these SIMMs, FreeBSD gives me a parity error and panics directly after the copyright notice during boot. With 2 x 32 MB, it seems to run OK. This, however, happens only when I enable ECC in the BIOS. When I disable ECC/parity, the system runs fine with 256 MB installed. I made world on the latest 2.2-stable in this configuration, no problem. I also tried the same SIMMs in a Gigabyte 586 HX board, and there I can boot and run just fine with ECC enabled in the BIOS (it's an NT system, though). Any ideas ? It doesn't look to me like the SIMMs were faulty. Maybe a problem with the parity chips ? I also exchanged the mainboard with another one of the same type, but found the same problem. Michael From owner-freebsd-hardware Mon Sep 15 09:42:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA08293 for hardware-outgoing; Mon, 15 Sep 1997 09:42:24 -0700 (PDT) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA08288 for ; Mon, 15 Sep 1997 09:42:21 -0700 (PDT) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id JAA12987; Mon, 15 Sep 1997 09:38:38 -0700 (PDT) Date: Mon, 15 Sep 1997 09:38:38 -0700 (PDT) From: Jim Shankland Message-Id: <199709151638.JAA12987@biggusdiskus.flyingfox.com> To: jlixfeld@idirect.com Subject: Re: DLINK 21140 Card Cc: freebsd-hardware@freebsd.org Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >From jlixfeld@idirect.com Mon Sep 15 06:04:06 1997 X-Authentication-Warning: thor.idirect.com: jlixfeld owned process doing -bs Date: Mon, 15 Sep 1997 09:07:35 -0400 (EDT) From: Jason Lixfeld To: Jim Shankland cc: freebsd-hardware@freebsd.org Subject: Re: DLINK 21140 Card In-Reply-To: <199709150503.WAA05355@biggusdiskus.flyingfox.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Jason Lixfeld writes: > I'm not sure if it will work or not, but I'm going to change it > to match TULIP_RXDESCS. That is set to 48. I'm not sure if it > will let me, or if it will even run. If you think not, let me > know. If I should change it to 32, should I not change RX to > 32 from 48 just to keep things symmetrical?! > > On Sun, 14 Sep 1997, Jim Shankland wrote: > > > Try reducing the value of TULIP_TXDESCS from 128 to 32, recompile the > > driver, and see if that helps; please report back either way. > > > > Jim Shankland > > Flying Fox Computer Systems, Inc. The important thing for the purpose of this experiment is to reduce the size of the tulip_softc structure to < 4 KB. The number of TXDESCS and RXDESCS need not be the same. When the size of the tulip_softc structure is > 4 KB, it is possible to see failures quite similar to what you are seeing. On the other hand, your problem might be entirely unrelated. Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-hardware Mon Sep 15 09:48:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA08665 for hardware-outgoing; Mon, 15 Sep 1997 09:48:12 -0700 (PDT) Received: from nemesis.idirect.com (root@nemesis.idirect.com [207.136.80.40]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA08651 for ; Mon, 15 Sep 1997 09:48:08 -0700 (PDT) Received: from thor.idirect.com (jlixfeld@thor.idirect.com [207.136.80.105]) by nemesis.idirect.com (8.8.5/8.8.4) with SMTP id MAA08539; Mon, 15 Sep 1997 12:48:02 -0400 (EDT) Received: from localhost (jlixfeld@localhost) by thor.idirect.com (8.6.12/8.6.12) with SMTP id MAA18869; Mon, 15 Sep 1997 12:48:01 -0400 X-Authentication-Warning: thor.idirect.com: jlixfeld owned process doing -bs Date: Mon, 15 Sep 1997 12:48:01 -0400 (EDT) From: Jason Lixfeld To: Jim Shankland cc: freebsd-hardware@freebsd.org Subject: Re: DLINK 21140 Card In-Reply-To: <199709151638.JAA12987@biggusdiskus.flyingfox.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Okay, well I adjusted the level from 128 to 48 (to match RXDESC) and it is looking good so far. On Mon, 15 Sep 1997, Jim Shankland wrote: > >From jlixfeld@idirect.com Mon Sep 15 06:04:06 1997 > X-Authentication-Warning: thor.idirect.com: jlixfeld owned process doing -bs > Date: Mon, 15 Sep 1997 09:07:35 -0400 (EDT) > From: Jason Lixfeld > To: Jim Shankland > cc: freebsd-hardware@freebsd.org > Subject: Re: DLINK 21140 Card > In-Reply-To: <199709150503.WAA05355@biggusdiskus.flyingfox.com> > MIME-Version: 1.0 > Content-Type: TEXT/PLAIN; charset=US-ASCII > > Jason Lixfeld writes: > > > I'm not sure if it will work or not, but I'm going to change it > > to match TULIP_RXDESCS. That is set to 48. I'm not sure if it > > will let me, or if it will even run. If you think not, let me > > know. If I should change it to 32, should I not change RX to > > 32 from 48 just to keep things symmetrical?! > > > > On Sun, 14 Sep 1997, Jim Shankland wrote: > > > > > Try reducing the value of TULIP_TXDESCS from 128 to 32, recompile the > > > driver, and see if that helps; please report back either way. > > > > > > Jim Shankland > > > Flying Fox Computer Systems, Inc. > > The important thing for the purpose of this experiment is to reduce > the size of the tulip_softc structure to < 4 KB. The number of TXDESCS > and RXDESCS need not be the same. > > When the size of the tulip_softc structure is > 4 KB, it is possible to > see failures quite similar to what you are seeing. On the other hand, > your problem might be entirely unrelated. > > Jim Shankland > Flying Fox Computer Systems, Inc. > From owner-freebsd-hardware Mon Sep 15 10:04:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA09767 for hardware-outgoing; Mon, 15 Sep 1997 10:04:54 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA09761 for ; Mon, 15 Sep 1997 10:04:50 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0xAeUx-0004P6-00; Mon, 15 Sep 1997 09:59:43 -0700 Date: Mon, 15 Sep 1997 09:59:43 -0700 (PDT) From: Tom To: Michael Beckmann cc: hardware@freebsd.org Subject: Re: Parity trouble with Asus mainboard In-Reply-To: <3.0.3.32.19970915160712.00b69930@mail.nacamar.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Mon, 15 Sep 1997, Michael Beckmann wrote: > Greetings, > > I had installed 8 x 32 MB parity SIMMs in an Asus P65UP5 Rev. 2.04 > mainboard with Pentium Pro card P6ND in it. The system is equipped with one > PPro 200 CPU. Unfortunately, when I install 4, 6 or 8 of these SIMMs, > FreeBSD gives me a parity error and panics directly after the copyright > notice during boot. With 2 x 32 MB, it seems to run OK. > > This, however, happens only when I enable ECC in the BIOS. When I disable > ECC/parity, the system runs fine with 256 MB installed. I made world on the > latest 2.2-stable in this configuration, no problem. > > I also tried the same SIMMs in a Gigabyte 586 HX board, and there I can > boot and run just fine with ECC enabled in the BIOS (it's an NT system, > though). > > Any ideas ? It doesn't look to me like the SIMMs were faulty. Maybe a > problem with the parity chips ? I also exchanged the mainboard with another > one of the same type, but found the same problem. > > Michael I've installed the the same motherboard in a server with 8 32MB SIMMs, with ECC turned on. It works very well. Tom From owner-freebsd-hardware Mon Sep 15 10:57:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA13215 for hardware-outgoing; Mon, 15 Sep 1997 10:57:43 -0700 (PDT) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA13210 for ; Mon, 15 Sep 1997 10:57:38 -0700 (PDT) Received: from Eng.Sun.COM ([129.146.1.25]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id KAA14028; Mon, 15 Sep 1997 10:57:06 -0700 Received: from taller.eng.sun.com by Eng.Sun.COM (SMI-8.6/SMI-5.3) id KAA14249; Mon, 15 Sep 1997 10:57:04 -0700 Received: from p-1.eng.sun.com by taller.eng.sun.com (SMI-8.6/SMI-SVR4) id KAA02384; Mon, 15 Sep 1997 10:57:30 -0700 Received: from localhost by p-1.eng.sun.com (SMI-8.6/SMI-SVR4) id KAA06546; Mon, 15 Sep 1997 10:54:58 -0700 Date: Mon, 15 Sep 1997 10:54:58 -0700 (PDT) From: William Maddox X-Sender: maddox@p-1 To: Michael Beckmann cc: hardware@FreeBSD.ORG Subject: Re: Parity trouble with Asus mainboard In-Reply-To: <3.0.3.32.19970915160712.00b69930@mail.nacamar.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 15 Sep 1997, Michael Beckmann wrote: > Greetings, > > I had installed 8 x 32 MB parity SIMMs in an Asus P65UP5 Rev. 2.04 > mainboard with Pentium Pro card P6ND in it. The system is equipped with one > PPro 200 CPU. Unfortunately, when I install 4, 6 or 8 of these SIMMs, > FreeBSD gives me a parity error and panics directly after the copyright > notice during boot. With 2 x 32 MB, it seems to run OK. > > This, however, happens only when I enable ECC in the BIOS. When I disable > ECC/parity, the system runs fine with 256 MB installed. I made world on the > latest 2.2-stable in this configuration, no problem. > > I also tried the same SIMMs in a Gigabyte 586 HX board, and there I can > boot and run just fine with ECC enabled in the BIOS (it's an NT system, > though). > > Any ideas ? It doesn't look to me like the SIMMs were faulty. Maybe a > problem with the parity chips ? I also exchanged the mainboard with another > one of the same type, but found the same problem. > > Michael Are you sure these are true parity SIMMs? Some cheap SIMMs use "logic parity", which just fakes a parity bit for older MBs that require it. These will not work with ECC, and should be avoided in any case. Also, you describe these SIMMs as 2 x 32, 8 x 32 and so forth. In standard nomenclature, the "32" is the width of the SIMM, i.e., 32 bits. Parity SIMMs are 2 x 36, etc. Admittedly, this doesn't explain why the Gigabyte board worked, unless somehow the ECC was disabled behind your back. --Bill From owner-freebsd-hardware Mon Sep 15 11:47:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA16165 for hardware-outgoing; Mon, 15 Sep 1997 11:47:50 -0700 (PDT) Received: from hobbes.saturn-tech.com (drussell@drussell.internode.net [198.161.228.154]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA16157 for ; Mon, 15 Sep 1997 11:47:45 -0700 (PDT) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id MAA01901; Mon, 15 Sep 1997 12:47:13 -0600 (MDT) Date: Mon, 15 Sep 1997 12:47:13 -0600 (MDT) From: Doug Russell To: William Maddox cc: Michael Beckmann , hardware@FreeBSD.ORG Subject: Re: Parity trouble with Asus mainboard In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Are you sure these are true parity SIMMs? Some cheap SIMMs use "logic > parity", which just fakes a parity bit for older MBs that require it. > These will not work with ECC, and should be avoided in any case. > Also, you describe these SIMMs as 2 x 32, 8 x 32 and so forth. In > standard nomenclature, the "32" is the width of the SIMM, i.e., 32 bits. > Parity SIMMs are 2 x 36, etc. > > Admittedly, this doesn't explain why the Gigabyte board worked, unless > somehow the ECC was disabled behind your back. It is quite possible that the Gigabyte automatically disables ECC if you don't actually have parity memory installed as an "idiot-proof" type feature. I honestly don't know for sure, though. Later...... From owner-freebsd-hardware Mon Sep 15 11:57:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA16760 for hardware-outgoing; Mon, 15 Sep 1997 11:57:51 -0700 (PDT) Received: from onyx.atipa.com (user27586@ns.atipa.com [208.128.22.10]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA16750 for ; Mon, 15 Sep 1997 11:57:47 -0700 (PDT) Received: (qmail-queue invoked by uid 1018); 15 Sep 1997 19:01:31 -0000 Date: Mon, 15 Sep 1997 13:01:31 -0600 (MDT) From: Atipa X-Sender: freebsd@dot.ishiboo.com To: Jason Lixfeld cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: DLINK 21140 Card In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The D-Link cards I am familiar with have a nice chipset, but a piss-poor connector. Instead of using all 8 pins for the RJ-45 connector, they try to save about $.0005 per card by only using the 4 TX/RX pins. This results in lots of intermittant connections. An intermittant connection on a switching medium (10/100) can cause lock-ups like you are reporting. We discontinued carrying that card for this exact reason. My recommendation would be to make sure you have good strain-relief on the cable, and lateral support if possible. Or replace the card... If it is not a physical connection problem, you may have buffer overflows. Do you get any erros in /var/log/messages? Does dmesg report "deo timeout"? Kevin On Sun, 14 Sep 1997, Jason Lixfeld wrote: > I have FreeBSD 2.2.2, DLink DEC Tulip 21140AE REV-2C Chipset with the > if_de.c from Matt Thomas' site, 3am-software.com. I have tried with the > 21140AC REV-1B Chipset, and am getting the same problems: It's fine on a > bootup, but after a few hours, the ethernet just stops responding. Their > is still a link light on my hub, put it is not pingable, and tests from > the console are useless. ifconfig de0 shows the interface as being up, > however I'm seeing a flag "OACTIVE" and I'm not sure that is supposed to > be there. Has anyone had trouble with these cards/driver before, and does > anyone have a solution? > > TiA.. > > > From owner-freebsd-hardware Mon Sep 15 12:30:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA18780 for hardware-outgoing; Mon, 15 Sep 1997 12:30:24 -0700 (PDT) Received: from cypher.net (black@zen.pratt.edu [205.232.115.155]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA18752; Mon, 15 Sep 1997 12:30:02 -0700 (PDT) Received: (from black@localhost) by cypher.net (8.8.7/8.7.1) id PAA14616; Mon, 15 Sep 1997 15:40:02 -0400 Date: Mon, 15 Sep 1997 15:40:01 -0400 (EDT) From: Ben Black To: Atipa cc: Jason Lixfeld , freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: DLINK 21140 Card In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk this is called T4 (vs TX) and it is a simplex version of fast ethernet. On Mon, 15 Sep 1997, Atipa wrote: > > The D-Link cards I am familiar with have a nice chipset, but a piss-poor > connector. Instead of using all 8 pins for the RJ-45 connector, they try > to save about $.0005 per card by only using the 4 TX/RX pins. This > results in lots of intermittant connections. An intermittant connection > on a switching medium (10/100) can cause lock-ups like you are > reporting. We discontinued carrying that card for this exact reason. > > My recommendation would be to make sure you have good strain-relief on > the cable, and lateral support if possible. Or replace the card... > > If it is not a physical connection problem, you may have buffer > overflows. Do you get any erros in /var/log/messages? Does dmesg report > "deo timeout"? > > Kevin > > On Sun, 14 Sep 1997, Jason Lixfeld wrote: > > > I have FreeBSD 2.2.2, DLink DEC Tulip 21140AE REV-2C Chipset with the > > if_de.c from Matt Thomas' site, 3am-software.com. I have tried with the > > 21140AC REV-1B Chipset, and am getting the same problems: It's fine on a > > bootup, but after a few hours, the ethernet just stops responding. Their > > is still a link light on my hub, put it is not pingable, and tests from > > the console are useless. ifconfig de0 shows the interface as being up, > > however I'm seeing a flag "OACTIVE" and I'm not sure that is supposed to > > be there. Has anyone had trouble with these cards/driver before, and does > > anyone have a solution? > > > > TiA.. > > > > > > > From owner-freebsd-hardware Mon Sep 15 15:50:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA00836 for hardware-outgoing; Mon, 15 Sep 1997 15:50:55 -0700 (PDT) Received: from ns2.xinetron.com (ns2.xinetron.com [206.86.215.67]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA00802; Mon, 15 Sep 1997 15:50:43 -0700 (PDT) Received: from pop.xinetron.com (pop.xinetron.com [206.86.215.82]) by ns2.xinetron.com (8.7.5/8.7.3) with ESMTP id PAA02959; Mon, 15 Sep 1997 15:50:12 -0700 (PDT) Received: from jason.xinetron.com (jason.xinetron.com [206.86.215.94]) by pop.xinetron.com (8.7.5/8.7.3) with ESMTP id PAA11736; Mon, 15 Sep 1997 15:48:26 -0700 (PDT) Message-ID: <341DBAF4.B55AAB13@xinetron.com> Date: Mon, 15 Sep 1997 15:47:16 -0700 From: Jason Liao Organization: Xinetron, Inc. X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-questions@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Failed to install on WD WDC33100H HDD X-Priority: 3 (Normal) References: <34195761.2FEBB195@xinetron.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Greetings, I tried the HDD again on an old 486 computer. It failed again. There is no LBA, no 32-bit access, no block access, no PIO mode 4 support on the 486 computer. The result is the same as on Pentium and Pentium PRO. On a Pentium system, DOS 6.22 can fdisk it without any problem. I didn't try DOS on the 486. I really believe that there are something special in the WDC33100H that the BIOS can support while FreeBSD 2.2.x can not. ---------------------------------------------------------- Jason Liao wrote: > Greetings, > > I tried to install FreeBSD 2.2.1 and 2.2.2 to a Western Digital > WDC33100H IDE HDD (3.1G). The kernel booted off the floppy and > detected > the correct model and size of the HDD. However, it hung after > displaying `/stand/sysinstall running as init on vty0'. Pressing > Alt+F3 > made the computer scream and only a hard reset could stop it. > Installing to other HDDs is OK. > > Then I hooked the WDC33100H as a slave disk to an existing FreeBSD > 2.2.1 > system. When I tried to fdisk, fdisk reported wrong geometry and the > kernel gave out lots of error messages: > wd1s1c: hard error reading fsbn 1wd1: status 59 err> > error 10 > > I connected the HDD back to a new system as the only HDD and booted > with > a kernel from a floppy diskette. I issued the following command: > dd if=/dev/rwd0c of=/dev/null bs=1b count=512 > I got the error message: > wd0s1c: wdstart: timeout waiting to give command reading fsbn 1wd0: > status 0 error 0 > wd0s1c: wdstart: timeout waiting to give command reading fsbn 1wd0: > status 0 error 1 > The error messages repeated and the system hung. > > Any hints? Your help is appreciated. > > P.S. I tried this HDD on different computers ( Pentium and Pentium > PRO), the same result. The HDD is OK in DOS environment. I heard of > someone else encountered this problem on WD HDDs about 1 or 2 months > ago. > -- > --------------------- > Jason Liao > > --------------------- -- --------------------- Jason Liao --------------------- From owner-freebsd-hardware Mon Sep 15 18:55:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA12271 for hardware-outgoing; Mon, 15 Sep 1997 18:55:25 -0700 (PDT) Received: from hobbes.saturn-tech.com (drussell@drussell.internode.net [198.161.228.154]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA12264; Mon, 15 Sep 1997 18:55:21 -0700 (PDT) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id TAA02676; Mon, 15 Sep 1997 19:55:21 -0600 (MDT) Date: Mon, 15 Sep 1997 19:55:20 -0600 (MDT) From: Doug Russell To: Jason Liao cc: freebsd-questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Failed to install on WD WDC33100H HDD In-Reply-To: <341DBAF4.B55AAB13@xinetron.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 15 Sep 1997, Jason Liao wrote: > I tried the HDD again on an old 486 computer. It failed again. There > is no LBA, no 32-bit access, no block access, no PIO mode 4 support on > the 486 computer. The result is the same as on Pentium and Pentium > PRO. On a Pentium system, DOS 6.22 can fdisk it without any problem. I > didn't try DOS on the 486. I really believe that there are something > special in the WDC33100H that the BIOS can support while FreeBSD 2.2.x > can not. In my hand I have a: MDL: WDAC33100-00H P/N: 99-004217-000 CCC: H9 4 MAR 97 DCM: CLABKVH Serial # is WT359 082 5920 If I plug it in to the machine beside me here, and pop in a 2.2.2-RELEASE boot disk, change flags to 0x80ff80ff on both wdc entries... wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0) , 32-bit, multi-block-16 wd0: 3020MB (6185088 sectors), 6136 cyls, 16 heads, 63 S/T, 512 B/S wdc1 at 0x170-0x177 irq 15 on isa wdc1: unit 0 (wd2) , 32-bit, multi-block-16 wd2: 3098MB (6346368 sectors), 6296 cyls, 16 heads, 63 S/T, 512 B/S It fdisks, disklabels, sysinstalls, no problem at all. What geometry did fdisk report to you? What did the probe report to you? What were the settings in the BIOS? Cylinders/Heads/Precompensation/LandingZone/Sectors/Mode The default here for the 33100 is 767/128/0/6135/63/LBA But, if I set it to 6136/16/65535/6135/63/NORMAL or 767/128/65535/6135/63/LARGE it works just fine as well. Either something is going very wrong in the bios/probe/fdisk procedure, or you have a flakey drive. Why it works corectly under DOS I do not know. Also, what motherboard and BIOS are you using? Later...... From owner-freebsd-hardware Mon Sep 15 20:15:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA16600 for hardware-outgoing; Mon, 15 Sep 1997 20:15:59 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA16595 for ; Mon, 15 Sep 1997 20:15:56 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id UAA05832; Mon, 15 Sep 1997 20:15:19 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199709160315.UAA05832@GndRsh.aac.dev.com> Subject: Re: Parity trouble with Asus mainboard In-Reply-To: from Doug Russell at "Sep 15, 97 12:47:13 pm" To: drussell@saturn-tech.com (Doug Russell) Date: Mon, 15 Sep 1997 20:15:19 -0700 (PDT) Cc: maddox@p-1.Eng.Sun.COM, beckmann@nacamar.net, 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-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > Are you sure these are true parity SIMMs? Some cheap SIMMs use "logic > > parity", which just fakes a parity bit for older MBs that require it. > > These will not work with ECC, and should be avoided in any case. > > Also, you describe these SIMMs as 2 x 32, 8 x 32 and so forth. In > > standard nomenclature, the "32" is the width of the SIMM, i.e., 32 bits. > > Parity SIMMs are 2 x 36, etc. > > > > Admittedly, this doesn't explain why the Gigabyte board worked, unless > > somehow the ECC was disabled behind your back. > > It is quite possible that the Gigabyte automatically disables ECC if you > don't actually have parity memory installed as an "idiot-proof" type > feature. I honestly don't know for sure, though. > Awards standard BIOS does this, Gigabyte uses Awards BIOS with very few modifications. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-hardware Mon Sep 15 21:13:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA19393 for hardware-outgoing; Mon, 15 Sep 1997 21:13:45 -0700 (PDT) Received: from hobbes.saturn-tech.com (drussell@drussell.internode.net [198.161.228.154]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA19378 for ; Mon, 15 Sep 1997 21:13:40 -0700 (PDT) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id WAA03101; Mon, 15 Sep 1997 22:13:42 -0600 (MDT) Date: Mon, 15 Sep 1997 22:13:42 -0600 (MDT) From: Doug Russell To: "Rodney W. Grimes" cc: maddox@p-1.Eng.Sun.COM, beckmann@nacamar.net, hardware@FreeBSD.ORG Subject: Re: Parity trouble with Asus mainboard In-Reply-To: <199709160315.UAA05832@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 15 Sep 1997, Rodney W. Grimes wrote: > > It is quite possible that the Gigabyte automatically disables ECC if you > > don't actually have parity memory installed as an "idiot-proof" type > > feature. I honestly don't know for sure, though. > > > Awards standard BIOS does this, Gigabyte uses Awards BIOS with very few > modifications. That is what I figured.... Later...... From owner-freebsd-hardware Tue Sep 16 01:06:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA05317 for hardware-outgoing; Tue, 16 Sep 1997 01:06:51 -0700 (PDT) Received: from news.nacamar.de (news.nacamar.de [194.162.162.210]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA05277 for ; Tue, 16 Sep 1997 01:06:38 -0700 (PDT) Received: from newsfeed (newsfeed.nacamar.de [194.162.162.196]) by news.nacamar.de (8.8.7/8.8.6) with SMTP id KAA12338; Tue, 16 Sep 1997 10:06:14 +0200 (CEST) Message-Id: <3.0.3.32.19970916100515.01432790@mail.nacamar.de> X-Sender: petzi@mail.nacamar.de X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Tue, 16 Sep 1997 10:05:15 +0200 To: Doug Russell , William Maddox From: Michael Beckmann Subject: Re: Parity trouble with Asus mainboard Cc: hardware@FreeBSD.ORG In-Reply-To: References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 12:47 15.09.97 -0600, Doug Russell wrote: > >> Are you sure these are true parity SIMMs? Some cheap SIMMs use "logic >> parity", which just fakes a parity bit for older MBs that require it. >> These will not work with ECC, and should be avoided in any case. >> Also, you describe these SIMMs as 2 x 32, 8 x 32 and so forth. In >> standard nomenclature, the "32" is the width of the SIMM, i.e., 32 bits. >> Parity SIMMs are 2 x 36, etc. >> >> Admittedly, this doesn't explain why the Gigabyte board worked, unless >> somehow the ECC was disabled behind your back. > >It is quite possible that the Gigabyte automatically disables ECC if you >don't actually have parity memory installed as an "idiot-proof" type >feature. I honestly don't know for sure, though. My Gigabyte 586 HX has three settings for parity: enabled, disabled and auto. I set it to enabled when I tried the parity SIMMs. Later I installed the normal SIMMs again and immediately got a parity error, so the parity check seems to work. Michael From owner-freebsd-hardware Tue Sep 16 01:18:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA08210 for hardware-outgoing; Tue, 16 Sep 1997 01:18:12 -0700 (PDT) Received: from bedroom.saturn-tech.com ([207.229.19.33]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA08193 for ; Tue, 16 Sep 1997 01:18:08 -0700 (PDT) Received: from localhost (drussell@localhost) by bedroom.saturn-tech.com (8.8.4/8.8.4) with SMTP id CAA22068; Mon, 16 Sep 1996 02:19:12 -0600 (MDT) X-Authentication-Warning: bedroom.saturn-tech.com: drussell owned process doing -bs Date: Mon, 16 Sep 1996 02:19:12 -0600 (MDT) From: Doug Russell To: Michael Beckmann cc: William Maddox , hardware@FreeBSD.ORG Subject: Re: Parity trouble with Asus mainboard In-Reply-To: <3.0.3.32.19970916100515.01432790@mail.nacamar.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, 16 Sep 1997, Michael Beckmann wrote: > >It is quite possible that the Gigabyte automatically disables ECC if you > >don't actually have parity memory installed as an "idiot-proof" type > >feature. I honestly don't know for sure, though. > > My Gigabyte 586 HX has three settings for parity: enabled, disabled and > auto. I set it to enabled when I tried the parity SIMMs. Later I installed > the normal SIMMs again and immediately got a parity error, so the parity > check seems to work. Hmmm... That shoots THAT theory, then... :) Later...... From owner-freebsd-hardware Tue Sep 16 04:15:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id EAA18487 for hardware-outgoing; Tue, 16 Sep 1997 04:15:17 -0700 (PDT) Received: from gatekeeper.acucobol.ie (gatekeeper.acucobol.ie [194.125.135.194]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id EAA18477; Tue, 16 Sep 1997 04:15:10 -0700 (PDT) Received: (from daemon@localhost) by gatekeeper.acucobol.ie (8.8.5/8.8.5) id MAA25170; Tue, 16 Sep 1997 12:12:18 +0100 (IST) Received: from guinness.acucobol.ie(194.125.135.195) by gatekeeper.acucobol.ie via smap (V2.0beta) id xma025158; Tue, 16 Sep 97 12:12:15 +0100 Received: from guinness (localhost [127.0.0.1]) by guinness.acucobol.ie (8.8.5/8.8.5) with ESMTP id MAA27536; Tue, 16 Sep 1997 12:15:38 +0100 (BST) Message-Id: <199709161115.MAA27536@guinness.acucobol.ie> From: "John McLaughlin" To: hardware@freebsd.org, scsi@freebsd.org Subject: Adaptec 1542CP on Compaq Prosignia VS problems Date: Tue, 16 Sep 1997 12:15:38 +0100 Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I'm running 2.2.2 on the above, which has started to intermittently give the following errors: aha0: Bus dropped at unexpected time aha0: Invalid bus phase/sequence sd0(aha0:0:0): UNIT ATTENTION asc:29,0 sd0(aha0:0:0): Power on, reset, or bus device reset occurred , retries:4 aha0: Invalid bus phase/sequence aha0: Invalid bus phase/sequence sd0(aha0:0:0): timed out sd0(aha0:0:0): UNIT ATTENTION asc:29,0 sd0(aha0:0:0): Power on, reset, or bus device reset occurred , retries:2 aha0: Invalid bus phase/sequence sd0(aha0:0:0): UNIT ATTENTION asc:29,0 sd0(aha0:0:0): Power on, reset, or bus device reset occurred , retries:4 And the dmesg output is: Copyright (c) 1992-1997 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.2-RELEASE #0: Wed Jul 23 11:40:00 IST 1997 root@holsten.acucobol.ie:/usr/src/sys/compile/HOLSTEN CPU: i486 DX2 (486-class CPU) Origin = "GenuineIntel" Id = 0x435 Stepping=5 Features=0x3 real memory = 16777216 (16384K bytes) avail memory = 14864384 (14516K bytes) eisa0: Probing for devices on the EISA bus eisa0:8 unknown device Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 not found at 0x280 sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 not found at 0x2f8 sio2: disabled, not probed. sio3: disabled, not probed. lpt0 at 0x3bc-0x3c3 irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in fd1: 1.2MB 5.25in aha0 at 0x330-0x333 irq 11 drq 5 on isa aha0 waiting for scsi devices to settle (aha0:0:0): "COMPAQ M2694ES-512 952B" type 0 fixed SCSI 2 sd0(aha0:0:0): Direct-Access 1001MB (2051000 512 byte sectors) (aha0:2:0): "TANDBERG TDC 3600 =08:" type 1 removable SCSI 2 st0(aha0:2:0): Sequential-Access density code 0x0, drive empty (aha0:4:0): "ARCHIVE Python 27871-XXX 4.BG" type 1 removable SCSI 2 st1(aha0:4:0): Sequential-Access density code 0x13, drive empty lnc0 at 0x8800-0x8817 irq 10 drq 0 on eisa slot 8 lnc0: PCnet-32 VL-Bus address 00:80:5f:18:d9:9c npx0 flags 0x1 on motherboard npx0: INT 16 interface It was working fine for about 6 weeks after the install, before the started turning up regularly, so I'd guess it's either a problem with the controller, or the disk. Is it possibly a problem with the setup on the card, or possibly the fact that it's all sitting inside a Compaq? Any suggestions much appreciated. Thanks, John ---------------------------------------------------------------------- John McLaughlin | Acucobol Ireland Ltd. IS Manager, Europe | South Co. Business Park | Dublin 18, Ireland. e-Mail: jmcl@Acucobol.IE | Phone: +353 1 294-0967 John.McLaughlin@Acucobol.IE | Fax: +353 1 294-0969 ---------------------------------------------------------------------- From owner-freebsd-hardware Tue Sep 16 08:15:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA29378 for hardware-outgoing; Tue, 16 Sep 1997 08:15:25 -0700 (PDT) Received: from www.xinetron.com (www.xinetron.com [206.86.215.68]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA29355; Tue, 16 Sep 1997 08:15:20 -0700 (PDT) Received: from pop.xinetron.com (pop.xinetron.com [206.86.215.82]) by www.xinetron.com (8.7.5/8.7.3) with ESMTP id IAA00757; Tue, 16 Sep 1997 08:15:10 -0700 (PDT) Received: from jason.xinetron.com (jason.xinetron.com [206.86.215.94]) by pop.xinetron.com (8.7.5/8.7.3) with ESMTP id IAA19688; Tue, 16 Sep 1997 08:15:05 -0700 (PDT) Message-ID: <341EA240.B211E225@xinetron.com> Date: Tue, 16 Sep 1997 08:14:08 -0700 From: Jason Liao Organization: Xinetron, Inc. X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: Doug Russell CC: freebsd-questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Failed to install on WD WDC33100H HDD X-Priority: 3 (Normal) References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Doug Russell wrote: > On Mon, 15 Sep 1997, Jason Liao wrote: > > > I tried the HDD again on an old 486 computer. It failed again. > There > > is no LBA, no 32-bit access, no block access, no PIO mode 4 support > on > > the 486 computer. The result is the same as on Pentium and Pentium > > PRO. On a Pentium system, DOS 6.22 can fdisk it without any > problem. I > > didn't try DOS on the 486. I really believe that there are > something > > special in the WDC33100H that the BIOS can support while FreeBSD > 2.2.x > > can not. > > > > In my hand I have a: > > MDL: WDAC33100-00H > P/N: 99-004217-000 > CCC: H9 4 MAR 97 > DCM: CLABKVH > > Serial # is WT359 082 5920 > > If I plug it in to the machine beside me here, and pop in a > 2.2.2-RELEASE > boot disk, change flags to 0x80ff80ff on both wdc entries... > > wdc0 at 0x1f0-0x1f7 irq 14 on isa > wdc0: unit 0 (wd0) , 32-bit, multi-block-16 > wd0: 3020MB (6185088 sectors), 6136 cyls, 16 heads, 63 S/T, 512 B/S > wdc1 at 0x170-0x177 irq 15 on isa > wdc1: unit 0 (wd2) , 32-bit, multi-block-16 > wd2: 3098MB (6346368 sectors), 6296 cyls, 16 heads, 63 S/T, 512 B/S > > It fdisks, disklabels, sysinstalls, no problem at all. > > What geometry did fdisk report to you? FreeBSD fdisk reported some very large numbers and negative numbers for the cyls, heads and sectors, along with the kernel error messages. DOS fdisk reported 6136 x 16 x 63 = 504MB. > What did the probe report to you? The kernel proble reported the same parameters as your disk. I tried flags 0x80ff80ff and 0x0 and got the same result. boot: -v looked normal, no addtional message when probing the HDD. > What were the settings in the BIOS? 6136x16x63 NORMAL. ( I also tried LBA on/off, 32-bit access on/off, block reading on/off, PIO mode 0/3/4 on Pentium and P Pro). The 486 computer doesn't have these settings. It also failed > Cylinders/Heads/Precompensation/LandingZone/Sectors/Mode > The default here for the 33100 is 767/128/0/6135/63/LBA > But, if I set it to 6136/16/65535/6135/63/NORMAL or > 767/128/65535/6135/63/LARGE it works just fine as well. > > Either something is going very wrong in the bios/probe/fdisk > procedure, or > you have a flakey drive. Why it works corectly under DOS I do not > know. > > Also, what motherboard and BIOS are you using? A Super dual Pentium PRO w/ one CPU, AMI bios. A Wintec (Edom) Pentium, Award BIOS and a Xinetron 486, AMI bios. Thank you for your comments. The hard disk is no in my hands now so I can not do further experiments on it :-( > > > Later...... --Jason --------------------- Jason Liao --------------------- From owner-freebsd-hardware Tue Sep 16 14:31:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA20907 for hardware-outgoing; Tue, 16 Sep 1997 14:31:55 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA20898 for ; Tue, 16 Sep 1997 14:31:49 -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 XAA04220 for ; Tue, 16 Sep 1997 23:31:42 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id XAA10285 for freebsd-hardware@FreeBSD.ORG; Tue, 16 Sep 1997 23:31:26 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-2.10/nospam) id WAA01514; Tue, 16 Sep 1997 22:52:24 +0200 (CEST) Received: (from uucp@localhost) by keltia.freenix.fr (8.8.7/keltia-uucp-2.10/nospam) with UUCP id GAA12186 for roberto@keltia.freenix.fr; Fri, 12 Sep 1997 06:33:57 +0200 (CEST) Received: from silvia.HIP.Berkeley.EDU (ala-ca11-23.ix.netcom.com [199.35.209.183]) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with ESMTP id GAA18925 for ; Fri, 12 Sep 1997 06:32:00 +0200 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id VAA28321; Thu, 11 Sep 1997 21:31:50 -0700 (PDT) Date: Thu, 11 Sep 1997 21:31:50 -0700 (PDT) Message-Id: <19979120431.VAA28321@silvia.HIP.Berkeley.EDU> To: roberto@keltia.freenix.fr CC: freebsd-hardware@FreeBSD.ORG In-reply-to: <19970911221642.45617@keltia.freenix.fr> (message from Ollivier Robert on Thu, 11 Sep 1997 22:16:42 +0200) Subject: Re: IBM/Cyrix PR200+ From: asami@cs.berkeley.edu (Satoshi Asami) Status: RO X-Status: A Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * > My too -- however, i suppose that Pentium-oriented copy/zero block * > procedures don't work. * * Oh they do but much slower then the regular ones. * * Always use "flags 0x7" for npx0 in your config. file for both Cyrix and * AMD's processors. Speaking of which, can anyone with an *MX processor check the gus mmx extension PR (filed under "gnu", I think) and try and see if copying through the mmx registers instead of FP would be faster for some of the CPU's? Satoshi From owner-freebsd-hardware Tue Sep 16 14:31:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA20920 for hardware-outgoing; Tue, 16 Sep 1997 14:31:58 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA20901 for ; Tue, 16 Sep 1997 14:31:52 -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 XAA04217 for ; Tue, 16 Sep 1997 23:31:42 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id XAA10287 for freebsd-hardware@FreeBSD.ORG; Tue, 16 Sep 1997 23:31:26 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-2.10/nospam) id WAA01554; Tue, 16 Sep 1997 22:55:29 +0200 (CEST) Received: (from uucp@localhost) by keltia.freenix.fr (8.8.7/keltia-uucp-2.10/nospam) with UUCP id GAA12186 for roberto@keltia.freenix.fr; Fri, 12 Sep 1997 06:33:57 +0200 (CEST) Received: from silvia.HIP.Berkeley.EDU (ala-ca11-23.ix.netcom.com [199.35.209.183]) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with ESMTP id GAA18925 for ; Fri, 12 Sep 1997 06:32:00 +0200 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id VAA28321; Thu, 11 Sep 1997 21:31:50 -0700 (PDT) Date: Thu, 11 Sep 1997 21:31:50 -0700 (PDT) Message-Id: <1979120431.VAA28321@silvia.HIP.Berkeley.EDU> To: roberto@keltia.freenix.fr CC: freebsd-hardware@FreeBSD.ORG In-reply-to: <19970911221642.45617@keltia.freenix.fr> (message from Ollivier Robert on Thu, 11 Sep 1997 22:16:42 +0200) Subject: Re: IBM/Cyrix PR200+ From: asami@cs.berkeley.edu (Satoshi Asami) Status: RO X-Status: A Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * > My too -- however, i suppose that Pentium-oriented copy/zero block * > procedures don't work. * * Oh they do but much slower then the regular ones. * * Always use "flags 0x7" for npx0 in your config. file for both Cyrix and * AMD's processors. Speaking of which, can anyone with an *MX processor check the gus mmx extension PR (filed under "gnu", I think) and try and see if copying through the mmx registers instead of FP would be faster for some of the CPU's? Satoshi From owner-freebsd-hardware Tue Sep 16 14:33:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA21083 for hardware-outgoing; Tue, 16 Sep 1997 14:33:08 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA20931 for ; Tue, 16 Sep 1997 14:32:00 -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 XAA04223; Tue, 16 Sep 1997 23:31:42 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id XAA10282; Tue, 16 Sep 1997 23:31:05 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-2.10/nospam) id WAA01484; Tue, 16 Sep 1997 22:49:54 +0200 (CEST) Received: (from uucp@localhost) by keltia.freenix.fr (8.8.7/keltia-uucp-2.10/nospam) with UUCP id XAA20827 for roberto@keltia.freenix.fr; Sat, 13 Sep 1997 23:31:47 +0200 (CEST) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with ESMTP id TAA12897 for ; Sat, 13 Sep 1997 19:45:34 +0200 Received: (from jfarmer@localhost) by sabre.goldsword.com (8.7.5/8.7.3) id NAA09633; Sat, 13 Sep 1997 13:48:44 -0400 (EDT) Date: Sat, 13 Sep 1997 13:48:44 -0400 (EDT) From: "John T. Farmer" Message-Id: <99709131748.NAA09633@sabre.goldsword.com> To: hardware@FreeBSD.ORG, roberto@keltia.freenix.fr Subject: Re: Fwd: K6 Linux Re-Compile Issue Cc: jfarmer@goldsword.com Status: RO X-Status: A Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 12 Sep 1997 18:58:12 +0200 Ollivier Robert said: >According to Mike Burgett: >> FWIW, I just got the following from AMD tech support, regarding the >> problems I had reported with my initial K6 and running 'make world' > >I also got news from AMD. They told me they will swap my K6 for a new and >fixed one in the near future (3 or 4 weeks). More details later. >-- When you get yours & verify that the problem is fixed, _please_ forward details such as rev. numbers & stepping so that we can be sure to get the new ones... John (Who has more than once had a distributor pass off old stock as new...) ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee dial-in (423)470-9953 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting From owner-freebsd-hardware Tue Sep 16 14:47:42 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA22025 for hardware-outgoing; Tue, 16 Sep 1997 14:47:42 -0700 (PDT) Received: from mexico.brainstorm.eu.org (root@mexico.brainstorm.fr [193.56.58.253]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA22018 for ; Tue, 16 Sep 1997 14:47:32 -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 XAA04214 for ; Tue, 16 Sep 1997 23:31:38 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id XAA10286 for freebsd-hardware@FreeBSD.ORG; Tue, 16 Sep 1997 23:31:26 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.7/keltia-2.10/nospam) id WAA01573; Tue, 16 Sep 1997 22:56:29 +0200 (CEST) Received: (from uucp@localhost) by keltia.freenix.fr (8.8.7/keltia-uucp-2.10/nospam) with UUCP id GAA12186 for roberto@keltia.freenix.fr; Fri, 12 Sep 1997 06:33:57 +0200 (CEST) Received: from silvia.HIP.Berkeley.EDU (ala-ca11-23.ix.netcom.com [199.35.209.183]) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with ESMTP id GAA18925 for ; Fri, 12 Sep 1997 06:32:00 +0200 Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id VAA28321; Thu, 11 Sep 1997 21:31:50 -0700 (PDT) Date: Thu, 11 Sep 1997 21:31:50 -0700 (PDT) Message-Id: <179120431.VAA28321@silvia.HIP.Berkeley.EDU> To: roberto@keltia.freenix.fr CC: freebsd-hardware@FreeBSD.ORG In-reply-to: <19970911221642.45617@keltia.freenix.fr> (message from Ollivier Robert on Thu, 11 Sep 1997 22:16:42 +0200) Subject: Re: IBM/Cyrix PR200+ From: asami@cs.berkeley.edu (Satoshi Asami) Status: RO X-Status: A Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * > My too -- however, i suppose that Pentium-oriented copy/zero block * > procedures don't work. * * Oh they do but much slower then the regular ones. * * Always use "flags 0x7" for npx0 in your config. file for both Cyrix and * AMD's processors. Speaking of which, can anyone with an *MX processor check the gus mmx extension PR (filed under "gnu", I think) and try and see if copying through the mmx registers instead of FP would be faster for some of the CPU's? Satoshi From owner-freebsd-hardware Tue Sep 16 17:18:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA29483 for hardware-outgoing; Tue, 16 Sep 1997 17:18:54 -0700 (PDT) Received: from austin.cs.unc.edu (austin.cs.unc.edu [152.2.128.87]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA29477 for ; Tue, 16 Sep 1997 17:18:49 -0700 (PDT) Received: from buzzard.cs.unc.edu by austin.cs.unc.edu (8.6.10/UNC_10_05_96) id UAA05868; Tue, 16 Sep 1997 20:18:46 -0400 From: Jan Martin Borgersen Received: by buzzard.cs.unc.edu (8.6.10/UNC_06_21_94) id UAA19721; Tue, 16 Sep 1997 20:18:45 -0400 Message-Id: <199709170018.UAA19721@buzzard.cs.unc.edu> Subject: 10Mbit Ethernet Adapter Performance To: freebsd-hardware@freebsd.org Date: Tue, 16 Sep 1997 20:18:45 -0400 (EDT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Can anyone point me to any performance evaluations of 10Mb ISA Ethernet adapters or their device drivers? I'm getting some really interesting numbers: On an isolated, 100Mb switched Ethernet hub with no other network traffic, I'm running ttcp to perform tcp and udp blasts between several 486-66 class machines with ISA 10Mb Ethernet adapters. When machines with generic IBM cards (looks like a NS 83905A chip) thrown into NE2000 emulation and using the ed0 driver are transmitting, I'm seeing network throughputs on the order of 8300 bps. When machines with 3Com 3C509 Etherlink III's using the ep0 driver are transmitting, I'm seeing network throughputs on the order of 3500 bps. Interestingly, the machine I have with a PCI 3C590 3Com card using the vx0 driver is transmitting at about 7700 bps -- still significantly SLOWER than the NE2000 emulated cards!!!! I've swapped cards among machines -- the bad numbers follow the 3C509's and ep0 drivers, and seem to be much more a function of transmitter than receiver. What happened to FreeBSD's 3Com drivers????? (Or am I not configuring something for optimization?) -j From owner-freebsd-hardware Tue Sep 16 18:00:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA01851 for hardware-outgoing; Tue, 16 Sep 1997 18:00:21 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA01824 for ; Tue, 16 Sep 1997 18:00:14 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id KAA01146; Wed, 17 Sep 1997 10:29:53 +0930 (CST) Message-ID: <19970917102953.15249@lemis.com> Date: Wed, 17 Sep 1997 10:29:53 +0930 From: Greg Lehey To: Jan Martin Borgersen Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: 10Mbit Ethernet Adapter Performance References: <199709170018.UAA19721@buzzard.cs.unc.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199709170018.UAA19721@buzzard.cs.unc.edu>; from Jan Martin Borgersen on Tue, Sep 16, 1997 at 08:18:45PM -0400 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, Sep 16, 1997 at 08:18:45PM -0400, Jan Martin Borgersen wrote: > > Can anyone point me to any performance evaluations > of 10Mb ISA Ethernet adapters or their device drivers? > > I'm getting some really interesting numbers: > > On an isolated, 100Mb switched Ethernet hub with no > other network traffic, I'm running ttcp to perform > tcp and udp blasts between several 486-66 class > machines with ISA 10Mb Ethernet adapters. > > When machines with generic IBM cards (looks like > a NS 83905A chip) thrown into NE2000 emulation and > using the ed0 driver are transmitting, I'm seeing > network throughputs on the order of 8300 bps. I hope these are Bytes per second, and not bits per second. Not that it makes much difference with those rates. > When machines with 3Com 3C509 Etherlink III's using > the ep0 driver are transmitting, I'm seeing network > throughputs on the order of 3500 bps. You could always install a modem... > Interestingly, the machine I have with a PCI 3C590 > 3Com card using the vx0 driver is transmitting > at about 7700 bps -- still significantly SLOWER than > the NE2000 emulated cards!!!! > > I've swapped cards among machines -- the bad numbers > follow the 3C509's and ep0 drivers, and seem to be > much more a function of transmitter than receiver. > > What happened to FreeBSD's 3Com drivers????? (Or am > I not configuring something for optimization?) You can be pretty sure that this is a network configuration problem of some nature. Some boards are faster than others, of course, but using reasonably fast machines, an ftp transfer should give you throughputs in the order of 1 MB/s. Here's an example of transfers I did just now between a 486DX/2-66 with a WD8013EPC and a P133 with a 3C509: 1242318 bytes received in 2.39 seconds (507.83 KB/s) 1242318 bytes received in 1.26 seconds (963.66 KB/s) 1242318 bytes received in 1.17 seconds (1.01 MB/s) 1242318 bytes received in 1.12 seconds (1.06 MB/s) 1242318 bytes received in 1.17 seconds (1.01 MB/s) You can assume the slow transfer time in the first attempt was due to the slowness of the 486 machine reading in the file; after that, the data was in cache, so we're measuring the transfer speed. So, what's wrong with your network? Check: 1. The output of netstat -in. It should look something like: Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ep0 1500 00.a0.24.37.0d.2b 231549 2 244717 4 0 ep0 1500 255.255.255&0 192.109.197.137 231549 2 244717 4 0 If the network is idle, you shouldn't have any collisions. Even on a heavily loaded network, you'll be in trouble with more than 1% collisions. 2. What's going on on the net? Use tcpdump to see if you're getting lots of retransmissions. 3. Normally, I'd be inclined to say "check the boards", but if you're getting the same performance out of a number of different boards, they're unlikely to be the problem. In any case, the problem isn't FreeBSD. If you look at your net, you'll probably find something. Greg From owner-freebsd-hardware Tue Sep 16 18:26:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA02972 for hardware-outgoing; Tue, 16 Sep 1997 18:26:40 -0700 (PDT) Received: from austin.cs.unc.edu (austin.cs.unc.edu [152.2.128.87]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA02967 for ; Tue, 16 Sep 1997 18:26:32 -0700 (PDT) Received: from buzzard.cs.unc.edu by austin.cs.unc.edu (8.6.10/UNC_10_05_96) id VAA08451; Tue, 16 Sep 1997 21:26:18 -0400 From: Jan Martin Borgersen Received: by buzzard.cs.unc.edu (8.6.10/UNC_06_21_94) id VAA20127; Tue, 16 Sep 1997 21:26:17 -0400 Message-Id: <199709170126.VAA20127@buzzard.cs.unc.edu> Subject: 10Mbit Ethernet Adapter Performance (fwd) To: freebsd-hardware@freebsd.org Date: Tue, 16 Sep 1997 21:26:17 -0400 (EDT) X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > 8300 bps ... 3500 bps ... I'm sorry. These are in kbps, making them roughly 1.0 MB/s and .44 MB/s. -j From owner-freebsd-hardware Tue Sep 16 18:42:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA03973 for hardware-outgoing; Tue, 16 Sep 1997 18:42:47 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id SAA03968 for ; Tue, 16 Sep 1997 18:42:42 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0xB93W-0005M1-00; Tue, 16 Sep 1997 18:37:26 -0700 Date: Tue, 16 Sep 1997 18:37:26 -0700 (PDT) From: Tom To: Jan Martin Borgersen cc: freebsd-hardware@freebsd.org Subject: Re: 10Mbit Ethernet Adapter Performance In-Reply-To: <199709170018.UAA19721@buzzard.cs.unc.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Tue, 16 Sep 1997, Jan Martin Borgersen wrote: > Can anyone point me to any performance evaluations > of 10Mb ISA Ethernet adapters or their device drivers? > > I'm getting some really interesting numbers: > > On an isolated, 100Mb switched Ethernet hub with no > other network traffic, I'm running ttcp to perform > tcp and udp blasts between several 486-66 class > machines with ISA 10Mb Ethernet adapters. > > When machines with generic IBM cards (looks like > a NS 83905A chip) thrown into NE2000 emulation and > using the ed0 driver are transmitting, I'm seeing > network throughputs on the order of 8300 bps. > > When machines with 3Com 3C509 Etherlink III's using > the ep0 driver are transmitting, I'm seeing network > throughputs on the order of 3500 bps. > > Interestingly, the machine I have with a PCI 3C590 > 3Com card using the vx0 driver is transmitting > at about 7700 bps -- still significantly SLOWER than > the NE2000 emulated cards!!!! > > I've swapped cards among machines -- the bad numbers > follow the 3C509's and ep0 drivers, and seem to be > much more a function of transmitter than receiver. > > What happened to FreeBSD's 3Com drivers????? (Or am > I not configuring something for optimization?) The 3COM drivers never did work that well. This is not new. It doesn't help that some of the 3COM have very limited buffer capacity (4k I belive). The vx driver als uses PIO, instead of dma. See man pages for vx, and ep. Also, to me, "bps" means bits per second, so all your number look very low to me ("b" bit, "B" byte). > -j > > Tom From owner-freebsd-hardware Tue Sep 16 18:49:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA04492 for hardware-outgoing; Tue, 16 Sep 1997 18:49:45 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA04483 for ; Tue, 16 Sep 1997 18:49:40 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id SAA24588; Tue, 16 Sep 1997 18:52:13 -0700 (PDT) Message-Id: <199709170152.SAA24588@implode.root.com> To: Jan Martin Borgersen cc: freebsd-hardware@FreeBSD.ORG Subject: Re: 10Mbit Ethernet Adapter Performance In-reply-to: Your message of "Tue, 16 Sep 1997 20:18:45 EDT." <199709170018.UAA19721@buzzard.cs.unc.edu> From: David Greenman Reply-To: dg@root.com Date: Tue, 16 Sep 1997 18:52:13 -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Can anyone point me to any performance evaluations >of 10Mb ISA Ethernet adapters or their device drivers? > >I'm getting some really interesting numbers: > >On an isolated, 100Mb switched Ethernet hub with no >other network traffic, I'm running ttcp to perform >tcp and udp blasts between several 486-66 class >machines with ISA 10Mb Ethernet adapters. > >When machines with generic IBM cards (looks like >a NS 83905A chip) thrown into NE2000 emulation and >using the ed0 driver are transmitting, I'm seeing >network throughputs on the order of 8300 bps. 8300? You mean 8.3Kbps? If that is really the case, then you've got a serious problem. Perhaps your switch is configured for full duplex? Or perhaps you have a bad cable? You should be seeing > 8Mbps. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hardware Wed Sep 17 15:47:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA16463 for hardware-outgoing; Wed, 17 Sep 1997 15:47:36 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA16449 for ; Wed, 17 Sep 1997 15:47:22 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.8.7/8.6.12) with SMTP id SAA26303 for ; Wed, 17 Sep 1997 18:47:19 -0400 (EDT) Date: Wed, 17 Sep 1997 18:47:17 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: FreeBSD-hardware@freebsd.org Subject: SCSI3 cables Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Anyone know of a good place to get 68 pin wide scsi cables? I have some new Fujitsu drives, a new NCR 875 controller, and I don't have any cables to hook them up. I've done some netsearching, and found there's an incredible range of prices ... if anyone knows where inexpensive and good might intersect, I'd appreciate it. Thanks. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hardware Wed Sep 17 16:26:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA18170 for hardware-outgoing; Wed, 17 Sep 1997 16:26:51 -0700 (PDT) Received: from lariat.lariat.org (ppp0.lariat.org@[129.72.251.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA18150 for ; Wed, 17 Sep 1997 16:26:46 -0700 (PDT) Received: from solo ([129.72.251.10] (may be forged)) by lariat.lariat.org (8.8.6/8.8.6) with SMTP id RAA15229; Wed, 17 Sep 1997 17:22:21 -0600 (MDT) Message-Id: <3.0.3.32.19970917172634.00876190@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 17 Sep 1997 17:26:34 -0600 To: chuckr@glue.umd.edu, FreeBSD-hardware@FreeBSD.ORG From: Brett Glass Subject: Re: SCSI3 cables In-Reply-To: <88256515.0080F659.00@IWNS2.infoworld.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Granite Digital is the best, and is not that expensive. --Brett At 06:47 PM 9/17/97 -0400, chuckr@glue.umd.edu wrote: > > > >Anyone know of a good place to get 68 pin wide scsi cables? I have some >new Fujitsu drives, a new NCR 875 controller, and I don't have any cables >to hook them up. I've done some netsearching, and found there's an >incredible range of prices ... if anyone knows where inexpensive and good >might intersect, I'd appreciate it. >Thanks. >----------------------------+---------------------------------------------- >- >Chuck Robey | Interests include any kind of voice or data >chuckr@eng.umd.edu | communications topic, C programming, and >Unix. >213 Lakeside Drive Apt T-1 | >Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD >(301) 220-2114 | version 3.0 current -- and great FUN! >----------------------------+---------------------------------------------- >- > > > > From owner-freebsd-hardware Wed Sep 17 16:45:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA19217 for hardware-outgoing; Wed, 17 Sep 1997 16:45:20 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA19212 for ; Wed, 17 Sep 1997 16:45:16 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id QAA09012; Wed, 17 Sep 1997 16:44:43 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199709172344.QAA09012@GndRsh.aac.dev.com> Subject: Re: SCSI3 cables In-Reply-To: from Chuck Robey at "Sep 17, 97 06:47:17 pm" To: chuckr@glue.umd.edu (Chuck Robey) Date: Wed, 17 Sep 1997 16:44:43 -0700 (PDT) Cc: FreeBSD-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-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Anyone know of a good place to get 68 pin wide scsi cables? I have some > new Fujitsu drives, a new NCR 875 controller, and I don't have any cables > to hook them up. I've done some netsearching, and found there's an > incredible range of prices ... if anyone knows where inexpensive and good > might intersect, I'd appreciate it. Did you search the freebsd-scsi mail archives, www.scsipro.com has been pinted to at least a half dozen times... -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-hardware Wed Sep 17 16:46:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA19262 for hardware-outgoing; Wed, 17 Sep 1997 16:46:00 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA19247 for ; Wed, 17 Sep 1997 16:45:41 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.8.7/8.6.12) with SMTP id TAA27918; Wed, 17 Sep 1997 19:45:23 -0400 (EDT) Date: Wed, 17 Sep 1997 19:45:21 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Brett Glass cc: FreeBSD-hardware@FreeBSD.ORG Subject: Re: SCSI3 cables In-Reply-To: <3.0.3.32.19970917172634.00876190@mail.lariat.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 17 Sep 1997, Brett Glass wrote: > Granite Digital is the best, and is not that expensive. I just checked their website, and their most inexpensive 3 foot 68 pin cable was $149. That's the single most expensive cable I've yet found, and costs quite a bit more than the controller. I didn't even look at their more expensive, sliver and gold cables. You may be right on their quality, but isn't that price a little overkill? Or does SCSI wide really need that kind of care? > > --Brett > > At 06:47 PM 9/17/97 -0400, chuckr@glue.umd.edu wrote: > > > > > > > > >Anyone know of a good place to get 68 pin wide scsi cables? I have some > >new Fujitsu drives, a new NCR 875 controller, and I don't have any cables > >to hook them up. I've done some netsearching, and found there's an > >incredible range of prices ... if anyone knows where inexpensive and good > >might intersect, I'd appreciate it. > >Thanks. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hardware Wed Sep 17 17:01:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA19989 for hardware-outgoing; Wed, 17 Sep 1997 17:01:19 -0700 (PDT) Received: from lariat.lariat.org (ppp0.lariat.org@[129.72.251.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA19980 for ; Wed, 17 Sep 1997 17:01:16 -0700 (PDT) Received: from solo ([129.72.251.10] (may be forged)) by lariat.lariat.org (8.8.6/8.8.6) with SMTP id RAA15705; Wed, 17 Sep 1997 17:56:49 -0600 (MDT) Message-Id: <3.0.3.32.19970917180101.0089d5f0@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 17 Sep 1997 18:01:01 -0600 To: Chuck Robey From: Brett Glass Subject: Re: SCSI3 cables Cc: FreeBSD-hardware@FreeBSD.ORG In-Reply-To: References: <3.0.3.32.19970917172634.00876190@mail.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 07:45 PM 9/17/97 -0400, Chuck Robey wrote: >On Wed, 17 Sep 1997, Brett Glass wrote: > >> Granite Digital is the best, and is not that expensive. > >I just checked their website, and their most inexpensive 3 foot 68 pin >cable was $149. That's the single most expensive cable I've yet found, >and costs quite a bit more than the controller. That's full list, direct from the manufacturer. The cables cost a whole lot less when you actually buy them at a competitive retailer. Engineers truly swear by these cables; they're great stuff. --Brett From owner-freebsd-hardware Wed Sep 17 17:04:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA20225 for hardware-outgoing; Wed, 17 Sep 1997 17:04:58 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA20216 for ; Wed, 17 Sep 1997 17:04:51 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0xBU0R-00065N-00; Wed, 17 Sep 1997 16:59:39 -0700 Date: Wed, 17 Sep 1997 16:59:38 -0700 (PDT) From: Tom To: Chuck Robey cc: FreeBSD-hardware@freebsd.org Subject: Re: SCSI3 cables In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 17 Sep 1997, Chuck Robey wrote: > Anyone know of a good place to get 68 pin wide scsi cables? I have some > new Fujitsu drives, a new NCR 875 controller, and I don't have any cables > to hook them up. I've done some netsearching, and found there's an > incredible range of prices ... if anyone knows where inexpensive and good > might intersect, I'd appreciate it. Granite Digital www.scsipro.com. They only sell SCSI acessories. They also make a cool SCSI extender box, that can double the SCSI cable distance. They also have some neat active terminators with status LEDs on them. > Thanks. > > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@eng.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > (301) 220-2114 | version 3.0 current -- and great FUN! > ----------------------------+----------------------------------------------- > > > Tom From owner-freebsd-hardware Wed Sep 17 17:05:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA20304 for hardware-outgoing; Wed, 17 Sep 1997 17:05:33 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA20287 for ; Wed, 17 Sep 1997 17:05:26 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.8.7/8.6.12) with SMTP id UAA29405; Wed, 17 Sep 1997 20:04:57 -0400 (EDT) Date: Wed, 17 Sep 1997 20:04:56 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: "Rodney W. Grimes" cc: FreeBSD-hardware@FreeBSD.ORG Subject: Re: SCSI3 cables In-Reply-To: <199709172344.QAA09012@GndRsh.aac.dev.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 17 Sep 1997, Rodney W. Grimes wrote: > > Anyone know of a good place to get 68 pin wide scsi cables? I have some > > new Fujitsu drives, a new NCR 875 controller, and I don't have any cables > > to hook them up. I've done some netsearching, and found there's an > > incredible range of prices ... if anyone knows where inexpensive and good > > might intersect, I'd appreciate it. > > Did you search the freebsd-scsi mail archives, www.scsipro.com has been > pinted to at least a half dozen times... Thanks, Rod. I misidentified their numbers a minute ago ... they look good, so I'll order tomorrow. > > > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation, Inc. Reliable computers for FreeBSD > > ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hardware Wed Sep 17 17:42:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA22920 for hardware-outgoing; Wed, 17 Sep 1997 17:42:18 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA22909 for ; Wed, 17 Sep 1997 17:42:14 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0xBUab-00066n-00; Wed, 17 Sep 1997 17:37:01 -0700 Date: Wed, 17 Sep 1997 17:37:00 -0700 (PDT) From: Tom To: Chuck Robey cc: Brett Glass , FreeBSD-hardware@freebsd.org Subject: Re: SCSI3 cables In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 17 Sep 1997, Chuck Robey wrote: > On Wed, 17 Sep 1997, Brett Glass wrote: > > > Granite Digital is the best, and is not that expensive. > > I just checked their website, and their most inexpensive 3 foot 68 pin > cable was $149. That's the single most expensive cable I've yet found, > and costs quite a bit more than the controller. I didn't even look at > their more expensive, sliver and gold cables. You may be right on their > quality, but isn't that price a little overkill? Or does SCSI wide really > need that kind of care? SCSI wide does not require that kind of "care", nor does SCSI-II, but ultra SCSI does. The clock rate is doubled, and cable quality is important. For me, buying a $150 cable for a $15K server is really good deal, and much better than pissing around for days getting rid of SCSI errors... but not everyone builds $15K boxes. Tom From owner-freebsd-hardware Wed Sep 17 19:00:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA26630 for hardware-outgoing; Wed, 17 Sep 1997 19:00:52 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA26621 for ; Wed, 17 Sep 1997 19:00:49 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.8.7/8.6.12) with SMTP id VAA06754; Wed, 17 Sep 1997 21:59:57 -0400 (EDT) Date: Wed, 17 Sep 1997 21:59:55 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Tom cc: Brett Glass , FreeBSD-hardware@FreeBSD.ORG Subject: Re: SCSI3 cables In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, 17 Sep 1997, Tom wrote: > > On Wed, 17 Sep 1997, Chuck Robey wrote: > > > On Wed, 17 Sep 1997, Brett Glass wrote: > > > > > Granite Digital is the best, and is not that expensive. > > > > I just checked their website, and their most inexpensive 3 foot 68 pin > > cable was $149. That's the single most expensive cable I've yet found, > > and costs quite a bit more than the controller. I didn't even look at > > their more expensive, sliver and gold cables. You may be right on their > > quality, but isn't that price a little overkill? Or does SCSI wide really > > need that kind of care? > > SCSI wide does not require that kind of "care", nor does SCSI-II, but > ultra SCSI does. The clock rate is doubled, and cable quality is > important. > > For me, buying a $150 cable for a $15K server is really good deal, and > much better than pissing around for days getting rid of SCSI errors... but > not everyone builds $15K boxes. I was going to wait until I located a discounter to post this, but maybe I shouldn't wait. I had the wrong web page, I was looking at the one for scsi external cabless. The internal cable I think I'll get (as soon as I find a discount place that sells Granite Digital, I've been told they exist) will only cost 86 bucks, full price. It's a lot for the application (which isn't a 15K server) but not as outrageous as I thought, for good quality. ----------------------------+----------------------------------------------- Chuck Robey | Interests include any kind of voice or data chuckr@eng.umd.edu | communications topic, C programming, and Unix. 213 Lakeside Drive Apt T-1 | Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD (301) 220-2114 | version 3.0 current -- and great FUN! ----------------------------+----------------------------------------------- From owner-freebsd-hardware Wed Sep 17 19:26:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA27914 for hardware-outgoing; Wed, 17 Sep 1997 19:26:29 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id TAA27909 for ; Wed, 17 Sep 1997 19:26:24 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0xBWDQ-0006Ai-00; Wed, 17 Sep 1997 19:21:12 -0700 Date: Wed, 17 Sep 1997 19:21:11 -0700 (PDT) From: Tom To: Chuck Robey cc: Brett Glass , FreeBSD-hardware@freebsd.org Subject: Re: SCSI3 cables In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 17 Sep 1997, Chuck Robey wrote: > > > I just checked their website, and their most inexpensive 3 foot 68 pin > > > cable was $149. That's the single most expensive cable I've yet found, > > > and costs quite a bit more than the controller. I didn't even look at > > > their more expensive, sliver and gold cables. You may be right on their > > > quality, but isn't that price a little overkill? Or does SCSI wide really > > > need that kind of care? > > > > SCSI wide does not require that kind of "care", nor does SCSI-II, but > > ultra SCSI does. The clock rate is doubled, and cable quality is > > important. > > > > For me, buying a $150 cable for a $15K server is really good deal, and > > much better than pissing around for days getting rid of SCSI errors... but > > not everyone builds $15K boxes. > > I was going to wait until I located a discounter to post this, but maybe I > shouldn't wait. I had the wrong web page, I was looking at the one for > scsi external cabless. The internal cable I think I'll get (as soon as I > find a discount place that sells Granite Digital, I've been told they > exist) will only cost 86 bucks, full price. It's a lot for the > application (which isn't a 15K server) but not as outrageous as I > thought, for good quality. You never said in your original message whether you wanted internal or external. Since you quote the external price, I guess that's you wanted :) Granite Digital will custom make internal cables. You basically tell them the distance between each connector. Some applications require specific distances between each device for some signalling requirements. > ----------------------------+----------------------------------------------- > Chuck Robey | Interests include any kind of voice or data > chuckr@eng.umd.edu | communications topic, C programming, and Unix. > 213 Lakeside Drive Apt T-1 | > Greenbelt, MD 20770 | I run Journey2 and picnic, both FreeBSD > (301) 220-2114 | version 3.0 current -- and great FUN! > ----------------------------+----------------------------------------------- > > > Tom From owner-freebsd-hardware Wed Sep 17 21:38:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA05601 for hardware-outgoing; Wed, 17 Sep 1997 21:38:49 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id VAA05596 for ; Wed, 17 Sep 1997 21:38:46 -0700 (PDT) Received: from soda (jwm@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with ESMTP id VAA19996 for ; Wed, 17 Sep 1997 21:38:44 -0700 Message-Id: <199709180438.VAA19996@soda.CSUA.Berkeley.EDU> To: hardware@freebsd.org Subject: New X11 drivers Reply-to: jwm@CSUA.Berkeley.EDU Date: Wed, 17 Sep 1997 21:34:43 -0700 From: John Milford Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Does anyone know who to contact about adding new drivers to XFree86? An aquantaince of mine says that his company has apointed him as a liason to the free UNIX comunity to help in developing a driver for thier card. I would like to help him find the right people, but have no idea where to start. Thank you for your help. --John From owner-freebsd-hardware Wed Sep 17 22:14:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA07616 for hardware-outgoing; Wed, 17 Sep 1997 22:14:24 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA07610 for ; Wed, 17 Sep 1997 22:14:20 -0700 (PDT) Received: (from grog@localhost) by freebie.lemis.com (8.8.7/8.8.5) id OAA15891; Thu, 18 Sep 1997 14:44:06 +0930 (CST) Message-ID: <19970918144405.62450@lemis.com> Date: Thu, 18 Sep 1997 14:44:05 +0930 From: Greg Lehey To: jwm@CSUA.Berkeley.EDU Cc: hardware@FreeBSD.ORG, David Dawes Subject: Re: New X11 drivers References: <199709180438.VAA19996@soda.CSUA.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199709180438.VAA19996@soda.CSUA.Berkeley.EDU>; from John Milford on Wed, Sep 17, 1997 at 09:34:43PM -0700 Organisation: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8250 Fax: +61-8-8388-8250 Mobile: +61-41-739-7062 WWW-Home-Page: http://www.lemis.com/~grog Fight-Spam-Now: http://www.cauce.org Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Sep 17, 1997 at 09:34:43PM -0700, John Milford wrote: > > Does anyone know who to contact about adding new drivers to > XFree86? An aquantaince of mine says that his company has apointed > him as a liason to the free UNIX comunity to help in developing a > driver for thier card. I would like to help him find the right > people, but have no idea where to start. Thank you for your help. The XFree86 could give you a better answer on this, of course. I don't know if David Dawes is on the -hardware list, but I'm copying him explicitly, just in case. He can point you closer to the right direction. Greg From owner-freebsd-hardware Wed Sep 17 23:28:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA10761 for hardware-outgoing; Wed, 17 Sep 1997 23:28:20 -0700 (PDT) Received: from mailhost.pi.net (root@mailhost.pi.net [145.220.3.9]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA10753 for ; Wed, 17 Sep 1997 23:28:18 -0700 (PDT) Received: from kinchenna (hn17.pi.net [145.220.214.17]) by mailhost.pi.net (8.8.3/8.7.1) with SMTP id IAA20250; Thu, 18 Sep 1997 08:28:02 +0200 (MET DST) Posted-Date: Thu, 18 Sep 1997 08:28:02 +0200 (MET DST) Date: Thu, 18 Sep 1997 08:31:23 +0100 From: Guido Kollerie Subject: Re: SCSI3 cables To: FreeBSD-hardware@FreeBSD.ORG Cc: Chuck Robey X-Mailer: Z-Mail Pro 6.1 (Win32 - 021297) Evaluation Copy, NetManage Inc. X-Priority: 3 (Normal) References: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Anyone know of a good place to get 68 pin wide scsi cables? I have some > new Fujitsu drives, a new NCR 875 controller, and I don't have any cables > to hook them up. I've done some netsearching, and found there's an > incredible range of prices ... if anyone knows where inexpensive and good > might intersect, I'd appreciate it. Another company which is supposed to offer high quality cables is CS Electronics. Recently I received a brochure were they announced "New Low-Cost SCSI cables!". I don't now what the difference in price and quality is with their top of the line SCSI cables. See their web site for more info: http://www.scsi-cables.com/ -- Guido Kollerie From owner-freebsd-hardware Thu Sep 18 01:55:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA19870 for hardware-outgoing; Thu, 18 Sep 1997 01:55:13 -0700 (PDT) Received: from forwiss.tu-muenchen.de (root@forwiss.tu-muenchen.de [131.159.128.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA19861; Thu, 18 Sep 1997 01:55:10 -0700 (PDT) Received: from pccog4.forwiss.tu-muenchen.de (hafner@pccog4.forwiss.tu-muenchen.de [131.159.128.55]) by forwiss.tu-muenchen.de (8.8.5/V5) with ESMTP id KAA01841; Thu, 18 Sep 1997 10:55:06 +0200 (MET DST) Received: (hafner@localhost) by pccog4.forwiss.tu-muenchen.de (8.8.5/8.6.12) id IAA03695; Thu, 18 Sep 1997 08:57:34 GMT Date: Thu, 18 Sep 1997 08:57:34 GMT Message-Id: <199709180857.IAA03695@pccog4.forwiss.tu-muenchen.de> From: Walter Hafner To: freebsd-scsi@freebsd.org, freebsd-hardware@freebsd.org Cc: hafner@forwiss.tu-muenchen.de Subject: Is my NCR controller broken? Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello! I just want to make sure I don't miss something before changing my mainboard. Please enlighten me. I run a 486/DX2-66 (ASUS SP-3 with onboard NCR-810 SCSI controller). This computer runs for about 3 years now (2.0.5, 2.1.0, 2.1.5) Since about four weeks I keep getting SCSI resets and then the bus is dead. No recovery! And it's really strange because the NCR controller reports totally different errors before hanging. Here are the error reports from the last three crashes (typed in by hand, so the actual format may differ): ------------------------------------------------------------------------------- sd1(ncr0:1:0): internal error: cmd00 != 91=(vdsp[0] >> 24) ncr0: timeout ccb=f19fbc00 (skip) ------------------------------------------------------------------------------- ncr0:1: ERROR (a0:0) (f-28-0) (8/13) @ (260:00000000). script cmd=fc00001c. reg: da 10 80 13 47 08 01 1f 00 0f 81 28 80 00 00 00. ncr0: restart (fatal error). sd1(ncr0:1:0): command failed (9ff)@f19fbc00. nrc0: timeout ccb=f19fbc00 (skip) ------------------------------------------------------------------------------- ncr0: SCSI phase error fixup: CCB already dequeued (0xf19fbc00) nrc0: timeout ccb=f19fbc00 (skip) ------------------------------------------------------------------------------- I changed everything: * disconnected everything except the system drive -> still errors * changed cables (three different ones) -> still errors * changed termination (two different external ones, internal, different termpower sttings etc.) -> still errors * turned all devices to 5MB synchr. and finally to acync via 'ncrcontrol' -> still errors * finally replaced the system drive (old DEC 5200 against new IBM DAHC 34330) and put 2.2.1 on it -> still errors. Actually, the errors above are from that setup. The only thing I didn't change was the mainboard. I'd be glad if anyone can confirm my suspicion that the NCR controller has gone nuts. I just can't imagine why ... I'd also appreciate it very much if someone with more insight than myself could explain the error reports to me. I'd especially like to know what this 'f19fbc00' means: it shows up in all three errors (what's a 'ccb' anyway?) Thanks in advance! -Walter From owner-freebsd-hardware Thu Sep 18 03:43:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id DAA27295 for hardware-outgoing; Thu, 18 Sep 1997 03:43:58 -0700 (PDT) Received: from news.nacamar.de (news.nacamar.de [194.162.162.210]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id DAA27239 for ; Thu, 18 Sep 1997 03:43:46 -0700 (PDT) Received: from newsfeed (newsfeed.nacamar.de [194.162.162.196]) by news.nacamar.de (8.8.7/8.8.6) with SMTP id MAA24928; Thu, 18 Sep 1997 12:43:27 +0200 (CEST) Message-Id: <3.0.3.32.19970918124220.00b51290@mail.nacamar.de> X-Sender: petzi@mail.nacamar.de X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 18 Sep 1997 12:42:20 +0200 To: Tom From: Michael Beckmann Subject: Re: Parity trouble with Asus mainboard Cc: hardware@freebsd.org In-Reply-To: References: <3.0.3.32.19970915160712.00b69930@mail.nacamar.de> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Following up to myself. I got 8 x 32 MB with parity from a different vendor today, and they work fine in the Asus mainboard with ECC on. So something weird apparently is wrong with the other SIMMs, so that they are incompatible with the Asus board. I used these other 8 x 32 MB in a busy newsserver since 3 days now, with parity off, and there was no problem. The same mainboard doesn't like these SIMMs with parity on. Maybe a timing problem with the parity chips on the SIMMs. Thanks, Michael At 09:59 15.09.97 -0700, you wrote: > >On Mon, 15 Sep 1997, Michael Beckmann wrote: > >> Greetings, >> >> I had installed 8 x 32 MB parity SIMMs in an Asus P65UP5 Rev. 2.04 >> mainboard with Pentium Pro card P6ND in it. The system is equipped with one >> PPro 200 CPU. Unfortunately, when I install 4, 6 or 8 of these SIMMs, >> FreeBSD gives me a parity error and panics directly after the copyright >> notice during boot. With 2 x 32 MB, it seems to run OK. >> >> This, however, happens only when I enable ECC in the BIOS. When I disable >> ECC/parity, the system runs fine with 256 MB installed. I made world on the >> latest 2.2-stable in this configuration, no problem. >> >> I also tried the same SIMMs in a Gigabyte 586 HX board, and there I can >> boot and run just fine with ECC enabled in the BIOS (it's an NT system, >> though). >> >> Any ideas ? It doesn't look to me like the SIMMs were faulty. Maybe a >> problem with the parity chips ? I also exchanged the mainboard with another >> one of the same type, but found the same problem. >> >> Michael > > I've installed the the same motherboard in a server with 8 32MB SIMMs, >with ECC turned on. It works very well. > >Tom > > > From owner-freebsd-hardware Thu Sep 18 06:25:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA05367 for hardware-outgoing; Thu, 18 Sep 1997 06:25:45 -0700 (PDT) Received: from destiny.erols.com (root@destiny.erols.com [207.96.73.65]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA05354; Thu, 18 Sep 1997 06:25:38 -0700 (PDT) Received: from destiny.erols.com (someone@destiny.erols.com [207.96.73.65]) by destiny.erols.com (8.8.7/8.6.12) with SMTP id JAA01136; Thu, 18 Sep 1997 09:25:01 -0400 (EDT) Date: Thu, 18 Sep 1997 09:25:00 -0400 (EDT) From: John Dowdal To: Walter Hafner cc: freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Is my NCR controller broken? In-Reply-To: <199709180857.IAA03695@pccog4.forwiss.tu-muenchen.de> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I just dealt with solving the same problem. In fact there were were several problems. 1) DEC DSP5400S drive dies with a physical media failure 2) Attempt to low level the drive; it fails and the drive powers down [ie it is dead, Jim] 3) remove the drive from /etc/fstab and run for two weeks with same physical setup, waiting for replacement. 4) Remove dead drive [internal] and add new drive [external] with correct termination. Haul dead drive to school, to try using the Solaris format comand on it. Attempt to remote log into my machine, its dead. 5) Go back home, and messages like you describe. The old good drive powering up and powering down. Turns out the Y connector is dead. Remove it. Sigh of releif; not two dead disks in two weeks. 6) Format the DSP5400S. It powers down on the sun too. The grown defect list is approx 1000; the primary is approx 200. Seems quite dead... 7) Return home, reconnect the rest of my external chain. Starts to boot, and dies with error messsages you describe during fsck. *Grumble* 8) Dissect each external case, try all combinations one at a time, turns out that if I include the CD writer I get the above errors while fscking. "FunnySCSI" below is the "weird" connector which is on a SUN-3 shoe box. [2 internal drives] -> [Computer-HD50] -> [Tape-Centronics] -> [CDWriter-FunnySCSI] -> [Disk-Centronics] Next I swapped the tape and disk; same effect 9) Next I bought a Centronics-Centronics cable, to remove the CDWriter from the chain. -> this worked fine 10) Broke SCSI spec by terminating the CD writer at the drive, leaving an illegal stub of cable sticking out of the case [the other FunnySCSI connector]. Connected this with one funnyscsi->centronics cable .. -> this seems to work fine Hopefully this helps somebody with scsi problems :) John On Thu, 18 Sep 1997, Walter Hafner wrote: > Hello! > > I just want to make sure I don't miss something before changing my > mainboard. Please enlighten me. > > I run a 486/DX2-66 (ASUS SP-3 with onboard NCR-810 SCSI > controller). This computer runs for about 3 years now (2.0.5, 2.1.0, > 2.1.5) > > Since about four weeks I keep getting SCSI resets and then the bus is > dead. No recovery! And it's really strange because the NCR controller > reports totally different errors before hanging. Here are the error > reports from the last three crashes (typed in by hand, so the actual > format may differ): > > ------------------------------------------------------------------------------- > > sd1(ncr0:1:0): internal error: cmd00 != 91=(vdsp[0] >> 24) > ncr0: timeout ccb=f19fbc00 (skip) > > ------------------------------------------------------------------------------- > > ncr0:1: ERROR (a0:0) (f-28-0) (8/13) @ (260:00000000). > script cmd=fc00001c. > reg: da 10 80 13 47 08 01 1f 00 0f 81 28 80 00 00 00. > ncr0: restart (fatal error). > sd1(ncr0:1:0): command failed (9ff)@f19fbc00. > nrc0: timeout ccb=f19fbc00 (skip) > > ------------------------------------------------------------------------------- > > ncr0: SCSI phase error fixup: CCB already dequeued (0xf19fbc00) > nrc0: timeout ccb=f19fbc00 (skip) > > ------------------------------------------------------------------------------- > > I changed everything: > > * disconnected everything except the system drive -> still errors > * changed cables (three different ones) -> still errors > * changed termination (two different external ones, internal, different > termpower sttings etc.) -> still errors > * turned all devices to 5MB synchr. and finally to acync via > 'ncrcontrol' -> still errors > * finally replaced the system drive (old DEC 5200 against new IBM DAHC > 34330) and put 2.2.1 on it -> still errors. Actually, the errors above > are from that setup. > > The only thing I didn't change was the mainboard. > > I'd be glad if anyone can confirm my suspicion that the NCR controller > has gone nuts. I just can't imagine why ... > > I'd also appreciate it very much if someone with more insight than > myself could explain the error reports to me. I'd especially like to > know what this 'f19fbc00' means: it shows up in all three errors (what's > a 'ccb' anyway?) > > Thanks in advance! > > -Walter > > From owner-freebsd-hardware Thu Sep 18 11:13:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA24516 for hardware-outgoing; Thu, 18 Sep 1997 11:13:21 -0700 (PDT) Received: from prwan.learcorp.com (nsn1-gw5-xl11.netrex.com [206.253.228.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA24487 for ; Thu, 18 Sep 1997 11:12:53 -0700 (PDT) Received: (from proberts@localhost) by prwan.learcorp.com (8.8.7/8.8.7) id OAA00607; Thu, 18 Sep 1997 14:13:29 -0400 (EDT) Message-ID: <19970918141328.11252@sequoianet.com> Date: Thu, 18 Sep 1997 14:13:28 -0400 From: "Patrick S. Roberts" To: Tom Cc: Chuck Robey , Brett Glass , FreeBSD-hardware@FreeBSD.ORG Subject: Re: SCSI3 cables References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: ; from Tom on Wed, Sep 17, 1997 at 05:37:00PM -0700 X-Useless-Header: Down with the BILL BORG! X-Operating-System: FreeBSD prwan.learcorp.com 3.0-970909-SNAP FreeBSD 3.0-970909-SNAP Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wed, Sep 17, 1997 at 05:37:00PM -0700, Tom wrote: > > On Wed, 17 Sep 1997, Chuck Robey wrote: > > > On Wed, 17 Sep 1997, Brett Glass wrote: > > > > > Granite Digital is the best, and is not that expensive. > > > > I just checked their website, and their most inexpensive 3 foot 68 pin > > cable was $149. That's the single most expensive cable I've yet found, > > and costs quite a bit more than the controller. I didn't even look at > > their more expensive, sliver and gold cables. You may be right on their > > quality, but isn't that price a little overkill? Or does SCSI wide really > > need that kind of care? > > SCSI wide does not require that kind of "care", nor does SCSI-II, but > ultra SCSI does. The clock rate is doubled, and cable quality is > important. > > For me, buying a $150 cable for a $15K server is really good deal, and > much better than pissing around for days getting rid of SCSI errors... but > not everyone builds $15K boxes. > > Tom > Heh... I just built a 80,000$ Box here and they started balking 'cause the ethernet card ran them 769$. hahha... -- ____ _ _ _ / ___|| |_ ___ _ __ _ __ ___ | |__ _ __(_)_ __ __ _ ___ _ __ \___ \| __/ _ \| '__| '_ ` _ \| '_ \| '__| | '_ \ / _` |/ _ \ '__| ___) | || (_) | | | | | | | | |_) | | | | | | | (_| | __/ | |____/ \__\___/|_| |_| |_| |_|_.__/|_| |_|_| |_|\__, |\___|_| |___/ -|- Patrick S. Roberts -|- Consultant to the Lear Corperation -|- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQCNAzNR7uEAAAEEAOugqOquu2QkYcOKKmCnxIVLcuDMemLO/g7Yw31+SWUMwkdS qQmOnkFwwuzSR4OQNlEIbntvix7tw0LJrErcfIG5EiBxMfGATu1VDwbv/vA7vTfd iEpCWz+xdX2tjSdr1NS904uAHPBl0SghqWrxE/wuJNS9wGm7qQY0nTadQbLxAAUR tCVQYXRyaWNrIFMuIFJvYmVydHMgPHN0b3JteWJAaXp6eS5uZXQ+ =o1kN -----END PGP PUBLIC KEY BLOCK----- From owner-freebsd-hardware Thu Sep 18 11:27:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA25460 for hardware-outgoing; Thu, 18 Sep 1997 11:27:19 -0700 (PDT) Received: from lariat.lariat.org (ppp0.lariat.org@[129.72.251.2]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA25412 for ; Thu, 18 Sep 1997 11:27:09 -0700 (PDT) Received: from solo ([129.72.251.10] (may be forged)) by lariat.lariat.org (8.8.6/8.8.6) with SMTP id MAA27283; Thu, 18 Sep 1997 12:22:06 -0600 (MDT) Message-Id: <3.0.3.32.19970918122624.00946100@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Thu, 18 Sep 1997 12:26:24 -0600 To: "Patrick S. Roberts" , Tom From: Brett Glass Subject: Re: SCSI3 cables Cc: Chuck Robey , FreeBSD-hardware@FreeBSD.ORG In-Reply-To: <19970918141328.11252@sequoianet.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 02:13 PM 9/18/97 -0400, Patrick S. Roberts wrote: >Heh... I just built a 80,000$ Box here and they started balking 'cause the >ethernet card ran them 769$. hahha... That must be quite a box. Is it Intel-based? If so, how many dozen PPros does it have in it? ;-) What sort of Ethernet card costs $769? In any event, the Granite external cables are high if you pay full list, but you can get discounts from resellers and most people really need the internal cables. At least for disk drives. --Brett From owner-freebsd-hardware Thu Sep 18 15:59:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA15115 for hardware-outgoing; Thu, 18 Sep 1997 15:59:39 -0700 (PDT) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA15101; Thu, 18 Sep 1997 15:59:33 -0700 (PDT) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.4/8.8.4) with ESMTP id PAA24536; Thu, 18 Sep 1997 15:58:49 -0700 (PDT) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id PAA10561; Thu, 18 Sep 1997 15:58:48 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id PAA00471; Thu, 18 Sep 1997 15:58:47 -0700 (PDT) From: Don Lewis Message-Id: <199709182258.PAA00471@salsa.gv.tsc.tdk.com> Date: Thu, 18 Sep 1997 15:58:47 -0700 In-Reply-To: John Dowdal "Re: Is my NCR controller broken?" (Sep 18, 9:25am) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: John Dowdal , Walter Hafner Subject: Re: Is my NCR controller broken? Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sep 18, 9:25am, John Dowdal wrote: } Subject: Re: Is my NCR controller broken? } I just dealt with solving the same problem. In fact there were were } several problems. } } 7) Return home, reconnect the rest of my external chain. Starts to boot, } and dies with error messsages you describe during fsck. *Grumble* } 8) Dissect each external case, try all combinations one at a time, turns } out that if I include the CD writer I get the above errors while } fscking. "FunnySCSI" below is the "weird" connector which is on a } SUN-3 shoe box. } } [2 internal drives] -> [Computer-HD50] -> [Tape-Centronics] -> } [CDWriter-FunnySCSI] -> [Disk-Centronics] } } Next I swapped the tape and disk; same effect } } 9) Next I bought a Centronics-Centronics cable, to remove the CDWriter } from the chain. } -> this worked fine } } 10) Broke SCSI spec by terminating the CD writer at the drive, leaving } an illegal stub of cable sticking out of the case [the other FunnySCSI } connector]. Connected this with one funnyscsi->centronics cable .. } -> this seems to work fine I seem to recall problems with termpower and Sun 3 vintage equipment (this stuff predates SCSI 1). I believe the some Sun 3's actually grounded the termpower pin which tended to melt things if you connected them to post-standard equipment that supplied termpower. I wonder if your shoe box or the cables that connect to it don't pass termpower through. This might result in no power to an external terminator at the end of your SCSI chain, and it is consistent with the configurations that worked and didn't work. You should be able to make it work by putting either the disk or tape back at the end of the chain and configuring the end device to supply termpower to the bus. --- Truck From owner-freebsd-hardware Thu Sep 18 17:00:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA19243 for hardware-outgoing; Thu, 18 Sep 1997 17:00:24 -0700 (PDT) Received: from fly.HiWAAY.net (root@fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA19236 for ; Thu, 18 Sep 1997 17:00:22 -0700 (PDT) Received: from nospam.hiwaay.net (tnt2-152.HiWAAY.net [208.147.148.152]) by fly.HiWAAY.net (8.8.6/8.8.6) with ESMTP id TAA12896; Thu, 18 Sep 1997 19:00:11 -0500 (CDT) Received: from nospam.hiwaay.net (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.7/8.8.4) with ESMTP id TAA20506; Thu, 18 Sep 1997 19:00:08 -0500 (CDT) Message-Id: <199709190000.TAA20506@nospam.hiwaay.net> X-Mailer: exmh version 2.0zeta 7/24/97 To: Michael Beckmann cc: hardware@FreeBSD.ORG From: dkelly@hiwaay.net Subject: Re: Parity trouble with Asus mainboard In-reply-to: Message from Michael Beckmann of "Thu, 18 Sep 1997 12:42:20 +0200." <3.0.3.32.19970918124220.00b51290@mail.nacamar.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 18 Sep 1997 19:00:07 -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Following up to myself. I got 8 x 32 MB with parity from a different vendor > today, and they work fine in the Asus mainboard with ECC on. So something > weird apparently is wrong with the other SIMMs, so that they are > incompatible with the Asus board. I used these other 8 x 32 MB in a busy > newsserver since 3 days now, with parity off, and there was no problem. The > same mainboard doesn't like these SIMMs with parity on. Maybe a timing > problem with the parity chips on the SIMMs. > > Thanks, > > Michael As somebody else mentioned there are quacks selling "logic parity" or "virtual parity" or other nonsense-named SIMMs with fake parity. Most real parity 72-pin SIMMs I've seen have 12 chips. Fake parity will have 9. If all your chips don't have the same part number then its likely you have fake parity. Fake parity is worse than none. It lets a vendor label memory x36 rather than x32. It lets questionable mom&pop PC shops to ship a box with parity enabled in the BIOS setup (sometimes) and suggest to the unkowning that the system is better than it really is. Fake parity SIMMs are slower than the marked speed because their logic has to calculate the faked parity bits and can't do that until after the memory read has happened. And if it so happens your MB calculates parity different than the SIMM, then you get the situation you just uncovered. ECC is likely to calculate the high 4 bits differently. -- 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 Thu Sep 18 17:30:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA21499 for hardware-outgoing; Thu, 18 Sep 1997 17:30:49 -0700 (PDT) Received: from ns.feral.com (mjacob@feral.mauswerks.net [204.152.96.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id RAA21476; Thu, 18 Sep 1997 17:30:42 -0700 (PDT) Received: (from mjacob@localhost) by ns.feral.com (8.8.6/8.8.6) id RAA07442; Thu, 18 Sep 1997 17:25:13 -0700 Date: Thu, 18 Sep 1997 17:25:13 -0700 From: Matthew Jacob Message-Id: <199709190025.RAA07442@ns.feral.com> To: Don.Lewis@tsc.tdk.com Subject: Re: Is my NCR controller broken? Cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >(this stuff predates SCSI 1) Wrong. > I believe the some Sun 3's actually Wrong. It was actually the sun 4/110. I'd also like to point out that neither SCSI-1 nor SASI before it specified cable pinouts- just pin numbers. From owner-freebsd-hardware Thu Sep 18 18:07:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA24154 for hardware-outgoing; Thu, 18 Sep 1997 18:07:45 -0700 (PDT) Received: from math.berkeley.edu (math.Berkeley.EDU [128.32.183.94]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA24148 for ; Thu, 18 Sep 1997 18:07:40 -0700 (PDT) Received: (from dan@localhost) by math.berkeley.edu (8.8.7/8.8.7) id SAA26720; Thu, 18 Sep 1997 18:07:37 -0700 (PDT) Date: Thu, 18 Sep 1997 18:07:37 -0700 (PDT) From: dan@math.berkeley.edu (Dan Strick) Message-Id: <199709190107.SAA26720@math.berkeley.edu> To: FreeBSD-hardware@FreeBSD.ORG Subject: Re: SCSI3 cables Cc: dan@math.berkeley.edu Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk The "high quality" SCSI cables sold by Granite Digital and other companies seem rather pricey. I think they are taking excessive advantage of a SCSI FUD factor resulting from SCSI errors caused by end-user ignorance and cable vendor behavior verging on outright fraud. For example, many end-users think nothing about connecting "fast-20" devices together with 6 foot cables and wouldn't even know to wonder about the termination of the extra signals at a wide/narrow SCSI cable junction. Then there are the cable manufactures/vendors who shave pennies off the cost of cables by using thin wire and omitting some of the grounds. Avoiding these kinds of really gross configuration errors is essential. You should pay attention to the rules for maximum cable and stub lengths. You should know exactly where your terminators are. Care is especially required with "fast" and "ultra" SCSI. However, using gold plated connector shells with embedded LEDs does not make your electrons move any faster. Gold plated contacts and teflon insulation can make the physical cable and the connections a little more robust, but they aren't worth the extra cost in most applications. You don't need silver wire. The manufacturer should have used an adequate wire size (28 awg of better) and the cable should have a "characteristic impedance" similar to the termination resistance (usually about 115 ohms these days; was about 132 ohms before "active" terminators). It is not easy to find out exactly how your cables are made, especially when they have molded high density connectors. The vendor probably doesn't even know. I feel ripped off at both ends. Dan Strick dan@math.berkeley.edu From owner-freebsd-hardware Thu Sep 18 18:26:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA25304 for hardware-outgoing; Thu, 18 Sep 1997 18:26:02 -0700 (PDT) Received: from gatekeeper.tsc.tdk.com (root@gatekeeper.tsc.tdk.com [207.113.159.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA25276; Thu, 18 Sep 1997 18:25:54 -0700 (PDT) Received: from sunrise.gv.tsc.tdk.com (root@sunrise.gv.tsc.tdk.com [192.168.241.191]) by gatekeeper.tsc.tdk.com (8.8.4/8.8.4) with ESMTP id SAA26662; Thu, 18 Sep 1997 18:25:51 -0700 (PDT) Received: from salsa.gv.tsc.tdk.com (salsa.gv.tsc.tdk.com [192.168.241.194]) by sunrise.gv.tsc.tdk.com (8.8.5/8.8.5) with ESMTP id SAA12896; Thu, 18 Sep 1997 18:25:50 -0700 (PDT) Received: (from gdonl@localhost) by salsa.gv.tsc.tdk.com (8.8.5/8.8.5) id SAA00739; Thu, 18 Sep 1997 18:25:49 -0700 (PDT) From: Don Lewis Message-Id: <199709190125.SAA00739@salsa.gv.tsc.tdk.com> Date: Thu, 18 Sep 1997 18:25:48 -0700 In-Reply-To: Matthew Jacob "Re: Is my NCR controller broken?" (Sep 18, 5:25pm) X-Mailer: Mail User's Shell (7.2.6 alpha(3) 7/19/95) To: Matthew Jacob , Don.Lewis@tsc.tdk.com Subject: Warning! Sun archaeology [was Re: Is my NCR controller broken?] Cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sep 18, 5:25pm, Matthew Jacob wrote: } Subject: Re: Is my NCR controller broken? } >(this stuff predates SCSI 1) } } Wrong. I may have misremembered on this point. } > I believe the some Sun 3's actually } } Wrong. It was actually the sun 4/110. Looks like we're both right. I was unaware that the 4/110 was similarly afflicted. From my sun-managers archives: First, I was reminded about something which, while not directly impacting my situation, is well worth repeating. This is the infamous design decision(?) by Sun to ground the "termination power" SCSI pin on the 3/60 and 4/110 models, which means that a straight-through cable from either of these models to a SCSI drive with termination power supplied tends to blow the drive up! So while it's safe to plug an ex sun-3 drive onto a new system, plugging a new drive onto a 3/60 is potentially a problem! It's ok if you disable "termination power" on the drive, or cut the appropriate pin of the SCSI cable. Also >> 1) most Sun-2/Sun-3 SCSI cards don't supply termination power to the >> TRMPWR line on the SCSI bus. Only very late engineering rev >> cards supply power (if your's does it will have a fuse on >> the card). Make sure that your disk is supplying termination >> power (most disks have a jumper to enable/disable this). and from comp.periphs.scsi: The SparcStation 1 and 1+, Sun3/50 and 3/60, all do not supply term power. And, I think I recall that some 3/60s even have their TERMPWR pin (pin 26) wired to ground. This can cause serious smoke if you connect a device that sources term power; The 386i seems to be the only Sun (non-VME) that sources term power, as this was required to power the external terminator plug that was supplied with that machine. and from comp.periphs: Some time ago, there was much discussion of how Sun screwed up the SCSI interface on their 3/60s -- pin 26, which is supposed to supply +5 volts for termination power was grounded. This meant that any other device which chose to supply +5 on that line was likely to melt-down its power supply, or worse, its firmware. Since, up till now, I have always connected to Sun shoeboxes, I have not been concerned with this problem. However, now that I am connecting to another vendor's shoebox, I must take precautions. As a simple, if ugly, fix, I just cut wire 26 of the ribbon cable at the Sun end, causing line to float. (Actually, I made a short piece of cable with line 26 cut which I can insert between the sun and the cable to the disk drives). Strangely, when I tested for continuity between pin 26 and ground on the 3/60, there was none. Still, better to be safe... } I'd also like to point out that neither SCSI-1 nor SASI before } it specified cable pinouts- just pin numbers. } }-- End of excerpt from Matthew Jacob --- Truck From owner-freebsd-hardware Thu Sep 18 18:29:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA25627 for hardware-outgoing; Thu, 18 Sep 1997 18:29:03 -0700 (PDT) Received: from ns.feral.com (mjacob@feral.mauswerks.net [204.152.96.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA25598; Thu, 18 Sep 1997 18:28:56 -0700 (PDT) Received: (from mjacob@localhost) by ns.feral.com (8.8.6/8.8.6) id SAA07539; Thu, 18 Sep 1997 18:23:29 -0700 Date: Thu, 18 Sep 1997 18:23:29 -0700 From: Matthew Jacob Message-Id: <199709190123.SAA07539@ns.feral.com> To: Don.Lewis@tsc.tdk.com, mjacob@feral.com Subject: Re: Warning! Sun archaeology [was Re: Is my NCR controller broken?] Cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Cc: freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG > >On Sep 18, 5:25pm, Matthew Jacob wrote: >} Subject: Re: Is my NCR controller broken? >} >(this stuff predates SCSI 1) >} >} Wrong. > >I may have misremembered on this point. Ooh, I should have been nicer... sorry... > >} > I believe the some Sun 3's actually >} >} Wrong. It was actually the sun 4/110. > >Looks like we're both right. I was unaware that the 4/110 was >similarly afflicted. From my sun-managers archives: >.. Oops- yer right, the 3/60 putzed it too. > >> 1) most Sun-2/Sun-3 SCSI cards don't supply termination power to the > >> TRMPWR line on the SCSI bus. Only very late engineering rev That's also true. From owner-freebsd-hardware Thu Sep 18 18:58:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA28364 for hardware-outgoing; Thu, 18 Sep 1997 18:58:35 -0700 (PDT) Received: from rio.workcover.qld.gov.au (server.workcover.qld.gov.au [203.101.253.1]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA28359 for ; Thu, 18 Sep 1997 18:58:30 -0700 (PDT) Received: from manila.workcover.qld.gov.au (manila-dmz [131.242.84.201]) by rio.workcover.qld.gov.au (8.8.5/8.8.6) with SMTP id MAA24334 for ; Fri, 19 Sep 1997 12:00:25 +1000 (EST) Received: from localhost by manila.workcover.qld.gov.au (8.6.8.1/DEVETIR-0.1) id CAA21091 for ; Fri, 19 Sep 1997 02:00:09 GMT Message-Id: <199709190200.CAA21091@manila.workcover.qld.gov.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: hardware@freebsd.org Subject: ATM cards for FreeBSD in Australia X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 19 Sep 1997 12:00:08 +1000 From: Stephen Hocking Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I'm not too clued in about ATM standards in Australia, so I have no idea if any of the U.S. cards work here. Someone I know in Canberra wishes to snoop ATM packets using the BPF device, which if the drivers follow the usual network model, should be in place already. Does anyone have answers to the following? Are there any ATM cards that are supported by FreeBSD current at all? Are they likely to work in a box running the SMP code? Stephen -- The views expressed above are not those of WorkCover Queensland, Australia. "We've heard that a million monkeys at a million keyboards could produce the Complete Works of Shakespeare; now, thanks to the Internet, we know this is not true." Robert Wilensky, University of California From owner-freebsd-hardware Thu Sep 18 23:00:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA15163 for hardware-outgoing; Thu, 18 Sep 1997 23:00:55 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA15158 for ; Thu, 18 Sep 1997 23:00:51 -0700 (PDT) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id HAA12467; Fri, 19 Sep 1997 07:55:01 +0200 (CEST) To: Stephen Hocking cc: hardware@freebsd.org Subject: Re: ATM cards for FreeBSD in Australia In-reply-to: Your message of "Fri, 19 Sep 1997 12:00:08 +1000." <199709190200.CAA21091@manila.workcover.qld.gov.au> Date: Fri, 19 Sep 1997 07:55:01 +0200 Message-ID: <12465.874648501@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199709190200.CAA21091@manila.workcover.qld.gov.au>, Stephen Hocking writes: > > I'm not too clued in about ATM standards in Australia, so I have no >idea if any of the U.S. cards work here. Someone I know in Canberra wishes to >snoop ATM packets using the BPF device, which if the drivers follow the usual >network model, should be in place already. Does anyone have answers to the >following? How does he intend to do that ? You can't wiretap a fiber... >Are there any ATM cards that are supported by FreeBSD current at all? yes, check out sys/dev/en >Are they likely to work in a box running the SMP code? yes. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-hardware Thu Sep 18 23:11:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA15799 for hardware-outgoing; Thu, 18 Sep 1997 23:11:38 -0700 (PDT) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA15786 for ; Thu, 18 Sep 1997 23:11:33 -0700 (PDT) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id XAA19614; Thu, 18 Sep 1997 23:10:13 -0700 (PDT) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpd019604; Fri Sep 19 06:10:09 1997 Date: Thu, 18 Sep 1997 23:09:26 -0700 (PDT) From: Julian Elischer To: Stephen Hocking cc: hardware@FreeBSD.ORG Subject: Re: ATM cards for FreeBSD in Australia In-Reply-To: <199709190200.CAA21091@manila.workcover.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk don't forget you can only snoop ATM packets that are passing through your machine. On Fri, 19 Sep 1997, Stephen Hocking wrote: > > I'm not too clued in about ATM standards in Australia, so I have no > idea if any of the U.S. cards work here. Someone I know in Canberra wishes to > snoop ATM packets using the BPF device, which if the drivers follow the usual > network model, should be in place already. Does anyone have answers to the > following? > > Are there any ATM cards that are supported by FreeBSD current at all? > > Are they likely to work in a box running the SMP code? > > > Stephen > -- > The views expressed above are not those of WorkCover Queensland, Australia. > > "We've heard that a million monkeys at a million keyboards could produce > the Complete Works of Shakespeare; now, thanks to the Internet, we know > this is not true." Robert Wilensky, University of California > > > From owner-freebsd-hardware Thu Sep 18 23:59:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA19381 for hardware-outgoing; Thu, 18 Sep 1997 23:59:09 -0700 (PDT) Received: from hobbes.saturn-tech.com (drussell@drussell.internode.net [198.161.228.154]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA19367 for ; Thu, 18 Sep 1997 23:58:43 -0700 (PDT) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id AAA10421; Fri, 19 Sep 1997 00:58:59 -0600 (MDT) Date: Fri, 19 Sep 1997 00:58:59 -0600 (MDT) From: Doug Russell To: Dan Strick cc: FreeBSD-hardware@FreeBSD.ORG Subject: Re: SCSI3 cables In-Reply-To: <199709190107.SAA26720@math.berkeley.edu> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 18 Sep 1997, Dan Strick wrote: > The "high quality" SCSI cables sold by Granite Digital and other > companies seem rather pricey. I think they are taking excessive > advantage of a SCSI FUD factor resulting from SCSI errors caused > by end-user ignorance and cable vendor behavior verging on > outright fraud. For example, many end-users think nothing about ...etc I tend to agree. Although the very expensive cables usually ARE good cables, you don't necessarily need to spend a fortune. Personally, I like to keep some good 50 and 68 pin cable on hand and a couple packages of IDC connectors. That way I can whip up a cable for how ever many drives, with whatever spacing I require. Of course, it isn't quite as simple for external cables. :) Luckily most of the time I'm linking in chains of hard disks, or CD-ROMS. Now if I could just figure out why the 5 CD-ROMS on an NCR 810 controller (ASUS SC-200) go WILD when they are probed, but the SCSI tape drive works fine (6th device) since I changed motherboards from a Gigabyte 486 board to an ASUS TX97-E... They worked before, but go NUTS now. I had to disconnect them all before they self destructed. :) SCSI CAN be fun sometimes. :) Later...... From owner-freebsd-hardware Fri Sep 19 06:45:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA12667 for hardware-outgoing; Fri, 19 Sep 1997 06:45:34 -0700 (PDT) Received: from plains.NoDak.edu (tinguely@plains.NoDak.edu [134.129.111.64]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA12660 for ; Fri, 19 Sep 1997 06:45:32 -0700 (PDT) Received: (from tinguely@localhost) by plains.NoDak.edu (8.8.5/8.8.5) id IAA03070; Fri, 19 Sep 1997 08:45:20 -0500 (CDT) Date: Fri, 19 Sep 1997 08:45:20 -0500 (CDT) From: Mark Tinguely Message-Id: <199709191345.IAA03070@plains.NoDak.edu> To: hardware@FreeBSD.ORG, sysseh@workcover.qld.gov.au Subject: Re: ATM cards for FreeBSD in Australia Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I'm not too clued in about ATM standards in Australia, so I have no > idea if any of the U.S. cards work here. Someone I know in Canberra wishes to > snoop ATM packets using the BPF device, which if the drivers follow the usual > network model, should be in place already. Does anyone have answers to the > following? > don't listen to those telling you can only snoop PDU local to the machine. there are two options of viewing other PDUs. 1) snooper ports in switches, redirect packets going down other lines 2) optical taps. these are T connection that you attach to a pair of fibers. there is a paritially reflective mirror inside that reflects a small portion of the light to you ATM card. ------->------- | | ==================>========+===== | -- to ATM card 1 SWITCH1 SWITCH2 ==================<========+===== | -- to ATM card 2 | | ------>-------- if you want to take advantage of the ATM card's SAR, it would be nice to know ahead of time what AAL of the VC you are looking at. At worse case, you can capture raw cells and then manually do the SAR functions. > Are there any ATM cards that are supported by FreeBSD current at all? the Fore and Efficient cards are supported. I wrote a IDT NICStAR driver that has BPF hooks, a graduate student wrote tcpdump parsing print routine for LANE (that work was done on a Sun), I am looking at doing the Classic IP over ATM print routine for the IDT (the HARP stack does IP over ATM). > Are they likely to work in a box running the SMP code? I think the capture into memory/disk, then post-process (like a commerical Sniffer does) is your best bet to keep from losing information. --mark. PS. you may be interested in asking ATM questions to the freebsd-atm mailing list. From owner-freebsd-hardware Fri Sep 19 07:06:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA13840 for hardware-outgoing; Fri, 19 Sep 1997 07:06:01 -0700 (PDT) Received: from prwan.learcorp.com (nsn1-gw5-xl11.netrex.com [206.253.228.21]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA13834 for ; Fri, 19 Sep 1997 07:05:54 -0700 (PDT) Received: (from proberts@localhost) by prwan.learcorp.com (8.8.7/8.8.7) id KAA00357; Fri, 19 Sep 1997 10:07:18 -0400 (EDT) Message-ID: <19970919100717.10530@sequoianet.com> Date: Fri, 19 Sep 1997 10:07:17 -0400 From: "Patrick S. Roberts" To: Brett Glass Cc: Tom , Chuck Robey , FreeBSD-hardware@FreeBSD.ORG Subject: Re: SCSI3 cables References: <19970918141328.11252@sequoianet.com> <3.0.3.32.19970918122624.00946100@mail.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81 In-Reply-To: <3.0.3.32.19970918122624.00946100@mail.lariat.org>; from Brett Glass on Thu, Sep 18, 1997 at 12:26:24PM -0600 X-Useless-Header: Down with the BILL BORG! X-Operating-System: FreeBSD prwan.learcorp.com 3.0-970909-SNAP FreeBSD 3.0-970909-SNAP Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Sep 18, 1997 at 12:26:24PM -0600, Brett Glass wrote: > At 02:13 PM 9/18/97 -0400, Patrick S. Roberts wrote: > > >Heh... I just built a 80,000$ Box here and they started balking 'cause the > >ethernet card ran them 769$. hahha... > > That must be quite a box. Is it Intel-based? If so, how many dozen PPros > does it have in it? ;-) What sort of Ethernet card costs $769? > > In any event, the Granite external cables are high if you pay full list, > but you can get discounts from resellers and most people really need the > internal cables. At least for disk drives. > > --Brett Noper.. its a Sun Ultra Enterprize 450... w/2 300mhz Ultra II's... 1.5gb of mem and a few other nice toys... [also that price also includes about 35,000$ worth of software too....] and the Ethernet card is real nice... albeit a bit expensive... -- ____ _ _ _ / ___|| |_ ___ _ __ _ __ ___ | |__ _ __(_)_ __ __ _ ___ _ __ \___ \| __/ _ \| '__| '_ ` _ \| '_ \| '__| | '_ \ / _` |/ _ \ '__| ___) | || (_) | | | | | | | | |_) | | | | | | | (_| | __/ | |____/ \__\___/|_| |_| |_| |_|_.__/|_| |_|_| |_|\__, |\___|_| |___/ -|- Patrick S. Roberts -|- Consultant to the Lear Corperation -|- -----BEGIN PGP PUBLIC KEY BLOCK----- Version: 2.6.2 mQCNAzNR7uEAAAEEAOugqOquu2QkYcOKKmCnxIVLcuDMemLO/g7Yw31+SWUMwkdS qQmOnkFwwuzSR4OQNlEIbntvix7tw0LJrErcfIG5EiBxMfGATu1VDwbv/vA7vTfd iEpCWz+xdX2tjSdr1NS904uAHPBl0SghqWrxE/wuJNS9wGm7qQY0nTadQbLxAAUR tCVQYXRyaWNrIFMuIFJvYmVydHMgPHN0b3JteWJAaXp6eS5uZXQ+ =o1kN -----END PGP PUBLIC KEY BLOCK----- From owner-freebsd-hardware Fri Sep 19 07:19:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA14649 for hardware-outgoing; Fri, 19 Sep 1997 07:19:09 -0700 (PDT) Received: from runningman.rs.itd.umich.edu (0@runningman.rs.itd.umich.edu [141.211.144.15]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA14644; Fri, 19 Sep 1997 07:19:07 -0700 (PDT) Received: from HG-BASIC1MAIL.HG.MED.UMICH.EDU by runningman.rs.itd.umich.edu (8.8.5/2.3) with ESMTP id KAA21718; Fri, 19 Sep 1997 10:19:06 -0400 (EDT) Received: from HG-BASIC1/SpoolDir by HG-BASIC1MAIL.HG.MED.UMICH.EDU (Mercury 1.31); 19 Sep 97 10:19:05 -0500 Received: from SpoolDir by HG-BASIC1 (Mercury 1.31); 19 Sep 97 10:18:51 -0500 Received: from biped by HG-BASIC1MAIL.HG.MED.UMICH.EDU (Mercury 1.31) with ESMTP; 19 Sep 97 10:18:50 -0500 Message-ID: <342289CA.99C025E9@umich.edu> Date: Fri, 19 Sep 1997 10:18:50 -0400 From: Sasha Kacanski X-Mailer: Mozilla 4.01 [en] (WinNT; I) MIME-Version: 1.0 To: "freebsd-scsi@FreeBSD.ORG" , "hardware@FreeBSD.ORG" Subject: password protected site X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, Have a Q: if I have a BSD machine running internet server and SUN running a intranet, how should I go about implementing user/password access to the intranet via BSD. Apache web server is running on the BSD side. What type of password encryption does Netscape client supports. I can't go with the clear text. Any suggestions! thanks /s From owner-freebsd-hardware Fri Sep 19 09:16:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA21782 for hardware-outgoing; Fri, 19 Sep 1997 09:16:49 -0700 (PDT) Received: from gw1.asacomputers.com (root@gw1.asacomputers.com [204.69.220.10]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA21777 for ; Fri, 19 Sep 1997 09:16:47 -0700 (PDT) Received: by gw1.asacomputers.com id GAA22633; Fri, 19 Sep 1997 06:16:18 -0700 (PDT) Message-Id: <2.2.32.19970919161324.00cc0bbc@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: Fri, 19 Sep 1997 09:13:24 -0700 To: Stephen Hocking From: Kedar Subject: Re: ATM cards for FreeBSD in Australia Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, We have had a couple of boxes using the EFFICIENT MMF PCI ENI-155P-MF-S WITH 2MB running current/ SMP for about a fortnight or more. So far so good. G'day, Kedar. At 12:00 PM 9/19/97 +1000, you wrote: >Are there any ATM cards that are supported by FreeBSD current at all? >Are they likely to work in a box running the SMP code? From owner-freebsd-hardware Fri Sep 19 11:26:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA29007 for hardware-outgoing; Fri, 19 Sep 1997 11:26:29 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA28999 for ; Fri, 19 Sep 1997 11:26:25 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id LAA11167; Fri, 19 Sep 1997 11:26:11 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199709191826.LAA11167@GndRsh.aac.dev.com> Subject: Re: SCSI3 cables In-Reply-To: <199709190107.SAA26720@math.berkeley.edu> from Dan Strick at "Sep 18, 97 06:07:37 pm" To: dan@math.berkeley.edu (Dan Strick) Date: Fri, 19 Sep 1997 11:26:11 -0700 (PDT) Cc: FreeBSD-hardware@FreeBSD.ORG, dan@math.berkeley.edu X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I agree with 98% of your message, just one small point I want to make. ... > However, using gold plated connector shells with embedded LEDs > does not make your electrons move any faster. Gold plated > contacts and teflon insulation can make the physical cable ^^^^^^ ^^^^^^^^^^^^^^ > and the connections a little more robust, but they aren't > worth the extra cost in most applications. You don't need > silver wire. The manufacturer should have used an adequate > wire size (28 awg of better) and the cable should have a > "characteristic impedance" similar to the termination ^^^^^^^^^^^^^^^^^^^^^^^^^^ > resistance (usually about 115 ohms these days; was about > 132 ohms before "active" terminators). Use of Teflon(TM) is not just to increase physical strength, infact that is a secondary reason. The number 1 reason is that to make a ribbon cable that has a continuous characteristic impendance you must control wire spacing very carefully at all times. PVC just can't do this, when you bend PVC cable the wire spacing changes all over the place, with Teflon which is more rigid this does not happen. _Always_ use Teflon when doing 20 Mhz SCSI busses is the rule here at AAI. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-hardware Fri Sep 19 11:58:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA01060 for hardware-outgoing; Fri, 19 Sep 1997 11:58:35 -0700 (PDT) Received: from iafnl.es.iaf.nl (uucp@iafnl.es.iaf.nl [195.108.17.20]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA01039; Fri, 19 Sep 1997 11:58:26 -0700 (PDT) Received: by iafnl.es.iaf.nl with UUCP id AA07459 (5.67b/IDA-1.5); Fri, 19 Sep 1997 20:59:38 +0200 Received: (from wilko@localhost) by yedi.iaf.nl (8.8.5/8.6.12) id UAA03014; Fri, 19 Sep 1997 20:45:49 +0200 (MET DST) From: Wilko Bulte Message-Id: <199709191845.UAA03014@yedi.iaf.nl> Subject: Re: Warning! Sun archaeology [was Re: Is my NCR controller broken?] To: Don.Lewis@tsc.tdk.com (Don Lewis) Date: Fri, 19 Sep 1997 20:45:49 +0200 (MET DST) Cc: mjacob@feral.com, Don.Lewis@tsc.tdk.com, freebsd-hardware@FreeBSD.ORG, freebsd-scsi@FreeBSD.ORG In-Reply-To: <199709190125.SAA00739@salsa.gv.tsc.tdk.com> from "Don Lewis" at Sep 18, 97 06:25:48 pm X-Organisation: Private FreeBSD site - Arnhem, The Netherlands X-Pgp-Info: PGP public key at 'finger wilko@freefall.freebsd.org' X-Mailer: ELM [version 2.4 PL24 ME8a] Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk As Don Lewis wrote... > > On Sep 18, 5:25pm, Matthew Jacob wrote: > } Subject: Re: Is my NCR controller broken? > } >(this stuff predates SCSI 1) > } > } Wrong. > > I may have misremembered on this point. > > } > I believe the some Sun 3's actually > } > } Wrong. It was actually the sun 4/110. > > Looks like we're both right. I was unaware that the 4/110 was > similarly afflicted. From my sun-managers archives: > > First, I was reminded about something which, while not directly impacting > my situation, is well worth repeating. This is the infamous design > decision(?) by Sun to ground the "termination power" SCSI pin on the 3/60 > and 4/110 models, which means that a straight-through cable from either of > these models to a SCSI drive with termination power supplied tends to blow > the drive up! So while it's safe to plug an ex sun-3 drive onto a new > system, plugging a new drive onto a 3/60 is potentially a problem! It's ok > if you disable "termination power" on the drive, or cut the appropriate pin > of the SCSI cable. The Sun thing is definitely a hardware bug. But drives should not die a smoking death 'cause the TERMPOWER line should always be current-limited (fused) of 1.5 amps per the ANSI SCSI standard. In addition a low-drop (Schottky) diode is normally used to avoid powering switched-off devices thru the SCSI bus. Wilko _ ____________________________________________________________________ | / o / / _ Bulte email: wilko@yedi.iaf.nl http://www.tcja.nl/~wilko |/|/ / / /( (_) Arnhem, The Netherlands - Do, or do not. There is no 'try' ----------------------------------------------------------------------Yoda From owner-freebsd-hardware Fri Sep 19 17:15:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA20327 for hardware-outgoing; Fri, 19 Sep 1997 17:15:09 -0700 (PDT) Received: from verdi.nethelp.no (verdi.nethelp.no [195.1.171.130]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA20320 for ; Fri, 19 Sep 1997 17:15:06 -0700 (PDT) From: sthaug@nethelp.no Received: (qmail 28192 invoked by uid 1001); 20 Sep 1997 00:14:06 +0000 (GMT) To: hafner@forwiss.tu-muenchen.de Cc: freebsd-scsi@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Is my NCR controller broken? In-Reply-To: Your message of "Thu, 18 Sep 1997 08:57:34 GMT" References: <199709180857.IAA03695@pccog4.forwiss.tu-muenchen.de> X-Mailer: Mew version 1.05+ on Emacs 19.28.2 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Date: Sat, 20 Sep 1997 02:14:06 +0200 Message-ID: <28190.874714446@verdi.nethelp.no> Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I run a 486/DX2-66 (ASUS SP-3 with onboard NCR-810 SCSI > controller). This computer runs for about 3 years now (2.0.5, 2.1.0, > 2.1.5) > > Since about four weeks I keep getting SCSI resets and then the bus is > dead. No recovery! And it's really strange because the NCR controller > reports totally different errors before hanging. Here are the error > reports from the last three crashes (typed in by hand, so the actual > format may differ): > > ------------------------------------------------------------------------------- > > sd1(ncr0:1:0): internal error: cmd00 != 91=(vdsp[0] >> 24) > ncr0: timeout ccb=f19fbc00 (skip) I have a PVI486-SP3 with AMD 5x86-133 processor and ASUS PCI-SC200 SCSI controller. It works very well for me. I had *one* problem initially, which may be relevant: Some versions of the PVI486-SP3 motherboard (I have version 1.22) have an "IDE prefetch buffer". This *must be* turned off if you use PCI bus master cards (such as a 53c810 card). This is explicitly mentioned in my PVI486-SP3 manual at page 3-15. Before I turned off the "IDE prefetch buffer" in the BIOS, I got errors similar to yours. Steinar Haug, Nethelp consulting, sthaug@nethelp.no From owner-freebsd-hardware Fri Sep 19 19:32:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA26509 for hardware-outgoing; Fri, 19 Sep 1997 19:32:20 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA26500 for ; Fri, 19 Sep 1997 19:32:17 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) id WAA29514; Fri, 19 Sep 1997 22:32:59 -0400 (EDT) Message-ID: <19970919223259.22704@vinyl.quickweb.com> Date: Fri, 19 Sep 1997 22:32:59 -0400 From: Mark Mayo To: dg@root.com Cc: Robert Schien , hardware@FreeBSD.ORG Subject: Re: 'make world' on P6 system takes 3 h References: <199709100506.WAA02544@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199709100506.WAA02544@implode.root.com>; from David Greenman on Tue, Sep 09, 1997 at 10:06:25PM -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Tue, Sep 09, 1997 at 10:06:25PM -0700, David Greenman wrote: > >Here are the essential options from /etc/make.conf: > > > > > >CFLAGS= -O2 -m486 -pipe > > Make that "-O" and kill the -m486. The -O2 nearly doubles the compile time > and provides almost no measurable improvement in most cases. Just curious. Did the -m486 ever really do anything?? I've always used it for 'make world' and kernel compiles in my 486's, but now that I'm using a PPro I suppose it's useless, no? Is gcc ever going to support -m686, etc? I think there is a pentium optimized version (pgcc?) -- has anyone ever tried doing a make world or kernel compile with it to see if it' actually better? TIA, -Mark > > -DG > > David Greenman > Core-team/Principal Architect, The FreeBSD Project -- ------------------------------------------------------------------------ Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ------------------------------------------------------------------------ "The newest book, The Dilbert Future, took a broader view, describing how idiots will threaten every aspect of business, technology and society in the future." --Scott Adams From owner-freebsd-hardware Fri Sep 19 19:59:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA28186 for hardware-outgoing; Fri, 19 Sep 1997 19:59:43 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA28178 for ; Fri, 19 Sep 1997 19:59:37 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) id XAA29656; Fri, 19 Sep 1997 23:00:17 -0400 (EDT) Message-ID: <19970919230016.40089@vinyl.quickweb.com> Date: Fri, 19 Sep 1997 23:00:16 -0400 From: Mark Mayo To: freebsd-hardware@freebsd.org Subject: HD failure; possible causes?? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all. Well, this weekend I had a couple of CCD disk arrays go belly up, and I'm curious if anyone has had any experience with multiple disks crashing at once. Originally I thought one of the disks in the pair had crashed, but when I sent the drives to a data recovery place the guy informed me that both disks were pooched - both of them had the heads physically touch the media, destroying the platters and all data of course. One of the disks was an old Seagate Baracuda (the 2XL I think) and one was a relatively new Quantum (Fireball). I've had several of the older Baracudas blow up in the past, which is what I assumed happened here. Needless to say I was quite surprised to learn that the Quantum suffered the same death - at the same time presumably... According to the data recovery guy, when 2 disks fail like this simultaneously in about 80% of the cases he sees the cause of the problem was not the disks themselves, but the computer or disk tower. My disks were held in a pretty decent tower from Open Storage Solutions, with redundant power supplies and redundant cooling. Typically, very reliable disk towers and I've never had a problem with them in the past. Both te computer and the disk tower were plugged into a nice 1400VA APC UPS - so I really doubt there was a power surge or anything that got to the drives... Naturally I'm quite a bit worried that this might happen again, or to other disks in the tower... So this leaves me with a possible problem with the computer. The guy said "the motherboard"... I'm having a really hard time imagining how the computer could have cause the destruction of 2 disks. Yet the odds seems low enough for 2 disks to die in unison (plus the advice of the "expert") that I'm trying to imagine where the problem could lie. Maybe the old Adaptec 2940 SCSI controller? The only reasonable event I can think of would be some sort of static discharge along the SCSI cable. Anyhow, if any body has any experience with drive failures I'd love to hear from you!! This whole event has me very nervous! :-) TIA, -Mark -- ------------------------------------------------------------------------ Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ------------------------------------------------------------------------ "The newest book, The Dilbert Future, took a broader view, describing how idiots will threaten every aspect of business, technology and society in the future." --Scott Adams From owner-freebsd-hardware Fri Sep 19 22:53:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id WAA09186 for hardware-outgoing; Fri, 19 Sep 1997 22:53:37 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241] (may be forged)) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA09181 for ; Fri, 19 Sep 1997 22:53:34 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id WAA11851; Fri, 19 Sep 1997 22:53:19 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199709200553.WAA11851@GndRsh.aac.dev.com> Subject: Re: HD failure; possible causes?? In-Reply-To: <19970919230016.40089@vinyl.quickweb.com> from Mark Mayo at "Sep 19, 97 11:00:16 pm" To: mark@quickweb.com (Mark Mayo) Date: Fri, 19 Sep 1997 22:53:19 -0700 (PDT) Cc: freebsd-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-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Hi all. Well, this weekend I had a couple of CCD disk arrays go belly up, > and I'm curious if anyone has had any experience with multiple disks > crashing at once. > > Originally I thought one of the disks in the pair had crashed, but when I > sent the drives to a data recovery place the guy informed me that both > disks were pooched - both of them had the heads physically touch the > media, destroying the platters and all data of course. Your expert sounds like he is full of B.S. when he says to look at your motherboard as a possible cause. Plain and simple fact that an electronic device can not cause a physical failure of a disk drive. Vibration, shock, or another physical thing happened here if 2 drives in the same chassis died at the same time with the same ``heads hit the platter'' failure mode, no doubt about it in my mind at all. -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-hardware Fri Sep 19 23:07:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA10848 for hardware-outgoing; Fri, 19 Sep 1997 23:07:23 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA10843 for ; Fri, 19 Sep 1997 23:07:18 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) id CAA00820; Sat, 20 Sep 1997 02:07:41 -0400 (EDT) Message-ID: <19970920020741.24668@vinyl.quickweb.com> Date: Sat, 20 Sep 1997 02:07:41 -0400 From: Mark Mayo To: "Rodney W. Grimes" Cc: Mark Mayo , freebsd-hardware@FreeBSD.ORG Subject: Re: HD failure; possible causes?? References: <19970919230016.40089@vinyl.quickweb.com> <199709200553.WAA11851@GndRsh.aac.dev.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199709200553.WAA11851@GndRsh.aac.dev.com>; from Rodney W. Grimes on Fri, Sep 19, 1997 at 10:53:19PM -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, Sep 19, 1997 at 10:53:19PM -0700, Rodney W. Grimes wrote: > > Hi all. Well, this weekend I had a couple of CCD disk arrays go belly up, > > and I'm curious if anyone has had any experience with multiple disks > > crashing at once. > > > > Originally I thought one of the disks in the pair had crashed, but when I > > sent the drives to a data recovery place the guy informed me that both > > disks were pooched - both of them had the heads physically touch the > > media, destroying the platters and all data of course. > > Your expert sounds like he is full of B.S. when he says to look at > your motherboard as a possible cause. Plain and simple fact that an > electronic device can not cause a physical failure of a disk drive. It certainly sounded like B.S. to me - glad to hear I'm not the only one who things so. :-) > Vibration, shock, or another physical thing happened here if 2 drives > in the same chassis died at the same time with the same ``heads hit > the platter'' failure mode, no doubt about it in my mind at all. I would tend to agree. The only thing is that this is a rather large chassis locked away in a control room. About the only physical thing that could have shook it would be an earthquake. And trust me, about the only way an earthquake would occur in Southern Ontario is if the Mir space station fell out of orbit and somehow made it in one piece to the surface, impacting just outside my building. In other words, it ain't likely! :-) I'm pretty confident now that the Baracuda started vibrating like savage, and probably had a big hickup as it said its last words. The hickup was big enough to cause the disk above it to throw a hissy fit as well. Bummer. At least this seems most likely - I went and plugged the dead Baracuda in again and it did indeed vibrate enough to jitter across the table on its own... Thanks for the advice, I think you're exactly correct. -Mark > > -- > Rod Grimes rgrimes@gndrsh.aac.dev.com > Accurate Automation, Inc. Reliable computers for FreeBSD -- ------------------------------------------------------------------------ Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ------------------------------------------------------------------------ "The newest book, The Dilbert Future, took a broader view, describing how idiots will threaten every aspect of business, technology and society in the future." --Scott Adams From owner-freebsd-hardware Sat Sep 20 01:39:08 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id BAA06543 for hardware-outgoing; Sat, 20 Sep 1997 01:39:08 -0700 (PDT) Received: from MindBender.serv.net (mindbender.serv.net [205.153.153.98]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id BAA06522 for ; Sat, 20 Sep 1997 01:39:04 -0700 (PDT) Received: from localhost.HeadCandy.com (localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.8.6/8.7.3) with SMTP id BAA22167; Sat, 20 Sep 1997 01:37:27 -0700 (PDT) Message-Id: <199709200837.BAA22167@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: Mark Mayo cc: dg@root.com, Robert Schien , hardware@freebsd.org Subject: Re: 'make world' on P6 system takes 3 h In-reply-to: Your message of Fri, 19 Sep 97 22:32:59 -0400. <19970919223259.22704@vinyl.quickweb.com> Date: Sat, 20 Sep 1997 01:37:27 -0700 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Tue, Sep 09, 1997 at 10:06:25PM -0700, David Greenman wrote: >> >Here are the essential options from /etc/make.conf: >> > >> > >> >CFLAGS= -O2 -m486 -pipe >> >> Make that "-O" and kill the -m486. The -O2 nearly doubles the compile time >> and provides almost no measurable improvement in most cases. > >Just curious. Did the -m486 ever really do anything?? I've always used it >for 'make world' and kernel compiles in my 486's, but now that I'm using a >PPro I suppose it's useless, no? No, it's not useless. Think about it: -m486 assumes that you want code to be optimized for processors _better_ than a 386. Why would then removing it for a Pentium Pro be good? That means you're going back to code that works better on a 386. >From what I understand, most of the "benefit" from -m486 is that it aligns data on 16-byte boundaries instead of 4 or 8-byte boundaries. This supposedly helps cache loads happen more efficiently. Back in "the old days", when 486s ruled, the XFree86 guys said that -m486 gave them 10-20% improvement in speed, if I remember right. They said speed gains were similar on Pentiums (and why shouldn't they be? -- optimizations for 486 shouldn't hurt Pentiums). There's no reason to assume it should hurt a Pentium Pro -- in fact going back to 4 or 8-byte alignment is almost certainly going to be slower on the PPro, which is highly-optimized for 32-bit code, with 64-bit and 128-bit internal busses. Supposedly there were other minor things -m486 did. It chose instruction mixes slightly differently to prefer instructions that ran faster on the 486, but didn't run faster on 386s. Once again, this should, at worst, be neutral on P5s and P6s, and at best, be a slight performance boost. This is all from foggy memory over the last three or four years, so take it with a grain of salt. ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net Contract software development for Windows NT, Windows 95 and Unix. Windows NT and Unix server development in C++ and C. --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-hardware Sat Sep 20 05:05:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA01878 for hardware-outgoing; Sat, 20 Sep 1997 05:05:07 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA01872 for ; Sat, 20 Sep 1997 05:05:04 -0700 (PDT) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id FAA19765; Sat, 20 Sep 1997 05:05:48 -0700 (PDT) Message-Id: <199709201205.FAA19765@implode.root.com> To: "Michael L. VanLoon -- HeadCandy.com" cc: Mark Mayo , Robert Schien , hardware@freebsd.org Subject: Re: 'make world' on P6 system takes 3 h In-reply-to: Your message of "Sat, 20 Sep 1997 01:37:27 PDT." <199709200837.BAA22167@MindBender.serv.net> From: David Greenman Reply-To: dg@root.com Date: Sat, 20 Sep 1997 05:05:48 -0700 Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >>Just curious. Did the -m486 ever really do anything?? I've always used it >>for 'make world' and kernel compiles in my 486's, but now that I'm using a >>PPro I suppose it's useless, no? > >No, it's not useless. Think about it: -m486 assumes that you want >code to be optimized for processors _better_ than a 386. Why would >then removing it for a Pentium Pro be good? That means you're going >back to code that works better on a 386. -m486 means to specifically optimize for the 486. It does not mean to optimize for the greater than 386. >>From what I understand, most of the "benefit" from -m486 is that it >aligns data on 16-byte boundaries instead of 4 or 8-byte boundaries. >This supposedly helps cache loads happen more efficiently. Back in >"the old days", when 486s ruled, the XFree86 guys said that -m486 gave >them 10-20% improvement in speed, if I remember right. They said >speed gains were similar on Pentiums (and why shouldn't they be? -- >optimizations for 486 shouldn't hurt Pentiums). > >There's no reason to assume it should hurt a Pentium Pro -- in fact >going back to 4 or 8-byte alignment is almost certainly going to be >slower on the PPro, which is highly-optimized for 32-bit code, with >64-bit and 128-bit internal busses. Yes, but the cache works very different on the P6 and it's been found that the alignment just results in a larger, slower program. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hardware Sat Sep 20 05:14:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id FAA02185 for hardware-outgoing; Sat, 20 Sep 1997 05:14:46 -0700 (PDT) Received: from istari.home.net (cc158233-a.catv1.md.home.com [24.3.25.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id FAA02180 for ; Sat, 20 Sep 1997 05:14:44 -0700 (PDT) Received: (from sjr@localhost) by istari.home.net (8.8.7/8.8.6) id IAA08327; Sat, 20 Sep 1997 08:14:40 -0400 (EDT) Date: Sat, 20 Sep 1997 08:14:40 -0400 (EDT) From: "Stephen J. Roznowski" Message-Id: <199709201214.IAA08327@istari.home.net> To: mark@quickweb.com, freebsd-hardware@FreeBSD.ORG Subject: Re: HD failure; possible causes?? In-Reply-To: Mail from 'Mark Mayo ' dated: Fri, 19 Sep 1997 23:00:16 -0400 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > From: Mark Mayo > Subject: HD failure; possible causes?? > > Hi all. Well, this weekend I had a couple of CCD disk arrays go belly up, > and I'm curious if anyone has had any experience with multiple disks > crashing at once. While it sounds like you've figured out this problem, one thing to remember when you are building disk arrays is to use disks from different production runs. When you start to approach the MTTF for drives, the ones in the same production run tend to fail at about the same time (i.e. the bell curve for MTTF is more of a spike). Getting drives from different production runs gives you a larger bell.... -SR From owner-freebsd-hardware Sat Sep 20 07:30:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA07276 for hardware-outgoing; Sat, 20 Sep 1997 07:30:23 -0700 (PDT) Received: from persprog.com (root@persprog.com [204.215.255.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id HAA07271 for ; Sat, 20 Sep 1997 07:30:19 -0700 (PDT) Received: by persprog.com (8.7.5/4.10) id JAA04788; Sat, 20 Sep 1997 09:24:37 -0500 Received: from dave.ppi.com(192.2.2.6) by cerberus.ppi.com via smap (V1.3) id sma004786; Sat Sep 20 10:24:28 1997 Message-ID: <3423DC8B.F5A1D720@persprog.com> Date: Sat, 20 Sep 1997 10:24:11 -0400 From: Dave Alderman Reply-To: dave@persprog.com Organization: Personalized Programming, Inc X-Mailer: Mozilla 4.0 [en] (Win95; U) MIME-Version: 1.0 To: Mark Mayo CC: freebsd-hardware@FreeBSD.ORG Subject: Re: HD failure; possible causes?? X-Priority: 3 (Normal) References: <19970919230016.40089@vinyl.quickweb.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Mark Mayo wrote: > > Hi all. Well, this weekend I had a couple of CCD disk arrays go belly > up, > and I'm curious if anyone has had any experience with multiple disks > crashing at once. By any chance, is the air conditioning turned off on the weekend? -- "Going down to South Park - going to leave my woes behind..." David W. Alderman dave@persprog.com From owner-freebsd-hardware Sat Sep 20 09:05:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA12244 for hardware-outgoing; Sat, 20 Sep 1997 09:05:45 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA12238 for ; Sat, 20 Sep 1997 09:05:39 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) id MAA05129; Sat, 20 Sep 1997 12:06:21 -0400 (EDT) Message-ID: <19970920120621.31536@vinyl.quickweb.com> Date: Sat, 20 Sep 1997 12:06:21 -0400 From: Mark Mayo To: dave@persprog.com Cc: Mark Mayo , freebsd-hardware@FreeBSD.ORG Subject: Re: HD failure; possible causes?? References: <19970919230016.40089@vinyl.quickweb.com> <3423DC8B.F5A1D720@persprog.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <3423DC8B.F5A1D720@persprog.com>; from Dave Alderman on Sat, Sep 20, 1997 at 10:24:11AM -0400 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, Sep 20, 1997 at 10:24:11AM -0400, Dave Alderman wrote: > Mark Mayo wrote: > > > > Hi all. Well, this weekend I had a couple of CCD disk arrays go belly > > up, > > and I'm curious if anyone has had any experience with multiple disks > > crashing at once. > > By any chance, is the air conditioning turned off on the weekend? No, and when I got there the fans were still working just fine. I don't think it was a cooling problem, but it certainly might have cotributed somehow. The leasing reasoning seems to suggest that vibration killed them. Time for a better disk tower I suppose... or better disks at least. cya, -Mark > > -- > "Going down to South Park - going to leave my woes behind..." > David W. Alderman dave@persprog.com -- ------------------------------------------------------------------------ Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ------------------------------------------------------------------------ "The newest book, The Dilbert Future, took a broader view, describing how idiots will threaten every aspect of business, technology and society in the future." --Scott Adams From owner-freebsd-hardware Sat Sep 20 10:10:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA16018 for hardware-outgoing; Sat, 20 Sep 1997 10:10:16 -0700 (PDT) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA16007 for ; Sat, 20 Sep 1997 10:10:08 -0700 (PDT) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id TAA05096; Sat, 20 Sep 1997 19:08:26 +0200 (CEST) To: Mark Mayo cc: dave@persprog.com, freebsd-hardware@freebsd.org Subject: Re: HD failure; possible causes?? In-reply-to: Your message of "Sat, 20 Sep 1997 12:06:21 EDT." <19970920120621.31536@vinyl.quickweb.com> Date: Sat, 20 Sep 1997 19:08:26 +0200 Message-ID: <5094.874775306@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <19970920120621.31536@vinyl.quickweb.com>, Mark Mayo writes: >On Sat, Sep 20, 1997 at 10:24:11AM -0400, Dave Alderman wrote: >> Mark Mayo wrote: >> > >> > Hi all. Well, this weekend I had a couple of CCD disk arrays go belly >> > up, >> > and I'm curious if anyone has had any experience with multiple disks >> > crashing at once. >> >> By any chance, is the air conditioning turned off on the weekend? > >No, and when I got there the fans were still working just fine. I don't >think it was a cooling problem, but it certainly might have cotributed >somehow. The leasing reasoning seems to suggest that vibration killed >them. Time for a better disk tower I suppose... or better disks at least. I saw a diskpack suffer instant death once because of a hammerdrill going into the wall from the other side. At a bad frequency it takes nothing. -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-hardware Sat Sep 20 10:14:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA16221 for hardware-outgoing; Sat, 20 Sep 1997 10:14:02 -0700 (PDT) Received: from loch2.prz.tu-berlin.de (loch2.prz.tu-berlin.de [130.149.237.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA16215 for ; Sat, 20 Sep 1997 10:13:57 -0700 (PDT) Received: from ppc.in-brb.de (uucp@localhost) by loch2.prz.tu-berlin.de (8.8.6-r-beta/8.8.6) with UUCP id TAA23440 for freebsd-hardware@freebsd.org; Sat, 20 Sep 1997 19:13:47 +0200 (CEST) Received: from ppc.in-brb.de (ppc.in-brb.de [127.0.0.1]) by ppc.in-brb.de (8.8.6/8.8.6) with ESMTP id TAA06385 for ; Sat, 20 Sep 1997 19:12:19 +0200 (CEST) Message-ID: <342403F2.31D0B9D3@ppc.in-brb.de> Date: Sat, 20 Sep 1997 19:12:18 +0200 From: Philipp Schmidt Reply-To: philipp@in-brb.de X-Mailer: Mozilla 4.03b8 [en] (X11; I; FreeBSD 2.2.2-RELEASE i386) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: EtherExpress 16 - How to use with 2.2.2 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hello, I got an EtherExpress 16 an wanted to use it with FreeBSD 2.2.2. I heared the driver has been removed from the Kernel. How to use it??? AVE! Philipp -- Philipp Schmidt | philipp@in-brb.de | philippOnline TEL:++49(30)6635514 | | FAX:++49(30)6635514 | +-> http://home.pages.de/~phils/ -----------------------+------------------------------------- INTERNET in Brandenburg? IN-BRB! -> info@in-brb.de From owner-freebsd-hardware Sat Sep 20 11:16:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA19873 for hardware-outgoing; Sat, 20 Sep 1997 11:16:56 -0700 (PDT) Received: from peeper.my.domain ([208.128.8.69]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA19866 for ; Sat, 20 Sep 1997 11:16:51 -0700 (PDT) Received: (from tom@localhost) by peeper.my.domain (8.8.7/8.7.3) id NAA05399; Sat, 20 Sep 1997 13:16:34 -0500 (CDT) Message-ID: <19970920131634.08085@my.domain> Date: Sat, 20 Sep 1997 13:16:34 -0500 From: Tom Jackson To: freebsd-hardware@FreeBSD.ORG Subject: Opinions please Was: Micropolis Runs Too HOT! References: <199709132341.NAA23393@pegasus.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199709132341.NAA23393@pegasus.com>; from Richard Foulk on Sat, Sep 13, 1997 at 01:41:23PM -1000 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In my previous post I disCussed the heating situation with this 7200rpm scsi Micropolis drive. I now have two 4-1/2in cooling fans on the midi case, one blowing over the Mic located in two 5-1/4 in bays and one sucking out at the back of the case. Although I have return approval for a Fujitsu M2954S, many claim it will run just hot as the Micropolis. I have run iozone on all of my drives trying to decide if I should exchange. Although the Mic seems to write at a good rate the read specs don't look good at all. Would anyone with good knowledge of this please comment. I need to decide soon. iozone single results: --------------------------------------------------------- In the three runs, done separately, the disk cache sized to 11 megabytes. sd0 is a Micropolis 4421 2.1gb 5400rpm scsi, sd1 is a Micropolis 4345 4.5gb 7200rpm scsi, and sd2 is a Fujitsu M1606sau 1.08gb 5400rpm scsi. IOZONE: Performance Test of Sequential File I/O -- V2.01 (10/21/94) By Bill Norcott Operating System: FreeBSD 2.x -- using fsync() Send comments to: b_norcott@xway.com IOZONE writes a 44 Megabyte sequential file consisting of 5632 records which are each 8192 bytes in length. It then reads the file. It prints the bytes-per-second rate at which the computer can read and write files. Writing the 44 Megabyte file, '/usr/ports/iozone.tmp'...11.265625 seconds Reading the file...7.914062 seconds on sd0 IOZONE performance measurements: 4095409 bytes/second for writing the file 5829792 bytes/second for reading the file <--- Writing the 44 Megabyte file, '/usr/iozone.tmp'...6.625000 seconds Reading the file...6.257812 seconds on sd1 IOZONE performance measurements: 6964127 bytes/second for writing the file 7372759 bytes/second for reading the file <--- Writing the 44 Megabyte file, '/mnt1/iozone.tmp'...6.335938 seconds Reading the file...5.953125 seconds on sd2 IOZONE performance measurements: 7281849 bytes/second for writing the file 7750105 bytes/second for reading the file ----------------------------------------------------------- iozone concurrent results: Concurrent run to all three drives. Disk cache sized itself to 11mb. IOZONE: Performance Test of Sequential File I/O -- V2.01 (10/21/94) By Bill Norcott Operating System: FreeBSD 2.x -- using fsync() Send comments to: b_norcott@xway.com IOZONE writes a 44 Megabyte sequential file consisting of 5632 records which are each 8192 bytes in length. It then reads the file. It prints the bytes-per-second rate at which the computer can read and write files. Writing the 44 Megabyte file, '/usr/ports/iozone.tmp'...11.250000 seconds Reading the file...7.453125 seconds on sd0 (MC4421) IOZONE performance measurements: 4101097 bytes/second for writing the file 6190335 bytes/second for reading the file <--- Writing the 44 Megabyte file, '/usr/iozone.tmp'...6.585938 seconds Reading the file...6.304688 seconds on sd1 (MC4345NS) IOZONE performance measurements: 7005433 bytes/second for writing the file 7317943 bytes/second for reading the file <--- Writing the 44 Megabyte file, '/mnt1/iozone.tmp'...6.359375 seconds Reading the file...5.867188 seconds on sd2 (Fuj M1606S) IOZONE performance measurements: 7255012 bytes/second for writing the file 7863621 bytes/second for reading the file I can't tell if this bad performance or the disk might be damaged Tom --- From owner-freebsd-hardware Sat Sep 20 11:26:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA20410 for hardware-outgoing; Sat, 20 Sep 1997 11:26:26 -0700 (PDT) Received: from po1.glue.umd.edu (root@po1.glue.umd.edu [128.8.10.97]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA20404 for ; Sat, 20 Sep 1997 11:26:23 -0700 (PDT) Received: from aliasing.eng.umd.edu (crb@aliasing.eng.umd.edu [129.2.98.137]) by po1.glue.umd.edu (8.8.7/8.8.7) with ESMTP id OAA08888; Sat, 20 Sep 1997 14:26:12 -0400 (EDT) Received: from localhost (crb@localhost) by aliasing.eng.umd.edu (8.8.7/8.8.7) with SMTP id OAA01386; Sat, 20 Sep 1997 14:26:07 -0400 (EDT) X-Authentication-Warning: aliasing.eng.umd.edu: crb owned process doing -bs Date: Sat, 20 Sep 1997 14:26:05 -0400 (EDT) From: "Christopher R. Bowman" X-Sender: crb@aliasing.eng.umd.edu To: Mark Mayo cc: freebsd-hardware@FreeBSD.ORG Subject: Re: HD failure; possible causes?? In-Reply-To: <19970919230016.40089@vinyl.quickweb.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Fri, 19 Sep 1997, Mark Mayo wrote: All that air conditioning, and power conditioning and UPS junk all sits on one side of the disk drives, not between them, I mean if you follow the current it comes out of the wall into the ups then into the redundant power supply, then to the drives, in all likely hood the drive power is tapped off them same point, their is no isolation between them, so what if the head crash of one drive cause a transient dip or spike in the regulated output of the power supply inside the case, air conditioning and UPS wont really help this. I am an electrical engineer (least that's what my degree sais) and this means that I am absolutlely posatively qualified to speak on this subject with NO credability whatsoever, so please take what I say with a large pile of salt. I am just speculating since it is unlikely you will ever really know what happened. > Hi all. Well, this weekend I had a couple of CCD disk arrays go belly up, > and I'm curious if anyone has had any experience with multiple disks > crashing at once. > > Originally I thought one of the disks in the pair had crashed, but when I > sent the drives to a data recovery place the guy informed me that both > disks were pooched - both of them had the heads physically touch the > media, destroying the platters and all data of course. > > One of the disks was an old Seagate Baracuda (the 2XL I think) and one > was a relatively new Quantum (Fireball). I've had several of the older > Baracudas blow up in the past, which is what I assumed happened here. > Needless to say I was quite surprised to learn that the Quantum suffered > the same death - at the same time presumably... According to the > data recovery guy, when 2 disks fail like this simultaneously in about > 80% of the cases he sees the cause of the problem was not the disks > themselves, but the computer or disk tower. My disks were held in a > pretty decent tower from Open Storage Solutions, with redundant power > supplies and redundant cooling. Typically, very reliable disk towers and > I've never had a problem with them in the past. Both te computer and the > disk tower were plugged into a nice 1400VA APC UPS - so I really doubt there > was a power surge or anything that got to the drives... > > Naturally I'm quite a bit worried that this might happen again, or to other > disks in the tower... So this leaves me with a possible problem with the > computer. The guy said "the motherboard"... I'm having a really hard time > imagining how the computer could have cause the destruction of 2 disks. Yet > the odds seems low enough for 2 disks to die in unison (plus the advice of > the "expert") that I'm trying to imagine where the problem could lie. > Maybe the old Adaptec 2940 SCSI controller? The only reasonable event I > can think of would be some sort of static discharge along the SCSI cable. > > Anyhow, if any body has any experience with drive failures I'd love to hear > from you!! This whole event has me very nervous! :-) > > TIA, > -Mark > > > -- > ------------------------------------------------------------------------ > Mark Mayo mark@quickweb.com > RingZero Comp. http://vinyl.quickweb.com/mark > > finger mark@quickweb.com for my PGP key and GCS code > ------------------------------------------------------------------------ > "The newest book, The Dilbert Future, took a broader view, describing how > idiots will threaten every aspect of business, technology and society in > the future." --Scott Adams > --------- Christopher R. Bowman crb@Glue.umd.edu My home page From owner-freebsd-hardware Sat Sep 20 12:24:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA22730 for hardware-outgoing; Sat, 20 Sep 1997 12:24:10 -0700 (PDT) Received: from vinyl.quickweb.com (vinyl.quickweb.com [206.222.77.8]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA22693 for ; Sat, 20 Sep 1997 12:24:00 -0700 (PDT) Received: (from mark@localhost) by vinyl.quickweb.com (8.8.5/8.6.12) id PAA06121; Sat, 20 Sep 1997 15:24:40 -0400 (EDT) Message-ID: <19970920152440.11922@vinyl.quickweb.com> Date: Sat, 20 Sep 1997 15:24:40 -0400 From: Mark Mayo To: "Christopher R. Bowman" Cc: Mark Mayo , freebsd-hardware@FreeBSD.ORG Subject: Re: HD failure; possible causes?? References: <19970919230016.40089@vinyl.quickweb.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: ; from Christopher R. Bowman on Sat, Sep 20, 1997 at 02:26:05PM -0400 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Sat, Sep 20, 1997 at 02:26:05PM -0400, Christopher R. Bowman wrote: > On Fri, 19 Sep 1997, Mark Mayo wrote: > > All that air conditioning, and power conditioning and UPS junk all sits > on one side of the disk drives, not between them, I mean if you follow > the current it comes out of the wall into the ups then into the redundant > power supply, then to the drives, in all likely hood the drive power > is tapped off them same point, their is no isolation between them, so > what if the head crash of one drive cause a transient dip or spike in the > regulated output of the power supply inside the case, air conditioning > and UPS wont really help this. Good point. This could also be the cause I suppose, although I would have assumed that a decent power supply would have taken care of this. Another option to add to the list! :-) You're certainly right that I will probably never know what really happened - I'd just like to reduce the likelyhood of it ever happening again. Ater plugging the bad Baracuda back in an watching it "walk" across the table, I'm quite sure now that this would have been enough to toast the other disks - the vibration was much worse than I would have ever expected. My case would have dampened the vibration somewhat, but apparently not enough... How do the big RAID towers get around this problem?? I was lucky in the sense that I only had 3 disks hanging off the chasis - as Poul noted a vibration like I experienced (at the right frequency) would probably have been enough to nuke all 8 drives if the bays had been full... I guess you could use rubber mounts or something?? Just curious :-) -Mark > > I am an electrical engineer (least that's what my degree sais) and this > means that I am absolutlely posatively qualified to speak on this subject > with NO credability whatsoever, so please take what I say with a large > pile of salt. I am just speculating since it is unlikely you will ever > really know what happened. > > > Hi all. Well, this weekend I had a couple of CCD disk arrays go belly up, > > and I'm curious if anyone has had any experience with multiple disks > > crashing at once. > > > > Originally I thought one of the disks in the pair had crashed, but when I > > sent the drives to a data recovery place the guy informed me that both > > disks were pooched - both of them had the heads physically touch the > > media, destroying the platters and all data of course. > > > > One of the disks was an old Seagate Baracuda (the 2XL I think) and one > > was a relatively new Quantum (Fireball). I've had several of the older > > Baracudas blow up in the past, which is what I assumed happened here. > > Needless to say I was quite surprised to learn that the Quantum suffered > > the same death - at the same time presumably... According to the > > data recovery guy, when 2 disks fail like this simultaneously in about > > 80% of the cases he sees the cause of the problem was not the disks > > themselves, but the computer or disk tower. My disks were held in a > > pretty decent tower from Open Storage Solutions, with redundant power > > supplies and redundant cooling. Typically, very reliable disk towers and > > I've never had a problem with them in the past. Both te computer and the > > disk tower were plugged into a nice 1400VA APC UPS - so I really doubt there > > was a power surge or anything that got to the drives... > > > > Naturally I'm quite a bit worried that this might happen again, or to other > > disks in the tower... So this leaves me with a possible problem with the > > computer. The guy said "the motherboard"... I'm having a really hard time > > imagining how the computer could have cause the destruction of 2 disks. Yet > > the odds seems low enough for 2 disks to die in unison (plus the advice of > > the "expert") that I'm trying to imagine where the problem could lie. > > Maybe the old Adaptec 2940 SCSI controller? The only reasonable event I > > can think of would be some sort of static discharge along the SCSI cable. > > > > Anyhow, if any body has any experience with drive failures I'd love to hear > > from you!! This whole event has me very nervous! :-) > > > > TIA, > > -Mark > > > > > > -- > > ------------------------------------------------------------------------ > > Mark Mayo mark@quickweb.com > > RingZero Comp. http://vinyl.quickweb.com/mark > > > > finger mark@quickweb.com for my PGP key and GCS code > > ------------------------------------------------------------------------ > > "The newest book, The Dilbert Future, took a broader view, describing how > > idiots will threaten every aspect of business, technology and society in > > the future." --Scott Adams > > > > --------- > Christopher R. Bowman > crb@Glue.umd.edu > My home page -- ------------------------------------------------------------------------ Mark Mayo mark@quickweb.com RingZero Comp. http://vinyl.quickweb.com/mark finger mark@quickweb.com for my PGP key and GCS code ------------------------------------------------------------------------ "The newest book, The Dilbert Future, took a broader view, describing how idiots will threaten every aspect of business, technology and society in the future." --Scott Adams From owner-freebsd-hardware Sat Sep 20 16:04:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA01348 for hardware-outgoing; Sat, 20 Sep 1997 16:04:55 -0700 (PDT) Received: from pompano.pcola.gulf.net (root@pompano.pcola.gulf.net [198.69.72.14]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id QAA01343 for ; Sat, 20 Sep 1997 16:04:49 -0700 (PDT) Received: from golan (octopus17.pcola.gulf.net [198.69.79.113]) by pompano.pcola.gulf.net (8.8.6/8.7.3) with SMTP id SAA08814 for ; Sat, 20 Sep 1997 18:04:43 -0500 (CDT) Message-ID: <34245574.7B4@gulf.net> Date: Sat, 20 Sep 1997 18:00:04 -0500 From: Gary Bond X-Mailer: Mozilla 3.01Gold (Win95; I) MIME-Version: 1.0 To: freebsd-hardware@FreeBSD.ORG Subject: EISA ethernet adapter Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello all, I recently got some SMC Elite 32c Ultra EISA ethernet cards. Has anyone used these sucessfully with FreeBSD. I can't get the card recognized, and suspect that there is probably not a driver to support it. Just looking for a faster transfer since these cards are bus mastering and multitasking. Also referred to as the 82M32. Anyone have ideas or suggestions. Thanks in advance, gary \o/ | / \