Denis <denis.che <at> gmail.com> writes:
> I was just updating from kernel linux-2.6.24-gentoo-r7 to > linux-2.6.27-gentoo-r7 using the "oldconfig" method, and I cannot get > the new kernel to load my network. I have Intel network hardware that > runs on the E1000 driver, which I generally compile right into the > kernel - never had any problem. For some reason, the > linux-2.6.27-gentoo-r7 kernel leaves me netless. We seem to be getting this a lot lately. I upgraded a sony laptop (intel cpu, eth etc) and had no problems with 2.6.27-gentoo-r7, right out of the box. However, I do not use 'make oldconfing'. What I do is use 'make menuconfig' and most of the meaningful options are carried forward (automatically) into the new kernel configurations. I also save both the old and new configs for comparison and trouble shooting. for Example on an amd 64 after the kernel is built: cd /usr/src && make menuconfig (make choices in gui-menu) make && make modules_install cp System.map /boot/System.map-2.6.27-gentoo-r7 cp arch/x86_64/boot/bzImage /boot/kernel-2.6.27-gentoo-r7 cp .config /boot/config-2.6.27-gentoo-r7 <edit grub.conf> The ".config" file saving is really worth keeping around for a few revs in case you experience problems. I know lost of folks use 'oldconfig' but I think it is problematic. (Surely, I'll get a few flames here). Particularly when your options do need to change as the kernel is routinely reorganized (sometimes) when new version numbers change I.E. (2.6.26 --> 2.6.27) for example. Using the ".config" files top parse line by line (when needed) is a very excellent methodology, methinks, to troubleshoot. YMMV, James
