WARNING: References to the introduction to "Zero Wing" will be made. You know what you doing.
In relation to one of my other threads (
http://www.linuxquestions.org/questi...hreadid=351214), I discovered my second NIC didn't show in $(ifconfig -a). And I'm all like "what happen ?" and "you are on the way to destruction."
So, what do I do, knowing that I know very little of hardware, Linux (the kernel) and drivers? The obvious move is to post in Linux - Hardware.
As I've done that before, I know the sticky suggests listing $(lspci) and $(uname -r). Somewhere, between re-reading the sticky and actually posting, my brain must have thawed.
I actually *read* the output of lspci. By doing so, I determine the brand and model of my second NIC (all I had to go on before that was the "level one" etched into the NIC `front panel' (where the LEDs are, too)).
So, I google on 'Realtek 8139 Linux 2.6.8' and similar, finding that a few people have had some issues, and that a few other people have worked them out using 8139too.
So, of course, I lsmod | grep 8139. Nothing. Hmm...
Okay, so I man modprobe (I didn't really know what it was doing) and modprobe -l *8139*. That one finds 8139(cp|too).ko. Allright, so I echo 8139too >> etc/modules, shutdown -r now, and tada...
$(ifconfig -a): eth0 eth1 lo sit0. It's there. I put in my cable, get a dhcp lease, and voila, "we get signal" (yoohoo).
In the process, I managed to learn a bit about the kernel: if the module isn't loaded, the answer is probably `no'. And I learned how to search for loaded modules (lsmod) and available modules (modprobe -l), load modules (modprobe 8139too), and make sure they're always loaded (/etc/modules).
Until next time, may all yuor base belong to us.
--Jonas