Forum: Geek Forum Topic: eth0 won't load... started by: Spydir Posted by Spydir on Jun. 19 2001,18:29
ok, I got X working (read: install slack-7.1, pkgtool all packages EXCEPT X related from slack-current cd), but I've built 3 different kernels with my NIC's driver as a module, and it won't work. I can modprobe the module, but during bootup depmod just won't load it.any idea on how to modprobe the driver (command would be "modprobe tulip") and link it to my card? ------------------ Posted by incubus on Jun. 19 2001,19:36
Oi fink it's insmod tulip.otheres loads of stuff at < www.scyld.com > HTH ------------------ Posted by RenegadeSnark on Jun. 20 2001,02:31
use your fav text editor (pico or vi) on /etc/conf.modules or modules.conf (name varies with distro)put alias eth0 tulip.o it might be just tulip i cant remember save file, reboot. it should load! Posted by damien_s_lucifer on Jun. 20 2001,03:13
Spydir, you didn't tell us what kind of NIC you have. Shame! Shame! Anyway, the best thing to do is just build the driver into the kernel instead of a module. Then you don't have to worry about using modprobe; the card will be detected and installed during kernel initialization. Modules are useful for some devices that aren't always needed or connected, but when was the last time you didn't need your NIC? If you MUST make it as a module, make sure you're building your kernel properly. Follow these steps (I'm assuming you unpacked the kernel source in /usr/src/linux): code: This message has been edited by damien_s_lucifer on June 20, 2001 at 10:15 PM Posted by Spydir on Jun. 20 2001,13:35
building the driver in doesn't help because when I used to do that, the moment I connected eth0 to any IP for my LAN ppp0 would die, defeating the purpose of eth0 even being there. and I pretty much said what kind of NIC it is, one that requires the tulip driver, when I said "requires command "modprobe tulip"" or whatever it was (to... lazy to... scrollllll.....)anyways... yeah, I fixed it. Thanks I'm an idiot. I'd load the module right, I just forgot to do the ifconfig for it :/ ------------------ Posted by CatKnight on Jun. 20 2001,14:40
quote: *laugh* be a weenie and use emacs or nedit (my fav) Posted by Spydir on Jun. 20 2001,20:40
vim for me, thank you...oh yeah, emacs sucks. Sorry, it's just the truth. ------------------ Posted by RenegadeSnark on Jun. 21 2001,05:42
I used to use emacs but it totally BLOWS now!!!
Posted by Unexplained on Jun. 25 2001,07:23
Editorwar!!I like MC (Midnight Commander). Very nice syntaxhighlighting. Posted by KL1NK on Jun. 25 2001,08:06
I like emacs.
Posted by SLATE on Jun. 25 2001,13:09
eight megs and constantly swappingthats not good Posted by KL1NK on Jun. 25 2001,20:20
*shrug* I like editing more than one file at once / being able to use the console and edit a file at the same time
Posted by Ash on Jun. 25 2001,21:11
Then you should try Screen. It's pretty nice.-Ash Posted by KL1NK on Jun. 26 2001,02:51
no, I don't mean like that, if I wanted what screen can do, I could just stop the processes. with emacs, I like how you can split your editor into more than one window for editing multiple files, or for using one as the console.This message has been edited by KL1NK on June 26, 2001 at 10:45 PM Posted by Spydir on Jun. 26 2001,05:40
vim for most things, gedit if I need a bunch of stuff open at once------------------ Posted by Beldurin on Aug. 08 2001,16:15
#include /usr/local/incompleI recently had a similar problem with a LinkSys card. They had instructions on how to recompile, but they were incomplete. Not only did I have to recompile and modprobe the tulip.o driver, but I had to do the same with a pci_scan.o driver (instructions < here >. Hope that helps! ------------------ |