From owner-freebsd-hardware Sun Aug 17 03:11:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA20896 for hardware-outgoing; Sun, 17 Aug 1997 03:11:49 -0700 (PDT) Received: from critter.dk.tfs.com (critter.phk.freebsd.dk [195.8.133.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA20889; Sun, 17 Aug 1997 03:11:41 -0700 (PDT) Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.6/8.8.5) with ESMTP id JAA09308; Sat, 16 Aug 1997 09:20:53 +0200 (CEST) To: Michael Smith cc: Nicolas.Souchu@prism.uvsq.fr, freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Parallel port developpements - ppbus In-reply-to: Your message of "Sat, 16 Aug 1997 11:08:19 +0930." <199708160138.LAA29530@genesis.atrad.adelaide.edu.au> Date: Sat, 16 Aug 1997 09:20:52 +0200 Message-ID: <9306.871716052@critter.dk.tfs.com> From: Poul-Henning Kamp Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199708160138.LAA29530@genesis.atrad.adelaide.edu.au>, Michael Smith writes: >Poul-Henning Kamp stands accused of saying: >> >> >Anyway, tell us which parallel-port-hardware should be first ported. >> >--------------------------------------------------------------------------- >- >> >> Well, how about parallel printers and the PLIP/LPIP support ? :-) > >Printers are already (sort of) supported with the 'nlpt' driver. If you >could work out why interrupts don't work, that'd be great of course. > >As for PLIP, well, Jordan sez you're Mr PLIP, so I think this one is best >done with your help... Come on guys... PLIP is so simple as it can be... I don't have the time at this point to go back and kick PLIP again... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-hardware Sun Aug 17 03:11:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA20926 for hardware-outgoing; Sun, 17 Aug 1997 03:11:58 -0700 (PDT) Received: from critter.dk.tfs.com (critter.phk.freebsd.dk [195.8.133.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA20910; Sun, 17 Aug 1997 03:11:51 -0700 (PDT) Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.6/8.8.5) with ESMTP id UAA06619; Fri, 15 Aug 1997 20:42:02 +0200 (CEST) To: Nicolas Souchu cc: FreeBSD hackers , FreeBSD hardware Subject: Re: Parallel port developpements - ppbus In-reply-to: Your message of "Fri, 15 Aug 1997 20:41:23 -0000." <33F4BEF3.446B9B3D@prism.uvsq.fr> Date: Fri, 15 Aug 1997 20:42:02 +0200 Message-ID: <6617.871670522@critter.dk.tfs.com> From: Poul-Henning Kamp Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <33F4BEF3.446B9B3D@prism.uvsq.fr>, Nicolas Souchu writes: > > - plip should of course. > We want to move it to a standalone file... plip.c? it should probably go in netinet/if_lp.c for consistency... -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-hardware Sun Aug 17 03:38:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA22204 for hardware-outgoing; Sun, 17 Aug 1997 03:38:04 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA22196; Sun, 17 Aug 1997 03:37:59 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id UAA04335; Sun, 17 Aug 1997 20:07:42 +0930 (CST) From: Michael Smith Message-Id: <199708171037.UAA04335@genesis.atrad.adelaide.edu.au> Subject: Re: Parallel port developpements - ppbus In-Reply-To: <6617.871670522@critter.dk.tfs.com> from Poul-Henning Kamp at "Aug 15, 97 08:42:02 pm" To: phk@critter.dk.tfs.com (Poul-Henning Kamp) Date: Sun, 17 Aug 1997 20:07:42 +0930 (CST) Cc: Nicolas.Souchu@prism.uvsq.fr, freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp stands accused of saying: > In message <33F4BEF3.446B9B3D@prism.uvsq.fr>, Nicolas Souchu writes: > > > > - plip should of course. > > We want to move it to a standalone file... plip.c? > > it should probably go in netinet/if_lp.c for consistency... I don't think so. It certainly doesn't belong in the "internet" networking code. The tradition with interface drivers seems to be to park them at the level of the device they drive, ie. ISA network hardware drivers are in the ISA bus-specific directory, so it would make the most sense to me to put it in dev/ppbus/if_lp.c > Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Sun Aug 17 06:06:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA26526 for hardware-outgoing; Sun, 17 Aug 1997 06:06:54 -0700 (PDT) Received: from godzilla.zeta.org.au (godzilla.zeta.org.au [203.2.228.19]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA26519; Sun, 17 Aug 1997 06:06:45 -0700 (PDT) Received: (from bde@localhost) by godzilla.zeta.org.au (8.8.5/8.6.9) id XAA17339; Sun, 17 Aug 1997 23:03:13 +1000 Date: Sun, 17 Aug 1997 23:03:13 +1000 From: Bruce Evans Message-Id: <199708171303.XAA17339@godzilla.zeta.org.au> To: msmith@atrad.adelaide.edu.au, phk@critter.dk.tfs.com Subject: Re: Parallel port developpements - ppbus Cc: freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG, Nicolas.Souchu@prism.uvsq.fr Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >>[plip driver] >I don't think so. It certainly doesn't belong in the "internet" networking >code. The tradition with interface drivers seems to be to park them at >the level of the device they drive, ie. ISA network hardware drivers >are in the ISA bus-specific directory, so it would make the most sense >to me to put it in dev/ppbus/if_lp.c It makes no sense to put it there either, since sys/dev is for bus-independent (parts of) drivers. Bruce From owner-freebsd-hardware Sun Aug 17 06:35:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA27512 for hardware-outgoing; Sun, 17 Aug 1997 06:35:39 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA27506; Sun, 17 Aug 1997 06:35:34 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id XAA06011; Sun, 17 Aug 1997 23:05:19 +0930 (CST) From: Michael Smith Message-Id: <199708171335.XAA06011@genesis.atrad.adelaide.edu.au> Subject: Re: Parallel port developpements - ppbus In-Reply-To: <199708171303.XAA17339@godzilla.zeta.org.au> from Bruce Evans at "Aug 17, 97 11:03:13 pm" To: bde@zeta.org.au (Bruce Evans) Date: Sun, 17 Aug 1997 23:05:18 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, phk@critter.dk.tfs.com, freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG, Nicolas.Souchu@prism.uvsq.fr X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bruce Evans stands accused of saying: > >>[plip driver] > > >I don't think so. It certainly doesn't belong in the "internet" networking > >code. The tradition with interface drivers seems to be to park them at > >the level of the device they drive, ie. ISA network hardware drivers > >are in the ISA bus-specific directory, so it would make the most sense > >to me to put it in dev/ppbus/if_lp.c > > It makes no sense to put it there either, since sys/dev is for > bus-independent (parts of) drivers. Well, then I'd better move the ppbus stuff. It makes no sense to me to have Yet Another toplevel directory for this though, and sys/dev strikes me as being the ideal place for architecture-independent device drivers. Any consensus on this? -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Sun Aug 17 08:39:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA05133 for hardware-outgoing; Sun, 17 Aug 1997 08:39:44 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA05113; Sun, 17 Aug 1997 08:39:38 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id BAA06417; Mon, 18 Aug 1997 01:09:14 +0930 (CST) From: Michael Smith Message-Id: <199708171539.BAA06417@genesis.atrad.adelaide.edu.au> Subject: Re: Parallel port developpements - ppbus In-Reply-To: <9306.871716052@critter.dk.tfs.com> from Poul-Henning Kamp at "Aug 16, 97 09:20:52 am" To: phk@critter.dk.tfs.com (Poul-Henning Kamp) Date: Mon, 18 Aug 1997 01:09:14 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, Nicolas.Souchu@prism.uvsq.fr, freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Poul-Henning Kamp stands accused of saying: > > > >As for PLIP, well, Jordan sez you're Mr PLIP, so I think this one is best > >done with your help... > > Come on guys... PLIP is so simple as it can be... I don't have the time > at this point to go back and kick PLIP again... If it's really that simple; where can I find some documentation on it? Is there a Linux mini-hownotto or something that spells it out in terms a poor simple brain like mine could handle? Is it likely to work on a port that's open to shared use? > Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Sun Aug 17 10:18:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA10139 for hardware-outgoing; Sun, 17 Aug 1997 10:18:40 -0700 (PDT) Received: from critter.dk.tfs.com (critter.phk.freebsd.dk [195.8.133.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA10132; Sun, 17 Aug 1997 10:18:33 -0700 (PDT) Received: from critter.dk.tfs.com (localhost [127.0.0.1]) by critter.dk.tfs.com (8.8.6/8.8.5) with ESMTP id TAA11280; Sun, 17 Aug 1997 19:13:03 +0200 (CEST) To: Michael Smith cc: Nicolas.Souchu@prism.uvsq.fr, freebsd-hackers@freebsd.org, freebsd-hardware@freebsd.org Subject: Re: Parallel port developpements - ppbus In-reply-to: Your message of "Mon, 18 Aug 1997 01:09:14 +0930." <199708171539.BAA06417@genesis.atrad.adelaide.edu.au> Date: Sun, 17 Aug 1997 19:13:03 +0200 Message-ID: <11278.871837983@critter.dk.tfs.com> From: Poul-Henning Kamp Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk In message <199708171539.BAA06417@genesis.atrad.adelaide.edu.au>, Michael Smith writes: >Poul-Henning Kamp stands accused of saying: >> > >> >As for PLIP, well, Jordan sez you're Mr PLIP, so I think this one is best >> >done with your help... >> >> Come on guys... PLIP is so simple as it can be... I don't have the time >> at this point to go back and kick PLIP again... > >If it's really that simple; where can I find some documentation on it? >Is there a Linux mini-hownotto or something that spells it out in >terms a poor simple brain like mine could handle? sys/i386/isa/lpt.c :-) >Is it likely to work on a port that's open to shared use? no. -- Poul-Henning Kamp | phk@FreeBSD.ORG FreeBSD Core-team. http://www.freebsd.org/~phk | phk@login.dknet.dk Private mailbox. whois: [PHK] | phk@tfs.com TRW Financial Systems, Inc. Power and ignorance is a disgusting cocktail. From owner-freebsd-hardware Sun Aug 17 11:03:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA12777 for hardware-outgoing; Sun, 17 Aug 1997 11:03:18 -0700 (PDT) Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.235]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA12770 for ; Sun, 17 Aug 1997 11:03:05 -0700 (PDT) Received: from srmail.sr.hp.com (srmail.sr.hp.com [15.4.45.14]) by palrel1.hp.com (8.8.6/8.8.5) with ESMTP id LAA10679 for ; Sun, 17 Aug 1997 11:03:03 -0700 (PDT) Received: from mina.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA014910983; Sun, 17 Aug 1997 11:03:03 -0700 Received: from mina.sr.hp.com by mina.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA104260982; Sun, 17 Aug 1997 11:03:02 -0700 Message-Id: <199708171803.AA104260982@mina.sr.hp.com> To: hardware@FreeBSD.ORG Subject: Quiet SCSI disk? Reply-To: darrylo@sr.hp.com Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Sun, 17 Aug 1997 11:03:02 -0700 From: Darryl Okahata Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, Can anyone recommend a decent, but QUIET, SCSI disk? I'm currently using a 4GB Quantum Atlas (I, not II), and the "jet engine whine" coming from the drive is driving me crazy (and probably deaf, in one ear ;-). Thanks, -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-hardware Sun Aug 17 12:30:18 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA16943 for hardware-outgoing; Sun, 17 Aug 1997 12:30:18 -0700 (PDT) Received: from tok.qiv.com ([204.214.141.211]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA16926 for ; Sun, 17 Aug 1997 12:30:14 -0700 (PDT) Received: (from uucp@localhost) by tok.qiv.com (8.8.6/8.8.5) with UUCP id OAA17960; Sun, 17 Aug 1997 14:30:08 -0500 (CDT) Received: from localhost (jdn@localhost) by acp.qiv.com (8.8.6/8.8.5) with SMTP id OAA00851; Sun, 17 Aug 1997 14:23:23 -0500 (CDT) X-Authentication-Warning: acp.qiv.com: jdn owned process doing -bs Date: Sun, 17 Aug 1997 14:23:23 -0500 (CDT) From: "Jay D. Nelson" To: darrylo@sr.hp.com cc: hardware@FreeBSD.ORG Subject: Re: Quiet SCSI disk? In-Reply-To: <199708171803.AA104260982@mina.sr.hp.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 had the same problem with Fujitsu. Try Seagate Hawks -- much quiter. You may want to change your fans, too. -- Jay On Sun, 17 Aug 1997, Darryl Okahata wrote: >Hi, > > Can anyone recommend a decent, but QUIET, SCSI disk? I'm currently >using a 4GB Quantum Atlas (I, not II), and the "jet engine whine" coming >from the drive is driving me crazy (and probably deaf, in one ear ;-). > > Thanks, > -- Darryl Okahata > Internet: darrylo@sr.hp.com > >DISCLAIMER: this message is the author's personal opinion and does not >constitute the support, opinion, or policy of Hewlett-Packard, or of the >little green men that have been following him all day. > -- Jay From owner-freebsd-hardware Sun Aug 17 13:46:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA21086 for hardware-outgoing; Sun, 17 Aug 1997 13:46:52 -0700 (PDT) Received: from mail.ruhrgebiet.individual.net (in-ruhr.ruhr.de [141.39.224.38]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA21081 for ; Sun, 17 Aug 1997 13:46:48 -0700 (PDT) Received: from robkaos.ruhr.de (admin@localhost) by mail.ruhrgebiet.individual.net (8.8.5-r-beta/8.8.5) with UUCP id WAA07438; Sun, 17 Aug 1997 22:34:48 +0200 (MET DST) Received: by robkaos.ruhr.de (Smail-3.2 1996-Jul-4 #1) id ; Sun, 17 Aug 1997 22:28:01 +0200 (MET DST) Message-Id: From: robsch@robkaos.ruhr.de (Robert Schien) Subject: Re: Quiet SCSI disk? In-Reply-To: <199708171803.AA104260982@mina.sr.hp.com> from Darryl Okahata at "Aug 17, 97 11:03:02 am" To: darrylo@sr.hp.com Date: Sun, 17 Aug 1997 22:28:00 +0200 (MET DST) Cc: hardware@freebsd.org X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Hi, > > Can anyone recommend a decent, but QUIET, SCSI disk? I'm currently > using a 4GB Quantum Atlas (I, not II), and the "jet engine whine" coming > from the drive is driving me crazy (and probably deaf, in one ear ;-). > > Thanks, > -- Darryl Okahata > Internet: darrylo@sr.hp.com > As far as I know IBM DCAS 4GB drives are quite quiet. I have this information from the reputable german computer magazine c't. They measure noise sound levels. The IBM drives are quite cheap here in Germany. Unfortunately, the prices increased due to the strong Greenback (or the weak Deutsche Mark) :-( Robert From owner-freebsd-hardware Sun Aug 17 14:15:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA22793 for hardware-outgoing; Sun, 17 Aug 1997 14:15:53 -0700 (PDT) Received: from execulink.com (root@mail.execulink.com [207.216.160.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id OAA22771 for ; Sun, 17 Aug 1997 14:15:37 -0700 (PDT) Received: from empey (pc-531.on.rogers.wave.ca [24.112.48.46]) by execulink.com (8.8.5/8.8.5) with ESMTP id RAA20274 for ; Sun, 17 Aug 1997 17:15:22 -0400 (EDT) Received: from Spooler by empey (Mercury/32 v2.01); 17 Aug 97 17:15:20 -0500 Received: from spooler by integral.on.ca (Mercury/32 v2.01); 17 Aug 97 17:15:13 -0500 From: "David Empey" Organization: Integral Communications To: freebsd-hardware@freeBSD.org Date: Sun, 17 Aug 1997 17:14:55 -0500 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: UPS Reply-to: empey@integral.on.ca Priority: normal X-mailer: Pegasus Mail for Win32 (v2.54) Message-ID: <56B53974A1@integral.on.ca> Sender: owner-freebsd-hardware@freeBSD.org X-Loop: FreeBSD.org Precedence: bulk I'm curious about any suggestions anyone may have about UPS products and FreeBSD. I am planning to use FreeBSD as a mail and web server, and thought I'd ask for suggestions before investing in one product or another. Any info is appreciated, with thanks! ___________________________________________________________ David Empey mailto: empey@integral.on.ca http://www.integral.on.ca/empey/ 604-185 Berkshire Drive, London, Ontario, Canada, N6J 3R6 (519)-474-0296 From owner-freebsd-hardware Sun Aug 17 15:00:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA26691 for hardware-outgoing; Sun, 17 Aug 1997 15:00:35 -0700 (PDT) Received: from fly.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA26680 for ; Sun, 17 Aug 1997 15:00:26 -0700 (PDT) Received: from nospam.hiwaay.net (tnt2-47.HiWAAY.net [208.147.148.47]) by fly.HiWAAY.net (8.8.6/8.8.6) with ESMTP id QAA25110; Sun, 17 Aug 1997 16:58:31 -0500 (CDT) Received: from nospam.hiwaay.net (localhost [127.0.0.1]) by nospam.hiwaay.net (8.8.6/8.8.4) with ESMTP id QAA16894; Sun, 17 Aug 1997 16:57:54 -0500 (CDT) Message-Id: <199708172157.QAA16894@nospam.hiwaay.net> X-Mailer: exmh version 2.0zeta 7/24/97 To: darrylo@sr.hp.com cc: hardware@FreeBSD.ORG From: dkelly@hiwaay.net Subject: Re: Quiet SCSI disk? In-reply-to: Message from robsch@robkaos.ruhr.de (Robert Schien) of "Sun, 17 Aug 1997 22:28:00 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 17 Aug 1997 16:57:28 -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > Hi, > > > > Can anyone recommend a decent, but QUIET, SCSI disk? I'm currently > > using a 4GB Quantum Atlas (I, not II), and the "jet engine whine" coming > > from the drive is driving me crazy (and probably deaf, in one ear ;-). > > > > Thanks, > > -- Darryl Okahata > > Internet: darrylo@sr.hp.com > > > As far as I know IBM DCAS 4GB drives are quite quiet. I have this > information from the reputable german computer magazine c't. > They measure noise sound levels. The IBM drives are quite > cheap here in Germany. Unfortunately, the prices increased due > to the strong Greenback (or the weak Deutsche Mark) :-( I concur. I bought an IBM DCAS 34330 for one of my FreeBSD systems and have been quite happy with its performance and lack of noise. Recently when purchasing a Power Computing PowerCenter Pro 210 was offered an upgrade to 4G for $170. Found out the drive was the same IBM and happily paid for the upgrade. U.S. mailorder disk houses are selling the drive for about $550 altho I've heard of $459 but never located one. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. From owner-freebsd-hardware Sun Aug 17 15:32:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA28972 for hardware-outgoing; Sun, 17 Aug 1997 15:32:02 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA28960; Sun, 17 Aug 1997 15:31:56 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id IAA05593; Mon, 18 Aug 1997 08:30:56 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id IAA08661; Mon, 18 Aug 1997 08:00:55 +0930 (CST) Message-ID: <19970818080055.00098@lemis.com> Date: Mon, 18 Aug 1997 08:00:55 +0930 From: Greg Lehey To: Michael Smith Cc: Poul-Henning Kamp , Nicolas.Souchu@prism.uvsq.fr, freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Parallel port developpements - ppbus References: <9306.871716052@critter.dk.tfs.com> <199708171539.BAA06417@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199708171539.BAA06417@genesis.atrad.adelaide.edu.au>; from Michael Smith on Mon, Aug 18, 1997 at 01:09:14AM +0930 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 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Aug 18, 1997 at 01:09:14AM +0930, Michael Smith wrote: > Poul-Henning Kamp stands accused of saying: >> > >> >As for PLIP, well, Jordan sez you're Mr PLIP, so I think this one is best >> >done with your help... >> >> Come on guys... PLIP is so simple as it can be... I don't have the time >> at this point to go back and kick PLIP again... > > If it's really that simple; where can I find some documentation on > it? Would you believe lp(4)? It's one of the best interface man pages in the section. > Is there a Linux mini-hownotto or something that spells it out in > terms a poor simple brain like mine could handle? I don't really understand. What is missing in the man page. > Is it likely to work on a port that's open to shared use? Of course! In fact, you can print and transfer data at the same time :-) Greg From owner-freebsd-hardware Sun Aug 17 15:58:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA01345 for hardware-outgoing; Sun, 17 Aug 1997 15:58:46 -0700 (PDT) Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id PAA01340 for ; Sun, 17 Aug 1997 15:58:43 -0700 (PDT) Received: (jin@localhost) by george.lbl.gov (8.6.10/8.6.5) id PAA05250; Sun, 17 Aug 1997 15:58:42 -0700 Date: Sun, 17 Aug 1997 15:58:42 -0700 From: "Jin Guojun[ITG]" Message-Id: <199708172258.PAA05250@george.lbl.gov> To: hlew@www2.shoppersnet.com, mburgett@cmnsens.zoom.com Subject: Re: K6 - New results.. Cc: hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Would some one explain how to get the replacement for old K6-200? Talk to the AMD or the vendor? and how huch will cost for the replacement? Thanks, -Jin }>Ok, I got my replacement K6-200 yesterday, after the distributor tried to say }>there was nothing wrong with the old chip (because they couldn't make it fail }>running windoze for a couple of hours... :( }> }>So far, the chip is performing flawlessly. I've run 10 full 'make worlds' in }>the last 24 hours (takes about 2 hours, with a 20 minute pause between them), }>and all have completed perfectly, without any sign of the errors I was seeing }>before. }> }> The original chip contained the manufacturing code: }> }> 9716CJD }> }> And noted the voltage as 2.9 }> }> The replacement contains the manufacturing code: }> }> B 9731FPAW }> }> And notes the voltage as 2.9 core/3.3 I/O }> }> Significant? Dunno, just trying to fill in blanks. :) } }I think currently all the K6's are Rev B. I don't know for sure, but my }guess is that the 2 digits after the 97 are the week number... So this new }one is a July chip I think. The previous was probably the first batch }(near the end of March and beginning of April) if I have the code right. }AMD has been playing around with the markings so I guess they are still }changing the markings. I think Rev A was the engineering sample batch }that was sent to MB companies. } From owner-freebsd-hardware Sun Aug 17 18:23:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA09462 for hardware-outgoing; Sun, 17 Aug 1997 18:23:07 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id SAA09457; Sun, 17 Aug 1997 18:23:01 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id KAA08379; Mon, 18 Aug 1997 10:52:35 +0930 (CST) From: Michael Smith Message-Id: <199708180122.KAA08379@genesis.atrad.adelaide.edu.au> Subject: Re: Parallel port developpements - ppbus In-Reply-To: <19970818080055.00098@lemis.com> from Greg Lehey at "Aug 18, 97 08:00:55 am" To: grog@lemis.com (Greg Lehey) Date: Mon, 18 Aug 1997 10:52:34 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, phk@critter.dk.tfs.com, Nicolas.Souchu@prism.uvsq.fr, freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Greg Lehey stands accused of saying: > >> > >> Come on guys... PLIP is so simple as it can be... I don't have the time > >> at this point to go back and kick PLIP again... > > > > If it's really that simple; where can I find some documentation on > > it? > > Would you believe lp(4)? It's one of the best interface man pages in > the section. Eep, frightening. > > Is it likely to work on a port that's open to shared use? > > Of course! In fact, you can print and transfer data at the same time :-) Really? From lp(4) : Initially, the lpt device is active for printing and the network inter- face is inactive; however, once the corresponding lp device has been con- figured 'up' with ifconfig(8) printing is disabled until the network in- terface is configured 'down'. That's OK though; in this case I merely needed to know whether the if_lp driver should obtain an exclusive lock on the port hardware. It'll let you tie yourself in some interesting knots, of course 8) > Greg -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Sun Aug 17 20:54:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA18488 for hardware-outgoing; Sun, 17 Aug 1997 20:54:50 -0700 (PDT) Received: from nico.telstra.net (nico.telstra.net [139.130.204.16]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id UAA18470; Sun, 17 Aug 1997 20:54:45 -0700 (PDT) Received: from freebie.lemis.com (gregl1.lnk.telstra.net [139.130.136.133]) by nico.telstra.net (8.6.10/8.6.10) with ESMTP id NAA12749; Mon, 18 Aug 1997 13:54:00 +1000 Received: (grog@localhost) by freebie.lemis.com (8.8.7/8.6.12) id NAA10202; Mon, 18 Aug 1997 13:23:59 +0930 (CST) Message-ID: <19970818132357.12809@lemis.com> Date: Mon, 18 Aug 1997 13:23:57 +0930 From: Greg Lehey To: Michael Smith Cc: phk@critter.dk.tfs.com, Nicolas.Souchu@prism.uvsq.fr, freebsd-hackers@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: Parallel port developpements - ppbus References: <19970818080055.00098@lemis.com> <199708180122.KAA08379@genesis.atrad.adelaide.edu.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.81e In-Reply-To: <199708180122.KAA08379@genesis.atrad.adelaide.edu.au>; from Michael Smith on Mon, Aug 18, 1997 at 10:52:34AM +0930 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 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, Aug 18, 1997 at 10:52:34AM +0930, Michael Smith wrote: > Greg Lehey stands accused of saying: >>> Is it likely to work on a port that's open to shared use? >> >> Of course! In fact, you can print and transfer data at the same time :-) > > Really? From lp(4) : > > Initially, the lpt device is active for printing and the network inter- > face is inactive; however, once the corresponding lp device has been con- > figured 'up' with ifconfig(8) printing is disabled until the network in- > terface is configured 'down'. I didn't think that you were humour-impaired. Greg From owner-freebsd-hardware Mon Aug 18 00:39:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA04181 for hardware-outgoing; Mon, 18 Aug 1997 00:39:37 -0700 (PDT) Received: from www2.shoppersnet.com (shoppersnet.com [204.156.152.112]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA04172 for ; Mon, 18 Aug 1997 00:39:33 -0700 (PDT) Received: (from hlew@localhost) by www2.shoppersnet.com (8.8.5/8.8.5) id AAA10402; Mon, 18 Aug 1997 00:45:14 -0700 (PDT) Date: Mon, 18 Aug 1997 00:45:14 -0700 (PDT) From: Howard Lew To: "Jin Guojun[ITG]" cc: mburgett@cmnsens.zoom.com, hardware@FreeBSD.ORG Subject: Re: K6 - New results.. In-Reply-To: <199708172258.PAA05250@george.lbl.gov> 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 Sun, 17 Aug 1997, Jin Guojun[ITG] wrote: > Would some one explain how to get the replacement for old K6-200? > Talk to the AMD or the vendor? and how huch will cost for the replacement? For replacements, contact the company where you got the chip. Some places can replace them for up to 1 year. Others will do 30 days. I know that those who get it from @Once (distributor) may be able to do longer (at least that's what the say). Also rumors about AMD K6 boxed cpus coming soon too. > > Thanks, > > -Jin > > }>Ok, I got my replacement K6-200 yesterday, after the distributor tried to say > }>there was nothing wrong with the old chip (because they couldn't make it fail > }>running windoze for a couple of hours... :( > }> > }>So far, the chip is performing flawlessly. I've run 10 full 'make worlds' in > }>the last 24 hours (takes about 2 hours, with a 20 minute pause between them), > }>and all have completed perfectly, without any sign of the errors I was seeing > }>before. > }> > }> The original chip contained the manufacturing code: > }> > }> 9716CJD > }> > }> And noted the voltage as 2.9 > }> > }> The replacement contains the manufacturing code: > }> > }> B 9731FPAW > }> > }> And notes the voltage as 2.9 core/3.3 I/O > }> > }> Significant? Dunno, just trying to fill in blanks. :) > } > }I think currently all the K6's are Rev B. I don't know for sure, but my > }guess is that the 2 digits after the 97 are the week number... So this new > }one is a July chip I think. The previous was probably the first batch > }(near the end of March and beginning of April) if I have the code right. > }AMD has been playing around with the markings so I guess they are still > }changing the markings. I think Rev A was the engineering sample batch > }that was sent to MB companies. > } > --------------------------------------------------------------------------- Shoppers Network (Support) AMD K5/K6s, Cyrix 6x86, Intel Pentiums/Pro Phone: (415) 759-8584 Email: howard@shoppersnet.com ==============================> WWW - http://www.shoppersnet.com ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ From owner-freebsd-hardware Mon Aug 18 07:44:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA25383 for hardware-outgoing; Mon, 18 Aug 1997 07:44:13 -0700 (PDT) Received: from relay.linet.it (relay.linet.it [194.185.24.71]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id HAA25378 for ; Mon, 18 Aug 1997 07:44:10 -0700 (PDT) Received: from icum.linet.it (unverified [194.185.24.73]) by relay.linet.it (EMWAC SMTPRS 0.83) with SMTP id ; Mon, 18 Aug 1997 16:30:02 +0200 Message-ID: From: "Francesco di Filippo" To: Subject: LS-120 Date: Mon, 18 Aug 1997 16:40:37 +0200 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1008.3 X-MimeOle: Produced By Microsoft MimeOLE Engine V4.71.1008.3 Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk The FreeBSD support the drive LS-120? From owner-freebsd-hardware Mon Aug 18 10:34:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA05309 for hardware-outgoing; Mon, 18 Aug 1997 10:34:41 -0700 (PDT) Received: from gw1.asacomputers.com (root@gw1.asacomputers.com [204.69.220.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA05285 for ; Mon, 18 Aug 1997 10:34:20 -0700 (PDT) Received: by gw1.asacomputers.com id HAA29302; Mon, 18 Aug 1997 07:34:15 -0700 (PDT) Message-Id: <2.2.32.19970818173101.00c4035c@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: Mon, 18 Aug 1997 10:31:01 -0700 To: robsch@robkaos.ruhr.de (Robert Schien) From: Kedar Subject: Re: Quiet SCSI disk? Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 10:28 PM 8/17/97 +0200, you wrote: >As far as I know IBM DCAS 4GB drives are quite quiet. I have this Hi, Is that not a 5400 rpm drive? I think all the Quantum Atlas series have always been 7200 rpm. That speed tends to create that high-pitch whine. Reportedly, the new Seagate ST34572 series creates a bit less of a whine (at least lesser than the ST34371) at the same rpm. YMMV, Kedar. From owner-freebsd-hardware Mon Aug 18 11:45:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA09143 for hardware-outgoing; Mon, 18 Aug 1997 11:45:25 -0700 (PDT) Received: from mindcrime.termfrost.org (root@mindcrime.termfrost.org [208.141.2.81]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA09136; Mon, 18 Aug 1997 11:45:20 -0700 (PDT) Received: from localhost (mandrews@localhost) by mindcrime.termfrost.org (8.8.7/8.8.6/mindcrime-19970604) with SMTP id OAA01628; Mon, 18 Aug 1997 14:45:11 -0400 (EDT) Date: Mon, 18 Aug 1997 14:45:11 -0400 (EDT) From: Mike Andrews To: freebsd-current@freebsd.org, freebsd-hardware@freebsd.org Subject: HP 4020i CD-R problems 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 to be doing something stupid here. Pentium 200 MMX, FreeBSD 2.2-STABLE, HP 4020i CD burner hanging off an NCR 53c875 card. On last month's 2.2-STABLE, I could burn CD's fine. (Unfortunately I don't know the exact date I last burned a disc.) On yesterday's, I can't -- wormcontrol just returns "device not configured" errors. Ejecting and reinserting the media doesn't help. As far as I can tell, neither worm.c in the kernel nor wormcontrol have changed since it was last working. Any ideas? mindcrime# scsi -f /dev/rworm0.ctl -c "0 0 0 0 0 0" SCIOCCOMMAND ioctl: Command accepted. return status 3 (Sense Returned)Command out (6 of 6): 00 00 00 00 00 00 No sense dump for error code 00. sense (32 of 48): 00 00 00 00 00 00 00 00 2e 00 00 00 88 01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 mindcrime# wormcontrol select HP 4020i wormcontrol: open(/dev/rworm0): Device not configured Kernel config file fragments: controller ncr0 controller scbus0 device sd0 device st0 device cd0 device worm0 at scbus? dmesg fragments: ncr0 rev 3 int a irq 12 on pci0:10 ncr0 waiting for scsi devices to settle (ncr0:1:0): "SEAGATE ST15230N 0298" type 0 fixed SCSI 2 sd0(ncr0:1:0): Direct-Access sd0(ncr0:1:0): 10.0 MB/s (100 ns, offset 15) 4095MB (8386733 512 byte sectors) (ncr0:2:0): "HP C4324/C4325 1.27" type 5 removable SCSI 2 worm0(ncr0:2:0): Write-Once (ncr0:3:0): "ARCHIVE Python 27216-XXX 2.59" type 1 removable SCSI 2 st0(ncr0:3:0): Sequential-Access st0(ncr0:3:0): 5.0 MB/s (200 ns, offset 15) density code 0x13, drive empty (ncr0:4:0): "TOSHIBA CD-ROM XM-3501TA 3054" type 5 removable SCSI 2 cd0(ncr0:4:0): CD-ROM cd0(ncr0:4:0): 4.0 MB/s (250 ns, offset 16) can't get the size (ncr0:6:0): "QUANTUM FIREBALL_TM3200S 300X" type 0 fixed SCSI 2 sd1(ncr0:6:0): Direct-Access sd1(ncr0:6:0): 10.0 MB/s (100 ns, offset 15) 3067MB (6281856 512 byte sectors) -- Mike Andrews (MA12) network & systems guy, Digital Crescent, Frankfort KY -- mandrews@dcr.net -- mandrews@termfrost.org -- http://www.termfrost.org/ -- "Evil shall always prevail over good, because evil has better marketing..." -- Sick of junk e-mail? Visit http://www.cauce.org/ or http://spam.abuse.net/ From owner-freebsd-hardware Mon Aug 18 16:18:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA24439 for hardware-outgoing; Mon, 18 Aug 1997 16:18:02 -0700 (PDT) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA24429 for ; Mon, 18 Aug 1997 16:17:56 -0700 (PDT) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.6/8.7.3) id QAA11642; Mon, 18 Aug 1997 16:17:53 -0700 (PDT) Date: Mon, 18 Aug 1997 16:17:53 -0700 (PDT) Message-Id: <199708182317.QAA11642@vader.cs.berkeley.edu> To: hardware@freebsd.org Subject: parity errors From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk What am I supposed to see when there is a parity error on the main memory? I have a few memory modules I suspect to be bad, so I put them (256MB total) in our package building machine and tried a "make world", and got one "kernel page fault" (or something like that) and two lockups (no message on console). I disabled parity check in the BIOS, and world aborted once with a sh seg-faulting and once with a syntax error from make. At this point, I think it is pretty clear that the memory's at fault, but shouldn't I see some "NMI" type messages? (If I grepped correctly, it should be the "NMI indicates hardware failure" at line 265 in /sys/i386/i386/trap.c.) This is with a P6-200 (not overclocked) on an Intel Venus motherboard. Satoshi From owner-freebsd-hardware Mon Aug 18 16:40:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA25426 for hardware-outgoing; Mon, 18 Aug 1997 16:40:27 -0700 (PDT) Received: from mars.aros.net (mars.aros.net [207.173.16.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA25418 for ; Mon, 18 Aug 1997 16:40:24 -0700 (PDT) Received: from shell.aros.net (root@shell.aros.net [207.173.16.19]) by mars.aros.net (8.8.5/8.8.4) with ESMTP id RAA21134 for ; Mon, 18 Aug 1997 17:37:09 -0600 (MDT) Received: from shell.aros.net (msanders@localhost.aros.net [127.0.0.1]) by shell.aros.net (8.8.5/8.8.5) with ESMTP id RAA01394 for ; Mon, 18 Aug 1997 17:40:22 -0600 (MDT) Message-Id: <199708182340.RAA01394@shell.aros.net> X-Attribution: msanders To: freebsd-hardware@FreeBSD.ORG Reply-To: msanders@aros.net Subject: Source for 150MHz PPro? X-Mailer: MH 6.8.3 Date: Mon, 18 Aug 1997 17:40:22 -0600 From: "Michael K. Sanders" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [ Please include me directly in any replies, I'm not subscribed to -hardware ] Does anyone have a source that still has any 150MHz PPro chips in stock? Thanks, :: Mike :: From owner-freebsd-hardware Mon Aug 18 20:21:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA05317 for hardware-outgoing; Mon, 18 Aug 1997 20:21:13 -0700 (PDT) Received: from palrel1.hp.com (palrel1.hp.com [156.153.255.235]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA05309 for ; Mon, 18 Aug 1997 20:21:00 -0700 (PDT) Received: from srmail.sr.hp.com (srmail.sr.hp.com [15.4.45.14]) by palrel1.hp.com (8.8.6/8.8.5) with ESMTP id UAA02724; Mon, 18 Aug 1997 20:20:34 -0700 (PDT) Received: from mina.sr.hp.com by srmail.sr.hp.com with ESMTP (1.37.109.16/15.5+ECS 3.3) id AA272110833; Mon, 18 Aug 1997 20:20:33 -0700 Received: from mina.sr.hp.com by mina.sr.hp.com with SMTP (1.37.109.16/15.5+ECS 3.3) id AA263120833; Mon, 18 Aug 1997 20:20:33 -0700 Message-Id: <199708190320.AA263120833@mina.sr.hp.com> To: "Mike Burgett" Cc: "hardware@freebsd.org" Subject: Re: K6 - New results.. Reply-To: darrylo@sr.hp.com In-Reply-To: Your message of "Sat, 16 Aug 1997 16:28:08 PDT." <199708162328.QAA15563@dragon.cmnsens.zoom.com> Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Date: Mon, 18 Aug 1997 20:20:32 -0700 From: Darryl Okahata Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Ok, I got my replacement K6-200 yesterday, after the distributor tried to say > there was nothing wrong with the old chip (because they couldn't make it fail > running windoze for a couple of hours... :( [ Sorry if this is old news, but I haven't seen this mentioned, yet. ] Just FYI, a Linux user has a page claiming that K6 systems with more than 32MB RAM exhibit "signal 11" problems: http://www.creaweb.fr/bpc/k6bug.html Instructions for "reproducing" the problem on either Linux or WinNT are given (although "make world" is probably good enough as anything ;-). -- Darryl Okahata Internet: darrylo@sr.hp.com DISCLAIMER: this message is the author's personal opinion and does not constitute the support, opinion, or policy of Hewlett-Packard, or of the little green men that have been following him all day. From owner-freebsd-hardware Mon Aug 18 20:21:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA05345 for hardware-outgoing; Mon, 18 Aug 1997 20:21:33 -0700 (PDT) Received: from 586quick166.saturn-tech.com ([207.229.19.32]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA05336 for ; Mon, 18 Aug 1997 20:21:29 -0700 (PDT) Received: from localhost (drussell@localhost) by 586quick166.saturn-tech.com (8.8.4/8.8.4) with SMTP id VAA00450; Mon, 18 Aug 1997 21:22:20 -0600 (MDT) X-Authentication-Warning: 586quick166.saturn-tech.com: drussell owned process doing -bs Date: Mon, 18 Aug 1997 21:22:19 -0600 (MDT) From: Doug Russell To: "Michael K. Sanders" cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Source for 150MHz PPro? In-Reply-To: <199708182340.RAA01394@shell.aros.net> 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, 18 Aug 1997, Michael K. Sanders wrote: > [ Please include me directly in any replies, I'm not subscribed to -hardware ] > > Does anyone have a source that still has any 150MHz PPro chips in stock? I'm quite sure I can still get 'em for you... Unfortunately, I'm at home now so I can't double check right now. I'll check when I hit the office in the morning and let you know. Later...... From owner-freebsd-hardware Mon Aug 18 21:26:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA08255 for hardware-outgoing; Mon, 18 Aug 1997 21:26:04 -0700 (PDT) Received: from mindcrime.termfrost.org (root@mindcrime.termfrost.org [208.141.2.81]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA08247 for ; Mon, 18 Aug 1997 21:25:54 -0700 (PDT) Received: from localhost (mandrews@localhost) by mindcrime.termfrost.org (8.8.7/8.8.6/mindcrime-19970604) with SMTP id AAA01952; Tue, 19 Aug 1997 00:23:41 -0400 (EDT) Date: Tue, 19 Aug 1997 00:23:41 -0400 (EDT) From: Mike Andrews To: darrylo@sr.hp.com cc: Mike Burgett , "hardware@freebsd.org" Subject: Re: K6 - New results.. In-Reply-To: <199708190320.AA263120833@mina.sr.hp.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, 18 Aug 1997, Darryl Okahata wrote: > > Ok, I got my replacement K6-200 yesterday, after the distributor tried to say > > there was nothing wrong with the old chip (because they couldn't make it fail > > running windoze for a couple of hours... :( > > [ Sorry if this is old news, but I haven't seen this mentioned, yet. ] > > Just FYI, a Linux user has a page claiming that K6 systems with > more than 32MB RAM exhibit "signal 11" problems: > > http://www.creaweb.fr/bpc/k6bug.html > > Instructions for "reproducing" the problem on either Linux or WinNT are > given (although "make world" is probably good enough as anything ;-). Interesting... The two systems I had problems with had 64 meg of parity memory, however, I tried 32 meg of EDO and it didn't make any difference. And I briefly had one 64 meg system that worked. -- Mike Andrews (MA12) network & systems guy, Digital Crescent, Frankfort KY -- mandrews@dcr.net -- mandrews@termfrost.org -- http://www.termfrost.org/ -- "Evil shall always prevail over good, because evil has better marketing..." -- Sick of junk e-mail? Visit http://www.cauce.org/ or http://spam.abuse.net/ From owner-freebsd-hardware Mon Aug 18 21:29:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA08426 for hardware-outgoing; Mon, 18 Aug 1997 21:29:21 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA08420 for ; Mon, 18 Aug 1997 21:29:17 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0x0ft5-0000Wk-00; Mon, 18 Aug 1997 21:27:23 -0700 Date: Mon, 18 Aug 1997 21:27:22 -0700 (PDT) From: Tom Samplonius To: Satoshi Asami cc: hardware@freebsd.org Subject: Re: parity errors In-Reply-To: <199708182317.QAA11642@vader.cs.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 Mon, 18 Aug 1997, Satoshi Asami wrote: > What am I supposed to see when there is a parity error on the main > memory? I have a few memory modules I suspect to be bad, so I put > them (256MB total) in our package building machine and tried a "make > world", and got one "kernel page fault" (or something like that) and > two lockups (no message on console). I disabled parity check in the > BIOS, and world aborted once with a sh seg-faulting and once with > a syntax error from make. > > At this point, I think it is pretty clear that the memory's at fault, > but shouldn't I see some "NMI" type messages? (If I grepped > correctly, it should be the "NMI indicates hardware failure" at line > 265 in /sys/i386/i386/trap.c.) They are true parity simms right? Do you have parity checking or ECC turned on in the CMOS setup? > This is with a P6-200 (not overclocked) on an Intel Venus motherboard. > > Satoshi > > Tom From owner-freebsd-hardware Mon Aug 18 22:37:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA12062 for hardware-outgoing; Mon, 18 Aug 1997 22:37:12 -0700 (PDT) Received: from pluto.plutotech.com (ken@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA12057 for ; Mon, 18 Aug 1997 22:37:09 -0700 (PDT) Received: (from ken@localhost) by pluto.plutotech.com (8.8.5/8.8.5) id XAA11729; Mon, 18 Aug 1997 23:37:07 -0600 (MDT) From: Kenneth Merry Message-Id: <199708190537.XAA11729@pluto.plutotech.com> Subject: Re: parity errors In-Reply-To: <199708182317.QAA11642@vader.cs.berkeley.edu> from Satoshi Asami at "Aug 18, 97 04:17:53 pm" To: asami@cs.berkeley.edu (Satoshi Asami) Date: Mon, 18 Aug 1997 23:37:07 -0600 (MDT) Cc: hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (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 Satoshi Asami wrote... > What am I supposed to see when there is a parity error on the main > memory? I have a few memory modules I suspect to be bad, so I put > them (256MB total) in our package building machine and tried a "make > world", and got one "kernel page fault" (or something like that) and > two lockups (no message on console). I disabled parity check in the > BIOS, and world aborted once with a sh seg-faulting and once with > a syntax error from make. > > At this point, I think it is pretty clear that the memory's at fault, > but shouldn't I see some "NMI" type messages? (If I grepped > correctly, it should be the "NMI indicates hardware failure" at line > 265 in /sys/i386/i386/trap.c.) > > This is with a P6-200 (not overclocked) on an Intel Venus motherboard. I agree, you should see some sort of error. I had some ram trouble on one of my machines (ASUS P/I-XP6NP5 MB), and I got a message that specifically said "ram parity error". It must have been from /sys/i386/isa/intr_machdep.c. (I grepped for "parity error") Of course I had parity memory in there, and I either had parity or ECC checking turned on.. I'm not so sure you'd get any NMI messages unless you have parity checking turned on. If that doesn't work, try turning on ECC support. I would put the SIMMs in the machine two at a time and swap them around until you isolate the bad SIMMs. Of course that'll take a while, I imagine, with a make world test. One test that I used that worked sometimes was to crank up a ton of xv processes with big pictures -- enough to eat up all the ram and some of the swap. That usually had the effect of crashing the machine with a "RAM parity error". Of course you'd want to display the xv processes on a remote machine so you catch the panic message. Hope this helps, Ken -- Kenneth Merry ken@plutotech.com From owner-freebsd-hardware Mon Aug 18 23:10:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA13812 for hardware-outgoing; Mon, 18 Aug 1997 23:10:38 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (wck-ca8-25.ix.netcom.com [204.31.231.89]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA13772 for ; Mon, 18 Aug 1997 23:10:04 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.6/8.6.9) id XAA22389; Mon, 18 Aug 1997 23:02:59 -0700 (PDT) Date: Mon, 18 Aug 1997 23:02:59 -0700 (PDT) Message-Id: <199708190602.XAA22389@silvia.HIP.Berkeley.EDU> To: tom@sdf.com CC: hardware@FreeBSD.ORG In-reply-to: (message from Tom Samplonius on Mon, 18 Aug 1997 21:27:22 -0700 (PDT)) Subject: Re: parity errors From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * > two lockups (no message on console). I disabled parity check in the * > BIOS, and world aborted once with a sh seg-faulting and once with * > a syntax error from make. * They are true parity simms right? I think so. There are 36 identical-looking chips on each module. I've never seen such big SIMMs before. However, I brought the memory home and stuck it in my computer, and make world's almost done. Maybe it's the mothearboard that can't handle the big modules, I have an Intel Venus at work and Asus P6NP5 at home. Which brings up another question: does anyone have the Venus working with 64MB memory modules? Is the Venus one of those that can't work with 24-chip or higher modules? We had two computers at work (pretty much the same hardware as others) with thise 64MB modules, running Windows NT for Adobe PhotoShop. They kept crashing with lots of different errors, so I swapped the memory with my package-building machine and got errors. If it's that one module is bad, I would think at least one of the machines would run ok. Of course, after I swapped the memory, the machines kept crashing so maybe some of that was just general Windows NT flakiness. * Do you have parity checking or * ECC turned on in the CMOS setup? Sorry, by "BIOS" above I meant "CMOS". Satoshi From owner-freebsd-hardware Mon Aug 18 23:13:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA13998 for hardware-outgoing; Mon, 18 Aug 1997 23:13:16 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (wck-ca8-25.ix.netcom.com [204.31.231.89]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA13993 for ; Mon, 18 Aug 1997 23:13:12 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.6/8.6.9) id XAA27378; Mon, 18 Aug 1997 23:12:30 -0700 (PDT) Date: Mon, 18 Aug 1997 23:12:30 -0700 (PDT) Message-Id: <199708190612.XAA27378@silvia.HIP.Berkeley.EDU> To: ken@plutotech.com CC: hardware@FreeBSD.ORG In-reply-to: <199708190537.XAA11729@pluto.plutotech.com> (message from Kenneth Merry on Mon, 18 Aug 1997 23:37:07 -0600 (MDT)) Subject: Re: parity errors From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * I agree, you should see some sort of error. I had some ram trouble * on one of my machines (ASUS P/I-XP6NP5 MB), and I got a message that * specifically said "ram parity error". It must have been from * /sys/i386/isa/intr_machdep.c. (I grepped for "parity error") Oh, I see. (That code is in "isa/isa.c" in 2.2, by the way.) * I'm not so sure you'd get any NMI messages unless you have * parity checking turned on. If that doesn't work, try turning on ECC * support. ECC is error correction, so the motherboard will interrupt only if it's not correctable (two bits of error?). That is why I'm testing stuff now with parity on. * I would put the SIMMs in the machine two at a time and swap them * around until you isolate the bad SIMMs. Of course that'll take a while, I * imagine, with a make world test. One test that I used that worked * sometimes was to crank up a ton of xv processes with big pictures -- enough * to eat up all the ram and some of the swap. That usually had the effect * of crashing the machine with a "RAM parity error". Of course you'd want to * display the xv processes on a remote machine so you catch the panic * message. Thanks for the advice, I opened up some more xv's and now the system is finally swapping. The make world is still running happily, though. Satoshi From owner-freebsd-hardware Tue Aug 19 00:31:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA18738 for hardware-outgoing; Tue, 19 Aug 1997 00:31:19 -0700 (PDT) Received: from ns2.yahoo.com (ns2.yahoo.com [205.216.162.20]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id AAA18733 for ; Tue, 19 Aug 1997 00:31:17 -0700 (PDT) Received: (from filo@localhost) by ns2.yahoo.com (8.8.5/8.6.12) id AAA19367; Tue, 19 Aug 1997 00:30:45 -0700 (PDT) Date: Tue, 19 Aug 1997 00:30:45 -0700 (PDT) Message-Id: <199708190730.AAA19367@ns2.yahoo.com> From: David Filo To: asami@cs.berkeley.edu (Satoshi Asami) cc: hardware@FreeBSD.ORG In-reply-to: asami@cs.berkeley.edu's message of Mon, 18 Aug 1997 23:02:59 -0700 (PDT) Subject: Re: parity errors Reply-To: filo@yahoo.com References: <199708190602.XAA22389@silvia.HIP.Berkeley.EDU> Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > However, I brought the memory home and stuck it in my computer, and > make world's almost done. Maybe it's the mothearboard that can't > handle the big modules, I have an Intel Venus at work and Asus P6NP5 > at home. > > Which brings up another question: does anyone have the Venus working > with 64MB memory modules? Is the Venus one of those that can't work > with 24-chip or higher modules? > Yep, the Venus does not work very well with such SIMMs. You really should use SIMMs based on 64Mb chips. I've seen this stated in the Venus manual, although it looks like they've recently certified some of the 16Mb based ones. http://developer.intel.com/design/motherbd/vs/vs_mem.htm We saw quite a few "RAM parity error" panics before switching to 64Mb SIMMs. David From owner-freebsd-hardware Tue Aug 19 01:07:23 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA20620 for hardware-outgoing; Tue, 19 Aug 1997 01:07:23 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca17-23.ix.netcom.com [204.32.168.183]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA20615 for ; Tue, 19 Aug 1997 01:07:19 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id BAA19796; Tue, 19 Aug 1997 01:07:14 -0700 (PDT) Date: Tue, 19 Aug 1997 01:07:14 -0700 (PDT) Message-Id: <199708190807.BAA19796@silvia.HIP.Berkeley.EDU> To: filo@yahoo.com CC: hardware@FreeBSD.ORG In-reply-to: <199708190730.AAA19367@ns2.yahoo.com> (message from David Filo on Tue, 19 Aug 1997 00:30:45 -0700 (PDT)) Subject: Re: parity errors From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * Yep, the Venus does not work very well with such SIMMs. You really * should use SIMMs based on 64Mb chips. I've seen this stated in the * Venus manual, although it looks like they've recently certified some * of the 16Mb based ones. Oh, manual, huh? We didn't get any, as these machines were donated -- didn't even know that they were Venus (Venii?) until I opened up the computer and compared the MB to the picture of it on Intel's web site. ;) Thanks for the info, I'll see if I can get them replaced. (Either the memory or motherboard, I'm really getting tired of all these Venus crap.) Satoshi From owner-freebsd-hardware Tue Aug 19 02:29:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA23747 for hardware-outgoing; Tue, 19 Aug 1997 02:29:06 -0700 (PDT) Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id CAA23741 for ; Tue, 19 Aug 1997 02:29:01 -0700 (PDT) Received: (jin@localhost) by george.lbl.gov (8.6.10/8.6.5) id OAA20895; Mon, 18 Aug 1997 14:15:18 -0700 Date: Mon, 18 Aug 1997 14:15:18 -0700 From: "Jin Guojun[ITG]" Message-Id: <199708182115.OAA20895@george.lbl.gov> To: mburgett@cmnsens.zoom.com Subject: Re: K6 - New results.. Cc: hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Ok, I got my replacement K6-200 yesterday, after the distributor tried to say > there was nothing wrong with the old chip (because they couldn't make it fail > running windoze for a couple of hours... :( > > So far, the chip is performing flawlessly. I've run 10 full 'make worlds' in > the last 24 hours (takes about 2 hours, with a 20 minute pause between them), > and all have completed perfectly, without any sign of the errors I was seeing > before. > > The original chip contained the manufacturing code: > > 9716CJD > > And noted the voltage as 2.9 > > The replacement contains the manufacturing code: > > B 9731FPAW > > And notes the voltage as 2.9 core/3.3 I/O I had K6-166 CPU with the manufacturing code: 9714EJE 2.9v I called the vendor, and the vendor said that they have new K6-166 CPU with the manufacturing code: 9722 EJLW Does any one know if the "9722 EJLW" has the flaw fixed? -Jin From owner-freebsd-hardware Tue Aug 19 03:38:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA26885 for hardware-outgoing; Tue, 19 Aug 1997 03:38:05 -0700 (PDT) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA26879 for ; Tue, 19 Aug 1997 03:38:01 -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 DAA09558; Tue, 19 Aug 1997 03:39:11 -0700 (PDT) Message-Id: <199708191039.DAA09558@implode.root.com> To: "Jin Guojun[ITG]" cc: mburgett@cmnsens.zoom.com, hardware@FreeBSD.ORG Subject: Re: K6 - New results.. In-reply-to: Your message of "Mon, 18 Aug 1997 14:15:18 PDT." <199708182115.OAA20895@george.lbl.gov> From: David Greenman Reply-To: dg@root.com Date: Tue, 19 Aug 1997 03:39:11 -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> The replacement contains the manufacturing code: >> >> B 9731FPAW >> >> And notes the voltage as 2.9 core/3.3 I/O > >I had K6-166 CPU with the manufacturing code: > >9714EJE 2.9v Just for reference, the part I'm having trouble with is identified as: B 9714EJD -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hardware Tue Aug 19 08:59:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA14717 for hardware-outgoing; Tue, 19 Aug 1997 08:59:04 -0700 (PDT) Received: from icicle.winternet.com (adm@icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA14703 for ; Tue, 19 Aug 1997 08:58:58 -0700 (PDT) Received: (from adm@localhost) by icicle.winternet.com (8.8.6/8.8.6) id KAA24903; Tue, 19 Aug 1997 10:58:36 -0500 (CDT) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma024777; Tue, 19 Aug 97 10:57:50 -0500 Received: from localhost (mestery@localhost) by tundra.winternet.com (8.8.4/8.8.4) with SMTP id KAA13262; Tue, 19 Aug 1997 10:57:49 -0500 (CDT) X-Authentication-Warning: tundra.winternet.com: mestery owned process doing -bs Date: Tue, 19 Aug 1997 10:57:49 -0500 (CDT) From: Kyle Mestery To: Doug Russell cc: "Michael K. Sanders" , freebsd-hardware@FreeBSD.ORG Subject: Re: Source for 150MHz PPro? 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 > I'm quite sure I can still get 'em for you... Unfortunately, I'm at home > now so I can't double check right now. I'll check when I hit the office > in the morning and let you know. > > Later...... > Could you post this to the list? I am also interested in possibly getting some 150s. Thanks. Kyle Mestery StorageTek's Network Systems Group 7600 Boone Ave. N., Brooklyn Park, MN 55428 mesteka@anubis.network.com, mestery@winternet.com From owner-freebsd-hardware Tue Aug 19 09:46:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA18107 for hardware-outgoing; Tue, 19 Aug 1997 09:46:58 -0700 (PDT) Received: from Ilsa.StevesCafe.com (Ilsa.StevesCafe.com [205.168.119.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA18100 for ; Tue, 19 Aug 1997 09:46:53 -0700 (PDT) Received: from Ilsa.StevesCafe.com (localhost [127.0.0.1]) by Ilsa.StevesCafe.com (8.8.7/8.8.5) with ESMTP id KAA15177; Tue, 19 Aug 1997 10:46:19 -0600 (MDT) Message-Id: <199708191646.KAA15177@Ilsa.StevesCafe.com> X-Mailer: exmh version 2.0gamma 1/27/96 From: Steve Passe To: Kyle Mestery cc: Doug Russell , "Michael K. Sanders" , freebsd-hardware@FreeBSD.ORG Subject: Re: Source for 150MHz PPro? In-reply-to: Your message of "Tue, 19 Aug 1997 10:57:49 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 19 Aug 1997 10:46:19 -0600 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi, > > I'm quite sure I can still get 'em for you... Unfortunately, I'm at home > > now so I can't double check right now. I'll check when I hit the office > > in the morning and let you know. > > > > Later...... > > > Could you post this to the list? I am also interested in possibly getting > some 150s. Thanks. go for 166s, the 150 uses a 60mHz bus, the 166 uses a 66mHz bus. -- Steve Passe | powered by smp@csn.net | Symmetric MultiProcessor FreeBSD From owner-freebsd-hardware Tue Aug 19 12:20:44 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA29737 for hardware-outgoing; Tue, 19 Aug 1997 12:20:44 -0700 (PDT) Received: from www.xinetron.com (www.xinetron.com [206.86.215.68]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA29725 for ; Tue, 19 Aug 1997 12:20:38 -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 MAA01336 for ; Tue, 19 Aug 1997 12:20:07 -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 MAA21301; Tue, 19 Aug 1997 12:19:38 -0700 (PDT) Message-ID: <33F9F1CA.99124C6@xinetron.com> Date: Tue, 19 Aug 1997 12:19:38 -0700 From: Local list X-Mailer: Mozilla 4.01 [en] (Win95; I) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: subscribe 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 subscribe From owner-freebsd-hardware Tue Aug 19 13:57:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA04869 for hardware-outgoing; Tue, 19 Aug 1997 13:57:41 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA04863 for ; Tue, 19 Aug 1997 13:57:36 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0x0vJT-00018n-00; Tue, 19 Aug 1997 13:55:39 -0700 Date: Tue, 19 Aug 1997 13:55:38 -0700 (PDT) From: Tom Samplonius To: Satoshi Asami cc: hardware@freebsd.org Subject: Re: parity errors In-Reply-To: <199708190602.XAA22389@silvia.HIP.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 Mon, 18 Aug 1997, Satoshi Asami wrote: > * > two lockups (no message on console). I disabled parity check in the > * > BIOS, and world aborted once with a sh seg-faulting and once with > * > a syntax error from make. > > * They are true parity simms right? > > I think so. There are 36 identical-looking chips on each module. > I've never seen such big SIMMs before. It is hard to find motherboards that support SIMMs with that many chips. Most are 24 or less. Tom From owner-freebsd-hardware Tue Aug 19 20:48:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA25368 for hardware-outgoing; Tue, 19 Aug 1997 20:48:29 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA25362 for ; Tue, 19 Aug 1997 20:48:16 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.5/8.8.6) id NAA11634 for freebsd-hardware@freebsd.org; Wed, 20 Aug 1997 13:48:09 +1000 Received: from localhost.dtir.qld.gov.au by ogre.dtir.qld.gov.au (8.7.5/DEVETIR-E0.3a) with SMTP id NAA21476; Wed, 20 Aug 1997 13:48:54 +1000 (EST) Message-Id: <199708200348.NAA21476@ogre.dtir.qld.gov.au> To: freebsd-hardware@freebsd.org cc: syssgm@dtir.qld.gov.au Subject: Re: Quiet SCSI disk? References: <2.2.32.19970818173101.00c4035c@gw1> In-Reply-To: <2.2.32.19970818173101.00c4035c@gw1> from Kedar at "Mon, 18 Aug 1997 17:31:01 +0000" Date: Wed, 20 Aug 1997 13:48:54 +1000 From: Stephen McKay Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Monday, 18th August 1997, Kedar wrote: >>As far as I know IBM DCAS 4GB drives are quite quiet. > > Is that not a 5400 rpm drive? I think all the Quantum Atlas series >have always been 7200 rpm. That speed tends to create that high-pitch whine. Yes, it is a 5400 rpm drive. I don't see that as a problem for end users. Indeed, the lower speed means less heat and less noise. I would have chosen a 5400 rpm drive over a 7200 rpm drive for these reasons, even if they were the same price. I am very please with my DCAS 4GB drive, and certainly don't think of it as slow (~7MB/s with iozone). I know a few people with the 2GB variant and they have had no problems either. Stephen. From owner-freebsd-hardware Tue Aug 19 20:51:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA25550 for hardware-outgoing; Tue, 19 Aug 1997 20:51:13 -0700 (PDT) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA25529 for ; Tue, 19 Aug 1997 20:50:54 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.7.5/8.7.3) id XAA26829; Tue, 19 Aug 1997 23:24:40 -0400 (EDT) Date: Tue, 19 Aug 1997 23:24:40 -0400 (EDT) From: "John T. Farmer" Message-Id: <199708200324.XAA26829@sabre.goldsword.com> To: jin@george.lbl.gov, mburgett@cmnsens.zoom.com Subject: Re: K6 - New results.. & [Added - Parity issues also?) Cc: hardware@FreeBSD.ORG, jfarmer@goldsword.com Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk To throw another note in this thread (& perhaps tie it into the parity thread...) I just noticed this on the Asus web site: (URL: http://www.asus.com.tw/Products/TECHREF/P5/430hxq&a/K6-ParityErr.html) Question: I get a memory parity check error when ECC/Parity option is enabled in BIOS setup on my motherboard with a AMD K6 CPU installed. Answer: Please upgrade your BIOS with version 0203.004 or above to fix the problem. I don't remember the BIOS versions of the various "test" systems... John (Who has to go check BIOS rev's on some P55t2p4 boards...) ------------------------------------------------------------------------- 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 Aug 19 21:10:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA26692 for hardware-outgoing; Tue, 19 Aug 1997 21:10:20 -0700 (PDT) Received: from iago.ienet.com (iago.ienet.com [207.78.32.53]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA26676 for ; Tue, 19 Aug 1997 21:10:15 -0700 (PDT) Received: from iago.ienet.com (localhost.ienet.com [127.0.0.1]) by iago.ienet.com (8.8.5/8.8.5) with ESMTP id UAA16965 Tue, 19 Aug 1997 20:16:53 -0700 (PDT) Message-Id: <199708200316.UAA16965@iago.ienet.com> To: freebsd-hardware@freebsd.org From: pius@ienet.com Cc: terryl@ienet.com, robert@ienet.com Subject: wdunwedge failed Date: Tue, 19 Aug 1997 20:16:53 -0700 Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk We've got a machine with the following configuration: 100 MHz Pentium on an ASUS VX97 motherboard 32 MB RAM 1282 MB IDE drive (Seagate Medalist SL) 2 Intel EtherExpress PRO/100 ethernet adapters (fxp0 and fxp1) a cheap ISA video card FreeBSD 2.2-stable (from mid-June) After running fine for a little over a month, it started spewing out the following message on the console: wd0: wdunwedge failed: wd0: status 80 error 80 wd0s1e: wdstart: timeout waiting to give command writing fsbn 80 of 80-95 (wd0s1 bn 217168; cn 14 tn 157 sn 7)wd0: status 80 error 80 The console flashes on and off and logging in at the console or via telnet doesn't work anymore. However it still responds to pings and it forwards packets from one ethernet interface to the other. However, after about an hour of spewing out these messages, the machine completely dies and it won't come up after a reboot (DRIVE BOOT FAILURE). The last time this happened, we left the machine turned off for a couple days, then turned it on, and it actually booted up fine, and now, after running most of the day, it's spewing out those error messages again. Has anyone else seen this? What's causing these errors and the flashing console? Is it a bad drive or a bad IDE controller? The cabling looks fine. Thanks very much for any help, Pius From owner-freebsd-hardware Tue Aug 19 21:36:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA27962 for hardware-outgoing; Tue, 19 Aug 1997 21:36:01 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (soda.CSUA.Berkeley.EDU [128.32.43.52]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id VAA27947 for ; Tue, 19 Aug 1997 21:35:55 -0700 (PDT) Received: from soda.CSUA.Berkeley.EDU (jwm@localhost) by soda.CSUA.Berkeley.EDU (8.6.12/8.6.12) with ESMTP id VAA06529; Tue, 19 Aug 1997 21:35:44 -0700 Message-Id: <199708200435.VAA06529@soda.CSUA.Berkeley.EDU> To: "John T. Farmer" Cc: jin@george.lbl.gov, mburgett@cmnsens.zoom.com, hardware@freebsd.org, root@meeko.eecs.berkeley.edu Subject: Re: K6 - New results.. & [Added - Parity issues also?) In-reply-to: Message from "John T. Farmer" of "Tue, 19 Aug 1997 23:24:40 EDT." <199708200324.XAA26829@sabre.goldsword.com> Date: Tue, 19 Aug 1997 21:35:27 -0700 From: John Milford Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk "John T. Farmer" wrote: > > To throw another note in this thread (& perhaps tie it into the > parity thread...) > > I just noticed this on the Asus web site: > (URL: http://www.asus.com.tw/Products/TECHREF/P5/430hxq&a/K6-ParityErr.html) > > Question: > I get a memory parity check error when ECC/Parity option > is enabled in BIOS setup on my motherboard with a AMD K6 > CPU installed. > > Answer: > Please upgrade your BIOS with version 0203.004 or above to fix > the problem. > > I don't remember the BIOS versions of the various "test" systems... > > John (Who has to go check BIOS rev's on some P55t2p4 boards...) > If my K6/200 and ASUS P55t2p4 is any indication, you can't boot if you are hitting this problem. It was taking an NMI right after the BIOS banner, and before showing the system configuration. For those of you that are wondering, my K6 is seeing the make world problem. I haven't posted yet becuase I am waiting for a fan/peltier cooler to arrive so I can test with it. Unfortunately I don't have the date stamp off the chip because I am about 50 miles froim the the machine, and it is pulling 24x7 server duty now. It appears that the day to day duty I subject it to does not cause any problems. --JOhn From owner-freebsd-hardware Tue Aug 19 22:01:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA29046 for hardware-outgoing; Tue, 19 Aug 1997 22:01:25 -0700 (PDT) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA29040 for ; Tue, 19 Aug 1997 22:01:21 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.7/8.6.9) with ESMTP id WAA04476; Tue, 19 Aug 1997 22:01:01 -0700 (PDT) To: Stephen McKay cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Quiet SCSI disk? In-reply-to: Your message of "Wed, 20 Aug 1997 13:48:54 +1000." <199708200348.NAA21476@ogre.dtir.qld.gov.au> Date: Tue, 19 Aug 1997 22:01:01 -0700 Message-ID: <4472.872053261@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > I am very please with my DCAS 4GB drive, and certainly don't think of it > as slow (~7MB/s with iozone). I know a few people with the 2GB variant > and they have had no problems either. I just bought 3 of the 4.3GB DCAS drives (34330W) and they've all been performing just fine for me. Very quiet, very cool and, so far, reliable. At the current street price of $410-$450, I'd say they're also pretty good value. Jordan From owner-freebsd-hardware Tue Aug 19 22:05:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id WAA29261 for hardware-outgoing; Tue, 19 Aug 1997 22:05:19 -0700 (PDT) Received: from genesis.atrad.adelaide.edu.au (genesis.atrad.adelaide.edu.au [129.127.96.120]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id WAA29252 for ; Tue, 19 Aug 1997 22:05:11 -0700 (PDT) Received: from word.smith.net.au (lot.atrad.adelaide.edu.au [203.20.121.21]) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) with ESMTP id OAA22778 for ; Wed, 20 Aug 1997 14:35:07 +0930 (CST) Received: from word.smith.net.au (localhost.atrad.adelaide.edu.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id OAA01146; Wed, 20 Aug 1997 14:31:21 +0930 (CST) Message-Id: <199708200501.OAA01146@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: pius@ienet.com cc: freebsd-hardware@freebsd.org, terryl@ienet.com, robert@ienet.com Subject: Re: wdunwedge failed In-reply-to: Your message of "Tue, 19 Aug 1997 20:16:53 MST." <199708200316.UAA16965@iago.ienet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Wed, 20 Aug 1997 14:31:20 +0930 From: Mike Smith Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > After running fine for a little over a month, it started spewing out > the following message on the console: > > wd0: wdunwedge failed: > wd0: status 80 error 80 > wd0s1e: wdstart: timeout waiting to give command writing fsbn 80 of 80-95 > (wd0s1 bn 217168; cn 14 tn 157 sn 7)wd0: status 80 error 80 The disk appears to be dying > The console flashes on and off and logging in at the console or via telnet > doesn't work anymore. This is strange; what do you mean by "flashes on and off"? > Has anyone else seen this? What's causing these errors and the flashing > console? Is it a bad drive or a bad IDE controller? The cabling looks fine. It sounds like the drive is either overheating or on its way out; fix/replace it ASAP, and MAKE A BACKUP if you haven't already. mike From owner-freebsd-hardware Wed Aug 20 01:32:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA08507 for hardware-outgoing; Wed, 20 Aug 1997 01:32:43 -0700 (PDT) Received: from silvia.HIP.Berkeley.EDU (ala-ca13-16.ix.netcom.com [204.32.168.48]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id BAA08500 for ; Wed, 20 Aug 1997 01:32:39 -0700 (PDT) Received: (from asami@localhost) by silvia.HIP.Berkeley.EDU (8.8.7/8.6.9) id BAA01106; Wed, 20 Aug 1997 01:32:31 -0700 (PDT) Date: Wed, 20 Aug 1997 01:32:31 -0700 (PDT) Message-Id: <199708200832.BAA01106@silvia.HIP.Berkeley.EDU> To: tom@sdf.com CC: hardware@FreeBSD.ORG In-reply-to: (message from Tom Samplonius on Tue, 19 Aug 1997 13:55:38 -0700 (PDT)) Subject: Re: parity errors From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * > I think so. There are 36 identical-looking chips on each module. * > I've never seen such big SIMMs before. * * It is hard to find motherboards that support SIMMs with that many chips. * Most are 24 or less. Well, it appeared to work on my Asus P6NP5. I tried two make worlds, and a 12-hour session in which I ran five emacs compiles continuously in parallel. Not a single seg fault. Satoshi From owner-freebsd-hardware Wed Aug 20 13:11:04 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA06720 for hardware-outgoing; Wed, 20 Aug 1997 13:11:04 -0700 (PDT) Received: from vader.cs.berkeley.edu (vader.CS.Berkeley.EDU [128.32.38.234]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA06704 for ; Wed, 20 Aug 1997 13:10:55 -0700 (PDT) Received: (from asami@localhost) by vader.cs.berkeley.edu (8.8.6/8.7.3) id NAA04128; Wed, 20 Aug 1997 13:10:49 -0700 (PDT) Date: Wed, 20 Aug 1997 13:10:49 -0700 (PDT) Message-Id: <199708202010.NAA04128@vader.cs.berkeley.edu> To: rgrimes@GndRsh.aac.dev.com CC: tom@sdf.com, hardware@FreeBSD.ORG In-reply-to: <199708201505.IAA24962@GndRsh.aac.dev.com> (rgrimes@GndRsh.aac.dev.com) Subject: Re: parity errors From: asami@cs.berkeley.edu (Satoshi Asami) Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk * One set of 36 chip simms will run reliably in a P6NP5, but try putting * 2 sets (4 total simms) and you'll be on the bloody edge of what the * Natoma chipset memory drivers can provide. You can make it work by * lowering the memory timing to one step below your actual DRAM speed, * but this is only a ``sometimes'' fix. Well, maybe I am incredibly lucky, but the test I mentioned before was run with all four of the modules (256MB total) used simultaneously. ;) Satoshi From owner-freebsd-hardware Wed Aug 20 13:12:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA06819 for hardware-outgoing; Wed, 20 Aug 1997 13:12:49 -0700 (PDT) Received: from compus.com (root@mail.compus.com [206.234.67.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA06809 for ; Wed, 20 Aug 1997 13:12:46 -0700 (PDT) Received: from seeker.compus.com (localhost) by compus.com (5.x/SMI-SVR4) id AA10859; Wed, 20 Aug 1997 16:12:44 -0400 Message-Id: <9708202012.AA10859@compus.com> To: hardware@freeBSD.org Subject: For ISA and ethernet, what's better than an NE2000? Date: Wed, 20 Aug 1997 16:12:44 -0400 From: Harlan Stenn Sender: owner-freebsd-hardware@freeBSD.org X-Loop: FreeBSD.org Precedence: bulk For ISA machines, what's better than an NE2000 (or clone) network card? I seems like the Intel EtherPro/10+ looks good, as might an NE2100 (Kingston has these). I'm looking for a better card and I'd also like to know that the FreeBSD driver for the card is good, too. What do folks recommend? (I'm trying to avoid NE2000 cards because I'm tired of cranking down the NFS read and write sizes to 1024 when I use those cards). Thanks... H From owner-freebsd-hardware Wed Aug 20 13:13:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA06872 for hardware-outgoing; Wed, 20 Aug 1997 13:13:33 -0700 (PDT) Received: from iago.ienet.com (iago.ienet.com [207.78.32.53]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA06861 for ; Wed, 20 Aug 1997 13:13:26 -0700 (PDT) Received: from iago.ienet.com (localhost.ienet.com [127.0.0.1]) by iago.ienet.com (8.8.5/8.8.5) with ESMTP id NAA03577 Wed, 20 Aug 1997 13:13:15 -0700 (PDT) Message-Id: <199708202013.NAA03577@iago.ienet.com> From: pius@ienet.com To: Mike Smith Cc: freebsd-hardware@freebsd.org, terryl@ienet.com, robert@ienet.com Subject: Re: wdunwedge failed Date: Wed, 20 Aug 1997 13:13:15 -0700 Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 20 Aug 1997, mike@smith.net.au wrote: > > > The console flashes on and off and logging in at the console or via telnet > > doesn't work anymore. > > This is strange; what do you mean by "flashes on and off"? It flickers. For example, a screen full of these "wdunwedge failed" error messages appears for a second or two and then the screen completely blanks out for a second. Then the error messages are visible again briefly, then the screen goes blank, and so no. Sort of like someone quickly turning the monitor on and off. I wonder if this could be caused by the OS not being able to write to the drive or if this might be a problem with the motherboard. > It sounds like the drive is either overheating or on its way out; > fix/replace it ASAP, and MAKE A BACKUP if you haven't already. Yes, overheating seems to at least trigger this problem, but the drive may be dying as well. This morning with the AC back on, the machine came up fine again. Both times that it died was in the evening when the AC in the room had been turned off. The machine was acting only as a router with little more than the FreeBSD 2.2-970618 snapshot installed on the drive. So there's no important data that'll be lost if the drive dies. We're already using another machine to do the routing that the problem machine used to be doing. Thanks for the help, Pius From owner-freebsd-hardware Wed Aug 20 14:05:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA09358 for hardware-outgoing; Wed, 20 Aug 1997 14:05:00 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA09353 for ; Wed, 20 Aug 1997 14:04:54 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0x1Htx-0001z2-00; Wed, 20 Aug 1997 14:02:50 -0700 Date: Wed, 20 Aug 1997 14:02:48 -0700 (PDT) From: Tom Samplonius To: Harlan Stenn cc: hardware@freebsd.org Subject: Re: For ISA and ethernet, what's better than an NE2000? In-Reply-To: <9708202012.AA10859@compus.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, 20 Aug 1997, Harlan Stenn wrote: > For ISA machines, what's better than an NE2000 (or clone) network card? > > I seems like the Intel EtherPro/10+ looks good, as might an NE2100 (Kingston > has these). > > I'm looking for a better card and I'd also like to know that the FreeBSD driver > for the card is good, too. > > What do folks recommend? > > (I'm trying to avoid NE2000 cards because I'm tired of cranking down the NFS > read and write sizes to 1024 when I use those cards). > > Thanks... > > H > > > For ISA cards, look for something with shared memory. The SMC Ultra/16 is good with 16KB of shared-memory. The newer SMC EtherEZ 16 isn't as good, because it only has 8KB of shared-memory :(. The SMC Ultra/16 uses the ed drive, and is reliable. Tom From owner-freebsd-hardware Wed Aug 20 14:28:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id OAA10360 for hardware-outgoing; Wed, 20 Aug 1997 14:28:30 -0700 (PDT) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id OAA10355 for ; Wed, 20 Aug 1997 14:28:28 -0700 (PDT) Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id OAA19781; Wed, 20 Aug 1997 14:27:50 -0700 Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3) id RAA26718; Wed, 20 Aug 1997 17:27:47 -0400 Received: from compound.east.sun.com by suneast.East.Sun.COM (SMI-8.6/SMI-SVR4) id RAA05401; Wed, 20 Aug 1997 17:27:46 -0400 Received: (from alk@localhost) by compound.east.sun.com (8.8.6/8.7.3) id QAA02966; Wed, 20 Aug 1997 16:29:31 -0500 (CDT) Date: Wed, 20 Aug 1997 16:29:31 -0500 (CDT) Reply-To: Anthony.Kimball@East.Sun.COM Message-Id: <199708202129.QAA02966@compound.east.sun.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: pius@ienet.com Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: wdunwedge failed References: <199708202013.NAA03577@iago.ienet.com> X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Quoth pius@ienet.com on Wed, 20 August: : It flickers. For example, a screen full of these "wdunwedge failed" error : messages appears for a second or two and then the screen completely blanks : out for a second. Then the error messages are visible again briefly, then : the screen goes blank, and so no. Sort of like someone quickly turning the : monitor on and off. Sounds like a dead marmoset stuck in the transformer coils of your power supply. Have you been routing in the rainforest lately? Try releasing some mealworms to clean it out. Pius, eh. Say, weren't you Pope for a while? From owner-freebsd-hardware Wed Aug 20 15:25:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA13060 for hardware-outgoing; Wed, 20 Aug 1997 15:25:25 -0700 (PDT) Received: from lariat.lariat.org (ppp0.lariat.org@[129.72.251.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA13045 for ; Wed, 20 Aug 1997 15:25:19 -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 QAA23408; Wed, 20 Aug 1997 16:20:08 -0600 (MDT) Message-Id: <3.0.3.32.19970820162223.00967b70@mail.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.3 (32) Date: Wed, 20 Aug 1997 16:22:23 -0600 To: Anthony.Kimball@East.Sun.COM, pius@ienet.com From: Brett Glass Subject: Re: wdunwedge failed Cc: freebsd-hardware@FreeBSD.ORG In-Reply-To: <882564F9.00799310.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 Actually, it is much more likely that the display is redrawing, erasing, and scrolling so fast that it appears blank or dim. Which means the messages are coming in at a rate of hundreds per second. The WD driver has some busy-waits that could easily cause the rest of the system to freeze at the same time. --Brett At 04:29 PM 8/20/97 -0500, alk@pobox.com wrote: > > > >Quoth pius@ienet.com on Wed, 20 August: >: It flickers. For example, a screen full of these "wdunwedge failed" error >: messages appears for a second or two and then the screen completely >blanks >: out for a second. Then the error messages are visible again briefly, then >: the screen goes blank, and so no. Sort of like someone quickly turning >the >: monitor on and off. >Sounds like a dead marmoset stuck in the transformer coils of your >power supply. Have you been routing in the rainforest lately? >Try releasing some mealworms to clean it out. >Pius, eh. Say, weren't you Pope for a while? > > > > > > > From owner-freebsd-hardware Wed Aug 20 19:08:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA22376 for hardware-outgoing; Wed, 20 Aug 1997 19:08:13 -0700 (PDT) Received: from hobbes.saturn-tech.com (drussell@drussell.internode.net [198.161.228.154]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA22369 for ; Wed, 20 Aug 1997 19:08:09 -0700 (PDT) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id UAA17961; Wed, 20 Aug 1997 20:07:52 -0600 (MDT) Date: Wed, 20 Aug 1997 20:07:52 -0600 (MDT) From: Doug Russell To: Kyle Mestery cc: "Michael K. Sanders" , freebsd-hardware@FreeBSD.ORG Subject: Re: Source for 150MHz PPro? 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 Tue, 19 Aug 1997, Kyle Mestery wrote: > > I'm quite sure I can still get 'em for you... Unfortunately, I'm at home > > now so I can't double check right now. I'll check when I hit the office > > in the morning and let you know. > > > > Later...... > > > Could you post this to the list? I am also interested in possibly getting > some 150s. Thanks. Sorry for the delay, folks. The 150s are getting a LOT harder to find than I thought. I called just about all of my suppliers yesterday, and everyone said they were permanently out of stock now. Two I needed to call back, but I ended up out mapping a new network for a client yesterday afternoon. ANYWAY.... To the point. I managed to scrounge up a whack of 150s. How many people are interested? I should have up to about 30 available. I've thought about getting a dual P6 board and loading it with a couple of 150s for quite a while. If you run them at 66 Mhz bus, they should make a nice *cheap* dual 166 system, which beats the pants off a more expensive single processor machine. I may do that given the current prices, and near zilch availability we are getting into. For those who are interested, each 150 chip is $189 in Canadian dollars. For those of you in the US, exchange rate is *quite* favourable. $1.00US is about $1.35 Canadian right now, so each chip works out to about $140US. Shipping, applicable taxes, etc. is extra, but minimal. Shipping hurts less (not that FedExing a processor costs that much :) ) if you need a new dual processor board or something too. I've got Gigabyte 686DX boards for $499 Canadian (about $370US after exchange) or ASUS dual pro boards for $709 Canadian (about $525US). Or, of course, just about any other hardware you could possibly desire. :) Anyone who is interested in any of this stuff, send e-mail to drussell@saturn-tech.com, and I'll give you our 1-800 number to call me. Saturn is located in Calgary, Alberta, for those who are interested. Later...... Doug Russell President Saturn Computer Technologies Inc. A huge fan of FreeBSD! From owner-freebsd-hardware Wed Aug 20 23:20:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA01953 for hardware-outgoing; Wed, 20 Aug 1997 23:20:35 -0700 (PDT) Received: from dragon.awen.com (dragon.awen.com [207.33.155.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA01946 for ; Wed, 20 Aug 1997 23:20:32 -0700 (PDT) Received: from cmnsens (cmnsens.awen.com [207.33.155.2]) by dragon.awen.com (8.8.7/8.8.6) with SMTP id XAA04677 for ; Wed, 20 Aug 1997 23:20:26 -0700 (PDT) Message-Id: <199708210620.XAA04677@dragon.awen.com> From: "Mike Burgett" To: "hardware@freebsd.org" Date: Wed, 20 Aug 97 23:20:25 -0700 Reply-To: "Mike Burgett" Priority: Normal X-Mailer: PMMail 1.92 For OS/2 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Subject: Further K6 testing... Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I've been running a modified version of the Linux 'burnit' script, that compiles the kernel over and over and over... It uses a '-j4' argument to make, to be sure the processor usage is kept high (mine ran between about 2.5 and 3.5, depending on exactly where it was in the loop, and what else was going on...) Wed Aug 20 05:44:29 PDT 1997 FAILED: 0/0 Wed Aug 20 05:47:16 PDT 1997 FAILED: 0/1 Wed Aug 20 05:49:53 PDT 1997 FAILED: 0/2 Wed Aug 20 05:52:29 PDT 1997 FAILED: 0/3 Wed Aug 20 05:55:06 PDT 1997 FAILED: 0/4 Wed Aug 20 05:57:41 PDT 1997 FAILED: 0/5 Wed Aug 20 06:00:17 PDT 1997 FAILED: 0/6 Wed Aug 20 06:02:53 PDT 1997 FAILED: 0/7 Wed Aug 20 06:05:28 PDT 1997 FAILED: 0/8 Wed Aug 20 06:08:04 PDT 1997 FAILED: 0/9 [ ... some 17 hours later ... ] Wed Aug 20 22:44:45 PDT 1997 FAILED: 0/391 Wed Aug 20 22:47:20 PDT 1997 FAILED: 0/392 Wed Aug 20 22:49:55 PDT 1997 FAILED: 0/393 Wed Aug 20 22:52:31 PDT 1997 FAILED: 0/394 Wed Aug 20 22:55:07 PDT 1997 FAILED: 0/395 Wed Aug 20 22:57:44 PDT 1997 FAILED: 0/396 Wed Aug 20 23:00:20 PDT 1997 FAILED: 0/397 Wed Aug 20 23:02:56 PDT 1997 FAILED: 0/398 Wed Aug 20 23:05:33 PDT 1997 FAILED: 0/399 Wed Aug 20 23:08:09 PDT 1997 FAILED: 0/400 This is on the configuration I posted earlier, with the chip marked "B 9731FPAW" If anyone is interested in a copy of the modified 'burnit' script, drop me a line and I'll send you a copy... Thanks, Mike From owner-freebsd-hardware Wed Aug 20 23:38:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA02856 for hardware-outgoing; Wed, 20 Aug 1997 23:38:45 -0700 (PDT) Received: from word.smith.net.au (word.smith.net.au [202.0.75.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA02851 for ; Wed, 20 Aug 1997 23:38:41 -0700 (PDT) Received: from word.smith.net.au ([127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id LAA00493; Thu, 21 Aug 1997 11:27:16 +0930 (CST) Message-Id: <199708210157.LAA00493@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: pius@ienet.com cc: Mike Smith , freebsd-hardware@freeBSD.org, terryl@ienet.com, robert@ienet.com Subject: Re: wdunwedge failed In-reply-to: Your message of "Wed, 20 Aug 1997 13:13:15 MST." <199708202013.NAA03577@iago.ienet.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Aug 1997 11:26:35 +0930 From: Mike Smith Sender: owner-freebsd-hardware@freeBSD.org X-Loop: FreeBSD.org Precedence: bulk > > > > The console flashes on and off and logging in at the console or via telnet > > > doesn't work anymore. > > > > This is strange; what do you mean by "flashes on and off"? > > It flickers. For example, a screen full of these "wdunwedge failed" error > messages appears for a second or two and then the screen completely blanks > out for a second. Then the error messages are visible again briefly, then > the screen goes blank, and so no. Sort of like someone quickly turning the > monitor on and off. > > I wonder if this could be caused by the OS not being able to write to the > drive or if this might be a problem with the motherboard. It's possibly (as Brett suggested) that some delays in the wd code are magically synchronising with something in the display driver, but I'd actually be putting my money on something wrong either with the monitor or the system. A screenful of bright text may be more than the power supply in the monitor can handle (if it's old), or there may be something power-related that's afflicting both the drive and the video card. > Yes, overheating seems to at least trigger this problem, but the drive > may be dying as well. This morning with the AC back on, the machine came up > fine again. Both times that it died was in the evening when the AC in the > room had been turned off. Sounds like a clue to me. mike From owner-freebsd-hardware Thu Aug 21 02:00:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA08596 for hardware-outgoing; Thu, 21 Aug 1997 02:00:45 -0700 (PDT) Received: from hobbes.saturn-tech.com (drussell@drussell.internode.net [198.161.228.154]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA08584 for ; Thu, 21 Aug 1997 02:00:40 -0700 (PDT) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id DAA18515; Thu, 21 Aug 1997 03:00:28 -0600 (MDT) Date: Thu, 21 Aug 1997 03:00:28 -0600 (MDT) From: Doug Russell To: Mike Burgett cc: "hardware@freebsd.org" Subject: Re: Further K6 testing... In-Reply-To: <199708210620.XAA04677@dragon.awen.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, 20 Aug 1997, Mike Burgett wrote: > If anyone is interested in a copy of the modified 'burnit' script, drop me a > line and I'll send you a copy... Sure, fire over a copy. I'm getting an ASUS TX97E board and a K6-166 chip for personal testing. We sell lots of K6-equipped machines, but until now I have yet to add one to my personal collection of machines. I'm going to try it out in the Gigabyte VX board as well, which is pretty much our 'standard' board for production. I have yet to have a single complaint, even though the 586VX uses a linear regulator, etc. I'm considering switching our base board to the TX97E, but I need to do some severe thrashing with that configuration first. Very few of our productions machines likely see anywhere close to the load that anyone on this list puts on their machine, so I really want to test this out for myself under at least a few conditions. Later...... From owner-freebsd-hardware Thu Aug 21 02:12:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA09090 for hardware-outgoing; Thu, 21 Aug 1997 02:12:47 -0700 (PDT) Received: from hobbes.saturn-tech.com (drussell@drussell.internode.net [198.161.228.154]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA09085 for ; Thu, 21 Aug 1997 02:12:43 -0700 (PDT) Received: from localhost (drussell@localhost) by hobbes.saturn-tech.com (8.8.4/8.8.2) with SMTP id DAA18532; Thu, 21 Aug 1997 03:11:06 -0600 (MDT) Date: Thu, 21 Aug 1997 03:11:05 -0600 (MDT) From: Doug Russell To: Mike Smith cc: pius@ienet.com, freebsd-hardware@FreeBSD.ORG, terryl@ienet.com, robert@ienet.com Subject: Re: wdunwedge failed In-Reply-To: <199708210157.LAA00493@word.smith.net.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 On Thu, 21 Aug 1997, Mike Smith wrote: > > It flickers. For example, a screen full of these "wdunwedge failed" error > > messages appears for a second or two and then the screen completely blanks > > out for a second. Then the error messages are visible again briefly, then > > the screen goes blank, and so no. Sort of like someone quickly turning the > > monitor on and off. > > It's possibly (as Brett suggested) that some delays in the wd code are > magically synchronising with something in the display driver, but I'd ... I'd guess either the error messages are just scrolling fast, and end up flickering, or, especially by the way he describes it, that the video signal is actually interrupted. It may not be the problem, but I would take a multimeter and check out the +12 volt supply while the machine is in this failed state. The hard drive most likely uses the 12 volt for spindle motor, etc., and most VGA cards use the +12 and -12 supplies for the RAMDAC. If the 12 volt line is really funky (might need a scope to see if it is fluctuating, poorly filtered due to a dead filter capacitor or something, etc.), the power supply is the suspect. Method B, of course, is to swap in a known good supply, and see if the problem happens again. :) You'd be surprised how many strange problems are caused by a flakey power supply. Don't ever buy one of those cheapo $30 mini-tower (or whatever) case deals. The power supply in a $30 case probably isn't too wonderful. Getting better built cases is an added bonus, too. :) Later..,.... From owner-freebsd-hardware Thu Aug 21 02:18:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA09247 for hardware-outgoing; Thu, 21 Aug 1997 02:18:56 -0700 (PDT) Received: from bunyip.cc.uq.edu.au (daemon@bunyip.cc.uq.edu.au [130.102.2.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id CAA09242 for ; Thu, 21 Aug 1997 02:18:46 -0700 (PDT) Received: (from daemon@localhost) by bunyip.cc.uq.edu.au (8.8.7/8.8.7) id TAA27660; Thu, 21 Aug 1997 19:18:25 +1000 Received: from troll.dtir.qld.gov.au by ogre.dtir.qld.gov.au (8.7.5/DEVETIR-E0.3a) with ESMTP id TAA21391; Thu, 21 Aug 1997 19:18:47 +1000 (EST) Received: from localhost (syssgm@localhost) by troll.dtir.qld.gov.au (8.8.5/8.8.5) with SMTP id TAA14147; Thu, 21 Aug 1997 19:18:12 +1000 (EST) Message-Id: <199708210918.TAA14147@troll.dtir.qld.gov.au> X-Authentication-Warning: troll.dtir.qld.gov.au: syssgm@localhost didn't use HELO protocol To: Andreas Klemm cc: freebsd-hardware@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: Quiet SCSI disk? References: <199708200348.NAA21476@ogre.dtir.qld.gov.au> <4472.872053261@time.cdrom.com> <19970820150743.09240@wup.de> In-Reply-To: <19970820150743.09240@wup.de> from Andreas Klemm at "Wed, 20 Aug 1997 15:07:43 +0200" Date: Thu, 21 Aug 1997 19:18:11 +1000 From: Stephen McKay Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Wednesday, 20th August 1997, Andreas Klemm wrote: [about the 4GB DCAS 34330W] >Do you know how many tags it uses (tagged command queuing) ? >It was a bit disappointing for me, that the IBM DORS 32160 2.1GB >only offers 3 and the the famous QUEUE_FULL condistion ... I run mine off a Diamond FirePort 40 (uses the 53c875J chip). When I run ncrcontrol, it tells me it is using 4 tags. I don't know if I can use more. I remember reading somewhere that Stefan thinks 4 is a good number. I can't remember his reasoning, or where I read it. :-/ Stephen. From owner-freebsd-hardware Thu Aug 21 03:02:56 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA10401 for hardware-outgoing; Thu, 21 Aug 1997 03:02:56 -0700 (PDT) Received: from mail.wup.de (ns.wup.de [149.237.200.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA10396 for ; Thu, 21 Aug 1997 03:02:45 -0700 (PDT) Received: (from andreas@localhost) by mail.wup.de (8.8.6/8.8.7) id MAA11939; Thu, 21 Aug 1997 12:02:27 +0200 (CEST) Message-ID: <19970821120226.20829@wup.de> Date: Thu, 21 Aug 1997 12:02:26 +0200 From: Andreas Klemm To: Stephen McKay Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Quiet SCSI disk? References: <199708200348.NAA21476@ogre.dtir.qld.gov.au> <4472.872053261@time.cdrom.com> <19970820150743.09240@wup.de> <199708210918.TAA14147@troll.dtir.qld.gov.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.79 In-Reply-To: <199708210918.TAA14147@troll.dtir.qld.gov.au>; from Stephen McKay on Thu, Aug 21, 1997 at 07:18:11PM +1000 X-phone: Wiechers & Partner +49 2173 3964 161 X-fax: Wiechers & Partner +49 2173 3964 222 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Aug 21, 1997 at 07:18:11PM +1000, Stephen McKay wrote: > On Wednesday, 20th August 1997, Andreas Klemm wrote: > > [about the 4GB DCAS 34330W] > > >Do you know how many tags it uses (tagged command queuing) ? > >It was a bit disappointing for me, that the IBM DORS 32160 2.1GB > >only offers 3 and the the famous QUEUE_FULL condistion ... > > I run mine off a Diamond FirePort 40 (uses the 53c875J chip). When I run > ncrcontrol, it tells me it is using 4 tags. I don't know if I can use > more. I remember reading somewhere that Stefan thinks 4 is a good number. > I can't remember his reasoning, or where I read it. :-/ AHC driver uses normally 8 tags. Or 4 if card doesn't have much SCM space. And reduces the number of opennings to x, if a queue full race condition occurs, where x = 3 using the IBM DORS... which is nearly the same as running without tagged queuing ;-) if ((inq_data->flags & SID_CmdQue) && !(ahc->tagenable & mask)) { printf("%s: target %d Tagged Queuing Device\n", ahc_name(ahc), xs->sc_link->target); ahc->tagenable |= mask; if (ahc->scb_data->maxhscbs >= 16 || (ahc->flags & AHC_PAGESCBS)) { /* Default to 8 tags */ xs->sc_link->opennings += 6; } else { /* * Default to 4 tags on whimpy * cards that don't have much SCB * space and can't page. This prevents * a single device from hogging all * slots. We should really have a better * way of providing fairness. */ xs->sc_link->opennings += 2; } -- Wiechers & Partner Datentechnik GmbH phone: +49 2173 3964 161 Support Unix - Andreas Klemm fax: +49 2173 3964 222 An der alten Ziegelei 2 mail1: andreas.klemm@wup.de D-40789 Monheim mail2: andreas@FreeBSD.ORG From owner-freebsd-hardware Thu Aug 21 03:09:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA10575 for hardware-outgoing; Thu, 21 Aug 1997 03:09:36 -0700 (PDT) Received: from iworks.InterWorks.org (deischen@iworks.interworks.org [128.255.18.10]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA10570 for ; Thu, 21 Aug 1997 03:09:29 -0700 (PDT) Received: (from deischen@localhost) by iworks.InterWorks.org (8.7.5/) id EAA13128; Thu, 21 Aug 1997 04:33:08 -0500 (CDT) Message-Id: <199708210933.EAA13128@iworks.InterWorks.org> Date: Thu, 21 Aug 1997 04:33:08 -0500 (CDT) From: "Daniel M. Eischen" To: andreas@wup.de, freebsd-hardware@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: Quiet SCSI disk? Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > [about the 4GB DCAS 34330W] > > >Do you know how many tags it uses (tagged command queuing) ? > >It was a bit disappointing for me, that the IBM DORS 32160 2.1GB > >only offers 3 and the the famous QUEUE_FULL condistion ... > > I run mine off a Diamond FirePort 40 (uses the 53c875J chip). When I run > ncrcontrol, it tells me it is using 4 tags. I don't know if I can use > more. I remember reading somewhere that Stefan thinks 4 is a good number. > I can't remember his reasoning, or where I read it. :-/ My IBM 32160: sd0: type 0 fixed SCSI 2 sd0: Direct-Access 2063MB (4226725 512 byte sectors) can do at least 16 tags. I've tested it under Linux with 16 tags and use the default 8 tags under FreeBSD (both with aic7xxx drivers). Dan Eischen deischen@iworks.InterWorks.org From owner-freebsd-hardware Thu Aug 21 03:11:52 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA10688 for hardware-outgoing; Thu, 21 Aug 1997 03:11:52 -0700 (PDT) Received: from mail.wup.de (ns.wup.de [149.237.200.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA10683 for ; Thu, 21 Aug 1997 03:11:46 -0700 (PDT) Received: (from andreas@localhost) by mail.wup.de (8.8.6/8.8.7) id MAA15063; Thu, 21 Aug 1997 12:11:22 +0200 (CEST) Message-ID: <19970821121122.45543@wup.de> Date: Thu, 21 Aug 1997 12:11:22 +0200 From: Andreas Klemm To: "Daniel M. Eischen" Cc: freebsd-hardware@FreeBSD.ORG, syssgm@dtir.qld.gov.au Subject: Re: Quiet SCSI disk? References: <199708210933.EAA13128@iworks.InterWorks.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.79 In-Reply-To: <199708210933.EAA13128@iworks.InterWorks.org>; from Daniel M. Eischen on Thu, Aug 21, 1997 at 04:33:08AM -0500 X-phone: Wiechers & Partner +49 2173 3964 161 X-fax: Wiechers & Partner +49 2173 3964 222 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, Aug 21, 1997 at 04:33:08AM -0500, Daniel M. Eischen wrote: > > > [about the 4GB DCAS 34330W] > > > > >Do you know how many tags it uses (tagged command queuing) ? > > >It was a bit disappointing for me, that the IBM DORS 32160 2.1GB > > >only offers 3 and the the famous QUEUE_FULL condistion ... > > > > I run mine off a Diamond FirePort 40 (uses the 53c875J chip). When I run > > ncrcontrol, it tells me it is using 4 tags. I don't know if I can use > > more. I remember reading somewhere that Stefan thinks 4 is a good number. > > I can't remember his reasoning, or where I read it. :-/ > > My IBM 32160: > > sd0: type 0 fixed SCSI 2 > sd0: Direct-Access 2063MB (4226725 512 byte sectors) > > can do at least 16 tags. I've tested it under Linux with 16 > tags and use the default 8 tags under FreeBSD (both with aic7xxx > drivers). Ah, you have the Wide scsi disk ... I have the narrow modell. This can't do more than 3 tags. -- Wiechers & Partner Datentechnik GmbH phone: +49 2173 3964 161 Support Unix - Andreas Klemm fax: +49 2173 3964 222 An der alten Ziegelei 2 mail1: andreas.klemm@wup.de D-40789 Monheim mail2: andreas@FreeBSD.ORG From owner-freebsd-hardware Thu Aug 21 03:39:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA11822 for hardware-outgoing; Thu, 21 Aug 1997 03:39:26 -0700 (PDT) Received: from bagpuss.visint.co.uk (bagpuss.visint.co.uk [194.207.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id DAA11813 for ; Thu, 21 Aug 1997 03:39:18 -0700 (PDT) Received: from dylan.visint.co.uk (dylan.visint.co.uk [194.207.134.180]) by bagpuss.visint.co.uk (8.7.5/8.7.3) with SMTP id LAA18159 for ; Thu, 21 Aug 1997 11:39:13 +0100 (BST) Date: Thu, 21 Aug 1997 11:39:31 +0100 (BST) From: Stephen Roome To: freebsd-hardware@freebsd.org Subject: What computer to buy ? 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 Well, my home computer is still a P100, and last night the hard drive died. So it's time to buy new bits. I thought I'd just get myself a new HD, but now I'm thinking that I should perhaps get myself an Ultra DMA IDE disc and a for that I'd need a new motherboard, and while prices are bottomed out for a while a new processor. Here's the options : 1) Pentium Pro 166 - no idea what motherboard and hard disc I can get with these, it'd have to be IDE (cost) and I don't know what the boards support. problem, if I get DIE (oops IDE =)) then I want Ultra DMA (windows dual boot) for performance, and I'm not sure of any PPRo boards which support UltraDMA IDE, or even support more than 66MHz bus speed. etc. etc. i.e. I know nothing about PPro's =) 2) Pentium [MMX or classic pentium) 200 Mhz (or 233 even) on a motherboard clocked at 75 or 83Mhz bus speed (e.g. FIC PA2007 or ABIT IT5H). problem: haven't got the faintest idea which boards are supporting 83MHz bus speeds properly or which boards support more than 64MB cacheable RAM. (I'm not buying RAM for a while, so I've got 32MB of EDO to use in the board I buy - unless I get the new ABIT board without 72pin FPRAM type slots.) Well, after all this, I've checked Tom's Hardware guide (which is looking neglected) and the figures are all windows only, which is something I'm not going to worry much about as I'm only using windows for wavetable with my soundcard. So, I want a fast machine for the following: quake (I've got an okay video card for now.) programming (It has to compile fast - mmm big deal) futureproof (ish) without buying an excessively overpriced Pentium II. Basically I think Pentium Pro is out, I just can't justify it yet, unless there are some damn nice PPro motherboards out there that anyone knows about with UltraDMA support. So, I think it boils down to which motherboard should I buy. Pentium or PPro, if anyone has any ideas or good sources of information please let me know. Hopefully I can get hold of a processor before Intel take all the Pentiums out of circulation (here in the uk at least it's heading that way). Thanks in advance. Steve P.S. I might not be subscribed to this list, or is hardware just a quiet list (that'd be odd considering recent developments!). -- Steve Roome - Vision Interactive Ltd. Tel:+44(0)117 9730597 Home:+44(0)976 241342 WWW: http://dylan.visint.co.uk/ From owner-freebsd-hardware Thu Aug 21 04:20:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA13758 for hardware-outgoing; Thu, 21 Aug 1997 04:20:05 -0700 (PDT) Received: from rfd1.oit.umass.edu (mailhub.oit.umass.edu [128.119.175.4]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA13705 for ; Thu, 21 Aug 1997 04:19:59 -0700 (PDT) Received: from lessing.oit.umass.edu by rfd1.oit.umass.edu (PMDF V5.1-8 #20973) with ESMTP id <0EF9GT9R500NGU@rfd1.oit.umass.edu> for hardware@FreeBSD.ORG; Thu, 21 Aug 1997 07:19:57 -0400 (EDT) Received: (from gp@localhost) by lessing.oit.umass.edu (8.8.3/8.8.6) id HAA12683 for hardware@FreeBSD.ORG; Thu, 21 Aug 1997 07:19:56 -0400 (EDT) Date: Thu, 21 Aug 1997 07:19:56 -0400 (EDT) From: Gregory Pavelcak Subject: Master/Slave or Master/Master To: hardware@FreeBSD.ORG Message-id: <199708211119.HAA12683@lessing.oit.umass.edu> MIME-version: 1.0 X-Mailer: ELM [version 2.4 PL25] Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Sorry for the non-BSD post, but just a quick question. I have IDE hard drive and CDROM. I assume I can set them up as primary master/primary slave or primary master/secondary master. Is there any reason at all to prefer one of these configurations to the other? Thanks. Greg From owner-freebsd-hardware Thu Aug 21 04:34:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA14848 for hardware-outgoing; Thu, 21 Aug 1997 04:34:58 -0700 (PDT) Received: from delenn.fl.net.au (root@delenn.fl.net.au [203.22.184.6]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id EAA14843 for ; Thu, 21 Aug 1997 04:34:53 -0700 (PDT) Received: from hari.fl.net.au (adf@hari.fl.net.au [203.22.184.25]) by delenn.fl.net.au (2.0/fl) with SMTP id VAA03224 for ; Thu, 21 Aug 1997 21:34:51 +1000 (EST) Message-Id: <199708211134.VAA03224@delenn.fl.net.au> From: "Andrew Foster" To: Subject: Pentium II & Idle Problem Date: Thu, 21 Aug 1997 21:33:48 +1000 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1008.3 X-MimeOle: Produced By Microsoft MimeOLE Engine V4.71.1008.3 Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, I've just installed a Pentium II 266Mhz CPU and motherboard into a 2.2.1-RELEASE box and after a few hours it panics with : Fatal trap 12: page fault while in kernel mode fault virtual address = 0x10 fault code = supervisor read, page not present instruction pointer = 0x8:0xf0132326 stack pointer = 0x10:0xf01e4e18 frame pointer = 0x10:0xf01e4e28 code segment = base 0x0, limit 0xfffff, type 0x1b = DPL 0, pres 1, def32 1, gran 1 processor eflags = interrupt enabled, resume, IOPL = 0 current process = Idle interrupt mask = bio kernel: type 12 trap, code=0 Stopped at _vget+0x8e: movl 0x10(%edx),%eax db> panic panic: from debugger Debugger("panic") Stopped at _Debugger+0x35: movb $0,_in_Debugger.118 My dmesg output is as follows : FreeBSD 2.2.1-RELEASE #0: Thu Aug 21 16:04:19 EST 1997 CPU: Pentium Pro (267.27-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x633 Stepping=3 Features=0x80f9ff,MTRR,PGE,MCA,CMOV > real memory = 134217728 (131072K bytes) avail memory = 129339392 (126308K bytes) Probing for devices on PCI bus 0: chip0 rev 2 on pci0:0 chip1 rev 1 on pci0:7:0 chip2 rev 0 on pci0:7:1 ahc0 rev 0 int a irq 11 on pci0:14 ahc0: aic7880 Single Channel, SCSI Id=7, 16 SCBs ahc0 waiting for scsi devices to settle (ahc0:0:0): "IBM DORS-32160 WA6A" type 0 fixed SCSI 2 sd0(ahc0:0:0): Direct-Access 2063MB (4226725 512 byte sectors) (ahc0:3:0): "IBM OEM DFHSS4F 4141" type 0 fixed SCSI 2 sd1(ahc0:3:0): Direct-Access 4303MB (8813870 512 byte sectors) (ahc0:5:0): "Quantum XP34300W L912" type 0 fixed SCSI 2 sd2(ahc0:5:0): Direct-Access 4101MB (8399520 512 byte sectors) (ahc0:6:0): "iomega jaz 1GB H.62" type 0 removable SCSI 2 sd3(ahc0:6:0): Direct-Access sd3(ahc0:6:0): ILLEGAL REQUEST asc:24,0 Invalid field in CDB sd3 could not mode sense (4). Using ficticious geometry sd3(ahc0:6:0): NOT READY asc:3a,0 Medium not present sd3: could not get size 0MB (0 512 byte sectors) vga0 rev 0 int a irq ?? on pci0:15 Probing for devices on the ISA bus: sc0 at 0x60-0x6f irq 1 on motherboard sc0: VGA color <16 virtual consoles, flags=0x0> ed0 at 0x300-0x31f irq 5 on isa ed0: address 00:00:01:16:63:56, type NE2000 (16 bit) sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x378-0x37f irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: NEC 72065B fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0x80ff80ff on isa wdc0: unit 0 (wd0): , 32-bit, multi-block-16 wd0: 2014MB (4124736 sectors), 4092 cyls, 16 heads, 63 S/T, 512 B/S npx0 on motherboard npx0: INT 16 interface changing root device to wd0a Is this issue resolved in a 3.0-SNAP or -current at all? If not is there any workaround for this issue besides returning the board for a Pentium Pro 200 ? (Please cc' replies). Regards, Andrew Foster -------------------------------------------------------------------- Andrew Foster System & Network Administrator First Link Internet Services (http://www.fl.net.au) Internet Access in Sydney, Newcastle & Surrounding Regions From owner-freebsd-hardware Thu Aug 21 07:56:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA24711 for hardware-outgoing; Thu, 21 Aug 1997 07:56:37 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA24705 for ; Thu, 21 Aug 1997 07:56:35 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id IAA17197; Thu, 21 Aug 1997 08:55:52 -0600 (MDT) Message-Id: <199708211455.IAA17197@pluto.plutotech.com> To: Andreas Klemm cc: Stephen McKay , freebsd-hardware@FreeBSD.ORG Subject: Re: Quiet SCSI disk? In-reply-to: Your message of "Thu, 21 Aug 1997 12:02:26 +0200." <19970821120226.20829@wup.de> Date: Thu, 21 Aug 1997 08:55:02 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >AHC driver uses normally 8 tags. >Or 4 if card doesn't have much SCM space. >And reduces the number of opennings to x, if a queue full race >condition occurs, where x = 3 using the IBM DORS... which is nearly >the same as running without tagged queuing ;-) > This changes with the new CAM code. All controller types can now page up to 255 commands (the aic7770, aic7850, and aic7860 doing this via "indirect paging" which costs an extra byte sized DMA). CAM also is much better at handling the QUEUE FULL and BUSY status conditions making it possible to properly dynamically size the number of transactions to use so long as the drive isn't "broken". On my CAM test system, the number of tags starts out at 64 for all devices, drops to 63 on the Seagate Hawks, drops to 16 on the Quantum Empire 2100, and is fixed (via a quirk entry) at 24 on the two Atlas II drives I have. The Atlas II is fixed at a particular number since it will return QUEUE FULL due to temporary internal resource shortages yet generally it can handle lots of tags. The algorithm that CAM uses is to "freeze" the transaction queue to a device that returns QUEUE FULL until a successful transaction completes, so even if the tag number is not reduced, the drive is not bombarded by requests as is the case in the current system. The increased number of tags that I'm able to use now makes the system much more responsive. I don't think that 4 is the optimum number for seek intensive workloads like a news expire. >-- >Wiechers & Partner Datentechnik GmbH phone: +49 2173 3964 161 >Support Unix - Andreas Klemm fax: +49 2173 3964 222 >An der alten Ziegelei 2 mail1: andreas.klemm@wup.de >D-40789 Monheim mail2: andreas@FreeBSD.ORG > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hardware Thu Aug 21 08:20:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA26456 for hardware-outgoing; Thu, 21 Aug 1997 08:20:40 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA26432 for ; Thu, 21 Aug 1997 08:20:31 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0x1Z0K-0002b8-00; Thu, 21 Aug 1997 08:18:32 -0700 Date: Thu, 21 Aug 1997 08:18:31 -0700 (PDT) From: Tom Samplonius To: Andrew Foster cc: freebsd-hardware@freebsd.org Subject: Re: Pentium II & Idle Problem In-Reply-To: <199708211134.VAA03224@delenn.fl.net.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 On Thu, 21 Aug 1997, Andrew Foster wrote: ... > Is this issue resolved in a 3.0-SNAP or -current at all? If not is there > any workaround for this issue besides returning the board for a Pentium Pro > 200 ? Why worry about 3.0-SNAP or current? You aren't even running the latest RELEASE software yet! FreeBSD doesn't have problems with PIIs. It could because you are running an old release (2.2.1), and running into bugs. Or, because your news processor and/or new mb are bad. > (Please cc' replies). > > Regards, > Andrew Foster > > > -------------------------------------------------------------------- > Andrew Foster System & Network Administrator > First Link Internet Services (http://www.fl.net.au) > Internet Access in Sydney, Newcastle & Surrounding Regions > > > > > > Tom From owner-freebsd-hardware Thu Aug 21 08:31:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA27595 for hardware-outgoing; Thu, 21 Aug 1997 08:31:10 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA27580 for ; Thu, 21 Aug 1997 08:31:06 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0x1ZAT-0002bv-00; Thu, 21 Aug 1997 08:29:01 -0700 Date: Thu, 21 Aug 1997 08:29:01 -0700 (PDT) From: Tom Samplonius To: Andreas Klemm cc: Stephen McKay , freebsd-hardware@freebsd.org Subject: Re: Quiet SCSI disk? In-Reply-To: <19970821120226.20829@wup.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 Thu, 21 Aug 1997, Andreas Klemm wrote: > On Thu, Aug 21, 1997 at 07:18:11PM +1000, Stephen McKay wrote: > > On Wednesday, 20th August 1997, Andreas Klemm wrote: > > > > [about the 4GB DCAS 34330W] > > > > >Do you know how many tags it uses (tagged command queuing) ? > > >It was a bit disappointing for me, that the IBM DORS 32160 2.1GB > > >only offers 3 and the the famous QUEUE_FULL condistion ... > > > > I run mine off a Diamond FirePort 40 (uses the 53c875J chip). When I run > > ncrcontrol, it tells me it is using 4 tags. I don't know if I can use > > more. I remember reading somewhere that Stefan thinks 4 is a good number. > > I can't remember his reasoning, or where I read it. :-/ > > AHC driver uses normally 8 tags. > Or 4 if card doesn't have much SCM space. > And reduces the number of opennings to x, if a queue full race > condition occurs, where x = 3 using the IBM DORS... which is nearly > the same as running without tagged queuing ;-) Beware. The ncr driver allocates up to 4 tags per device. The ahc driver has a certain number of tags per channel (and it isn't easy to see how many tags a device is using). This number is determined by the card type. Most have 16 tags per channel (the 2940UW definitely has 16SCBs). This number can be increased via paging the SCBs to system RAM. Adaptec has been cheapening their 2940 line. The original 2940 had 16 SCBs, but newer cards only have 8. I think the only 2940 with 16 SCBs is the 2940UW. Adaptec also made a 3940 with 255 SCBs, but newer 3940s also only have 16. > -- > Wiechers & Partner Datentechnik GmbH phone: +49 2173 3964 161 > Support Unix - Andreas Klemm fax: +49 2173 3964 222 > An der alten Ziegelei 2 mail1: andreas.klemm@wup.de > D-40789 Monheim mail2: andreas@FreeBSD.ORG > > Tom From owner-freebsd-hardware Thu Aug 21 08:58:33 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA29506 for hardware-outgoing; Thu, 21 Aug 1997 08:58:33 -0700 (PDT) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id IAA29501 for ; Thu, 21 Aug 1997 08:58:28 -0700 (PDT) Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id IAA14006; Thu, 21 Aug 1997 08:57:53 -0700 Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3) id LAA21122; Thu, 21 Aug 1997 11:57:50 -0400 Received: from compound.east.sun.com by suneast.East.Sun.COM (SMI-8.6/SMI-SVR4) id LAA17402; Thu, 21 Aug 1997 11:57:49 -0400 Received: (from alk@localhost) by compound.east.sun.com (8.8.6/8.7.3) id KAA06052; Thu, 21 Aug 1997 10:59:49 -0500 (CDT) Date: Thu, 21 Aug 1997 10:59:49 -0500 (CDT) Reply-To: Anthony.Kimball@East.Sun.COM Message-Id: <199708211559.KAA06052@compound.east.sun.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: steve@visint.co.uk Cc: freebsd-hardware@FreeBSD.ORG Subject: What computer to buy ? References: X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Quoth Stephen Roome on Thu, 21 August: : futureproof (ish) without buying an excessively overpriced Pentium II. Pentium II is just about the opposite of futureproof -- it is planned obsolescence: Slot 1 has a very short lifetime plan. From owner-freebsd-hardware Thu Aug 21 09:32:02 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA02014 for hardware-outgoing; Thu, 21 Aug 1997 09:32:02 -0700 (PDT) Received: from bagpuss.visint.co.uk (bagpuss.visint.co.uk [194.207.134.1]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA01953 for ; Thu, 21 Aug 1997 09:31:58 -0700 (PDT) Received: from dylan.visint.co.uk (dylan.visint.co.uk [194.207.134.180]) by bagpuss.visint.co.uk (8.7.5/8.7.3) with SMTP id RAA23088; Thu, 21 Aug 1997 17:31:43 +0100 (BST) Date: Thu, 21 Aug 1997 17:32:06 +0100 (BST) From: Stephen Roome To: Anthony.Kimball@East.Sun.COM cc: freebsd-hardware@FreeBSD.ORG Subject: Re: What computer to buy ? In-Reply-To: <199708211559.KAA06052@compound.east.sun.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 Thu, 21 Aug 1997, Tony Kimball wrote: > Quoth Stephen Roome on Thu, 21 August: > : futureproof (ish) without buying an excessively overpriced Pentium II. > > Pentium II is just about the opposite of futureproof -- it is planned > obsolescence: Slot 1 has a very short lifetime plan. Sorry, I didn't mean it like that! I meant I wan't something futureproof in that I won't need much more performance, not that I won't be able to run Windoze 97 or install a Descutes or whatever intel plans for.. Maybe "slot two" will be more reasonable, but from the specs I keep seeing, there's no good reason to be buying a Pentium II (apart from inability to get hold of any other Intel processors expect 486's!) -- Steve Roome - Vision Interactive Ltd. Tel:+44(0)117 9730597 Home:+44(0)976 241342 WWW: http://dylan.visint.co.uk/ From owner-freebsd-hardware Thu Aug 21 09:55:59 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA03422 for hardware-outgoing; Thu, 21 Aug 1997 09:55:59 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA03408 for ; Thu, 21 Aug 1997 09:55:56 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id KAA20737; Thu, 21 Aug 1997 10:55:35 -0600 (MDT) Message-Id: <199708211655.KAA20737@pluto.plutotech.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Tom Samplonius cc: Andreas Klemm , Stephen McKay , freebsd-hardware@FreeBSD.ORG Subject: Re: Quiet SCSI disk? In-reply-to: Your message of "Thu, 21 Aug 1997 08:29:01 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Aug 1997 10:54:43 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Beware. The ncr driver allocates up to 4 tags per device. The ahc >driver has a certain number of tags per channel (and it isn't easy to see >how many tags a device is using). This number is determined by the card >type. Most have 16 tags per channel (the 2940UW definitely has 16SCBs). >This number can be increased via paging the SCBs to system RAM. > > Adaptec has been cheapening their 2940 line. The original 2940 had 16 >SCBs, but newer cards only have 8. I think the only 2940 with 16 >SCBs is the 2940UW. Adaptec also made a 3940 with 255 SCBs, but newer >3940s also only have 16. Just to clear up any misconceptions: Chip # of SCBs # of slots in FIFOs paging #tags CAM paging #tags aic7770 4 4 N/A 255 aic7850 3 8 8 255 aic7860 3 8 8 255 aic7870 16 16 255 255 aic7880 16 16 255 255 Card Model Chip External SCB RAM 2940 aic7870 NO DISCONTINUED 2940W aic7870 NO DISCONTINUED 3940 aic7870 NO DISCONTINUED 3940W aic7870 NO DISCONTINUED 2940U aic7880 NO DISCONTINUED 2940UW aic7880 NO 3940U aic7880 NO 3940UW aic7880 NO 2940AU aic7860 NO 3980 aic7870 YES DISCONTINUED 3980W aic7870 YES DISCONTINUED 3980U aic7880 YES 3980UW aic7880 YES 3985 aic7870 YES DISCONTINUED 3985W aic7870 YES DISCONTINUED 3985U aic7880 YES 3985UW aic7880 YES Adapters with external SRAM can be configured to have 255 SCBs, but since I've never had access to a card to experiment with enabling this feature, the current aic7xxx driver does not support this mode. >Tom -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hardware Thu Aug 21 10:19:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA04984 for hardware-outgoing; Thu, 21 Aug 1997 10:19:22 -0700 (PDT) Received: from punt-1.mail.demon.net (relay-13.mail.demon.net [194.217.242.137]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA04977; Thu, 21 Aug 1997 10:19:15 -0700 (PDT) Received: from leys.demon.co.uk ([194.222.64.103]) by punt-1.mail.demon.net id aa0924236; 21 Aug 97 17:50 BST Received: from fluorine.theleys.cambs.sch.uk (fluorine.theleys.cambs.sch.uk [10.0.1.9]) by hydrogen.theleys.cambs.sch.uk (8.7.5/8.7.3) with SMTP id RAA00472; Thu, 21 Aug 1997 17:12:32 +0100 (BST) Date: Thu, 21 Aug 1997 17:10:47 +0100 (BST) From: "Dr R.D. Gidden" Subject: Re: 100Mbit fibre net card (was Net interface card) To: FreeBSD Hardware Cc: FreeBSD Questions Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; CHARSET=ISO-8859-1 X-Organization: The Leys School, Cambridge, CB2 2AD, U.K. X-Mailer: ANT RISCOS Marcel [ver 1.08] Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I asked a few weeks ago about what sort of net- interface card which worked at 100Mbit and went straight out on multimode fibre (ST conns). Four of you folk were kind enough to reply: Thanks! May I report I have now installed - working :-)) an Allied Telesyn AT-2560FX (PCI) [ UKP279.00+tax] and it is working fine using the fxp0 driver. Regards, Bob. -- rdg@theleys.cambs.sch.uk From owner-freebsd-hardware Thu Aug 21 10:19:58 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA05042 for hardware-outgoing; Thu, 21 Aug 1997 10:19:58 -0700 (PDT) Received: from as5200-port-254.no.neosoft.com (as5200-port-254.no.neosoft.com [206.27.167.254]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA05032 for ; Thu, 21 Aug 1997 10:19:47 -0700 (PDT) Received: (from conrads@localhost) by as5200-port-254.no.neosoft.com (8.8.7/8.8.6) id MAA00945; Thu, 21 Aug 1997 12:16:53 -0500 (CDT) Message-ID: X-Mailer: XFMail 1.2-alpha [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199708211559.KAA06052@compound.east.sun.com> Date: Thu, 21 Aug 1997 12:16:53 -0500 (CDT) Organization: NeoSoft, Inc. From: Conrad Sabatier To: Anthony.Kimball@East.Sun.COM Subject: Re: What computer to buy ? Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On 21-Aug-97 Tony Kimball wrote: > >Pentium II is just about the opposite of futureproof -- it is planned >obsolescence: Slot 1 has a very short lifetime plan. Could you possibly elaborate on this a bit? A friend of mine is considering purchasing a Pentium II (266 MHz) system, and I'd like to know if I should warn him off of it. Thanks. -- Conrad Sabatier | FreeBSD -- UNIX for your PC | Why settle for less than the best? http://www.neosoft.com/~conrads/ | http://www.freebsd.org From owner-freebsd-hardware Thu Aug 21 10:45:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA06492 for hardware-outgoing; Thu, 21 Aug 1997 10:45:40 -0700 (PDT) Received: from mercury.Sun.COM (mercury.Sun.COM [192.9.25.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id KAA06487 for ; Thu, 21 Aug 1997 10:45:34 -0700 (PDT) Received: from East.Sun.COM ([129.148.1.241]) by mercury.Sun.COM (SMI-8.6/mail.byaddr) with SMTP id KAA09149; Thu, 21 Aug 1997 10:45:03 -0700 Received: from suneast.East.Sun.COM by East.Sun.COM (SMI-8.6/SMI-5.3) id NAA02097; Thu, 21 Aug 1997 13:45:00 -0400 Received: from compound.east.sun.com by suneast.East.Sun.COM (SMI-8.6/SMI-SVR4) id NAA01947; Thu, 21 Aug 1997 13:44:59 -0400 Received: (from alk@localhost) by compound.east.sun.com (8.8.6/8.7.3) id MAA06419; Thu, 21 Aug 1997 12:47:01 -0500 (CDT) Date: Thu, 21 Aug 1997 12:47:01 -0500 (CDT) Reply-To: Anthony.Kimball@East.Sun.COM Message-Id: <199708211747.MAA06419@compound.east.sun.com> From: Tony Kimball MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: conrads@neosoft.com Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: What computer to buy ? References: <199708211559.KAA06052@compound.east.sun.com> X-Face: O9M"E%K;(f-Go/XDxL+pCxI5*gr[=FN@Y`cl1.Tn Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Quoth Conrad Sabatier on Thu, 21 August: : : On 21-Aug-97 Tony Kimball wrote: : > : >Pentium II is just about the opposite of futureproof -- it is planned : >obsolescence: Slot 1 has a very short lifetime plan. : : Could you possibly elaborate on this a bit? A friend of mine is : considering purchasing a Pentium II (266 MHz) system, and I'd like to know : if I should warn him off of it. It's just that the P2 form factor is unique to the P2. As I understand it, there will be Slot 2 modules within a year. I don't know that any other manufacturer will be producing Slot 1 modules. So, if you get a P2, you have to discard your motherboard when you upgrade. Since the P2 is selling at such a large premium, this may not be terribly large proportion of the cost, actually. My personal habit is to buy the most *cost-effective* hardware. Thus I strongly prefer Socket 7 processors which have a future upgrade path, commodity motherboards, etc. From owner-freebsd-hardware Thu Aug 21 11:34:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA10903 for hardware-outgoing; Thu, 21 Aug 1997 11:34:30 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA10893 for ; Thu, 21 Aug 1997 11:34:24 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0x1c1s-0002ig-00; Thu, 21 Aug 1997 11:32:20 -0700 Date: Thu, 21 Aug 1997 11:32:20 -0700 (PDT) From: Tom Samplonius To: Anthony.Kimball@East.Sun.COM cc: steve@visint.co.uk, freebsd-hardware@freebsd.org Subject: Re: What computer to buy ? In-Reply-To: <199708211559.KAA06052@compound.east.sun.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 Thu, 21 Aug 1997, Tony Kimball wrote: > Quoth Stephen Roome on Thu, 21 August: > : futureproof (ish) without buying an excessively overpriced Pentium II. > > Pentium II is just about the opposite of futureproof -- it is planned > obsolescence: Slot 1 has a very short lifetime plan. But all Intel CPUs have planned obsolescence. There is only so much you can do with CPU development and keep the connector the same. Besides a typical CPU costs almost twice as much a the motherboard, so who cares about whether the connector is going to change? In a year, the mb isn't going to be worth anything, anyhow. BTW, don't get screwed on PII 266 prices. Prices have already dropped, but some are still selling at old prices. Tom From owner-freebsd-hardware Thu Aug 21 11:40:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA11370 for hardware-outgoing; Thu, 21 Aug 1997 11:40:49 -0700 (PDT) Received: from misery.sdf.com (misery.sdf.com [204.244.210.193]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA11365 for ; Thu, 21 Aug 1997 11:40:46 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0x1c84-0002is-00; Thu, 21 Aug 1997 11:38:44 -0700 Date: Thu, 21 Aug 1997 11:38:43 -0700 (PDT) From: Tom Samplonius To: Anthony.Kimball@East.Sun.COM cc: conrads@neosoft.com, freebsd-hardware@freebsd.org Subject: Re: What computer to buy ? In-Reply-To: <199708211747.MAA06419@compound.east.sun.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 Thu, 21 Aug 1997, Tony Kimball wrote: > Quoth Conrad Sabatier on Thu, 21 August: > : > : On 21-Aug-97 Tony Kimball wrote: > : > > : >Pentium II is just about the opposite of futureproof -- it is planned > : >obsolescence: Slot 1 has a very short lifetime plan. > : > : Could you possibly elaborate on this a bit? A friend of mine is > : considering purchasing a Pentium II (266 MHz) system, and I'd like to know > : if I should warn him off of it. > > It's just that the P2 form factor is unique to the P2. As I > understand it, there will be Slot 2 modules within a year. > I don't know that any other manufacturer will be producing > Slot 1 modules. So, if you get a P2, you have to discard your > motherboard when you upgrade. Since the P2 is selling at such > a large premium, this may not be terribly large proportion of Large premium? Over what? The only equiv processor is the PPro, and PII is cheaper than a PPro with the same sized L2 cache. > the cost, actually. My personal habit is to buy the most > *cost-effective* hardware. Thus I strongly prefer Socket 7 > processors which have a future upgrade path, commodity > motherboards, etc. The PII 266 is faster than anything that will go into a socket 7. Socket 7 is dead. It days were numbered when socket 8 came out. Tom From owner-freebsd-hardware Thu Aug 21 11:46:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA11772 for hardware-outgoing; Thu, 21 Aug 1997 11:46:16 -0700 (PDT) Received: from relay.hq.tis.com (firewall-user@relay.hq.tis.com [192.94.214.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA11765 for ; Thu, 21 Aug 1997 11:46:12 -0700 (PDT) Received: by relay.hq.tis.com; id OAA10685; Thu, 21 Aug 1997 14:48:42 -0400 (EDT) Received: from defenestration.hq.tis.com(10.33.112.240) by relay.hq.tis.com via smap (4.0) id xma010681; Thu, 21 Aug 97 14:48:41 -0400 Received: from localhost (bwelling@localhost) by defenestration.hq.tis.com (8.8.5/8.8.5) with SMTP id OAA09041 for ; Thu, 21 Aug 1997 14:44:26 -0400 X-Authentication-Warning: defenestration.hq.tis.com: bwelling owned process doing -bs Date: Thu, 21 Aug 1997 14:44:25 -0400 (EDT) From: Brian Wellington X-Sender: bwelling@defenestration.hq.tis.com To: freebsd-hardware@freebsd.org Subject: Quantum 3.1G IDE HD - dual boot 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 We recently got a Quantum Fireball 3.1G IDE HD, and are trying to get Win 95 and FreeBSD to dual boot. The drive info is: wd0: QUANTUM FIREBALL TM3200A 3067M 6281856 sectors 6232c/16h/63s 512b/sec Since you can't boot from a partition crossing the 1024 cylinder limit, we made a 400M FAT partition at the beginning, and then a 50M FreeBSD partiton to be used as /. After installing FreeBSD (2.2.2) on the drive, it won't boot FreeBSD from wd0s2. Hitting F2 at the bootloader prompt causes nothing to happen, except the prompt changes to "F?". This drive is replacing a WD 3.1G IDE drive which worked perfectly in the same computer and configuration (until it died). Any ideas? Brian From owner-freebsd-hardware Thu Aug 21 12:46:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA15308 for hardware-outgoing; Thu, 21 Aug 1997 12:46:48 -0700 (PDT) Received: (from jmb@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA15302; Thu, 21 Aug 1997 12:46:43 -0700 (PDT) From: "Jonathan M. Bresler" Message-Id: <199708211946.MAA15302@hub.freebsd.org> Subject: Re: What computer to buy ? To: tom@sdf.com (Tom Samplonius) Date: Thu, 21 Aug 1997 12:46:42 -0700 (PDT) Cc: Anthony.Kimball@East.Sun.COM, steve@visint.co.uk, freebsd-hardware@FreeBSD.ORG In-Reply-To: from "Tom Samplonius" at Aug 21, 97 11:32:20 am X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Tom Samplonius wrote: > > > On Thu, 21 Aug 1997, Tony Kimball wrote: > > > Quoth Stephen Roome on Thu, 21 August: > > : futureproof (ish) without buying an excessively overpriced Pentium II. > > > > Pentium II is just about the opposite of futureproof -- it is planned > > obsolescence: Slot 1 has a very short lifetime plan. > > But all Intel CPUs have planned obsolescence. There is only so much you > can do with CPU development and keep the connector the same. > > Besides a typical CPU costs almost twice as much a the motherboard, so > who cares about whether the connector is going to change? In a year, the > mb isn't going to be worth anything, anyhow. > > BTW, don't get screwed on PII 266 prices. Prices have already dropped, > but some are still selling at old prices. buying things that are just going out of favor can get you good hardware at very good prices. (trailing edge technology?) how about dual pentium pro-166MHz 512kB L2 Gigabyte 686DX, Natome, EIDE 64MB, ATX case $1374 Intel Pentium II 266 512K $697 Intel Pentium II 233 512K $580 Intel Pentium Pro 200 512K $968 Intel Pentium Pro 200 256K $504 Intel Pentium Pro 180 256K $368 Intel Pentium Pro 166 512K $318 Intel Pentium Pro 150 256K $208 prices from www.atipa.com. jmb From owner-freebsd-hardware Thu Aug 21 12:53:47 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA15711 for hardware-outgoing; Thu, 21 Aug 1997 12:53:47 -0700 (PDT) Received: from relay.hq.tis.com (firewall-user@relay.hq.tis.com [192.94.214.100]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id MAA15703 for ; Thu, 21 Aug 1997 12:53:43 -0700 (PDT) Received: by relay.hq.tis.com; id PAA13224; Thu, 21 Aug 1997 15:56:13 -0400 (EDT) Received: from defenestration.hq.tis.com(10.33.112.240) by relay.hq.tis.com via smap (4.0) id xma013217; Thu, 21 Aug 97 15:56:01 -0400 Received: from localhost (bwelling@localhost) by defenestration.hq.tis.com (8.8.5/8.8.5) with SMTP id PAA09130; Thu, 21 Aug 1997 15:51:45 -0400 X-Authentication-Warning: defenestration.hq.tis.com: bwelling owned process doing -bs Date: Thu, 21 Aug 1997 15:51:44 -0400 (EDT) From: Brian Wellington X-Sender: bwelling@defenestration.hq.tis.com To: Chuck Robey cc: freebsd-hardware@freebsd.org Subject: Re: Quantum 3.1G IDE HD - dual boot 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 Thu, 21 Aug 1997, Chuck Robey wrote: > On Thu, 21 Aug 1997, Brian Wellington wrote: > > > We recently got a Quantum Fireball 3.1G IDE HD, and are trying to get Win > > 95 and FreeBSD to dual boot. The drive info is: > > > > wd0: QUANTUM FIREBALL TM3200A 3067M 6281856 sectors 6232c/16h/63s 512b/sec > > > > Since you can't boot from a partition crossing the 1024 cylinder limit, we > > made a 400M FAT partition at the beginning, and then a 50M FreeBSD > > partiton to be used as /. After installing FreeBSD (2.2.2) on the drive, > > it won't boot FreeBSD from wd0s2. Hitting F2 at the bootloader prompt > > causes nothing to happen, except the prompt changes to "F?". This drive > > is replacing a WD 3.1G IDE drive which worked perfectly in the same > > computer and configuration (until it died). > > Are you certain of the actual cylinder mapping being used on the drive? > I mean, did you use pfdisk.exe to get the info? Those numbers came from the FreeBSD boot message, and matched the numbers on the sticker on the disk, and the BIOS autodetection, so I assume they're right. I just looked at pfdisk.exe and didn't see a way to print the geometry. Brian From owner-freebsd-hardware Thu Aug 21 13:07:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA16609 for hardware-outgoing; Thu, 21 Aug 1997 13:07:55 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id NAA16594 for ; Thu, 21 Aug 1997 13:07:42 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id PAA06014; Thu, 21 Aug 1997 15:41:22 -0400 Date: Thu, 21 Aug 1997 15:41:21 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Brian Wellington cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Quantum 3.1G IDE HD - dual boot 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 Thu, 21 Aug 1997, Brian Wellington wrote: > We recently got a Quantum Fireball 3.1G IDE HD, and are trying to get Win > 95 and FreeBSD to dual boot. The drive info is: > > wd0: QUANTUM FIREBALL TM3200A 3067M 6281856 sectors 6232c/16h/63s 512b/sec > > Since you can't boot from a partition crossing the 1024 cylinder limit, we > made a 400M FAT partition at the beginning, and then a 50M FreeBSD > partiton to be used as /. After installing FreeBSD (2.2.2) on the drive, > it won't boot FreeBSD from wd0s2. Hitting F2 at the bootloader prompt > causes nothing to happen, except the prompt changes to "F?". This drive > is replacing a WD 3.1G IDE drive which worked perfectly in the same > computer and configuration (until it died). Are you certain of the actual cylinder mapping being used on the drive? I mean, did you use pfdisk.exe to get the info? > > Any ideas? > > Brian > > > ----------------------------+----------------------------------------------- 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 Thu Aug 21 17:12:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA02624 for hardware-outgoing; Thu, 21 Aug 1997 17:12:53 -0700 (PDT) Received: from earth.mat.net (root@earth.mat.net [206.246.122.2]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA02614 for ; Thu, 21 Aug 1997 17:12:33 -0700 (PDT) Received: from Journey2.mat.net (journey2.mat.net [206.246.122.116]) by earth.mat.net (8.6.12/8.6.12) with SMTP id UAA20122; Thu, 21 Aug 1997 20:12:18 -0400 Date: Thu, 21 Aug 1997 20:12:17 -0400 (EDT) From: Chuck Robey X-Sender: chuckr@Journey2.mat.net To: Brian Wellington cc: freebsd-hardware@freebsd.org Subject: Re: Quantum 3.1G IDE HD - dual boot 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 Thu, 21 Aug 1997, Brian Wellington wrote: > On Thu, 21 Aug 1997, Chuck Robey wrote: > > > On Thu, 21 Aug 1997, Brian Wellington wrote: > > > > > We recently got a Quantum Fireball 3.1G IDE HD, and are trying to get Win > > > 95 and FreeBSD to dual boot. The drive info is: > > > > > > wd0: QUANTUM FIREBALL TM3200A 3067M 6281856 sectors 6232c/16h/63s 512b/sec > > > > > > Since you can't boot from a partition crossing the 1024 cylinder limit, we > > > made a 400M FAT partition at the beginning, and then a 50M FreeBSD > > > partiton to be used as /. After installing FreeBSD (2.2.2) on the drive, > > > it won't boot FreeBSD from wd0s2. Hitting F2 at the bootloader prompt > > > causes nothing to happen, except the prompt changes to "F?". This drive > > > is replacing a WD 3.1G IDE drive which worked perfectly in the same > > > computer and configuration (until it died). > > > > Are you certain of the actual cylinder mapping being used on the drive? > > I mean, did you use pfdisk.exe to get the info? > > Those numbers came from the FreeBSD boot message, and matched the numbers > on the sticker on the disk, and the BIOS autodetection, so I assume > they're right. I just looked at pfdisk.exe and didn't see a way to print > the geometry. The "L" option lists the whole partition table, and the geometry also. > > Brian > > > ----------------------------+----------------------------------------------- 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 Thu Aug 21 19:40:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id TAA09683 for hardware-outgoing; Thu, 21 Aug 1997 19:40:37 -0700 (PDT) Received: from fly.HiWAAY.net (fly.HiWAAY.net [208.147.154.56]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id TAA09677 for ; Thu, 21 Aug 1997 19:40:23 -0700 (PDT) Received: from nospam.hiwaay.net (tnt1-147.HiWAAY.net [208.147.147.147]) by fly.HiWAAY.net (8.8.6/8.8.6) with ESMTP id VAA14875 for ; Thu, 21 Aug 1997 21:38:55 -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 VAA07533 for ; Thu, 21 Aug 1997 21:38:53 -0500 (CDT) Message-Id: <199708220238.VAA07533@nospam.hiwaay.net> X-Mailer: exmh version 2.0zeta 7/24/97 To: freebsd-hardware@FreeBSD.ORG From: dkelly@hiwaay.net Subject: Re: Quiet SCSI disk? In-reply-to: Message from "Daniel M. Eischen" of "Thu, 21 Aug 1997 04:33:08 CDT." <199708210933.EAA13128@iworks.InterWorks.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 21 Aug 1997 21:38:52 -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > [about the 4GB DCAS 34330W] > > > > >Do you know how many tags it uses (tagged command queuing) ? > > >It was a bit disappointing for me, that the IBM DORS 32160 2.1GB > > >only offers 3 and the the famous QUEUE_FULL condistion ... Wait! How to I querry the drive, kernel, SCSI card, etc, to know how many tags are being used? Is this a value which changes dynamically as the system is running? Others have mentioned the Symbios cards and Adaptec cards. How does this relate? Is one clearly superior to the other in this respect? The clues I've gleaned from these lists in the past suggest the Symbios cards are as good as Adaptecs best, but not as agressively supported in FreeBSD as the Adaptec 2940 family. Notably the Symbios cards currently lack support for Ultra SCSI timing. The Adaptec 3940 has an advantage in large systems such as ftp.cdrom.com by providing dual SCSI buses on one PCI card. Next week I was planning on ordering 7 or 8 Symbios '875 cards for 5 systems I need to set up. Still plan on ordering them as I wasn't terribly pleased when my last 2940AU only had 3 SCB's. -- 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 Aug 21 21:18:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id VAA13332 for hardware-outgoing; Thu, 21 Aug 1997 21:18:50 -0700 (PDT) Received: from pluto.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id VAA13323 for ; Thu, 21 Aug 1997 21:18:45 -0700 (PDT) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by pluto.plutotech.com (8.8.5/8.8.5) with ESMTP id WAA05068; Thu, 21 Aug 1997 22:18:37 -0600 (MDT) Message-Id: <199708220418.WAA05068@pluto.plutotech.com> To: dkelly@hiwaay.net cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Quiet SCSI disk? In-reply-to: Your message of "Thu, 21 Aug 1997 21:38:52 CDT." <199708220238.VAA07533@nospam.hiwaay.net> Date: Thu, 21 Aug 1997 22:17:41 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >> > [about the 4GB DCAS 34330W] >> > >> > >Do you know how many tags it uses (tagged command queuing) ? > >Wait! How to I querry the drive, kernel, SCSI card, etc, to know how >many tags are being used? Is this a value which changes dynamically >as the system is running? Good question. There is no way to querry a device to determine how many transactions it supports. You basically have to bombard it with commands until it says, "I give up! I give up! QUEUE FULL! QUEUE FULL!". You can think of this as the SCSI equivalent of crying 'Uncle!' Currently in FreeBSD, the number of tags in use will fluctuate based on load up to some set maximum. On the Adaptec aic7xxx cards, this maximum is usually 8. On the NCR cards, the maximum is 4, but you can raise this number via the ncrcontrol utility while the system is running. In the future, the SCSI system will dynamically set the maximum on a per device basis based on the capabilities of the controller, the number of transactions active when a device returns QUEUE FULL status, and any 'quirk table entries' that apply to the device. To use my own system, which is running experimental CAM SCSI code that has these features, as an example: ahc0: rev 0x01 int a irq 15 on pci0.10.0 ahc0: aic7860 Single Channel, SCSI Id=7, 3/255I SCBs ahc1: rev 0x00 int a irq 12 on pci0.12.0 ahc1: aic7880 Wide Channel, SCSI Id=7, 16/255 SCBs Both adapters can support up to 255 transactions (adapter 0 using Indirect paging, hence the 'I' in it's SCB count). Now the devices: da0 at ahc0 bus 0 target 0 lun 0 da0: Fixed Direct Access SCSI2 device da0: Serial Number PCB=2011303001 ; HDA=184631651330 da0: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da0: 4341MB (8890760 512 byte sectors: 255H 63S/T 553C) da1 at ahc0 bus 0 target 1 lun 0 da1: Fixed Direct Access SCSI2 device da1: Serial Number PCB=2011303101 ; HDA=189704332253 da1: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da1: 8682MB (17781520 512 byte sectors: 255H 63S/T 1106C) da3 at ahc1 bus 0 target 1 lun 0 da3: Fixed Direct Access SCSI2 device da3: Serial Number 0TC6BH da3: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da3: 2049MB (4197405 512 byte sectors: 255H 63S/T 261C) da5 at ahc1 bus 0 target 3 lun 0 da5: Fixed Direct Access SCSI2 device da5: Serial Number 0T1G79 da5: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da5: 2049MB (4197405 512 byte sectors: 255H 63S/T 261C) da4 at ahc1 bus 0 target 2 lun 0 da4: Fixed Direct Access SCSI2 device da4: Serial Number 0S1Q7K da4: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da4: 2049MB (4197405 512 byte sectors: 255H 63S/T 261C) da2 at ahc1 bus 0 target 0 lun 0 da2: Fixed Direct Access SCSI2 device da2: Serial Number 0S9NBW da2: 20.0MB/s transfers (20.0MHz, offset 15), Tagged Queueing Enabled da2: 2049MB (4197405 512 byte sectors: 255H 63S/T 261C) The drives are attached in parallel and while the order of unit number assignments is preserved, they are listed in the order that the probes complete which is not necessarily the same order as the unit numbers. It's a small price to pay for a much faster boot. The geometry is not the geometry from mode page 5, but the translated geometry that the controller exports. This means that utilities like fdisk will have the appropriate geometry to use even on uninitialized disks. But I digress... Here are the quirk entries that determine tag policy: static struct xpt_quirk_entry xpt_quirk_table[] = { { /* Reports QUEUE FULL for temporary resource shortages */ { T_DIRECT, SIP_MEDIA_FIXED, quantum, "XP39100S", "LX??" }, /*quirks*/0, /*mintags*/24, /*maxtags*/32 }, { /* Reports QUEUE FULL for temporary resource shortages */ { T_DIRECT, SIP_MEDIA_FIXED, quantum, "XP34550S", "LX??" }, /*quirks*/0, /*mintags*/24, /*maxtags*/32 }, { /* Broken tagged queueing drive */ { T_DIRECT, SIP_MEDIA_FIXED, "HP", "C372*", "*" }, /*quirks*/0, /*mintags*/0, /*maxtags*/0 }, { /* Default tagged queuing parameters for all devices */ { T_ANY, SIP_MEDIA_REMOVABLE|SIP_MEDIA_FIXED, /*vendor*/"*", /*product*/"*", /*revision*/"*" }, /*quirks*/0, /*mintags*/2, /*maxtags*/64 }, }; And here are the interresting console messages: Aug 16 03:30:16 dm /kernel: (da3:ahc1:0:1:0): tagged openings reduced to 63 Aug 20 16:14:00 dm /kernel: (da0:ahc0:0:0:0): tagged openings reduced to 31 Aug 20 16:14:00 dm /kernel: (da0:ahc0:0:0:0): tagged openings reduced to 29 The Seagate drives match the default quirk entry and so start out with 64 tags. The system generated 64 transactions at one point in time to one of these drives, got a QUEUE FULL status, and so lowered the number of tags to 63. On the Atlas II, the drive will report QUEUE FULL for temporary resource shortages, so we 'peg' the number of tags to a number that gives decent performance (24). Although this machine has seen two QUEUE FULL messages from the Atlas II drive, it hasn't reduced the tag number to the lower limit yet. I believe that the IBM drive that was mentioned earlier behaves similarly to the Atlas II, so it may be beneficial to add a quirk entry for it too. The goal of this system is to make it so you don't have to worry too much about the number of tags that are in use. Once the base system is complete, however, additional facilities will be added so that you can obtain performance statistics on all devices including the number of transactions/sec and the maximum/average number of transactions active. >Others have mentioned the Symbios cards and Adaptec cards. How does >this relate? Is one clearly superior to the other in this respect? Performance wise, I believe that they are very similar. Cost wise, the Symbios cards are a clear winner. Support wise, all I can say is that the new CAM code will have aic7xxx support before Symbios support (actually, it has aic7xxx support now), but that both will be equally well supported by the time that the new SCSI code enters the tree (late this year). >The Adaptec 3940 has >an advantage in large systems such as ftp.cdrom.com by providing dual >SCSI buses on one PCI card. I've heard that there is a new Symbios controller that supports two busses without the added overhead of a PCI->PCI bridge. I don't know if Stefan has added support for it yet. I do know that the driver in current does support Ultra speeds though. >-- >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. > > > -- Justin T. Gibbs =========================================== FreeBSD: Turning PCs into workstations =========================================== From owner-freebsd-hardware Fri Aug 22 14:53:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA04513 for hardware-outgoing; Fri, 22 Aug 1997 14:53:30 -0700 (PDT) Received: from hda.hda.com (hda-bicnet.bicnet.net [208.220.66.37]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA04508 for ; Fri, 22 Aug 1997 14:53:24 -0700 (PDT) Received: (from dufault@localhost) by hda.hda.com (8.8.5/8.8.5) id RAA18095 for hardware@freebsd.org; Fri, 22 Aug 1997 17:06:54 -0400 (EDT) From: Peter Dufault Message-Id: <199708222106.RAA18095@hda.hda.com> Subject: Fast a-d card To: hardware@freebsd.org Date: Fri, 22 Aug 1997 17:06:53 -0400 (EDT) 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 Can anyone suggest a fast (40Mhz) 8 bit PCI A-D card with flexible DMA hardware or on board smarts from a company that provides technical info and believes in life outside of Windows? This could be anything from a good fast flexible board to a oscilloscope board to a combo DSP/A-D card. A single channel, the ability to level trigger, and chaining of DMA buffers with configurable done interrupt are the minimum requirement. PCI only - no ISA is available. Peter -- Peter Dufault (dufault@hda.com) Realtime development, Machine control, HD Associates, Inc. Safety critical systems, Agency approval From owner-freebsd-hardware Fri Aug 22 16:20:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA09616 for hardware-outgoing; Fri, 22 Aug 1997 16:20:12 -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 QAA09600 for ; Fri, 22 Aug 1997 16:20:04 -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 BAA31691 for ; Sat, 23 Aug 1997 01:03:41 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id BAA03083 for freebsd-hardware@FreeBSD.ORG; Sat, 23 Aug 1997 01:03:25 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.6/keltia-uucp-2.9) id AAA00411; Sat, 23 Aug 1997 00:44:13 +0200 (CEST) Message-ID: <19970823004413.13900@keltia.freenix.fr> Date: Sat, 23 Aug 1997 00:44:13 +0200 From: Ollivier Robert To: freebsd-hardware@FreeBSD.ORG Subject: Re: K6 References: <199707302033.NAA13858@soda.CSUA.Berkeley.EDU> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <199707302033.NAA13858@soda.CSUA.Berkeley.EDU>; from John Milford on Wed, Jul 30, 1997 at 01:33:24PM -0700 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3481 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to John Milford: > I few weeks ago, I posted that I was having trouble with > my new K6/200 machine. In the end the vendor swapped a Pentium/200 > for it and all was happy. But I really wanted a K6 so I did some I've been running FreeBSD CURRENT for three months with a K6-166 running at 2.5x 83 MHz at 3.2V on an ASUS P/I P55T2P4 rev. 3.1. It rocks. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #23: Sun Jul 20 18:10:34 CEST 1997 From owner-freebsd-hardware Fri Aug 22 16:20:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA09625 for hardware-outgoing; Fri, 22 Aug 1997 16:20:15 -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 QAA09603 for ; Fri, 22 Aug 1997 16:20:07 -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 BAA31694 for ; Sat, 23 Aug 1997 01:03:41 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id BAA03084 for hardware@FreeBSD.ORG; Sat, 23 Aug 1997 01:03:26 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.6/keltia-uucp-2.9) id AAA00432; Sat, 23 Aug 1997 00:45:20 +0200 (CEST) Message-ID: <19970823004520.28925@keltia.freenix.fr> Date: Sat, 23 Aug 1997 00:45:20 +0200 From: Ollivier Robert To: "hardware@freebsd.org" Subject: Re: K6-200 Has anyone successfully done a 'make world' ? References: <199708112237.PAA05218@dragon.cmnsens.zoom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <199708112237.PAA05218@dragon.cmnsens.zoom.com>; from Mike Burgett on Mon, Aug 11, 1997 at 03:37:29PM -0700 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3481 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Mike Burgett: > I've tried everything but a new chip here, AMD recommended motherboard and > cooler and all, without getting through a 'make world'. The new chip is on > the way. :) Has *anyone* been able to do a 'make world' successfully with > this chip? I've only a 166 MHz but I've made several "make world" without problems. -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #23: Sun Jul 20 18:10:34 CEST 1997 From owner-freebsd-hardware Fri Aug 22 16:20:20 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA09639 for hardware-outgoing; Fri, 22 Aug 1997 16:20:20 -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 QAA09611 for ; Fri, 22 Aug 1997 16:20:10 -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 BAA31697 for ; Sat, 23 Aug 1997 01:03:41 +0200 Received: (from uucp@localhost) by brasil.brainstorm.eu.org (8.8.6/brasil-1.2) with UUCP id BAA03085 for freebsd-hardware@FreeBSD.ORG; Sat, 23 Aug 1997 01:03:26 +0200 Received: (from roberto@localhost) by keltia.freenix.fr (8.8.6/keltia-uucp-2.9) id AAA00461; Sat, 23 Aug 1997 00:56:43 +0200 (CEST) Message-ID: <19970823005643.32466@keltia.freenix.fr> Date: Sat, 23 Aug 1997 00:56:43 +0200 From: Ollivier Robert To: freebsd-hardware@FreeBSD.ORG Subject: Re: Quiet SCSI disk? References: <199708200348.NAA21476@ogre.dtir.qld.gov.au> <4472.872053261@time.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.76 In-Reply-To: <4472.872053261@time.cdrom.com>; from Jordan K. Hubbard on Tue, Aug 19, 1997 at 10:01:01PM -0700 X-Operating-System: FreeBSD 3.0-CURRENT ctm#3481 AMD-K6 MMX @ 208 MHz Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Jordan K. Hubbard: > I just bought 3 of the 4.3GB DCAS drives (34330W) and they've all been > performing just fine for me. Very quiet, very cool and, so far, > reliable. At the current street price of $410-$450, I'd say they're > also pretty good value. I bought mine (34330W) at Fry's in Palo Alto last friday at $469. I'm very happy with it, even quieter than my DORS 32160 (although not by much). My "home" machine is becoming quite large with the 6 SCSI disks, plus DAT, QIC-6150 and the CD on 2 NCR... (total is 8.2 GB now). -- Ollivier ROBERT -=- FreeBSD: There are no limits -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #23: Sun Jul 20 18:10:34 CEST 1997 From owner-freebsd-hardware Fri Aug 22 16:38:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id QAA10301 for hardware-outgoing; Fri, 22 Aug 1997 16:38:19 -0700 (PDT) Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id QAA10294 for ; Fri, 22 Aug 1997 16:38:17 -0700 (PDT) Received: (jin@localhost) by george.lbl.gov (8.6.10/8.6.5) id QAA14635; Fri, 22 Aug 1997 16:33:40 -0700 Date: Fri, 22 Aug 1997 16:33:40 -0700 From: "Jin Guojun[ITG]" Message-Id: <199708222333.QAA14635@george.lbl.gov> To: hardware@FreeBSD.ORG, roberto@keltia.freenix.fr Subject: Re: K6-200 Has anyone successfully done a 'make world' ? Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >According to Mike Burgett: >> I've tried everything but a new chip here, AMD recommended motherboard and >> cooler and all, without getting through a 'make world'. The new chip is on >> the way. :) Has *anyone* been able to do a 'make world' successfully with >> this chip? > >I've only a 166 MHz but I've made several "make world" without problems. Would you please tell what is the manufactory code on you CPU? Thanks, -Jin From owner-freebsd-hardware Sat Aug 23 08:57:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id IAA23956 for hardware-outgoing; Sat, 23 Aug 1997 08:57:48 -0700 (PDT) Received: from cwsys.cwent.com (66@cschuber.net.gov.bc.ca [142.31.240.113]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id IAA23917 for ; Sat, 23 Aug 1997 08:57:35 -0700 (PDT) Received: (from uucp@localhost) by cwsys.cwent.com (8.8.7/8.6.10) id IAA08451; Sat, 23 Aug 1997 08:57:29 -0700 (PDT) Message-Id: <199708231557.IAA08451@cwsys.cwent.com> Received: from localhost.cwent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwent.com, id smtpd008432; Sat Aug 23 15:57:01 1997 Reply-to: cy@uumail.gov.bc.ca X-Mailer: MH X-Sender: cschuber To: freebsd-hardware@freebsd.org cc: cschuber@uumail.gov.bc.ca Subject: 3C509B Card Date: Sat, 23 Aug 1997 08:56:59 -0700 From: Cy Schubert Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Recently I replaced a faulty SMC Elite 16 card with a 3COM 3C509B card. It's been working fine, almost too fine. Since installing the card I haven't seen any collisions. My network consists of a P120 with the 3C509B and a 486DX/33 with an SMC Elite 16 connected via thinnet up through the attic of my house. Is it possible that the Parallel Tasking feature of the card is handling collisions itself without reporting them to FreeBSD? Or, is there a bug in the FreeBSD driver that it's not recognizing or reporting collisions. As I write this the netstat -i on the P120 (3C509B) reports: cwsys$ netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll lp0* 1500 0 0 0 0 0 ep0 1500 00.60.97.d3.32.3e 452413 411 444431 1 0 ep0 1500 cw-subnet/24 cwsys 452413 411 444431 1 0 sl0* 552 0 0 0 0 0 ppp0 1500 2969 1 3176 0 0 ppp0 1500 bcsc-net2 cschuber.net.go 2969 1 3176 0 0 lo0 16384 30126 0 30126 0 0 lo0 16384 localnet localhost 30126 0 30126 0 0 cwsys$ And the netstat -i on the 486 (SMC Elite 16) reports: cwsys$ rsh cwtest netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ed0 1500 00.00.c0.d9.b1.4a 444764 0 453362 0 12447 ed0 1500 cwnet.cwent.c cwtest 444764 0 453362 0 12447 lp0* 1500 0 0 0 0 0 lo0 16384 7933 0 7933 0 0 lo0 16384 your-net localhost 7933 0 7933 0 0 cwsys$ The card is working fine. It's just puzzling that I see these kind of numbers from netstat. When I had an SMC card installed in the P120 it too reported collisions. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 UNIX Support OV/VM: BCSC02(CSCHUBER) ITSD BITNET: CSCHUBER@BCSC02.BITNET Government of BC Internet: cschuber@uumail.gov.bc.ca cschuber@bcsc02.gov.bc.ca cy@uumail.gov.bc.ca "Quit spooling around, JES do it." From owner-freebsd-hardware Sat Aug 23 09:16:43 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA26518 for hardware-outgoing; Sat, 23 Aug 1997 09:16:43 -0700 (PDT) Received: from tok.qiv.com ([204.214.141.211]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA26482 for ; Sat, 23 Aug 1997 09:16:26 -0700 (PDT) Received: (from uucp@localhost) by tok.qiv.com (8.8.6/8.8.5) with UUCP id LAA11331 for freebsd-hardware@freebsd.org; Sat, 23 Aug 1997 11:16:11 -0500 (CDT) Received: from localhost (jdn@localhost) by acp.qiv.com (8.8.6/8.8.5) with SMTP id LAA03827 for ; Sat, 23 Aug 1997 11:15:26 -0500 (CDT) X-Authentication-Warning: acp.qiv.com: jdn owned process doing -bs Date: Sat, 23 Aug 1997 11:15:26 -0500 (CDT) From: "Jay D. Nelson" To: freebsd-hardware@freebsd.org Subject: About k5-166 on ASUS P55T2P4 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 bought the above board and would like to put a 166Mhz K5 on it. ASUS shows a bios upgrade from ~May this year that adds support (?) for this chip. Which leads to the following: 1. Why would this chip be any different than the 133 or lower. 2. If I install the chip, would I run into any trouble setting the board for 66Mhz/2.5x -- or should I set it up at lower speeds until I install the new bios? 3. The chip is marked as 3.52V and the MB jumper sets 3.4V-3.6V. Is this part of any problem? Any advice or experience is welcome. Also -- unrelated to above, this will be a SCSI system (ASUS S200). ATAPI CDROMS, though are cheap. Does anyone know of problems running a CDROM as the only device on the primary IDE bus? Thanks -- Jay From owner-freebsd-hardware Sat Aug 23 09:22:09 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA27041 for hardware-outgoing; Sat, 23 Aug 1997 09:22:09 -0700 (PDT) Received: from cwsys.cwent.com (66@cschuber.net.gov.bc.ca [142.31.240.113]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA27034 for ; Sat, 23 Aug 1997 09:22:04 -0700 (PDT) Received: (from uucp@localhost) by cwsys.cwent.com (8.8.7/8.6.10) id JAA08525; Sat, 23 Aug 1997 09:22:00 -0700 (PDT) Message-Id: <199708231622.JAA08525@cwsys.cwent.com> Received: from localhost.cwent.com(127.0.0.1), claiming to be "cwsys" via SMTP by localhost.cwent.com, id smtpd008522; Sat Aug 23 16:21:46 1997 Reply-to: cschuber@uumail.gov.bc.ca X-Mailer: MH X-Sender: cschuber To: freebsd-hardware@freebsd.org cc: cschuber@uumail.gov.bc.ca Subject: 3C509B Card Date: Sat, 23 Aug 1997 09:21:45 -0700 From: Cy Schubert Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I think I got my answer from the 3Com website. Question: Can the EtherLink III family of adapters operate in promiscuous mode? Answer: All EtherLink III family adapters are certified for promiscuous mode. However, the parallel task feature of these adapters does not support the promiscuous mode since it drops the bad packets before it gets to the CPU. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 UNIX Support OV/VM: BCSC02(CSCHUBER) ITSD BITNET: CSCHUBER@BCSC02.BITNET Government of BC Internet: cschuber@uumail.gov.bc.ca cschuber@bcsc02.gov.bc.ca "Quit spooling around, JES do it." ------- Forwarded Message Reply-to: cy@uumail.gov.bc.ca X-Mailer: MH X-Sender: cschuber To: freebsd-hardware@freebsd.org cc: cschuber@uumail.gov.bc.ca Subject: 3C509B Card Date: Sat, 23 Aug 1997 08:56:59 -0700 From: Cy Schubert Recently I replaced a faulty SMC Elite 16 card with a 3COM 3C509B card. It's been working fine, almost too fine. Since installing the card I haven't seen any collisions. My network consists of a P120 with the 3C509B and a 486DX/33 with an SMC Elite 16 connected via thinnet up through the attic of my house. Is it possible that the Parallel Tasking feature of the card is handling collisions itself without reporting them to FreeBSD? Or, is there a bug in the FreeBSD driver that it's not recognizing or reporting collisions. As I write this the netstat -i on the P120 (3C509B) reports: cwsys$ netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll lp0* 1500 0 0 0 0 0 ep0 1500 00.60.97.d3.32.3e 452413 411 444431 1 0 ep0 1500 cw-subnet/24 cwsys 452413 411 444431 1 0 sl0* 552 0 0 0 0 0 ppp0 1500 2969 1 3176 0 0 ppp0 1500 bcsc-net2 cschuber.net.go 2969 1 3176 0 0 lo0 16384 30126 0 30126 0 0 lo0 16384 localnet localhost 30126 0 30126 0 0 cwsys$ And the netstat -i on the 486 (SMC Elite 16) reports: cwsys$ rsh cwtest netstat -i Name Mtu Network Address Ipkts Ierrs Opkts Oerrs Coll ed0 1500 00.00.c0.d9.b1.4a 444764 0 453362 0 12447 ed0 1500 cwnet.cwent.c cwtest 444764 0 453362 0 12447 lp0* 1500 0 0 0 0 0 lo0 16384 7933 0 7933 0 0 lo0 16384 your-net localhost 7933 0 7933 0 0 cwsys$ The card is working fine. It's just puzzling that I see these kind of numbers from netstat. When I had an SMC card installed in the P120 it too reported collisions. Regards, Phone: (250)387-8437 Cy Schubert Fax: (250)387-5766 UNIX Support OV/VM: BCSC02(CSCHUBER) ITSD BITNET: CSCHUBER@BCSC02.BITNET Government of BC Internet: cschuber@uumail.gov.bc.ca cschuber@bcsc02.gov.bc.ca cy@uumail.gov.bc.ca "Quit spooling around, JES do it." ------- End of Forwarded Message From owner-freebsd-hardware Sat Aug 23 12:51:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA11302 for hardware-outgoing; Sat, 23 Aug 1997 12:51:25 -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 MAA11288 for ; Sat, 23 Aug 1997 12:51:22 -0700 (PDT) Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1) id 0x2MBR-0004oG-00; Sat, 23 Aug 1997 12:49:17 -0700 Date: Sat, 23 Aug 1997 12:49:16 -0700 (PDT) From: Tom Samplonius To: cschuber@uumail.gov.bc.ca cc: freebsd-hardware@freebsd.org Subject: Re: 3C509B Card In-Reply-To: <199708231622.JAA08525@cwsys.cwent.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 Sat, 23 Aug 1997, Cy Schubert wrote: > I think I got my answer from the 3Com website. > > Question: Can the EtherLink III family of adapters operate in promiscuous > mode? > > Answer: All EtherLink III family adapters are certified for promiscuous > mode. However, the parallel task feature of these adapters does not support > the promiscuous mode since it drops the bad packets before it gets to the > CPU. Not really. Most cards (all?) handle retransmits internally these days. However, I don't belive the Etherlink driver is reading the count off the card. Some of the other drivers use to report 0 for collisions as well, until the driver was educated on where to read the collision count from. > Regards, Phone: (250)387-8437 > Cy Schubert Fax: (250)387-5766 > UNIX Support OV/VM: BCSC02(CSCHUBER) > ITSD BITNET: CSCHUBER@BCSC02.BITNET > Government of BC Internet: cschuber@uumail.gov.bc.ca > cschuber@bcsc02.gov.bc.ca > > "Quit spooling around, JES do it." Tom From owner-freebsd-hardware Sat Aug 23 15:56:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id PAA19035 for hardware-outgoing; Sat, 23 Aug 1997 15:56:10 -0700 (PDT) Received: from mail.nacamar.de (mail.nacamar.de [194.162.162.200]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id PAA19030 for ; Sat, 23 Aug 1997 15:56:06 -0700 (PDT) Received: from [195.52.251.6] (apfel.nacamar.de [195.52.251.6]) by mail.nacamar.de (8.8.7/8.8.6) with ESMTP id AAA21630 for ; Sun, 24 Aug 1997 00:55:55 +0200 (CEST) X-Sender: petzi@mail.nacamar.de Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Sun, 24 Aug 1997 00:56:01 +0200 To: hardware@freebsd.org From: Michael Beckmann Subject: de0: abnormal interrupt: receive process stopped Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk de0: abnormal interrupt: receive process stopped I have this message on one server in dmesg since a few days. Has anyone else seen this before ? I've exchanged the Ethernet card (SMC Etherpower 10) with a new one already, it didn't help. This never occurred before with the same card. Is something going wrong with the mainboard ? I'm running 2.2-RELENG. Michael From owner-freebsd-hardware Sat Aug 23 19:23:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA29595 for hardware-outgoing; Sat, 23 Aug 1997 19:23:05 -0700 (PDT) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA29590 for ; Sat, 23 Aug 1997 19:22:58 -0700 (PDT) Received: from word.smith.net.au (localhost.smith.net.au [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id LAA00737; Sun, 24 Aug 1997 11:51:43 +0930 (CST) Message-Id: <199708240221.LAA00737@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: Peter Dufault cc: hardware@freebsd.org Subject: Re: Fast a-d card In-reply-to: Your message of "Fri, 22 Aug 1997 17:06:53 -0400." <199708222106.RAA18095@hda.hda.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 24 Aug 1997 11:51:40 +0930 From: Mike Smith Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Can anyone suggest a fast (40Mhz) 8 bit PCI A-D card with flexible > DMA hardware or on board smarts from a company that provides > technical info and believes in life outside of Windows? This could > be anything from a good fast flexible board to a oscilloscope board > to a combo DSP/A-D card. Datel have a very nice board that I got _that_ close to getting to use recently. The card itself provides the PCI interface & triggering, and there are a pile of plugin modules to choose from. We were looking at the 16-channel 250KHz plugin, but I'm fairly sure there was a single-channel module at the 40MHz mark. The card we were looking at was comfortably under the AUD$6000 mark; I don't think the plugins vary a great deal in price. > A single channel, the ability to level trigger, and chaining of > DMA buffers with configurable done interrupt are the minimum > requirement. The PCI interface on these cards is provided by the AMCC 9533 PCI Matchmaker; it has _most_ of what you want, but no DMA buffer chaining. The card does have fairly deep FIFOs though, so you could probably do your buffer chaining manually without too much stress. AMCC were more than happy to send me a copy of the databook for the 9533, and Datel were likewise open about programming their card; for about AUD$700 more we could have had the source to their DOS-based diagnostic/ test/harddisk-recorder program if we felt we needed examples. You could try National Instruments, but getting data on their MITE PCI interface ASIC is like kicking dead whales down the beach with a jelly toothbrush nailed to a tree 8) > PCI only - no ISA is available. At 40MHz? No shit 8) mike