On Tue, 26 Nov 2002 02:11:09 GMT, Joe Dumais staggered into the Black
Sun and said:
Quote:> I added a Linux partition to a system that had originally been Windows
> 2000 only. On boot-up, Linux cannot properly recognize the subject
> Ethernet card. I looked at the Windows configuration for the card,
> and it said the following: Intel Pro/100 VE; IRQ 20, Address
> 78C0-78FF; Memory FCFFF000-FCFFFFFF.
> I added the following line to the lilo.conf file in an attempt to have
> Linux recognize the card:
> append="ether=20,78C0,FCFFF000,FCFFFFFF,eth0"
> Unfortunately, this did not work either.
No, it wouldn't. EEPro100 cards are PCI, therefore they have their
resources autodetected when the eepro100 module is loaded. ether= is
only used if you compiled the EEPro100 support directly into the kernel
(which you shouldn't do except for highly specialized situations like a
diskless workstation that boots over the local net.) IRQ 20 wouldn't
work on an x86 anyway unless the local APIC is being used. Is it?
What does "lspci -vv" report for the card in question? What does "uname
-a" report? The EEPro100 is well supported and has been for ages, but
there have been many revisions of the card, and older kernels may not
grok newer card revisions. The solution to your problem may be as
simple as upgrading the kernel. You might want to post the output from
"dmesg | tail -15" immediately after you do "modprobe eepro100" though,
since something else may be wrong.
--
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /
http://www.brainbench.com / "He is a rhythmic movement of the
-----------------------------/ penguins, is Tux." --MegaHAL