Adding kernel boot parameters via YaST2 take no effect

English Install/Boot/Login
1

So I wanted to add rd.neednet=1 ip=dhcp to my kernel boot parameters with CLI YaST2, and I see the kernel parameters in the snapshot boot entries in /boot/efi/loader/entries, but not in the main boot entries. What’s going wrong here?

2

Please show the result of

sudo update-bootloader --show

(using pre-formatted text tags, the </> button above the editing area)

3 
❯ sudo update-bootloader --show
[sudo] password for root:
grub2-bls
4

I’m not sure that YaST2-bootloader works with grub2-bls. You should try:

sudo update-bootloader --add-option rd.neednet=1 ip=dhcp

assuming that you are not multi-booting, or at least the system you are writing from is the one controlling the bootloader.

5

@OrsoBruno @XaserIII after adding/deleting options you must run update-bootloader --config. The option --config is the default, I just use update-bootloader which works for me.

6

@XaserIII There seems to be a bug, just did a fresh Tumbleweed install and boot options are not being saved… need to investigate some more. In the interim, just use the e key to edit and add at the end of the linux line…

2 Likes
7

Thanks. Just to clarify: does the bug pertain YaST itself or update-bootloader? is update-bootloader required with grub-bls after changing kernel boot parameters with YaST?

8

Hi, after investigation completes if report needed then file bug with https://bugzilla.opensuse.org/ perhaps this is not solved yet?

Under the category of: Component > Bootloader

Not sure but update-bootloader is a command line argument. See update-bootloader --helpfor more info.

Cannot use YaST to change grub-bls boot loader options (possibly never as YaST is becoming depreciated). Must change grub-bls entries via command line currently.

1 Like
9
10

@XaserIII YaST is deprecated so not looking at that, update-booloader AFAIKT update-bootloader is working, just not getting to where it needs to be I’m on ext4 as well…

11

@XaserIII what filesystem in use? I just did a fresh install and used btrfs, all is fine, I can add and delete options…

12

Runnig update-bootloader --config does indeed work. To me it was not transparent if update-bootloader respects changes done to the kernel boot parameters in YaST2, i.e. if both tools use the same files, which appears to be the case, in particular /etc/kernel/cmdline.

13

@XaserIII What filesystem in use?

14

@malcolmlewis btrfs in LVM

15

@XaserIII ok, thanks for confirming :smile:

16

Hi @malcolmlewis, any updates on a fix for not saving boot options? In my case it’s Tumbleweed (snapshot 20260103) installed on Lenovo Legion with 5080 (filesystem ext4 with no LVM nor encryption) so I needed nomodeset option during install. Now there is no way to remove it using update-bootloader --del-option nomodeset

17

Ok what’s funny one of two things did the trick (did both before reboot so can’t say which):

  1. Using update-bootloader --config instaed of just update-bootloader
  2. Installing nvidia drivers using zypper install-new-recommends
18

AFAIU, with GRUB2+BLS, update-bootloader updates /etc/kernel/cmdline for future kernel entries, but existing entries aren’t rewritten. To apply a change immediately, you must boot a newly generated kernel entry or modify the current entry directly. Reinstalling the kernel, as you did, triggers the GRUB2 BLS hooks to regenerate the per-kernel .conf file in /boot/loader/entries/<kernel>.conf.

1 Like
19

Running update-bootloader defaults to --config, so no difference.

Installing or updating kernel module packages (like NVIDIA drivers) involves regenerating the initramfs, which in turn triggers GRUB2 BLS hooks to rebuild the current kernel’s .conf entry, making any boot option changes take effect immediately.

20

@deano_ferrari correct, just tested it again and just doing update-bootloader --config is not enough. Thanks for additional info