Date: Fri, 26 Jan 2001 12:22:46 -0500 From: Dennis <dennis@etinc.com> To: Jim Sander <jim@federation.addy.com> Cc: hackers@FreeBSD.ORG Subject: Re: if_fxp driver info (which card then?) Message-ID: <5.0.0.25.0.20010126122046.022922f0@mail.etinc.com> In-Reply-To: <Pine.BSF.4.10.10101260930280.15369-100000@federation.addy. com> References: <Pine.BSF.4.21.0101260844390.34314-100000@net-ninja.com>
next in thread | previous in thread | raw e-mail | index | archive | help
At 09:47 AM 01/26/2001, Jim Sander wrote: > > > Linux people avoid the EtherExpress because they think something is > > > wrong with the card. > > > Intel EtherExpress Pro 10/100B cards in FreeBSD > > These cards work well in our many 3.x and 4.x systems. > > But I just built up a Redhat 6.2 box with one, and all seemed to be >working fine, but after a while I started having various problems starting >net services. The box would boot, but often would "hang" indefinitely when >"Starting eth0" - requiring a hard reboot. I swapped to another EE-Pro >NIC, new MB, different RAM, other cables, everything, but no change. the eepro100 driver is badly broken in linux (havent you been paying attention?). it took me a few hours to fix it. They dont reset the card properly on an overrun, which causes it to lock up. Clearly the driver as is is unusable in a heavy use environment. DB > After I switched to a linksys NIC, voila- everything worked without a >problem. (so far) Of course the Intel NICs still work perfectly when put >into a spare BSD system. So it's *not* that the cards themselves are >unreliable. Perhaps the drivers controlling them? Perhaps a weird MB/NIC >conflict of some sort? > >-=Jim=- > > > >To Unsubscribe: send mail to majordomo@FreeBSD.org >with "unsubscribe freebsd-hackers" in the body of the message To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?5.0.0.25.0.20010126122046.022922f0>