[opensuse] menu.lst not updated in latest kernel upgrade
3.4.6-2.10 3.4.11-2.16 I just had the most interesting thing happen. I ran a zypper patch, having noticed that there was a kernel update. I am working on my laptop, in which I did an upgrade from openSUSE 12.1 to 12.2 about 3 weeks ago (it was not a clean install, but an upgrade from the dvd). After I had done the upgrade, last week sometime, I decided to try and switch to grub2. It worked fine, but it wasn't as nice looking, so as I was advised on this list, I switched back to grub legacy. I don't know if that is relevant to this latest problem, but I wrote it here so that those of you who are more experienced with this may be able to shed some light on the problem. So back to the zypper patch. On the zypper patch, the kernel was upgraded from 3.4.6-2.10 to 3.4.11-2.16. When I went to reboot, my menu.lst had not been updated (as it has in the past when I was on 12.1), so the system would not boot up. I got a "file not found" error right after grub's menu screen, as it was looking for kernel 3.4.6-2.10. Is this normal? This is the first time I have done a kernel upgrade in 12.2 that I can think of. On my desktop, which was a clean install and hence uses grub2 it was not a problem on the kernel upgrade after I rebooted - everything was done automatically. To fix it, I booted into 12.1, which I still have on another partition, mounted my root, went into the menu.lst file and manually changed the kernel entries to 3.4.11-2.16 on the kernel and initrd. Then it booted up fine. Is there something I am missing here? I would have thought that menu.lst would have been automatically updated when the upgraded kernel was installed with zypper patch. -- G.O. Box #1: 12.2 | KDE 4.9.1 | AMD Phenom IIX4 | 64 | ATI Radeon HD 3300 | 16GB Box #2: 12.2 | KDE 4.9.1 | AMD Athlon X3 | 64 | nVidia C61 GeForce 7025 | 4GB Laptop: 12.2 | KDE 4.9.1 | Core i7-2620M | 64 | Intel HD Graphics 3000 | 8GB learning openSUSE and loving it -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 2012-10-16 18:22 (GMT+0800) George Olson composed: ...
3.4.11-2.16 ... When I went to reboot, my menu.lst had not been updated (as it has in the past when I was on 12.1), so the system would not boot up.
That never happens to me. YaST always makes symlinks vmlinuz and initrd to the latest kernel and initrd, so any time a menu.lst update fails, all that's necessary is to edit the grub lines on the fly to remove the version portion of the kernel and initrd lines before proceeding to boot the new kernel. Another reason why when menu.lst update failure does happen I don't see this is that I keep multiversion set for kernel in zypp.conf on all my systems, so usually there's an older kernel to boot if there's a problem with the newest. Another way to get past a non-updated menu.lst is to drop to the Grub shell and form kernel and initrd lines manually on a cmdline, same as if there were no menu.lst at all. Menu.lst amounts to little more than a script for the Grub shell to use to display a nice menu. ...
Is there something I am missing here? I would have thought that menu.lst would have been automatically updated when the upgraded kernel was installed with zypper patch.
My menu.lst was updated normally when I did a zypper dup getting that kernel yesterday on a 64 bit 12.2 Grub Legacy system, though I probably do mine differently than most people: zypper ref zypper al kernel-desktop zypper dup zypper rl kernel-desktop zypper dup I get annoyed seeing multiple builds of initrds and resulting process completion delay, and this procedure forces a new kernel to get its done only once before the next round of updates builds each one three times or more after updates to mkinitrd, udev and/or other things that affect what necessarily goes into each initrd. That system, like all my systems, also has had /boot/grub2 and any remnants of grub2 an original installation may have left in /etc removed. -- "The wise are known for their understanding, and pleasant words are persuasive." Proverbs 16:21 (New Living Translation) Team OS/2 ** Reg. Linux User #211409 ** a11y rocks! Felix Miata *** http://fm.no-ip.com/ -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 2012-10-16 12:22, George Olson wrote:
Is there something I am missing here? I would have thought that menu.lst would have been automatically updated when the upgraded kernel was installed with zypper patch.
- From an answer in the forums: +++···························· Subject: Re: Change to grub2 Date: Fri, 12 Oct 2012 16:26:02 GMT From: arvidjaar <> Organization: forums.opensuse.org Newsgroups: opensuse.org.help.tumbleweed Zypper calls bootloader utils which refresh *current* bootloader configuration. Where "current" is whatever is defined in /etc/sysconfig/bootloader. You need to switch to grub2 via YaST2. ····························++- Instead, you can add an entry to boot the symlinked kernel. I said add, not replace ;-) - -- Cheers / Saludos, Carlos E. R. (from 12.1 x86_64 "Asparagus" at Telcontar) -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.18 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://www.enigmail.net/ iEYEARECAAYFAlB9ZVkACgkQIvFNjefEBxr/PQCcCS1KN79oSNacbWUS76ve7snm 4fkAoNr5lXD+4MzQ/dGYoSvY/VGjBaPf =ct4g -----END PGP SIGNATURE----- -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On 10/16/2012 09:47 PM, Carlos E. R. wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-10-16 12:22, George Olson wrote:
Is there something I am missing here? I would have thought that menu.lst would have been automatically updated when the upgraded kernel was installed with zypper patch.
- From an answer in the forums:
+++···························· Subject: Re: Change to grub2 Date: Fri, 12 Oct 2012 16:26:02 GMT From: arvidjaar <> Organization: forums.opensuse.org Newsgroups: opensuse.org.help.tumbleweed
Zypper calls bootloader utils which refresh *current* bootloader configuration. Where "current" is whatever is defined in /etc/sysconfig/bootloader. You need to switch to grub2 via YaST2. ····························++-
Instead, you can add an entry to boot the symlinked kernel. I said add, not replace ;-)
- -- Ok, thanks guys for the guidance. I can see why now it did what it did. I think I will add the symlinked kernel, and I changed the /etc/sysconfig/bootloader back to grub from grub2, where it had been changed earlier when I had gone to grub2.
-- G.O. Box #1: 12.2 | KDE 4.9.1 | AMD Phenom IIX4 | 64 | ATI Radeon HD 3300 | 16GB Box #2: 12.2 | KDE 4.9.1 | AMD Athlon X3 | 64 | nVidia C61 GeForce 7025 | 4GB Laptop: 12.2 | KDE 4.9.1 | Core i7-2620M | 64 | Intel HD Graphics 3000 | 8GB learning openSUSE and loving it -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (3)
-
Carlos E. R.
-
Felix Miata
-
George Olson