Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
I have been struggling long time with new RH 220.127.116.11 kernel. After much angst with nvidia, got it to compile. Then I noticed that i was missing eth2(onboard NIC). I have researched and done lspci -v thinking that it would show me what I did wrong. I tried comparing the old .config with the new .config. I am lost. I used xconfig and the only thing I changed was Security Options to allow updated policy file. What happened to my ethernet?
ifconfig -a (old kernel)
eth0 Link encap:Ethernet HWaddr 00:10:64:30:F7:11
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Base address:0xbf00 Memory:fdbe0000-fdc00000
Yes, I did a make install_modules. This is what I did after bzip2 of linux-2.6.27-10. I made a backup copy of the .config from my 2.6.9-67 kernel.
make oldconfig and just took the defaults. Must have flown past Security options so had to boot to CD to set selinux=disabled in /etc/selinux/selinux.conf
ln -s /usr/src/linux-2.6-27-10 /usr/src/linux
init 6 and wait for Xserver to flounder looking for nvidia
init 3 (CTrl-Alt-F2)
cd /root and run sh NVIDIA-blah-blah
init 5 and up it comes
uname -a show me new kernel so I change the /boot/grub/grub.conf file to default=0 to get the new kernel at bootup.
ifconfig -a shows only eth0, eth 1 and lo0. I've been told that the onboard NIC is supposed to be eth0 but it doesn't look that way to me. We normally activate eth1 and eth2 and leave eth0 deactivated.
I have also tried xconfig. I tried kernel 18.104.22.168 the first week or so and moved onto 22.214.171.124. I'm in week 3 and ready to jump out a window if I can't get this done. This is my first kernel change out so my inexperience is not helping. The only reason I am changing is CVE-2008-5134.
OK, so I did an lsmod and to my surprise e1000 was listed as used by 0 in both the old kernel and the new. Man pages are slim on lsmod so I'm not sure what that is telling me. My guess is that e1000 does not have a module in the kernel. Hmm, does all hardware have modules in the kernel. I would think that would make it hard to change out hardware when things go bad/wrong, you have to re-compile your kernel. Is that right?
- Put the [driver.gz file in /usr/local and then gunzip'd the driver (had trouble with tar zvf)
- # cd /usr/local/e1000e-0.5.8.2/src
# make install #(verified the new modules were in /lib/modules/2.6.27-10/kernel/drivers/net/e1000e; it is e1000e.ko)
# vi /etc/modprobe.conf and changed the alias lines for eth0/eth1/eth2 to e1000e (write and quit)
# init 6
# ifconfig -a (and look for eth0/1/2 to ensure that new driver took)
- go back and clean up /usr/local