Re: [SLE] Many modules not found during boot after update...
From: Johnny Ernst Nielsen (johnny.ernst.nielsen_at_get2net.dk)
Date: 01/13/04
- Previous message: Johnny Ernst Nielsen: "Re: [SLE] Many modules not found during boot after update..."
- In reply to: Richard Atcheson: "Re: [SLE] Many modules not found during boot after update..."
- Next in thread: Johnny Ernst Nielsen: "Re: [SLE] Many modules not found during boot after update..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
To: suse-linux-e@suse.com Date: Tue, 13 Jan 2004 11:08:38 +0100
Tirsdag 13 januar 2004 06:35 kvad Richard Atcheson:
> On Monday 12 January 2004 08:56 pm, Carlos E. R. wrote:
> > > The update was supposed to update the kernel to build 166.
> > >
> > > uname -a reports 2.4.21-144-default
> > > mk_initrd however thinks the kernel is 2.4.21-166-default
> >
> > Do you use lilo, perchance? If so, you need to run it. According
> > to the above, install is not complete.
> >
> > Did you edit the lilo/grub configuration? You could be not
> > booting from vmlinuz.
> >
> > > This time I notised that during the update YaST said it was
> > > installing the Athlon kernel, although the system uses the
> > > default kernel, but I did not dare to cancel the update half
> > > way through.
> >
> > A wrong comment on the patch file. If you look at the right panel
> > in YOU, you see that it is installing k_deflt.
> >
> > > Has anyone got an idea what went wrong, and how I can fix this
> > > without reinstalling the computer again?
> >
> > Simply reinstall the kernel rpm, and run you to upgrade it.
>
> Carlos is partially right. I found an old thread that suggested you
> remove the old/new kernel and reinstall it. I solved the same
> problem by finding the new kernel rpm that Yast had saved then
> using kpackage I uninstalled the kerrnel then installed the same
> one back. And it worked. I did the mk_initrd, ldconfig and
> shutdown-reboot. All is well now.
>
> I sure would like to know why the upgrade to -166 didnt upgrade the
> modules.
So would I.
Physically it seems the modules were updated since /lib/modules/
contains the updated module directory (build 166).
All kernel stuff in /boot/ is up to 166 too.
I don't have physical access to the computer right now, but when I get
to it I will try to run mk_initrd and then ldconfig and then reboot.
If that does not work I will try to reinstall the kernel by
uninstalling the current one, reinstalling the original one off the
CDs and then try the update with the patch CD containing the newest
patch (build 166). As Carlos suggested.
Thank you very much for your help. :o)
Best regards
Johnny :o)
-- Check the headers for your unsubscription address For additional commands send e-mail to suse-linux-e-help@suse.com Also check the archives at http://lists.suse.com Please read the FAQs: suse-linux-e-faq@suse.com
- Previous message: Johnny Ernst Nielsen: "Re: [SLE] Many modules not found during boot after update..."
- In reply to: Richard Atcheson: "Re: [SLE] Many modules not found during boot after update..."
- Next in thread: Johnny Ernst Nielsen: "Re: [SLE] Many modules not found during boot after update..."
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
|
