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.
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.
Ha
#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 -
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
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.
5 matches
Mail list logo