From owner-freebsd-hardware Sun Nov 9 09:13:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA23069 for hardware-outgoing; Sun, 9 Nov 1997 09:13:05 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from netjava.com (Espresso.NetJava.net [204.253.66.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA23064 for ; Sun, 9 Nov 1997 09:13:02 -0800 (PST) (envelope-from jayb@netjava.com) Received: from NJ042.NETJAVA.NET (NJ042.NETJAVA.NET [204.253.66.42]) by netjava.com (NTMail 3.02.13) with ESMTP id la234193 for ; Sun, 9 Nov 1997 11:25:44 -0600 Message-ID: <3465EF89.41C67EA6@netjava.com> Date: Sun, 09 Nov 1997 11:14:49 -0600 From: Jay Bratcher X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2.2-RELEASE i386) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: UMC chipset and second IDE? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk I seem to be having a problem getting FreeBSD to recognize my second IDE interface. The PCI probe finds the second interface, but it is apparently not at 0x170. The chipset is UMC 8670F (label on chip). Has anyone had any experience with this? Attached is the relevent portions of the startup messages. Thanks, Jay jayb@netjava.com From owner-freebsd-hardware Sun Nov 9 09:41:50 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA24345 for hardware-outgoing; Sun, 9 Nov 1997 09:41:50 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from netjava.com (Espresso.NetJava.net [204.253.66.2]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA24340 for ; Sun, 9 Nov 1997 09:41:46 -0800 (PST) (envelope-from jayb@netjava.com) Received: from NJ042.NETJAVA.NET (NJ042.NETJAVA.NET [204.253.66.42]) by netjava.com (NTMail 3.02.13) with ESMTP id qa234198 for ; Sun, 9 Nov 1997 11:54:40 -0600 Message-ID: <3465F651.167EB0E7@netjava.com> Date: Sun, 09 Nov 1997 11:43:45 -0600 From: Jay Bratcher X-Mailer: Mozilla 3.01Gold (X11; I; FreeBSD 2.2.2-RELEASE i386) MIME-Version: 1.0 To: freebsd-hardware@freebsd.org Subject: Re: UMC chipset and second IDE? References: <3465EF89.41C67EA6@netjava.com> Content-Type: multipart/mixed; boundary="------------794BDF32446B9B3D2781E494" Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk This is a multi-part message in MIME format. --------------794BDF32446B9B3D2781E494 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Oops - here is the attachment that should have gone with the original message. --------------794BDF32446B9B3D2781E494 Content-Type: text/plain; charset=us-ascii; name="dms" Content-Transfer-Encoding: 7bit Content-Disposition: inline; filename="dms" Probing for devices on PCI bus 0: ... chip0 rev 4 on pci0:16 chip1 rev 14 on pci0:18:0 pci0:18:1: UMC, device=0x673a, class=storage (ide) [no driver assigned] ... wdc0 at 0x1f0-0x1f7 irq 14 on isa wdc0: unit 0 (wd0): wd0: 812MB (1664208 sectors), 1651 cyls, 16 heads, 63 S/T, 512 B/S wdc1 not found at 0x170 --------------794BDF32446B9B3D2781E494-- From owner-freebsd-hardware Sun Nov 9 17:35:12 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id RAA21590 for hardware-outgoing; Sun, 9 Nov 1997 17:35:12 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from thunder. (thunder.uni.net.hk [202.71.252.171]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id RAA21578 for ; Sun, 9 Nov 1997 17:35:07 -0800 (PST) (envelope-from kelvin@uni.net.hk) Received: from uni.net.hk by thunder. (SMI-8.6/SMI-SVR4) id JAA10624; Mon, 10 Nov 1997 09:32:15 +0800 Message-ID: <3466652B.7F715993@uni.net.hk> Date: Mon, 10 Nov 1997 09:36:43 +0800 From: Kelvin X-Mailer: Mozilla 4.03 [en] (WinNT; I) MIME-Version: 1.0 To: hardware@freebsd.org Subject: PCMCIA card support list Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Dear Sir/Madam, I've the Xircom PCMCIA card, which I found not supported by freeBSD. Can I have the list of PCMCIA cards that are supported by FreeBSD? Thanks a lot. Regards, Kelvin. From owner-freebsd-hardware Sun Nov 9 18:14:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA24034 for hardware-outgoing; Sun, 9 Nov 1997 18:14:00 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA24025 for ; Sun, 9 Nov 1997 18:13:54 -0800 (PST) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id TAA12939; Sun, 9 Nov 1997 19:13:50 -0700 (MST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id TAA07141; Sun, 9 Nov 1997 19:13:49 -0700 (MST) Date: Sun, 9 Nov 1997 19:13:49 -0700 (MST) Message-Id: <199711100213.TAA07141@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: Kelvin Cc: hardware@freebsd.org Subject: Re: PCMCIA card support list In-Reply-To: <3466652B.7F715993@uni.net.hk> References: <3466652B.7F715993@uni.net.hk> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > I've the Xircom PCMCIA card, which I found not supported by freeBSD. Can > I have the list of PCMCIA cards that are supported by FreeBSD? Thanks a > lot. Look in /usr/src/etc/pccard.conf.sample, or /etc/pccard.conf.sample. Nate From owner-freebsd-hardware Sun Nov 9 23:38:45 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA10649 for hardware-outgoing; Sun, 9 Nov 1997 23:38:45 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from spokane.vmunix.com (mmayo.neon.sentex.ca [207.245.212.243]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA10643 for ; Sun, 9 Nov 1997 23:38:32 -0800 (PST) (envelope-from mark@spokane.vmunix.com) Received: (from mark@localhost) by spokane.vmunix.com (8.8.7/8.8.7) id CAA02469; Mon, 10 Nov 1997 02:39:56 -0500 (EST) Message-ID: <19971110023955.15338@vmunix.com> Date: Mon, 10 Nov 1997 02:39:55 -0500 From: Mark Mayo To: freebsd-hardware@freebsd.org Subject: Diamond FirePort 40 Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.85e X-Operating-System: FreeBSD 2.2-STABLE i386 Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Has anyone tried the Diamond FirePort 40 or FirePort 40 Dual SCSI controllers yet? How are they? It appears to just be a NCR 53c875 controller, but their benchmarks are putting it ahead of the Adaptec 2940/3940UW. I'm not sure how good the 875 is versus the 810, but I know from my own testing that the 2940U kicks the NCR 810 around the block... On my home system, I was getting about 4MB/s read and write out of a Quantum Fireball UltraSCSI drive with the 53c810. When I plugged the same drive into an old 2940U my throughput jumped to 5.5 MB/s on writes, and 6.1MB/s on read.. I used iozone with a gigantic file (with 512 and 8192 bytes blocks - same effect). I'm in the marketplace for a new SCSI controller for a server system I'm building, and I'd love to go with the 875 based Diamond FirePort - the price is right. I guess I'm wondering why the 810 performs so crappily under FreeBSD, and if I can expect the same crappy performance from the 875 under FreeBSD? Is the ahc driver really that much better?? TIA, -Mark -- ------------------------------------------------------------------------ Mark Mayo mark@vmunix.com RingZero Comp. http://www.vmunix.com/mark finger mark@vmunix.com for my PGP key and GCS code ------------------------------------------------------------------------ Win95/NT - 32 bit extensions and a graphical shell for a 16 bit patch to an an 8 bit operating system originally coded for a 4 bit microprocessor, written by a 2 bit company that can't stand 1 bit of competition. -UGU From owner-freebsd-hardware Mon Nov 10 06:46:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id GAA03936 for hardware-outgoing; Mon, 10 Nov 1997 06:46:29 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from mongkok.hk.super.net (mongkok.hk.super.net [202.14.67.46]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id GAA03924 for ; Mon, 10 Nov 1997 06:45:57 -0800 (PST) (envelope-from eh@fore.com.hk) Received: from hk.super.net (root@hk.super.net [202.14.67.4]) by mongkok.hk.super.net (8.8.5/8.8.5) with ESMTP id WAA29965; Mon, 10 Nov 1997 22:45:51 +0800 (HKT) Received: from is3.hk.super.net (eh@is3.hk.super.net [202.14.67.36]) by hk.super.net (8.8.7/8.8.5) with SMTP id WAA29799; Mon, 10 Nov 1997 22:45:46 +0800 (HKT) Date: Mon, 10 Nov 1997 22:45:45 +0800 (HKT) From: Eric Ho To: Kelvin cc: hardware@freebsd.org Subject: Re: PCMCIA card support list In-Reply-To: <3466652B.7F715993@uni.net.hk> 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 Hi, Kelvin: 3c589b works fine. eh On Mon, 10 Nov 1997, Kelvin wrote: > Dear Sir/Madam, > > I've the Xircom PCMCIA card, which I found not supported by freeBSD. Can > I have the list of PCMCIA cards that are supported by FreeBSD? Thanks a > lot. > > Regards, > Kelvin. > > > From owner-freebsd-hardware Mon Nov 10 09:30:30 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA13204 for hardware-outgoing; Mon, 10 Nov 1997 09:30:30 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from grayling.erg.sri.com (grayling.erg.sri.com [128.18.4.194]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id JAA13195 for ; Mon, 10 Nov 1997 09:30:26 -0800 (PST) (envelope-from templin@erg.sri.com) Received: from grayling.erg.sri.com by grayling.erg.sri.com (8.6.12/2.7davy) id JAA23650; Mon, 10 Nov 1997 09:25:23 -0800 Message-Id: <199711101725.JAA23650@grayling.erg.sri.com> X-Mailer: exmh version 2.0delta 6/3/97 To: Kelvin , hardware@FreeBSD.ORG cc: templin@erg.sri.com Subject: Re: PCMCIA card support list In-reply-to: Your message of "Mon, 10 Nov 1997 09:36:43 +0800." <3466652B.7F715993@uni.net.hk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Mon, 10 Nov 1997 09:25:23 -0800 From: "Fred L. Templin" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Kelvin, Are you talking about the Xircom Ethernet cards, or wireless (radio frequency) networking cards? I'm certain the Ethernet cards are supported, but perhaps others can give more specific details. As to the wireless networing cards, Xircom has split this business off to a new company called NetWave who still makes these cards. As of this writing, there is no FreeBSD driver which supports the Xircom/NetWave wireless cards, but I'm currently 50% finished coding one up and plan to submit the finished product to the FreeBSD community when it's ready. Stay tuned... Fred templin@erg.sri.com P.S. Look on the PAO homepage at: http://www.makefile.org/FreeBSD/PAO/ for an extensive list of supported devices. With few exceptions, the devices supported under PAO are also supported under the vanilla FreeBSD distribution. From owner-freebsd-hardware Mon Nov 10 09:46:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA14426 for hardware-outgoing; Mon, 10 Nov 1997 09:46:00 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from ha1.rdc1.nj.home.com (siteadm@ha1.rdc1.nj.home.com [24.3.128.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA14411 for ; Mon, 10 Nov 1997 09:45:50 -0800 (PST) (envelope-from luomat@luomat.peak.org) Received: from luomat.peak.org ([24.2.83.40]) by ha1.rdc1.nj.home.com (Netscape Mail Server v2.02) with ESMTP id AAA3400 for ; Mon, 10 Nov 1997 09:45:43 -0800 Received: (from luomat@localhost) by luomat.peak.org (8.8.7/8.8.7) id MAA04350 for freebsd-hardware@FreeBSD.ORG; Mon, 10 Nov 1997 12:45:43 -0500 (EST) Message-Id: <199711101745.MAA04350@luomat.peak.org> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) X-Image-URL: http://www.peak.org/~luomat/next/luomat@peak.org.tiff X-Nextstep-Mailer: Mail 4.2mach (Enhance 2.0b6.3) Received: by NeXT.Mailer (1.148.RR) From: Timothy J Luoma Date: Mon, 10 Nov 97 12:45:34 -0500 To: freebsd-hardware@FreeBSD.ORG Subject: Matrox Millenium supported? (and a couple of other newbie questions) X-Image-URL-Disclaimer: hey, it's off my student ID, gimme a break ;-) Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Hi all! Been lurking for a little while, and checking out the webpages. I think all of my hardware is ok, except I haven't seen anything about the Matrox Millenium (4meg). I did see something about another Matrox card, but not that one. I just found out that I am getting a new 2nd hand drive (Seagate ST31230N, 1 gig) and figured I might as well try an installation tonight! I was expecting to lurk longer, but fate seems to be pushing me ahead. Here's my hardware, in case anyone cares to confirm or deny any potential problems (actually, I have some questions here too!): Motherboard: Tyan Tomcat III P5 Processor: P-133 (``classic'') Sound Card: SoundBlaster16 at dma channel 1 irq 5 Ethernet card: Intel EtherExpress PRO/10+ ISA at port 0x300 irq 10 Pointing Dev: PS/2 Logitech MarbleMan Trackball (will this work??) CD-ROM: Sony CDU76s (4x) Controller: Adaptec 2940 Host Adapter found at Bus 0 Device 19 Weirdness: The Ethernet card listed above is actually the second Ethernet card (ie en1 not en0). Yes, I have 2 Ethernet cards. One is en0 which connects my old computer (without a real address) to my new computer (which has a real address). The second one is en1 which connects my new computer to the Internet via a cable modem (I was planning a net-install of FreeBSD) I am a PC-hardware weenie, and know nothing about IRQs and DMAs and all that other stuff (this machine was put together for me) Here is the current DMA and IRQ listings: ISASerialPort1: Base=0x02f8, IRQ=3, Type=16550AF/C/CF, FIFO=16 ISASerialPort0: Base=0x03f8, IRQ=4, Type=16550AF/C/CF, FIFO=16 SoundBlaster16 at dma channel 1 irq 5 DECchip21040 based adapter at port 0x6000 irq 9 Intel EtherExpress PRO/10+ ISA at port 0x300 irq 10 Final note: the machine is 100% SCSI, no (E)?IDE anywhere. Thanks for your time and help, TjL From owner-freebsd-hardware Mon Nov 10 10:29:57 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA17743 for hardware-outgoing; Mon, 10 Nov 1997 10:29:57 -0800 (PST) (envelope-from owner-freebsd-hardware) 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 KAA17718 for ; Mon, 10 Nov 1997 10:29:52 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xUyTw-0001DU-00; Mon, 10 Nov 1997 10:22:40 -0800 Date: Mon, 10 Nov 1997 10:22:27 -0800 (PST) From: Tom To: Mark Mayo cc: freebsd-hardware@freebsd.org Subject: Re: Diamond FirePort 40 In-Reply-To: <19971110023955.15338@vmunix.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, 10 Nov 1997, Mark Mayo wrote: > Has anyone tried the Diamond FirePort 40 or FirePort 40 Dual > SCSI controllers yet? How are they? They work, but I'm not sure if the driver turns Ultra on yet. > It appears to just be a NCR 53c875 controller, but their benchmarks > are putting it ahead of the Adaptec 2940/3940UW. I'm not sure > how good the 875 is versus the 810, but I know from my own testing > that the 2940U kicks the NCR 810 around the block... The 810 is a Fast controller, and the 2940U and Ultra controller. > On my home system, I was getting about 4MB/s read and write out of > a Quantum Fireball UltraSCSI drive with the 53c810. When I > plugged the same drive into an old 2940U my throughput jumped > to 5.5 MB/s on writes, and 6.1MB/s on read.. I used iozone > with a gigantic file (with 512 and 8192 bytes blocks - same > effect). 512 and 8192 blocks are quite small. This gives a lot of command overhead, that any Ultra controller will handle better. I bet if you try 64k blocks, you will notice little difference. The Adaptec controllers process commands a bit more quickly. > I'm in the marketplace for a new SCSI controller for a server > system I'm building, and I'd love to go with the 875 based > Diamond FirePort - the price is right. I guess I'm wondering > why the 810 performs so crappily under FreeBSD, and if I can > expect the same crappy performance from the 875 under FreeBSD? > > Is the ahc driver really that much better?? It has nothing to do with the driver. It is the card. First of all you are comparing an Ultra to a Fast controller. Adaptec 2940/3940 controllers can keep outstanding commands on the card, speeding up simultaneous commands. The only time you ever notice this, if you are issuing a lot of commands. Also, the ahc driver has some reliability problems on some hardware. If your drives do funny things, the ahc driver may not be able to sort it out. See "timed out while idle" problems in archive. > TIA, > -Mark Tom From owner-freebsd-hardware Mon Nov 10 10:47:40 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA19106 for hardware-outgoing; Mon, 10 Nov 1997 10:47:40 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from srv.net (snake.srv.net [199.104.81.3]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA19096 for ; Mon, 10 Nov 1997 10:47:37 -0800 (PST) (envelope-from cmott@srv.net) Received: from darkstar.home (tc-if3-20.ida.net [208.141.171.125]) by srv.net (8.8.7/8.8.5) with SMTP id LAA03980; Mon, 10 Nov 1997 11:47:15 -0700 (MST) Date: Mon, 10 Nov 1997 11:46:42 -0700 (MST) From: Charles Mott X-Sender: cmott@darkstar.home To: Timothy J Luoma cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Matrox Millenium supported? (and a couple of other newbie questions) In-Reply-To: <199711101745.MAA04350@luomat.peak.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk On Mon, 10 Nov 1997, Timothy J Luoma wrote: > Motherboard: Tyan Tomcat III P5 > Processor: P-133 (``classic'') > Sound Card: SoundBlaster16 at dma channel 1 irq 5 > Ethernet card: Intel EtherExpress PRO/10+ ISA at port 0x300 irq 10 > Pointing Dev: PS/2 Logitech MarbleMan Trackball (will this work??) > CD-ROM: Sony CDU76s (4x) > Controller: Adaptec 2940 Host Adapter found at Bus 0 Device 19 > > Weirdness: The Ethernet card listed above is actually the second Ethernet > card (ie en1 not en0). > > Yes, I have 2 Ethernet cards. One is en0 which connects my old computer > (without a real address) to my new computer (which has a real address). The > second one is en1 which connects my new computer to the Internet via a cable > modem (I was planning a net-install of FreeBSD) Has your cable company given you a fixed IP address? I have heard some cable modems work with DHCP. I haven't done a net install of FreeBSD, but I think you need a fixed IP address. In practice, the DHCP addresses don't change for weeks or months I have heard, but you still need to know what the address is. If you are in the States and this is your first FreeBSD installation, a cd-rom makes things a lot easier. They used to even ship a book by Greg Lehey with the cd giving alot of useful install information, but I don't know if this is the case anymore. Charles Mott From owner-freebsd-hardware Mon Nov 10 10:53:34 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA19720 for hardware-outgoing; Mon, 10 Nov 1997 10:53:34 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from ha1.rdc1.nj.home.com (siteadm@ha1.rdc1.nj.home.com [24.3.128.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id KAA19715 for ; Mon, 10 Nov 1997 10:53:30 -0800 (PST) (envelope-from luomat@luomat.peak.org) Received: from luomat.peak.org ([24.2.83.40]) by ha1.rdc1.nj.home.com (Netscape Mail Server v2.02) with ESMTP id AAA17043; Mon, 10 Nov 1997 10:53:08 -0800 Received: (from luomat@localhost) by luomat.peak.org (8.8.7/8.8.7) id NAA09161; Mon, 10 Nov 1997 13:53:09 -0500 (EST) Message-Id: <199711101853.NAA09161@luomat.peak.org> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) X-Image-URL: http://www.peak.org/~luomat/next/luomat@peak.org.tiff In-Reply-To: X-Nextstep-Mailer: Mail 4.2mach (Enhance 2.0b6.3) Received: by NeXT.Mailer (1.148.RR) From: Timothy J Luoma Date: Mon, 10 Nov 97 13:53:04 -0500 To: Charles Mott Subject: Re: Matrox Millenium supported? (and a couple of other newbie questions) cc: freebsd-hardware@FreeBSD.ORG References: X-Image-URL-Disclaimer: hey, it's off my student ID, gimme a break ;-) Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Author: Charles Mott Original-Date: Mon, 10 Nov 1997 11:46:42 -0700 (MST) Message-ID: > Has your cable company given you a fixed IP address? Yes they have... I should have made that clear before. If it doesn't go well a friend of mine is getting the CDs later this week (hopefully. They are ordered at least). TjL From owner-freebsd-hardware Mon Nov 10 11:01:17 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA20446 for hardware-outgoing; Mon, 10 Nov 1997 11:01:17 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA20424 for ; Mon, 10 Nov 1997 11:01:13 -0800 (PST) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id MAA19150; Mon, 10 Nov 1997 12:00:57 -0700 (MST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA10205; Mon, 10 Nov 1997 12:00:54 -0700 (MST) Date: Mon, 10 Nov 1997 12:00:54 -0700 (MST) Message-Id: <199711101900.MAA10205@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Fred L. Templin" Cc: Kelvin , hardware@freebsd.org Subject: Re: PCMCIA card support list In-Reply-To: <199711101725.JAA23650@grayling.erg.sri.com> References: <3466652B.7F715993@uni.net.hk> <199711101725.JAA23650@grayling.erg.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Are you talking about the Xircom Ethernet cards, or wireless (radio frequency) > networking cards? I'm certain the Ethernet cards are supported Actually, no. Xircom won't give out programming information on their network cards, hence there is no driver for them. The 'modem' cards are the same as everyone else's, but we don't recommend anyone buying them due to the programming problems on everything else they make. Nate From owner-freebsd-hardware Mon Nov 10 11:34:22 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA22680 for hardware-outgoing; Mon, 10 Nov 1997 11:34:22 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from grayling.erg.sri.com (grayling.erg.sri.com [128.18.4.194]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA22667 for ; Mon, 10 Nov 1997 11:34:19 -0800 (PST) (envelope-from templin@erg.sri.com) Received: by grayling.erg.sri.com (8.6.12/2.7davy) id LAA23754; Mon, 10 Nov 1997 11:34:26 -0800 Message-Id: <199711101934.LAA23754@grayling.erg.sri.com> Date: Mon, 10 Nov 1997 11:34:26 -0800 From: "Fred L. Templin" To: nate@mt.sri.com Cc: hardware@freebsd.org, kelvin@uni.net.hk Subject: Re: PCMCIA card support list Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Nate, > Actually, no. Xircom won't give out programming information on their > network cards, hence there is no driver for them. The 'modem' cards are > the same as everyone else's, but we don't recommend anyone buying them > due to the programming problems on everything else they make. That's right - I now remember seeing the comment about FreeBSD not supporting Xircom because of their closed architecture. This brings to mind an interesting question, however: when I finish the NetWave radio driver, will the FreeBSD community even want a copy for integration into the source tree? If not, I suppose I'll have to handle release engineering on my own. I understand (and support) where the FreeBSD community is coming from on this issue, and am somewhat chagrined at being stuck with developing a public-domain driver to a proprietary interface... Fred templin@erg.sri.com From owner-freebsd-hardware Mon Nov 10 11:40:03 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA23096 for hardware-outgoing; Mon, 10 Nov 1997 11:40:03 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from ns.mt.sri.com (SRI-56K-FR.mt.net [206.127.65.42]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA23052 for ; Mon, 10 Nov 1997 11:39:58 -0800 (PST) (envelope-from nate@rocky.mt.sri.com) Received: from rocky.mt.sri.com (rocky.mt.sri.com [206.127.76.100]) by ns.mt.sri.com (8.8.7/8.8.7) with ESMTP id MAA19441; Mon, 10 Nov 1997 12:39:51 -0700 (MST) Received: (from nate@localhost) by rocky.mt.sri.com (8.7.5/8.7.3) id MAA10454; Mon, 10 Nov 1997 12:39:48 -0700 (MST) Date: Mon, 10 Nov 1997 12:39:48 -0700 (MST) Message-Id: <199711101939.MAA10454@rocky.mt.sri.com> From: Nate Williams MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Fred L. Templin" Cc: nate@mt.sri.com, hardware@freebsd.org, kelvin@uni.net.hk Subject: Re: PCMCIA card support list In-Reply-To: <199711101934.LAA23754@grayling.erg.sri.com> References: <199711101934.LAA23754@grayling.erg.sri.com> X-Mailer: VM 6.29 under 19.15 XEmacs Lucid Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > ....when I finish the NetWave radio > driver, will the FreeBSD community even want a copy for integration into > the source tree? Sure, why not? NetWave != Xircom, so if they released you to give out the driver, we're welcome to take it. (Although, having used their cards I'm less than impressed, but it may have more to do with a bad driver under Win95, so the FreeBSD stuff should work much better, right? *grin* Nate From owner-freebsd-hardware Mon Nov 10 12:58:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA28045 for hardware-outgoing; Mon, 10 Nov 1997 12:58:49 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from time.cdrom.com (root@time.cdrom.com [204.216.27.226]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA28035 for ; Mon, 10 Nov 1997 12:58:45 -0800 (PST) (envelope-from jkh@time.cdrom.com) 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 MAA16993; Mon, 10 Nov 1997 12:58:09 -0800 (PST) To: "Fred L. Templin" cc: nate@mt.sri.com, hardware@FreeBSD.ORG, kelvin@uni.net.hk Subject: Re: PCMCIA card support list In-reply-to: Your message of "Mon, 10 Nov 1997 11:34:26 PST." <199711101934.LAA23754@grayling.erg.sri.com> Date: Mon, 10 Nov 1997 12:58:09 -0800 Message-ID: <16989.879195489@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > That's right - I now remember seeing the comment about FreeBSD not > supporting Xircom because of their closed architecture. This brings to > mind an interesting question, however: when I finish the NetWave radio > driver, will the FreeBSD community even want a copy for integration into > the source tree? If not, I suppose I'll have to handle release engineering > on my own. I understand (and support) where the FreeBSD community is coming > from on this issue, and am somewhat chagrined at being stuck with developing > a public-domain driver to a proprietary interface... I don't see why we wouldn't. We wouldn't mind a completely reverse-engineered Xircom driver either (assuming that Xircom didn't have it in mind to sue anyone doing so, and I genuinely don't know whether they would or not), this not being a political issue so much as a technical one. If you've managed to write a driver for some proprietary product and there are no legal barriers to us incorporating it, I don't see a problem at all. Jordan From owner-freebsd-hardware Tue Nov 11 07:47:49 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id HAA00438 for hardware-outgoing; Tue, 11 Nov 1997 07:47:49 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from electric.tbe.net (electric.tbe.net [208.208.122.10]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id HAA00422 for ; Tue, 11 Nov 1997 07:47:41 -0800 (PST) (envelope-from gary@tbe.net) Received: (qmail 6345 invoked from network); 11 Nov 1997 15:55:47 -0000 Received: from flash.tbe.net (gary@208.208.122.15) by electric.tbe.net with SMTP; 11 Nov 1997 15:55:47 -0000 Date: Tue, 11 Nov 1997 10:45:59 -0500 (EST) From: "Gary D. Margiotta" To: FreeBSD Hardware List Subject: MB Chipset Differences 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 Hello, I have a quick question, though the answers might not be so. I am looking for some new motherboards, and I would like to clear up some fog in my head over the different chipsets the boards have. I am including what I think I know about the different chipsets, but have one nagging question which I would love an anser to above all the other things: Among the VX, TX, and HX chipsets, what does the max cacheable RAM mean? I know the VX & TX can do up to 64 MB, and the HX can do 512 MB, but what does this mean in the long run, and how does this affect server performance? VX: Good chipset for low-to-medium end machines, can cache up to 64 MB RAM, and can support both 72-pin SIMMS and 168-pin DRAM, though not always at the same time. TX: Fast chipset, good for higher-end systems, and its strongpoint is SDRAM. CAn cache up to 64 MB RAM. HX: Good for high-end servers. Supports 72-pin SIMMS, and can accept and cache up to 512 MB of RAM. FX: Used in PPro boards. Not much known about this chipset. What am I missing, where am I wrong, and what else should I know. (I know that is a lot to ask, and I apologize). I have been quite happy with the Asus, Gigabyte and Tyan boards that we have, but I would like to know a bit more before I buy another. I am partial to the HX boards, but I couldn't really explain why and have it hold up in a 'HX is better than TX is better than VX' discussion. Any insight would be greatly appreciated. ______________________________________________________________ -Gary Margiotta Voice: (973) 835-9696 TBE Internet Services Fax: (973) 256-4605 http://www.tbe.net E-Mail: gary@tbe.net From owner-freebsd-hardware Tue Nov 11 18:47:27 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA21131 for hardware-outgoing; Tue, 11 Nov 1997 18:47:27 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from MindBender.serv.net (mindbender.serv.net [205.153.153.98]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA21123 for ; Tue, 11 Nov 1997 18:47:22 -0800 (PST) (envelope-from michaelv@MindBender.serv.net) Received: from localhost.HeadCandy.com (localhost.HeadCandy.com [127.0.0.1]) by MindBender.serv.net (8.8.7/8.7.3) with SMTP id SAA07900; Tue, 11 Nov 1997 18:46:44 -0800 (PST) Message-Id: <199711120246.SAA07900@MindBender.serv.net> X-Authentication-Warning: MindBender.serv.net: localhost.HeadCandy.com [127.0.0.1] didn't use HELO protocol To: "Gary D. Margiotta" cc: FreeBSD Hardware List Subject: Re: MB Chipset Differences In-reply-to: Your message of Tue, 11 Nov 97 10:45:59 -0500. Date: Tue, 11 Nov 1997 18:46:40 -0800 From: "Michael L. VanLoon -- HeadCandy.com" Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >I have a quick question, though the answers might not be so. I am looking [...] This might be a source of interesting information for you: http://www.tomshardware.com/ ----------------------------------------------------------------------------- Michael L. VanLoon michaelv@MindBender.serv.net Contract software development for Windows NT, Windows 95 and Unix. Windows NT and Unix server development in C++ and C. --< Free your mind and your machine -- NetBSD free un*x >-- NetBSD working ports: 386+PC, Mac 68k, Amiga, Atari 68k, HP300, Sun3, Sun4/4c/4m, DEC MIPS, DEC Alpha, PC532, VAX, MVME68k, arm32... NetBSD ports in progress: PICA, others... ----------------------------------------------------------------------------- From owner-freebsd-hardware Tue Nov 11 23:06:35 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA20955 for hardware-outgoing; Tue, 11 Nov 1997 23:06:35 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from ren.dtir.qld.gov.au (firewall-user@ns.dtir.qld.gov.au [203.108.138.66]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA20939 for ; Tue, 11 Nov 1997 23:06:29 -0800 (PST) (envelope-from syssgm@dtir.qld.gov.au) Received: by ren.dtir.qld.gov.au; id RAA14701; Wed, 12 Nov 1997 17:22:12 +1000 (EST) Received: from ogre.dtir.qld.gov.au(167.123.8.3) by ren.dtir.qld.gov.au via smap (3.2) id xma014699; Wed, 12 Nov 97 17:22:09 +1000 Received: from localhost.dtir.qld.gov.au (localhost.dtir.qld.gov.au [127.0.0.1]) by ogre.dtir.qld.gov.au (8.8.7/8.8.7) with SMTP id RAA01942; Wed, 12 Nov 1997 17:04:17 +1000 (EST) Message-Id: <199711120704.RAA01942@ogre.dtir.qld.gov.au> X-Authentication-Warning: ogre.dtir.qld.gov.au: localhost.dtir.qld.gov.au [127.0.0.1] didn't use HELO protocol To: Tom , Mark Mayo cc: freebsd-hardware@freebsd.org, syssgm@dtir.qld.gov.au Subject: Re: Diamond FirePort 40 References: In-Reply-To: from Tom at "Mon, 10 Nov 1997 18:22:27 +0000" Date: Wed, 12 Nov 1997 17:04:16 +1000 From: Stephen McKay Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Monday, 10th November 1997, Tom wrote: >On Mon, 10 Nov 1997, Mark Mayo wrote: > >> Has anyone tried the Diamond FirePort 40 or FirePort 40 Dual >> SCSI controllers yet? How are they? > > They work, but I'm not sure if the driver turns Ultra on yet. I have a FirePort 40 for personal use. It works fine and runs my disk at the full manufacturer's claimed speed. 2.2.2 did not support the 53C875J chip in the FirePort 40. 2.2.5 and -current support it at full speed. The LED doesn't work under FreeBSD, so you miss out on some flashing lights. The ncrcontrol program is a selling point. I know of no equivalent for the Adaptec controllers. I've not seen the dual version, so you would have to try that yourself. If it is just 2 SCSI chips behind a PCI-PCI bridge it should work. Stephen. From owner-freebsd-hardware Tue Nov 11 23:09:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA21347 for hardware-outgoing; Tue, 11 Nov 1997 23:09:38 -0800 (PST) (envelope-from owner-freebsd-hardware) 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 XAA21330 for ; Tue, 11 Nov 1997 23:09:33 -0800 (PST) (envelope-from tom@sdf.com) Received: from tom by misery.sdf.com with smtp (Exim 1.73 #1) id 0xVWob-00023y-00; Tue, 11 Nov 1997 23:02:17 -0800 Date: Tue, 11 Nov 1997 23:02:12 -0800 (PST) From: Tom To: Stephen McKay cc: Mark Mayo , freebsd-hardware@freebsd.org Subject: Re: Diamond FirePort 40 In-Reply-To: <199711120704.RAA01942@ogre.dtir.qld.gov.au> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Wed, 12 Nov 1997, Stephen McKay wrote: > The ncrcontrol program is a selling point. I know of no equivalent for > the Adaptec controllers. Most of these functions are handled by the Adaptec BIOS control panel system, and more. It can also do low-level verifies, and formats. About the only things you can't do on the Adaptec, are the performance monitoring, and setting tag use per device. Tom From owner-freebsd-hardware Wed Nov 12 23:27:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA24370 for hardware-outgoing; Wed, 12 Nov 1997 23:27:29 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from bacchus.eng.umd.edu (bacchus.eng.umd.edu [129.2.94.5]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA24360 for ; Wed, 12 Nov 1997 23:27:25 -0800 (PST) (envelope-from crb@glue.umd.edu) Received: from [10.0.0.4] (rkv-as2s61.erols.com [207.172.239.125]) by bacchus.eng.umd.edu (8.8.7/8.8.7) with ESMTP id CAA25924; Thu, 13 Nov 1997 02:27:21 -0500 (EST) X-Sender: crb@bacchus.eng.umd.edu Message-Id: In-Reply-To: <3462A55A.4412DF3F@acsu.buffalo.edu> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Thu, 13 Nov 1997 02:27:13 -0500 To: John Gather From: "Christopher R. Bowman" Subject: Re: Tekram DC-390 Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Can anyone on this list tell me if the Tekram scsi controllers >DC-390, DC-390F and DC390U have driver support for >FreeBSD? >I don't see them listed under 'supported configurations' adapter >cards, but Tekram technical service says that there are drivers >for FreeBSD! These controllers seem to have excellent price/value >relation. Please let me know your opinion on this. Thanks, > >John Gather I paid around $150 for my DC 390F (Ultra & Wide ie 40MHz/40MBytes/sec) and it is symbios 53c875 based. Look at www.uvision.com for a pretty good price. (they are cheaper now) It Just Works (TM) under Window 95 and FreeBSD. NOTE however that if you want to take full advantage of the hardware you will have to use somthing after 2.2.2 RELEASE since that version doesn't do more than 20MBytes/sec (I hear the current does better, but I haven't personally verified it) --------- Christopher R. Bowman crb@eng.umd.edu My home page From owner-freebsd-hardware Thu Nov 13 10:59:01 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id KAA07893 for hardware-outgoing; Thu, 13 Nov 1997 10:59:01 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from skyserv.med.osd.mil (skyserv.med.osd.mil [199.209.8.144]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id KAA07870; Thu, 13 Nov 1997 10:58:55 -0800 (PST) (envelope-from rpotts@med.osd.mil) Received: from (ae1970.med.osd.mil [161.14.168.22]) by skyserv.med.osd.mil (8.6.8.1/SCA-6.6) with SMTP id NAA26834; Thu, 13 Nov 1997 13:58:41 -0500 From: "Ross Potts" Message-Id: <9711131358.ZM7559@unknown.zmail.host> Date: Thu, 13 Nov 1997 13:58:40 -0500 X-Mailer: ZM-Win (3.2.1 11Sep94) To: freebsd-hardware@FreeBSD.ORG Subject: modems Cc: freebsd-isp@FreeBSD.ORG Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Okay, I'm not a newbie. But, for the life of me, I have never had to use a modem. I've led a privileged life of working in a set environment with all the NICs I could carry. Now I want to use a modem on FreeBSD at home. Before I started leaning over to this OS, I tried Linux. Then I heard that they would not take winmodems. On my Compaq Presario, that is apparently what I have(no jumpers!). That and the stupidly easy setup in FreeBSD made me change over. I have since then bought a motorola modemsurfr-33.6(with jumpers). Wouldn't you know it... two days after I bought it, I found (in the FreeBSD Handbook?) how to change IRQ settings in userconfig. Maybe I could still use the winmodem and save the settings like described for NICs? I will keep both modems. My problem is this: I have yet to be able to get a dial tone! AARRRGghhhhh! I'm using a book for Linux, but the concept is the same in how to set the dev files! I know once I get a dial tone, setting ppp will be simple. Can anyone send some info other than reading the FAQs and handbook? -- UNIX Rules!!! Ross Potts Internet : Ross.Potts@med.osd.mil EDS-D/SIDDOMS Phone : (703) 824-7601 Skyline Two, Suite 1200 Beeper : 5203 Leesburg Pike, Falls Church, VA 22041 From owner-freebsd-hardware Thu Nov 13 11:46:38 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA12806 for hardware-outgoing; Thu, 13 Nov 1997 11:46:38 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from marlin.exis.net (root@marlin.exis.net [205.252.72.102]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id LAA12787; Thu, 13 Nov 1997 11:46:27 -0800 (PST) (envelope-from stefan@exis.net) Received: from sailfish.exis.net (sailfish.exis.net [205.252.72.104]) by marlin.exis.net (8.8.4/8.8.5) with SMTP id OAA16123; Thu, 13 Nov 1997 14:46:07 -0500 Date: Thu, 13 Nov 1997 14:37:18 -0500 (EST) From: Stefan Molnar To: Ross Potts cc: freebsd-hardware@FreeBSD.ORG, freebsd-isp@FreeBSD.ORG Subject: Re: modems In-Reply-To: <9711131358.ZM7559@unknown.zmail.host> 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 > Now I want to use a modem on FreeBSD at home. Before I started leaning over to > this OS, I tried Linux. Then I heard that they would not take winmodems. On my > Compaq Presario, that is apparently what I have(no jumpers!). That and the > stupidly easy setup in FreeBSD made me change over. It is not the lack of jumpers makes the winmodem suck, it is the lack of a UART chip. The UART chip is being emulated in software. When I worked for an isp, the winmodemds were the hardest to fix via phone support, and dies very easly. > I have since then bought a motorola modemsurfr-33.6(with jumpers). Wouldn't you > know it... two days after I bought it, I found (in the FreeBSD Handbook?) how to > change IRQ settings in userconfig. Maybe I could still use the winmodem and > save the settings like described for NICs? I will keep both modems. Take the winmodem and donate it for a tax writeoff, it is better that way. > My problem is this: I have yet to be able to get a dial tone! AARRRGghhhhh! > I'm using a book for Linux, but the concept is the same in how to set the dev > files! I know once I get a dial tone, setting ppp will be simple. I am asumeing you are not getting the dial tone on he winmodem. YOu do not have to set and dev files for serial devices like a modem, the ones are in this order. COM1 /dev/cuaa0 COM2 /dev/cuaa1 COM3 /dev/cuaa2 COM4 /dev/cuaa3 I find the best way to make sure the modem is working is use minicom. It is alot like Telix (in my opinion the best term that was ever made), and it is easy to configure. Stefan From owner-freebsd-hardware Thu Nov 13 11:48:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id LAA13045 for hardware-outgoing; Thu, 13 Nov 1997 11:48:21 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from dns (dns.ida.net [204.228.203.1]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id LAA13017 for ; Thu, 13 Nov 1997 11:48:10 -0800 (PST) (envelope-from cmott@srv.net) Received: from darkstar.home (dialin1.anlw.anl.gov [141.221.254.101]) by dns (SMI-8.6/mail.byaddr) with SMTP id MAA13567; Thu, 13 Nov 1997 12:42:39 -0700 Date: Thu, 13 Nov 1997 12:47:46 -0700 (MST) From: Charles Mott X-Sender: cmott@darkstar.home To: Ross Potts cc: freebsd-hardware@FreeBSD.ORG Subject: Re: modems In-Reply-To: <9711131358.ZM7559@unknown.zmail.host> 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, 13 Nov 1997, Ross Potts wrote: > Now I want to use a modem on FreeBSD at home. Before I started leaning over to > this OS, I tried Linux. Then I heard that they would not take winmodems. On my > Compaq Presario, that is apparently what I have(no jumpers!). That and the > stupidly easy setup in FreeBSD made me change over. If this is a US Robotics winmodem, then it is probably in a default "plug and play." If you can configure the modem to a fixed IRQ and IO base address with a DOS or Windows configuration program, then it should be pretty simple to use with FreeBSD. Charles Mott From owner-freebsd-hardware Thu Nov 13 18:06:54 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id SAA14481 for hardware-outgoing; Thu, 13 Nov 1997 18:06:54 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from anvil.BLaCKSMITH.com (blacksmith.com [207.86.5.40]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA14472 for ; Thu, 13 Nov 1997 18:06:43 -0800 (PST) (envelope-from sarah@BLaCKSMITH.com) Received: from tori.blacksmith.com (tori [192.168.8.101]) by anvil.BLaCKSMITH.com (8.8.5/8.8.5) with ESMTP id VAA29897 for ; Thu, 13 Nov 1997 21:06:31 -0500 (EST) Received: from mccullers.blacksmith.com (mccullers.BLaCKSMITH.com [192.168.8.35]) by tori.blacksmith.com (8.8.5/8.8.5) with ESMTP id VAA15419 for ; Thu, 13 Nov 1997 21:06:30 -0500 (EST) Received: (from sarah@localhost) by mccullers.blacksmith.com (8.8.5/8.8.5) id VAA02737 for freebsd-hardware@freebsd.org; Thu, 13 Nov 1997 21:06:30 -0500 (EST) Message-Id: <199711140206.VAA02737@mccullers.blacksmith.com> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) Received: by NeXT.Mailer (1.148) From: Sarah Bartlett Date: Thu, 13 Nov 97 21:06:27 -0500 To: freebsd-hardware@freebsd.org Subject: four-port ethernet card compatible with freebsd Reply-To: sarah@BLaCKSMITH.com Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk Hi, We're looking to build a firewall using freebsd and were wondering if there were any 4-port ethernet adaptors known to work under freebsd. Right now we're looking at an adaptec. We haven't decided yet which version to use and this may be the deciding factor. Thanks in advance for any input, Sarah From owner-freebsd-hardware Thu Nov 13 19:41:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id TAA20407 for hardware-outgoing; Thu, 13 Nov 1997 19:41:32 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from icicle.winternet.com (adm@icicle.winternet.com [198.174.169.13]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id TAA20400 for ; Thu, 13 Nov 1997 19:41:29 -0800 (PST) (envelope-from mestery@mail.winternet.com) Received: (from adm@localhost) by icicle.winternet.com (8.8.8/8.8.8) id VAA29673 for ; Thu, 13 Nov 1997 21:41:24 -0600 (CST) Received: from tundra.winternet.com(198.174.169.11) by icicle.winternet.com via smap (V2.0) id xma029567; Thu, 13 Nov 97 21:40:48 -0600 Received: from localhost (mestery@localhost) by tundra.winternet.com (8.8.7/8.8.4) with SMTP id VAA04233 for ; Thu, 13 Nov 1997 21:40:46 -0600 (CST) X-Authentication-Warning: tundra.winternet.com: mestery owned process doing -bs Date: Thu, 13 Nov 1997 21:40:46 -0600 (CST) From: Kyle Mestery To: freebsd-hardware@freebsd.org Subject: Is my drive bad? 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 Hi, I have the following drive exhibiting the following problems, and was wondering if the drive is bad, like I suspect. Here is the drive: wd2: 1040MB (2130912 sectors), 2114 cyls, 16 heads, 63 S/T, 512 B/S And, here is what happens when I try to mount the drive: wd2c: reverting to PIO mode writing fsbn 0 of 0-15 (wd2 bn 0; cn 0 tn 0 sn 0)wd2 : status 71 error 4 wd2c: hard error writing fsbn 0 of 0-15 (wd2 bn 0; cn 0 tn 0 sn 0)wd2: status 71 error 4 wd2c: reverting to non-multi sector mode writing fsbn 0 of 0-15 (wd2 bn 0; cn 0 tn 0 sn 0)wd2: status 71 error 4 I manage to get a couple of those, depending on what partition I try and mount. The drive was on a machine about 6 months ago running 2.2, and I am trying to mount the partitions on a 3.0 machine. Also, attempting to use /stand/sysinstall instead of doing disklabel/newfs by hand results in the errors above and sysinstall exiting. The reason I am asking if the drive is going bad is because all partitions on it pass a fsck. Any ideas? Kyle Mestery StorageTek's Network Systems Group 7600 Boone Ave. N., Minneapolis, MN 55428 mesteka@anubis.network.com, mestery@winternet.com "You do not greet Death, you punch him in the throat repeatedly until he drags you away." --No Fear From owner-freebsd-hardware Thu Nov 13 20:33:26 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id UAA22903 for hardware-outgoing; Thu, 13 Nov 1997 20:33:26 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from u3.farm.idt.net (root@u3.farm.idt.net [169.132.8.12]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id UAA22898 for ; Thu, 13 Nov 1997 20:33:24 -0800 (PST) (envelope-from garycorc@idt.net) Received: from idt.net (ppp-15.ts-1.mlb.idt.net [169.132.71.15]) by u3.farm.idt.net (8.8.8/8.8.5) with ESMTP id XAA16635; Thu, 13 Nov 1997 23:32:59 -0500 (EST) Message-ID: <346BD40D.87E7F05@idt.net> Date: Thu, 13 Nov 1997 23:31:09 -0500 From: "Gary T. Corcoran" X-Mailer: Mozilla 4.03b8 [en] (X11; I; FreeBSD 2.2.1-RELEASE i386) MIME-Version: 1.0 To: Stefan Molnar CC: Ross Potts , freebsd-hardware@FreeBSD.ORG Subject: Re: modems References: Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Stefan Molnar wrote: > Ross Potts wrote: > > Now I want to use a modem on FreeBSD at home. Before I started leaning over to > > this OS, I tried Linux. Then I heard that they would not take winmodems. On my > > Compaq Presario, that is apparently what I have(no jumpers!). That and the > > stupidly easy setup in FreeBSD made me change over. > > It is not the lack of jumpers makes the winmodem suck, it is the lack of > a UART chip. The UART chip is being emulated in software. Actually it's not the 'UART chip' that's emulated in software, it's the 'controller' microprocessor (often a Z-80). That is, it's the chip that interprets the 'AT' commands and controls the datapump (DSP) which is emulated in software. Generically, they're known as 'controllerless' modems. Nevertheless, they only come with Windows drivers to emulate the controller, and won't work in *any* Unix environment, including FreeBSD. Gary From owner-freebsd-hardware Thu Nov 13 23:59:24 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id XAA09718 for hardware-outgoing; Thu, 13 Nov 1997 23:59:24 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from critter.freebsd.dk (critter.freebsd.dk [195.8.129.26]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id XAA09712 for ; Thu, 13 Nov 1997 23:59:18 -0800 (PST) (envelope-from phk@critter.freebsd.dk) Received: from critter.freebsd.dk (localhost.cybercity.dk [127.0.0.1]) by critter.freebsd.dk (8.8.7/8.8.7) with ESMTP id IAA03919; Fri, 14 Nov 1997 08:57:53 +0100 (CET) (envelope-from phk@critter.freebsd.dk) To: sarah@BLaCKSMITH.com cc: freebsd-hardware@FreeBSD.ORG Subject: Re: four-port ethernet card compatible with freebsd In-reply-to: Your message of "Thu, 13 Nov 1997 21:06:27 EST." <199711140206.VAA02737@mccullers.blacksmith.com> Date: Fri, 14 Nov 1997 08:57:44 +0100 Message-ID: <3917.879494264@critter.freebsd.dk> From: Poul-Henning Kamp Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk In message <199711140206.VAA02737@mccullers.blacksmith.com>, Sarah Bartlett wri tes: >Hi, > >We're looking to build a firewall using freebsd and were wondering if there > >were any 4-port ethernet adaptors known to work under freebsd. Right now >we're looking at an adaptec. We haven't decided yet which version to use an >d >this may be the deciding factor. www.znyx.com -- Poul-Henning Kamp FreeBSD coreteam member phk@FreeBSD.ORG "Real hackers run -current on their laptop." From owner-freebsd-hardware Fri Nov 14 09:35:15 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id JAA16386 for hardware-outgoing; Fri, 14 Nov 1997 09:35:15 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from biggusdiskus.flyingfox.com (biggusdiskus.flyingfox.com [206.14.52.27]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id JAA16351 for ; Fri, 14 Nov 1997 09:35:06 -0800 (PST) (envelope-from jas@flyingfox.com) Received: (from jas@localhost) by biggusdiskus.flyingfox.com (8.8.5/8.8.5) id JAA16933; Fri, 14 Nov 1997 09:34:20 -0800 (PST) Date: Fri, 14 Nov 1997 09:34:20 -0800 (PST) From: Jim Shankland Message-Id: <199711141734.JAA16933@biggusdiskus.flyingfox.com> To: phk@critter.freebsd.dk, sarah@BLaCKSMITH.com Subject: Re: four-port ethernet card compatible with freebsd Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Re: quad ethernet adapters, Poul-Henning writes: > www.znyx.com A couple of notes on Znyx: Their quad 10 Mbit card (the ZX314) seems very stable, but has been discontinued (some are still available). Somebody on this list alluded a few days ago to Znyx delaying production or shipment of the quad 100 Mbit card; so I'd look into that just a little before buying. I have bought a 10-pack of the single Znyx 100 Mbit cards, and wasn't 100% happy. (As it turned out, I was using them all in 10 Mbit mode.) I had to pull several from customer sites in response to ill-defined "flakiness" and performance complaints that disappeared when I swapped in a different brand. So now I have a bunch lying around the office. One has failed here (bizarrely): a single Web page wouldn't load, and it turns out the card was consistently corrupting a single byte in a TCP packet containing part of a JPEG image (one of a sequence of FF bytes, as it happens). And a machine that works fine with Znyx's quad 10 Mbit card and 2 SMC 100 Mbit cards gets weird, random crashes and lockups if I replace the 2 SMC cards with 2 of the Znyx 100 Mb cards. All this makes me a little nervous about Znyx's control of its 100 Mb technology. I'd be interested in hearing whether or not others have had similar problems; maybe I just got unlucky. On the plus side, Znyx knows who Matt Thomas is, and is supportive of his driver writing efforts, and generally acknowledges that there is a market beyond Microsoft OS's, which is a lot more than you can say for some vendors. Jim Shankland Flying Fox Computer Systems, Inc. From owner-freebsd-hardware Fri Nov 14 12:02:05 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA28379 for hardware-outgoing; Fri, 14 Nov 1997 12:02:05 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from anvil.BLaCKSMITH.com (blacksmith.com [207.86.5.40]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA28369 for ; Fri, 14 Nov 1997 12:02:01 -0800 (PST) (envelope-from sarah@BLaCKSMITH.com) Received: from tori.blacksmith.com (tori [192.168.8.101]) by anvil.BLaCKSMITH.com (8.8.5/8.8.5) with ESMTP id OAA28761; Fri, 14 Nov 1997 14:58:24 -0500 (EST) Received: from mccullers.blacksmith.com (mccullers.BLaCKSMITH.com [192.168.8.35]) by tori.blacksmith.com (8.8.5/8.8.5) with ESMTP id OAA19421; Fri, 14 Nov 1997 14:58:19 -0500 (EST) Received: (from sarah@localhost) by mccullers.blacksmith.com (8.8.5/8.8.5) id OAA03148; Fri, 14 Nov 1997 14:58:18 -0500 (EST) Message-Id: <199711141958.OAA03148@mccullers.blacksmith.com> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) Received: by NeXT.Mailer (1.148) From: Sarah Bartlett Date: Fri, 14 Nov 97 14:58:17 -0500 To: Jim Shankland Subject: Re: four-port ethernet card compatible with freebsd cc: phk@critter.freebsd.dk, freebsd-hardware@FreeBSD.ORG Reply-To: sarah@BLaCKSMITH.com References: <199711141734.JAA16933@biggusdiskus.flyingfox.com> Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Thanks for the input on the znyx. I checked it out and noticed that it has the Dec chip 21140, which is essentially the same as the adaptec that we were looking at. I'm not sure how freeBSD drivers are written, but it could be that a driver for the znyx would work on the adaptec(cogent). If there are known problems with the znyx we probably want to avoid it. I have another related question, though. Our fileserver runs freeBSD 2.1.6 and has an intel etherexpress pro 100b ethernet card. We've been noticing increasingly high Ierrs with this setup, which is kind of scary with it being the fileserver and all. One of my co-workers has the exact same setup on his home machine and is experiencing the same problem. Is there a known problem with that driver? If so, is it fixed in later versions of freeBSD? Any ideas on how to minimize the Ierrs? Thanks again for any input. Sarah From owner-freebsd-hardware Fri Nov 14 12:31:21 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id MAA01229 for hardware-outgoing; Fri, 14 Nov 1997 12:31:21 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from persprog.com (root@persprog.com [204.215.255.203]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id MAA01220 for ; Fri, 14 Nov 1997 12:31:13 -0800 (PST) (envelope-from dave@persprog.com) Received: by persprog.com (8.7.5/4.10) id PAA26174; Fri, 14 Nov 1997 15:25:28 -0500 Received: from dave.ppi.com(192.2.2.6) by cerberus.ppi.com via smap (V1.3) id sma026169; Fri Nov 14 15:25:07 1997 Message-ID: <346CB3AD.AEC93383@persprog.com> Date: Fri, 14 Nov 1997 15:25:17 -0500 From: Dave Alderman Reply-To: dave@persprog.com Organization: Personalized Programming, Inc X-Mailer: Mozilla 4.03 [en] (Win95; U) MIME-Version: 1.0 To: "Gary T. Corcoran" CC: Stefan Molnar , Ross Potts , freebsd-hardware@FreeBSD.ORG Subject: Re: modems References: <346BD40D.87E7F05@idt.net> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk Gary T. Corcoran wrote: > > Stefan Molnar wrote: > Actually it's not the 'UART chip' that's emulated in software, it's the > 'controller' microprocessor (often a Z-80). That is, it's the chip that > interprets the 'AT' commands and controls the datapump (DSP) which is emulated > in software. Generically, they're known as 'controllerless' modems. > > Nevertheless, they only come with Windows drivers to emulate the controller, > and won't work in *any* Unix environment, including FreeBSD. > If I remember correctly, there used to be a modem called an RPI modem that performed the data compression in software as well as the modem control functions. Very nasty. Are any of the current crop of "winmodems" similar to the old Rockwell RPI based stinkers? NOTE: I like Rockwell modem chipsets in general - I just thought RPI was ill-conceived. -- "Going down to South Park - going to leave my woes behind..." David W. Alderman dave@persprog.com From owner-freebsd-hardware Fri Nov 14 13:25:00 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA04695 for hardware-outgoing; Fri, 14 Nov 1997 13:25:00 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id NAA04689 for ; Fri, 14 Nov 1997 13:24:54 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id NAA09366; Fri, 14 Nov 1997 13:24:26 -0800 (PST) Message-Id: <199711142124.NAA09366@implode.root.com> To: sarah@BLaCKSMITH.com cc: Jim Shankland , phk@critter.freebsd.dk, freebsd-hardware@FreeBSD.ORG Subject: Re: four-port ethernet card compatible with freebsd In-reply-to: Your message of "Fri, 14 Nov 1997 14:58:17 EST." <199711141958.OAA03148@mccullers.blacksmith.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 14 Nov 1997 13:24:26 -0800 Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk >Thanks for the input on the znyx. I checked it out and noticed that it has >the Dec chip 21140, which is essentially the same as the adaptec that we were >looking at. I'm not sure how freeBSD drivers are written, but it could be >that a driver for the znyx would work on the adaptec(cogent). If there are >known problems with the znyx we probably want to avoid it. > >I have another related question, though. Our fileserver runs freeBSD 2.1.6 >and has an intel etherexpress pro 100b ethernet card. We've been noticing >increasingly high Ierrs with this setup, which is kind of scary with it being >the fileserver and all. One of my co-workers has the exact same setup on >his home machine and is experiencing the same problem. Is there a known >problem with that driver? If so, is it fixed in later versions of freeBSD? >Any ideas on how to minimize the Ierrs? There shouldn't be any input errors - this is indicating that something is wrong. The version of the driver in 2.1.6 doesn't support full duplex, but the card will try to negotiate it in any case. If you have the machine connected to a switch, then this is likely the problem. You'll need to configure the switch port to half duplex or upgrade to the current release of FreeBSD (which supports full duplex operation). -DG David Greenman Core-team/Principal Architect, The FreeBSD Project From owner-freebsd-hardware Fri Nov 14 13:29:29 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id NAA04980 for hardware-outgoing; Fri, 14 Nov 1997 13:29:29 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from gatekeeper.itribe.net (gatekeeper.itribe.net [209.49.144.254]) by hub.freebsd.org (8.8.7/8.8.7) with SMTP id NAA04975 for ; Fri, 14 Nov 1997 13:29:26 -0800 (PST) (envelope-from jamie@itribe.net) Message-Id: <199711142128.QAA14926@gatekeeper.itribe.net> Received: forwarded by SMTP 1.5.2. Date: Fri, 14 Nov 1997 16:26:23 -0500 (EST) From: Jamie Bowden To: Dave Alderman cc: freebsd-hardware@freebsd.org Subject: Re: modems In-Reply-To: <346CB3AD.AEC93383@persprog.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Fri, 14 Nov 1997, Dave Alderman wrote: > Gary T. Corcoran wrote: > > > > Stefan Molnar wrote: > > Actually it's not the 'UART chip' that's emulated in software, it's the > > 'controller' microprocessor (often a Z-80). That is, it's the chip that > > interprets the 'AT' commands and controls the datapump (DSP) which is emulated > > in software. Generically, they're known as 'controllerless' modems. > > > > Nevertheless, they only come with Windows drivers to emulate the controller, > > and won't work in *any* Unix environment, including FreeBSD. > > > > If I remember correctly, there used to be a modem called an RPI modem that performed the > data compression in software as well as the modem control functions. Very nasty. Are any > of the current crop of "winmodems" similar to the old Rockwell RPI based stinkers? > > NOTE: I like Rockwell modem chipsets in general - I just thought RPI was ill-conceived. > > -- > "Going down to South Park - going to leave my woes behind..." > David W. Alderman dave@persprog.com > Winmodems are missing one of the chips a normal modem has (I forget which one, as it was unimportant since I would never use one), and uses software to offload that chip's function onto the main processor. Jamie Bowden Systems Administrator, iTRiBE.net If we've got to fight over grep, sign me up. But boggle can go. -Ted Faber (on Hasbro's request for removal of /usr/games/boggle) From owner-freebsd-hardware Fri Nov 14 14:11:41 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id OAA08031 for hardware-outgoing; Fri, 14 Nov 1997 14:11:41 -0800 (PST) (envelope-from owner-freebsd-hardware) Received: from anvil.BLaCKSMITH.com (blacksmith.com [207.86.5.40]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id OAA08017 for ; Fri, 14 Nov 1997 14:11:36 -0800 (PST) (envelope-from sarah@BLaCKSMITH.com) Received: from tori.blacksmith.com (tori [192.168.8.101]) by anvil.BLaCKSMITH.com (8.8.5/8.8.5) with ESMTP id RAA04202; Fri, 14 Nov 1997 17:11:01 -0500 (EST) Received: from mccullers.blacksmith.com (mccullers.BLaCKSMITH.com [192.168.8.35]) by tori.blacksmith.com (8.8.5/8.8.5) with ESMTP id RAA20200; Fri, 14 Nov 1997 17:11:00 -0500 (EST) Received: (from sarah@localhost) by mccullers.blacksmith.com (8.8.5/8.8.5) id RAA03228; Fri, 14 Nov 1997 17:10:59 -0500 (EST) Message-Id: <199711142210.RAA03228@mccullers.blacksmith.com> Content-Type: text/plain MIME-Version: 1.0 (NeXT Mail 4.2mach v148) Received: by NeXT.Mailer (1.148) From: Sarah Bartlett Date: Fri, 14 Nov 97 17:10:55 -0500 To: dg@root.com Subject: Re: four-port ethernet card compatible with freebsd cc: freebsd-hardware@FreeBSD.ORG Reply-To: sarah@BLaCKSMITH.com References: <199711142124.NAA09366@implode.root.com> Sender: owner-freebsd-hardware@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > To: sarah@BLaCKSMITH.com > cc: Jim Shankland , phk@critter.freebsd.dk, > freebsd-hardware@FreeBSD.ORG Subject: Re: four-port ethernet card > compatible with freebsd > In-reply-to: Your message of "Fri, 14 Nov 1997 14:58:17 EST." > <199711141958.OAA03148@mccullers.blacksmith.com> > From: David Greenman > Reply-To: dg@root.com > Date: Fri, 14 Nov 1997 13:24:26 -0800 > Sender: root@implode.root.com > > There shouldn't be any input errors - this is indicating that something > is wrong. The version of the driver in 2.1.6 doesn't support full duplex, > but the card will try to negotiate it in any case. If you have the machine > connected to a switch, then this is likely the problem. You'll need to > configure the switch port to half duplex or upgrade to the current release > of FreeBSD (which supports full duplex operation). > Thanks for the response. Our server is connected to a 100mb hub and not a switch, so I don't think that's the problem. My co-worker's machine, which is having a similar problem, is also not plugged into a switch or to another machine directly. Any other suggestions? This is not something we've seen before. Thanks, Sarah