From owner-freebsd-hardware Sun Jun 22 04:22:06 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA27501 for hardware-outgoing; Sun, 22 Jun 1997 04:22:06 -0700 (PDT) Received: from ns1.netcologne.de (ns1.netcologne.de [194.8.194.70]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA27395; Sun, 22 Jun 1997 04:21:47 -0700 (PDT) Received: from theseus.mediaconsult.de by ns1.netcologne.de (8.6.12/NetCologne/marvin/netsafe-a0020) id ; Sun, 22 Jun 1997 12:58:25 +0200 with ESMTP X-Ncc-Regid: de.netcologne Message-ID: <33AD0A8E.ED1452A0@netcologne.de> Date: Sun, 22 Jun 1997 13:20:46 +0200 From: Richard Cochius Reply-To: richard.cochius@netcologne.de Organization: Media Connect Cologne X-Mailer: Mozilla 4.0b5 [en] (Win95; I) MIME-Version: 1.0 To: FREEBSD-ADMIN@freebsd.org, FREEBSD-ANNOUNCE@freebsd.org, FREEBSD-ARCH@freebsd.org, FREEBSD-BUGS@freebsd.org, FREEBSD-CORE@freebsd.org, FREEBSD-CURRENT@freebsd.org, FREEBSD-CURRENT-DIGEST@freebsd.org, FREEBSD-STABLE@freebsd.org, FREEBSD-DOC@freebsd.org, FREEBSD-FS@freebsd.org, FREEBSD-HACKERS@freebsd.org, FREEBSD-HACKERS-DIGEST@freebsd.org, FREEBSD-HARDWARE@freebsd.org, FREEBSD-INSTALL@freebsd.org, FREEBSD-ISP@freebsd.org, FREEBSD-MULTIMEDIA@freebsd.org, FREEBSD-PLATFORMS@freebsd.org, FREEBSD-PORTS@freebsd.org, FREEBSD-QUESTIONS@freebsd.org, FREEBSD-QUESTIONS-DIGEST@freebsd.org, FREEBSD-SCSI@freebsd.org, FREEBSD-SECURITY@freebsd.org, FREEBSD-SECURITY-NOTIFICATIONS@freebsd.org, FREEBSD-USER-GROUPS@freebsd.org Subject: subscribe X-Priority: 3 (Normal) Content-Type: text/plain; charset=iso-8859-1 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk From owner-freebsd-hardware Mon Jun 23 03:55:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id DAA27710 for hardware-outgoing; Mon, 23 Jun 1997 03:55:28 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id DAA27705 for ; Mon, 23 Jun 1997 03:55:25 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr2-44.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA17877 (5.67b/IDA-1.5 for ); Mon, 23 Jun 1997 12:54:46 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id MAA00582; Mon, 23 Jun 1997 12:54:38 +0200 (CEST) X-Face: " Date: Mon, 23 Jun 1997 12:54:37 +0200 From: Stefan Esser To: NetSonic Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: NIC Card Configuration References: <3.0.32.19960621201159.00b8b98c@mail.netsonic.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <3.0.32.19960621201159.00b8b98c@mail.netsonic.com>; from NetSonic on Fri, Jun 21, 1996 at 08:12:01PM -0500 Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jun 21, 1996, NetSonic wrote: > Hello: Hi! Please adjust your date! It's 1997 already, not 1996 anymore ... > I have a generic ethernet card known to work with free bsd.. I have just > reinstalled the Free BSD OS and have found that during bootup there are > conflicts with ed0 with other things and ed1 appears as the nic card. > After that, i get errors that says > > ed1 device time out. Is there somthing I need to do with the IRQ's or > somthing? How can we know, if you don't tell a thing about your system, the kernel you used (GENERIC or customized) and from what release to which other you upgraded. Please enter "-v" at the "Boot: " prompt and send me the boot message log (which should have been saved to /var/run/dmesg.boot). Regards, STefan From owner-freebsd-hardware Mon Jun 23 05:00:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA29992 for hardware-outgoing; Mon, 23 Jun 1997 05:00:12 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA29953; Mon, 23 Jun 1997 05:00:03 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id EAA18496; Mon, 23 Jun 1997 04:59:48 -0700 (PDT) Message-ID: <19970623045948.30766@hydrogen.nike.efn.org> Date: Mon, 23 Jun 1997 04:59:48 -0700 From: John-Mark Gurney To: Stefan Esser Cc: NetSonic , freebsd-hardware@FreeBSD.ORG Subject: Re: NIC Card Configuration References: <3.0.32.19960621201159.00b8b98c@mail.netsonic.com> <19970623125437.57366@mi.uni-koeln.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: <19970623125437.57366@mi.uni-koeln.de>; from Stefan Esser on Mon, Jun 23, 1997 at 12:54:37PM +0200 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Stefan Esser scribbled this message on Jun 23: > On Jun 21, 1996, NetSonic wrote: > > > I have a generic ethernet card known to work with free bsd.. I have just > > reinstalled the Free BSD OS and have found that during bootup there are > > conflicts with ed0 with other things and ed1 appears as the nic card. > > After that, i get errors that says > > > > ed1 device time out. Is there somthing I need to do with the IRQ's or > > somthing? this is probably a miss match of the irq the ed1 expects, and the irq that your card is producing.. make sure they agree... if you still get the error.. make sure that the cable is properly attached, and working well... (i.e. terminated if coax, or the link light on the hub lights up)... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hardware Mon Jun 23 23:42:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id XAA27154 for hardware-outgoing; Mon, 23 Jun 1997 23:42:22 -0700 (PDT) Received: from ghpc8.ihf.rwth-aachen.de (ghpc8.ihf.RWTH-Aachen.DE [134.130.90.8]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA27147 for ; Mon, 23 Jun 1997 23:42:12 -0700 (PDT) Received: from ghpc6.ihf.rwth-aachen.de (ghpc6.ihf.rwth-aachen.de [134.130.90.6]) by ghpc8.ihf.rwth-aachen.de (8.8.5/8.8.5) with ESMTP id IAA20379; Tue, 24 Jun 1997 08:41:51 +0200 (CEST) Received: (from thomas@localhost) by ghpc6.ihf.rwth-aachen.de (8.8.5/8.8.5) id IAA01920; Tue, 24 Jun 1997 08:41:50 +0200 (CEST) To: Bernie Doehner Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: GPIB program? References: From: Thomas Gellekum Date: 24 Jun 1997 08:41:50 +0200 In-Reply-To: Bernie Doehner's message of Mon, 23 Jun 1997 14:03:14 -0400 (EDT) Message-ID: <87oh8w7b9t.fsf@ghpc6.ihf.rwth-aachen.de> Lines: 20 X-Mailer: Gnus v5.4.37/XEmacs 19.15 Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bernie Doehner writes: > Hi: > > I have a national instruments GPIB card and I am trying to use it under > FreeBSD. I noticed the "gp" device, so I know there is at least a driver > that can be compiled into the kernl, but do we have a program in the ports > collection that talks to the driver and records the data? Fred Cawthorne (sp?) has a new version of his driver. I can send it to you if you want. It contains a library for acccessing the device. Your other choice is linux-gpib. Look at http://www.llp.fu-berlin.de/. > P.S. please reply privately to me, I am not on this mailing list.. Thanks. `Group reply' takes care of that. BTW, freebsd-hardware would probably be a better list for a question like this. tg From owner-freebsd-hardware Tue Jun 24 00:35:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA00434 for hardware-outgoing; Tue, 24 Jun 1997 00:35:36 -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 AAA00425 for ; Tue, 24 Jun 1997 00:35:32 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id QAA23342; Tue, 24 Jun 1997 16:58:54 +0930 (CST) From: Michael Smith Message-Id: <199706240728.QAA23342@genesis.atrad.adelaide.edu.au> Subject: Re: GPIB program? In-Reply-To: <87oh8w7b9t.fsf@ghpc6.ihf.rwth-aachen.de> from Thomas Gellekum at "Jun 24, 97 08:41:50 am" To: tg@ihf.rwth-aachen.de (Thomas Gellekum) Date: Tue, 24 Jun 1997 16:58:54 +0930 (CST) Cc: bad@uhf.wireless.net, 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-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thomas Gellekum stands accused of saying: > Bernie Doehner writes: > > > I have a national instruments GPIB card and I am trying to use it under > > FreeBSD. I noticed the "gp" device, so I know there is at least a driver > > that can be compiled into the kernl, but do we have a program in the ports > > collection that talks to the driver and records the data? > > Fred Cawthorne (sp?) has a new version of his driver. I can send it to > you if you want. It contains a library for acccessing the device. Just FWIW, NI have a a developer's kit for the PCI version of this card. We were looking at it, but with their new PCI 32-bit DIO card, I can't see us going that way. Regardless, if you need _fast_ GPIB, the DDK was ~US$500 with an NDA. -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Tue Jun 24 01:41:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id BAA03434 for hardware-outgoing; Tue, 24 Jun 1997 01:41:25 -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 BAA03427 for ; Tue, 24 Jun 1997 01:41:18 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id SAA23999 for hardware@freebsd.org; Tue, 24 Jun 1997 18:11:11 +0930 (CST) From: Michael Smith Message-Id: <199706240841.SAA23999@genesis.atrad.adelaide.edu.au> Subject: DNA reference design details released To: hardware@freebsd.org Date: Tue, 24 Jun 1997 18:11:11 +0930 (CST) X-Mailer: ELM [version 2.4ME+ PL28 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk If you've been waiting as long as I have : http://www.research.digital.com:80/SRC/iag/ -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Tue Jun 24 06:17:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA13920 for hardware-outgoing; Tue, 24 Jun 1997 06:17:26 -0700 (PDT) Received: from uhf.wdc.net (uhf.wdc.net [198.147.74.44]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id GAA13891 for ; Tue, 24 Jun 1997 06:17:13 -0700 (PDT) Received: from localhost (bad@localhost) by uhf.wdc.net (8.8.5/8.6.12) with SMTP id JAA00820; Tue, 24 Jun 1997 09:16:32 -0400 (EDT) Date: Tue, 24 Jun 1997 09:15:33 -0400 (EDT) From: Bernie Doehner To: Michael Smith cc: Thomas Gellekum , freebsd-hardware@FreeBSD.ORG Subject: Re: GPIB program? In-Reply-To: <199706240728.QAA23342@genesis.atrad.adelaide.edu.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > > I have a national instruments GPIB card and I am trying to use it under > > > FreeBSD. I noticed the "gp" device, so I know there is at least a driver > > > that can be compiled into the kernl, but do we have a program in the ports > > > collection that talks to the driver and records the data? > > > > Fred Cawthorne (sp?) has a new version of his driver. I can send it to > > you if you want. It contains a library for acccessing the device. Thanks. Fred already wrote me, but he also figured out that my 1984 vintage card has a different controller, than his driver supports. > Just FWIW, NI have a a developer's kit for the PCI version of this > card. We were looking at it, but with their new PCI 32-bit DIO card, > I can't see us going that way. And I am not dragging my PCI machine to field tests. Unfortunately that means putting DOS on my 386 and using the DOS tools.. Oh well. > Regardless, if you need _fast_ GPIB, the DDK was ~US$500 with an NDA. I suspect we don't. The fastest test requires roughly one screen save/second, but that's only looking into the far far future. Of immediate need is to just do single screen saves on a network analyzer. Thanks. Bernie From owner-freebsd-hardware Tue Jun 24 07:03:28 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA15840 for hardware-outgoing; Tue, 24 Jun 1997 07:03:28 -0700 (PDT) Received: from smug.flevel.co.uk (smug.flevel.co.uk [194.6.101.22]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id HAA15835 for ; Tue, 24 Jun 1997 07:03:21 -0700 (PDT) Received: (from neil@localhost) by smug.flevel.co.uk (8.8.5/8.7.3) id PAA00260 for hardware@freebsd.org; Tue, 24 Jun 1997 15:03:19 +0100 (BST) Message-ID: X-Mailer: XFMail 1.0 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Tue, 24 Jun 1997 14:55:26 +0100 (BST) From: Neil Smith To: hardware@freebsd.org Subject: DMA timed out with Soundblaster Pro soundcard Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi all. I'm using FREEBSD 2.2.2 RELEASE. I'm trying to get a Soundblaster Pro (8bit) soundcard working. When I cat an .au file to /dev/audio, I get bursts of sample (sounding correct), with 1 second (approx) pauses in between. The bursts of sample only last perhaps 0.2 seconds. I get this error message: Sound: DMA timed out - IRQ/DRQ config error? dmesg reports: sb0 at 0x220 irq 7 drq 1 on isa sb0: (the soundcard is at factory default settings) I've tried different irq's, drq's etc. using the user config, but exactly the same thing happens. I've also tried changing the kernel to set -DDSP_BUFFSIZE=16384 (as recommended for the Pro soundcard), but to no avail. Any advice greatly appreciated. Regards, Neil. /-----------------------------------------\ | From: Neil Smith | | | \-----------------------------------------/ From owner-freebsd-hardware Tue Jun 24 07:57:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id HAA18323 for hardware-outgoing; Tue, 24 Jun 1997 07:57:41 -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 HAA18316 for ; Tue, 24 Jun 1997 07:57:36 -0700 (PDT) Received: (from msmith@localhost) by genesis.atrad.adelaide.edu.au (8.8.5/8.7.3) id AAA24945; Wed, 25 Jun 1997 00:26:21 +0930 (CST) From: Michael Smith Message-Id: <199706241456.AAA24945@genesis.atrad.adelaide.edu.au> Subject: Re: GPIB program? In-Reply-To: from Bernie Doehner at "Jun 24, 97 09:15:33 am" To: bad@uhf.wireless.net (Bernie Doehner) Date: Wed, 25 Jun 1997 00:26:21 +0930 (CST) Cc: msmith@atrad.adelaide.edu.au, tg@ihf.rwth-aachen.de, 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-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Bernie Doehner stands accused of saying: > > Thanks. Fred already wrote me, but he also figured out that my 1984 > vintage card has a different controller, than his driver supports. Ah, bingo. _That_ card. I think I recall you mentioning that one before. > And I am not dragging my PCI machine to field tests. Unfortunately that > means putting DOS on my 386 and using the DOS tools.. Oh well. You could always get one of the NI ethernet-to-GPIB units; expensive, but very handy. They just talk TCP/IP. Probably not too good for your situation though 8) -- ]] Mike Smith, Software Engineer msmith@gsoft.com.au [[ ]] Genesis Software genesis@gsoft.com.au [[ ]] High-speed data acquisition and (GSM mobile) 0411-222-496 [[ ]] realtime instrument control. (ph) +61-8-8267-3493 [[ ]] Unix hardware collector. "Where are your PEZ?" The Tick [[ From owner-freebsd-hardware Tue Jun 24 16:18:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA12920 for hardware-outgoing; Tue, 24 Jun 1997 16:18:10 -0700 (PDT) Received: from hydrogen.nike.efn.org (resnet.uoregon.edu [128.223.170.28]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id QAA12904 for ; Tue, 24 Jun 1997 16:18:04 -0700 (PDT) Received: (from jmg@localhost) by hydrogen.nike.efn.org (8.8.5/8.8.5) id QAA06348; Tue, 24 Jun 1997 16:17:42 -0700 (PDT) Message-ID: <19970624161741.24051@hydrogen.nike.efn.org> Date: Tue, 24 Jun 1997 16:17:41 -0700 From: John-Mark Gurney To: Neil Smith Cc: hardware@FreeBSD.ORG Subject: Re: DMA timed out with Soundblaster Pro soundcard References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.69 In-Reply-To: ; from Neil Smith on Tue, Jun 24, 1997 at 02:55:26PM +0100 Reply-To: John-Mark Gurney Organization: Cu Networking X-Operating-System: FreeBSD 2.2.1-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Neil Smith scribbled this message on Jun 24: > > Hi all. > > I'm using FREEBSD 2.2.2 RELEASE. > > I'm trying to get a Soundblaster Pro (8bit) soundcard working. When I cat I have almost the exact same card (rev 3.1 though)... > an .au file to /dev/audio, I get bursts of sample (sounding correct), with > 1 second (approx) pauses in between. The bursts of sample only last > perhaps 0.2 seconds. this sounds like a IRQ problem... as the sound driver isn't getting notified that the buffer is [partially] done playing and needs to load it up again... > I've tried different irq's, drq's etc. using the user config, but exactly > the same thing happens. this alomst might be a problem with conflicts with a lpt port... right now I have my sbpro on irq 10 just to keep it out of the way... just match the kernel with the jumpers on the card... hope you get it working... -- John-Mark Gurney Modem/FAX: +1 541 683 6954 Cu Networking Live in Peace, destroy Micro$oft, support free software, run FreeBSD From owner-freebsd-hardware Wed Jun 25 05:52:11 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA21067 for hardware-outgoing; Wed, 25 Jun 1997 05:52:11 -0700 (PDT) Received: from sunny.wup.de (www.wup.de [149.237.200.2]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id FAA21025; Wed, 25 Jun 1997 05:51:55 -0700 (PDT) Received: (from andreas@localhost) by sunny.wup.de (8.8.6/8.8.6) id OAA06564; Wed, 25 Jun 1997 14:48:07 +0200 (MET DST) Message-ID: <19970625144802.57953@sunny.wup.de> Date: Wed, 25 Jun 1997 14:48:02 +0200 From: Andreas Klemm To: jkh@FreeBSD.ORG Cc: isp@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Advice for a 10/100 MBit PCI card Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 X-phone: Wiechers & Partner +49 2173 3964 161 X-fax: Wiechers & Partner +49 2173 3964 222 Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi ! Need a quick advice, which 10/100 MBit Tisted pair PCI card works best supported and reliable under FreeBSD 2.1 and 2.2. Theres a good chance, that our company will get a FreeBSD communications server soon ... !!! And I urgently need some help, because of the pitfalls I heard about supported and not supported DEC Chips and such .... What PCI cards are in use on freefall and wcarchive ??? Do you think FreeBSD-2.2.2 is ok for a reliable server or should I better choose 2.1.7.1 ??? I think the FreeBSD-2.2.2 machines are well enough and one could use the -current ports, which might be an advantage over the older ports .... Andreas /// -- aklemm@wup.de /\/\___ Wiechers & Partner Datentechnik GmbH Andreas Klemm ___/\/\/ - Support Unix - From owner-freebsd-hardware Wed Jun 25 06:51:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id GAA23235 for hardware-outgoing; Wed, 25 Jun 1997 06:51:29 -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 GAA23229 for ; Wed, 25 Jun 1997 06:51:27 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id GAA21346; Wed, 25 Jun 1997 06:51:31 -0700 (PDT) To: Andreas Klemm cc: hardware@FreeBSD.ORG Subject: Re: Advice for a 10/100 MBit PCI card In-reply-to: Your message of "Wed, 25 Jun 1997 14:48:02 +0200." <19970625144802.57953@sunny.wup.de> Date: Wed, 25 Jun 1997 06:51:30 -0700 Message-ID: <21343.867246690@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Intel Pro 100B. You need to read the mailing lists more often - this has been discussed to death. :) Jordan > Hi ! > > Need a quick advice, which 10/100 MBit Tisted pair PCI > card works best supported and reliable under FreeBSD 2.1 and > 2.2. > > Theres a good chance, that our company will get a FreeBSD > communications server soon ... !!! > > And I urgently need some help, because of the pitfalls > I heard about supported and not supported DEC Chips and > such .... > > What PCI cards are in use on freefall and wcarchive ??? > Do you think FreeBSD-2.2.2 is ok for a reliable server > or should I better choose 2.1.7.1 ??? > > I think the FreeBSD-2.2.2 machines are well enough and > one could use the -current ports, which might be an > advantage over the older ports .... > > Andreas /// > > -- > aklemm@wup.de /\/\___ Wiechers & Partner Datentechnik GmbH > Andreas Klemm ___/\/\/ - Support Unix - From owner-freebsd-hardware Wed Jun 25 09:18:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id JAA00863 for hardware-outgoing; Wed, 25 Jun 1997 09:18:19 -0700 (PDT) Received: from dpnegoro.bit.net.id (dpnegoro.bit.net.id [202.147.252.3]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id JAA00858 for ; Wed, 25 Jun 1997 09:18:08 -0700 (PDT) Received: from phoenix (rover5-2.bit.net.id [202.147.252.134]) by dpnegoro.bit.net.id (8.7.6/SCO5) with SMTP id QAA06659 for ; Wed, 25 Jun 1997 16:23:15 GMT Message-Id: <3.0.1.32.19970625132151.0071f3ac@mail.bit.net.id> X-Sender: phoenix@mail.bit.net.id (Unverified) X-Mailer: Windows Eudora Pro Version 3.0.1 (32) Date: Wed, 25 Jun 1997 13:21:51 +0700 To: hardware@FreeBSD.ORG From: Irwan Hadi Subject: Get FreeBSD Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk I just want to know, where can I get the Newest Free BSD in the internet ? I hope that I can buy it and hope the price is quite cheap :) ***************************************************************** * This E-Mail was sent by : Irwan Hadi ** * Want reply it ?? mailto:phoenix@bit.net.id ** * ** * \\\|/// ** * \\ ~ ~ // ** * (/ @ @ /) ** * ____ oOOo_(.)_oOOo ________ ** * ________________________ ** * Another E-Mail account : phoenixboy@rocketmail.com ** * atlasboy@hotmail.com ** * phoenix@cutey.com ** * andromeda@emails.com ** * phoenixboy@bigfoot.com ** * URl http://www.geocities.com/SouthBeach/Lights/7855/index.html ** * http://www.geocities.com/TheTropics/Shores/5458/index.html ** * http://www.geocities.com/Athens/Forum/4878/index.html ** ****************************************************************** -----BEGIN PGP SIGNATURE----- Version: 2.6.3i Charset: noconv Comment: Requires PGP version 2.6 or later. iQEVAwUBM6T+yWG82edHTLXxAQFStQgAkyz4wd2S5+LQrWkF1KPSMa4Ng6ojkLBO flSC5Y/AkN28Turh9KckFPs1ljLwgFKmJZJEB1M+j8/mG9YAWy4s8vRI6i1MxMsz PMJLzgi/DlodSlTQrDzMfnYUVV6dRjk2jnx8h4xZLBf6qxIBWg64JY/zZBaGiMXC uR0v33UBoRgqIJdcl3ywKC3CTJRhGdCkeCdaxpIwOdklBsING5RMGvtRACmhdThv RpYOFeGvnQJb3MG2IZw5OpeSgHnbY917w7sDNlZgylOtdESaI3yjbFQ7TUFZz6nm 4b3802Np1jW5mNBg6wjBspE9uPBqv6LNuI5oOl4wK6r0uMANW9q08A== =9ZDR -----END PGP SIGNATURE----- From owner-freebsd-hardware Wed Jun 25 20:47:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA01553 for hardware-outgoing; Wed, 25 Jun 1997 20:47:45 -0700 (PDT) Received: from madoka.hal.t.u-tokyo.ac.jp (madoka.hal.t.u-tokyo.ac.jp [133.11.98.129]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA01545 for ; Wed, 25 Jun 1997 20:47:33 -0700 (PDT) Received: from hitomi.hal.t.u-tokyo.ac.jp (hitomi.hal.t.u-tokyo.ac.jp [133.11.98.148]) by madoka.hal.t.u-tokyo.ac.jp (8.8.5+2.7Wbeta5/3.5Wpl2/HALmailhost/97020422) with ESMTP id MAA11813; Thu, 26 Jun 1997 12:44:44 +0900 (JST) Received: from hal.t.u-tokyo.ac.jp by hitomi.hal.t.u-tokyo.ac.jp (8.8.5+2.7Wbeta5/3.2W5/HAL) with ESMTP id MAA05400; Thu, 26 Jun 1997 12:44:37 +0900 (JST) Message-Id: <199706260344.MAA05400@hitomi.hal.t.u-tokyo.ac.jp> To: phoenix@bit.net.id Cc: hardware@freebsd.org Subject: Re: Get FreeBSD In-Reply-To: Your message of "Wed, 25 Jun 1997 13:21:51 +0700" References: <3.0.1.32.19970625132151.0071f3ac@mail.bit.net.id> X-Mailer: Mew version 1.70 on Emacs 19.28.1 / Mule 2.3 X-PGP-fingerprint: 5A A1 E6 D0 FF 96 FB F8 DE 23 EF 06 A1 76 94 E9 X-PGP-Public-Key-Location: finger -l pasqual@hal.t.u-tokyo.ac.jp or Home Page X-URL: http://www.hal.t.u-tokyo.ac.jp/~pasqual Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Date: Thu, 26 Jun 1997 12:44:37 +0900 From: "" Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk phoenix> I just want to know, where can I get the Newest Free BSD in the internet ? phoenix> I hope that I can buy it and hope the price is quite cheap :) www.cdrom.com or look at www.freebsd.org From owner-freebsd-hardware Thu Jun 26 04:58:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA18456 for hardware-outgoing; Thu, 26 Jun 1997 04:58:16 -0700 (PDT) Received: from dolphin.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 EAA18448; Thu, 26 Jun 1997 04:58:11 -0700 (PDT) Received: (from conrads@localhost) by dolphin.neosoft.com (8.8.5/8.8.5) id GAA01166; Thu, 26 Jun 1997 06:58:20 -0500 (CDT) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Date: Thu, 26 Jun 1997 06:43:44 -0500 (CDT) Organization: NeoSoft, Inc. From: Conrad Sabatier To: freebsd-multimedia@freebsd.org Subject: Advice on audio strategy needed Cc: freebsd-hardware@freebsd.org, freebsd-questions@freebsd-org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hope no one minds the cross-mailing. Wasn't sure which would be the best group. I'm in need of some advice on how to approach a rather tricky problem. The situation is this: I have two conflicting sound sources in my machine. One is the motherboard audio, a Crystal 4232C that cannot be disabled by hardware or software toggles, and the other is a Soundblaster AWE 64. Both devices are Plug-and-Play, both default to the same IRQ's, etc. No jumpers to configure either through hardware. What would be the best approach to take in configuring a kernel for such a setup? Ideally, I'd like to use the AWE 64, of course. I've been exploring the PnP patches, but I'm not getting something right in the configuration, as at boot time, my audio is not detected. Should I configure for both devices? Or only one? Is the order of devices critical in the PnP (pnp.c) configuration? Do I have to configure for *all* devices in pnp.c, even those I don't intend to use (game controllers and such)? A lot of questions, I know. :-) But after months of struggling with this thing, I could really use some fresh input. Obviously, I'm missing something here. I've just upgraded to FreeBSD-current, by the way. Many thanks for any advice. -- Conrad Sabatier http://www.neosoft.com/~conrads/ From owner-freebsd-hardware Thu Jun 26 05:02:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id FAA18722 for hardware-outgoing; Thu, 26 Jun 1997 05:02:32 -0700 (PDT) Received: from dolphin.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 FAA18702; Thu, 26 Jun 1997 05:02:23 -0700 (PDT) Received: (from conrads@localhost) by dolphin.neosoft.com (8.8.5/8.8.5) id HAA01195; Thu, 26 Jun 1997 07:02:33 -0500 (CDT) Resent-Message-Id: <199706261202.HAA01195@dolphin.neosoft.com> Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 Resent-Date: Thu, 26 Jun 1997 06:43:44 -0500 (CDT) Resent-From: Conrad Sabatier Resent-To: freebsd-multimedia@freebsd.org Date: Thu, 26 Jun 1997 07:00:51 -0500 (CDT) Organization: NeoSoft, Inc. From: Conrad Sabatier To: freebsd-multimedia@freebsd.org Subject: Advice on audio strategy needed Cc: freebsd-hardware@freebsd.org, freebsd-questions@freebsd.org Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hope no one minds the cross-mailing. Wasn't sure which would be the best group. And my apologies if this appears twice; I messed up one of the addresses the first time. I'm in need of some advice on how to approach a rather tricky problem. The situation is this: I have two conflicting sound sources in my machine. One is the motherboard audio, a Crystal 4232C that cannot be disabled by hardware or software toggles, and the other is a Soundblaster AWE 64. Both devices are Plug-and-Play, both default to the same IRQ's, etc. No jumpers to configure either through hardware. What would be the best approach to take in configuring a kernel for such a setup? Ideally, I'd like to use the AWE 64, of course. I've been exploring the PnP patches, but I'm not getting something right in the configuration, as at boot time, my audio is not detected. Should I configure for both devices? Or only one? Is the order of devices critical in the PnP (pnp.c) configuration? Do I have to configure for *all* devices in pnp.c, even those I don't intend to use (game controllers and such)? A lot of questions, I know. :-) But after months of struggling with this thing, I could really use some fresh input. Obviously, I'm missing something here. I've just upgraded to FreeBSD-current, by the way. Many thanks for any advice. -- Conrad Sabatier http://www.neosoft.com/~conrads/ From owner-freebsd-hardware Thu Jun 26 08:55:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id IAA27331 for hardware-outgoing; Thu, 26 Jun 1997 08:55:39 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id IAA27306; Thu, 26 Jun 1997 08:55:33 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id IAA02297; Thu, 26 Jun 1997 08:55:26 -0700 (PDT) Message-Id: <199706261555.IAA02297@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: Conrad Sabatier cc: freebsd-multimedia@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG Subject: Re: Advice on audio strategy needed In-reply-to: Your message of "Thu, 26 Jun 1997 07:00:51 CDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 26 Jun 1997 08:55:25 -0700 From: Amancio Hasty Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Just disable the CS4232C and use your AWE .. Your motherboard should come with a manual which should have the info on how to disable the CS4232c if not just call the motherboard manufacturer. Here is an old posting from Randal Hopper: From: rhh@ct.picker.com (Randall Hopper) To: multimedia@freebsd.org, bkogawa@primenet.com Subject: ANN: AWEDRV 0.2.99c AWE32 & Sound Blaster 32 owners: AWEDRV 0.2.99c was released recently. This drops right into a 2.2-ALPHA kernel -- just follow INSTALL.frbsd in the driver package. New features: recent versions now allow loading .SBKs/.SF2s directly without patching, and also support stereo/multi-layer instruments. If you'd like to try it, I've created a help page you might want to browse: http://multiverse.com/~rhh/awedrv/ Have fun, Amancio >From The Desk Of Conrad Sabatier : > Hope no one minds the cross-mailing. Wasn't sure which would be the best > group. And my apologies if this appears twice; I messed up one of the > addresses the first time. > > I'm in need of some advice on how to approach a rather tricky problem. > The situation is this: I have two conflicting sound sources in my machine. > One is the motherboard audio, a Crystal 4232C that cannot be disabled by > hardware or software toggles, and the other is a Soundblaster AWE 64. > Both devices are Plug-and-Play, both default to the same IRQ's, etc. > No jumpers to configure either through hardware. > > What would be the best approach to take in configuring a kernel for > such a setup? Ideally, I'd like to use the AWE 64, of course. I've > been exploring the PnP patches, but I'm not getting something right in > the configuration, as at boot time, my audio is not detected. > > Should I configure for both devices? Or only one? Is the order of > devices critical in the PnP (pnp.c) configuration? Do I have to configure > for *all* devices in pnp.c, even those I don't intend to use (game > controllers and such)? > > A lot of questions, I know. :-) But after months of struggling with this > thing, I could really use some fresh input. Obviously, I'm missing > something here. > > I've just upgraded to FreeBSD-current, by the way. > > Many thanks for any advice. > > -- > Conrad Sabatier > http://www.neosoft.com/~conrads/ From owner-freebsd-hardware Thu Jun 26 10:16:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA01408 for hardware-outgoing; Thu, 26 Jun 1997 10:16:00 -0700 (PDT) Received: from agora.rdrop.com (root@agora.rdrop.com [199.2.210.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA01403 for ; Thu, 26 Jun 1997 10:15:58 -0700 (PDT) Received: from sed.cs.fsu.edu (sed.cs.fsu.edu [128.186.121.157]) by agora.rdrop.com (8.8.5/8.8.5) with ESMTP id KAA02610 for ; Thu, 26 Jun 1997 10:15:54 -0700 (PDT) Received: (from uh@localhost) by sed.cs.fsu.edu (8.8.5/8.7.3) id NAA01145 for freebsd-hardware@FreeBSD.ORG; Thu, 26 Jun 1997 13:14:27 -0400 (EDT) Date: Thu, 26 Jun 1997 13:14:27 -0400 (EDT) From: Gang-Ryung Uh Message-Id: <199706261714.NAA01145@sed.cs.fsu.edu> To: freebsd-hardware@FreeBSD.ORG Subject: NEC versa 6200 Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hello, If you successfully installed FreeBSD on this machine, then would you let me know? Thanks. Gang-Ryung Uh (uh@cs.fsu.edu) From owner-freebsd-hardware Thu Jun 26 10:17:46 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA01535 for hardware-outgoing; Thu, 26 Jun 1997 10:17:46 -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 KAA01493; Thu, 26 Jun 1997 10:17:28 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.7.5/8.7.3) id NAA26228; Thu, 26 Jun 1997 13:20:24 -0400 (EDT) Date: Thu, 26 Jun 1997 13:20:24 -0400 (EDT) From: "John T. Farmer" Message-Id: <199706261720.NAA26228@sabre.goldsword.com> To: conrads@neosoft.com, hasty@rah.star-gate.com Subject: Re: Advice on audio strategy needed Cc: freebsd-hardware@FreeBSD.ORG, freebsd-multimedia@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, jfarmer@goldsword.com Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 26 Jun 1997 08:55:25 -0700 Amancio Hasty said: >Just disable the CS4232C and use your AWE .. > >Your motherboard should come with a manual which should have the info >on how to disable the CS4232c if not just call the motherboard manufacturer. > >Here is an old posting from Randal Hopper: >From: rhh@ct.picker.com (Randall Hopper) >To: multimedia@freebsd.org, bkogawa@primenet.com >Subject: ANN: AWEDRV 0.2.99c > >AWE32 & Sound Blaster 32 owners: > > AWEDRV 0.2.99c was released recently. This drops right into a >2.2-ALPHA kernel -- just follow INSTALL.frbsd in the driver package. New >features: recent versions now allow loading .SBKs/.SF2s directly without >patching, and also support stereo/multi-layer instruments. > > If you'd like to try it, I've created a help page you might want to >browse: > > http://multiverse.com/~rhh/awedrv/ > > Have fun, > Amancio Uh, I believe that he said that the onboard audio _could_not_ be disabled. While I've never run into such a setup, I'm willing to believe that a "bottom feeder" MB manufacturer would leave out control of on-board devices, leaving you with only PnPray to enable/disable it. John ------------------------------------------------------------------------- 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 Thu Jun 26 10:29:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA02051 for hardware-outgoing; Thu, 26 Jun 1997 10:29:54 -0700 (PDT) Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA02005; Thu, 26 Jun 1997 10:29:42 -0700 (PDT) Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.8.5) with ESMTP id KAA14373; Thu, 26 Jun 1997 10:29:35 -0700 (PDT) Message-Id: <199706261729.KAA14373@rah.star-gate.com> X-Mailer: exmh version 1.6.9 8/22/96 To: "John T. Farmer" cc: conrads@neosoft.com, freebsd-hardware@FreeBSD.ORG, freebsd-multimedia@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, jfarmer@goldsword.com Subject: Re: Advice on audio strategy needed In-reply-to: Your message of "Thu, 26 Jun 1997 13:20:24 EDT." <199706261720.NAA26228@sabre.goldsword.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Thu, 26 Jun 1997 10:29:34 -0700 From: Amancio Hasty Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Most likely he has an Intel motherboard which you can indeed disable the CS4232C. At any rate Sujal Patel's PnP stuff should be able also to disable the CS4232c however the BIOS will still reserve the CS4232c's IRQs which translates to wasting IRQ during the BIOS init. So the question now is : what is his make and model for his motherboard. Amancio >From The Desk Of "John T. Farmer" : > > On Thu, 26 Jun 1997 08:55:25 -0700 Amancio Hasty said: > >Just disable the CS4232C and use your AWE .. > > > >Your motherboard should come with a manual which should have the info > >on how to disable the CS4232c if not just call the motherboard manufacturer. > > > >Here is an old posting from Randal Hopper: > >From: rhh@ct.picker.com (Randall Hopper) > >To: multimedia@freebsd.org, bkogawa@primenet.com > >Subject: ANN: AWEDRV 0.2.99c > > > >AWE32 & Sound Blaster 32 owners: > > > > AWEDRV 0.2.99c was released recently. This drops right into a > >2.2-ALPHA kernel -- just follow INSTALL.frbsd in the driver package. New > >features: recent versions now allow loading .SBKs/.SF2s directly without > >patching, and also support stereo/multi-layer instruments. > > > > If you'd like to try it, I've created a help page you might want to > >browse: > > > > http://multiverse.com/~rhh/awedrv/ > > > > Have fun, > > Amancio > > Uh, I believe that he said that the onboard audio _could_not_ be disabled. > > While I've never run into such a setup, I'm willing to believe that a > "bottom feeder" MB manufacturer would leave out control of on-board > devices, leaving you with only PnPray to enable/disable it. > > John > > ------------------------------------------------------------------------- > 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 Thu Jun 26 11:12:53 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA03626 for hardware-outgoing; Thu, 26 Jun 1997 11:12:53 -0700 (PDT) Received: from mail.sns.com (jack.sns.com [199.35.183.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id LAA03620; Thu, 26 Jun 1997 11:12:44 -0700 (PDT) Received: from speedy.pcscons.net by mail.sns.com with smtp (Smail3.1.28.1 #5) id m0whJ1t-000Q9NC; Thu, 26 Jun 97 11:12 PDT Message-Id: <3.0.2.32.19970626111147.0085a4b0@mail.sns.com> X-Sender: ludwigp@mail.sns.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) Date: Thu, 26 Jun 1997 11:11:47 -0700 To: Amancio Hasty , "John T. Farmer" From: Ludwig Pummer Subject: Re: Advice on audio strategy needed Cc: conrads@neosoft.com, freebsd-hardware@FreeBSD.ORG, freebsd-multimedia@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, jfarmer@goldsword.com In-Reply-To: <199706261729.KAA14373@rah.star-gate.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from quoted-printable to 8bit by hub.freebsd.org id LAA03622 Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 10:29 AM 6/26/97 -0700, Amancio Hasty wrote: >Most likely he has an Intel motherboard which you can indeed disable the >CS4232C. At any rate Sujal Patel's PnP stuff should be able also to disable >the CS4232c however the BIOS will still reserve the CS4232c's IRQs >which translates to wasting IRQ during the BIOS init. Sounds like he has the Intel Atlantis (Advanced/AS), which has the CS4232C soundcard-on-a-chip, and an ATI mach64 video card (video card is optional) built into the motherboard. From Intel's Atlantis FAQ (http://developer.intel.com/design/motherbd/as/as_inst.HTM): ----- How can I disable the Crystal audio component on the Advanced/AS? For non-Plug and Play operating systems (DOS, Windows, WFW, etc.) you need to use the ISA Configuration Utility (ICU) to disable the Advanced/AS on-board Crystal Audio subsystem. Important note: The DOS/Windows ICU should not be used with Windows 95. Follow these steps with non-Plug and Play operating systems: To disable the on-board sound using the Windows 95 device manager: It basically says to uncheck the box marked "Original Configuration". Finally, using a text editor, add REM in front of C:\win95\cs4232c.exe /w /x in the CONFIG.SYS file. The above procedure can be used for disabling the Crystal Audio component using version 1.24 of the Windows 95 Crystal audio drivers. The above procedure also can be used to disable the Crystal Audio component for drivers previous to version 1.24. The driver names in the Device Manager for previous versions are: •Crystal CS4232PNP Audio Hardware •Gameport Joystick •MPU-401 Compatible ----- Obviously, not very friendly to non-Micro$oft systems. --Ludwig Pummer ------------------------------------------------------------------ ludwigp@bigfoot.com ICQ UIN: 692441 http://chipweb.home.ml.org PGP Key & Geek Code available on web page ^-- Updated 04/18/97 "If God had intended Man to Smoke, He would have set him on Fire." From owner-freebsd-hardware Thu Jun 26 11:18:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA03982 for hardware-outgoing; Thu, 26 Jun 1997 11:18:19 -0700 (PDT) Received: from plains.NoDak.edu (plains.NoDak.edu [134.129.111.64]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA03942; Thu, 26 Jun 1997 11:18:09 -0700 (PDT) Received: (from tinguely@localhost) by plains.NoDak.edu (8.8.5/8.8.5) id NAA03894; Thu, 26 Jun 1997 13:17:27 -0500 (CDT) Date: Thu, 26 Jun 1997 13:17:27 -0500 (CDT) From: Mark Tinguely Message-Id: <199706261817.NAA03894@plains.NoDak.edu> To: conrads@neosoft.com, hasty@rah.star-gate.com, jfarmer@sabre.goldsword.com Subject: Re: Advice on audio strategy needed Cc: freebsd-hardware@FreeBSD.ORG, freebsd-multimedia@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, jfarmer@goldsword.com Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Uh, I believe that he said that the onboard audio _could_not_ be disabled. > > While I've never run into such a setup, I'm willing to believe that a > "bottom feeder" MB manufacturer would leave out control of on-board > devices, leaving you with only PnPray to enable/disable it. HP sells a Pentium computer that does not have jumpers or a BIOS option to disable the onboard Crystal soundcard. The machine was here so quickly that I did not see the manufacturer of the motherboard. According to the owner, he could not get the OSS driver to work with the card. People that buy these crap machines cannot afford to lose a IRQ. They already max-ed out the IRQs because of IDE drive, APATI drive, PS/2 mouse and (usually internal) modem. --mark. From owner-freebsd-hardware Thu Jun 26 11:32:14 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id LAA04576 for hardware-outgoing; Thu, 26 Jun 1997 11:32:14 -0700 (PDT) Received: from vdp01.vailsystems.com (root@vdp01.vailsystems.com [207.152.98.18]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id LAA04556; Thu, 26 Jun 1997 11:32:09 -0700 (PDT) Received: from crocodile.vale.com (crocodile [192.168.128.47]) by vdp01.vailsystems.com (8.8.3/8.7.3) with ESMTP id NAA20312; Thu, 26 Jun 1997 13:30:10 -0500 (CDT) Received: from slave1.vale.com (slave1.vale.com [192.168.129.10]) by crocodile.vale.com (8.8.3/8.7.3) with ESMTP id NAA18335; Thu, 26 Jun 1997 13:30:09 -0500 (CDT) Message-ID: <33B2B52B.61CED7CB@vailsys.com> Date: Thu, 26 Jun 1997 13:30:03 -0500 From: Dan Riley Organization: Vail Systems, Inc. X-Mailer: Mozilla 4.0b5C (X11; I; FreeBSD 2.2.2-RELEASE i386) MIME-Version: 1.0 To: Amancio Hasty CC: "John T. Farmer" , conrads@neosoft.com, freebsd-hardware@FreeBSD.ORG, freebsd-multimedia@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, jfarmer@goldsword.com Subject: Re: Advice on audio strategy needed X-Priority: 3 (Normal) References: <199706261729.KAA14373@rah.star-gate.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Amancio Hasty wrote: > > Most likely he has an Intel motherboard which you can indeed disable > the > CS4232C. At any rate Sujal Patel's PnP stuff should be able also to > disable > the CS4232c however the BIOS will still reserve the CS4232c's IRQs > which translates to wasting IRQ during the BIOS init. > > So the question now is : what is his make and model for his > motherboard. > If this is a Intel Atlantis or a similiar Intel mb with the Crystal Audio integrated chipset, I went through the same thing several months ago and at that time there was a utility on the Intel web site for configuring the integrated Crystal Audio PnP options (if you care to boot dos). Hope this helps. Regards, Dan Riley From owner-freebsd-hardware Thu Jun 26 12:16:07 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA06591 for hardware-outgoing; Thu, 26 Jun 1997 12:16:07 -0700 (PDT) Received: from indurain.cse.ogi.edu (indurain.cse.ogi.edu [129.95.50.34]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA06569 for ; Thu, 26 Jun 1997 12:16:04 -0700 (PDT) Received: from localhost by indurain.cse.ogi.edu with SMTP (1.38.193.4/16.2) id AA04845; Thu, 26 Jun 1997 12:16:02 -0700 Date: Thu, 26 Jun 1997 12:16:02 -0700 (PDT) From: Jon Inouye To: freebsd-hardware@FreeBSD.ORG Subject: IRQ assignment for PII motherboards Message-Id: Organization: Oregon Graduate Institute of Science & Technology Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk We just received two machines using Pentium II motherboards (Intel PD440FX) with AMI BIOS 1.00.04.DT0. The problem is the BIOS configures the PCI SCSI and Ethernet devices to share the same IRQ. While WindowsNT device drivers appear to have no problem with this (IRQ sharing is part of the PCI spec), some Linux and FreeBSD drivers do. There are some free IRQs, but the BIOS assignment appears to be non-user-configurable. I've looked for a SCU (System Configuration Utility) program for this motherboard on the Intel developers web site without success. Moving boards around and disabling the COM, USB, and LPT devices didn't help either. The current solution is removing the SCSI controller and going with an IDE disk. I'd appreciate any other suggestions or pointers to a SCU program I can use! -- Jon From owner-freebsd-hardware Thu Jun 26 12:30:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA07262 for hardware-outgoing; Thu, 26 Jun 1997 12:30:16 -0700 (PDT) Received: from george.lbl.gov (george.lbl.gov [128.3.196.93]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id MAA07255 for ; Thu, 26 Jun 1997 12:30:12 -0700 (PDT) Received: (jin@localhost) by george.lbl.gov (8.6.10/8.6.5) id MAA09301; Thu, 26 Jun 1997 12:30:11 -0700 Date: Thu, 26 Jun 1997 12:30:11 -0700 From: "Jin Guojun[ITG]" Message-Id: <199706261930.MAA09301@george.lbl.gov> To: freebsd-hardware@FreeBSD.ORG, jinouye@cse.ogi.edu Subject: Re: IRQ assignment for PII motherboards Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk This is no a real BIOS problem. Two ways to solve it: (1) boot -c irq xxx # xxx is either your SCSI or Ethernet devices name # is any non-shared irq. (2) recompile your kernel. Please refer the freebsd manual. -Jin >We just received two machines using Pentium II motherboards >(Intel PD440FX) with AMI BIOS 1.00.04.DT0. The problem is the >BIOS configures the PCI SCSI and Ethernet devices to share the >same IRQ. While WindowsNT device drivers appear to have no problem >with this (IRQ sharing is part of the PCI spec), some Linux and FreeBSD >drivers do. There are some free IRQs, but the BIOS assignment appears >to be non-user-configurable. I've looked for a SCU (System Configuration >Utility) program for this motherboard on the Intel developers web >site without success. Moving boards around and disabling the COM, USB, >and LPT devices didn't help either. > >The current solution is removing the SCSI controller and going with >an IDE disk. I'd appreciate any other suggestions or pointers to >a SCU program I can use! From owner-freebsd-hardware Thu Jun 26 13:09:13 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id NAA09436 for hardware-outgoing; Thu, 26 Jun 1997 13:09:13 -0700 (PDT) Received: from GndRsh.aac.dev.com (GndRsh.aac.dev.com [198.145.92.241]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id NAA09429 for ; Thu, 26 Jun 1997 13:09:08 -0700 (PDT) Received: (from rgrimes@localhost) by GndRsh.aac.dev.com (8.8.5/8.7.3) id NAA07276; Thu, 26 Jun 1997 13:08:53 -0700 (PDT) From: "Rodney W. Grimes" Message-Id: <199706262008.NAA07276@GndRsh.aac.dev.com> Subject: Re: IRQ assignment for PII motherboards In-Reply-To: from Jon Inouye at "Jun 26, 97 12:16:02 pm" To: jinouye@cse.ogi.edu (Jon Inouye) Date: Thu, 26 Jun 1997 13:08:53 -0700 (PDT) Cc: freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL25 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > We just received two machines using Pentium II motherboards > (Intel PD440FX) with AMI BIOS 1.00.04.DT0. The problem is the The only suggestions I can make is don't buy Intel Brand motherboards, they Intel OEMCO division thinks that what they have done is just dandy and could care less that sharing interrupts is a bad idea for server class machines, and/or specify Award BIOS's on all products ordered, as the Award BIOS tends to be very good about not doing this, and when it does do it you have enough control in the PCI/Pnp setup screen to ``fix it''. ... -- Rod Grimes rgrimes@gndrsh.aac.dev.com Accurate Automation, Inc. Reliable computers for FreeBSD From owner-freebsd-hardware Thu Jun 26 15:09:37 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id PAA15302 for hardware-outgoing; Thu, 26 Jun 1997 15:09:37 -0700 (PDT) Received: from dolphin.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 PAA15291; Thu, 26 Jun 1997 15:09:27 -0700 (PDT) Received: (from conrads@localhost) by dolphin.neosoft.com (8.8.5/8.8.5) id RAA03577; Thu, 26 Jun 1997 17:08:47 -0500 (CDT) Message-ID: X-Mailer: XFMail 1.1 [p0] on FreeBSD Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <199706261817.NAA03894@plains.NoDak.edu> Date: Thu, 26 Jun 1997 16:47:47 -0500 (CDT) Organization: NeoSoft, Inc. From: Conrad Sabatier To: freebsd-multimedia@FreeBSD.ORG Subject: Re: Advice on audio strategy needed Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk [ freebsd-questions removed from Cc: (better, Jordan?) :-) ] On 26-Jun-97 Mark Tinguely wrote: > >> Uh, I believe that he said that the onboard audio _could_not_ be >> disabled. >> >> While I've never run into such a setup, I'm willing to believe that a >> "bottom feeder" MB manufacturer would leave out control of on-board >> devices, leaving you with only PnPray to enable/disable it. > >HP sells a Pentium computer that does not have jumpers or a BIOS option to >disable the onboard Crystal soundcard. The machine was here so quickly >that I did not see the manufacturer of the motherboard. According to >the owner, he could not get the OSS driver to work with the card. Yep, that's what I got -- an HP Pavilion 7160. I've already called HP about this, which was where I got the shocking news that the onboard audio could not be disabled. I wanted to reach through the phone and strangle someone. I never could get OSS to work either, by the way. Thinking seriously of just replacing the motherboard completely. I'm *really* tired of grappling with this problem. Besides the above, the BIOS setup utility really stinks, too. Obviously a machine for clueless Windoze users. At the time, it was one of the earliest 166 MHz machines out, and seemed like a good buy. >People that buy these crap machines cannot afford to lose a IRQ. They >already max-ed out the IRQs because of IDE drive, APATI drive, PS/2 >mouse and (usually internal) modem. Yep, you're right on it. I don't use the internal whatever-the-hell-it-is modem, though. Much prefer my external Sportster 33.6. Thanks for all the replies, folks. While not quite what I was hoping for (like, some miraculous solution to this aggravating situation), the feedback was enlightening, and much appreciated. Guess it's time once again to whip out the plastic and dig myself even deeper into debt. I never should have bought the damned AWE 64, really. When I was checking it out in the store, though, I saw nothing on the box that indicated it was PnP. Should have returned it at once. Oh well. It does sound great under Windows (like, who cares?). :-) -- Conrad Sabatier http://www.neosoft.com/~conrads/ From owner-freebsd-hardware Thu Jun 26 16:28:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id QAA19007 for hardware-outgoing; Thu, 26 Jun 1997 16:28:16 -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 QAA19002 for ; Thu, 26 Jun 1997 16:28:13 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id QAA28217; Thu, 26 Jun 1997 16:28:40 -0700 (PDT) To: "Jin Guojun[ITG]" cc: freebsd-hardware@FreeBSD.ORG, jinouye@cse.ogi.edu Subject: Re: IRQ assignment for PII motherboards In-reply-to: Your message of "Thu, 26 Jun 1997 12:30:11 PDT." <199706261930.MAA09301@george.lbl.gov> Date: Thu, 26 Jun 1997 16:28:39 -0700 Message-ID: <28213.867367719@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > This is no a real BIOS problem. Two ways to solve it: > (1) boot -c > irq xxx # For a pair of PCI devices? That would be an interesting trick. I don't think you read his message in enough detail. :-) > (2) recompile your kernel. Please refer the freebsd manual. Won't help either - see above. The bigger issue here for me at least is why this doesn't work with a shared IRQ. I've had, for example, my SMC (PCI) ethernet card and my Adaptec 2940 on the same IRQ and it worked just fine. No problems. What are the symptoms of failure with the shared IRQ this person is having? Are they sure it's because of IRQ sharing that this problem exists, or is it perhaps something else? Jordan From owner-freebsd-hardware Thu Jun 26 17:12:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA21664 for hardware-outgoing; Thu, 26 Jun 1997 17:12:50 -0700 (PDT) Received: from indurain.cse.ogi.edu (indurain.cse.ogi.edu [129.95.50.34]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id RAA21659 for ; Thu, 26 Jun 1997 17:12:48 -0700 (PDT) Received: from localhost by indurain.cse.ogi.edu with SMTP (1.38.193.4/16.2) id AA05254; Thu, 26 Jun 1997 17:12:45 -0700 Date: Thu, 26 Jun 1997 17:12:45 -0700 (PDT) From: Jon Inouye Reply-To: Jon Inouye To: "Jordan K. Hubbard" Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: IRQ assignment for PII motherboards In-Reply-To: <28213.867367719@time.cdrom.com> Message-Id: Organization: Oregon Graduate Institute of Science & Technology Mime-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 26 Jun 1997, Jordan K. Hubbard wrote: > The bigger issue here for me at least is why this doesn't work with a > shared IRQ. I've had, for example, my SMC (PCI) ethernet card and my > Adaptec 2940 on the same IRQ and it worked just fine. No problems. > > What are the symptoms of failure with the shared IRQ this person > is having? Are they sure it's because of IRQ sharing that this > problem exists, or is it perhaps something else? > > Jordan Umm, I don't want to start a flame war here, but most of the problems have been with Red Hat Linux drivers not wanting to share PCI interrupts. ;-) The Linux side of the group is currently searching for PCI PnP software. David Greenman confirmed that FreeBSD supports PCI interrupt sharing and should work fine on the PD440FX motherboard. (PC-Card interrupt sharing, required for multi-function PCMCIA devices, is not yet supported as far as I know.) However, sharing an IRQ between an Intel EtherExpress 10/100 and an Adaptec 3940W is _not_ performance friendly - I expect timeout errors for FreeBSD and see them occasionally on WindowsNT. You would think that given some free IRQs (by disabling the serial, parallel, and USB ports) the BIOS would set up a one-to-one mapping between PCI interrupts and ISA IRQs. Unfortunately, it doesn't seem to want to and there appears to be no hook to manually configure things. Oh, well, I sent off email to our Intel sponsors and hope to get utility software from them - or a BIOS upgrade. (Or perhaps even a RTFM on page xxx! ;-) -JI From owner-freebsd-hardware Thu Jun 26 17:24:55 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id RAA22284 for hardware-outgoing; Thu, 26 Jun 1997 17:24:55 -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 RAA22276 for ; Thu, 26 Jun 1997 17:24:51 -0700 (PDT) Received: from time.cdrom.com (jkh@localhost.cdrom.com [127.0.0.1]) by time.cdrom.com (8.8.5/8.6.9) with ESMTP id RAA28616; Thu, 26 Jun 1997 17:25:18 -0700 (PDT) To: Jon Inouye cc: freebsd-hardware@FreeBSD.ORG Subject: Re: IRQ assignment for PII motherboards In-reply-to: Your message of "Thu, 26 Jun 1997 17:12:45 PDT." Date: Thu, 26 Jun 1997 17:25:18 -0700 Message-ID: <28612.867371118@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > However, sharing an IRQ between an Intel EtherExpress 10/100 and an > Adaptec 3940W is _not_ performance friendly - I expect timeout errors for > FreeBSD and see them occasionally on WindowsNT. You would think that Really? I wouldn't expect it and will be curious to see what your actual results are. Sorry, I mis-inferred from your previous message that you were already running FreeBSD and were having problems, not that you hadn't even tried it yet. Please, go try it and then come back and tell us what happens. :) Jordan From owner-freebsd-hardware Thu Jun 26 18:06:10 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA24570 for hardware-outgoing; Thu, 26 Jun 1997 18:06:10 -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 SAA24563 for ; Thu, 26 Jun 1997 18:06:05 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with SMTP id SAA10980; Thu, 26 Jun 1997 18:07:09 -0700 (PDT) Message-Id: <199706270107.SAA10980@implode.root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Jon Inouye cc: "Jordan K. Hubbard" , freebsd-hardware@FreeBSD.ORG Subject: Re: IRQ assignment for PII motherboards In-reply-to: Your message of "Thu, 26 Jun 1997 17:12:45 PDT." From: David Greenman Reply-To: dg@root.com Date: Thu, 26 Jun 1997 18:07:09 -0700 Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >However, sharing an IRQ between an Intel EtherExpress 10/100 and an >Adaptec 3940W is _not_ performance friendly - I expect timeout errors for >FreeBSD and see them occasionally on WindowsNT. You would think that >given some free IRQs (by disabling the serial, parallel, and USB ports) >the BIOS would set up a one-to-one mapping between PCI interrupts and ISA >IRQs. Unfortunately, it doesn't seem to want to and there appears to be >no hook to manually configure things. Oh, well, I sent off email to our >Intel sponsors and hope to get utility software from them - or a BIOS >upgrade. (Or perhaps even a RTFM on page xxx! ;-) I was able to get the Pro/100B, in a system with a pair of ahc3940's, to get assigned to a non-shared interrupt by playing around with which slots the cards were plugged into. It took about 3 tries to find the right order (including leaving a slot empty), but I finally found an arrangement that worked. My understanding is that the shared irq assignment isn't a function of the BIOS, but rather a function of the slot the card is in and how it is wired compared to the others. The motherboard I did this in wasn't made by Intel, but the same principles should still apply. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hardware Thu Jun 26 20:24:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA00958 for hardware-outgoing; Thu, 26 Jun 1997 20:24:19 -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 UAA00922; Thu, 26 Jun 1997 20:24:09 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.7.5/8.7.3) id XAA27235; Thu, 26 Jun 1997 23:27:04 -0400 (EDT) Date: Thu, 26 Jun 1997 23:27:04 -0400 (EDT) From: "John T. Farmer" Message-Id: <199706270327.XAA27235@sabre.goldsword.com> To: hasty@rah.star-gate.com, ludwigp@bigfoot.com Subject: Re: Advice on audio strategy needed Cc: conrads@neosoft.com, freebsd-hardware@FreeBSD.ORG, freebsd-multimedia@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, jfarmer@goldsword.com Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 26 Jun 1997 11:11:47 -0700 Ludwig Pummer said: >At 10:29 AM 6/26/97 -0700, Amancio Hasty wrote: >>Most likely he has an Intel motherboard which you can indeed disable the >>CS4232C. At any rate Sujal Patel's PnP stuff should be able also to disable >>the CS4232c however the BIOS will still reserve the CS4232c's IRQs >>which translates to wasting IRQ during the BIOS init. > >Sounds like he has the Intel Atlantis (Advanced/AS), which has the CS4232C >soundcard-on-a-chip, and an ATI mach64 video card (video card is optional) >built into the motherboard. From Intel's Atlantis FAQ >(http://developer.intel.com/design/motherbd/as/as_inst.HTM): >----- [FAQ info deleted (but it's in my files...] > >Obviously, not very friendly to non-Micro$oft systems. >--Ludwig Pummer Why am I not surprised ? :^< But it fits in with what we've always known, if a board will work with Windoze, then it's "good enough." Can you tell, I spend more time worrying about equipment that will work well under FreeBSD (& similar os's) than Win95 :^/ Sigh. Now I have the other problem. Client has 20 workstations to be upgraded from Win 3.1 & 386/486 to P-class & Win95. Now I have to find out which mainboards are solid under Win95 & don't cost an arm & a leg... Their mailserver/router will be a FreeBSD box, I know what to use there! :^> John ------------------------------------------------------------------------- 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 Fri Jun 27 00:02:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA07817 for hardware-outgoing; Fri, 27 Jun 1997 00:02:30 -0700 (PDT) Received: from mail.sns.com (jack.sns.com [199.35.183.1]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA07806; Fri, 27 Jun 1997 00:02:22 -0700 (PDT) Received: from speedy.pcscons.net by mail.sns.com with smtp (Smail3.1.28.1 #5) id m0whV2n-000Q9SC; Fri, 27 Jun 97 00:02 PDT Message-Id: <3.0.2.32.19970626235812.007c1100@mail.sns.com> X-Sender: ludwigp@mail.sns.com X-Mailer: QUALCOMM Windows Eudora Pro Version 3.0.2 (32) Date: Thu, 26 Jun 1997 23:58:12 -0700 To: "John T. Farmer" , hasty@rah.star-gate.com From: Ludwig Pummer Subject: Re: Advice on audio strategy needed Cc: conrads@neosoft.com, freebsd-hardware@FreeBSD.ORG, freebsd-multimedia@FreeBSD.ORG, freebsd-questions@FreeBSD.ORG, jfarmer@goldsword.com In-Reply-To: <199706270327.XAA27235@sabre.goldsword.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk At 11:27 PM 6/26/97 -0400, John T. Farmer wrote: >Sigh. Now I have the other problem. Client has 20 workstations to >be upgraded from Win 3.1 & 386/486 to P-class & Win95. Now I have to >find out which mainboards are solid under Win95 & don't cost an arm & >a leg... Their mailserver/router will be a FreeBSD box, I know what to >use there! :^> > >John > >------------------------------------------------------------------------- >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 I work in a computer store (laitron.home.ml.org or www.laitrons.com) and have found Asus motherboards (www.asus.com) to be very reliable (i'm a technician, not a salesman, btw). The Asus VX97 can be had for $95 (San Francisco Bay Area prices; i don't know about Tennessee). If the VX board isn't good (or fast) enough, the basic TX97 board is $155. There are also models of the TX which have a SoundBlaster 16, more DIMM sockets, ATX form factor, or ATI Rage II video). There's also the classic $135 XP55 T2P4 board (HX chipset) which isn't the latest, but is still a good value. Of the boards we sell (Microstar, SuperMicro, Asus, an Iwill or two, Intel, FIC), Asus boards give us the least trouble. Sadly, the TX97 is so new that you need to install all of the motherboard drivers from the CDROM in order to get Win95's plug-and-pray working properly. --Ludwig Pummer ------------------------------------------------------------------ ludwigp@bigfoot.com ICQ UIN: 692441 http://chipweb.home.ml.org PGP Key & Geek Code available on web page ^-- Updated 04/18/97 "If God had intended Man to Smoke, He would have set him on Fire." From owner-freebsd-hardware Fri Jun 27 00:57:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id AAA09999 for hardware-outgoing; Fri, 27 Jun 1997 00:57:57 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id AAA09992 for ; Fri, 27 Jun 1997 00:57:54 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-1.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA07479 (5.67b/IDA-1.5 for ); Fri, 27 Jun 1997 09:57:49 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id JAA10693; Fri, 27 Jun 1997 09:57:52 +0200 (CEST) X-Face: " Date: Fri, 27 Jun 1997 09:57:50 +0200 From: Stefan Esser To: Jon Inouye Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: IRQ assignment for PII motherboards References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: ; from Jon Inouye on Thu, Jun 26, 1997 at 12:16:02PM -0700 Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jun 26, Jon Inouye wrote: > We just received two machines using Pentium II motherboards > (Intel PD440FX) with AMI BIOS 1.00.04.DT0. The problem is the > BIOS configures the PCI SCSI and Ethernet devices to share the > same IRQ. While WindowsNT device drivers appear to have no problem > with this (IRQ sharing is part of the PCI spec), some Linux and FreeBSD > drivers do. There are some free IRQs, but the BIOS assignment appears > to be non-user-configurable. I've looked for a SCU (System Configuration > Utility) program for this motherboard on the Intel developers web > site without success. Moving boards around and disabling the COM, USB, > and LPT devices didn't help either. Hi Jon! I'm the maintainer of the FreeBSD PCI code, and that PCI interrupt sharing doesn't work for all cards is (bad) news to me ... Could you please be more specific, and send a VERBOSE boot log (i.e. enter "-v" at the "Boot: " prompt) ? You didn't even give information on the FreeBSD version you are trying to install ... I'll either give further directions (or fix any bug in the code, if there really is one) in order to get you going ... > The current solution is removing the SCSI controller and going with > an IDE disk. I'd appreciate any other suggestions or pointers to > a SCU program I can use! This is obviously inacceptable ... But we will do better than that :) Regards, STefan From owner-freebsd-hardware Fri Jun 27 02:42:16 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA13832 for hardware-outgoing; Fri, 27 Jun 1997 02:42:16 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id CAA13824 for ; Fri, 27 Jun 1997 02:42:12 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-6.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA11228 (5.67b/IDA-1.5 for ); Fri, 27 Jun 1997 11:41:54 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id LAA11044; Fri, 27 Jun 1997 11:40:22 +0200 (CEST) X-Face: " Date: Fri, 27 Jun 1997 11:40:22 +0200 From: Stefan Esser To: dg@root.com Cc: Jon Inouye , "Jordan K. Hubbard" , freebsd-hardware@FreeBSD.ORG Subject: Re: IRQ assignment for PII motherboards References: <199706270107.SAA10980@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199706270107.SAA10980@implode.root.com>; from David Greenman on Thu, Jun 26, 1997 at 06:07:09PM -0700 Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jun 26, David Greenman wrote: > I was able to get the Pro/100B, in a system with a pair of ahc3940's, to > get assigned to a non-shared interrupt by playing around with which slots > the cards were plugged into. It took about 3 tries to find the right order > (including leaving a slot empty), but I finally found an arrangement that > worked. My understanding is that the shared irq assignment isn't a function > of the BIOS, but rather a function of the slot the card is in and how it > is wired compared to the others. The motherboard I did this in wasn't made > by Intel, but the same principles should still apply. Interrupts should not be shared, unless at least one PCI card in the system either: 1) contains a PCI to PCI bridge, or 2) contains a multi-function PCI chip. The PCI spec requires all other cards to only use PCI IntA, if an interrupt line is required at all, and I know of no current 4 slot PCI motherboard, that can't assign a unique IRQ to the PCI IntA pin of each slot. As has been discussed before, the IntA pin of each slot is wired to IntB of its one neighbor, and IntD of the other one. (Or, perhaps easier to understand: IntB of the slot is wired to IntA of its one neighbor and IntC of its other neighbor.) This is repeated for all slots, and thus a safe way to force use of shared interrupts is to place any PCI card between two AH3940 cards :) Int A B C D Slot 1 o o o o- to IntA of slot 4 / / / / Slot 2 o o o o- to IntA of slot 1 / / / / Slot 3 o o o o- to IntA of slot 2 / / / / Slot 4 o o o o- to IntA of slot 3 / (from IntD of Slot 4) As also has been discussed before, there are no INTR_FAST support in the current PCI code (the flag has just not been passed down to the low level code, and nobody ever bothered to make PCI interrupt handlers conform to the very strict requirements of a fast interrupt handler ...). This means, that PCI interrupts may introduce higher latencies than highly optimized interrupt handlers for some ISA devices. This can be fixed (and the PCI interrupt registration code in -current allows to specify the INTR_FAST flag), but there will be some additional work required to make this work for the shared+fast case ... Regards, STefan From owner-freebsd-hardware Fri Jun 27 02:58:48 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id CAA14299 for hardware-outgoing; Fri, 27 Jun 1997 02:58:48 -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 CAA14293; Fri, 27 Jun 1997 02:58:42 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with SMTP id CAA15026; Fri, 27 Jun 1997 02:59:46 -0700 (PDT) Message-Id: <199706270959.CAA15026@implode.root.com> X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol To: Stefan Esser cc: Jon Inouye , freebsd-hardware@freebsd.org Subject: Re: IRQ assignment for PII motherboards In-reply-to: Your message of "Fri, 27 Jun 1997 11:40:22 +0200." <19970627114022.32725@mi.uni-koeln.de> From: David Greenman Reply-To: dg@root.com Date: Fri, 27 Jun 1997 02:59:46 -0700 Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >On Jun 26, David Greenman wrote: >> I was able to get the Pro/100B, in a system with a pair of ahc3940's, to >> get assigned to a non-shared interrupt by playing around with which slots >> the cards were plugged into. It took about 3 tries to find the right order >> (including leaving a slot empty), but I finally found an arrangement that >> worked. My understanding is that the shared irq assignment isn't a function >> of the BIOS, but rather a function of the slot the card is in and how it >> is wired compared to the others. The motherboard I did this in wasn't made >> by Intel, but the same principles should still apply. > >Interrupts should not be shared, unless at least one PCI card >in the system either: > >1) contains a PCI to PCI bridge, or >2) contains a multi-function PCI chip. Yes, the aha3940's are dual-channel SCSI adapters and have a bridge chip on each card to connect the two SCSI chips. This seems to make the determination of which interrupts will be shared on how they are shared very difficult or impossible. Is there a scheme to the sharing when bridge chips are involved? -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hardware Fri Jun 27 04:07:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id EAA16408 for hardware-outgoing; Fri, 27 Jun 1997 04:07:21 -0700 (PDT) Received: from Sisyphos.MI.Uni-Koeln.DE (Sisyphos.MI.Uni-Koeln.DE [134.95.212.10]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id EAA16401 for ; Fri, 27 Jun 1997 04:07:18 -0700 (PDT) Received: from x14.mi.uni-koeln.de (annexr3-15.slip.Uni-Koeln.DE) by Sisyphos.MI.Uni-Koeln.DE with SMTP id AA13027 (5.67b/IDA-1.5 for ); Fri, 27 Jun 1997 13:07:13 +0200 Received: (from se@localhost) by x14.mi.uni-koeln.de (8.8.5/8.6.9) id NAA11380; Fri, 27 Jun 1997 13:07:13 +0200 (CEST) X-Face: " Date: Fri, 27 Jun 1997 13:07:12 +0200 From: Stefan Esser To: dg@root.com Cc: Jon Inouye , freebsd-hardware@FreeBSD.ORG Subject: Re: IRQ assignment for PII motherboards References: <19970627114022.32725@mi.uni-koeln.de> <199706270959.CAA15026@implode.root.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.74 In-Reply-To: <199706270959.CAA15026@implode.root.com>; from David Greenman on Fri, Jun 27, 1997 at 02:59:46AM -0700 Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Jun 27, David Greenman wrote: > >On Jun 26, David Greenman wrote: > >> I was able to get the Pro/100B, in a system with a pair of ahc3940's, to > >> get assigned to a non-shared interrupt by playing around with which slots > >> the cards were plugged into. It took about 3 tries to find the right order > >> (including leaving a slot empty), but I finally found an arrangement that > >> worked. My understanding is that the shared irq assignment isn't a function > >> of the BIOS, but rather a function of the slot the card is in and how it > >> is wired compared to the others. The motherboard I did this in wasn't made > >> by Intel, but the same principles should still apply. > > > >Interrupts should not be shared, unless at least one PCI card > >in the system either: > > > >1) contains a PCI to PCI bridge, or > >2) contains a multi-function PCI chip. > > Yes, the aha3940's are dual-channel SCSI adapters and have a bridge chip on > each card to connect the two SCSI chips. This seems to make the determination > of which interrupts will be shared on how they are shared very difficult or > impossible. Is there a scheme to the sharing when bridge chips are involved? Yes, sure! While the PCI BIOS knows about the wires on the motherboards (or should at least :), but can't possibly determine how the secondary bridge interrupt lines are routed to the primary side, except if there is a strict and unique rule. Well, and for that reason, this rule was introduced in rev. 2.0 of the PCI specification: Primary | Secondary IntA Sec IntB Sec IntC Sec IntD ------------------------------------------------------------------------------- IntA | Slot 0,4,8,... Slot 3,7,... Slot 2,6,... Slot 1,5,... IntB | Slot 1,5,9,... Slot 0,4,... Slot 3,7,... Slot 2,6,... IntC | Slot 2,6,10,... Slot 1,5,... Slot 0,4,... Slot 3,7,... IntD | Slot 3,7,11,... Slot 2,6,... Slot 1,5,... Slot 0,4,... I.e. for slot 0,4,8,... the PCI interrupt pins go straight through to the primary bus. IntA of slot 1,5,9,... goes to IntB on the primary side, and the rest follows if you assume circular boundaries :) A multi-function device uses IntA for function 0 and 4, IntB for function 1 and 5, and so on, and is thus identical to a PCI to PCI bridge with single function devices (which all use IntA) on slots corresponding to the function number on the secondary side. Or, viewed another way: If you assign a 0 to IntA, ... 3 to IntD, then you can just sum up modulo 4 all the secondary bus numbers, the function number and interrupt pin, and you will get the associated interrupt pin on the primary bus for some device behind an arbitrary number of PCI to PCI bridges. Again: This is required by the PCI spec., and it is the *only* way a PCI BIOS can initialize PCI interrupt routing for devices behind PCI to PCI bridges. And for this reason, card vendors tend to follow these rules! (If some card does not, it should be considered broken. The device driver may use PCI BIOS services AND its knowledge of the actual wiring to fix the interrupt routing, but I don't want to even consider adding code for that aberration :) Regards, STefan From owner-freebsd-hardware Fri Jun 27 10:59:19 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA04446 for hardware-outgoing; Fri, 27 Jun 1997 10:59:19 -0700 (PDT) Received: from cyberus.ca (root@mail.cyberus.ca [207.216.2.5]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA04441 for ; Fri, 27 Jun 1997 10:59:16 -0700 (PDT) Received: from cybernext.cyberus.ca (cybernext [207.216.2.254]) by cyberus.ca (8.8.5/Cyberus Online Inc) with SMTP id NAA02717 for ; Fri, 27 Jun 1997 13:57:41 -0400 (EDT) Received: by cybernext.cyberus.ca (NX5.67e/NX3.0S) id AA25999; Fri, 27 Jun 97 13:56:23 -0400 Message-Id: <9706271756.AA25999@cybernext.cyberus.ca> Content-Type: text/plain Mime-Version: 1.0 (NeXT Mail 3.3 v118.2) Received: by NeXT.Mailer (1.118.2) From: Wayne MacLaurin Date: Fri, 27 Jun 97 13:56:22 -0400 To: freebsd-hardware@freebsd.org Subject: RNS 2340 Quad Fast Ethernet Reply-To: waynem@cyberus.ca Sender: owner-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi... I'm hoping somebody has already figured this out. We are running a FreeBSD 2.2.1 box with a couple RNS 2340 Quad Fast Ethernet cards. These cards are DEC 21140 based and the system finds them no problem as standard "de" interfaces. However, we are unable to get them to work as 100baseTX cards. Issuing an "ifconfig -link2" drops the cards into 10baseT mode and they work just fine. Anybody got any ideas ? --- Wayne MacLaurin Cyberus Online Inc. waynem@cyberus.ca From owner-freebsd-hardware Fri Jun 27 12:28:51 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id MAA10053 for hardware-outgoing; Fri, 27 Jun 1997 12:28:51 -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 MAA10039 for ; Fri, 27 Jun 1997 12:28:41 -0700 (PDT) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.7.5/8.7.3) id OAA28641; Fri, 27 Jun 1997 14:54:48 -0400 (EDT) Date: Fri, 27 Jun 1997 14:54:48 -0400 (EDT) From: "John T. Farmer" Message-Id: <199706271854.OAA28641@sabre.goldsword.com> To: hasty@rah.star-gate.com, jfarmer@sabre.goldsword.com, ludwigp@bigfoot.com Subject: Motherboard choices [WAS: Re: Advice on audio strategy needed] Cc: conrads@neosoft.com, freebsd-hardware@FreeBSD.ORG Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Thu, 26 Jun 1997 23:58:12 -0700 Ludwig Pummer said: >At 11:27 PM 6/26/97 -0400, John T. Farmer wrote: >>Sigh. Now I have the other problem. Client has 20 workstations to >>be upgraded from Win 3.1 & 386/486 to P-class & Win95. Now I have to >>find out which mainboards are solid under Win95 & don't cost an arm & >>a leg... Their mailserver/router will be a FreeBSD box, I know what to >>use there! :^> >> >I work in a computer store (laitron.home.ml.org or www.laitrons.com) and >have found Asus motherboards (www.asus.com) to be very reliable (i'm a >technician, not a salesman, btw). The Asus VX97 can be had for $95 (San >Francisco Bay Area prices; i don't know about Tennessee). If the VX board >isn't good (or fast) enough, the basic TX97 board is $155. There are also >models of the TX which have a SoundBlaster 16, more DIMM sockets, ATX form >factor, or ATI Rage II video). There's also the classic $135 XP55 T2P4 >board (HX chipset) which isn't the latest, but is still a good value. Of >the boards we sell (Microstar, SuperMicro, Asus, an Iwill or two, Intel, >FIC), Asus boards give us the least trouble. Sadly, the TX97 is so new that >you need to install all of the motherboard drivers from the CDROM in order >to get Win95's plug-and-pray working properly. Yeah, I messed around with some cheap no-name boards for a couple of projects until I realized that I'd lost any "savings" in downtime... I replaced them with ASUS P55 T2P4's & never had another problem. Right now, that's what I'm recommending for low-cost servers (the T2P4). It works with all of the Intel chips (haven't tried it with MMX ones yet.), all the AMD K5-series chips, and the Cyrix 686 chips. I'm staying away from the new "chip carrier" design until the dust clears (My understanding is that Pentium II cartridge _will_not_ be the same used for future cpus). For the Win95 machines, I think that the VX97 (as you suggested) will be the best choice. John ------------------------------------------------------------------------- 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 Fri Jun 27 18:24:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id SAA26560 for hardware-outgoing; Fri, 27 Jun 1997 18:24:22 -0700 (PDT) Received: from lightning.tbe.net (qmailr@lightning.tbe.net [208.208.122.5]) by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA26551 for ; Fri, 27 Jun 1997 18:24:17 -0700 (PDT) Received: (qmail 11416 invoked by uid 1010); 28 Jun 1997 01:19:35 -0000 Date: Fri, 27 Jun 1997 21:19:35 -0400 (EDT) From: "Gary D. Margiotta" To: "John T. Farmer" cc: hasty@rah.star-gate.com, ludwigp@bigfoot.com, conrads@neosoft.com, freebsd-hardware@FreeBSD.ORG Subject: Re: Motherboard choices [WAS: Re: Advice on audio strategy needed] In-Reply-To: <199706271854.OAA28641@sabre.goldsword.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > Right now, that's what I'm recommending for low-cost servers (the T2P4). > It works with all of the Intel chips (haven't tried it with MMX ones > yet.), all the AMD K5-series chips, and the Cyrix 686 chips. We had a problem with the Cyrix 6x86-166+ on an Asus T2P4 board a couple months back, but that is the only problem we have ever had with an Asus board. My partner has two boards, one Intel-200 (no MMX) and one P-100, and has had absolutely no problems with them. On my machine and in one of our servers we have Gigabyte boards. I have the HX set, and it appears that was the most stable one. I am definately buying more for our servers and any other machines we build. The extra $20-$30 you spend on the 'name' boards is definately worth it...we have a machie with a no-name board in it and it just up and reboots every once in a while, and that has a VX set on it. We are going to replace that one as soon as possible. > > For the Win95 machines, I think that the VX97 (as you suggested) will > be the best choice. > We had problems with earlier VX chipsets, and by now they should be better, though my personal choice would be to stick with the HX set just because of past experiences, though the new TX boards are supposed to be good. If you want some benchmarks, take a look at the following page: http://www.esc-ca.com/notbenmb.htm Good luck! -Gary Margiotta TBE Internet Services http://www.tbe.net