[eepro100] Re: problem getting eepro100 driver to work

[Mike Schwartz]

--=====================_797353==_.ALT
Content-Type: text/plain; charset="us-ascii"; format=flowed

Hi,

thanks to those who responded to my inquiry below.  The problem was that 
the motherboard in this system uses Intel's latest network chip (82562), 
and the eepro100 driver doesn't recognize the response from this chip 
during initialization.  It's possible to modify the driver to get it to 
recognize the chip, but the simplest soln was for me to use the e100 driver 
(written by Intel, and also bundled with RedHat 7.0) instead of the 
eepro100 driver.

so, now I have a working network. Thanks again,
  - Mike

At 08:43 PM 11/19/2000, Mike Schwartz wrote:
>Hi,
>
>I am trying to get an Intel EtherExpress Pro 100 NIC (built into an Intel 
>Desktop Board D815EEA) working under Linux 7.0.  When trying to insmod the 
>driver it complains:
>/lib/modules/2.2.16-22/net/eepro100.o: init_module: Device or resource busy
>Hint: insmod errors can be caused by incorrect module parameters, 
>including invalid IO or IRQ parameters
>/lib/modules/2.2.16-22/net/eepro100.o: insmod 
>/lib/modules/2.2.16-22/net/eepro100.o failed
>/lib/modules/2.2.16-22/net/eepro100.o: insmod eth0 failed
>
>I checked the BIOS settings, and PnP OS is disabled (as noted in one of 
>the scyld.com pages about this driver), and the LAN device is 
>enabled.  All the IRQ priorirites were set to "auto".
>
>I ran eepro100-diag, and it output:
>eepro100-diag.c:v2.02 7/19/2000 Donald Becker (becker@scyld.com)
>http://www.scyld.com/diag/index.html
>Index #1: Found a Intel i82562 EEPro100 adapter at 0xdf00.
>Can anyone suggest what I need to do to solve this problem?
>
>Thanks
>  - Mike Schwartz

--=====================_797353==_.ALT
Content-Type: text/html; charset="us-ascii"

Hi,

thanks to those who responded to my inquiry below.  The problem was
that the motherboard in this system uses Intel's latest network chip
(82562), and the eepro100 driver doesn't recognize the response from this
chip during initialization.  It's possible to modify the driver to
get it to recognize the chip, but the simplest soln was for me to use the
e100 driver (written by Intel, and also bundled with RedHat 7.0) instead
of the eepro100 driver.

so, now I have a working network. Thanks again,
 - Mike

At 08:43 PM 11/19/2000, Mike Schwartz wrote:
> Hi,
>
> I am trying to get an Intel EtherExpress Pro 100 NIC (built into an Intel
> Desktop Board D815EEA) working under Linux 7.0.  When trying to
> insmod the driver it complains: 
> /lib/modules/2.2.16-22/net/eepro100.o: init_module: Device or
> resource busy 
> Hint: insmod errors can be caused by incorrect module parameters,
> including invalid IO or IRQ parameters 
> /lib/modules/2.2.16-22/net/eepro100.o: insmod
> /lib/modules/2.2.16-22/net/eepro100.o failed 
> /lib/modules/2.2.16-22/net/eepro100.o: insmod eth0 failed 
>
> I checked the BIOS settings, and PnP OS is disabled (as noted in one of
> the scyld.com pages about this driver), and the LAN device is
> enabled.  All the IRQ priorirites were set to 
> "auto".
>
> I ran eepro100-diag, and it output: 
> eepro100-diag.c:v2.02 7/19/2000 Donald Becker (becker@scyld.com) 
> http://www.scyld.com/diag/index.html 
> Index #1: Found a Intel i82562 EEPro100 adapter at 0xdf00.
> Can anyone suggest what I need to do to solve this problem?
>
> Thanks
>  - Mike Schwartz


--=====================_797353==_.ALT--