On Thu, May 2, 2019 at 8:36 AM Tom Horsley <horsley1953@xxxxxxxxx> wrote: > > I have theoretically disabled the BLS stuff > (so I can boot fedora 30 with the configfile > command from an older grub that knows nothing > of the BLS support in the configfile). > > This worked, but now I wonder about the state > of the rpmfusion nvidia drivers and what they > can deal with when changing kernel options > (to blacklist nouveau). > > How much trouble are folks using the nvidia binaries > in with the new grub stuff? I don't have any Nvidia computers, but I have one with busted Radeon graphics and working i915, so I have to clobber the Radeon within GRUB to make sure it's powered off. For S&G, see this crazy bug and work around [1] which I updated for Fedora 30 because some things have changed including BLS stuff. Anyway, if you just want to globally change kernel parameters, you can still do it the usual way. Edit /etc/default/grub GRUB_CMDLINE_LINUX= line adding the parameters you want, and then run grub2-mkconfig pointed to the proper grub.cfg location. This works because it also modifies /boot/grub2/grubenv kernelopts= which in turn is picked up by the 'options $kernelopts ' line found in every uncustomized /boot/loader/entries/*.conf file. Instead of that, I've settled on a one shot global change method, which I've heard is a bit fragile even though I haven't had problems with it, and I did this quite a lot during the F30 testing cycle. Show grubenv contents # grub2-editenv list Change boot parameters # grub2-editenv - set kernelopts="root=UUID=blahblahblahuuidblahblah ro rootflags=subvol=root30 enable_mtrr_cleanup=1 zswap.enabled=1 zswap.max_pool_percent=25 zswap.compressor=lz4 no_console_suspend" If you want to make some extra menu entries that have unique boot parameters, you can just duplicate the *.conf files, give them a unique name, and wipe out the $kernelopts and add whatever you want. What I haven't tried is whether you can just tack on after $kernelopts additional options, I suspect you can. Also, I know there are naming rules that affect the ordering of the menu entries, possibly based on the conf file version value, but I'm not certain. Bottom line is $kernelopts is defined in the grubenv. It is possible for the grub.cfg or /etc/default/grub to go stale, but GRUB only cares about the contents of the grubenv at the time GRUB loads in the pre-boot environment. [1] https://bugzilla.redhat.com/show_bug.cgi?id=765954#c65 -- Chris Murphy _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
