Re: [SLE] kernel update version 2.6.16.21-0.13-default
On Friday 15 September 2006 21:56, Ed McCanless wrote:
Thanks for the quick response, Carl. I saw one other update in the window to the right. I expected it to be a necessary part of the update, so I left it selected. I have grown used to seeing warnings when I need to do something special. YOU did appear to install everything correctly. I clicked "Finish" when the progress bars reached 100%, and watched the linker progress to completion. That's when I got the message that I would have to re-boot. --ED--
Hopefully, you *deselected* the 'Remove packages after installation' checkbox to preserve the downloaded packages. If not, you'll need to download them manually from an updates repository. I'm presently booted into 10.0 (I'm still massaging 10.1), so the packages downloaded by YOU are stored under '/var/lib/YaST2/you/mnt/i386/update/10.0/rpm/i586' You should have '.../10.1/...', instead. The last kernel update on my 10.0 system included the following packages: kernel-default-2.6.13-15.8.i586.rpm kernel-default-nongpl-2.6.13-15.8.i586.rpm kernel-source-2.6.13-15.8.i586.rpm If I were going to reinstall these packages, I'd copy them to a temporary working directory, open a shell, 'su' to superuser permissions and run the following commands: rpm -ihv --force kernel-*.rpm --test If no errors were reported, I'd continue (using the 'up' arrow and backspacing out the '--test' parameter): rpm -ihv --force kernel-*.rpm ldconfig SuSEconfig I can't recall if the installation script handles this already, but repeating it doesn't hurt anything: mkinitrd I'd then exit out of superuser, exit the shell, log out of my desktop and select to restart the computer. I've put this 'plan' together from memory. If I've overlooked something, I'm sure we'll read about it shortly. ;-) One more thing: Before attempting this procedure, you might want to first boot the system using your installation media (DVD/CD) and select 'Boot installed system' to ensure the appropriate environment has been established for installing the updates. hth & regards, Carl
Carl Hartung wrote:
rpm -ihv --force kernel-*.rpm ldconfig SuSEconfig
I can't recall if the installation script handles this already, but repeating it doesn't hurt anything:
Actually, in this case I don't believe ldconfig are needed, nor SuSEconfig. Not positive about SuSEconfig though.
mkinitrd
This one is called by the rpm scripts. I haven't figured out yet what the newer packages are doing to grub's menu.lst, but they also do something here. That may have caused his problem as well.
I'd then exit out of superuser, exit the shell, log out of my desktop and select to restart the computer.
I've put this 'plan' together from memory. If I've overlooked something, I'm sure we'll read about it shortly. ;-)
I think it would be wise to check grub and especially menu.lst.
One more thing: Before attempting this procedure, you might want to first boot the system using your installation media (DVD/CD) and select 'Boot installed system' to ensure the appropriate environment has been established for installing the updates.
If that would work then I believe it indicates a grub problem and not a kernel problem. -- Joe Morris Registered Linux user 231871
participants (2)
-
Carl Hartung -
Joe Morris (NTM)