Page 1 of 2 12 LastLast
Results 1 to 10 of 14

Thread: update to kernel gone wrong ?

  1. #1

    Default update to kernel gone wrong ?

    Hi

    Earlier this evening I was presented with some security updates, including an update to the kernel. I clicked to allow them to install. The kernel update stops at a login prompt, but doesn't seem to recognise any of my username / password combinations. Any ideas ? Can I back out of this update or am I screwed ?

  2. #2
    Join Date
    Oct 2008
    Location
    North Wales, UK
    Posts
    1,114

    Default Re: update to kernel gone wrong ?

    Usually the auto-updates only require that you enter the root password.
    Else go to yast2>software>online update and choose the updates you want to install.

  3. #3

    Unhappy Re: update to kernel gone wrong ?

    It might help if I explain a little further. After the downloads for the updates had completed, I was asked to reboot. When the system restarted it went into a command line mode; spent about 10 minutes presumably upgrading stuff and then halted at a command line login prompt. This prompt will not accept my userid / password. If I power off, then on restart it goes through the whole process again. So - I am currently unable to complete this update nor get back to the desktop. All a bit concerning for something that I didn't even request in the first place

  4. #4

    Default Re: update to kernel gone wrong ?

    Is this "command line" mode the usual console shell or is it by any chance saying something about "fsck"? If something on your disks needs fixing, fsck will take some time, and then ask for your input, which fits your symptoms. If your reboot shows a green screen, try pressing F2 once booting starts so you can see the console diagnostics.

  5. #5
    Join Date
    Jun 2008
    Location
    Wellington, NZ
    Posts
    29

    Default Re: update to kernel gone wrong ?

    In my case I don't even get to the command line and therefore can't get into the system to investigate. After applying the kernel update, all I get on reboot is a long series of messages complaining about iptables, and another about not being able to load modules (fatal), and the system hangs.

    I've tried twice, and had to restore from backup each time. This is openSuSE 11.1 64-bit, KDE 4.2.9X, running on a Core 2 Quad desktop. The kernels concerned are 2.6.27.23-0.1 (installed) and 2.6.27.25-0.1 (available).

  6. #6
    Join Date
    Jun 2008
    Location
    Mallow, Ireland
    Posts
    1,031
    Blog Entries
    1

    Default Re: update to kernel gone wrong ?

    Any chance you can post a list of the modules involved? A kernel upgrade always screws up certain modules that were added manually after you installed your previous kernel. In my case, for example, I have to reinstall my wifi drivers, webcam and soundcard. In your case it might be something else and giving a list of things it fails on might help.

    Did you try the fail safe startup? It should allow you to at least get to your command prompt since it doesn't load much. It should be in the grub menu.
    "To err is human... to really foul up requires the root password."

  7. #7
    Join Date
    Jun 2008
    Location
    Wellington, NZ
    Posts
    29

    Default Re: update to kernel gone wrong ?

    What I got was soemthing like modprobe: FATAL: could not load /lib/modules/2.2.27-0.1-default/modules.dep: No such file or directory.

    and this:

    iptables v 1.4.0: can't initialize iptables table 'filter' [& more, plus the suggestion "Perhaps iptables or your kernel needs to be upgraded".

    And then a hang without ever getting to a command prompt.

    Thanks for the suggestion about failsafe. But before I chance my arm and try again, I observe the following and wonder what it means, if anything.

    The installed kernel is 2.6.27.23-0.1. The available kernel is 2.6.27.25-0.1. What I don't understand that opening the file list for the new kernel in
    YaST2 shows (typically) /lib/modules/2.6.27.23-0.1-default/[etc etc]. That seems odd - I'd have expected the subdirectory to be referenced to 2.6.27.25, but then I don't know enough about it to be sure.

  8. #8
    Join Date
    Jun 2008
    Location
    Mallow, Ireland
    Posts
    1,031
    Blog Entries
    1

    Default Re: update to kernel gone wrong ?

    Quote Originally Posted by RobinJK View Post
    Thanks for the suggestion about failsafe. But before I chance my arm and try again, I observe the following and wonder what it means, if anything.
    The failsafe might get you in to a command prompt or even a desktop. If you that you can use yast or zipper to reinstall the old kernel. That's what I meant with the failafe.

    Has this machine ever done a kernel update successfully? Mine went smoothly except for the before mentioned hardware. My grubline has the kernel image as:
    Code:
    image=/boot/vmlinuz-2.6.27.25-0.1-default, initrd=/boot/initrd-2.6.27.25-0.1-default
    The failing modules looks to me like the update went wrong, it deleted the old kernel but didn't put back the new one properly. Another option for you is running the repair option from a opensuse 11.1 DVD. This might also help you.
    "To err is human... to really foul up requires the root password."

  9. #9
    Join Date
    Oct 2008
    Location
    North Wales, UK
    Posts
    1,114

    Default Re: update to kernel gone wrong ?

    Quote Originally Posted by RobinJK View Post
    What I got was soemthing like modprobe: FATAL: could not load /lib/modules/2.2.27-0.1-default/modules.dep: No such file or directory.

    and this:

    iptables v 1.4.0: can't initialize iptables table 'filter' [& more, plus the suggestion "Perhaps iptables or your kernel needs to be upgraded".

    And then a hang without ever getting to a command prompt.
    It looks like you are linking to the old kernel modules.
    You modprobe to link to the new kernel modules.
    If you can boot with a live system, you can either create a link to the new modules (2.6.27.23-0.1) or copy the new modules to the old directory (2.2.27-0.1).


    Quote Originally Posted by RobinJK View Post
    Thanks for the suggestion about failsafe. But before I chance my arm and try again, I observe the following and wonder what it means, if anything.

    The installed kernel is 2.6.27.23-0.1. The available kernel is 2.6.27.25-0.1. What I don't understand that opening the file list for the new kernel in
    YaST2 shows (typically) /lib/modules/2.6.27.23-0.1-default/[etc etc]. That seems odd - I'd have expected the subdirectory to be referenced to 2.6.27.25, but then I don't know enough about it to be sure.
    I think the update is probably doing an incremental update. It will perform the next delta when it is next run.

  10. #10
    Join Date
    Jun 2008
    Location
    Wellington, NZ
    Posts
    29

    Default Re: update to kernel gone wrong ?

    OK - found it!

    The updated kernel & sources had been installing OK all along, except that when grub's menu.lst was overwritten it pointed (wrongly) to an 11.0 root partition on another disc. So when it tried to boot, of course it couldn't find the right modules (and much else, I should imagine).

    Dead simple, really. Turns out the only incremental thing was my understanding. Live and learn.

    Thanks for the commments everyone.

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •