Jeremy Kersenbrock wrote:
> Hello,
>
> I've been trying to get an Intel Etherexpress PRO/100 pci nic to work in linux
> for 3 weeks, and I'm almost ready to give up. Linux is renowned for being a
> superior network OS, but I can't prove it.
>
> My distro is Linux-Mandrake 6.0, but I'm running a custom kernel compiled from
> the kernel.org 2.2.14 source.
>
> When I installed Linux, I didn't have a nic, so I'm trying to add this one to
> my running system.
>
> I have compiled support for the eepro100 as a module. When I configured my
> eth0 interface with netcfg, I specified that it not be activated at boot.
> Since it is a PCI card, I have not specified an IRQ or i/o.
>
> When I boot, I get the message that interface eth0 was started OK anyway.
> When I manually activate the eth0 interface with netcfg, I get the message:
> "Delaying eth0 initilization". Then I deactivate it and get the message
> "unknown interface."
>
> When I manually launch the eth0 interface with the appropriate ifconfig command
> I get these errors:
>
> SIOCSIFADDR: No such device
> eth0: Unknown interface: No such device
> SIOSCIFNETMASK: No such device
> eth0: Unknown interface: No such device
>
> How can this be an unknown interface and still be launching at boot? Why is it
> launching at boot when netcfg still shows is as not activated at boot?
>
> I have a dual-boot maching, and the nic works beautifully in Windows98.
>
> What the heck do I have to do to make this thing work?
>
> --
> Jeremy Kersenbrock
> [EMAIL PROTECTED]
I installed An Etherexpress Pro on 6.0 with no difficulty... I believe the module
already exists, and you did not need to compile one. IIRC, I used linuxconf, went
to networking, named the adapter and used a drop-down list at kernel module to
select the module, which was called eepro100, ticked "Enable" and quit allowing
linuxconf to activate the changes. The only reboot was to put in the card.
I use the IIRC there because I don't have any Venus installations running any
longer. I am using Helios and Air on all machines now.
FWIW, I had an interesting bout with some ATX mothers, AGP cards, and EtherPro
cards. Every time I activated the network, I would lose video and I couldn't
telnet or Webmin in to force reboot because the network was wrapped around itself
too. The only way out ot that Klein bottle was to use the dreaded switch...
RESET. The solution was to take the NICs from those machines and use them in some
aging socket-7 mothers and use the "under$10 Blue light special" NICs from them in
my brand new PPGA Socket 370 boards running the latest in Intel Socketed
processors. Both seemed to digest the others NICs and all ran Mandrake happily,
but I will NEVER, EVER use or allow to be specified another EtherPro Card in any
system I manage. I am not happy when AGPs and Ethernet Cards try to select the
same interrupt, and neither is linux.
Based on my experience with EtherexpressPro cards in combination with other recent
hardware (All of it by Intel, in this case), my suggestion, with all due respect,
is to develop a punt, pass, and kick sporting event using those cards instead of a
football.
But, if you are avoiding the "shared interrupt" visitor, I know for certain that
both 6.1 and 7.0 have those modules and the latest 7.0 is capable of upgrading
your current system in place as long as you select upgrade instead of install in
the opening dialogue. (and if you have some patience... An Upgrade that really
does without a lot of unresolved side issues is something new to me, and well
worth the time it takes while you are thinking it has died, running a marathon and
not finishing first, and going out for a few cups of coffee and interesting
conversation.)
Civileme
--
experimentation involving more than 500 trials with an
ordinary slice of bread and a tablespoon of peanut butter
has determined that the probability a random toss will
land sticky side down (SSD) is approximately .98
