I was wondering if somebody could help me with the installation of my NIC. My NIC works great with the autoCD but once it is removed I cant get a connection. ..it cant find the NIC. I tried loading the module but it said that there are no ebuilds. I had 2 NICS. They are:
Realtek RTL-8139
Davicom DEC-Tulip comp.
AUTOCD loads up 8139too, mii and also crc32, tulip. I tried emerging these but I got the no ebuilds. Please help. Thank you very much.
I tried that but it said 'could not load /lib/modules/2.6.9-gentoo-r1/modules.dep.' I took a look and I am running '2.4.8-gentoo-r7.' How would I change this so my modprobe will work?
if you didn't include the modules in the kernel then you'll have to recompile it witht he correct modules selected. you might as well build them into the kernel so as it's less hassle then having htem as moduels
Man, I thought Ultimate Robot Fighting was real, like pro wrestling, but it turns out it's fixed, like boxing.
Can anybody explain to me why they are talking about using 'emerge' in the handbook to add modules when you have to use modprobe to do it. It doesnt make much sense to me.
So I re-compiled my kernel and I added support for both tulip and 8139too drivers, which are what loads with the autocd.. . I rebooted and it still doesnt load my NICs. I made sure to cp the bzimage and appropriate files to the boot partition /dev/hda1. It still doesnt load. When I try the emerge it gives me no ebuilds to satisfy and when I do a modprobe it gives me 'cant find (module)' What am I doing wrong here?
Ok, although this should be covered somewhere else in the forum, probably several times, here's some basics on the kernel. When you select an option and "M" shows in the little box beside it that means it's building as a module. In order to use this module you must run "make modules ; make modules_install" for the 2.4 series kernel and just "make modules_install" under the 2.6 series to put the module in the right place. If you select the option and it show "*" in the box then that means it's built into the kernel and there's no need for running modprobe. If this is the case, try typing "ifconfig -a" and see if "eth0" shows up. If it does then your nic is loaded and waiting to be brought up. At this point it is a good idea to start reading the section of the handbook on setting up your network. It doesn't get much easier than this so I hope you understand a little better now.
I respect faith, but doubt is what gives you an education.
-- Wilson Mizner