On 2020-06-11 05:41, R. G. Newbury wrote: > On 2020-06-09 8:11 p.m.Stephen Morris<samorris@xxxxxxxxxxxxxxx> wrote >> if in /etc/default/grub you have the entry GRUB_ENABLE_BLSCFG=true >> that inserts a line into the grub processes to use the new BLS standard,=20 >> in which case grub2-mkconfig and possibly grubby do nothing until that=20 >> entry is set to false. I have always use grub2-mkconfig because I have=20 >> never liked what grubby generated, and what BLS generates appears to be=20 >> the same as what grubby does, and I found that I had to set that entry=20 >> to false for grub2-mkconfig to continue to work. > > THANKS FOR THAT, Steve! > > I could not get grub2-mkconfig to actually change the grub.cfg file. Now I know why ( but not why such a dangerously misdescriptive switch would be hidden away in a default file). > In the past I would just edit the damn file, but the new motherboard uses EFI, and such hands-on fixing might lead to an undesired result! > I know I'm "late to the party". Laid up in hospital for the past week and previous message in this thread have been "expired". I've just used the grub2-editenv command which is new with the BLS standard. My understanding is that at some point using GRUB_ENABLE_BLSCFG=false may no longer be an option. So, using my system as an example, I just do below to do a change. grub2-editenv - set "kernelopts=root=UUID=4455f2e9-fed2-4e1e-856d-642b531547f9 ro rd.driver.blacklist=nouveau modprobe.blacklist=nouveau" Of course I normally first do grub2-editenv list to get the current settings. -- The key to getting good answers is to ask good questions. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
