From owner-freebsd-hardware Sun May 31 00:40:22 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA19003 for freebsd-hardware-outgoing; Sun, 31 May 1998 00:40:22 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from lariat.lariat.org (ppp1000.lariat.org@lariat.lariat.org [129.72.251.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA18986 for ; Sun, 31 May 1998 00:40:04 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.8) id BAA02148; Sun, 31 May 1998 01:39:58 -0600 (MDT) Message-Id: <199805310739.BAA02148@lariat.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Sun, 31 May 1998 01:39:59 -0600 To: hardware@FreeBSD.ORG From: Brett Glass Subject: Driver for SMC EtherPower II 10/100? Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Does anyone know if one of FreeBSD's drivers will work with SMC's EtherPower II 10/100 card? It's a very aggressively priced card which is claimed to be able to do 100 Mbps full duplex. --Brett Glass To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun May 31 13:04:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA10156 for freebsd-hardware-outgoing; Sun, 31 May 1998 13:04:32 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles208.castles.com [208.214.165.208]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA10042 for ; Sun, 31 May 1998 13:04:09 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id LAA12746; Sun, 31 May 1998 11:59:40 -0700 (PDT) Message-Id: <199805311859.LAA12746@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brett Glass cc: hardware@FreeBSD.ORG Subject: Re: Driver for SMC EtherPower II 10/100? In-reply-to: Your message of "Sun, 31 May 1998 01:39:59 MDT." <199805310739.BAA02148@lariat.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 May 1998 11:59:40 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Does anyone know if one of FreeBSD's drivers will work with SMC's > EtherPower II 10/100 card? It's a very aggressively priced card which is > claimed to be able to do 100 Mbps full duplex. Yes, this is handled by the 'tx' driver. -- \\ 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 May 31 13:15:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA12049 for freebsd-hardware-outgoing; Sun, 31 May 1998 13:15:18 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from smtp1.erols.com (smtp1.erols.com [207.172.3.234]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA11755; Sun, 31 May 1998 13:13:50 -0700 (PDT) (envelope-from hartong@erols.com) Received: from mhartong (207-172-41-114.s114.tnt10.brd.erols.com [207.172.41.114]) by smtp1.erols.com (8.8.8/8.8.5) with SMTP id QAA10249; Sun, 31 May 1998 16:13:20 -0400 (EDT) From: "Hartong" To: Cc: , Subject: ATAPI CD ROM Installation Failure on BSD 2.2.6 Date: Sun, 31 May 1998 16:09:41 -0400 Message-ID: <01bd8cd0$0c06cb60$7229accf@mhartong.man.fs.lmco.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_0008_01BD8CAE.84F52B60" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.71.1712.3 X-MimeOLE: Produced By Microsoft MimeOLE V4.71.1712.3 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org This is a multi-part message in MIME format. ------=_NextPart_000_0008_01BD8CAE.84F52B60 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable HELP!!!!! While installing FreeBSD 2.2.6 I I obtain the following: The system locks up with the dreaded blue screen of death on virtual = console 1 with "Probing devices, Please wait..." Diagnostic message on virtual console 2 ATAPI.IO: INVALID COMMAND PHASE, = IREASON=3D0xd8,STATUS=3Dd8, ERROR=3Dd8 Hardware Configuration: NEC CD-Rom Drive 273, running as master on = secondary IDE controller 1GB HD running as master on primary IDE = controller. System is a Dell Dimension P133. Additional Diagnostic Information: 1 System will do intial boot from CD Rom player with CD Rom selected as = intial boot medium. Configuration is accomplished, all conflicts are = resolved. System starts reboot recognizes wcd0 and wcd1 controllers, = then freezes. 2. System will do intial boot from floopy selected as intial boot = medium. Configuration is accomplished, all conflicts are resolved. = System starts reboot recognizes wcd0 and wcd1 controllers, then freezes 3. CD-ROM player placed as slave on primary IDE controller. System = will do intial boot from CD Rom with CD Rom selected as intial boot = medium. Configuration is accomplished, all conflicts are resolved. = System starts reboot recognizes wcd0 and wcd1 controllers, then = freezes. 4. CD-ROM player placed as slave on primary IDE controller. System = will do intial boot from flloppy selected as intial boot medium. = Configuration is accomplished, all conflicts are resolved. System = starts reboot recognizes wcd0 and wcd1 controllers, then freezes. Help, what do I do next! I've gone through the FAQ's, searched the = Mailing List archives, and tried deciphering the ATAPIA source code with = no luck. I've run out of ideas. I'm sure that someone must have = encountered this problem somewhere. As a last resort I could try a DOS = installation, but that still leaves the problem of an unrecognized CD = ROM player to fix. I really DON"T want to go back to Linux :( Regds =20 Mark Hartong =20 hartong@erols.com mark.hartong@lmco.com ------=_NextPart_000_0008_01BD8CAE.84F52B60 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable
HELP!!!!!
 
While installing FreeBSD 2.2.6 I I = obtain the=20 following:
 
The system locks up with the dreaded blue screen of=20 death  on virtual console 1 with "Probing devices, Please=20 wait..."
 
Diagnostic message on=20 virtual console 2
 
ATAPI.IO: INVALID COMMAND PHASE,=20 IREASON=3D0xd8,STATUS=3Dd8<BUSY,READY,OPDONE,IRQ>,=20 ERROR=3Dd8<mchg>
 
 
 
Hardware Configuration:   = NEC CD-Rom Drive 273, running as master on = secondary IDE=20 controller   1GB HD running as master on primary IDE = controller. =20 System is a Dell Dimension P133.  <All in all a relatively=20 "standard" equipment and configuration, I = think>
 
Additional Diagnostic = Information:
 
1  System will do intial boot = from CD Rom=20 player with CD Rom selected as intial boot medium.  Configuration = is=20 accomplished, all conflicts are resolved.  System starts = reboot =20 recognizes wcd0 and wcd1 controllers, then freezes.
 
2.  System will do intial boot = from floopy=20 selected as intial boot medium.  Configuration is accomplished, all = conflicts are resolved.  System starts reboot  recognizes wcd0 = and=20 wcd1 controllers, then freezes
 
3.  CD-ROM player placed as = slave on=20 primary IDE controller.  System will do intial boot from CD Rom = with CD Rom=20 selected as intial boot medium.  Configuration is accomplished, all = conflicts are resolved.  System starts reboot  recognizes wcd0 = and=20 wcd1 controllers, then freezes.
 
4.   CD-ROM player placed = as slave on=20 primary IDE controller.  System will do intial boot from flloppy = selected=20 as intial boot medium.  Configuration is accomplished, all = conflicts are=20 resolved.  System starts reboot  recognizes wcd0 and wcd1 = controllers,=20 then freezes. 
 
Help, what do I do next!  I've = gone through=20 the FAQ's, searched the Mailing List archives, and tried deciphering the = ATAPIA=20 source code with no luck.  I've run out of ideas.  I'm sure = that=20 someone must have encountered this problem somewhere.  As a last = resort I=20 could try a DOS installation, but that still leaves the problem of an=20 unrecognized CD ROM player to fix.  I really = DON"T=20 want to go back to Linux :(
 
Regds
 
Mark Hartong
 
hartong@erols.com
mark.hartong@lmco.com
------=_NextPart_000_0008_01BD8CAE.84F52B60-- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun May 31 13:55:21 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA20487 for freebsd-hardware-outgoing; Sun, 31 May 1998 13:55:21 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from lariat.lariat.org (ppp1000.lariat.org@lariat.lariat.org [129.72.251.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA20016 for ; Sun, 31 May 1998 13:54:00 -0700 (PDT) (envelope-from brett@lariat.org) Received: (from brett@localhost) by lariat.lariat.org (8.8.8/8.8.8) id OAA09285; Sun, 31 May 1998 14:53:47 -0600 (MDT) Message-Id: <199805312053.OAA09285@lariat.lariat.org> X-Sender: brett@mail.lariat.org X-Mailer: QUALCOMM Windows Eudora Pro Version 4.0.1 Date: Sun, 31 May 1998 14:53:43 -0600 To: Mike Smith From: Brett Glass Subject: Re: Driver for SMC EtherPower II 10/100? Cc: hardware@FreeBSD.ORG In-Reply-To: <199805311859.LAA12746@antipodes.cdrom.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org If the below is true, how come the HARDWARE.TXT file for 2.2.6-RELEASE doesn't list a "tx" driver (either as part of the GENERIC kernel or otherwise)? Is it part of the GENERIC kernel? --Brett At 11:59 AM 5/31/98 -0700, Mike Smith wrote: >> Does anyone know if one of FreeBSD's drivers will work with SMC's >> EtherPower II 10/100 card? It's a very aggressively priced card which is >> claimed to be able to do 100 Mbps full duplex. > >Yes, this is handled by the 'tx' driver. > >-- >\\ 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 May 31 14:18:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA23736 for freebsd-hardware-outgoing; Sun, 31 May 1998 14:18:29 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles208.castles.com [208.214.165.208]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA23624 for ; Sun, 31 May 1998 14:18:00 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id NAA13188; Sun, 31 May 1998 13:13:35 -0700 (PDT) Message-Id: <199805312013.NAA13188@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Brett Glass cc: Mike Smith , hardware@FreeBSD.ORG Subject: Re: Driver for SMC EtherPower II 10/100? In-reply-to: Your message of "Sun, 31 May 1998 14:53:43 MDT." <199805312053.OAA09285@lariat.lariat.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 May 1998 13:13:35 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Documentation bug. It's in GENERIC. > If the below is true, how come the HARDWARE.TXT file for 2.2.6-RELEASE > doesn't list a "tx" driver (either as part of the GENERIC kernel or > otherwise)? Is it part of the GENERIC kernel? > > --Brett > > > At 11:59 AM 5/31/98 -0700, Mike Smith wrote: > > >> Does anyone know if one of FreeBSD's drivers will work with SMC's > >> EtherPower II 10/100 card? It's a very aggressively priced card which is > >> claimed to be able to do 100 Mbps full duplex. > > > >Yes, this is handled by the 'tx' driver. > > > >-- > >\\ 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 > > > -- \\ 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 May 31 15:22:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA04018 for freebsd-hardware-outgoing; Sun, 31 May 1998 15:22:35 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles208.castles.com [208.214.165.208]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA02805; Sun, 31 May 1998 15:17:55 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id OAA13464; Sun, 31 May 1998 14:13:35 -0700 (PDT) Message-Id: <199805312113.OAA13464@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Hartong" cc: freebsd-questions@FreeBSD.ORG, freebsd-newbies@FreeBSD.ORG, freebsd-hardware@FreeBSD.ORG Subject: Re: ATAPI CD ROM Installation Failure on BSD 2.2.6 In-reply-to: Your message of "Sun, 31 May 1998 16:09:41 EDT." <01bd8cd0$0c06cb60$7229accf@mhartong.man.fs.lmco.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sun, 31 May 1998 14:13:35 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Please don't send HTML messages to a public mailing list. > HELP!!!!! > > While installing FreeBSD 2.2.6 I I obtain the following: > > The system locks up with the dreaded blue screen of death on virtual = > console 1 with "Probing devices, Please wait..." > > Diagnostic message on virtual console 2 > > ATAPI.IO: INVALID COMMAND PHASE, = > IREASON=3D0xd8,STATUS=3Dd8, ERROR=3Dd8 > > Hardware Configuration: NEC CD-Rom Drive 273, running as master on = > secondary IDE controller 1GB HD running as master on primary IDE = > controller. System is a Dell Dimension P133. "standard" equipment and configuration, I think> Do you have a Zip drive in this system? Can you please copy the message accurately, and indicate where the various drives are in the system? The message should start "atapi.: ... " The fact that the fields above are all 0xd8 implies that the problem may involve a false probe or other bogus item. The ".IO" that you quote makes me think that this is atapi1.0, ie. master on the second bus, but your CDROM is on the first bus. > Additional Diagnostic Information: > > 1 System will do intial boot from CD Rom player with CD Rom selected as = > intial boot medium. Configuration is accomplished, all conflicts are = > resolved. System starts reboot recognizes wcd0 and wcd1 controllers, = > then freezes. wcd0 and wcd1? wdc0 and wdc1 perhaps? What if you disable wdc1? What are you disabling to resolve "all" conflicts? When the system "freezes", how long are you waiting? Is there disk activity? Does it stop at some point? > Help, what do I do next! I've gone through the FAQ's, searched the = > Mailing List archives, and tried deciphering the ATAPIA source code with = > no luck. I've run out of ideas. I'm sure that someone must have = > encountered this problem somewhere. As a last resort I could try a DOS = > installation, but that still leaves the problem of an unrecognized CD = > ROM player to fix. I really DON"T want to go back to Linux :( -- \\ 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 May 31 18:06:49 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id SAA28627 for freebsd-hardware-outgoing; Sun, 31 May 1998 18:06:49 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from russian-caravan.cloud9.net (russian-caravan.cloud9.net [168.100.1.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id SAA28540 for ; Sun, 31 May 1998 18:06:26 -0700 (PDT) (envelope-from scottd@cloud9.net) Received: from earl-grey.cloud9.net (7RjWZtERr9f7I4PU1qxMyrtQiXCKoC6b@earl-grey.cloud9.net [168.100.1.1]) by russian-caravan.cloud9.net (8.8.8/8.8.8) with SMTP id VAA22232 for ; Sun, 31 May 1998 21:06:20 -0400 (EDT) Date: Sun, 31 May 1998 21:06:20 -0400 (EDT) From: Scott Drassinower To: freebsd-hardware@FreeBSD.ORG Subject: Intel EtherExpress 100+ problems 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 I've been having some problems with an Intel EtherExpress 100+ card (which 2.2.6-RELEASE is seeing as a 100B card, fwiw) running in 100 megabit mode, full duplex, to a Cisco Catalyst 2900XL. Running tail or grep on a large (>10mb) file via NFS from another 2.2.6 machine (with an Intel 100+ too) will simply freeze the tail or grep process, and it won't die. ps shows the process in disk wait, even though other operations on the mount will be fine. When I replace the Cisco with a 10 megabit hub, the cards drop to 10 megabit and half duplex, and there are no nfs problems. Cisco said they had some internal docs talking about problems with the Intel 100B cards running 100 megabit, full duplex, that were cleared up with the 100+ cards. Intel was completely useless. I'm wondering if there is perhaps a problem with the fxp driver in 2.2.6, or some weird issue with the Cisco. I don't have another 100 megabit switch laying around, and I really wouldn't want to have to switch from the Intel cards not knowing what the problem is. All that Cisco could suggest was different cards or a sniffer to look for more clues. Any ideas? This seems pretty weird. Thanks. -- Scott M. Drassinower scottd@cloud9.net Cloud 9 Consulting, Inc. White Plains, NY +1 914 696-4000 http://www.cloud9.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sun May 31 22:11:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA01716 for freebsd-hardware-outgoing; Sun, 31 May 1998 22:11:12 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA01711 for ; Sun, 31 May 1998 22:11:05 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id WAA09519; Sun, 31 May 1998 22:10:37 -0700 (PDT) Message-Id: <199806010510.WAA09519@implode.root.com> To: Scott Drassinower cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Intel EtherExpress 100+ problems In-reply-to: Your message of "Sun, 31 May 1998 21:06:20 EDT." From: David Greenman Reply-To: dg@root.com Date: Sun, 31 May 1998 22:10:37 -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >I've been having some problems with an Intel EtherExpress 100+ card (which >2.2.6-RELEASE is seeing as a 100B card, fwiw) running in 100 megabit mode, >full duplex, to a Cisco Catalyst 2900XL. Running tail or grep on a large >(>10mb) file via NFS from another 2.2.6 machine (with an Intel 100+ too) >will simply freeze the tail or grep process, and it won't die. ps shows >the process in disk wait, even though other operations on the mount will >be fine. > >When I replace the Cisco with a 10 megabit hub, the cards drop to 10 >megabit and half duplex, and there are no nfs problems. > >Cisco said they had some internal docs talking about problems with the >Intel 100B cards running 100 megabit, full duplex, that were cleared up >with the 100+ cards. Intel was completely useless. > >I'm wondering if there is perhaps a problem with the fxp driver in 2.2.6, >or some weird issue with the Cisco. I don't have another 100 megabit >switch laying around, and I really wouldn't want to have to switch from >the Intel cards not knowing what the problem is. All that Cisco could >suggest was different cards or a sniffer to look for more clues. > >Any ideas? This seems pretty weird. There are no known bugs in the fxp driver, but there are plenty of NFS bugs, some of which show up as link speed sensitive race conditions. -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 Mon Jun 1 00:27:32 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id AAA16584 for freebsd-hardware-outgoing; Mon, 1 Jun 1998 00:27:32 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id AAA16563; Mon, 1 Jun 1998 00:27:21 -0700 (PDT) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE (8.8.8/8.8.8) with ESMTP id JAA26820; Mon, 1 Jun 1998 09:27:18 +0200 (MET DST) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id XAA01836; Sun, 31 May 1998 23:58:03 +0200 (CEST) X-Face: " Date: Sun, 31 May 1998 23:58:02 +0200 From: Stefan Esser To: Case , freebsd-hardware@FreeBSD.ORG Cc: Stefan Esser Subject: Re: pci_map_port failed: device's iorange ? References: <6kpguj$kv4$1@xs2.xs4all.nl> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <6kpguj$kv4$1@xs2.xs4all.nl>; from Case on Sat, May 30, 1998 at 07:51:15PM +0200 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1998-05-30 19:51 +0200, Case wrote: > Hi, > > I just installed FreeBSD-2.2.6 on a micron transport xke laptop, > and when I booted it while connected to the docking station > I noticed the following messages: > > Probing for devices on PCI bus 0: > [ .. ] > chip5 rev 1 on pci0:9:[ .. ] > Probing for devices on PCI bus 1: > ahc0 rev 3 int a irq 9 on pci1:7:0 > pci_map_port failed: device's iorange 0xe800-0xe8ff is incompatible > with its bridge's range 0x0-0xfff > de0 rev 48 int a irq 9 on pci1:8:0 > pci_map_port failed: device's iorange 0xec00-0xec7f is incompatible > with its bridge's range 0x0-0xfff Could you please send complete *verbose* boot messages ? (I.e. enter "-v" at the boot prompt.) > The iorange 0x0-0xfff on the bridge chips seems odd.. is freebsd > confused by the fact that there are 2 pci busses on this machine ? > (430TX mobile chipset) I'm not sure what's wrong, but that message was just meant to be an indication of a possible cause, in case you can't get a device behind a PCI bridge to work. I don't know the particular chip-set in your machine, and the PCI code may need to know a little more about the bridge chip. > (oh, interesting sidenote, it works fine in netbsd :-] ) Hmmm, it should work under FreeBSD, as well ... You may try the following patch to let the device driver use memory mapped accesses (which are better for several reasons, anyway ...). Regards, STefan *** /sys/pci/if_de.c~ Mon Oct 27 23:08:56 1997 --- /sys/pci/if_de.c Sun May 31 23:56:02 1998 *************** *** 154,158 **** */ #if defined(__i386__) || defined(TULIP_EISA) ! #define TULIP_IOMAPPED #endif --- 154,158 ---- */ #if defined(__i386__) || defined(TULIP_EISA) ! #undef TULIP_IOMAPPED #endif To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 1 07:07:19 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA11073 for freebsd-hardware-outgoing; Mon, 1 Jun 1998 07:07:19 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from russian-caravan.cloud9.net (russian-caravan.cloud9.net [168.100.1.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA11044 for ; Mon, 1 Jun 1998 07:07:14 -0700 (PDT) (envelope-from scottd@cloud9.net) Received: from earl-grey.cloud9.net (b9DUdK4pCscPjqbz0mqWSZ6rcVl0tqjw@earl-grey.cloud9.net [168.100.1.1]) by russian-caravan.cloud9.net (8.8.8/8.8.8) with SMTP id KAA01170; Mon, 1 Jun 1998 10:07:10 -0400 (EDT) Date: Mon, 1 Jun 1998 10:07:09 -0400 (EDT) From: Scott Drassinower To: David Greenman cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Intel EtherExpress 100+ problems In-Reply-To: <199806010510.WAA09519@implode.root.com> 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 So the problem that I'm having with NFS will likely occur with a 3Com or SMC card as well? There is no workaround at all for this, just deal with messed up nfs or run at 10 megabits? -- Scott M. Drassinower scottd@cloud9.net Cloud 9 Consulting, Inc. White Plains, NY +1 914 696-4000 http://www.cloud9.net On Sun, 31 May 1998, David Greenman wrote: > >I've been having some problems with an Intel EtherExpress 100+ card (which > >2.2.6-RELEASE is seeing as a 100B card, fwiw) running in 100 megabit mode, > >full duplex, to a Cisco Catalyst 2900XL. Running tail or grep on a large > >(>10mb) file via NFS from another 2.2.6 machine (with an Intel 100+ too) > >will simply freeze the tail or grep process, and it won't die. ps shows > >the process in disk wait, even though other operations on the mount will > >be fine. > > > >When I replace the Cisco with a 10 megabit hub, the cards drop to 10 > >megabit and half duplex, and there are no nfs problems. > > > >Cisco said they had some internal docs talking about problems with the > >Intel 100B cards running 100 megabit, full duplex, that were cleared up > >with the 100+ cards. Intel was completely useless. > > > >I'm wondering if there is perhaps a problem with the fxp driver in 2.2.6, > >or some weird issue with the Cisco. I don't have another 100 megabit > >switch laying around, and I really wouldn't want to have to switch from > >the Intel cards not knowing what the problem is. All that Cisco could > >suggest was different cards or a sniffer to look for more clues. > > > >Any ideas? This seems pretty weird. > > There are no known bugs in the fxp driver, but there are plenty of NFS > bugs, some of which show up as link speed sensitive race conditions. > > -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 > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 1 08:28:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA25102 for freebsd-hardware-outgoing; Mon, 1 Jun 1998 08:28:12 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from george.lbl.gov (george-2.lbl.gov [131.243.2.12]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA25017 for ; Mon, 1 Jun 1998 08:27:52 -0700 (PDT) (envelope-from jin@george.lbl.gov) Received: (from jin@localhost) by george.lbl.gov (8.8.8/LBL-ITG) id IAA23215; Mon, 1 Jun 1998 08:27:36 -0700 (PDT) Date: Mon, 1 Jun 1998 08:27:36 -0700 (PDT) From: Jin Guojun (ITG staff) Message-Id: <199806011527.IAA23215@george.lbl.gov> To: dg@root.com, scottd@cloud9.net Subject: Re: Intel EtherExpress 100+ problems Cc: freebsd-hardware@FreeBSD.ORG Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Can your switch do auto-negotiate? I have a Cisco Catalyst 5000 with two network module, one manual and one auto negotiate. SMC, 3COM, and Intel NIC are works well on the auto-negotiate module and work well on the manual-negotiate module if the duplex is matching. This is very common problme for 100 BT network between host and switch. The duplex mode must in agreement between the host and the port on the switch module. I have heard a tons of such problem around problem. After I told them to check the duplex status, problem are solved. -Jin > So the problem that I'm having with NFS will likely occur with a 3Com or > SMC card as well? There is no workaround at all for this, just deal with > messed up nfs or run at 10 megabits? > > -- > Scott M. Drassinower scottd@cloud9.net > Cloud 9 Consulting, Inc. White Plains, NY > +1 914 696-4000 http://www.cloud9.net > > On Sun, 31 May 1998, David Greenman wrote: > > > >I've been having some problems with an Intel EtherExpress 100+ card (which > > >2.2.6-RELEASE is seeing as a 100B card, fwiw) running in 100 megabit mode, > > >full duplex, to a Cisco Catalyst 2900XL. Running tail or grep on a large > > >(>10mb) file via NFS from another 2.2.6 machine (with an Intel 100+ too) > > >will simply freeze the tail or grep process, and it won't die. ps shows > > >the process in disk wait, even though other operations on the mount will > > >be fine. > > > > > >When I replace the Cisco with a 10 megabit hub, the cards drop to 10 > > >megabit and half duplex, and there are no nfs problems. > > > > > >Cisco said they had some internal docs talking about problems with the > > >Intel 100B cards running 100 megabit, full duplex, that were cleared up > > >with the 100+ cards. Intel was completely useless. > > > > > >I'm wondering if there is perhaps a problem with the fxp driver in 2.2.6, > > >or some weird issue with the Cisco. I don't have another 100 megabit > > >switch laying around, and I really wouldn't want to have to switch from > > >the Intel cards not knowing what the problem is. All that Cisco could > > >suggest was different cards or a sniffer to look for more clues. > > > > > >Any ideas? This seems pretty weird. > > > > There are no known bugs in the fxp driver, but there are plenty of NFS > > bugs, some of which show up as link speed sensitive race conditions. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 1 08:47:25 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA29507 for freebsd-hardware-outgoing; Mon, 1 Jun 1998 08:47:25 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from russian-caravan.cloud9.net (russian-caravan.cloud9.net [168.100.1.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA29490 for ; Mon, 1 Jun 1998 08:47:18 -0700 (PDT) (envelope-from scottd@cloud9.net) Received: from earl-grey.cloud9.net (tIz5SLvpvq1QH/V95FFlOjZQ71gFp1Fo@earl-grey.cloud9.net [168.100.1.1]) by russian-caravan.cloud9.net (8.8.8/8.8.8) with SMTP id LAA10902; Mon, 1 Jun 1998 11:47:10 -0400 (EDT) Date: Mon, 1 Jun 1998 11:47:10 -0400 (EDT) From: Scott Drassinower To: Jin Guojun cc: dg@root.com, freebsd-hardware@FreeBSD.ORG Subject: Re: Intel EtherExpress 100+ problems In-Reply-To: <199806011527.IAA23215@george.lbl.gov> 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 The 2900XL can auto negotiate -- it does so by default. I can force things to 10 or 100 and half or full too, but that shouldn't be necessary. With the switch auto negotiating, it definitely has each port as 100/full. Cisco suggested I add spantree portfast to each port's config so that it will start forwarding packets faster, but that's the only non-default setting that the Cisco is using. Same problem either way. The only problems with the network are with certain types of file operations over nfs, not with everything being broken. -- Scott M. Drassinower scottd@cloud9.net Cloud 9 Consulting, Inc. White Plains, NY +1 914 696-4000 http://www.cloud9.net On Mon, 1 Jun 1998, Jin Guojun wrote: > Can your switch do auto-negotiate? > I have a Cisco Catalyst 5000 with two network module, one manual and one auto > negotiate. SMC, 3COM, and Intel NIC are works well on the auto-negotiate module > and work well on the manual-negotiate module if the duplex is matching. > > This is very common problme for 100 BT network between host and switch. > The duplex mode must in agreement between the host and the port on the switch > module. I have heard a tons of such problem around problem. After I told them > to check the duplex status, problem are solved. > > -Jin > > > So the problem that I'm having with NFS will likely occur with a 3Com or > > SMC card as well? There is no workaround at all for this, just deal with > > messed up nfs or run at 10 megabits? > > > > -- > > Scott M. Drassinower scottd@cloud9.net > > Cloud 9 Consulting, Inc. White Plains, NY > > +1 914 696-4000 http://www.cloud9.net > > > > On Sun, 31 May 1998, David Greenman wrote: > > > > > >I've been having some problems with an Intel EtherExpress 100+ card (which > > > >2.2.6-RELEASE is seeing as a 100B card, fwiw) running in 100 megabit mode, > > > >full duplex, to a Cisco Catalyst 2900XL. Running tail or grep on a large > > > >(>10mb) file via NFS from another 2.2.6 machine (with an Intel 100+ too) > > > >will simply freeze the tail or grep process, and it won't die. ps shows > > > >the process in disk wait, even though other operations on the mount will > > > >be fine. > > > > > > > >When I replace the Cisco with a 10 megabit hub, the cards drop to 10 > > > >megabit and half duplex, and there are no nfs problems. > > > > > > > >Cisco said they had some internal docs talking about problems with the > > > >Intel 100B cards running 100 megabit, full duplex, that were cleared up > > > >with the 100+ cards. Intel was completely useless. > > > > > > > >I'm wondering if there is perhaps a problem with the fxp driver in 2.2.6, > > > >or some weird issue with the Cisco. I don't have another 100 megabit > > > >switch laying around, and I really wouldn't want to have to switch from > > > >the Intel cards not knowing what the problem is. All that Cisco could > > > >suggest was different cards or a sniffer to look for more clues. > > > > > > > >Any ideas? This seems pretty weird. > > > > > > There are no known bugs in the fxp driver, but there are plenty of NFS > > > bugs, some of which show up as link speed sensitive race conditions. > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 1 10:41:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA20292 for freebsd-hardware-outgoing; Mon, 1 Jun 1998 10:41:10 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from sabre.goldsword.com (sabre.goldsword.com [199.170.202.32]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA20275 for ; Mon, 1 Jun 1998 10:41:03 -0700 (PDT) (envelope-from jfarmer@sabre.goldsword.com) Received: (from jfarmer@localhost) by sabre.goldsword.com (8.8.8/8.8.8) id NAA01141; Mon, 1 Jun 1998 13:46:06 -0400 (EDT) Date: Mon, 1 Jun 1998 13:46:06 -0400 (EDT) From: "John T. Farmer" Message-Id: <199806011746.NAA01141@sabre.goldsword.com> To: hardware@FreeBSD.ORG Subject: Wide SCSI adaptors... Cc: jfarmer@goldsword.com Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Looking at getting a Wide SCSI PCI card for a new server here. Motherboard is a Tyan dual processor "Tomcat III." So far I've found 2 possibliities, the ASUS SC275, and the Tekram 390F item. The tekram appears to decent & I get grab one for $30 to $60 less than the ASUS. I know the ASUS card works well in FreeBSD, but if the Tekram is as good & supported (It does appear to be a plain 875 board with onboard flashable BIOS), well saving $30 to $60 _always_ appeals to the Scots blood in me (:^>, being part Scots, I guess I can say such things..) So, ASUS or Tekram? Opinions, experiences, advice wanted. Guarantied that I will listen, & do something! Thanks John ps. In case it matters, the adpator (& the Tyan dual Tomcat) are going into a web server. While plain scsi would prob. be fast enough, I have some wide Seagate 2.1gb Hawks just setting here. (couldn't get them sold fast enough before prices tumbled... Did get the Adaptec 3940W card sold tho...) ------------------------------------------------------------------------- John T. Farmer Proprietor, GoldSword Systems jfarmer@goldsword.com Public Internet Access in East Tennessee Office: (423)691-6498 for info, e-mail to info@goldsword.com Network Design, Internet Services & Servers, Consulting To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 1 13:48:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA00654 for freebsd-hardware-outgoing; Mon, 1 Jun 1998 13:48:39 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from breckenridge.datatimes.com (breckenridge.datatimes.com [206.155.225.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA00580 for ; Mon, 1 Jun 1998 13:48:24 -0700 (PDT) (envelope-from ksloan@datatimes.com) Received: from okc-nt02.umi.bhowell.com (unverified [165.215.21.17]) by breckenridge.datatimes.com (Integralis SMTPRS 2.0.15) with SMTP id for ; Mon, 01 Jun 1998 15:42:00 -0500 Received: by okc-nt02.umi.bhowell.com with SMTP (Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52) id <01BD8D73.3AF174E0@okc-nt02.umi.bhowell.com>; Mon, 1 Jun 1998 15:37:48 -0500 Message-Id: From: "Sloan, Kyle" To: "'hardware@freebsd.org'" Subject: Digi Supported Devices Date: Mon, 1 Jun 1998 15:37:47 -0500 X-Mailer: Microsoft Exchange Server Internet Mail Connector Version 4.0.995.52 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 According to Digi's website...... Drivers for Digi products are included with the FreeBSD operating system for releases 2.2 and higher. For a list of the FreeBSD supported hardware, Please contact hardware@bsdi.com or http://www.freebsd.org The only thing for Digi that I see on the web is: Digiboard Sync/570i high-speed sync serial card However, the book from Walnut Creek CD-Rom shows that the Digi PC/X series is supported. Can you clarify which models of Digi Products are supported in the 2.2.6 Release? Kyle Sloan Data Communications Engineer Oklahoma City Operations UMI - A Bell & Howell Company Direct 405.601.6969 Fax 405.601.6800 [Katsu Hayabi - Victory at the speed of sunlight. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 1 19:30:02 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id TAA13290 for freebsd-hardware-outgoing; Mon, 1 Jun 1998 19:30:02 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from quark.ChrisBowman.com (crbowman.erols.com [209.122.47.155]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id TAA13140 for ; Mon, 1 Jun 1998 19:29:23 -0700 (PDT) (envelope-from crb@ChrisBowman.com) Received: from localhost (crb@localhost) by quark.ChrisBowman.com (8.8.8/8.8.8) with SMTP id WAA02079; Mon, 1 Jun 1998 22:30:41 -0500 (EST) (envelope-from crb@ChrisBowman.com) X-Authentication-Warning: quark.ChrisBowman.com: crb owned process doing -bs Date: Mon, 1 Jun 1998 22:30:41 -0500 (EST) From: "Christopher R. Bowman" To: "John T. Farmer" cc: hardware@FreeBSD.ORG Subject: Re: Wide SCSI adaptors... In-Reply-To: <199806011746.NAA01141@sabre.goldsword.com> 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 Mon, 1 Jun 1998, John T. Farmer wrote: > >Looking at getting a Wide SCSI PCI card for a new server here. >Motherboard is a Tyan dual processor "Tomcat III." So far I've >found 2 possibliities, the ASUS SC275, and the Tekram >390F item. The tekram appears to decent & I get grab one for $30 >to $60 less than the ASUS. > >I know the ASUS card works well in FreeBSD, but if the Tekram is as >good & supported (It does appear to be a plain 875 board with onboard >flashable BIOS), well saving $30 to $60 _always_ appeals to the Scots >blood in me (:^>, being part Scots, I guess I can say such things..) > >So, ASUS or Tekram? Opinions, experiences, advice wanted. Guarantied >that I will listen, & do something! > >Thanks >John > >ps. In case it matters, the adpator (& the Tyan dual Tomcat) are > going into a web server. While plain scsi would prob. be fast > enough, I have some wide Seagate 2.1gb Hawks just setting here. > (couldn't get them sold fast enough before prices tumbled... > Did get the Adaptec 3940W card sold tho...) Never had a problem with my 390F, been very happy with it. Don't have anything to compareit with though. --------- Christopher R. Bowman crb@ChrisBowman.com My home page To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Mon Jun 1 21:32:56 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA06250 for freebsd-hardware-outgoing; Mon, 1 Jun 1998 21:32:56 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA06230 for ; Mon, 1 Jun 1998 21:32:49 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id VAA12291; Mon, 1 Jun 1998 21:32:13 -0700 (PDT) Message-Id: <199806020432.VAA12291@implode.root.com> To: Scott Drassinower cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Intel EtherExpress 100+ problems In-reply-to: Your message of "Mon, 01 Jun 1998 10:07:09 EDT." From: David Greenman Reply-To: dg@root.com Date: Mon, 01 Jun 1998 21:32:13 -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >So the problem that I'm having with NFS will likely occur with a 3Com or >SMC card as well? There is no workaround at all for this, just deal with >messed up nfs or run at 10 megabits? I was only suggesting that our NFS has problems in some corner cases. Usually this only shows up when there are multiple clients writing to the same file, and the usual result is file corruption, not a client/server wedge. Our NFS also doesn't recover properly from certain kinds of failures. All of these issues are being looked at in -current and there have been a few fixes that have trickled back to -stable...not that I think those will fix your problem, however. I think your troubles are at the link level and are symptoms of packet loss. Try setting both sides to forced 100/half. I've had some compatiblity problems with Cisco router-switches when connected to other vendor switches in 100/full. For some reason switching to half duplex causes the problems to go away (and it's not actually a duplex problem as that was verified to be correct on both ends...weird). I haven't seen the problems you are having with NFS and the Cisco/Intel combination. It sounds like there is packet loss in some cases which is causing NFS clients to wedge. Are you sure that your cable is up to spec? Are there any interface errors on either side? -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 Mon Jun 1 22:48:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id WAA19779 for freebsd-hardware-outgoing; Mon, 1 Jun 1998 22:48:52 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from duey.hs.wolves.k12.mo.us (root@duey.hs.wolves.k12.mo.us [207.160.214.9]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id WAA19755 for ; Mon, 1 Jun 1998 22:48:43 -0700 (PDT) (envelope-from cdillon@wolves.k12.mo.us) Received: from duey.hs.wolves.k12.mo.us (cdillon@duey.hs.wolves.k12.mo.us [207.160.214.9]) by duey.hs.wolves.k12.mo.us (8.8.7/8.8.7) with SMTP id AAA14378; Tue, 2 Jun 1998 00:48:36 -0500 (CDT) (envelope-from cdillon@wolves.k12.mo.us) Date: Tue, 2 Jun 1998 00:48:36 -0500 (CDT) From: Chris Dillon X-Sender: cdillon@duey.hs.wolves.k12.mo.us To: "John T. Farmer" cc: hardware@FreeBSD.ORG Subject: Re: Wide SCSI adaptors... In-Reply-To: <199806011746.NAA01141@sabre.goldsword.com> 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 Mon, 1 Jun 1998, John T. Farmer wrote: > Looking at getting a Wide SCSI PCI card for a new server here. > Motherboard is a Tyan dual processor "Tomcat III." So far I've > found 2 possibliities, the ASUS SC275, and the Tekram > 390F item. The tekram appears to decent & I get grab one for $30 > to $60 less than the ASUS. > > I know the ASUS card works well in FreeBSD, but if the Tekram is as > good & supported (It does appear to be a plain 875 board with onboard > flashable BIOS), well saving $30 to $60 _always_ appeals to the Scots > blood in me (:^>, being part Scots, I guess I can say such things..) > > So, ASUS or Tekram? Opinions, experiences, advice wanted. Guarantied > that I will listen, & do something! I have a Tekram DC-390F in this box and it has worked flawlessly for quite some time now. I'd say the only difference between the ASUS and the Tekram card is the BIOS, which FreeBSD probably couldn't care less about anyway. This card has also worked just fine when I've booted to DOS/Win95 (which is extremely rare). -- Chris Dillon - cdillon@wolves.k12.mo.us - cdillon@inter-linc.net /* FreeBSD: The fastest and most stable server OS on the planet. For Intel x86 and compatibles (SPARC and Alpha under development) (http://www.freebsd.org) */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 2 06:42:11 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id GAA25571 for freebsd-hardware-outgoing; Tue, 2 Jun 1998 06:42:11 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mail.keyworld.net (root@mail.keyworld.net [194.21.164.2]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA25544 for ; Tue, 2 Jun 1998 06:42:06 -0700 (PDT) (envelope-from mailing@keyworld.net) Received: from scanner (scanner.keyworld.net [194.21.164.17]) by mail.keyworld.net (8.8.5/8.8.4) with ESMTP id PAA00533 for ; Tue, 2 Jun 1998 15:37:48 +0200 Message-Id: <199806021337.PAA00533@mail.keyworld.net> From: "KeyWORLD" To: Subject: Problems with SCSI disks Date: Tue, 2 Jun 1998 15:43:51 +0200 X-MSMail-Priority: Normal X-Priority: 3 X-Mailer: Microsoft Internet Mail 4.70.1161 MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi all, After installing FreeBSD 2.2.2 and 2.2.5, and trying to reboot from a Fujitsu 4.3G SCSI hard disk, I always get the message saying No Bootable Partition. I have also 4 IDE devices installed. When I get into the FDISK program from the installation, I see that the partition on the SCSI hard disk is still not set to active (typing s from the fdisk program) Even by doing so again and again, it still does not boot up. I have formatted the hard disk using the FDISK 32-bit install disk which comes with (sorry about this) Windows 95 and after formatting the hd with the system files, it boots up as usual. I also tried making a low level format and no go. Any ideas ??? Regards, Nicholas Aquilina nicholas@keyworld.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 2 07:12:39 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id HAA01735 for freebsd-hardware-outgoing; Tue, 2 Jun 1998 07:12:39 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from russian-caravan.cloud9.net (russian-caravan.cloud9.net [168.100.1.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id HAA01729 for ; Tue, 2 Jun 1998 07:12:35 -0700 (PDT) (envelope-from scottd@cloud9.net) Received: from earl-grey.cloud9.net (xkfs4sz+Nrf2SFd6Av41SBiEoiaha3IR@earl-grey.cloud9.net [168.100.1.1]) by russian-caravan.cloud9.net (8.8.8/8.8.8) with SMTP id KAA22037; Tue, 2 Jun 1998 10:12:31 -0400 (EDT) Date: Tue, 2 Jun 1998 10:12:30 -0400 (EDT) From: Scott Drassinower Reply-To: Scott Drassinower To: David Greenman cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Intel EtherExpress 100+ problems In-Reply-To: <199806020432.VAA12291@implode.root.com> 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 I will try forcing the two machines to use 100/half in the switch. The interface counters for the Cisco really don't show any major errors or drops for those interfaces (there were a handful of input errors for the server, none for other machines). I don't remember whose cable it is, but I think it is Enhanced Cat 5, and the cables are all about 6 feet. I could try different cable, but I'm not sure that would change the situation. netstat -i on the client has no interface errors, netstat -i on the server has one output error but no input errors. I might be able to get a hold of another 100 megabit switch, perhaps an Intel, and we can see if the problem goes away or if it's the same. I'm wondering if there are other people running 100 megabit that might be able to duplicate this problem. -- Scott M. Drassinower scottd@cloud9.net Cloud 9 Consulting, Inc. White Plains, NY +1 914 696-4000 http://www.cloud9.net On Mon, 1 Jun 1998, David Greenman wrote: > >So the problem that I'm having with NFS will likely occur with a 3Com or > >SMC card as well? There is no workaround at all for this, just deal with > >messed up nfs or run at 10 megabits? > > I was only suggesting that our NFS has problems in some corner cases. > Usually this only shows up when there are multiple clients writing to the > same file, and the usual result is file corruption, not a client/server > wedge. Our NFS also doesn't recover properly from certain kinds of failures. > All of these issues are being looked at in -current and there have been a > few fixes that have trickled back to -stable...not that I think those will > fix your problem, however. I think your troubles are at the link level and > are symptoms of packet loss. > Try setting both sides to forced 100/half. I've had some compatiblity > problems with Cisco router-switches when connected to other vendor switches > in 100/full. For some reason switching to half duplex causes the problems > to go away (and it's not actually a duplex problem as that was verified to > be correct on both ends...weird). > I haven't seen the problems you are having with NFS and the Cisco/Intel > combination. It sounds like there is packet loss in some cases which is > causing NFS clients to wedge. Are you sure that your cable is up to spec? > Are there any interface errors on either side? > > -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 Tue Jun 2 12:39:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA25532 for freebsd-hardware-outgoing; Tue, 2 Jun 1998 12:39:57 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from quark.ChrisBowman.com (crbowman.erols.com [209.122.47.155]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA25524 for ; Tue, 2 Jun 1998 12:39:44 -0700 (PDT) (envelope-from crb@ChrisBowman.com) Received: from localhost (crb@localhost) by quark.ChrisBowman.com (8.8.8/8.8.8) with SMTP id PAA00345; Tue, 2 Jun 1998 15:39:48 -0500 (EST) (envelope-from crb@ChrisBowman.com) X-Authentication-Warning: quark.ChrisBowman.com: crb owned process doing -bs Date: Tue, 2 Jun 1998 15:39:47 -0500 (EST) From: "Christopher R. Bowman" To: KeyWORLD cc: hardware@FreeBSD.ORG Subject: Re: Problems with SCSI disks In-Reply-To: <199806021337.PAA00533@mail.keyworld.net> 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, 2 Jun 1998, KeyWORLD wrote: >Hi all, > >After installing FreeBSD 2.2.2 and 2.2.5, and trying to reboot from a >Fujitsu 4.3G SCSI hard disk, I always get the message saying No Bootable >Partition. >I have also 4 IDE devices installed. > >When I get into the FDISK program from the installation, I see that the >partition on the SCSI hard disk is still not set to active (typing s from >the fdisk program) >Even by doing so again and again, it still does not boot up. > >I have formatted the hard disk using the FDISK 32-bit install disk which >comes with (sorry about this) Windows 95 and after formatting the hd with >the system files, it boots up as usual. > >I also tried making a low level format and no go. I also have a mixed IDE SCSI system on which I boot FreeBSD and Win 95. I don't know if the FreeBSD boot loader (BootEasy) will boot from the SCSI drive on a mixed system. I did the following. I have installed Win 95 on my IDE drive. I installed FreeBSD on my second SCSI drive. I used OS-BS version 2.0 beta 8 (this seems to be the latest free version) booter available on the FreeBSD CDROM (tools folder in a self extracting archive called Osbsbeta) I used this to create a boot up screen which gives me 15 seconds to select an OS and then boot into FreeBSD if none is selected. It can also be set to mark as active which ever partition it finally decides to boot from. This works fine for Win 95 since it is on the IDE drive. But FreeBSD gets confused about the boot disk when attempting to load the root partition so I needed to boot using the command 2:sd(1,a)/kernel which tells FreeBSD to boot from BIOS disk 2 (First IDE is 0 first SCSI is 1 second SCSI is 2) second DOS partion/FreeBSD slice (my first partition on the second scsi drive has is a DOS partition) and then use the a partition inside the FreeBSD slice. Once you have FreeBSD running you can put the 2:sd(1,a)/kernel command in a file called /boot.config and it will be done automagically for you from then on. Hope this helps. I would be happy to answer any questions if I can. --------- Christopher R. Bowman crb@ChrisBowman.com My home page To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Tue Jun 2 15:45:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA25637 for freebsd-hardware-outgoing; Tue, 2 Jun 1998 15:45:42 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA25629 for ; Tue, 2 Jun 1998 15:45:36 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id PAA18069; Tue, 2 Jun 1998 15:44:54 -0700 (PDT) Message-Id: <199806022244.PAA18069@implode.root.com> To: Scott Drassinower cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Intel EtherExpress 100+ problems In-reply-to: Your message of "Tue, 02 Jun 1998 10:12:30 EDT." From: David Greenman Reply-To: dg@root.com Date: Tue, 02 Jun 1998 15:44:54 -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >netstat -i on the client has no interface errors, netstat -i on the server >has one output error but no input errors. I'm not too surprised by this; the one case where I saw the lossage problem with the Cisco didn't show any errors on either side, yet there was 20% packet loss. I'm sure if I had been using NFS in that case that things would have sucked badly. >I might be able to get a hold of another 100 megabit switch, perhaps an >Intel, and we can see if the problem goes away or if it's the same. I'm >wondering if there are other people running 100 megabit that might be able >to duplicate this problem. I use Intel Pro/100B and 100+ cards in all of my machines here on a fast ether switch in full duplex with NFS. I've never had any problems. We also do the same with freefall/hub/etc. While we've had problems with NFS there when one of the machines goes down, I don't recall seeing any problems like you're having with selective processes wedging. -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 Tue Jun 2 15:50:52 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA26329 for freebsd-hardware-outgoing; Tue, 2 Jun 1998 15:50:52 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from russian-caravan.cloud9.net (russian-caravan.cloud9.net [168.100.1.4]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA26319 for ; Tue, 2 Jun 1998 15:50:44 -0700 (PDT) (envelope-from scottd@cloud9.net) Received: from earl-grey.cloud9.net (gt+HSMAAPGzaaQo+lr8+ZMsjZaSNtJZ4@earl-grey.cloud9.net [168.100.1.1]) by russian-caravan.cloud9.net (8.8.8/8.8.8) with SMTP id SAA13048; Tue, 2 Jun 1998 18:50:42 -0400 (EDT) Date: Tue, 2 Jun 1998 18:50:42 -0400 (EDT) From: Scott Drassinower To: David Greenman cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Intel EtherExpress 100+ problems In-Reply-To: <199806022244.PAA18069@implode.root.com> 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 Which switch are you using? -- Scott M. Drassinower scottd@cloud9.net Cloud 9 Consulting, Inc. White Plains, NY +1 914 696-4000 http://www.cloud9.net On Tue, 2 Jun 1998, David Greenman wrote: > >netstat -i on the client has no interface errors, netstat -i on the server > >has one output error but no input errors. > > I'm not too surprised by this; the one case where I saw the lossage problem > with the Cisco didn't show any errors on either side, yet there was 20% packet > loss. I'm sure if I had been using NFS in that case that things would have > sucked badly. > > >I might be able to get a hold of another 100 megabit switch, perhaps an > >Intel, and we can see if the problem goes away or if it's the same. I'm > >wondering if there are other people running 100 megabit that might be able > >to duplicate this problem. > > I use Intel Pro/100B and 100+ cards in all of my machines here on a fast > ether switch in full duplex with NFS. I've never had any problems. We also > do the same with freefall/hub/etc. While we've had problems with NFS there > when one of the machines goes down, I don't recall seeing any problems like > you're having with selective processes wedging. > > -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 Tue Jun 2 16:28:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA03437 for freebsd-hardware-outgoing; Tue, 2 Jun 1998 16:28:06 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA03351 for ; Tue, 2 Jun 1998 16:27:52 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id QAA18407; Tue, 2 Jun 1998 16:27:04 -0700 (PDT) Message-Id: <199806022327.QAA18407@implode.root.com> To: Scott Drassinower cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Intel EtherExpress 100+ problems In-reply-to: Your message of "Tue, 02 Jun 1998 18:50:42 EDT." From: David Greenman Reply-To: dg@root.com Date: Tue, 02 Jun 1998 16:27:04 -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >Which switch are you using? In both cases, we're using inexpensive Lantronix LSW8F (and managed LSW8F-S) switches. The LSW8F-S doesn't get along with a Cisco 7513 in full duplex, however. -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 Thu Jun 4 01:42:57 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id BAA28921 for freebsd-hardware-outgoing; Thu, 4 Jun 1998 01:42:57 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from fox.doc.ic.ac.uk (fox.doc.ic.ac.uk [146.169.1.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id BAA28916 for ; Thu, 4 Jun 1998 01:42:52 -0700 (PDT) (envelope-from md@doc.ic.ac.uk) Received: from theon.doc.ic.ac.uk ([146.169.1.33] helo=doc.ic.ac.uk) by fox.doc.ic.ac.uk with esmtp (Exim 1.92 #1) id 0yhVbS-000251-00; Thu, 4 Jun 1998 09:42:30 +0100 Message-ID: <35765DF3.ABEC9C7A@doc.ic.ac.uk> Date: Thu, 04 Jun 1998 09:42:27 +0100 From: Mark Dawson X-Mailer: Mozilla 4.05 [en] (X11; I; Linux 2.0.32 i586) MIME-Version: 1.0 To: freebsd-hardware@FreeBSD.ORG Subject: PCI bus not probed Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org FreeBSD-2.2.6 cannot see cards on one of the pci buses in a Compaq ProLiant 1600R. I enclose the results of booting with -v . The upshot is that three of the six PCI slots aren't available - this isn't a big problem for me at the moment but I'd like to get everything in order while I have the opportunity to do some testing before it goes into service. Many thanks, Mark p.s. When a chip isn't recognised why not display a URL saying how/where to report the problem? --- Copyright (c) 1992-1998 FreeBSD Inc. Copyright (c) 1982, 1986, 1989, 1991, 1993 The Regents of the University of California. All rights reserved. FreeBSD 2.2.6-STABLE #0: Wed Jun 3 15:37:07 BST 1998 root@hex.doc.ic.ac.uk:/usr/src/sys/compile/HEX Calibrating clock(s) ... i586 clock: 299521257 Hz, i8254 clock: 1193171 Hz CLK_USE_I8254_CALIBRATION not specified - using default frequency CLK_USE_I586_CALIBRATION not specified - using old calibration method CPU: Pentium II (299.53-MHz 686-class CPU) Origin = "GenuineIntel" Id = 0x634 Stepping=4 Features=0x80f9ff real memory = 335544320 (327680K bytes) Physical memory chunk(s): 0x00001000 - 0x0009efff, 647168 bytes (158 pages) 0x0021b000 - 0x13ffdfff, 333328384 bytes (81379 pages) avail memory = 326590464 (318936K bytes) eisa0: Probing for devices on the EISA bus pcibus_setup(1): mode 1 addr port (0x0cf8) is 0x00000000 pcibus_setup(1a): mode1res=0x80000000 (0x80000000) pcibus_check: device 0 is there (id=00051166) Probing for devices on PCI bus 0: configuration mode 1 allows 32 devices. chip0 rev 3 on pci0:0:0 vga0 rev 34 int a irq ?? on pci0:6:0 mapreg[10] type=0 addr=b7000000 size=1000000. ncr0 rev 4 int a irq 5 on pci0:8:0 mapreg[10] type=1 addr=00006000 size=0100. mapreg[14] type=0 addr=c6cfef00 size=0100. mapreg[18] type=0 addr=c6cff000 size=1000. reg20: virtual=0xf6df5f00 physical=0xc6cfef00 size=0x100 reg24: virtual=0xf6df6000 physical=0xc6cff000 size=0x1000 ncr0: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo ncr0: single-ended, open drain IRQ driver, using on-chip SRAM ncr0: restart (scsi reset). ncr0 scanning for targets 0..6 and 8..15 (V2 pl24 96/12/14) ncr0 waiting for scsi devices to settle chip1 rev 7 on pci0:10:0 bridge from pci0 to pci1 through 1. mapping regs: io:22807171 mem:c6e0c6e0 pmem:bff0b800 fxp0 rev 4 int a irq 11 on pci0:11:0 mapreg[10] type=0 addr=b6fff000 size=1000. mapreg[14] type=1 addr=00006400 size=0020. mapreg[18] type=0 addr=c6d00000 size=100000. reg16: virtual=0xf6df7000 physical=0xb6fff000 size=0x1000 fxp0: Ethernet address 00:a0:c9:92:c8:d9 bpf: fxp0 attached chip2 rev 7 on pci0:15:0 chip3 rev 3 on pci0:17:0 pci0: uses 17834240 bytes of memory from b6fff000 upto c6efffff. pci0: uses 288 bytes of I/O space from 6000 upto 7fff. pci0: subordinate busses from 1 upto 1. Probing for devices on PCI bus 1: ida0 rev 3 int a irq 11 on pci1:0:0 mapreg[10] type=1 addr=00007000 size=0100. [pci1 uses memory from c6e00000 to c6efffff] mapreg[14] type=0 addr=c6efff00 size=0100. [pci1 uses memory from c6e00000 to c6efffff] mapreg[18] type=0 addr=b8000000 size=8000000. reg20: virtual=0xf6df8f00 physical=0xc6efff00 size=0x100 using shared irq 11. ida0: drvs=3 firm_rev=2.02 ida0: unit 0 (id0): id0: 9000MB (18433440 total sec), 2259 cyl, 255 head, 32 sec, bytes/sec 512 ida0: unit 1 (id1): id1: 47852MB (98001600 total sec), 12010 cyl, 255 head, 32 sec, bytes/sec 512 ida0: unit 2 (id2): id2: 47338MB (96948960 total sec), 11881 cyl, 255 head, 32 sec, bytes/sec 512 pci1: uses 134217984 bytes of memory from b8000000 upto c6efffff. pci1: uses 256 bytes of I/O space from 7000 upto 70ff. Probing for devices on PCI bus 2: pci2:7: Compaq, device=0xae43, class=network (misc) int a irq 9 [no driver assigned] map(10): io(8400) map(14): mem32(c6ffeef0) ncr1 rev 4 int a irq 10 on pci2:9:0 mapreg[10] type=1 addr=00008000 size=0100. mapreg[14] type=0 addr=c6ffef00 size=0100. mapreg[18] type=0 addr=c6fff000 size=1000. reg20: virtual=0xf6df9f00 physical=0xc6ffef00 size=0x100 reg24: virtual=0xf6dfa000 physical=0xc6fff000 size=0x1000 ncr1: minsync=12, maxsync=137, maxoffs=16, 128 dwords burst, large dma fifo ncr1: single-ended, open drain IRQ driver, using on-chip SRAM ncr1: restart (scsi reset). ncr1 scanning for targets 0..6 and 8..15 (V2 pl24 96/12/14) ncr1 waiting for scsi devices to settle pci2: uses 4352 bytes of memory from c6ffef00 upto c6ffffff. pci2: uses 256 bytes of I/O space from 8000 upto 80ff. Probing for devices on PCI bus 3: Probing for devices on the ISA bus: sc0: the current keyboard controller command byte 0065 kbdio: DIAGNOSE status:0055 kbdio: TEST_KBD_PORT status:0000 kbdio: RESET_KBD return code:00fa kbdio: RESET_KBD status:00aa sc0 at 0x60-0x6f irq 1 on motherboard sc0: BIOS video mode:3 sc0: VGA registers upon power-up 50 18 10 00 10 00 03 00 02 67 5f 4f 50 82 55 81 bf 1f 00 4f 0d 0e 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 sc0: video mode:24 sc0: VGA registers 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 sc0: VGA registers 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 sc0: rows_offset:1 sc0: VGA color <16 virtual consoles, flags=0x0> sio0 at 0x3f8-0x3ff irq 4 on isa sio0: type 16550A sio1 at 0x2f8-0x2ff irq 3 on isa sio1: type 16550A lpt0 at 0x3bc-0x3c3 irq 7 on isa lpt0: Interrupt-driven port lp0: TCP/IP capable interface bpf: lp0 attached psm0: disabled, not probed. fdc0 at 0x3f0-0x3f7 irq 6 drq 2 on isa fdc0: FIFO enabled, 8 bytes threshold fd0: 1.44MB 3.5in ida0 not found stub0 not found at 0x1f0 npx0 flags 0x1 on motherboard npx0: INT 16 interface imasks: bio c0080c60, tty c007089a, net c007089a BIOS Geometries: 0:03fffe20 0..1023=1024 cylinders, 0..254=255 heads, 1..32=32 sectors 1:03fffe20 0..1023=1024 cylinders, 0..254=255 heads, 1..32=32 sectors 2:03fffe20 0..1023=1024 cylinders, 0..254=255 heads, 1..32=32 sectors 0 accounted for Device configuration finished. bpf: tun0 attached bpf: sl0 attached bpf: lo0 attached Considering FFS root f/s. id0s1: type 0xa5, start 73440, end = 18433439, size 18360000 : OK id0s3: type 0x12, start 32, end = 73439, size 73408 : OK id1s1: type 0xa5, start 32, end = 98001599, size 98001568 : OK id2s1: type 0xa5, start 32, end = 96948959, size 96948928 : OK id2s1: type 0xa5, start 32, end = 96948959, size 96948928 : OK id1s1: type 0xa5, start 32, end = 98001599, size 98001568 : OK id1s1: type 0xa5, start 32, end = 98001599, size 98001568 : OK id2s1: type 0xa5, start 32, end = 96948959, size 96948928 : OK id2s1: type 0xa5, start 32, end = 96948959, size 96948928 : OK id1s1: type 0xa5, start 32, end = 98001599, size 98001568 : OK id2s1: type 0xa5, start 32, end = 96948959, size 96948928 : OK id1s1: type 0xa5, start 32, end = 98001599, size 98001568 : OK id1s1: type 0xa5, start 32, end = 98001599, size 98001568 : OK id2s1: type 0xa5, start 32, end = 96948959, size 96948928 : OK To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Thu Jun 4 21:16:59 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA22090 for freebsd-hardware-outgoing; Thu, 4 Jun 1998 21:16:59 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mail1.panix.com (mail1.panix.com [166.84.0.212]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA22065 for ; Thu, 4 Jun 1998 21:16:43 -0700 (PDT) (envelope-from dexter@dexter.dialup.access.net) Received: from dexter.dialup.access.net (dexter.dialup.access.net [166.84.192.199]) by mail1.panix.com (8.8.8/8.8.8/PanixM1.3) with ESMTP id AAA25273 for ; Fri, 5 Jun 1998 00:16:31 -0400 (EDT) Received: (from dexter@localhost) by dexter.dialup.access.net (8.8.7/8.8.5) id AAA03045; Fri, 5 Jun 1998 00:16:35 -0400 (EDT) Message-ID: <19980605001628.24925@panix.com> Date: Fri, 5 Jun 1998 00:16:28 -0400 From: Dexter McNeil To: hardware@FreeBSD.ORG Subject: DPT driver in V2.2.6 - EISA support anytime soon? Reply-To: dexter@panix.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.88e Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Hi, I have the 2.2.6 release CDROMS, and have it up on a test box (still need to do a cvsup...) I noticed that there is now a DPT device driver, but support for EISA controllers is listed in the 'to do' column. :-( Any idea when (if?) there will be support for the EISA controllers? I have two of them (PM2012B and a 2122) that I'd like to use with FreeBSD. I'd offer to do the work, but unless someone can draw a paint-by-numbers outline that I can fill in, I'd be pretty lost.... Thanks for the great O/S! regards, Dexter McNeil dexter@panix.com To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jun 5 04:00:58 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA26036 for freebsd-hardware-outgoing; Fri, 5 Jun 1998 04:00:58 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from mailgate.cadence.com (mailgate.Cadence.COM [158.140.2.1]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id EAA26025 for ; Fri, 5 Jun 1998 04:00:53 -0700 (PDT) (envelope-from dmlb@ragnet.demon.co.uk) Received: (from smap@localhost) by mailgate.cadence.com (8.8.5/8.6.8) id EAA05202 for ; Fri, 5 Jun 1998 04:00:52 -0700 (PDT) Message-Id: <199806051100.EAA05202@mailgate.cadence.com> Received: from unknown(194.32.96.130) by mailgate.cadence.com via smap (mjr-v1.2) id xma897044450.005194; Fri, 5 Jun 98 04:00:50 -0700 Comments: Authenticated sender is From: "Duncan Barclay" To: freebsd-hardware@FreeBSD.ORG Date: Fri, 5 Jun 1998 12:00:31 +0000 MIME-Version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7BIT Subject: Anyone used SOYO 5EH Skt 7 wtith ETAQ chipset? Reply-to: dmlb@ragnet.demon.co.uk X-mailer: Pegasus Mail for Win32 (v2.53/R1) Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Has anyone used these boards? Here in the UK getting MVP3 boards is a bit difficult (the FIC boat hasn't docked yet!). Also does anyone know of any Aladdin 5 AT boards? Thanks Duncan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jun 5 08:53:06 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17299 for freebsd-hardware-outgoing; Fri, 5 Jun 1998 08:53:06 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from sasami.jurai.net (winter@sasami.jurai.net [207.153.65.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17159 for ; Fri, 5 Jun 1998 08:51:33 -0700 (PDT) (envelope-from winter@jurai.net) Received: from localhost (winter@localhost) by sasami.jurai.net (8.8.8/8.8.7) with SMTP id LAA21393; Fri, 5 Jun 1998 11:51:27 -0400 (EDT) Date: Fri, 5 Jun 1998 11:51:27 -0400 (EDT) From: "Matthew N. Dodd" To: Dexter McNeil cc: hardware@FreeBSD.ORG Subject: Re: DPT driver in V2.2.6 - EISA support anytime soon? In-Reply-To: <19980605001628.24925@panix.com> 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 Fri, 5 Jun 1998, Dexter McNeil wrote: > I have the 2.2.6 release CDROMS, and have it up on a test box > (still need to do a cvsup...) I noticed that there is now a DPT device > driver, but support for EISA controllers is listed in the 'to do' > column. :-( Check sys/i386/eisa/dpt_eisa.[ch] :) > Any idea when (if?) there will be support for the EISA > controllers? I have two of them (PM2012B and a 2122) that I'd like to > use with FreeBSD. I'd offer to do the work, but unless someone can draw > a paint-by-numbers outline that I can fill in, I'd be pretty lost.... I've got a PM2012B which I was unable to get working correctly (may just be me) and a PM2022 which does work. There are some problems with the EISA probe/attach that I still have to fix but I'd ask that you compile a kernel with the drivers and see if it works. I've been trying to work out a better way of retrieveing the board config but my attempts to read any useful information from the EISA config registers have produced garbage. The current method sets up a mostly empty DPT config structure and issues an EATA command to read the board config. I suspect this causes problems with some versions of the card (it did with some of mine.) but not all. Anyhow, try it and see what you get. /* Matthew N. Dodd | A memory retaining a love you had for life winter@jurai.net | As cruel as it seems nothing ever seems to http://www.jurai.net/~winter | go right - FLA M 3.1:53 */ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jun 5 09:25:47 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA21720 for freebsd-hardware-outgoing; Fri, 5 Jun 1998 09:25:47 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from symbion.srrc.usda.gov ([199.78.118.118]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA21697 for ; Fri, 5 Jun 1998 09:25:35 -0700 (PDT) (envelope-from glenn@nola.srrc.usda.gov) Received: from nola.srrc.usda.gov (localhost.srrc.usda.gov [127.0.0.1]) by symbion.srrc.usda.gov (8.8.8/8.8.8) with ESMTP id LAA18241 for ; Fri, 5 Jun 1998 11:25:28 -0500 (CDT) (envelope-from glenn@nola.srrc.usda.gov) Message-Id: <199806051625.LAA18241@symbion.srrc.usda.gov> X-Mailer: exmh version 2.0.2 2/24/98 To: hardware@FreeBSD.ORG From: Glenn Johnson Subject: advice for fast ethernet hardware Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Jun 1998 11:25:27 -0500 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have a cluster of FreeBSD worksations that have 3Com 3C905 NICs. They are currently hooked into a 10Mbps hub, which is connected to our 10Mbps LAN. I do a lot of transfers and NFS mounts between my machines and would like to take advantage of the 100Mbps NICs. My first question is, do the 3C509s work okay at 100Mbps? If so then, would it be worth the extra money to get a 10/100Mbps Switch as opposed to a 10/100Mbps hub? I have noticed a large difference in price for what seems to be similar equipment, dependent on the manufacturer, so brand recommendations would be extremely helpful. Performance and reliability are more important than price. I thank you in advance for your help. -- Glenn Johnson Technician USDA, ARS, SRRC gjohnson@nola.srrc.usda.gov To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jun 5 09:32:16 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA23125 for freebsd-hardware-outgoing; Fri, 5 Jun 1998 09:32:16 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from assurance ([206.29.49.3]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA22994 for ; Fri, 5 Jun 1998 09:31:43 -0700 (PDT) (envelope-from vshah@rstcorp.com) Received: (from uucp@localhost) by assurance (8.7.5/8.6.9) id MAA19067 for ; Fri, 5 Jun 1998 12:28:19 -0400 Received: from sandbox.rstcorp.com(206.29.49.63) by assurance.rstcorp.com via smap (V2.0) id xma019063; Fri, 5 Jun 98 12:28:10 -0400 Received: from fault.rstcorp.com (fault [206.29.49.18]) by sandbox.rstcorp.com (8.8.8/8.8.8) with ESMTP id MAA09235 for ; Fri, 5 Jun 1998 12:30:58 -0400 (EDT) Received: (from vshah@localhost) by fault.rstcorp.com (8.8.8/8.8.8) id MAA00332; Fri, 5 Jun 1998 12:29:57 -0400 (EDT) Date: Fri, 5 Jun 1998 12:29:57 -0400 (EDT) Message-Id: <199806051629.MAA00332@fault.rstcorp.com> From: "Viren R. Shah" To: freebsd-hardware@FreeBSD.ORG Subject: Inter EtherExpress PRO/100+ or 10/100B X-Mailer: VM 6.40 under 19.16 "Lille" XEmacs Lucid Reply-To: "Viren R. Shah" X-Face: )~y+U*K:yzjz{q<5lzpI_SVef'U.])9g[C9`1N@]u3,MHY7f*l7C)[_NjM4y4K8$uIUh|\u (K&&HS6,M!61&GMTk'mqmB/Qg]]X}"?TzsFl]"2v!bl8']dma.:^IY^a[lbOI>U:b<~FyK3q-p{HmZ mn~g.`~BE!5{2D:}Yi+\_KkWe?XaHj9$ko1k8iKLYv5*_2c8"G=?Up[}hn+7RNM(bzBZ_wWk6!Pf&B ?3Tcm7M7B~W%K/I0aX3]*=jP?aM]H6HBPT`oLk+0n^_;N\2\%|Rhy;p}34Q.jEsM\qtnxcm;ag%Nq Mime-Version: 1.0 (generated by tm-edit 7.106) Content-Type: text/plain; charset=US-ASCII Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org We are getting a new NIC for our FreeBSD NFS server (we are having problems with a 3COM 3c905 with spontaneous reboots and NFS timeouts on a 100baseT network). >From the mailing list archives, it seems that the Intel EtherExpress cards have the best driver (fxp). IS there any preference between the PRO 100+ and the PRO 10/100B? Is one better than the other? Can they both do autonegotiation, and full-duplex (as in does the driver work equally well with both cards)? I would appreciate a fast response, since we would like to get the server stable as soon as possible. Viren -- Viren R. Shah "I merely note, if you want to catch something, running after it isn't always the best way." -- Miles Vorkosigan (Lois McMaster Bujold, "The Mountains of Mourning") To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jun 5 09:38:50 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA24804 for freebsd-hardware-outgoing; Fri, 5 Jun 1998 09:38:50 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles182.castles.com [208.214.165.182]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA24690 for ; Fri, 5 Jun 1998 09:38:21 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id IAA01271; Fri, 5 Jun 1998 08:33:01 -0700 (PDT) Message-Id: <199806051533.IAA01271@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: Glenn Johnson cc: hardware@FreeBSD.ORG Subject: Re: advice for fast ethernet hardware In-reply-to: Your message of "Fri, 05 Jun 1998 11:25:27 CDT." <199806051625.LAA18241@symbion.srrc.usda.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Fri, 05 Jun 1998 08:33:01 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > I have a cluster of FreeBSD worksations that have 3Com 3C905 NICs. > They are currently hooked into a 10Mbps hub, which is connected to our > 10Mbps LAN. I do a lot of transfers and NFS mounts between my machines > and would like to take advantage of the 100Mbps NICs. Unfortunately, our support for the '905 currently *sucks*, so you're not going to be taking much advantage of them. 8( > My first question is, do the 3C509s work okay at 100Mbps? If so then, They work, but you would be better off selecting a card that's better supported. The Intel EtherExpress Pro 100+ is going for about $50 these days, and these are the top recommendation. > would it be worth the extra money to get a 10/100Mbps Switch as opposed > to a 10/ 100Mbps hub? This depends on your activity patterns. If you have a single server and many clients, then a switch is less useful. If you have a more incestuous arrangement, then a switch will give better results. But unless you're really pushing the network, it's unlikely that the difference will be worth the cost. > I have noticed a large difference in price for > what seems to be similar equipment, dependent on the manufacturer, so > brand recommendations would be extremely helpful. Performance and > reliability are more important than price. I thank you in advance for > your help. We're using a Lantronix switch for the freebsd.org machines; it appears to work just fine. I also have a D-Link 8-port 100MBps hub in my office - it was cheap and works "as desired". YMMV. -- \\ 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 Jun 5 11:15:43 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA12733 for freebsd-hardware-outgoing; Fri, 5 Jun 1998 11:15:43 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from pegasus.com (pegasus.com [206.127.225.31]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id LAA12432 for ; Fri, 5 Jun 1998 11:14:18 -0700 (PDT) (envelope-from richard@pegasus.com) Received: by pegasus.com (8.6.8/PEGASUS-2.2) id IAA20445; Fri, 5 Jun 1998 08:13:06 -1000 Date: Fri, 5 Jun 1998 08:13:06 -1000 From: richard@pegasus.com (Richard Foulk) Message-Id: <199806051813.IAA20445@pegasus.com> In-Reply-To: Glenn Johnson "advice for fast ethernet hardware" (Jun 5, 11:25am) X-Mailer: Mail User's Shell (7.2.5 10/14/92) To: Glenn Johnson , hardware@FreeBSD.ORG Subject: Re: advice for fast ethernet hardware Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org } } My first question is, do the 3C509s work okay at 100Mbps? If so then, would it } be worth the extra money to get a 10/100Mbps Switch as opposed to a 10/100Mbps } hub? I have noticed a large difference in price for what seems to be similar } equipment, dependent on the manufacturer, so brand recommendations would be } extremely helpful. Performance and reliability are more important than price. } I thank you in advance for your help. } -- Here's a recent test report on a bunch of Ethernet switches: http://www.data.com/lab_tests/quantity.html Richard To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Fri Jun 5 11:47:35 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id LAA18493 for freebsd-hardware-outgoing; Fri, 5 Jun 1998 11:47:35 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from panzer.plutotech.com (ken@panzer.plutotech.com [206.168.67.125]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id LAA18439 for ; Fri, 5 Jun 1998 11:47:05 -0700 (PDT) (envelope-from ken@panzer.plutotech.com) Received: (from ken@localhost) by panzer.plutotech.com (8.8.8/8.8.5) id MAA07195; Fri, 5 Jun 1998 12:46:54 -0600 (MDT) From: "Kenneth D. Merry" Message-Id: <199806051846.MAA07195@panzer.plutotech.com> Subject: Re: Inter EtherExpress PRO/100+ or 10/100B In-Reply-To: <199806051629.MAA00332@fault.rstcorp.com> from "Viren R. Shah" at "Jun 5, 98 12:29:57 pm" To: viren@rstcorp.com Date: Fri, 5 Jun 1998 12:46:53 -0600 (MDT) 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 Viren R. Shah wrote... > > > We are getting a new NIC for our FreeBSD NFS server (we are having > problems with a 3COM 3c905 with spontaneous reboots and NFS > timeouts on a 100baseT network). > > >From the mailing list archives, it seems that the Intel EtherExpress > cards have the best driver (fxp). IS there any preference between the > PRO 100+ and the PRO 10/100B? Is one better than the other? Can they > both do autonegotiation, and full-duplex (as in does the driver work > equally well with both cards)? We've got tons of both (Pro/100B and Pro/100+) cards here, and they both work fine. The B has an 82557 and separate PHY chip, and I think the Pro/100+ has an 82558, with the PHY part on board. A friend of mine has done tests, and says that the Pro/100+ is faster. In any case, it's newer. The driver works fine with either card, though. They can both do autonegotiaion, and I believe they can both do full duplex, although I've never tried it out. 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 Fri Jun 5 13:42:10 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id NAA09216 for freebsd-hardware-outgoing; Fri, 5 Jun 1998 13:42:10 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from implode.root.com (implode.root.com [198.145.90.17]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id NAA09109 for ; Fri, 5 Jun 1998 13:41:34 -0700 (PDT) (envelope-from root@implode.root.com) Received: from implode.root.com (localhost [127.0.0.1]) by implode.root.com (8.8.5/8.8.5) with ESMTP id NAA09723; Fri, 5 Jun 1998 13:40:21 -0700 (PDT) Message-Id: <199806052040.NAA09723@implode.root.com> To: "Viren R. Shah" cc: freebsd-hardware@FreeBSD.ORG Subject: Re: Inter EtherExpress PRO/100+ or 10/100B In-reply-to: Your message of "Fri, 05 Jun 1998 12:29:57 EDT." <199806051629.MAA00332@fault.rstcorp.com> From: David Greenman Reply-To: dg@root.com Date: Fri, 05 Jun 1998 13:40:21 -0700 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >>From the mailing list archives, it seems that the Intel EtherExpress >cards have the best driver (fxp). IS there any preference between the >PRO 100+ and the PRO 10/100B? Is one better than the other? Can they >both do autonegotiation, and full-duplex (as in does the driver work >equally well with both cards)? They should perform identically. I certainly saw no differences in performance in my tests here and it's my understanding that the NIC on the Pro/100+ (82558 chip) is simply an 82557 NIC + 82555 PHY...there are otherwise no other differences in the logic/design. -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 Fri Jun 5 16:10:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id QAA07842 for freebsd-hardware-outgoing; Fri, 5 Jun 1998 16:10:55 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from Octopussy.MI.Uni-Koeln.DE (Octopussy.MI.Uni-Koeln.DE [134.95.166.20]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id QAA07770; Fri, 5 Jun 1998 16:10:29 -0700 (PDT) (envelope-from se@dialup124.zpr.uni-koeln.de) Received: from dialup124.zpr.Uni-Koeln.DE (dialup124.zpr.Uni-Koeln.DE [134.95.219.124]) by Octopussy.MI.Uni-Koeln.DE (8.8.8/8.8.8) with ESMTP id BAA15791; Sat, 6 Jun 1998 01:10:23 +0200 (MET DST) Received: (from se@localhost) by dialup124.zpr.Uni-Koeln.DE (8.8.8/8.6.9) id BAA06838; Sat, 6 Jun 1998 01:03:33 +0200 (CEST) X-Face: " Date: Sat, 6 Jun 1998 01:03:33 +0200 From: Stefan Esser To: Mark Dawson , freebsd-hardware@FreeBSD.ORG Cc: Stefan Esser Subject: Re: PCI bus not probed References: <35765DF3.ABEC9C7A@doc.ic.ac.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.89i In-Reply-To: <35765DF3.ABEC9C7A@doc.ic.ac.uk>; from Mark Dawson on Thu, Jun 04, 1998 at 09:42:27AM +0100 Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On 1998-06-04 09:42 +0100, Mark Dawson wrote: > FreeBSD-2.2.6 cannot see cards on one of the pci buses in a Compaq > ProLiant 1600R. I enclose the results of booting with -v . The upshot > is that three of the six PCI slots aren't available - this isn't a big > problem for me at the moment but I'd like to get everything in order > while I have the opportunity to do some testing before it goes into > service. Support for the dual directly attached host bridge chips used in the ProLiant 1600 was added as of March, 1998. Please fetch /sys/pci/pcisupport.c revision 1.40.2.7 from some FreeBSD mirror, or apply the following patch against revision 1.40.2.6 of that file ... Regards, STefan Index: /sys_22/pci/pcisupport.c =================================================================== RCS file: /usr/cvs/src/sys/pci/pcisupport.c,v retrieving revision 1.40.2.6 retrieving revision 1.40.2.7 diff -C2 -r1.40.2.6 -r1.40.2.7 *** pcisupport.c 1998/03/01 10:12:00 1.40.2.6 --- pcisupport.c 1998/03/26 22:28:42 1.40.2.7 *************** *** 1,5 **** /************************************************************************** ** ! ** $Id: pcisupport.c,v 1.40.2.6 1998/03/01 10:12:00 asami Exp $ ** ** Device driver for DEC/INTEL PCI chipsets. --- 1,5 ---- /************************************************************************** ** ! ** $Id: pcisupport.c,v 1.40.2.7 1998/03/26 22:28:42 se Exp $ ** ** Device driver for DEC/INTEL PCI chipsets. *************** *** 52,55 **** --- 52,57 ---- static void config_orion (pcici_t tag); + static void config_i1225 (pcici_t tag); + static void config_Ross (pcici_t tag); /*--------------------------------------------------------- *************** *** 171,174 **** --- 173,178 ---- case 0x84c58086: return ("Intel 82454GX (Orion) host to PCI bridge"); + case 0x00051166: + return ("Ross (?) host to PCI bridge"); case 0x00221014: return ("IBM 82351 PCI-PCI bridge"); *************** *** 700,703 **** --- 704,718 ---- static void + config_Ross(pcici_t tag) + { + int secondarybus; + + /* just guessing the secondary bus register number ... */ + secondarybus = (pci_conf_read(tag, 0x44) >> 8) & 0xff; + if (secondarybus != 0) + pciroots++; + } + + static void chipset_attach (pcici_t config_id, int unit) { *************** *** 709,712 **** --- 724,730 ---- case 0x12258086: /* unidentified Intel host bridge, dev ID == 0x1225 */ config_i1225 (config_id); + break; + case 0x00051166: /* Ross ??? */ + config_Ross (config_id); break; } To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message From owner-freebsd-hardware Sat Jun 6 10:18:12 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id KAA24604 for freebsd-hardware-outgoing; Sat, 6 Jun 1998 10:18:12 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from antipodes.cdrom.com (castles171.castles.com [208.214.165.171]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id KAA24593 for ; Sat, 6 Jun 1998 10:18:05 -0700 (PDT) (envelope-from mike@antipodes.cdrom.com) Received: from antipodes.cdrom.com (localhost [127.0.0.1]) by antipodes.cdrom.com (8.8.8/8.8.5) with ESMTP id JAA00706; Sat, 6 Jun 1998 09:13:38 -0700 (PDT) Message-Id: <199806061613.JAA00706@antipodes.cdrom.com> X-Mailer: exmh version 2.0zeta 7/24/97 To: "KeyWORLD" cc: hardware@FreeBSD.ORG Subject: Re: Problems with SCSI disks In-reply-to: Your message of "Tue, 02 Jun 1998 15:43:51 +0200." <199806021337.PAA00533@mail.keyworld.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 06 Jun 1998 09:13:38 -0700 From: Mike Smith Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > Hi all, > > After installing FreeBSD 2.2.2 and 2.2.5, and trying to reboot from a > Fujitsu 4.3G SCSI hard disk, I always get the message saying No Bootable > Partition. > I have also 4 IDE devices installed. What are you using to try to boot from the 5th disk in your system? Many BIOSsen will only allow you to boot from the first or second disk. -- \\ 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 Sat Jun 6 12:17:08 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id MAA09143 for freebsd-hardware-outgoing; Sat, 6 Jun 1998 12:17:08 -0700 (PDT) (envelope-from owner-freebsd-hardware@FreeBSD.ORG) Received: from luomat.peak.org (cc344191-a.ewndsr1.nj.home.com [24.2.83.40]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id MAA09138 for ; Sat, 6 Jun 1998 12:17:01 -0700 (PDT) (envelope-from luomat@luomat.peak.org) Received: (from luomat@localhost) by luomat.peak.org (8.8.8/8.8.8) id PAA25490 for freebsd-hardware@FreeBSD.ORG; Sat, 6 Jun 1998 15:17:01 -0400 (EDT) Message-Id: <199806061917.PAA25490@luomat.peak.org> Content-Type: text/plain MIME-Version: 1.0 From: Timothy J Luoma Date: Sat, 6 Jun 98 15:16:59 -0400 To: freebsd-hardware@FreeBSD.ORG Subject: Support for Intel EtherExpres Pro/10+ Lan Adaptor ? Sender: owner-freebsd-hardware@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org I have two Intel EtherExpres Pro/10+ Lan Adaptor ethernet cards that I was hoping to use in a 486-as-firewall. I did checkout the FAQ but didn't see a section on what Ethernet cards were supported. AFAIK this is a relatively common card, so I was hopeful that there would be support for it. TjL To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hardware" in the body of the message