Compiled new kernel, eth0 fails to show up

[supernov]

Hi all,

I installed kernel 2.6.16-r3 next to my 2.6.15-r1. On the latter, eth0 is showing up and dhcpcd is running smoothly, but when I startup the 2.6.16 kernel
eth0 is gone! I can't see what I've set differently in my new kernel-config. Known problem?

Oh...and when I try to load it as a module (my SIS controller that is), it fails because of module version conflicts... If you guys need more tech. info I'll boot-up the other
kernel again. Can't do that now however, since eth0 is gone in the other.


Thanks, Vincent

[M1Sports20]

Are you sure you didn't remove the module or compiled in support on the new kernel
Did you start over or did you cp the .config file to the new kernel and run make oldconfig


you could always do a diff on the two .config files

If you want you could also post both config files allow with the output of lspci

[supernov]

OmG!

uname gave me the fact that I was running the previous kernel! I tried so many things to explain all the behaviour I was constantly seeing,
I'm not a noob anymore, but now I really dropped my trousers. For some reason, in previous gentoo installations, I didn't have to
mount boot. It was probably done automatically, but with the new one I apparently changed this (which is a good thing I believe). So here I was
compiling new kernels, copying them to /boot, checking to see if they were copied, updating my linux link... and probably was doing all
that virtually!? Mounting the boot did the trick, after that my modules loaded, eth0 was working again and even the ati-drivers with
fglrx!! Incredible, weeks I spend behind the screen for this.

So, what works for me on this system is gentoo 2.6.16-r6 with ati-drivers 8.23.7, not forgetting to mount /boot when copying new kernels:

- Ati Radeon 9600
- SiS chipset controllers
- Realtek, SiS ethernet controllers

Thanks m8's!