--- Maurice E Johnson <[EMAIL PROTECTED]> wrote:
> modules-update only updates for the running version. > In order to update > the new version, you could simply reboot to the new > version. Ok, here's where it gets weird, at least to me: The symlink points to the new sources. When I cd /usr/src/linux that's where I end up. I run make menuconfig, then make && make modules_install. Then I copy bzImage to /boot/vmlinuz as always; take a quick look around; check that the new /lib/modules dir(there are now two, natch) is full of modular goodness, and reboot. At the grub prompt I run >root, >kernel /vmlinuz #the *new* kernel and >boot as I always do. CERTAIN modules load. CERTAIN modules don't, predominantly having to do with communications hardware. The thing makes it to the prompt. I log in. Run uname. Yikes! It *is* _running_ the old kernel. BUT, it's _booting_ from the new! I checked! Puh-leeeeeeeze! Chew me out! Deny my competency! Flame me like you've never flamed the rankest wannabe!But tell me how to fix this thing! -Your humble servant etc etc -Maxim __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com -- gentoo-user@gentoo.org mailing list
