I'm not convinced it was a problem with the 2.4.21 kernel, I think it's more along the lines of something I didn't do before that I did now.
Anyway, it works
Thanks for the help
]]>[/quote]
]]>Btw, I'm starting up Arch with the install iso, using the command "vmlinuz root=/dev/discs/disc0/part5" at the "boot" prompt. I didn't install a bootloader because I want to use the LILO already installed for Mdk. However, I can't get it to work - lilo complains about missing initrd.
Any ideas on that?
]]>Then I recompiled the same kernel (during re-install) but taking out the SMP option and compiling in eepro100 and e100 as modules <M>. This still brought errors on "modprobe", but not relating to SMP (Rsmp)
The errors for "modprobe eepro100" at this stage with my recompiled 2.4.21 kernel:
/lib/modules/2.4.21/kernel/drivers/net/mii.o: unresolved symbol: __netdev_watchdog_up_R9a7e3a94
/lib/modules/2.4.21/kernel/drivers/net/mii.o: insmod /lib/modules/2.4.21/kernel/drivers/net/mii.o failed
/lib/modules/2.4.21/kernel/drivers/net/mii.o: insmod eepro100 failed
I tried installing the e100 module (modprobe e100), but it gave me 11 different errors of more or less the same format as the above
]]>Once you have set up your network with a "known" kernel you can move on and compile your own. If the NIC fails then, you most certainly know that something went wrong during compilation.
Now, I assume you also rebooted your system ?
Also, I'm a bit confused about when you are using modules, when you have the driver compiled in and when you are doing a modprobe ?
Note, that if you compile a driver into the kernel and still do a modprobe (which you should not), then modprobe may still look in /lib/modules/..../ and actually find something from a previous kernel/modules install ! That is calling for trouble !
You say, you disabled SMP, recompiled everything and installed everything ? Yet you get an unresolved symbol wich has "SMP" in its string ? Am I right ? The watchdog-messgae has "SMP" at the end.
Now, something completely different : try the e100 module - it's an EtherExpress driver by Intel itself - it works for one of my machines.
]]>I took out the SMP option and did:
make dep clean
make bzImage
make modules
make modules_install
After trying "modprobe eepro100", I didn't get the Rsmp error, but still got the other error (the "watchdog" error I mentioned previously). Still no progress.
I'm using the standard kernel for IDE from the install iso (2.4.21)
I think I'll try loading the "eepro" module. I installed it as a module just in case
]]>I just vaguely remember similar problems, but I also remember I solved it with setting up properly the kernel and the modules.
]]>Another thing : when re-compiling the kernel and modules, did you also do make modules_install ?
]]>Is there a command I can use to check the PCI bus? (like scanpci or lspci from debian)
]]>The module was included in the kernel (compiled in, not as a module). I set my hostname in rc.conf, as well as IP, netmask and broadcast for eth0. I also set default gateway in rc.conf
In resolv.conf I put in nameserver values for lo and eth0
I had IP addresses, domainname and hostname for eth0 and lo in /etc/hosts
Typing "modprobe eepro100" gives an error:
"/lib/modules/2.4.21/kernel/drivers/net/mii.o: unresolved symbol"
There are 4 lines with variations of the first line, basically saying "mii.o" failed and "eepro100" failed
I tried "ifconfig <ip address>", I got this error:
"SIOCSIFADDR: no such device
eth0: unknown interface: no such device"
Typing "/sbin/route add -net default gw <gateway>" returns this error:
"SIOCADDRT: network is unreachable"
I have since recompiled the kernel and set "eepro100" as a module (not compiled in).
When the dust settled, I typed "modprobe eepro100" and naturally got the same error as before.
Seems like the card is not being recognized or found. I'm wondering if my other hardware might also not be found. eepro100 is the first thing I tried to set up.
I'd appreciate any help here, obviously without net access I'm stuck with a base install.
]]>