Re: Intel Etherexpress support?
Gerhard Sittig wrote: > > On Tue, Oct 31, 2000 at 00:08 +0100, Peter van Dijk wrote: > > > > Without looking at any of your code, I would kindly like to ask > > you not to look at the Linux driver for eexpress too much - > > it's severely broken and has all kinds of timing problems that > > can crash boxes at predictable moments (some boxes crash when > > you ifconfig, some crash when you run tcpdump [probably on the > > switch to PROMISC]). Slower boxes seem to work better. > > Which driver version are you talking about? I didn't follow this > stuff too closely (my EEPro100 always worked when not sitting in > an Asus SP3 board which has problems of its own regarding PCI) They're discussing the ISA card, which has very little to do with your PCI bus. -- "Where am I, and what am I doing in this handbasket?" Wes Peters Softweyr LLC [EMAIL PROTECTED] http://softweyr.com/ To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Intel Etherexpress support?
On Tue, Oct 31, 2000 at 10:57:11AM +0100, Gerhard Sittig wrote: > On Tue, Oct 31, 2000 at 00:08 +0100, Peter van Dijk wrote: > > > > Without looking at any of your code, I would kindly like to ask > > you not to look at the Linux driver for eexpress too much - > > it's severely broken and has all kinds of timing problems that > > can crash boxes at predictable moments (some boxes crash when > > you ifconfig, some crash when you run tcpdump [probably on the > > switch to PROMISC]). Slower boxes seem to work better. > > Which driver version are you talking about? I didn't follow this > stuff too closely (my EEPro100 always worked when not sitting in > an Asus SP3 board which has problems of its own regarding PCI) [snip] We're talking about the old eexpress cards, not the eepro's. eepro's rock :) Greetz, Peter -- dataloss networks '/ignore-ance is bliss' - me 'Het leven is een stuiterbal, maar de mijne plakt aan t plafond!' - me To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Intel Etherexpress support?
On Tue, Oct 31, 2000 at 00:08 +0100, Peter van Dijk wrote: > > Without looking at any of your code, I would kindly like to ask > you not to look at the Linux driver for eexpress too much - > it's severely broken and has all kinds of timing problems that > can crash boxes at predictable moments (some boxes crash when > you ifconfig, some crash when you run tcpdump [probably on the > switch to PROMISC]). Slower boxes seem to work better. Which driver version are you talking about? I didn't follow this stuff too closely (my EEPro100 always worked when not sitting in an Asus SP3 board which has problems of its own regarding PCI) but there is an enhanced and corrected driver besides the "official" in the Linux kernel. It always got good critics and seems to work reliable from what I hear. Donald Becker's original http://cesdis.gsfc.nasa.gov/linux/drivers/kern-2.3/index.html ftp://cesdis.gsfc.nasa.gov/pub/linux/drivers/kern-2.3 Andrey Savochkin's improvements ftp://ftp.sw.com.sg/pub/Linux/people/saw/kernel/ I don't know whether the ML [EMAIL PROTECTED] (the Linux EEPro list) is archived somewhere and how useful http://support.intel.com/support/network/adapter/pro100/100linux.htm is. But I hope these links to be helpful. virtually yours 82D1 9B9C 01DC 4FB4 D7B4 61BE 3F49 4F77 72DE DA76 Gerhard Sittig true | mail -s "get gpg key" [EMAIL PROTECTED] -- If you don't understand or are scared by any of the above ask your parents or an adult to help you. To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Intel Etherexpress support?
On Tue, 31 Oct 2000, Peter van Dijk wrote: > Without looking at any of your code, I would kindly like to ask you > not to look at the Linux driver for eexpress too much - it's severely > broken and has all kinds of timing problems that can crash boxes at > predictable moments (some boxes crash when you ifconfig, some crash > when you run tcpdump [probably on the switch to PROMISC]). Slower > boxes seem to work better. I've ported the NetBSD driver. I avoid looking at Linux code as much as possible. -- | Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD | | [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax | | http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever | To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Intel Etherexpress support?
On Thu, Oct 26, 2000 at 12:58:28AM -0400, Matthew N. Dodd wrote: > On Tue, 24 Oct 2000, Glendon Gross wrote: > > Is it possible to use the old Intel EtherExpress-16 cards with FreeBSD? > > The driver was broken a while back and I'm right in the middle of trying > to fix it. I've actually given up on the FreeBSD driver and ported the > NetBSD driver with mixed success. I've got 3c503 boards working great but > the EE16s are really nasty and I'm still tracking down a few issues. > > You might try the attached patch against sys/dev/ie/if_ie.c though as I'm > not quite ready to commit what I've got. Without looking at any of your code, I would kindly like to ask you not to look at the Linux driver for eexpress too much - it's severely broken and has all kinds of timing problems that can crash boxes at predictable moments (some boxes crash when you ifconfig, some crash when you run tcpdump [probably on the switch to PROMISC]). Slower boxes seem to work better. Greetz, Peter -- dataloss networks '/ignore-ance is bliss' - me 'Het leven is een stuiterbal, maar de mijne plakt aan t plafond!' - me To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-current" in the body of the message
Re: Intel Etherexpress support?
On Tue, 24 Oct 2000, Glendon Gross wrote:
> Is it possible to use the old Intel EtherExpress-16 cards with FreeBSD?
The driver was broken a while back and I'm right in the middle of trying
to fix it. I've actually given up on the FreeBSD driver and ported the
NetBSD driver with mixed success. I've got 3c503 boards working great but
the EE16s are really nasty and I'm still tracking down a few issues.
You might try the attached patch against sys/dev/ie/if_ie.c though as I'm
not quite ready to commit what I've got.
--
| Matthew N. Dodd | '78 Datsun 280Z | '75 Volvo 164E | FreeBSD/NetBSD |
| [EMAIL PROTECTED] | 2 x '84 Volvo 245DL| ix86,sparc,pmax |
| http://www.jurai.net/~winter | This Space For Rent | ISO8802.5 4ever |
Index: if_ie.c
===
RCS file: /cvs/src/sys/dev/ie/if_ie.c,v
retrieving revision 1.77
diff -u -r1.77 if_ie.c
--- if_ie.c 2000/10/15 14:18:16 1.77
+++ if_ie.c 2000/10/18 17:40:54
@@ -216,8 +216,12 @@
* This tells the autoconf code how to set us up.
*/
struct isa_driver iedriver = {
- ieprobe, ieattach, "ie",
+ INTR_TYPE_NET,
+ ieprobe,
+ ieattach,
+ "ie",
};
+COMPAT_ISA_DRIVER(ie, iedriver);
enum ie_hardware {
IE_STARLAN10,
@@ -2069,6 +2073,7 @@
}
ie->arpcom.ac_if.if_flags |= IFF_RUNNING; /* tell higher levels
* we're here */
+ ie->arpcom.ac_if.if_flags &= ~IFF_OACTIVE;
start_receiver(unit);
return;
@@ -2089,6 +2094,7 @@
switch (command) {
case SIOCSIFADDR:
+ ieinit(ifp->if_softc);
case SIOCGIFADDR:
case SIOCSIFMTU:
error = ether_ioctl(ifp, command, data);
