From owner-freebsd-hardware Sun Jun 24 12:10:51 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from mail8.nc.rr.com (fe8.southeast.rr.com [24.93.67.55]) by hub.freebsd.org (Postfix) with ESMTP id E947F37B405 for ; Sun, 24 Jun 2001 12:10:49 -0700 (PDT) (envelope-from aa8vb@nc.rr.com) Received: from stealth.dummynet ([24.25.3.190]) by mail8.nc.rr.com with Microsoft SMTPSVC(5.5.1877.687.68); Sun, 24 Jun 2001 15:10:44 -0400 Received: (from rhh@localhost) by stealth.dummynet (8.11.1/8.11.1) id f5OJDPZ08613 for hardware@FreeBSD.ORG; Sun, 24 Jun 2001 15:13:25 -0400 (EDT) (envelope-from aa8vb@nc.rr.com) X-Authentication-Warning: stealth.dummynet: rhh set sender to aa8vb@nc.rr.com using -f Date: Sun, 24 Jun 2001 15:13:25 -0400 From: Randall Hopper To: hardware@FreeBSD.ORG Subject: 3C905B-Combo supported? Message-ID: <20010624151325.A8308@nc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Lots of good things about this chipset, but nothing about whether anyone has the BNC working well in FreeBSD. It's a 3Com 3C905B with both TP and BNC inputs. There's an open problem report (18336) that makes me wonder: o [2000/05/01] misc/18336 3C905B-COMBO cannot find 10base-2 LAN Randall -- Randall Hopper aa8vb@nc.rr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 25 10:43:16 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id 1C19937B405 for ; Mon, 25 Jun 2001 10:43:13 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f5PHh3I18461; Mon, 25 Jun 2001 10:43:03 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <20010624151325.A8308@nc.rr.com> Date: Mon, 25 Jun 2001 12:16:53 -0700 (PDT) From: John Baldwin To: Randall Hopper Subject: RE: 3C905B-Combo supported? Cc: hardware@FreeBSD.org Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 24-Jun-01 Randall Hopper wrote: > Lots of good things about this chipset, but nothing about whether > anyone has the BNC working well in FreeBSD. > > It's a 3Com 3C905B with both TP and BNC inputs. There's an open > problem report (18336) that makes me wonder: > > o [2000/05/01] misc/18336 3C905B-COMBO cannot find 10base-2 LAN I used one of these for years when I ran a BNC LAN in my dormroom at college. I needed to use -link1 with ifconfig to force it to use the BNC tranceiver though. Nowadays the ep driver supports 'media' so you will probably need to do: ifconfig ep0 media 10base2/BNC See the manpage for more info. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 25 15: 1:16 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from tantivy.stanford.edu (tantivy.Stanford.EDU [171.64.234.70]) by hub.freebsd.org (Postfix) with ESMTP id AE9D937B405; Mon, 25 Jun 2001 15:01:14 -0700 (PDT) (envelope-from techie@tantivy.stanford.edu) Received: (from techie@localhost) by tantivy.stanford.edu (8.9.3/8.9.1) id PAA03746; Mon, 25 Jun 2001 15:01:14 -0700 (PDT) Date: Mon, 25 Jun 2001 15:01:14 -0700 (PDT) From: Bob Vaughan Message-Id: <200106252201.PAA03746@tantivy.stanford.edu> To: jhb@freebsd.org Subject: RE: 3C905B-Combo supported? Cc: freebsd-hardware@freebsd.org In-Reply-To: Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I think you're thinking of the 3c509b... I am surprised that 3com came out with a combo version of the 3c905b (10/100 PCI - uses the xl driver). I guess they needed to replace the 3c509b combo with a pci version.. -- Welcome My Son, Welcome To The Machine -- Bob Vaughan | techie@{w6yx|tantivy}.stanford.edu | kc6sxc@w6yx.ampr.org | P.O. Box 19792, Stanford, Ca 94309 -- I am Me, I am only Me, And no one else is Me, What could be simpler? -- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 25 15:11:52 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from meow.osd.bsdi.com (meow.osd.bsdi.com [204.216.28.88]) by hub.freebsd.org (Postfix) with ESMTP id C8AF937B401 for ; Mon, 25 Jun 2001 15:11:49 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: from laptop.baldwin.cx (john@jhb-laptop.osd.bsdi.com [204.216.28.241]) by meow.osd.bsdi.com (8.11.3/8.11.2) with ESMTP id f5PMB6I23421; Mon, 25 Jun 2001 15:11:06 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.4.0 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: <200106252201.PAA03746@tantivy.stanford.edu> Date: Mon, 25 Jun 2001 15:14:43 -0700 (PDT) From: John Baldwin To: Bob Vaughan Subject: RE: 3C905B-Combo supported? Cc: freebsd-hardware@FreeBSD.org Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 25-Jun-01 Bob Vaughan wrote: > I think you're thinking of the 3c509b... Doh, I am. > I am surprised that 3com came out with a combo version of the 3c905b > (10/100 PCI - uses the xl driver). I guess they needed to replace the > 3c509b combo with a pci version.. 10base2 on a PCI card seems really, really weird. -- John Baldwin -- http://www.FreeBSD.org/~jhb/ PGP Key: http://www.baldwin.cx/~john/pgpkey.asc "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 25 15:55:16 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from sleipner.eiffel.dk (sub19-229.member.dsl-only.net [63.105.19.229]) by hub.freebsd.org (Postfix) with ESMTP id 5096737B405 for ; Mon, 25 Jun 2001 15:55:13 -0700 (PDT) (envelope-from flemming@froekjaer.org) Received: from froekjaer.org (sub19-225.member.dsl-only.net [63.105.19.225]) by sleipner.eiffel.dk (8.11.1/8.11.1) with ESMTP id f5PMuhQ93271 for ; Mon, 25 Jun 2001 15:56:43 -0700 (PDT) (envelope-from flemming@froekjaer.org) Message-ID: <3B37C156.CD4CE20C@froekjaer.org> Date: Mon, 25 Jun 2001 15:55:18 -0700 From: Flemming Froekjaer X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.12 i386) X-Accept-Language: en MIME-Version: 1.0 To: hardware@freebsd.org Subject: Disk performance Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I tried to dump a file system to a DLT tape. The tape is cable of 10MB/s but I only got about 1600 KB/s To find out if it was the tape I tried to dump to /dev/null instead, but i still only get 1665 KB/s It's a raid 1 on a ami raid controller, and 2 IBM Disks. What performance should I expect from a setup like that? How do I best measure the disk performance? I get about twice that performance from my IDE workstation. That cant be right. Is there any way to improve the performance? \Flemming > dump -0af /dev/null / DUMP: Date of this level 0 dump: Mon Jun 25 10:41:35 2001 DUMP: Date of last level 0 dump: the epoch DUMP: Dumping /dev/amrd0s1a (/) to /dev/null DUMP: mapping (Pass I) [regular files] DUMP: mapping (Pass II) [directories] DUMP: estimated 34970 tape blocks. DUMP: dumping (Pass III) [directories] DUMP: dumping (Pass IV) [regular files] DUMP: DUMP: 34972 tape blocks on 1 volume DUMP: finished in 21 seconds, throughput 1665 KBytes/sec DUMP: Closing /dev/null DUMP: DUMP IS DONE > mount /dev/amrd0s1a on / (ufs, local) /dev/amrd0s1f on /usr (ufs, NFS exported, local, soft-updates) /dev/amrd0s1e on /var (ufs, local, soft-updates) procfs on /proc (procfs, local) To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 25 16: 5:42 2001 Delivered-To: freebsd-hardware@freebsd.org Received: by hub.freebsd.org (Postfix, from userid 618) id 4F52C37B409; Mon, 25 Jun 2001 16:05:40 -0700 (PDT) Subject: Re: 3C905B-Combo supported? In-Reply-To: <20010624151325.A8308@nc.rr.com> from Randall Hopper at "Jun 24, 2001 03:13:25 pm" To: aa8vb@nc.rr.com (Randall Hopper) Date: Mon, 25 Jun 2001 16:05:38 -0700 (PDT) Cc: freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL54 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-Id: <20010625230540.4F52C37B409@hub.freebsd.org> From: wpaul@FreeBSD.ORG (Bill Paul) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Lots of good things about this chipset, but nothing about whether > anyone has the BNC working well in FreeBSD. > > It's a 3Com 3C905B with both TP and BNC inputs. There's an open > problem report (18336) that makes me wonder: > > o [2000/05/01] misc/18336 3C905B-COMBO cannot find 10base-2 LAN Yes, these cards do work, but no, autoselect doesn't work with the BNC port. The xl driver only does autonegotiation using 10/100 port: you can use the 10base2 port, but you have to select it manually. ifconfig_xl0="inet 10.0.0.1 media 10base2/BNC netmask 255.255.255.0" The 10/100 autonegotiation is carried out automatically by the transceiver hardware, but for 10base2, the driver would have to do a lot of its own work to test for media presence. The 3.x driver would attempt to use the media selection specified in the EEPROM (which can be changed with the 3C90XCFG.EXE utility that comes with the card), but the 4.x and later driver always defaults to autonegotiate. -Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 25 17:22:14 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from netau1.alcanet.com.au (ntp.alcanet.com.au [203.62.196.27]) by hub.freebsd.org (Postfix) with ESMTP id AEA0F37B406 for ; Mon, 25 Jun 2001 17:22:08 -0700 (PDT) (envelope-from jeremyp@gsmx07.alcatel.com.au) Received: from mfg1.cim.alcatel.com.au (mfg1.cim.alcatel.com.au [139.188.23.1]) by netau1.alcanet.com.au (8.9.3 (PHNE_22672)/8.9.3) with ESMTP id KAA24183; Tue, 26 Jun 2001 10:21:59 +1000 (EST) Received: from gsmx07.alcatel.com.au by cim.alcatel.com.au (PMDF V5.2-32 #37640) with ESMTP id <01K57WKDDKPCVLRHGS@cim.alcatel.com.au>; Tue, 26 Jun 2001 10:21:58 +1000 Received: (from jeremyp@localhost) by gsmx07.alcatel.com.au (8.11.1/8.11.1) id f5Q0Lvd83561; Tue, 26 Jun 2001 10:21:57 +1000 (EST envelope-from jeremyp) Content-return: prohibited Date: Tue, 26 Jun 2001 10:21:56 +1000 From: Peter Jeremy Subject: Re: Disk performance In-reply-to: <3B37C156.CD4CE20C@froekjaer.org>; from flemming@froekjaer.org on Mon, Jun 25, 2001 at 03:55:18PM -0700 To: Flemming Froekjaer Cc: hardware@FreeBSD.ORG Mail-Followup-To: Flemming Froekjaer , hardware@FreeBSD.ORG Message-id: <20010626102156.G95583@gsmx07.alcatel.com.au> MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-disposition: inline User-Agent: Mutt/1.2.5i References: <3B37C156.CD4CE20C@froekjaer.org> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On 2001-Jun-25 15:55:18 -0700, Flemming Froekjaer wrote: >I tried to dump a file system to a DLT tape. >The tape is cable of 10MB/s but I only got about 1600 KB/s >To find out if it was the tape I tried to dump to /dev/null instead, but >i still only get 1665 KB/s Some time ago (mid-November 1998), I looked into dump (check out the thread `dump(8) very slow' in freebsd-hackers). The major problem with dump is that it reads the disk in filesystem-block (typically 8K) sized blocks (or less for frags) and doesn't attempt to merge adjacent reads. It also dumps files in inode order - accessing the disk in same order as the output blocks, rather than trying to sort the disk reads. At the time, I instrumented dump to get a record of physical disk accesses whilst dumping a couple of filesystems and did some experiments with re-ordering the reads, but never posted my results (I don't remember what the results were, but I didn't get a massive speed-up). Apparently, NetBSD's dump(8) has improved the buffering to get much better throughput. You might like to have a look - I haven't gotten around to it yet. Peter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 25 18: 1: 9 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from mail.cs.ait.ac.th (mail.cs.ait.ac.th [192.41.170.16]) by hub.freebsd.org (Postfix) with ESMTP id 5697737B406 for ; Mon, 25 Jun 2001 18:01:06 -0700 (PDT) (envelope-from on@cs.ait.ac.th) Received: from banyan.cs.ait.ac.th (on@banyan.cs.ait.ac.th [192.41.170.5]) by mail.cs.ait.ac.th (8.11.3/8.9.3) with ESMTP id f5Q12ip46975; Tue, 26 Jun 2001 08:02:44 +0700 (ICT) Received: (from on@localhost) by banyan.cs.ait.ac.th (8.8.5/8.8.5) id IAA13636; Tue, 26 Jun 2001 08:00:48 +0700 (ICT) Date: Tue, 26 Jun 2001 08:00:48 +0700 (ICT) Message-Id: <200106260100.IAA13636@banyan.cs.ait.ac.th> X-Authentication-Warning: banyan.cs.ait.ac.th: on set sender to on@banyan.cs.ait.ac.th using -f From: Olivier Nicole To: peter.jeremy@alcatel.com.au Cc: flemming@froekjaer.org, hardware@FreeBSD.ORG In-reply-to: <20010626102156.G95583@gsmx07.alcatel.com.au> (message from Peter Jeremy on Tue, 26 Jun 2001 10:21:56 +1000) Subject: Re: Disk performance References: <3B37C156.CD4CE20C@froekjaer.org> <20010626102156.G95583@gsmx07.alcatel.com.au> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >I tried to dump a file system to a DLT tape. >The tape is cable of 10MB/s but I only got about 1600 KB/s >To find out if it was the tape I tried to dump to /dev/null instead, but >i still only get 1665 KB/s There have been mention about team and cstream, both are in the ports, to buffer disk read and send larger blocks to the tape. Olivier To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 25 19:56:17 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from mail7.nc.rr.com (mail7.southeast.rr.com [24.93.67.54]) by hub.freebsd.org (Postfix) with ESMTP id 758DB37B405 for ; Mon, 25 Jun 2001 19:56:15 -0700 (PDT) (envelope-from aa8vb@nc.rr.com) Received: from stealth.dummynet ([24.25.3.190]) by mail7.nc.rr.com with Microsoft SMTPSVC(5.5.1877.687.68); Mon, 25 Jun 2001 22:56:08 -0400 Received: (from rhh@localhost) by stealth.dummynet (8.11.4/8.11.1) id f5Q2wtJ00916 for hardware@FreeBSD.ORG; Mon, 25 Jun 2001 22:58:55 -0400 (EDT) (envelope-from aa8vb@nc.rr.com) X-Authentication-Warning: stealth.dummynet: rhh set sender to aa8vb@nc.rr.com using -f Date: Mon, 25 Jun 2001 22:58:55 -0400 From: Randall Hopper To: hardware@FreeBSD.ORG Subject: Re: 3C905B-Combo supported? Message-ID: <20010625225855.A900@nc.rr.com> References: <20010624151325.A8308@nc.rr.com> <20010625230540.4F52C37B409@hub.freebsd.org> <200106252201.PAA03746@tantivy.stanford.edu> <200106252201.PAA03746@tantivy.stanford.edu> <20010624151325.A8308@nc.rr.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from jhb@FreeBSD.ORG on Mon, Jun 25, 2001 at 12:16:53PM -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Thanks for the replies! Randall -- Randall Hopper aa8vb@nc.rr.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 26 13:15:33 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from oracle.clara.net (oracle.clara.net [195.8.69.94]) by hub.freebsd.org (Postfix) with ESMTP id C70CD37B407 for ; Tue, 26 Jun 2001 13:15:30 -0700 (PDT) (envelope-from alex@clara.co.uk) Received: from [213.253.39.95] (helo=myname.my.domain) by oracle.clara.net with esmtp (Exim 3.11 #5) id 15EzFB-000P2a-00 for hardware@freebsd.org; Tue, 26 Jun 2001 21:15:29 +0100 Received: (from alex@localhost) by myname.my.domain (8.11.3/8.11.3) id f5QKGvI00883 for hardware@freebsd.org; Tue, 26 Jun 2001 21:16:57 +0100 (BST) (envelope-from alex) Date: Tue, 26 Jun 2001 21:16:57 +0100 From: "Aleksandar Simic'" To: hardware@freebsd.org Subject: NIC error message Message-ID: <20010626211657.A811@frustum.clara.co.uk> Mail-Followup-To: Aleksandar Simic' , hardware@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hello, I get the following error quite often: ste0: transmission error: 90 ste0: tx underrun; increasing tx star threshold to 60 bytes where ste0 is my D-Link DFE-550TX 10/100BaseTX NIC. What is the error due to ? And how do I get rid of it if possible ? --Alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jun 28 5: 1:19 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from netcabo.pt (mail1.netcabo.pt [212.113.161.135]) by hub.freebsd.org (Postfix) with ESMTP id 6506337B403 for ; Thu, 28 Jun 2001 05:01:10 -0700 (PDT) (envelope-from OpsyDopsy@netcabo.pt) Received: from OpsyDopsy ([213.22.0.69]) by netcabo.pt with Microsoft SMTPSVC(5.5.1877.687.68); Thu, 28 Jun 2001 12:55:22 +0100 Date: Thu, 28 Jun 2001 13:01:36 +0100 To: hardware@freebsd.org From: =?iso-8859-1?Q?Jo=E3o_Fernandes?= Subject: NIC Reply-To: OpsyDopsy@netcabo.pt X-Mailer: Opera 5.11 build 904 X-Priority: 3 (Normal) Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Message-ID: <00bdf2255111c61TVCABO05@netcabo.pt> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Hey, I've given up on my Realtek 8139 working on FBSD, so could anyone sugest a good well suported NIC? Thanks in advance. JF To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jun 28 7:31:19 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from zogbe.tasam.com (cj45658-a.reston1.va.home.com [65.9.36.73]) by hub.freebsd.org (Postfix) with ESMTP id 32D0537B407 for ; Thu, 28 Jun 2001 07:31:16 -0700 (PDT) (envelope-from clash@fireduck.com) Received: from battleship (zogbe.tasam.com [10.45.45.11] (may be forged)) by zogbe.tasam.com (8.11.4/8.11.4) with SMTP id f5SEV7K60908; Thu, 28 Jun 2001 10:31:07 -0400 (EDT) Message-ID: <002301c0ffde$f83688c0$0a2d2d0a@battleship> From: "Joseph Gleason" To: , References: <00bdf2255111c61TVCABO05@netcabo.pt> Subject: Re: NIC Date: Thu, 28 Jun 2001 10:31:07 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org I always like intel ether express pro (fxp driver) or 3com 3c905 (xl driver). I used to have lots of problems with realteks under FreeBSD, but since Bill Paul is the man, I haven't had any problems with recent versions of FreeBSD. What version are you running? ----- Original Message ----- From: "Joćo Fernandes" To: Sent: Thursday, June 28, 2001 08:01 Subject: NIC > Hey, I've given up on my Realtek 8139 working on FBSD, so could anyone sugest a good well suported NIC? > > Thanks in advance. > > JF > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jun 28 7:43:31 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from zogbe.tasam.com (cj45658-a.reston1.va.home.com [65.9.36.73]) by hub.freebsd.org (Postfix) with ESMTP id 78B0C37B409 for ; Thu, 28 Jun 2001 07:43:27 -0700 (PDT) (envelope-from clash@fireduck.com) Received: from battleship (zogbe.tasam.com [10.45.45.11] (may be forged)) by zogbe.tasam.com (8.11.4/8.11.4) with SMTP id f5SEhCK61035; Thu, 28 Jun 2001 10:43:12 -0400 (EDT) Message-ID: <002d01c0ffe0$a8562930$0a2d2d0a@battleship> From: "Joseph Gleason" To: "Joseph Gleason" , , References: <00bdf2255111c61TVCABO05@netcabo.pt> <002301c0ffde$f83688c0$0a2d2d0a@battleship> Subject: Re: NIC + PCI IRQ assignment Date: Thu, 28 Jun 2001 10:43:12 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.3018.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.3018.1300 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Also, you might want to shuffle your PCI cards around and frob various bios settings to get the realtek card to use a different IRQ. That seems to work for me sometimes. Yes, I realize when I say things like "seems to work for me sometimes" it means I don't know enough about something I probably should. Anyone have an references/explanations for: 1) How do PCI cards get assigned IRQ's? What is the process? 2) What will happen if two PCI devices get assigned the same IRQ? Is it a problem with well designed and well behaved devices? 3) What does telling the BIOS "Plug and Play OS Installed: Yes" really do? I have been using PC hardware for many years, but with no formal training/training I have some gaps that I would like to work on. ----- Original Message ----- From: "Joseph Gleason" To: ; Sent: Thursday, June 28, 2001 10:31 Subject: Re: NIC > I always like intel ether express pro (fxp driver) or 3com 3c905 (xl > driver). > > I used to have lots of problems with realteks under FreeBSD, but since Bill > Paul is the man, I haven't had any problems with recent versions of FreeBSD. > What version are you running? > > > > ----- Original Message ----- > From: "Joćo Fernandes" > To: > Sent: Thursday, June 28, 2001 08:01 > Subject: NIC > > > > Hey, I've given up on my Realtek 8139 working on FBSD, so could anyone > sugest a good well suported NIC? > > > > Thanks in advance. > > > > JF > > > > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-hardware" in the body of the message > > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jun 28 9:16:41 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from edwin.mounet.com (edwin.mounet.com [216.145.76.8]) by hub.freebsd.org (Postfix) with SMTP id 1A23837B406 for ; Thu, 28 Jun 2001 09:16:38 -0700 (PDT) (envelope-from hornback@wireco.net) Received: (qmail 1331 invoked by uid 0); 28 Jun 2001 16:14:44 -0000 Received: from unknown (HELO tomcat) (216.145.84.76) by mounet.com with SMTP; 28 Jun 2001 16:14:44 -0000 From: "Andrew C. Hornback" To: Subject: RE: NIC Date: Thu, 28 Jun 2001 12:16:24 -0400 Message-ID: <001201c0ffed$ad2e5240$0e00000a@tomcat> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 8bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <00bdf2255111c61TVCABO05@netcabo.pt> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org If you're looking for a good PCI NIC that enjoys wonderful support in FreeBSD, I would recommend my favorite weapon of choice... the SMC 9432TX. These cards can be had for little to nothing these days and offer wonderful support (their driver in FreeBSD is tx, if that tells you anything). --- Andy > -----Original Message----- > From: owner-freebsd-hardware@FreeBSD.ORG > [mailto:owner-freebsd-hardware@FreeBSD.ORG]On Behalf Of Joćo Fernandes > Sent: Thursday, June 28, 2001 8:02 AM > To: hardware@freebsd.org > Subject: NIC > > > Hey, I've given up on my Realtek 8139 working on FBSD, so could > anyone sugest a good well suported NIC? > > Thanks in advance. > > JF > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hardware" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jun 28 11:11:19 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 53BB537B409 for ; Thu, 28 Jun 2001 11:11:17 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f5SIBEO25097; Thu, 28 Jun 2001 11:11:14 -0700 Date: Thu, 28 Jun 2001 11:11:14 -0700 From: Brooks Davis To: "Andrew C. Hornback" Cc: hardware@FreeBSD.ORG Subject: Re: NIC Message-ID: <20010628111114.E7843@Odin.AC.HMC.Edu> References: <00bdf2255111c61TVCABO05@netcabo.pt> <001201c0ffed$ad2e5240$0e00000a@tomcat> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="EgVrEAR5UttbsTXg" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <001201c0ffed$ad2e5240$0e00000a@tomcat>; from hornback@wireco.net on Thu, Jun 28, 2001 at 12:16:24PM -0400 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --EgVrEAR5UttbsTXg Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 28, 2001 at 12:16:24PM -0400, Andrew C. Hornback wrote: > If you're looking for a good PCI NIC that enjoys wonderful support in > FreeBSD, I would recommend my favorite weapon of choice... the SMC 9432TX. > These cards can be had for little to nothing these days and offer wonderf= ul > support (their driver in FreeBSD is tx, if that tells you anything). The autoneg function sucks on these cards. It's even a known problem under Windows. I often have problems with the one in my docking station when it's first powered up. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --EgVrEAR5UttbsTXg Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7O3NBXY6L6fI4GtQRAuvqAJsGMYuc6P2dXQAzJWicTU6vxpVm/QCcCoke nh4g8WMlyr+/x7YjOVk2K9A= =a248 -----END PGP SIGNATURE----- --EgVrEAR5UttbsTXg-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jun 28 12: 8: 7 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from arg1.demon.co.uk (arg1.demon.co.uk [194.222.34.166]) by hub.freebsd.org (Postfix) with ESMTP id BC9E237B405 for ; Thu, 28 Jun 2001 12:08:02 -0700 (PDT) (envelope-from arg@arg1.demon.co.uk) Received: by arg1.demon.co.uk (Postfix, from userid 300) id 5DF9C9B03; Thu, 28 Jun 2001 20:07:59 +0100 (BST) Received: from localhost (localhost [127.0.0.1]) by arg1.demon.co.uk (Postfix) with ESMTP id 5611F5D1D; Thu, 28 Jun 2001 20:07:59 +0100 (BST) Date: Thu, 28 Jun 2001 20:07:59 +0100 (BST) From: Andrew Gordon X-X-Sender: To: Joseph Gleason Cc: Subject: Re:PCI IRQ assignment In-Reply-To: <002d01c0ffe0$a8562930$0a2d2d0a@battleship> Message-ID: <20010628190706.I15194-100000@server.arg.sj.co.uk> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Thu, 28 Jun 2001, Joseph Gleason wrote: > > Anyone have an references If you want the full detail, the Mindshare "PCI System Architecture" book is a good read (ISBN 0-0201-40993-3). >/explanations for: > > 1) How do PCI cards get assigned IRQ's? What is the process? Each PCI card has four INT pins (A,B,C,D). Most single-function cards are hard-wired to use INT-A. Multi-function cards, or cards with PCI bridges on them can use more. All of the IRQ pins on the PCI sockets are wired to pins on the motherboard chipset. In order to economise on pins, these are often shared in a 'diagonal' fashion (ie. slot1/INT-A is wired to slot2/INT-B and slot3/INT-C, slot2/INT-A is wired to slot3/INT-B and slot1/INT-D etc), but the exact details are motherboard dependent. Note that this doesn't normally in itself lead to interrupt sharing unless you have more than 4 slots or have some multi-function cards. These chipset pins are then mapped onto the interrupts seen by the CPU in a chipset-specific fashion (eg. a standard chipset emulates a pair of 8259 interrupt controllers for the traditional 15 ISA interrupts, but an SMP chipset has more APIC interrupts available). The BIOS is responsible for knowing how all of this implementation-dependent stuff is wired up: each card (or function within a multi-function card) has a read/write register on it for the interrupt number, so the BIOS can assign an interrupt to the card, configure the interrupt routing logic, then write the chosen interrupt number back into the card so that driver software can find out which interrupt will be generated by that card. > 2) What will happen if two PCI devices get assigned the same IRQ? Is it a > problem with well designed and well behaved devices? It is not normally a problem, provided that the drivers are written to allow interrupt sharing, which most are - particularly under FreeBSD. One source of confusion is where otherwise identical hardware is available in both PCI and ISA versions, with the same driver: the driver must not share interrupts in the ISA case, but can do so in the PCI case. > 3) What does telling the BIOS "Plug and Play OS Installed: Yes" really do? When set to "no", the BIOS configures all PnP hardware (assigns I/O addresses, IRQs etc) before booting. When set to "yes", it need only configure those devices needed for the boot process, and leaves the OS to configure the rest later. The exact details vary: older BIOSes tend to configure all of the PCI devices regardless, such that the 'PnP OS' setting only affects ISA PnP; more recent BIOSes often leave PCI devices unconfigured too (which will then show up at "irq 255" when booting FreeBSD-4.x on such a system). Note that even when the OS is assigning the interrupt, it still needs to interract with the BIOS to do so, since only the BIOS knows how the sockets are wired up on the motherboard. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jun 28 17:27:34 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from edwin.mounet.com (edwin.mounet.com [216.145.76.8]) by hub.freebsd.org (Postfix) with SMTP id CF07437B409 for ; Thu, 28 Jun 2001 17:27:31 -0700 (PDT) (envelope-from hornback@wireco.net) Received: (qmail 19270 invoked by uid 0); 29 Jun 2001 00:25:36 -0000 Received: from unknown (HELO tomcat) (216.145.84.89) by mounet.com with SMTP; 29 Jun 2001 00:25:36 -0000 From: "Andrew C. Hornback" To: "Brooks Davis" Cc: Subject: RE: NIC Date: Thu, 28 Jun 2001 20:27:06 -0400 Message-ID: <003601c10032$3a02a060$0e00000a@tomcat> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 (Normal) X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook 8.5, Build 4.71.2173.0 In-Reply-To: <20010628111114.E7843@Odin.AC.HMC.Edu> X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Importance: Normal Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > -----Original Message----- > From: owner-freebsd-hardware@FreeBSD.ORG > [mailto:owner-freebsd-hardware@FreeBSD.ORG]On Behalf Of Brooks Davis > Sent: Thursday, June 28, 2001 2:11 PM > To: Andrew C. Hornback > Cc: hardware@FreeBSD.ORG > Subject: Re: NIC > > > On Thu, Jun 28, 2001 at 12:16:24PM -0400, Andrew C. Hornback wrote: > > If you're looking for a good PCI NIC that enjoys wonderful support in > > FreeBSD, I would recommend my favorite weapon of choice... the > SMC 9432TX. > > These cards can be had for little to nothing these days and > offer wonderful > > support (their driver in FreeBSD is tx, if that tells you anything). > > The autoneg function sucks on these cards. It's even a known problem > under Windows. I often have problems with the one in my docking station > when it's first powered up. Are you sure that we're even talking about the same NIC here? The 9432TX is a PCI card, not a PCMCIA card. From all of the ones that I've had (roughly 20), I've never had a problem. FreeBSD has always found the card and configured it properly on install. I have two of these cards in my high end workstation, two in my firewall and one in my other workstation. The rest were sold to various clients who have as of yet to report any problems at all. --- Andy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jun 28 17:35:54 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from odin.ac.hmc.edu (Odin.AC.HMC.Edu [134.173.32.75]) by hub.freebsd.org (Postfix) with ESMTP id 6E15637B405 for ; Thu, 28 Jun 2001 17:35:52 -0700 (PDT) (envelope-from brdavis@odin.ac.hmc.edu) Received: (from brdavis@localhost) by odin.ac.hmc.edu (8.11.0/8.11.0) id f5T0Zoo11535; Thu, 28 Jun 2001 17:35:50 -0700 Date: Thu, 28 Jun 2001 17:35:50 -0700 From: Brooks Davis To: "Andrew C. Hornback" Cc: hardware@FreeBSD.ORG Subject: Re: NIC Message-ID: <20010628173550.A10944@Odin.AC.HMC.Edu> References: <20010628111114.E7843@Odin.AC.HMC.Edu> <003601c10032$3a02a060$0e00000a@tomcat> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-md5; protocol="application/pgp-signature"; boundary="T4sUOijqQbZv57TR" Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: <003601c10032$3a02a060$0e00000a@tomcat>; from hornback@wireco.net on Thu, Jun 28, 2001 at 08:27:06PM -0400 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org --T4sUOijqQbZv57TR Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Thu, Jun 28, 2001 at 08:27:06PM -0400, Andrew C. Hornback wrote: > Are you sure that we're even talking about the same NIC here? The 9432TX > is a PCI card, not a PCMCIA card. Absolutly, my docking station has two PCI slots, one of which is occupied by the only one of these I still have in production. I've ripped several out of systems in our lab and replaced them with Intel cards. Our networking people have also reported significant problems with them. -- Brooks --=20 Any statement of the form "X is the one, true Y" is FALSE. PGP fingerprint 655D 519C 26A7 82E7 2529 9BF0 5D8E 8BE9 F238 1AD4 --T4sUOijqQbZv57TR Content-Type: application/pgp-signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.0.4 (GNU/Linux) Comment: For info see http://www.gnupg.org iD8DBQE7O81lXY6L6fI4GtQRAgr1AJ0ceRb3zcNnutszPf9EQTh/QO+RLQCgxyHY hOFLSYQXWm7oE48wMJTnveQ= =TWDe -----END PGP SIGNATURE----- --T4sUOijqQbZv57TR-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jun 28 21:43:30 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from mass.dis.org (tserver.conference.usenix.org [199.103.159.3]) by hub.freebsd.org (Postfix) with ESMTP id 04DF437B40C for ; Thu, 28 Jun 2001 21:43:28 -0700 (PDT) (envelope-from msmith@mass.dis.org) Received: from mass.dis.org (localhost [127.0.0.1]) by mass.dis.org (8.11.4/8.11.3) with ESMTP id f5T4tgq01485; Thu, 28 Jun 2001 21:55:43 -0700 (PDT) (envelope-from msmith@mass.dis.org) Message-Id: <200106290455.f5T4tgq01485@mass.dis.org> X-Mailer: exmh version 2.1.1 10/15/1999 To: "Joseph Gleason" Cc: OpsyDopsy@netcabo.pt, hardware@FreeBSD.ORG Subject: Re: NIC + PCI IRQ assignment In-reply-to: Your message of "Thu, 28 Jun 2001 10:43:12 EDT." <002d01c0ffe0$a8562930$0a2d2d0a@battleship> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Mime-Version: 1.0 Content-Transfer-Encoding: quoted-printable Date: Thu, 28 Jun 2001 21:55:42 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org > Anyone have an references/explanations for: > = > 1) How do PCI cards get assigned IRQ's? What is the process? Bad, evil BIOS magic, combined with knowledge of how your motherboard is = laid out. Seriously. > 2) What will happen if two PCI devices get assigned the same IRQ? Is i= t a > problem with well designed and well behaved devices? No. > 3) What does telling the BIOS "Plug and Play OS Installed: Yes" really = do? It depends. Typically, it means the BIOS will do less work setting up = your hardware. -- = =2E.. every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jun 29 4:52:51 2001 Delivered-To: freebsd-hardware@freebsd.org Received: from netcabo.pt (mail1.netcabo.pt [212.113.161.135]) by hub.freebsd.org (Postfix) with ESMTP id 945E337B405 for ; Fri, 29 Jun 2001 04:52:38 -0700 (PDT) (envelope-from OpsyDopsy@netcabo.pt) Received: from OpsyDopsy.net.dhis.org ([213.22.0.69]) by netcabo.pt with Microsoft SMTPSVC(5.5.1877.687.68); Fri, 29 Jun 2001 12:46:41 +0100 Content-Type: text/plain; charset="iso-8859-1" From: JF Reply-To: OpsyDopsy@netcabo.pt To: hardware@freebsd.org Subject: Realtek 8139 problem... Date: Fri, 29 Jun 2001 12:52:58 +0100 X-Mailer: KMail [version 1.2] MIME-Version: 1.0 Message-Id: <01062912525801.02096@OpsyDopsy.net.dhis.org> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Heys, from -questions no one could find a solution for this problem... but then again I was probably posting to the wrong list :-/ I've recently (2001/06/22) updated and rebuilt all my sources. I have a Realtek 8139 and am running IPFilter as a firewall (ipf.rules at the end) I aint connected to a LAN. Now the problem is that sometimes all my connections just start timing out, even though my cablemodem has a fixed clean signal. These timeouts happen randomly as far as I can tell and the only way to regain my connection is by powering the cable modem off and back on and running a restart DHCP client script that I will paste at the end of the mail. In windows these timeouts do not ocur. I have the same subnet mask in windows and in FBSD. Now, I cought something through syslogd that seems to be the start of the problem: Jun 29 12:34:11 OpsyDopsy /kernel: pcm0: record overrun, dumping 176896 bytes I'll paste the whole log at the end of the mail. The renewals are beeing applyed correctly (log at the end of the mail) Besides this small problem the network works perfectly fine the rest of the time. I've cought something strange in a traceroute I made (the complete traceroute is at the end of the mail) that was the first hop the packs pass is a 10.22.255.254 address when this should be if I'm not mistaken my default gateway 213.22.3.254. I will also paste a netstat -rn and a dmesg hoping these extra infos will help. I just dont know why these timeouts happen and hope someone can help me. Thanks in advance for all your time. JF PS: I've already changed the NIC from a nearer to the lower part of the box slot to a higher one... syslogd keeps giving the same error. Netstat: bash-2.05# netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 213.22.3.254 UGSc 41 22 rl0 127.0.0.1 127.0.0.1 UH 0 0 lo0 213.22/22 link#1 UC 1 0 rl0 => 213.22.3.254 0:4:28:23:ec:54 UHLW 42 0 rl0 71 Internet6: Destination Gateway Flags Netif Expire ::1 ::1 UH lo0 fe80::%rl0/64 link#1 UC rl0 fe80::%lo0/64 fe80::1%lo0 Uc lo0 ff01::/32 ::1 U lo0 ff02::%rl0/32 link#1 UC rl0 ff02::%lo0/32 fe80::1%lo0 UC lo0 Traceroute: bash-2.05# traceroute telepac.pt traceroute to telepac.pt (194.65.3.20), 30 hops max, 40 byte packets 1 10.22.255.254 (10.22.255.254) 6.978 ms 9.164 ms 9.546 ms 2 212.113.164.10 (212.113.164.10) 9.738 ms 7.296 ms 8.648 ms 3 lpc-br01-porta1.netcabo.net (212.113.161.33) 9.650 ms 7.984 ms 7.433 ms 4 213.13.128.25 (213.13.128.25) 7.529 ms 8.652 ms 9.077 ms 5 lcatrt2.telepac.net (213.13.135.90) 8.180 ms 7.984 ms 10.577 ms 6 katrt3.telepac.net (213.13.135.242) 9.508 ms 16.839 ms 10.751 ms 7 tpone.telepac.pt (194.65.3.20) 10.487 ms * 8.656 ms DHCP Renewal: Jun 22 18:58:23 OpsyDopsy dhclient: DHCPREQUEST on rl0 to 212.113.164.3 port 67 Jun 22 18:58:23 OpsyDopsy dhclient: DHCPACK from 212.113.164.3 Jun 22 18:58:23 OpsyDopsy dhclient: bound to 213.22.0.69 -- renewal in 900 seconds. DHCP Restart Script: #!/bin/sh # Kill old DHCP process /bin/kill `cat /var/run/dhclient.pid` # Delete old DHCP IP address /sbin/ifconfig rl0 inet delete # Clear the old route /sbin/route -q flush -inet # Start new dhclient process /sbin/dhclient rl0 Dmesg: Copyright (c) 1992-2001 The FreeBSD Project. Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994 The Regents of the University of California. All rights reserved. FreeBSD 4.3-STABLE #0: Fri Jun 22 15:43:46 WEST 2001 root@OpsyDopsy.net.dhis.org:/usr/obj/usr/src/sys/PIII-650 Timecounter "i8254" frequency 1193182 Hz CPU: Pentium III/Pentium III Xeon/Celeron (651.48-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x681 Stepping = 1 Features=0x383f9ff real memory = 402636800 (393200K bytes) config> di sn0 No such device: sn0 Invalid command or syntax. Type `?' for help. config> di lnc0 No such device: lnc0 Invalid command or syntax. Type `?' for help. config> di ie0 No such device: ie0 Invalid command or syntax. Type `?' for help. config> di fe0 No such device: fe0 Invalid command or syntax. Type `?' for help. config> q avail memory = 388390912 (379288K bytes) Preloaded elf kernel "kernel" at 0xc034d000. Preloaded userconfig_script "/boot/kernel.conf" at 0xc034d09c. VESA: v3.0, 4096k memory, flags:0x1, mode table:0xc02e7462 (1000022) VESA: NVidia Pentium Pro MTRR support enabled md0: Malloc disk npx0: on motherboard npx0: INT 16 interface pcib0: on motherboard pci0: on pcib0 pcib1: at device 1.0 on pci0 pci1: on pcib1 pci1: at 0.0 irq 11 isab0: at device 4.0 on pci0 isa0: on isab0 atapci0: port 0xd800-0xd80f at device 4.1 on pci0ata0: at 0x1f0 irq 14 on atapci0 ata1: at 0x170 irq 15 on atapci0 pci0: at 4.2 irq 9 chip1: port 0xe800-0xe80f at device 4.3 on pci0 pcm0: port 0xd000-0xd01f irq 5 at device 10.0 on pci0 rl0: port 0xb400-0xb4ff mem 0xc5800000-0xc58000ff irq 10 at device 11.0 on pci0 rl0: Ethernet address: 00:00:b4:c2:2d:28 miibus0: on rl0 rlphy0: on miibus0 rlphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto atapci1: port 0x9800-0x983f,0xa000-0xa003,0xa400-0xa407,0xa800-0xa803,0xb000-0xb007 mem 0xc5000000-0xc501ffff irq 5 at device 14.0 on pci0 ata2: at 0xb000 on atapci1 ata3: at 0xa400 on atapci1 orm0: 
=0A=
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I am having difficult getting a Toshiba XM-3801B SCSI CDROM (SCSI
ID#5) to work in my machine.  It is set up on a SCSI chain with a
Plextor CDR (SCSI ID#6).  The controller is an Adaptec 2940.

The Plextor CDR is /dev/cd1c; the Toshiba CD is /dev/cd0c.  cd1 is
properly detected upon boot, but the following error always occurs
for cd0:
    cd0: Attempted to query device size failed: NOT READY, Medium not
present
when there is a valid media in the drive (I know it's a valid media
because I can read it when I mount it under cd1).

cd1 seems to work perfectly well, although I haven't tried burning a
CD from it yet; but it can be mounted and read just fine.

If I try to mount_cd9660 /dev/cd0c /mnt/cd0, I receive a "device not
configured error" typically with an occasional "input/output error".

There are no other SCSI devices in the system.

Does anyone have any tips on what I should look for or what could
cause a problem like this?


Thank you,

Kevin J. Kelly=20



-----BEGIN PGP SIGNATURE-----
Version: PGPfreeware 7.0.3 for non-commercial use 
Comment: Pub key: www.homeintexas.org/pub/kjkelly.asc

iQA/AwUBOz5dtm7Q/8BlX4PkEQIvLACgoYuMMic4USrQwaeZfjyCkGg+h38AoO7Q
b3ejUQXqR5B/U66enXMrYQsy
=3D338C
-----END PGP SIGNATURE-----
=0A=
------=_NextPart_001_0001_01C10190.BAF08D90-- ------=_NextPart_000_0000_01C10190.BAEF06F0 Content-Type: application/octet-stream; name="PGPexch.htm.asc" Content-Transfer-Encoding: 7bit Content-Disposition: attachment; filename="PGPexch.htm.asc" -----BEGIN PGP MESSAGE----- Version: PGPfreeware 7.0.3 for non-commercial use Comment: Pub key: www.homeintexas.org/pub/kjkelly.asc owHVVr9vI0UUDiAKVtqCgoqCh5HuLlLsXW9iK7nYPjm2uZiLYyvZA65Ap/HuODtk d2ZvZjZmaSioEB0FDRJQIRpEhygojgaJBh3S1VT8FwjBm107l5zICa5BsWSPd358 773vfe/NfrRy47nnn9nuvPMdf/DXfXr3w99ffPbK9yufb70w19/ef/jLT60Pfu1+ /DL8/CD4YeWL21+99PCVLz+9+edw74/ffvx69zP5Sesba0WvmE/r1f6459+ZDGDX H+3B5PbO3rAHlarjvLXec5y+3y8XNmou+JJwxTQTnMSOM9ivdGyrZVY7rd1Bt2+e RgO/C5HWaZXey9hJuye4plxX/TylEJQP7Yqm72kn0km8bVtBRKSius2UqG5uNraq 9cop0OmB0WHhRKPWcGsbDc+r1TddtwKcJLR9c7A/OOj644NOy1m6sTPu3zFjf/jm cmi9Pt73YUYC2u5KRmJQ7H3a9jqtw0l3H4KYKNVuehv1emPL86rrrtv0XLfeGQJJ bCsiJ4wfgW2FbDZjQRZrOKJamzkCvlARmxJ4e1Rd33TrO3DYOxxCr38wHsG14v+w /1pj9QqfqnRbC9uaC3kMjEOSI2JCgohxWiuXYaiBKUBCIEtBcIQvEJAlPDBnOsKZ SYz8CWlMLAzYFppori5B/KgkW4o4ptIAEg7dkKSaBuBtbbi1lmPCRsYMKzj8a6Iw YRdRdR6zdOU/IF+Ii9HY1tmYMR7bckJ64gRhPdgGjeEuk9Drm+XFohssGcGNZj6V IqUyzjGRFLnQNESakWXbmgqh12Ca6QJthsSJuUkvlRKtknhOcgUiCDKpcFUiDaF7 /WlZfAKJpb9nf6G0BV2taZIal7WAexmVOWCULKAFNJpiMQ2vw/7YhwMsgztrMKIh yxLgQiNGKqnCWnrqxF/o8Tyi3LaQNUkLpaGtExKzEBI0T4zODaOhZCcUrg3hmIs5 MH3V7Dy7b0oDkikKqHWCeJKSELeBQQcj8ERkXJuZjIeoaUzo6qVSsVGgojRRyJWA ogVgUqicoQzjHOY0jtdQZzoS2VGEEWPLofwqylEyTPk0k7zsNijwmRSJYSKnGhuo 0Sw+IGvI4ZIoPEJ4CAWL72ZKw8z0mMvE13CGJGiZF3QtorobhFvNpvuovMFJuDb/ 1nCzpAE1IiNQWRSGUT72wRk7yiQNbaso5gqi6TxlAYkN70VL5aa0iSpuNqgwnmba EZnGYXnosnVMLEYisW9yAcLUJrpR3BQlM2pZlipX2FX+p+CeHMTjhssJ21rY7wtq rrVccCN6Uy3mCTRLlbk35xHRqAmF5RSHEAtxbNr2ue7rec2G6256649sAvb64iTu KQ6WPYmYi2Ma0wRidkxNs2PqxuOcLYbFZBHgzoGJdXIhh35E+PFZGv7JJdvKRbbA XTOQ5nsL08jhjRrcokbFp9Yn55N3lvWWU7wV4UuSeWOzrb8B =+090 -----END PGP MESSAGE----- ------=_NextPart_000_0000_01C10190.BAEF06F0-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message