From owner-freebsd-hardware Sun Jan 24 03:58:24 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id DAA23223 for freebsd-hardware-outgoing; Sun, 24 Jan 1999 03:58:24 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from pc144s118r1.jancomulti.com (pc144s118r1.jancomulti.com [195.139.118.144]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA23218 for ; Sun, 24 Jan 1999 03:58:21 -0800 (PST) (envelope-from psommerh@jancomulti.com) Received: from jancomulti.com (localhost [127.0.0.1]) by pc144s118r1.jancomulti.com (8.8.8/8.8.8) with ESMTP id MAA00418 for ; Sun, 24 Jan 1999 12:55:15 +0100 (CET) (envelope-from psommerh@jancomulti.com) Message-ID: <36AB0A23.2819BC0D@jancomulti.com> Date: Sun, 24 Jan 1999 12:55:15 +0100 From: "Pål Sommerhein" X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: freebsd-hardware@FreeBSD.ORG Subject: Need alternative to Intel Etherexpress Pro/100B Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I am looking for a 100Mbps ethernet card (PCI). I was told that the Intel Etherexpress Pro/100B was really nice, but I assume it is out of production as I can not find it on Intel's home page nor at local computer stores. The Intel Etherexpress Pro100+ is easy to get hold of, but in LINT I read there is no support for it. Or am I mistaken? The question is thus: Can anyone recommend a good 100Mbps ethernet card for the PCI bus? Any help appreciated, Pal Sommerhein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jan 24 04:44:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA29794 for freebsd-hardware-outgoing; Sun, 24 Jan 1999 04:44:53 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from implode.root.com (root.com [208.221.12.98]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA29789 for ; Sun, 24 Jan 1999 04:44:51 -0800 (PST) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.8/8.8.5) with ESMTP id EAA18916; Sun, 24 Jan 1999 04:41:09 -0800 (PST) Message-Id: <199901241241.EAA18916@implode.root.com> To: "P l Sommerhein" cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Need alternative to Intel Etherexpress Pro/100B In-reply-to: Your message of "Sun, 24 Jan 1999 12:55:15 +0100." <36AB0A23.2819BC0D@jancomulti.com> From: David Greenman Reply-To: dg@root.com Date: Sun, 24 Jan 1999 04:41:09 -0800 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I am looking for a 100Mbps ethernet card (PCI). I was told >that the Intel Etherexpress Pro/100B was really nice, >but I assume it is out of production as I can not find it >on Intel's home page nor at local computer stores. The >Intel Etherexpress Pro100+ is easy to get hold of, but >in LINT I read there is no support for it. Or am I >mistaken? > >The question is thus: Can anyone recommend a good 100Mbps >ethernet card for the PCI bus? The PCI Pro/100+ is functionally identical to the Pro/100B and works fine with FreeBSD. -DG David Greenman Co-founder/Principal Architect, The FreeBSD Project To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jan 24 07:57:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA16406 for freebsd-hardware-outgoing; Sun, 24 Jan 1999 07:57:21 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from xpert.com (xpert.com [199.203.132.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA16397 for ; Sun, 24 Jan 1999 07:57:18 -0800 (PST) (envelope-from elijah@xpert.com) Received: from xpert.com ([199.203.132.116]) by xpert.com (8.8.5/8.8.5) with ESMTP id RAA04023 for ; Sun, 24 Jan 1999 17:57:04 +0200 Message-ID: <36AB4469.AA152F60@xpert.com> Date: Sun, 24 Jan 1999 18:03:53 +0200 From: Elijah Kagan Reply-To: ekagan@usa.net X-Mailer: Mozilla 4.5 [en] (WinNT; I) X-Accept-Language: en MIME-Version: 1.0 Newsgroups: comp.os.linux.hardware,comp.unix.bsd.freebsd.misc To: freebsd-hardware@FreeBSD.ORG Subject: Alternative BIOS Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello all, I was wondering whether anyone has ever seen an alternative BIOS for Intel based servers that allows using serial port as a console, and not VGA. Something like Sun's eprom that can detect an absence of console and redirect all input/output to a terminal. And if so, does it work with Linux and/or FreeBSD. Thanks, Elijah Kagan PS Please, reply to me personally as well as to the group since I do not monitor them regularly. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jan 24 09:31:12 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA25434 for freebsd-hardware-outgoing; Sun, 24 Jan 1999 09:31:12 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (castles340.castles.com [208.214.167.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA25425 for ; Sun, 24 Jan 1999 09:31:10 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (LOCALHOST [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id JAA03993; Sun, 24 Jan 1999 09:27:26 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901241727.JAA03993@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: ekagan@usa.net cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Alternative BIOS In-reply-to: Your message of "Sun, 24 Jan 1999 18:03:53 +0200." <36AB4469.AA152F60@xpert.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 24 Jan 1999 09:27:25 -0800 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hello all, > > I was wondering whether anyone has ever seen an alternative BIOS for > Intel based servers that allows using serial port as a console, and not > VGA. Unfortunately, the nature of PC hardware means that the BIOS is tied very closely to the hardware itself. Thus, what you're looking for is actually a board and BIOS combination. > Something like Sun's eprom that can detect an absence of console and > redirect all input/output to a terminal. > And if so, does it work with Linux and/or FreeBSD. I've used a very nice serial console facility on the Intel AD450NX server platform; I expect that it's also available on its smaller sibling the SC450NX. These systems work just fine with FreeBSD, although you will want to be installing 3.1 to take full advantage of them. At the opposite end of the scale, Mesa Electronics have a 386sx-based board that also has a working serial console. You may find a few other vendors of embedded server products with serial BIOS support; they're going to tend to be quite a lot more expensive than a "normal" server. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jan 24 12:22:01 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA13808 for freebsd-hardware-outgoing; Sun, 24 Jan 1999 12:22:01 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from zogbe.tasam.com ([198.232.144.254]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA13779 for ; Sun, 24 Jan 1999 12:21:56 -0800 (PST) (envelope-from clash@tasam.com) Received: from bug (bug.tasam.com [205.252.239.241]) by zogbe.tasam.com (8.9.1/8.9.1) with SMTP id PAA00615; Sun, 24 Jan 1999 15:21:19 -0500 (EST) (envelope-from clash@tasam.com) Message-ID: <000e01be47d7$1bd076a0$f1effccd@bug.tasam.com> From: "Joe Gleason" To: "=?iso-8859-1?Q?P=E5l_Sommerhein?=" , Subject: Re: Need alternative to Intel Etherexpress Pro/100B Date: Sun, 24 Jan 1999 15:21:18 -0500 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.2106.4 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.2106.4 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I always like my 3com 905's or 3com 905b's. I run almost all of my systems with them. Durring my network stress testing, I got them up to 95% to 100mb without any problems. Joe Gleason Tasam >I am looking for a 100Mbps ethernet card (PCI). I was told >that the Intel Etherexpress Pro/100B was really nice, >but I assume it is out of production as I can not find it >on Intel's home page nor at local computer stores. The >Intel Etherexpress Pro100+ is easy to get hold of, but >in LINT I read there is no support for it. Or am I >mistaken? > >The question is thus: Can anyone recommend a good 100Mbps >ethernet card for the PCI bus? > >Any help appreciated, >Pal Sommerhein > >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 Sun Jan 24 14:33:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA27204 for freebsd-hardware-outgoing; Sun, 24 Jan 1999 14:33:13 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from pc144s118r1.jancomulti.com (pc144s118r1.jancomulti.com [195.139.118.144]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27199 for ; Sun, 24 Jan 1999 14:33:09 -0800 (PST) (envelope-from psommerh@jancomulti.com) Received: from jancomulti.com (localhost [127.0.0.1]) by pc144s118r1.jancomulti.com (8.8.8/8.8.8) with ESMTP id XAA00405; Sun, 24 Jan 1999 23:29:38 +0100 (CET) (envelope-from psommerh@jancomulti.com) Message-ID: <36AB9ED2.E540ACC5@jancomulti.com> Date: Sun, 24 Jan 1999 23:29:38 +0100 From: "Pål Sommerhein" X-Mailer: Mozilla 4.07 [en] (X11; I; FreeBSD 2.2.8-RELEASE i386) MIME-Version: 1.0 To: Joe Gleason CC: freebsd-hardware@FreeBSD.ORG, dg@root.com Subject: Re: Need alternative to Intel Etherexpress Pro/100B References: <000e01be47d7$1bd076a0$f1effccd@bug.tasam.com> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Joe Gleason wrote: > > I always like my 3com 905's or 3com 905b's. I run almost all of my > systems with them. > Durring my network stress testing, I got them up to 95% to 100mb > without any problems. Do you know (or anybody else :)) how the 3com 905's compare to the Intel Etherexpress Pro/100+ ? (which David Greenman just pointed out is functionally equivalent to the Intel Etherexpress 100/B. Thank you David :)) Thanks and take care, Pal Sommerhein To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun Jan 24 16:35:50 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA15428 for freebsd-hardware-outgoing; Sun, 24 Jan 1999 16:35:50 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from whizzo.transsys.com (whizzo.TransSys.COM [144.202.42.10]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA15423 for ; Sun, 24 Jan 1999 16:35:49 -0800 (PST) (envelope-from louie@whizzo.transsys.com) Received: from whizzo.transsys.com (localhost.transsys.com [127.0.0.1]) by whizzo.transsys.com (8.9.1/8.9.1) with ESMTP id TAA01003; Sun, 24 Jan 1999 19:35:17 -0500 (EST) (envelope-from louie@whizzo.transsys.com) Message-Id: <199901250035.TAA01003@whizzo.transsys.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Mike Smith cc: ekagan@usa.net, freebsd-hardware@FreeBSD.ORG From: "Louis A. Mamakos" Subject: Re: Alternative BIOS References: <199901241727.JAA03993@dingo.cdrom.com> In-reply-to: Your message of "Sun, 24 Jan 1999 09:27:25 PST." <199901241727.JAA03993@dingo.cdrom.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 24 Jan 1999 19:35:17 -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I think that Award has a BIOS extension that will do a good chunk of what you want. Of course, unless you're a hardware OEM they're not terribly interested in talking to you about how to get it. louie To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 26 07:22:41 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA17914 for freebsd-hardware-outgoing; Tue, 26 Jan 1999 07:22:41 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mail.netsys.hn ([206.48.255.45]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA17828 for ; Tue, 26 Jan 1999 07:22:16 -0800 (PST) (envelope-from freebsd@netsys.hn) Received: from [206.48.255.64] (dedicated.netsys.hn [206.48.255.64]) by mail.netsys.hn (8.9.1/8.9.1) with SMTP id JAA18820 for ; Tue, 26 Jan 1999 09:23:14 -0600 (CST) Message-Id: <199901261523.JAA18820@mail.netsys.hn> To: "freebsd-hardware@freebsd.org" Subject: SCSI-3 vrs. ATA Date: Tue, 26 Jan 99 09:22:56 -0500 From: FreeBSD Questions X-Mailer: E-Mail Connection v2.5.03 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -- [ From: FreeBSD Questions * EMC.Ver #2.5.02 ] -- Hello, this is my first message to the hardware list. I'm planning in buying a clone to put FreeBSD 2.2.8 on it. This will be used as a Web Caching Server, thus it needs a high speed disk. What would be better Quantum Fireball SE 3.2 GB SCSI-3 which price is double of the ATA or Quantum Fireball SE 3.2 GB ATA (UltraDMA)? Thanks Pablo Quintana HONDURAS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 26 08:02:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA24022 for freebsd-hardware-outgoing; Tue, 26 Jan 1999 08:02:32 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (castles360.castles.com [208.214.167.60]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA24011 for ; Tue, 26 Jan 1999 08:02:28 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id HAA17468; Tue, 26 Jan 1999 07:57:58 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901261557.HAA17468@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: FreeBSD Questions cc: "freebsd-hardware@freebsd.org" Subject: Re: SCSI-3 vrs. ATA In-reply-to: Your message of "Tue, 26 Jan 1999 09:22:56 EST." <199901261523.JAA18820@mail.netsys.hn> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 26 Jan 1999 07:57:57 -0800 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > -- [ From: FreeBSD Questions * EMC.Ver #2.5.02 ] -- > > Hello, this is my first message to the hardware list. I'm planning in buying > a clone to put FreeBSD 2.2.8 on it. This will be used as a Web Caching > Server, thus it needs a high speed disk. > > What would be better Quantum Fireball SE 3.2 GB SCSI-3 which price is double > of the ATA or Quantum Fireball SE 3.2 GB ATA (UltraDMA)? Neither. The Fireball is a low-cost disk designed for desktop systems. You should be looking at a 7200rpm SCSI disk from IBM or Seagate. -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 26 08:15:46 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25792 for freebsd-hardware-outgoing; Tue, 26 Jan 1999 08:15:46 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mail.netsys.hn ([206.48.255.45]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25775 for ; Tue, 26 Jan 1999 08:15:38 -0800 (PST) (envelope-from freebsd@netsys.hn) Received: from [206.48.255.64] (dedicated.netsys.hn [206.48.255.64]) by mail.netsys.hn (8.9.1/8.9.1) with SMTP id KAA22909; Tue, 26 Jan 1999 10:00:57 -0600 (CST) Message-Id: <199901261600.KAA22909@mail.netsys.hn> To: Vincent Fleming Subject: Re: SCSI-3 vrs. ATA Date: Tue, 26 Jan 99 10:00:40 -0500 From: FreeBSD Questions X-Mailer: E-Mail Connection v2.5.03 CC: "freebsd-hardware@freebsd.org" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -- [ From: FreeBSD Questions * EMC.Ver #2.5.02 ] -- > The SCSI drive is faster - it has an 80MB/s burst transfer rate. The ATA has > only 33MB/s burst rate. According to the Quantum Spec Sheet on the Web http://www.quantum. com/products/hdd/fireball_se/datasheet.html the speed for the ATA is 33.3MB/s and 20MB/s for the SCSI-3 I'm sorry to insist with Quantum but here that is the only choice I have. > Vince > > > Hello, this is my first message to the hardware list. I'm planning in buying > > a clone to put FreeBSD 2.2.8 on it. This will be used as a Web Caching > > Server, thus it needs a high speed disk. > > > > What would be better Quantum Fireball SE 3.2 GB SCSI-3 which price is double > > of the ATA or Quantum Fireball SE 3.2 GB ATA (UltraDMA)? > > > > Thanks > > > > Pablo Quintana > > HONDURAS Pablo Quintana HONDURAS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 26 08:43:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29060 for freebsd-hardware-outgoing; Tue, 26 Jan 1999 08:43:14 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from paprika.michvhf.com (paprika.michvhf.com [209.57.60.12]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id IAA29053 for ; Tue, 26 Jan 1999 08:43:11 -0800 (PST) (envelope-from vev@michvhf.com) Received: (qmail 6138 invoked by uid 1001); 26 Jan 1999 16:43:08 -0000 Date: Tue, 26 Jan 1999 11:43:08 -0500 (EST) From: Vince Vielhaber To: FreeBSD Questions cc: "freebsd-hardware@freebsd.org" Subject: Re: SCSI-3 vrs. ATA In-Reply-To: <199901261600.KAA22909@mail.netsys.hn> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 26 Jan 1999, FreeBSD Questions wrote: > -- [ From: FreeBSD Questions * EMC.Ver #2.5.02 ] -- > > > The SCSI drive is faster - it has an 80MB/s burst transfer rate. The ATA > has > > only 33MB/s burst rate. > > According to the Quantum Spec Sheet on the Web http://www.quantum. > com/products/hdd/fireball_se/datasheet.html > the speed for the ATA is 33.3MB/s and 20MB/s for the SCSI-3 > > I'm sorry to insist with Quantum but here that is the only choice I have. If this is going into something that's going to be worked so hard as to need that kind of transfer rate, an IDE won't last. In less than 90 days I destroyed one and it was only keeping the history file on a news feeder. Vince. -- ========================================================================== Vince Vielhaber -- KA8CSH email: vev@michvhf.com flame-mail: /dev/null # include TEAM-OS2 Online Searchable Campground Listings http://www.camping-usa.com "There is no outfit less entitled to lecture me about bloat than the federal government" -- Tony Snow ========================================================================== To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 26 09:18:31 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02669 for freebsd-hardware-outgoing; Tue, 26 Jan 1999 09:18:31 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from colosso.fisica.ist.edu ([193.136.100.65]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02664 for ; Tue, 26 Jan 1999 09:18:23 -0800 (PST) (envelope-from gabriel@maquina.com) Received: from localhost (gabriel@localhost) by colosso.fisica.ist.edu (8.9.1a/8.9.1) with ESMTP id RAA13931; Tue, 26 Jan 1999 17:16:41 GMT X-Authentication-Warning: colosso.fisica.ist.edu: gabriel owned process doing -bs Date: Tue, 26 Jan 1999 17:16:41 +0000 (WET) From: Jose Gabriel Marcelino To: FreeBSD Questions cc: "freebsd-hardware@freebsd.org" Subject: Re: SCSI-3 vrs. ATA In-Reply-To: <199901261523.JAA18820@mail.netsys.hn> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > What would be better Quantum Fireball SE 3.2 GB SCSI-3 which price is double > of the ATA or Quantum Fireball SE 3.2 GB ATA (UltraDMA)? I would say neither, but as you are constrained to them do chose the ATA version because for the trash they are for a server at least you're paying less. Let me warn you that these disks were giving lots of problems, in 24 systems we had 7 faulty disks these summer. I would prefer the new version, the Fireball EX ATA version which are excellent disks for the price. If you want SCSI do go for the Viking if your stuck with Quantum or IBM / Seagate if you're free :-) -- Jose Marcelino To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 26 13:27:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02726 for freebsd-hardware-outgoing; Tue, 26 Jan 1999 13:27:19 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02720 for ; Tue, 26 Jan 1999 13:27:17 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id WAA07534 for freebsd-hardware@FreeBSD.ORG; Tue, 26 Jan 1999 22:27:12 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 75E1A1513; Tue, 26 Jan 1999 22:01:06 +0100 (CET) Date: Tue, 26 Jan 1999 22:01:06 +0100 From: Ollivier Robert To: "freebsd-hardware@freebsd.org" Subject: Re: SCSI-3 vrs. ATA Message-ID: <19990126220106.A77068@keltia.freenix.fr> Mail-Followup-To: "freebsd-hardware@freebsd.org" References: <199901261523.JAA18820@mail.netsys.hn> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199901261523.JAA18820@mail.netsys.hn>; from FreeBSD Questions on Tue, Jan 26, 1999 at 09:22:56AM -0500 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4994 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to FreeBSD Questions: > What would be better Quantum Fireball SE 3.2 GB SCSI-3 which price is double > of the ATA or Quantum Fireball SE 3.2 GB ATA (UltraDMA)? Stay away from the Fireball for your sake (your data's really). If you can't buy anything else than Quantum, buy a Ultrawide VikingII. It is working great and fast. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 26 13:27:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA02757 for freebsd-hardware-outgoing; Tue, 26 Jan 1999 13:27:27 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA02741 for ; Tue, 26 Jan 1999 13:27:23 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id WAA07535 for freebsd-hardware@FreeBSD.ORG; Tue, 26 Jan 1999 22:27:21 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 4244F1513; Tue, 26 Jan 1999 22:05:10 +0100 (CET) Date: Tue, 26 Jan 1999 22:05:10 +0100 From: Ollivier Robert To: "freebsd-hardware@freebsd.org" Subject: Re: SCSI-3 vrs. ATA Message-ID: <19990126220510.B77068@keltia.freenix.fr> Mail-Followup-To: "freebsd-hardware@freebsd.org" References: <199901261600.KAA22909@mail.netsys.hn> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199901261600.KAA22909@mail.netsys.hn>; from FreeBSD Questions on Tue, Jan 26, 1999 at 10:00:40AM -0500 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4994 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to FreeBSD Questions: > According to the Quantum Spec Sheet on the Web http://www.quantum. > com/products/hdd/fireball_se/datasheet.html > the speed for the ATA is 33.3MB/s and 20MB/s for the SCSI-3 The drive is not able to deliver data that fast. The best you can have now is around 12 MB/s (maybe a bit more but not much). Don't mistake the _bus_ speed with the _drive_ speed. ATA UDMA is a 33 MB/s bus and that seems to be near an UW drive (40 MB/s) but you won't never get that kind of speed from any drive. If you're using a single drive configuration, take either UDMA or SCSI. The only difference you may see is in CPU cycles consumption. SCSI will probably eat a bit less than ATA. If you begin to have more peripherals, like a CD-ROM or a second or third drive, go for SCSI. The disconnect & tagged commands features of SCSI will give you more performance on concurrent accesses than ATA. -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 26 13:35:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA03619 for freebsd-hardware-outgoing; Tue, 26 Jan 1999 13:35:13 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from fw.bhmi.com (fw.bhmi.com [206.153.216.249]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA03601 for ; Tue, 26 Jan 1999 13:35:06 -0800 (PST) (envelope-from dwebster@bhmi.com) Received: from david (david.whq.bhmi.com [172.16.1.195] (may be forged)) by fw.bhmi.com (2.5 Build 2630 (Berkeley 8.8.6)/8.8.4) with ESMTP id PAA06292; Tue, 26 Jan 1999 15:34:50 -0600 Message-ID: <36AE34CA.576A7830@bhmi.com> Date: Tue, 26 Jan 1999 15:34:02 -0600 From: David Webster Organization: BHM X-Mailer: Mozilla 4.01 [en] (WinNT; I) MIME-Version: 1.0 To: Ollivier Robert CC: "freebsd-hardware@freebsd.org" Subject: Re: SCSI-3 vrs. ATA X-Priority: 3 (Normal) References: <199901261523.JAA18820@mail.netsys.hn> <19990126220106.A77068@keltia.freenix.fr> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Agreed. I know sometimes people are on tight budgets, but if this server is for a business, going cheap will cost you plenty, not in just down time but lost productivity as well. if you can afford it in any way get your self a reputable Raid controller and at least three 10,000RPM Ultrawide SCSI drives from someone like Seagate in a Raid5 array. The cost is WELL worth it. Can't imagine running an UltraDMA drive in a server. But if you're just screwing around at home, who cares???? Ollivier Robert wrote: > According to FreeBSD Questions: > > What would be better Quantum Fireball SE 3.2 GB SCSI-3 which price > is double > > of the ATA or Quantum Fireball SE 3.2 GB ATA (UltraDMA)? > > Stay away from the Fireball for your sake (your data's really). If you > > can't buy anything else than Quantum, buy a Ultrawide VikingII. It is > working great and fast. > -- > Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- > roberto@keltia.freenix.fr > FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET > 1999 > > 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 Tue Jan 26 18:45:13 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA11904 for freebsd-hardware-outgoing; Tue, 26 Jan 1999 18:45:13 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from vespucci.advicom.net (vespucci.advicom.net [199.170.120.42]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA11887; Tue, 26 Jan 1999 18:45:10 -0800 (PST) (envelope-from avalon@vespucci.advicom.net) Received: from localhost (avalon@localhost) by vespucci.advicom.net (8.8.8/8.8.5) with ESMTP id UAA01613; Tue, 26 Jan 1999 20:44:59 -0600 (CST) X-Envelope-Recipient: freebsd-isdn@freebsd.org Date: Tue, 26 Jan 1999 20:44:59 -0600 (CST) From: Avalon Books To: freebsd-hardware@FreeBSD.ORG cc: freebsd-isdn@FreeBSD.ORG Subject: Up and coming support page for ISDN Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This message is directed towards North American FreeBSD users who are currently using ISDN with their systems. Due to an apparent lack of support for North American ISDN in the FreeBSD community, myself and a fellow telecommunications expert will be starting the Unofficial North American FreeBSD ISDN Support Page--and we need your help to fill this void in our support network. We need detailed information from current North American ISDN subscribers on *exactly* what equipment you are using, *exactly* how you set it up, and why you chose the hardware you use. Terminal adapters, routers, whatever--it doesn't matter. These documents will be posted on our page to assist others in need of either technical support or those contemplating an upgrade to ISDN, and need to know what works (and what doesn't). The authors will also be making themselves available to answer questions, etc. Full credit will be giving for all submissions. And let us know if you want your email address included for questions (if not, we will omit them in order to prevent unwanted mail). Also, any experiences relating to hardware that *didn't* work could prove helpful, so feel free to include such material if you wish. As we will also be including links to manufacturer's sites, suggestions for new links are also appreciated. Note, however, that we will be orienting this page towards products available in the North American market, and suggestions should be tempered accordingly. This support page will be put on-line as soon as we have enough material to do so. The more material I get, the more quickly this page will spring into existance. Please mail me directly with any material you wish to submit. Thank you in advance for your help. --R. Pelletier (avalon@advicom.net) Sys Admin, House Galiagante We are a Micro$oft-free site To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 26 19:35:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA16536 for freebsd-hardware-outgoing; Tue, 26 Jan 1999 19:35:27 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA16518 for ; Tue, 26 Jan 1999 19:35:15 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id EAA23954 for freebsd-hardware@FreeBSD.ORG; Wed, 27 Jan 1999 04:35:04 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 860A51513; Wed, 27 Jan 1999 00:24:42 +0100 (CET) Date: Wed, 27 Jan 1999 00:24:42 +0100 From: Ollivier Robert To: "freebsd-hardware@freebsd.org" Subject: Re: SCSI-3 vrs. ATA Message-ID: <19990127002442.A78002@keltia.freenix.fr> Mail-Followup-To: "freebsd-hardware@freebsd.org" References: <199901261523.JAA18820@mail.netsys.hn> <19990126220106.A77068@keltia.freenix.fr> <36AE34CA.576A7830@bhmi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <36AE34CA.576A7830@bhmi.com>; from David Webster on Tue, Jan 26, 1999 at 03:34:02PM -0600 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4994 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to David Webster: > way get your self a reputable Raid controller and at least three > 10,000RPM Ultrawide SCSI drives from someone like Seagate in a Raid5 Well, we could argue about the 10k rpms drives. Is there so big a difference with 7200 rpms ones ? It seems to me that 10k are only slightly faster but they're warmer and noisier. > But if you're just screwing around at home, who cares???? Don't tell that to my machine at home, it has 2 SCSI controllers and 4 disks (2 UW, 1 ultra and one narrow), a DAT, a CD and a Tandberg streamer) :-) -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 26 21:18:30 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA28139 for freebsd-hardware-outgoing; Tue, 26 Jan 1999 21:18:30 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from panzer.plutotech.com (panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA28134 for ; Tue, 26 Jan 1999 21:18:28 -0800 (PST) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.9.2/8.8.5) id WAA48800; Tue, 26 Jan 1999 22:18:13 -0700 (MST) From: "Kenneth D. Merry" Message-Id: <199901270518.WAA48800@panzer.plutotech.com> Subject: Re: SCSI-3 vrs. ATA In-Reply-To: <19990127002442.A78002@keltia.freenix.fr> from Ollivier Robert at "Jan 27, 99 00:24:42 am" To: roberto@keltia.freenix.fr (Ollivier Robert) Date: Tue, 26 Jan 1999 22:18:13 -0700 (MST) Cc: freebsd-hardware@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL28s (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Ollivier Robert wrote... > According to David Webster: > > way get your self a reputable Raid controller and at least three > > 10,000RPM Ultrawide SCSI drives from someone like Seagate in a Raid5 > > Well, we could argue about the 10k rpms drives. Is there so big a > difference with 7200 rpms ones ? It seems to me that 10k are only slightly > faster but they're warmer and noisier. How many 7200 RPM drives can do 18MB/sec? I've got a machine with two 18GB Seagate Cheetah II's in a CCD array. They can do 36MB/sec reads, and 30 or 31MB/sec writes. The third generation Cheetahs look like they'll be even faster. [ NB: the read rate *could* be a little low, since there is one other disk on the chain, and unfortunately the SCA->68pin converters we have seem to force single ended operation. i.e., we're limited to 20MHz Wide instead of 40MHz Wide. ] My IBM Ultrastar 9ZX can do between 13 and 15MB/sec. For a good comparison, go to the Seagate or IBM web sites, and compare their latest-generation 7200 RPM drives with their latest-generation 10000 RPM drives. It looks like for both vendors, their 10K RPM drives are generally about 5MB/sec faster than their 7200RPM drives. Ken -- Kenneth Merry ken@plutotech.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 26 22:26:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA04299 for freebsd-hardware-outgoing; Tue, 26 Jan 1999 22:26:25 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA04294 for ; Tue, 26 Jan 1999 22:26:23 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost (480 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Tue, 26 Jan 1999 22:26:23 -0800 (PST) (Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13) Message-Id: Date: Tue, 26 Jan 1999 22:26:23 -0800 (PST) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: "Kenneth D. Merry" Cc: freebsd-hardware@FreeBSD.ORG Subject: Re: SCSI-3 vrs. ATA References: <19990127002442.A78002@keltia.freenix.fr> <199901270518.WAA48800@panzer.plutotech.com> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org i prefer to get multiple slower, and hence quieter, drives and stripe them. randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 26 22:46:49 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA05865 for freebsd-hardware-outgoing; Tue, 26 Jan 1999 22:46:49 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ns.koganei.wide.ad.jp (ns.koganei.wide.ad.jp [203.178.148.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA05860 for ; Tue, 26 Jan 1999 22:46:47 -0800 (PST) (envelope-from ikob@koganei.wide.ad.jp) Received: from localhost (eeyore.koganei.wide.ad.jp [203.178.148.35]) by ns.koganei.wide.ad.jp (8.8.5/3.6W) with ESMTP id PAA15418 for ; Wed, 27 Jan 1999 15:46:25 +0900 (JST) To: hardware@FreeBSD.ORG Subject: Firewire[IEEE1394] device driver. [alpha release] X-Mailer: Mew version 1.92 on XEmacs 20.4 (Emerald) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990127154637M.ikob@koganei.wide.ad.jp> Date: Wed, 27 Jan 1999 15:46:37 +0900 From: Katsushi Kobayashi X-Dispatcher: imput version 971024 Lines: 29 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hello, I have been implementing firewire device driver for FreeBSD. Today, I announce the first public release of the driver I developed. The driver only has limited functions now and the IP implementation is not accord any Internet Draft submitted to IETF due to chipset restriction. But, my driver will be helpful some people for following purposes: - To use DV equipements. - To use raw 1394 functions. I will release improved driver in the next time. My driver supports only Texas Instruments' PCILynx chipset only. This chip set is equipped on Radius (Now Digital Origin?) Photo DV/Moto DV firewire card. You can obtain the driver from ftp://new-tremaine.cc.uec.ac.jp/pub/firewire The related URL (ML information and others) is as follows: http://www.sfc.wide.ad.jp/DVTS Katsushi Kobayashi ikob@koganei.wide.ad.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jan 26 23:04:10 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id XAA07893 for freebsd-hardware-outgoing; Tue, 26 Jan 1999 23:04:10 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from frmug.org (frmug-gw.frmug.org [193.56.58.252]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id XAA07884 for ; Tue, 26 Jan 1999 23:04:07 -0800 (PST) (envelope-from roberto@keltia.freenix.fr) Received: (from uucp@localhost) by frmug.org (8.9.1/frmug-2.3/nospam) with UUCP id IAA02594 for freebsd-hardware@FreeBSD.ORG; Wed, 27 Jan 1999 08:03:59 +0100 (CET) (envelope-from roberto@keltia.freenix.fr) Received: by keltia.freenix.fr (Postfix, from userid 101) id 1A0A31513; Wed, 27 Jan 1999 07:44:01 +0100 (CET) Date: Wed, 27 Jan 1999 07:44:01 +0100 From: Ollivier Robert To: freebsd-hardware@FreeBSD.ORG Subject: Re: SCSI-3 vrs. ATA Message-ID: <19990127074401.B80418@keltia.freenix.fr> Mail-Followup-To: freebsd-hardware@FreeBSD.ORG References: <19990127002442.A78002@keltia.freenix.fr> <199901270518.WAA48800@panzer.plutotech.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95i In-Reply-To: <199901270518.WAA48800@panzer.plutotech.com>; from Kenneth D. Merry on Tue, Jan 26, 1999 at 10:18:13PM -0700 X-Operating-System: FreeBSD 3.0-CURRENT/ELF ctm#4994 AMD-K6 MMX @ 200 MHz Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org According to Kenneth D. Merry: > Seagate Cheetah II's in a CCD array. They can do 36MB/sec reads, and 30 or > 31MB/sec writes. The third generation Cheetahs look like they'll be even Nice. I haven't tested very recent drives so my experience may be as you see outdated now. > RPM drives. It looks like for both vendors, their 10K RPM drives are > generally about 5MB/sec faster than their 7200RPM drives. Without being too warm I hope. The IBM drives seems to stay very cool... -- Ollivier ROBERT -=- FreeBSD: The Power to Serve! -=- roberto@keltia.freenix.fr FreeBSD keltia.freenix.fr 3.0-CURRENT #69: Mon Jan 18 02:02:12 CET 1999 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jan 27 06:57:29 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA23734 for freebsd-hardware-outgoing; Wed, 27 Jan 1999 06:57:29 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from rip.psg.com (rip.psg.com [147.28.0.39]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA23724 for ; Wed, 27 Jan 1999 06:57:28 -0800 (PST) (envelope-from randy@psg.com) Received: from localhost (413 bytes) by rip.psg.com via sendmail with P:stdio/R:inet_resolve/T:smtp (sender: ) (ident using unix) id for ; Wed, 27 Jan 1999 06:57:27 -0800 (PST) (Smail-3.2.0.101 1997-Dec-17 #1 built 1998-Oct-13) Message-Id: Date: Wed, 27 Jan 1999 06:57:27 -0800 (PST) From: Randy Bush MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit To: freebsd-hardware@FreeBSD.ORG Subject: Matrox m-2 and X Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Am I correct that the best X driver for a vga0: rev 0x00 int a irq 11 on pci1.0.0 on AGP is the SVGA driver? randy To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jan 27 08:42:09 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA07548 for freebsd-hardware-outgoing; Wed, 27 Jan 1999 08:42:09 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from polaris.we.lc.ehu.es (polaris.we.lc.ehu.es [158.227.6.43]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA07427 for ; Wed, 27 Jan 1999 08:41:33 -0800 (PST) (envelope-from jose@we.lc.ehu.es) Received: from we.lc.ehu.es (tiburon [158.227.6.111]) by polaris.we.lc.ehu.es (8.9.1/8.9.1) with ESMTP id RAA17446; Wed, 27 Jan 1999 17:36:36 +0100 (MET) Message-ID: <36AF408E.8B35A675@we.lc.ehu.es> Date: Wed, 27 Jan 1999 17:36:30 +0100 From: "Jose M. Alcaide" Organization: Universidad del Pais Vasco - Dept. de Electricidad y Electronica X-Mailer: Mozilla 4.07 [en] (X11; U; FreeBSD 3.0-STABLE i386) MIME-Version: 1.0 To: Randy Bush CC: freebsd-hardware@FreeBSD.ORG Subject: Re: Matrox m-2 and X References: Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Randy Bush wrote: > > Am I correct that the best X driver for a > > vga0: rev 0x00 int a irq 11 on pci1.0.0 > > on AGP is the SVGA driver? > Yes. Include a "VideoRam XXXX" in the Device section of your XF86Config, specifying the exact amount of VideoRam your card has. For example, "VideoRam 8192" for a Millennium II with 8MB. The reason is that, sometimes, the SVGA Xserver fails when trying to detect the amount of VRAM installed, crashing the entire system. -- JM ----------------------------------------------------------------------- José Mª Alcaide | mailto:jose@we.lc.ehu.es Universidad del País Vasco | http://www.we.lc.ehu.es/~jose Dpto. de Electricidad y Electrónica | Facultad de Ciencias - Campus de Lejona | Tel.: +34-946012479 48940 Lejona (Vizcaya) - SPAIN | Fax: +34-944858139 ----------------------------------------------------------------------- "Go ahead... make my day." - H. Callahan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jan 27 09:12:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA11076 for freebsd-hardware-outgoing; Wed, 27 Jan 1999 09:12:39 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from feral-gw.feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA11066 for ; Wed, 27 Jan 1999 09:12:31 -0800 (PST) (envelope-from mjacob@feral.com) Received: from localhost (mjacob@localhost) by feral-gw.feral.com (8.8.7/8.8.7) with ESMTP id JAA25136; Wed, 27 Jan 1999 09:11:43 -0800 Date: Wed, 27 Jan 1999 09:11:42 -0800 (PST) From: Matthew Jacob X-Sender: mjacob@feral-gw Reply-To: mjacob@feral.com To: Katsushi Kobayashi cc: hardware@FreeBSD.ORG Subject: Re: Firewire[IEEE1394] device driver. [alpha release] In-Reply-To: <19990127154637M.ikob@koganei.wide.ad.jp> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Very good! On Wed, 27 Jan 1999, Katsushi Kobayashi wrote: > > Hello, > > I have been implementing firewire device driver for FreeBSD. > Today, I announce the first public release of the driver I developed. > The driver only has limited functions now and the IP implementation is > not accord any Internet Draft submitted to IETF due to chipset > restriction. > > But, my driver will be helpful some people for following purposes: > > - To use DV equipements. > - To use raw 1394 functions. > > I will release improved driver in the next time. My driver supports only > Texas Instruments' PCILynx chipset only. This chip set is equipped on > Radius (Now Digital Origin?) Photo DV/Moto DV firewire card. > > You can obtain the driver from > > ftp://new-tremaine.cc.uec.ac.jp/pub/firewire > > The related URL (ML information and others) is as follows: > > http://www.sfc.wide.ad.jp/DVTS > > > Katsushi Kobayashi > ikob@koganei.wide.ad.jp > > 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 Wed Jan 27 11:51:27 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA01165 for freebsd-hardware-outgoing; Wed, 27 Jan 1999 11:51:27 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from alpo.whistle.com (alpo.whistle.com [207.76.204.38]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA01160 for ; Wed, 27 Jan 1999 11:51:25 -0800 (PST) (envelope-from julian@whistle.com) Received: (from daemon@localhost) by alpo.whistle.com (8.8.5/8.8.5) id LAA01480; Wed, 27 Jan 1999 11:42:46 -0800 (PST) Received: from current1.whistle.com(207.76.205.22) via SMTP by alpo.whistle.com, id smtpdfp1469; Wed Jan 27 19:42:39 1999 Date: Wed, 27 Jan 1999 11:42:34 -0800 (PST) From: Julian Elischer To: Matthew Jacob cc: Katsushi Kobayashi , hardware@FreeBSD.ORG Subject: Re: Firewire[IEEE1394] device driver. [alpha release] In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org is it based on the existing NetBSD code? On Wed, 27 Jan 1999, Matthew Jacob wrote: > > Very good! > > > > On Wed, 27 Jan 1999, Katsushi Kobayashi wrote: > > > > > Hello, > > > > I have been implementing firewire device driver for FreeBSD. > > Today, I announce the first public release of the driver I developed. > > The driver only has limited functions now and the IP implementation is > > not accord any Internet Draft submitted to IETF due to chipset > > restriction. > > > > But, my driver will be helpful some people for following purposes: > > > > - To use DV equipements. > > - To use raw 1394 functions. > > > > I will release improved driver in the next time. My driver supports only > > Texas Instruments' PCILynx chipset only. This chip set is equipped on > > Radius (Now Digital Origin?) Photo DV/Moto DV firewire card. > > > > You can obtain the driver from > > > > ftp://new-tremaine.cc.uec.ac.jp/pub/firewire > > > > The related URL (ML information and others) is as follows: > > > > http://www.sfc.wide.ad.jp/DVTS > > > > > > Katsushi Kobayashi > > ikob@koganei.wide.ad.jp > > > > 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 Wed Jan 27 14:54:33 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25273 for freebsd-hardware-outgoing; Wed, 27 Jan 1999 14:54:33 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from sasami.jurai.net (sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA25266 for ; Wed, 27 Jan 1999 14:54:32 -0800 (PST) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id RAA27955; Wed, 27 Jan 1999 17:54:08 -0500 (EST) Date: Wed, 27 Jan 1999 17:54:07 -0500 (EST) From: "Matthew N. Dodd" To: Ollivier Robert cc: "freebsd-hardware@freebsd.org" Subject: Re: SCSI-3 vrs. ATA In-Reply-To: <19990126220510.B77068@keltia.freenix.fr> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Tue, 26 Jan 1999, Ollivier Robert wrote: > If you begin to have more peripherals, like a CD-ROM or a second or > third drive, go for SCSI. The disconnect & tagged commands features of > SCSI will give you more performance on concurrent accesses than ATA. We found that multiple drives are fine so long as they are masters. IE: 1 driver per IDE interface. Using IBM 10 gig drives, 2 drives goes quite a long ways. I'd imagine that buying a PCI EIDE board for channels 3 and 4 would be of some benefit for a 'server' that doesn't need the IRQs for anything else. Not the greatest performance solution, but quite a bit of bang for the buck. -- | Matthew N. Dodd | 78 280Z | 75 164E | 84 245DL | FreeBSD/NetBSD/Sprite/VMS | | winter@jurai.net | This Space For Rent | ix86,sparc,m68k,pmax,vax | | http://www.jurai.net/~winter | Are you k-rad elite enough for my webpage? | To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jan 27 16:03:04 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA04725 for freebsd-hardware-outgoing; Wed, 27 Jan 1999 16:03:04 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ns.koganei.wide.ad.jp (ns.koganei.wide.ad.jp [203.178.148.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA04711 for ; Wed, 27 Jan 1999 16:02:57 -0800 (PST) (envelope-from ikob@koganei.wide.ad.jp) Received: from localhost (eeyore.koganei.wide.ad.jp [203.178.148.35]) by ns.koganei.wide.ad.jp (8.8.5/3.6W) with ESMTP id JAA18266; Thu, 28 Jan 1999 09:02:40 +0900 (JST) To: julian@whistle.com Cc: mjacob@feral.com, hardware@FreeBSD.ORG Subject: Re: Firewire[IEEE1394] device driver. [alpha release] In-Reply-To: Your message of "Wed, 27 Jan 1999 11:42:34 -0800 (PST)" References: X-Mailer: Mew version 1.92 on Emacs 19.28 / Mule 2.3 (SUETSUMUHANA) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit Message-Id: <19990128090246O.ikob@koganei.wide.ad.jp> Date: Thu, 28 Jan 1999 09:02:46 +0900 From: Katsushi Kobayashi X-Dispatcher: imput version 971024 Lines: 13 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org From: Julian Elischer Subject: Re: Firewire[IEEE1394] device driver. [alpha release] Date: Wed, 27 Jan 1999 11:42:34 -0800 (PST) > > is it based on the existing NetBSD code? > No. But, I think it is not difficult to port other 4.4Lite derived sustem. Katsushi Kobayashi ikob@koganei.wide.ad.jp To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jan 27 18:57:44 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA25122 for freebsd-hardware-outgoing; Wed, 27 Jan 1999 18:57:44 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mail.netsys.hn ([206.48.255.45]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA24954; Wed, 27 Jan 1999 18:57:00 -0800 (PST) (envelope-from freebsd@netsys.hn) Received: from [206.48.255.64] (dedicated.netsys.hn [206.48.255.64]) by mail.netsys.hn (8.9.1/8.9.1) with SMTP id UAA01350; Wed, 27 Jan 1999 20:56:49 -0600 (CST) Message-Id: <199901280256.UAA01350@mail.netsys.hn> To: "freebsd-questions@FreeBSD.ORG" , "freebsd-hardware@freebsd.org" Subject: Your opinion please! Date: Wed, 27 Jan 99 20:57:10 -0500 From: FreeBSD Questions X-Mailer: E-Mail Connection v2.5.03 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org -- [ From: FreeBSD Questions * EMC.Ver #2.5.02 ] -- Sorry guys to ask this here, but I don't know other reliable source of information and founded opinions on the net. For those who are using Proxy Caching: What do you think is better, Squid or the Proxy Module from Apache? Thanks a lot for your feedback. Pablo Quintana HONDURAS To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Wed Jan 27 22:53:06 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA24628 for freebsd-hardware-outgoing; Wed, 27 Jan 1999 22:53:06 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from house.key.net.au (house.key.net.au [203.35.4.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA24609; Wed, 27 Jan 1999 22:52:57 -0800 (PST) (envelope-from keith@apcs.com.au) Received: (from uucp@localhost) by house.key.net.au (8.8.8/8.8.8) id RAA13912; Thu, 28 Jan 1999 17:52:24 +1100 (EST) (envelope-from keith@apcs.com.au) Received: from well.apcs.com.au(203.35.4.19) via SMTP by mailgw.key.net.au, id smtpdv13910; Thu Jan 28 17:52:20 1999 Message-ID: X-Mailer: XFMail 1.3 [p0] on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit MIME-Version: 1.0 In-Reply-To: <199901280256.UAA01350@mail.netsys.hn> Date: Thu, 28 Jan 1999 17:54:08 +1100 (EST) Reply-To: keith@apcs.com.au Organization: Australia Power Control Systems P/L From: Keith Anderson To: FreeBSD Questions Subject: RE: Your opinion please! Cc: "freebsd-hardware@freebsd.org" Cc: "freebsd-hardware@freebsd.org" , "freebsd-questions@FreeBSD.ORG" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Squid Squid is good Squid is great Keith Anderson On 28-Jan-99 FreeBSD Questions wrote: > -- [ From: FreeBSD Questions * EMC.Ver #2.5.02 ] -- > > Sorry guys to ask this here, but I don't know other reliable source of > information and founded opinions on the net. > > For those who are using Proxy Caching: > > What do you think is better, Squid or the Proxy Module from Apache? > > Thanks a lot for your feedback. > > Pablo Quintana > HONDURAS > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message --- ---------------------------------- E-Mail: Keith Anderson Date: 28-Jan-99 Time: 17:53:05 Satelite Service 64K to 2Meg This message was sent by XFMail ---------------------------------- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jan 28 05:27:14 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id FAA15846 for freebsd-hardware-outgoing; Thu, 28 Jan 1999 05:27:14 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from ns.ge.com (ns.ge.com [192.35.39.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id FAA15825; Thu, 28 Jan 1999 05:27:08 -0800 (PST) (envelope-from steve.combs@indsys.ge.com) Received: from thomas.ge.com (thomas3.ge.com [3.47.28.19]) by ns.ge.com (8.9.1/8.9.1) with ESMTP id IAA24183; Thu, 28 Jan 1999 08:27:06 -0500 (EST) Received: from carsdb.salem.ge.com (carsdb.salem.ge.com [3.29.7.15]) by thomas.ge.com (8.9.1/8.9.1) with ESMTP id IAA25094; Thu, 28 Jan 1999 08:27:02 -0500 (EST) Received: from indsys.ge.com (combssf.salem.ge.com [3.29.24.77]) by carsdb.salem.ge.com (8.8.8/8.8.8) with ESMTP id IAA24435; Thu, 28 Jan 1999 08:23:13 -0500 (EST) Message-ID: <36B064C1.83A8A1A4@indsys.ge.com> Date: Thu, 28 Jan 1999 08:23:13 -0500 From: "Stephen F. Combs" Reply-To: steve.combs@indsys.ge.com Organization: GE Industrial Systems (Global Security & Messaging) X-Mailer: Mozilla 4.5 [en] (WinNT; U) X-Accept-Language: en MIME-Version: 1.0 To: FreeBSD Questions CC: "freebsd-questions@FreeBSD.ORG" , "freebsd-hardware@freebsd.org" Subject: Re: Your opinion please! References: <199901280256.UAA01350@mail.netsys.hn> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I've been running Squid on two FBSD machines and two SPARCs for over a year. Beats Netscape proxy AND apache hands down FreeBSD Questions wrote: > -- [ From: FreeBSD Questions * EMC.Ver #2.5.02 ] -- > > Sorry guys to ask this here, but I don't know other reliable source of > information and founded opinions on the net. > > For those who are using Proxy Caching: > > What do you think is better, Squid or the Proxy Module from Apache? > > Thanks a lot for your feedback. > > Pablo Quintana > HONDURAS > > 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 Fri Jan 29 12:54:39 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA10273 for freebsd-hardware-outgoing; Fri, 29 Jan 1999 12:54:39 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mailc.telia.com (mailc.telia.com [194.22.190.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA10265 for ; Fri, 29 Jan 1999 12:54:37 -0800 (PST) (envelope-from s.lindgren@telia.com) Received: from d1o49.telia.com (root@d1o49.telia.com [195.198.194.241]) by mailc.telia.com (8.8.8/8.8.8) with ESMTP id VAA21733 for ; Fri, 29 Jan 1999 21:54:35 +0100 (CET) Received: from telia.com (t2o49p41.telia.com [195.198.194.101]) by d1o49.telia.com (8.8.8/8.8.5) with ESMTP id VAA17046 for ; Fri, 29 Jan 1999 21:54:34 +0100 (CET) Message-ID: <36DAFE8B.5849912A@telia.com> Date: Mon, 01 Mar 1999 21:54:35 +0100 From: Stefan Lindgren X-Mailer: Mozilla 4.5 [sv] (Win98; I) X-Accept-Language: sv MIME-Version: 1.0 To: hardware@FreeBSD.ORG Subject: Where to get a Quad PPRO 450 GX? Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all. Does somebody know a place to get a Quad PPRO MB? (Pref. international netshop) Thanks in advance Stefan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jan 29 14:39:32 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23538 for freebsd-hardware-outgoing; Fri, 29 Jan 1999 14:39:32 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23516; Fri, 29 Jan 1999 14:39:27 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id RAA01940; Fri, 29 Jan 1999 17:39:23 -0500 (EST) Message-ID: <19990129173922.A29551@netmonger.net> Date: Fri, 29 Jan 1999 17:39:22 -0500 From: Christopher Masto To: hardware@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Network/ARP problem? Maybe pn driver? Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I hope I'm not just being really stupid, but I think there's a problem somewhere. If it's a configuration error on my part, then I think I'd better take a vacation, considering what my job is supposed to be. Anyway, I have a machine that is exhibiting a weird network problem. My guess is that ARP is not working, or perhaps something that ARP depends on (broadcasts?) is not working. The symptom is, quite simply, that computer A (this new one) is not able to communicate with any other computers.. until those other computers communicate with A. For example, if A tries to ping B, A appears to get no response, saying that B is down. But if B pings A, A is now able to ping B. But A still can't ping C until C pings A as well. All (two dozen) other machines on the network have been working fine, some of them for years. I have ruled out problems with the hub, cabling, etc., by swapping them. I have not swapped out the network card (a PNIC-based NetGear 10/100), but it does work under Windows on this same machine. Here is what the routing table looks like during one of these episodes: Destination Gateway Flags Refs Use Netif Expire default 209.54.21.129 UGSc 0 0 pn0 127.0.0.1 127.0.0.1 UH 0 0 lo0 209.54.21 link#1 UC 0 0 pn0 209.54.21.129 0:e0:b0:e2:bc:79 UHLW 1 0 pn0 970 209.54.21.142 link#1 UHRLW 0 7 pn0 209.54.21.181 link#1 UHRLW 0 7 pn0 209.54.21.199 0:60:97:a3:63:e6 UHLW 1 44 pn0 1159 At this time, it is possible to talk to .129 and .199, but not .142 or .181. Attempts to ping other addresses result in them appearing in the table with "link#1" entries. If I ping A from the other machine, the "link#1" is replaced by the correct hardware address. Here's the ARP table: bertha% arp -n -a ? (209.54.21.129) at 0:e0:b0:e2:bc:79 ? (209.54.21.142) at (incomplete) ? (209.54.21.181) at (incomplete) ? (209.54.21.199) at 0:60:97:a3:63:e6 bertha% arp -n 209.54.21.142 ? (209.54.21.142) at (incomplete) It's as if machine A isn't hearing the ARP responses. Here is part of a tcpdump done from another machine on the same segment during this time: 17:07:06.751678 arp who-has 209.54.21.142 tell 209.54.21.233 17:07:06.751862 arp reply 209.54.21.142 is-at 0:60:97:a3:63:af 17:07:16.767849 arp who-has 209.54.21.142 tell 209.54.21.233 17:07:16.767997 arp reply 209.54.21.142 is-at 0:60:97:a3:63:af 17:07:26.783799 arp who-has 209.54.21.142 tell 209.54.21.233 17:07:26.783928 arp reply 209.54.21.142 is-at 0:60:97:a3:63:af 17:07:46.796125 arp who-has 209.54.21.142 tell 209.54.21.233 17:07:46.796279 arp reply 209.54.21.142 is-at 0:60:97:a3:63:af The ARP is being sent out, and so is the response, but it's not being picked up for some reason. Here's a boot -v from the machine (at least, the part that fit in the dmesg buffer): 06-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 chip0: rev 0x01 on pci0.0.0 found-> vendor=0x8086, dev=0x7000, revid=0x00 class=06-01-00, hdrtype=0x00, mfdev=1 subordinatebus=0 secondarybus=0 chip1: rev 0x00 on pci0.7.0 I/O Recovery Timing: 8-bit 3 clocks, 16-bit 2 clocks Extended BIOS: enabled Lower BIOS: disabled Coprocessor IRQ13: enabled Mouse IRQ12: disabled Interrupt Routing: A: IRQ9, B: IRQ12, C: disabled, D: IRQ11 MB0: IRQ15, MB1: found-> vendor=0x8086, dev=0x7010, revid=0x00 class=01-01-80, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 map[0]: type 4, range 32, base 00009000, size 4 ide_pci0: rev 0x00 on pci0.7.1 intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: primary master/slave sample = 3, master/slave recovery = 1 intel_piix_status: primary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 0 status: 04 from port: 00009002 intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 3 intel_piix_status: secondary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled intel_piix_status: secondary master/slave sample = 3, master/slave recovery = 3 intel_piix_status: secondary slave fastDMAonly disabled, pre/post disabled, intel_piix_status: IORDY sampling disabled, intel_piix_status: fast PIO disabled ide_pci: busmaster 1 status: 04 from port: 0000900a found-> vendor=0x8086, dev=0x7020, revid=0x00 class=0c-03-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=d, irq=11 map[0]: type 4, range 32, base 00006000, size 5 found-> vendor=0x5333, dev=0x8811, revid=0x40 class=03-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=9 map[0]: type 1, range 32, base e0000000, size 26 vga0: rev 0x40 int a irq 9 on pci0.17.0 found-> vendor=0x11ad, dev=0x0002, revid=0x21 class=02-00-00, hdrtype=0x00, mfdev=0 subordinatebus=0 secondarybus=0 intpin=a, irq=12 map[0]: type 4, range 32, base 00006100, size 8 map[1]: type 1, range 32, base e4000000, size 8 pn0: <82c168/82c169 PNIC 10/100BaseTX> rev 0x21 int a irq 12 on pci0.18.0 pn0: Ethernet address: 00:a0:cc:3b:66:51 pn0: probing for a PHY pn0: checking address: 0 pn0: checking address: 1 pn0: found PHY at address 1, vendor id: 7810 device id: 0 pn0: PHY type: pn0: PHY status word: 7809 pn0: 10Mbps half-duplex mode supported pn0: 10Mbps full-duplex mode supported pn0: 100Mbps half-duplex mode supported pn0: 100Mbps full-duplex mode supported pn0: autoneg supported pn0: autoneg complete, link status good (half-duplex, 10Mbps) bpf: pn0 attached Initializing PnP override table Probing for PnP devices: Trying Read_Port at 203 Trying Read_Port at 243 PnP: CSN 1 COMP_DEVICE_ID = 0x0006d041 CSN 1 Vendor ID: CTL0044 [0x44008c0e] Serial 0x000ca45a Comp ID: PNP0600 [0x0006d041] Called nullpnp_probe with tag 0x00000001, type 0x44008c0e Called nullpnp_probe with tag 0x00000001, type 0x0006d041 Probing for devices on the ISA bus: atkbd: the current kbd controller command byte 0047 atkbd: keyboard ID 0x41ab (2) kbdc: RESET_KBD return code:00fa kbdc: RESET_KBD status:00aa sc0 on isa sc0: fb0 kbd0 sc0: VGA color <16 virtual consoles, flags=0x0> atkbdc0 at 0x60-0x6f on motherboard atkbd0 irq 1 on isa kbd0: atkbd0, AT 101/102 (2), config:0x10000, flags:0x3d0000 psm0: current command byte:0047 kbdc: TEST_AUX_PORT status:0000 kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: RESET_AUX return code:00fe kbdc: DIAGNOSE status:0055 kbdc: TEST_KBD_PORT status:0000 psm0: failed to reset the aux device. psm0 not found sio0: irq maps: 0x1 0x11 0x1 0x1 sio0 at 0x3f8-0x3ff irq 4 flags 0x10 on isa sio0: type 16550A sio1: irq maps: 0x1 0x9 0x1 0x1 sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A ppc: parallel port found at 0x3bc ppc0: ECP SPP ECP+EPP SPP ppc0 at 0x3bc irq 7 on isa ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode ppc0: FIFO with 16/16/14 bytes threshold nlpt0: on ppbus 0 nlpt0: Interrupt-driven port ppi0: on ppbus 0 plip: irq 7 plip0: on ppbus 0 bpf: lp0 attached fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in wdc0 at 0x1f0-0x1f7 irq 14 flags 0xa0ffa0ff on isa intel_piix_dmainit: setting multiword DMA mode 2 wd0: wdsetmode() setting transfer mode to 22 intel_piix_status: primary master sample = 3, master recovery = 1 intel_piix_status: primary master fastDMAonly disabled, pre/post enabled, intel_piix_status: IORDY sampling enabled, intel_piix_status: fast PIO enabled wdc0: unit 0 (wd0): , DMA, 32-bit, multi-block-16 wd0: 6149MB (12594960 sectors), 13328 cyls, 15 heads, 63 S/T, 512 B/S wd0: ATA INQUIRE valid = 0007, dmamword = 0407, apio = 0003, udma = 0007 wdc1 at 0x170-0x177 irq 15 flags 0xa0ffa0ff on isa wdc1: unit 0 (atapi): , removable, intr, dma, iordis acd0: drive speed 1033KB/sec, 256KB cache acd0: supported read types: acd0: Audio: play, 255 volume levels acd0: Mechanism: ejectable tray acd0: Medium: no/blank disc inside, unlocked wdc1: unit 1 (atapi): , removable, intr, iordis vga0 at 0x3b0-0x3df maddr 0xa0000 msize 131072 on isa fb0: vga0, vga, type:VGA (5), flags:0x7007f fb0: port:0x3b0-0x3df, crtc:0x3d4, mem:0xa0000 0x20000 fb0: init mode:24, bios mode:3, current mode:24 fb0: window:0xf00b8000 size:32k gran:32k, buf:0x0 size:0k VGA parameters upon power-up 50 18 10 00 00 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0e 0f 00 00 07 80 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff VGA parameters in BIOS for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff EGA/VGA parameters to be used for mode 24 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 00 00 00 00 9c 8e 8f 28 1f 96 b9 a3 ff 00 01 02 03 04 05 14 07 38 39 3a 3b 3c 3d 3e 3f 0c 00 0f 08 00 00 00 00 00 10 0e 00 ff npx0 on motherboard npx0: INT 16 interface apm0 flags 0x31 on isa apm: found APM BIOS version 1.1 sb0 at 0x220 irq 5 drq 1 on isa snd0: sbxvi0 at drq 5 on isa snd0: sbmidi0 at 0x330 on isa snd0: imasks: bio c008c040, tty c007109a, net c007109a BIOS Geometries: 0:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 1:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 2:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 3:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 4:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 5:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 6:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 7:00000000 0..0=1 cylinders, 0..0=1 heads, 1..0=0 sectors 0 accounted for Device configuration finished. IP packet filtering initialized, divert enabled, rule-based forwarding enabled, logging limited to 100 packets/entry bpf: tun0 attached bpf: sl0 attached bpf: ppp0 attached new masks: bio c008c040, tty c007109a, net c007109a bpf: lo0 attached IP Filter: initialized. Default = pass all, Logging = enabled Considering MFS root f/s. No MFS image available as root f/s. Considering FFS root f/s. changing root device to wd0s2a wd0s1: type 0xb, start 63, end = 8193149, size 8193087 : OK wd0s2: type 0xa5, start 8193150, end = 12594959, size 4401810 : OK ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates ffs_mountfs: superblock updated for soft updates By the way, it's running: FreeBSD 4.0-CURRENT #1: Sun Jan 24 23:39:56 EST 1999 But I had the same problems with a 3.0-CURRENT snapshot (I upgraded it in case this problem had already been fixed). This machine is not mine; I will only have access to it for another week or so, but during that time I will be able to do any testing or diagnostics needed. I'd appreciate any ideas or suggestions. -- Christopher Masto Director of Operations NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net "Good tools allow users to do stupid things." -- Clay Shirky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jan 29 14:52:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA25615 for freebsd-hardware-outgoing; Fri, 29 Jan 1999 14:52:21 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id OAA25598; Fri, 29 Jan 1999 14:52:19 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <53867(1)>; Fri, 29 Jan 1999 14:52:15 PST Received: by crevenia.parc.xerox.com id <177534>; Fri, 29 Jan 1999 14:52:13 -0800 From: Bill Fenner To: chris@netmonger.net, hardware@FreeBSD.ORG Subject: Re: Network/ARP problem? Maybe pn driver? Cc: current@FreeBSD.ORG Message-Id: <99Jan29.145213pst.177534@crevenia.parc.xerox.com> Date: Fri, 29 Jan 1999 14:52:07 PST Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can you run a "tcpdump arp" on the machine that is having the problem, as well? This could help to determine if it's a driver problem (e.g. if the replies don't show up) or an ARP problem (e.g. if the replies do show up but arp doesn't use them). Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jan 29 15:06:19 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA27351 for freebsd-hardware-outgoing; Fri, 29 Jan 1999 15:06:19 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA27330; Fri, 29 Jan 1999 15:06:15 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id SAA04552; Fri, 29 Jan 1999 18:06:12 -0500 (EST) Message-ID: <19990129180612.C3237@netmonger.net> Date: Fri, 29 Jan 1999 18:06:12 -0500 From: Christopher Masto To: Bill Fenner , hardware@FreeBSD.ORG Cc: current@FreeBSD.ORG Subject: Re: Network/ARP problem? Maybe pn driver? References: <99Jan29.145213pst.177534@crevenia.parc.xerox.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <99Jan29.145213pst.177534@crevenia.parc.xerox.com>; from Bill Fenner on Fri, Jan 29, 1999 at 02:52:07PM -0800 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jan 29, 1999 at 02:52:07PM -0800, Bill Fenner wrote: > Can you run a "tcpdump arp" on the machine that is having the problem, > as well? This could help to determine if it's a driver problem (e.g. > if the replies don't show up) or an ARP problem (e.g. if the replies > do show up but arp doesn't use them). Good idea. Hmm. Running tcpdump seems to make the problem go away. The ARP replies show up immediately appear in the table. Clue. -- Christopher Masto Director of Operations NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net "Good tools allow users to do stupid things." -- Clay Shirky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jan 29 15:16:25 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA28493 for freebsd-hardware-outgoing; Fri, 29 Jan 1999 15:16:25 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mailhub1.cuckoo.com (wrangler.cuckoo.com [206.109.5.194]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA28472 for ; Fri, 29 Jan 1999 15:16:12 -0800 (PST) (envelope-from dbaker@cuckoo.com) From: dbaker@cuckoo.com Received: (qmail 65571 invoked by uid 200); 29 Jan 1999 23:16:05 -0000 Message-ID: <19990129171605.A32721@cuckoo.com> Date: Fri, 29 Jan 1999 17:16:05 -0600 To: freebsd-questions@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG, usb-bsd@makelist.com Subject: Logitech USB Wheel Mouse on -current Reply-To: dbaker@cuckoo.com Mime-Version: 1.0 Content-Type: multipart/signed; protocol="application/pgp-signature"; micalg=pgp-md5; boundary=5vNYLRcllDrimb99 X-Mailer: Mutt 0.93.2i X-PGP-Fingerprint: F3 41 B7 EE 96 92 F5 35 5E 3C 02 61 08 22 23 98 X-Operating-System: FreeBSD 3.0-CURRENT i386 X-Distributed: Join the Effort! http://www.distributed.net/ ]:8) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org --5vNYLRcllDrimb99 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Moo! I've "installed" (read: plugged in) a Logitech USB Wheel Mouse on my FreeBSD 4.0-CURRENT box (Fri Jan 29 12:10:58 CST 1999) and it seems to probe it nicely: scream:/home/dbaker% dmesg|grep ^u uhci0: rev 0x01 int d irq = 19 on pci0.4.2 usb0: uhub0 at usb0 uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1 uhub0: 2 ports with 2 removable, self powered ums0 ums0: Logitech N48, rev 1.00/4.00, addr 2, iclass 3/1 ums0: 3 buttons scream:/home/dbaker% ls -l /dev/u* crw------- 1 root wheel 111, 0 Jan 29 13:04 /dev/ums0 crw-r--r-- 1 root wheel 2, 4 Nov 19 18:36 /dev/urandom crw------- 1 root wheel 108, 0 Jan 29 13:04 /dev/usb0 scream:/home/dbaker% su ksu[8888]: Account root: authorization for dbaker@CUCKOO.COM successful scream# usbdevs -v Controller /dev/usb0: addr 1: self powered, config 1, UHCI root hub, Intel, rev 1.00 port 1 powered port 2 addr 2: low speed, power 26 mA, config 1, N48, Logitech, rev 4.00 scream#=20 However, I've been unsuccessful in getting either Xaccel or Xfree to=20 properly handle the mouse. I think this may be because I'm selecting the incorrect "protocol" for the device. I've tried all three in Xaccel (bus, serial, ps/2), and a handful in XFree, but the mouse is never properly functional. (It either doesn't move the way I'm moving the pointing device, or it doesn't do anything at all). Throughout this, I've had the X servers to access the mouse via /dev/ums0. I'm not confident that this is the correct device, as it may be some raw device for the BSD USB programs to acquire their data. So, what should I be using as the device name and protocol? Thanks, Daniel --=20 dbaker@cuckoo.com - CuckooNet Consultant - www.cuckoo.com --5vNYLRcllDrimb99 Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: PGPfreeware 5.0i for non-commercial use MessageID: x+HqzqEBpQjcdlQ1QkJneteHgyWeWkq1 iQCVAwUBNrIzJDPZFXqiby35AQEGDQQAyqmNegwYr3mxiiUN0LJN/hXowWPulWSV UGsAx/M+xETnpivy+LwEXMfoDkX3d/F1DYoR2agZ9bNzrPxDz7zDXU4sTdWcVie3 kFJeMui1QO3zxlHMcksgDH1NNrRH4Sk/cey5teLLoG/wxMh8uTlFw2/r0RvFLNlA zZ+aLuOfEk4= =6qEF -----END PGP SIGNATURE----- --5vNYLRcllDrimb99-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jan 29 15:22:20 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29514 for freebsd-hardware-outgoing; Fri, 29 Jan 1999 15:22:20 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from skynet.ctr.columbia.edu (skynet.ctr.columbia.edu [128.59.64.70]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA29505; Fri, 29 Jan 1999 15:22:15 -0800 (PST) (envelope-from wpaul@skynet.ctr.columbia.edu) Received: (from wpaul@localhost) by skynet.ctr.columbia.edu (8.6.12/8.6.9) id SAA26781; Fri, 29 Jan 1999 18:28:47 -0500 From: Bill Paul Message-Id: <199901292328.SAA26781@skynet.ctr.columbia.edu> Subject: Re: Network/ARP problem? Maybe pn driver? To: chris@netmonger.net (Christopher Masto) Date: Fri, 29 Jan 1999 18:28:46 -0500 (EST) Cc: fenner@parc.xerox.com, current@FreeBSD.ORG, hardware@FreeBSD.ORG In-Reply-To: <19990129180612.C3237@netmonger.net> from "Christopher Masto" at Jan 29, 99 06:06:12 pm X-Mailer: ELM [version 2.4 PL24] Content-Type: text Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Of all the gin joints in all the towns in all the world, Christopher Masto had to walk into mine and say: > On Fri, Jan 29, 1999 at 02:52:07PM -0800, Bill Fenner wrote: > > Can you run a "tcpdump arp" on the machine that is having the problem, > > as well? This could help to determine if it's a driver problem (e.g. > > if the replies don't show up) or an ARP problem (e.g. if the replies > > do show up but arp doesn't use them). > > Good idea. > > Hmm. Running tcpdump seems to make the problem go away. The ARP > replies show up immediately appear in the table. Clue. You should have tried that first. There's something I'd like you to try for me. (Don't delay in trying this; I've had a long string of people who appear suddenly, complain about a problem of some sort, then vanish before I can extract enough information from them to find a solution.) I was menaced by a bug in the PNIC's receive DMA operation which, according to all my tests, only appeared in promiscuous mode. I devised a workaround, however it's only enabled when the IFF_PROMISC flag is set on the interface. Running tcpdump (without the -p flag) places the interface in promiscuous mode and enables the workaround. Given what you've said, it's possible that we need to enable the workaround all the time, not just in promiscuous mode. Do me the following: - Bring up /sys/pci/if_pn.c in your favorite editor. - Locate the pn_rxeof() function and find the following code: #ifdef PN_PROMISC_BUG_WAR /* * XXX The PNIC seems to have a bug that manifests * when the promiscuous mode bit is set: we have to * watch for it and work around it. */ if (sc->pn_promisc_war && ifp->if_flags & IFF_PROMISC) { [...] - Change the if() clause so that it looks like this: if (sc->pn_promisc_war /*&& ifp->if_flags & IFF_PROMISC*/) { (In other words, comment out the test for the IFF_PROMISC flag.) This will enable the workaround all the time and allow the receiver bug to be detected and handled properly. Compile a new kernel with this change and see if the problem persists. Report back your findings (one way or the other) so that I'll know if I should modify the code in the repository. -Bill -- ============================================================================= -Bill Paul (212) 854-6020 | System Manager, Master of Unix-Fu Work: wpaul@ctr.columbia.edu | Center for Telecommunications Research Home: wpaul@skynet.ctr.columbia.edu | Columbia University, New York City ============================================================================= "It is not I who am crazy; it is I who am mad!" - Ren Hoek, "Space Madness" ============================================================================= To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jan 29 15:23:21 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA29638 for freebsd-hardware-outgoing; Fri, 29 Jan 1999 15:23:21 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from alpha.xerox.com (alpha.Xerox.COM [13.1.64.93]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id PAA29628; Fri, 29 Jan 1999 15:23:18 -0800 (PST) (envelope-from fenner@parc.xerox.com) Received: from crevenia.parc.xerox.com ([13.2.116.11]) by alpha.xerox.com with SMTP id <53946(2)>; Fri, 29 Jan 1999 15:23:10 PST Received: from localhost by crevenia.parc.xerox.com with SMTP id <177534>; Fri, 29 Jan 1999 15:23:02 -0800 To: Christopher Masto cc: Bill Fenner , hardware@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Network/ARP problem? Maybe pn driver? In-reply-to: Your message of "Fri, 29 Jan 99 15:06:12 PST." <19990129180612.C3237@netmonger.net> Date: Fri, 29 Jan 1999 15:22:55 PST From: Bill Fenner Message-Id: <99Jan29.152302pst.177534@crevenia.parc.xerox.com> Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Big Clue. Run "tcpdump -p" and see if the problem doesn't go away. ("tcpdump" puts the card in promiscuous mode, "tcpdump -p" does not). Bill To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jan 29 15:30:52 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA00723 for freebsd-hardware-outgoing; Fri, 29 Jan 1999 15:30:52 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA00700; Fri, 29 Jan 1999 15:30:44 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id SAA03955; Fri, 29 Jan 1999 18:00:13 -0500 (EST) Message-ID: <19990129180013.B3237@netmonger.net> Date: Fri, 29 Jan 1999 18:00:13 -0500 From: Christopher Masto To: Alfred Perlstein Cc: current@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Network/ARP problem? Maybe pn driver? References: <19990129173922.A29551@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: ; from Alfred Perlstein on Fri, Jan 29, 1999 at 06:02:16PM -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jan 29, 1999 at 06:02:16PM -0500, Alfred Perlstein wrote: > On Fri, 29 Jan 1999, Christopher Masto wrote: > > I hope I'm not just being really stupid, but I think there's a problem > > somewhere. If it's a configuration error on my part, then I think I'd > > better take a vacation, considering what my job is supposed to be. > > > > Anyway, I have a machine that is exhibiting a weird network problem. > > My guess is that ARP is not working, or perhaps something that ARP > > depends on (broadcasts?) is not working. > > > > i didn't see your netmask's, can you show me those please? > > on the broken box, and on one of the working boxes? Yes, sorry.. I accidentally deleted that part of the message. Here's the broken box: pn0: flags=8843 mtu 1500 inet 209.54.21.233 netmask 0xffffff00 broadcast 209.54.21.255 ether 00:a0:cc:3b:66:51 media: 10baseT/UTP supported media: autoselect 100baseTX 100baseTX 100baseTX 10baseT/UTP 10baseT/UTP 10baseT/UTP And here's a working one: ep0: flags=8943 mtu 1500 inet 209.54.21.199 netmask 0xffffff00 broadcast 209.54.21.255 ether 00:60:97:a3:63:e6 The 255.255.255.0 netmask is correct here, despite the router being at .129. -- Christopher Masto Director of Operations NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net "Good tools allow users to do stupid things." -- Clay Shirky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jan 29 15:57:05 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04014 for freebsd-hardware-outgoing; Fri, 29 Jan 1999 15:57:05 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from whistle.com (s205m131.whistle.com [207.76.205.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA03995; Fri, 29 Jan 1999 15:57:01 -0800 (PST) (envelope-from archie@whistle.com) Received: (from smap@localhost) by whistle.com (8.7.5/8.6.12) id PAA28631; Fri, 29 Jan 1999 15:56:22 -0800 (PST) Received: from bubba.whistle.com( 207.76.205.7) by whistle.com via smap (V2.0) id xma028629; Fri, 29 Jan 99 15:56:20 -0800 Received: (from archie@localhost) by bubba.whistle.com (8.8.7/8.6.12) id PAA01669; Fri, 29 Jan 1999 15:56:20 -0800 (PST) From: Archie Cobbs Message-Id: <199901292356.PAA01669@bubba.whistle.com> Subject: Re: Network/ARP problem? Maybe pn driver? In-Reply-To: <19990129180612.C3237@netmonger.net> from Christopher Masto at "Jan 29, 99 06:06:12 pm" To: chris@netmonger.net (Christopher Masto) Date: Fri, 29 Jan 1999 15:56:20 -0800 (PST) Cc: fenner@parc.xerox.com, hardware@FreeBSD.ORG, current@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL38 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Christopher Masto writes: > > Can you run a "tcpdump arp" on the machine that is having the problem, > > as well? This could help to determine if it's a driver problem (e.g. > > if the replies don't show up) or an ARP problem (e.g. if the replies > > do show up but arp doesn't use them). > > Good idea. > > Hmm. Running tcpdump seems to make the problem go away. The ARP > replies show up immediately appear in the table. Clue. Tcpdump puts the Ethernet card in promiscuous mode. So perhaps somebody is trying to unicast you something but using the wrong Ethernet address. Could be the local or remote ARP code. Just a guess. -Archie ___________________________________________________________________________ Archie Cobbs * Whistle Communications, Inc. * http://www.whistle.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jan 29 17:23:36 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA19206 for freebsd-hardware-outgoing; Fri, 29 Jan 1999 17:23:36 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from dingo.cdrom.com (dingo.cdrom.com [204.216.28.145]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA18999; Fri, 29 Jan 1999 17:23:31 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Received: from dingo.cdrom.com (localhost.cdrom.com [127.0.0.1]) by dingo.cdrom.com (8.9.1/8.8.8) with ESMTP id RAA03574; Fri, 29 Jan 1999 17:19:14 -0800 (PST) (envelope-from mike@dingo.cdrom.com) Message-Id: <199901300119.RAA03574@dingo.cdrom.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Christopher Masto cc: hardware@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: Network/ARP problem? Maybe pn driver? In-reply-to: Your message of "Fri, 29 Jan 1999 17:39:22 EST." <19990129173922.A29551@netmonger.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 29 Jan 1999 17:19:14 -0800 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I hope I'm not just being really stupid, but I think there's a problem > somewhere. If it's a configuration error on my part, then I think I'd > better take a vacation, considering what my job is supposed to be. > > Anyway, I have a machine that is exhibiting a weird network problem. > My guess is that ARP is not working, or perhaps something that ARP > depends on (broadcasts?) is not working. > > The symptom is, quite simply, that computer A (this new one) is not > able to communicate with any other computers.. until those other > computers communicate with A. This usually means that you have the netmask wrong, so broadcasts don't work (wrong destination address). When someone else talks to the misconfigured machine, they create an ARP cache entry, which allows the victim to "see" them (until it times out). -- \\ Sometimes you're ahead, \\ Mike Smith \\ sometimes you're behind. \\ mike@smith.net.au \\ The race is long, and in the \\ msmith@freebsd.org \\ end it's only with yourself. \\ msmith@cdrom.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jan 29 17:36:53 1999 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id RAA21873 for freebsd-hardware-outgoing; Fri, 29 Jan 1999 17:36:53 -0800 (PST) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from cheddar.netmonger.net (cheddar.netmonger.net [209.54.21.140]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id RAA21850; Fri, 29 Jan 1999 17:36:46 -0800 (PST) (envelope-from chris@cheddar.netmonger.net) Received: (from chris@localhost) by cheddar.netmonger.net (8.8.8/8.8.8) id UAA16694; Fri, 29 Jan 1999 20:36:35 -0500 (EST) Message-ID: <19990129203635.A13393@netmonger.net> Date: Fri, 29 Jan 1999 20:36:35 -0500 From: Christopher Masto To: Bill Paul Cc: fenner@parc.xerox.com, current@FreeBSD.ORG, hardware@FreeBSD.ORG Subject: Re: Network/ARP problem? Maybe pn driver? References: <19990129180612.C3237@netmonger.net> <199901292328.SAA26781@skynet.ctr.columbia.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.91.1i In-Reply-To: <199901292328.SAA26781@skynet.ctr.columbia.edu>; from Bill Paul on Fri, Jan 29, 1999 at 06:28:46PM -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Fri, Jan 29, 1999 at 06:28:46PM -0500, Bill Paul wrote: > > Hmm. Running tcpdump seems to make the problem go away. The ARP > > replies show up immediately appear in the table. Clue. > > You should have tried that first. I'm sorry. I ran tcpdump on a different host precisely because I didn't want to interfere with the problem and make it harder to debug. I overlooked the obvious. > There's something I'd like you to try for me. (Don't delay in trying > this; I've had a long string of people who appear suddenly, complain > about a problem of some sort, then vanish before I can extract enough > information from them to find a solution.) I have been active with FreeBSD for the past four years. I have not appeared suddenly, nor do I intend to vanish. The delay in responding to your message is solely a result of a dinner party I had to attend. > I was menaced by a bug in the PNIC's receive DMA operation which, according > to all my tests, only appeared in promiscuous mode. I devised a workaround, > however it's only enabled when the IFF_PROMISC flag is set on the > interface. Running tcpdump (without the -p flag) places the interface > in promiscuous mode and enables the workaround. Given what you've said, > it's possible that we need to enable the workaround all the time, not > just in promiscuous mode. I would say you're quite right, considering the result of tcpdump -n -p arp: 20:32:36.302468 arp who-has 209.54.21.129 tell 209.54.21.233 20:32:36.303175 arp who-has 209.54.21.129 tell 209.54.21.233 20:32:37.310842 arp who-has 209.54.21.129 tell 209.54.21.233 20:32:37.311563 arp who-has 209.54.21.129 tell 209.54.21.233 20:32:38.320858 arp who-has 209.54.21.129 tell 209.54.21.233 20:32:38.321579 arp who-has 209.54.21.129 tell 209.54.21.233 20:32:39.330866 arp who-has 209.54.21.129 tell 209.54.21.233 20:32:39.331600 arp who-has 209.54.21.129 tell 209.54.21.233 20:32:40.340883 arp who-has 209.54.21.129 tell 209.54.21.233 20:32:40.341581 arp who-has 209.54.21.129 tell 209.54.21.233 Run again without -p, and voila: 20:33:30.232549 arp who-has 209.54.21.129 tell 209.54.21.233 20:33:30.233301 arp reply 209.54.21.129 is-at 0:e0:b0:e2:bc:79 > Do me the following: > > - Bring up /sys/pci/if_pn.c in your favorite editor. [...] > Compile a new kernel with this change and see if the problem persists. > Report back your findings (one way or the other) so that I'll know if > I should modify the code in the repository. I will have the results for you by tomorrow. Thank you very much for your assistance. -- Christopher Masto Director of Operations NetMonger Communications chris@netmonger.net info@netmonger.net http://www.netmonger.net "Good tools allow users to do stupid things." -- Clay Shirky To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message