I compiled a second kernel to my redhat 7.3 macnhine. I have an on board ethernet controller which uses eepro100 in my old kernel and works fine.

But, if I boot my second kernel it says eth0 does not seem to be present. Delaying initilization.


I tried to recompile kernel w/ different options a couple of times but did not help.

any suggestions?

thanks

yildiz

Welcome to LQ. Perhaps the issue is just that the eepro100 module is not compiled into the new kernel, and needs to be manually loaded. What are the results of running lsmod in the new kernel? Does eepro100 appear in the list?

Also, if you could provide more details about your PC, the model numbers of the components you're using, and the exact error messages you're seeing, it would be helpful. Good luck with it -- J.W.

here is some output:

uname -r : 2.4.18

/sbin/lspci

00:00.0 Host bridge: Intel Corp.: Unknown device 2560 (rev 01)
00:02.0 VGA compatible controller: Intel Corp.: Unknown device 2562 (rev 01)
00:1d.0 USB Controller: Intel Corp.: Unknown device 24c2 (rev 01)
00:1d.1 USB Controller: Intel Corp.: Unknown device 24c4 (rev 01)
00:1d.2 USB Controller: Intel Corp.: Unknown device 24c7 (rev 01)
00:1d.7 USB Controller: Intel Corp.: Unknown device 24cd (rev 01)
00:1e.0 PCI bridge: Intel Corp. 82801BA/CA PCI Bridge (rev 81)
00:1f.0 ISA bridge: Intel Corp.: Unknown device 24c0 (rev 01)
00:1f.1 IDE interface: Intel Corp.: Unknown device 24cb (rev 01)
00:1f.3 SMBus: Intel Corp.: Unknown device 24c3 (rev 01)
00:1f.5 Multimedia audio controller: Intel Corp.: Unknown device 24c5 (rev 01)
01:08.0 Ethernet controller: Intel Corp.: Unknown device 1039 (rev 81)

--------------

modprobe eepro100


Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.
You may find more information in syslog or the output from dmesg

---------------


As I said before, the old kernel uses eepro100 for the ethernet card.

OK - what about the results of lsmod? -- J.W.

lsmod only shows nothing.... no module is loaded

yildiz

make sure when you do recompile, you load that driver in as a module, not directly into the kernel, then on reboot, it should come right up.