Page 3 of 5 FirstFirst 12345 LastLast
Results 21 to 30 of 45

Thread: How to activate installed latest kernel after latest upgrade?

  1. #21
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,278
    Blog Entries
    2

    Default Re: How to activate installed latest kernel after latest upgrade?

    Try running the mkconfig command in a root console instead of running "sudo" in a normal User console...

    If that doesn't work,
    Then something happened when your kernel was installed.
    Instead of chasing the problem,
    I'd recommend force re-installing your kernel which I'd assume should re-write proper entries to your grub files...
    ie.
    Determine your exact kernel package name by running "zypper si kernel"
    Then
    Code:
    zypper in -f package_name 
    HTH,
    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  2. #22
    Join Date
    Mar 2019
    Location
    mtl.qc.ca
    Posts
    127

    Default Re: How to activate installed latest kernel after latest upgrade?

    Do you see the Kernel in the third option in the Grub menu: Start bootloader from a read-only snapshot? Try to boot from there.
    Ryzen 2700U FHD Lenovo ThinkPad E585

  3. #23
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,617
    Blog Entries
    3

    Default Re: How to activate installed latest kernel after latest upgrade?

    Quote Originally Posted by ace4dude View Post
    Code:
    + /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg                                                                          
    /usr/sbin/grub2-mkconfig: line 275: /bin/rm: Argument list too long                                                         
    >>>>>>>>>>>>>>>>                                                                                                              
    Updating bootloader failed                                                                                                  
    warning: %postun(virtualbox-host-kmp-default-6.0.8_k5.2.2_1-3.4.x86_64) scriptlet failed, exit status 1
    That's what is failing. The command "grub2-mkconfig" is failing because of that, so no new config is being generated.

    I looked at "/usr/sbin/grub2-mkconfig". That failing line is just
    Code:
     rm -f "${grub_cfg}.new"
    At a quick scan, it looks as if "${grub_cfg}" is just supposed to be the path to the file "grub.cfg". It is weird that it is too long.

    As root, can you run the command:
    Code:
    sh -x /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg
    Maybe first use the "script" command. And, when finished, use "exit" to leave "script". That way the output will be in the file "typescript" in the current directory, where it can be examined. It should show what "${grub_cfg} is being expanded to. The last few lines in that "typescript" file are where to look.

    Something is messed up on your system (which seems to be a virtual machine under "virtualbox").
    Last edited by nrickert; 31-Jul-2019 at 10:57.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  4. #24
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,278
    Blog Entries
    2

    Default Re: How to activate installed latest kernel after latest upgrade?

    The error "/bin/rm: Argument list too long" means that the "rm" command was invoked, but the directory it's pointing to has too many files to remove. You may need to use an "xargs rm" command against that directory or manually remove files in smaller batches. Problem is, I'm having problems locating the directory grub2-mkconfig is trying to clean out.

    Before trying to troubleshoot the error directly though,
    You should probably run the following from
    https://doc.opensuse.org/documentati...cha.grub2.html

    Verify your grub script hasn't been altered with syntax errors
    Code:
    grub2-script-check /boot/grub2/grub.cfg
    Although it's probably not especially helpful,
    Getting a readout of your grub.cfg output is probably something you should do to just verify it matches what you see and doesn't have hidden lines or garbage
    Code:
    grub2-mkconfig
    And,
    An off the wall question... Is your root partition BTRFS and are you sure you have <plenty> of available, unused space?
    Code:
    btrfs du
    TSU
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  5. #25

    Default Re: How to activate installed latest kernel after latest upgrade?

    Quote Originally Posted by mrmazda View Post
    This shows the current kernel is symlinked, aka the kernel you wish to boot. You can boot this kernel without having to figure out what is wrong with grub first by striking the E at the grub menu, scrolling down to the lines where you see -5.2.2-1-default, and removing those characters, leaving only vmlinuz and initrd when finished. Then you can proceed to boot kernel 5.2.2-1 via the instruction at the bottom of that screen, and be running 5.2.2-1 to find and fix your Grub menu problem.

    99.7+% of my openSUSE booting is done from kernel and initrd lines with no version numbers.
    Yep, using the E and removed -5.1.16-default (no 5.2.x is listed on the Grub menu as I mentioned previously), I managed to log in with 5.2.3-1. Now I need to figure out how to fix the Grub menu to list the latest kernel version 5.2.3 and remove the old kernel versions on the Grub menu.

  6. #26

    Default Re: How to activate installed latest kernel after latest upgrade?

    Quote Originally Posted by tsu2 View Post
    Verify your grub script hasn't been altered with syntax errors
    Code:
    grub2-script-check /boot/grub2/grub.cfg
    Executing this returns nothing.

  7. #27

    Default Re: How to activate installed latest kernel after latest upgrade?

    Quote Originally Posted by tsu2 View Post
    Although it's probably not especially helpful,
    Getting a readout of your grub.cfg output is probably something you should do to just verify it matches what you see and doesn't have hidden lines or garbage
    Code:
    grub2-mkconfig
    Executing this returns
    Code:
    /usr/sbin/grub2-mkconfig: line 280: /usr/bin/gettext: Argument list too long
    My system does not use any BTRFS. I think it's Ext4 only

  8. #28

    Default Re: How to activate installed latest kernel after latest upgrade?

    Quote Originally Posted by nrickert View Post
    As root, can you run the command:
    Code:
    sh -x /usr/sbin/grub2-mkconfig -o /boot/grub2/grub.cfg
    Executing this returns the following:
    Code:
    ...buntch of 
    vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16'
    + '[' xgfxterm '!=' x ']'
    + '[' xgfxterm '!=' xgfxterm ']'
    + GRUB_TERMINAL_OUTPUT=gfxterm
    + termoutdefault=0
    + '[' xgfxterm = x ']'
    + for x in ${GRUB_TERMINAL_OUTPUT}
    + case "x${x}" in
    + GRUB_ACTUAL_DEFAULT=saved
    + '[' xsaved = xsaved ']'
    ++ /usr/bin/grub2-editenv - list
    ++ sed -n '/^saved_entry=/ s,^saved_entry=,,p'
    + GRUB_ACTUAL_DEFAULT='openSUSE Tumbleweed'
    + '[' x = x ']'
    + '[' -f /etc/os-release ']'
    + . /etc/os-release
    ++ NAME='openSUSE Tumbleweed'
    ++ ID=opensuse-tumbleweed
    ++ ID_LIKE='opensuse suse'
    ++ VERSION_ID=20190730
    ++ PRETTY_NAME='openSUSE Tumbleweed'
    ++ ANSI_COLOR='0;32'
    ++ CPE_NAME=cpe:/o:opensuse:tumbleweed:20190730
    ++ BUG_REPORT_URL=https://bugs.opensuse.org
    ++ HOME_URL=https://www.opensuse.org/
    ++ LOGO=distributor-logo
    + echo 'openSUSE Tumbleweed'
    + grep -q '^openSUSE Tumbleweed'
    + GRUB_DISTRIBUTOR='openSUSE Tumbleweed'
    + export GRUB_DEVICE GRUB_DEVICE_UUID GRUB_DEVICE_BOOT GRUB_DEVICE_BOOT_UUID GRUB_FS GRUB_FONT GRUB_PRELOAD_MODULES GRUB_ACTUAL_DEFAULT
    + export GRUB_DEFAULT GRUB_HIDDEN_TIMEOUT GRUB_HIDDEN_TIMEOUT_QUIET GRUB_TIMEOUT GRUB_TIMEOUT_STYLE GRUB_DEFAULT_BUTTON GRUB_HIDDEN_TIMEOUT_BUTTON GRUB_TIMEOUT_BUTTON GRUB_TIMEOUT_STYLE_BUTTON GRUB_BUTTON_CMOS_ADDRESS GRUB_BUTTON_CMOS_CLEAN GRUB_DISTRIBUTOR GRUB_CMDLINE_LINUX GRUB_CMDLINE_LINUX_DEFAULT GRUB_CMDLINE_XEN GRUB_CMDLINE_XEN_DEFAULT GRUB_CMDLINE_LINUX_XEN_REPLACE GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT GRUB_CMDLINE_NETBSD GRUB_CMDLINE_NETBSD_DEFAULT GRUB_CMDLINE_GNUMACH GRUB_TERMINAL_INPUT GRUB_TERMINAL_OUTPUT GRUB_SERIAL_COMMAND GRUB_DISABLE_LINUX_UUID GRUB_DISABLE_RECOVERY GRUB_VIDEO_BACKEND GRUB_GFXMODE GRUB_BACKGROUND GRUB_THEME GRUB_GFXPAYLOAD_LINUX GRUB_DISABLE_OS_PROBER GRUB_INIT_TUNE GRUB_SAVEDEFAULT GRUB_ENABLE_CRYPTODISK GRUB_BADRAM GRUB_OS_PROBER_SKIP_LIST GRUB_DISABLE_SUBMENU GRUB_CMDLINE_LINUX_RECOVERY GRUB_USE_LINUXEFI SUSE_BTRFS_SNAPSHOT_BOOTING SUSE_CMDLINE_XENEFI SUSE_REMOVE_LINUX_ROOT_PARAM
    + test x/boot/grub2/grub.cfg '!=' x
    + rm -f /boot/grub2/grub.cfg.new
    /usr/sbin/grub2-mkconfig: line 275: /usr/bin/rm: Argument list too long
    There're a buntch of "vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 " stuffs in the 1st part of the output extended beyond the upper terminal. So that was the "Argument list too long" I think.

  9. #29
    Join Date
    Aug 2010
    Location
    Chicago suburbs
    Posts
    12,617
    Blog Entries
    3

    Default Re: How to activate installed latest kernel after latest upgrade?

    Quote Originally Posted by ace4dude View Post
    There're a buntch of "vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 vga=gfx-1024x768x16 " stuffs in the 1st part of the output extended beyond the upper terminal. So that was the "Argument list too long" I think.
    I'm still a bit puzzled by this.

    I'm pretty sure that the argument list is stored on the stack. I'm beginningn to wonder whether you are running out of stack space.

    Is this 32-bit Tumbleweed? It's more likely to have a stack problem with 32-bit than with 64-bit.
    openSUSE Leap 15.1; KDE Plasma 5;
    testing Leap 15.2Alpha

  10. #30

    Default Re: How to activate installed latest kernel after latest upgrade?

    Quote Originally Posted by nrickert View Post
    I'm still a bit puzzled by this.

    I'm pretty sure that the argument list is stored on the stack. I'm beginningn to wonder whether you are running out of stack space.

    Is this 32-bit Tumbleweed? It's more likely to have a stack problem with 32-bit than with 64-bit.
    It's 64-bit Tumbleweed.

Page 3 of 5 FirstFirst 12345 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
  •