[opensuse] multiple kernel versions
I have a situation on an openSUSE 13.1 install that I cannot figure out. I have multiple kernels installed. They have been installed as the result of 'zypper up'. I am confused why the latest version installed (3.11.10-25.1) is not the one used. The system runs 3.11.10-21-desktop. I would have expected the newest version to be used when it was installed, and previous versions to remain - but not be used - until I take action to remove them. How do I get the latest version to be the one used? I know how to remove older versions. But not how to make a newer version that is installed get used. # zypper se -s 'kernel*' | grep "i | " i | kernel-default | package | 3.11.10-25.1 | i586 | openSUSE-13.1-Update i | kernel-default | package | 3.11.10-21.1 | i586 | openSUSE-13.1-Update i | kernel-default-devel | package | 3.11.10-25.1 | i586 | openSUSE-13.1-Update i | kernel-default-devel | package | 3.11.10-21.1 | i586 | openSUSE-13.1-Update i | kernel-desktop | package | 3.11.10-25.1 | i686 | openSUSE-13.1-Update i | kernel-desktop | package | 3.11.10-21.1 | i686 | openSUSE-13.1-Update i | kernel-desktop-devel | package | 3.11.10-25.1 | i686 | openSUSE-13.1-Update i | kernel-desktop-devel | package | 3.11.10-21.1 | i686 | openSUSE-13.1-Update i | kernel-devel | package | 3.11.10-25.1 | noarch | openSUSE-13.1-Update i | kernel-devel | package | 3.11.10-21.1 | noarch | openSUSE-13.1-Update i | kernel-firmware | package | 20130714git-2.21.1 | noarch | openSUSE-13.1-Update i | kernel-pae-devel | package | 3.11.10-25.1 | i686 | openSUSE-13.1-Update i | kernel-pae-devel | package | 3.11.10-21.1 | i686 | openSUSE-13.1-Update i | kernel-source | package | 3.11.10-25.1 | noarch | openSUSE-13.1-Update i | kernel-source | package | 3.11.10-21.1 | noarch | openSUSE-13.1-Update i | kernel-syms | package | 3.11.10-25.1 | i586 | openSUSE-13.1-Update i | kernel-syms | package | 3.11.10-21.1 | i586 | openSUSE-13.1-Update i | kernel-xen-devel | package | 3.11.10-25.1 | i686 | openSUSE-13.1-Update i | kernel-xen-devel | package | 3.11.10-21.1 | i686 | openSUSE-13.1-Update -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Wed, 2015-03-11 at 22:26 +0100, Roger Oberholtzer wrote:
I have a situation on an openSUSE 13.1 install that I cannot figure out. I have multiple kernels installed. They have been installed as the result of 'zypper up'. I am confused why the latest version installed (3.11.10-25.1) is not the one used. The system runs 3.11.10-21-desktop. I would have expected the newest version to be used when it was installed, and previous versions to remain - but not be used - until I take action to remove them. How do I get the latest version to be the one used? I know how to remove older versions. But not how to make a newer version that is installed get used.
# zypper se -s 'kernel*' | grep "i | " i | kernel-default | package | 3.11.10-25.1 | i586 | openSUSE-13.1-Update i | kernel-default | package | 3.11.10-21.1 | i586 | openSUSE-13.1-Update i | kernel-default-devel | package | 3.11.10-25.1 | i586 | openSUSE-13.1-Update i | kernel-default-devel | package | 3.11.10-21.1 | i586 | openSUSE-13.1-Update i | kernel-desktop | package | 3.11.10-25.1 | i686 | openSUSE-13.1-Update i | kernel-desktop | package | 3.11.10-21.1 | i686 | openSUSE-13.1-Update i | kernel-desktop-devel | package | 3.11.10-25.1 | i686 | openSUSE-13.1-Update i | kernel-desktop-devel | package | 3.11.10-21.1 | i686 | openSUSE-13.1-Update i | kernel-devel | package | 3.11.10-25.1 | noarch | openSUSE-13.1-Update i | kernel-devel | package | 3.11.10-21.1 | noarch | openSUSE-13.1-Update i | kernel-firmware | package | 20130714git-2.21.1 | noarch | openSUSE-13.1-Update i | kernel-pae-devel | package | 3.11.10-25.1 | i686 | openSUSE-13.1-Update i | kernel-pae-devel | package | 3.11.10-21.1 | i686 | openSUSE-13.1-Update i | kernel-source | package | 3.11.10-25.1 | noarch | openSUSE-13.1-Update i | kernel-source | package | 3.11.10-21.1 | noarch | openSUSE-13.1-Update i | kernel-syms | package | 3.11.10-25.1 | i586 | openSUSE-13.1-Update i | kernel-syms | package | 3.11.10-21.1 | i586 | openSUSE-13.1-Update i | kernel-xen-devel | package | 3.11.10-25.1 | i686 | openSUSE-13.1-Update i | kernel-xen-devel | package | 3.11.10-21.1 | i686 | openSUSE-13.1-Update
-- Roger Oberholtzer Hi, you didn't say whether you are using grub or grub2 as your boot loader.
In the case of grub, if the latest kernel isn't booting by default, then you need to use yast>System>Boot loader. Find the kernel you want to boot as default and use yast to set it as default. If you are using grub2 as your boot loader and update the kernel with zypper, it sets the latest version of kernel to boot as default. On the odd occasion that it didn't do that, I just used yast>System>Boot Loader and reinstalled the boot loader to repair the problem. I don't find a map of kernels and operating systems in yast when grub2 is the boot loader, but no matter. When I rebooted the computer the latest kernel booted by default. Mark -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, Mar 12, 2015 at 9:52 AM, Mark Misulich <munguanaweza@gmail.com> wrote:
If you are using grub2 as your boot loader and update the kernel with zypper, it sets the latest version of kernel to boot as default. On the odd occasion that it didn't do that, I just used yast>System>Boot Loader and reinstalled the boot loader to repair the problem.
Should actually be enough to run "update-bootloader --refresh" or - to avoid reinstallation on older relases (do not remember if fix was already in 13.1) - "grub2-mkconfig -o /boot/grub2/grub.cfg". YaST does not do anything different anyway. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Roger Oberholtzer wrote:
I have a situation on an openSUSE 13.1 install that I cannot figure out. I have multiple kernels installed. They have been installed as the result of 'zypper up'. I am confused why the latest version installed (3.11.10-25.1) is not the one used. The system runs 3.11.10-21-desktop. I would have expected the newest version to be used when it was installed, and previous versions to remain - but not be used - until I take action to remove them. How do I get the latest version to be the one used?
Update your bootloader? -- Per Jessen, Zürich (5.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
It failed for the same reason both when I ran update-bootloader --refresh and when I updated via YaST. It complains like this: Perl-Bootloader: 2015-03-12 20:53:13 <3> pbl-3048.2 Core::RunCommand.1642: Error: Command '/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg >/var/log/YaST2/y2log_bootloader 2>&1' failed with code 32512 and output: /etc/default/grub: line 25: @=auto: command not found Indeed line 25 in /etc/default/grub is "@=auto" Here is the context in that file: # The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' @=auto GRUB_GFXMODE=1920x1080 I am fairly certain I did not put that line there. Should it be something else? I can say that the current boot menu is a terrible low resolution. But at least it built for the kernel. Not it just fails. On Thu, Mar 12, 2015 at 9:16 AM, Per Jessen <per@computer.org> wrote:
Roger Oberholtzer wrote:
I have a situation on an openSUSE 13.1 install that I cannot figure out. I have multiple kernels installed. They have been installed as the result of 'zypper up'. I am confused why the latest version installed (3.11.10-25.1) is not the one used. The system runs 3.11.10-21-desktop. I would have expected the newest version to be used when it was installed, and previous versions to remain - but not be used - until I take action to remove them. How do I get the latest version to be the one used?
Update your bootloader?
-- Per Jessen, Zürich (5.1°C) http://www.dns24.ch/ - free dynamic DNS, made in Switzerland.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
On Thu, 12 Mar 2015 21:05, Roger Oberholtzer <roger.oberholtzer@...> wrote:
It failed for the same reason both when I ran update-bootloader --refresh and when I updated via YaST. It complains like this:
Perl-Bootloader: 2015-03-12 20:53:13 <3> pbl-3048.2 Core::RunCommand.1642: Error: Command '/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg >/var/log/YaST2/y2log_bootloader 2>&1' failed with code 32512 and output: /etc/default/grub: line 25: @=auto: command not found
Indeed line 25 in /etc/default/grub is "@=auto"
Here is the context in that file:
# The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' @=auto GRUB_GFXMODE=1920x1080
I am fairly certain I did not put that line there. Should it be something else?
I can say that the current boot menu is a terrible low resolution. But at least it built for the kernel. Not it just fails.
The line "@=auto" belongs to the line above it, it should be: ...vbeinfo' @=auto Remove the 'newline' between "vbeinfo'" and "@=auto" and try again. Default fallback resolution is 640 x 480 (VGA), which gives you the "terrible low resolution", GRUB_GFXMODE=@ means autodetect. - Yamaban. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Putting @=auto back on the line above fixed the problem. The newest installed kernel is running. Thanks! I know it is a different thing than the original topic, but I still get the crappy resolution in the boot menu. Maybe I should try GRUB_GFXMODE=@ On Thu, Mar 12, 2015 at 9:44 PM, Yamaban <foerster@lisas.de> wrote:
On Thu, 12 Mar 2015 21:05, Roger Oberholtzer <roger.oberholtzer@...> wrote:
It failed for the same reason both when I ran update-bootloader --refresh and when I updated via YaST. It complains like this:
Perl-Bootloader: 2015-03-12 20:53:13 <3> pbl-3048.2 Core::RunCommand.1642: Error: Command '/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg >/var/log/YaST2/y2log_bootloader 2>&1' failed with code 32512 and output: /etc/default/grub: line 25: @=auto: command not found
Indeed line 25 in /etc/default/grub is "@=auto"
Here is the context in that file:
# The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' @=auto GRUB_GFXMODE=1920x1080
I am fairly certain I did not put that line there. Should it be something else?
I can say that the current boot menu is a terrible low resolution. But at least it built for the kernel. Not it just fails.
The line "@=auto" belongs to the line above it, it should be: ...vbeinfo' @=auto
Remove the 'newline' between "vbeinfo'" and "@=auto" and try again.
Default fallback resolution is 640 x 480 (VGA), which gives you the "terrible low resolution", GRUB_GFXMODE=@ means autodetect.
- Yamaban.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
Default fallback resolution is 640 x 480 (VGA), which gives you the "terrible low resolution", GRUB_GFXMODE=@ means autodetect.
GRUB_GFXMODE=@ results in a character menu I see that if you select auto in Yast, it sets GRUB_GFXMODE=auto GRUB_GFXMODE=auto and GRUB_GFXMODE=1920x1080 both result in the low resolution graphic menu. The physical resolution is 1920x1080. I sense a new thread is needed for this. -- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
В Thu, 12 Mar 2015 21:44:59 +0100 (CET) Yamaban <foerster@lisas.de> пишет:
On Thu, 12 Mar 2015 21:05, Roger Oberholtzer <roger.oberholtzer@...> wrote:
It failed for the same reason both when I ran update-bootloader --refresh and when I updated via YaST. It complains like this:
Perl-Bootloader: 2015-03-12 20:53:13 <3> pbl-3048.2 Core::RunCommand.1642: Error: Command '/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg >/var/log/YaST2/y2log_bootloader 2>&1' failed with code 32512 and output: /etc/default/grub: line 25: @=auto: command not found
Indeed line 25 in /etc/default/grub is "@=auto"
Here is the context in that file:
# The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' @=auto GRUB_GFXMODE=1920x1080
I am fairly certain I did not put that line there. Should it be something else?
I can say that the current boot menu is a terrible low resolution. But at least it built for the kernel. Not it just fails.
The line "@=auto" belongs to the line above it,
No, it does not. There is no @=auto in this file and "vbeinfo @=auto" makes no sense (it is invalid parameter). Something incorrectly put it in there. I suppose intention was to produce GRUB_GFXMODE=auto.
it should be: ...vbeinfo' @=auto
Remove the 'newline' between "vbeinfo'" and "@=auto" and try again.
Default fallback resolution is 640 x 480 (VGA), which gives you the "terrible low resolution", GRUB_GFXMODE=@ means autodetect.
- Yamaban.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
I will remove the extraneous @=auto Thanks all. Next to remove all the old kernels eating my laptop's hard disk space! On Fri, Mar 13, 2015 at 4:13 AM, Andrei Borzenkov <arvidjaar@gmail.com> wrote:
В Thu, 12 Mar 2015 21:44:59 +0100 (CET) Yamaban <foerster@lisas.de> пишет:
On Thu, 12 Mar 2015 21:05, Roger Oberholtzer <roger.oberholtzer@...> wrote:
It failed for the same reason both when I ran update-bootloader --refresh and when I updated via YaST. It complains like this:
Perl-Bootloader: 2015-03-12 20:53:13 <3> pbl-3048.2 Core::RunCommand.1642: Error: Command '/usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg >/var/log/YaST2/y2log_bootloader 2>&1' failed with code 32512 and output: /etc/default/grub: line 25: @=auto: command not found
Indeed line 25 in /etc/default/grub is "@=auto"
Here is the context in that file:
# The resolution used on graphical terminal # note that you can use only modes which your graphic card supports via VBE # you can see them in real GRUB with the command `vbeinfo' @=auto GRUB_GFXMODE=1920x1080
I am fairly certain I did not put that line there. Should it be something else?
I can say that the current boot menu is a terrible low resolution. But at least it built for the kernel. Not it just fails.
The line "@=auto" belongs to the line above it,
No, it does not. There is no @=auto in this file and "vbeinfo @=auto" makes no sense (it is invalid parameter).
Something incorrectly put it in there. I suppose intention was to produce GRUB_GFXMODE=auto.
it should be: ...vbeinfo' @=auto
Remove the 'newline' between "vbeinfo'" and "@=auto" and try again.
Default fallback resolution is 640 x 480 (VGA), which gives you the "terrible low resolution", GRUB_GFXMODE=@ means autodetect.
- Yamaban.
-- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
-- Roger Oberholtzer -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse+owner@opensuse.org
participants (5)
-
Andrei Borzenkov -
Mark Misulich -
Per Jessen -
Roger Oberholtzer -
Yamaban