Recently, Somebody Somewhere wrote these words
> Hello out there!
>
> Here are the newest results ;)
>
> I added an old D-Link DFE-530 TX 10/100 card to the system which I
> know is working with the Via Rhine driver - and magically eth0
> appeared for it. So in general networking seems to be okay on the
> system.
>
> I tried the e1000 driver in the kernel (which is one major version
> number smaller than the one Intel provides) but it did not help. So I
> got back to the module (because it seems to be much newer). The
> documentation says it is aware of multi port cards and googling I
> found someone having 4 (!) of the this cards working in his firewall
> (makes 8 port total).
>
> Does anyone see a possiblity to compile the driver supplied by Intel
> into the kernel? In my opinion this is a hotplug/udev issue, so this
> might help and the supplied driver is just too old for the nic. What
> about copying the source code of the driver over the e1000 source code
> in the kernel? The files have the same name but in my e1000 driver
> there are threee addional file name kcompat.c, kcompat.h and
> kcompat_ethtool.c. With a look at both Makefiles I guess I have to add
> kcompat.o to the kernel ones.
>
> Thanks so far for any help!
OK, we can figure a few things.
You original (long ago snipped) problem was
Bringing up the eth0 interface...
Interface eth0 doesn't exist. [WARN]
And then you got eth1. So What's going on is
1. The kernel finds a nic, and barfs trying to configure it with
the built in module, at a guess
2. The second half of the nic gets assigned eth1
3. The pci.ids in the kernel is probably out of date.
Presuming you have CONFIG_PCI_NAMES set, the pci.ids file your kernel
uses resides in ~/drivers/pci/pci.ids and I doubt if THAT is up to date.
Go modular, young man, and use two modules. It is very probable that one
will need the other. One has to be a module - you have no choice. Then
experiment with modprobe-ing them and see what they find, if anything.
If this doesn't work, (i.e. one barfs, and the other does little) add a
line in /lib/modules/<kernel-version>/modules.dep to modules.dep (a real
hack) or to /etc/modprobe.conf (Is there still a preinstall command?)
--
With best Regards,
Declan Moriarty.
--
http://linuxfromscratch.org/mailman/listinfo/blfs-support
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
