Vivek Kumar wrote:
If you have a Pentium-class or greater machine, you might want the 586 or 686 variant rather than the 386 variant. The 386 should work fine, but the others are more "optimized" for their respective chips.Hi, I had 2.20 version installed on my system and reiserfs was not working. So I installed kernel-image-2.4.18-386 (apt-get install kernel-image-2.4.18-386). It did configure and then I reboot my box and the reiserfs started working butsomehow my networking is gone. I can't get my eth0 and eth1 up. Once I use isup eth0 command it says about module not found or something and next time I do it it says eth0 is already configured. What should I do to make eth0 and eth1 work. Kindly help. Thanks
To answer your question, you probably need to load the correct module for your nic. Assuming it's a PCI-based nic, run "lspci" to find out which chipset you have (like 3Com 3c509 or Intel i810), then you can run "modprobe [the appropriate driver]" or run "modconf". modconf is menu-driven, and has the advantage of placing the module in /etc/modules so that the module will be available automatically at future reboots. If you use modprobe, you'll want to make that entry yourself. The modules should be available in /lib/modules/[kernel-version]/kernel/drivers/net. So for example, if you have a LNE100TX nic, which requires the "tulip" driver, you'd run "modprobe tulip". If you have a 3com 3c509, I think you'd want to run "modprobe 3c59x". Then restart networking with a command like "/etc/init.d/networking restart" (although I've had better success doing a "stop" followed by a "start" instead of a "restart" - I have no idea why). If that works, add the module name to /etc/modules for future reboots.
-- Kent