Re: Current EEPRO100 Driver in boot-floppies
Eduard Bloch a écrit: #include * Adam Di Carlo [Thu, Jan 09 2003, 09:59:14AM]: 2. http://support.intel.com/support/network/adapter/index.htm As for the issue of the shipped EEPro, are you using the bf2.4 to boot with or no? This seems like an issue with the stable kernel-source-* package. There is hope - new boot-floppies in r2 (I hope) have the new driver developed by Intel. Gruss/Regards, Eduard. I don't know what kernel will be shipped for r2 but the intel driver enter 2.4.20 : From ChangeLog-2.4.20 : ... Jeff Garzik <[EMAIL PROTECTED]>: o Add register dumping and NIC-specific stats to 8139too net driver o Fix 8139too net driver register dump o Temporarily disable MTU-change-while-active support in 8139cp net driver, until it is confirmed fixed on all boards. Users can s till change MTU when the interface is down, like always. o Add Intel e100 net driver o Add e1000 gige net driver o Move e100 net driver after eepro100, in kernel image link order ... Fab -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Current EEPRO100 Driver in boot-floppies
Adam DiCarlo <[EMAIL PROTECTED]> [2003-01-09 09:59:14 -0600]: > As for the issue of the shipped EEPro, are you using the bf2.4 to boot > with or no? This seems like an issue with the stable kernel-source-* > package. It would seem like an issue for upstream more than for a downstream package. Having used the Intel NICs much which use the eepro100 driver I will second that the upstream driver even in 2.4.18 is not perfect. It takes heavy usage to trigger problems. I have never seen casual use be trouble. But under heavy use the driver will sometimes report "out of resources" or some similar message as that is from my memory. Sometimes it will continue. Sometimes it will just stop doing anything and the network is offline. When that is one of your DNS and NIS servers it is a bad thing. (Of course everyone has at least two of all critical servers, right, and so the redundant servers pick up the load at that point.) If the eepro100 driver stops responding you can log in on the console and restart the networking. Everything is fine. I once put that in a cron to happen regularly just to recover from this problem. Obviously that is an unsatisfying resolution. Installing the previously cited Intel source driver instead of the eepro100 solved the problem completely. It would be great if upstream either adopted that driver or merged a fix into the eepro100 driver. Bob msg25159/pgp0.pgp Description: PGP signature
Re: Current EEPRO100 Driver in boot-floppies
#include * Adam Di Carlo [Thu, Jan 09 2003, 09:59:14AM]: > > 2. http://support.intel.com/support/network/adapter/index.htm > > As for the issue of the shipped EEPro, are you using the bf2.4 to boot > with or no? This seems like an issue with the stable kernel-source-* > package. There is hope - new boot-floppies in r2 (I hope) have the new driver developed by Intel. Gruss/Regards, Eduard. -- Am 8. Tag schuf Gott Linux und er sah das es gut war. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: Current EEPRO100 Driver in boot-floppies
CCS Crew <[EMAIL PROTECTED]> writes: > The driver in the boot-floppies images for the eepro100 seems to be > out-of-date and broken. The problem is characterized by the NIC's > failure to respond after minimal usage. Intel (and newer drivers for > the NIC) offers a working driver for Linux that I have successfully > tested under Slackware 7.1. The driver source can be found by > following link #2 below. Link #1 indicates the URL of the > boot-floppies page with the boot images with the broken driver > (phew!). > > 1. http://people.debian.org/~dwhedon/boot-floppies/ This is rather outdated. > 2. http://support.intel.com/support/network/adapter/index.htm As for the issue of the shipped EEPro, are you using the bf2.4 to boot with or no? This seems like an issue with the stable kernel-source-* package. -- ...Adam Di Carlo..<[EMAIL PROTECTED]>...http://www.onshored.com/> -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Current EEPRO100 Driver in boot-floppies
The driver in the boot-floppies images for the eepro100 seems to be out-of-date and broken. The problem is characterized by the NIC's failure to respond after minimal usage. Intel (and newer drivers for the NIC) offers a working driver for Linux that I have successfully tested under Slackware 7.1. The driver source can be found by following link #2 below. Link #1 indicates the URL of the boot-floppies page with the boot images with the broken driver (phew!).1. http://people.debian.org/~dwhedon/boot-floppies/2. http://support.intel.com/support/network/adapter/index.htm DanDo you Yahoo!? Yahoo! Mail Plus - Powerful. Affordable. Sign up now