On Wed, Apr 10, 2019 at 5:48 AM Berend De Schouwer <berend.de.schouwer@xxxxxxxxx> wrote: > > On Tue, 2019-04-09 at 23:10 -0600, Chris Murphy wrote: > > set debug=all > > blscfg > > script/lexer.c:321: token 288 text [blscfg] > script/lexer.c:321: token 259 text [ > ] > script/lexer.c:321: token 0 text [] > error: ../../grub-core/commands/blscfg.c:959:variable 'boot' isn't set. > > > Indeed, grub.cfg doesn't have a boot statement. It does have boot_once > and fastboot, etc. > > None of loader/entries/ has "boot" either. grub.cfg.rpmsave also > doesn't have "boot". I think it wants ($boot) but isn't seeing it defined. Back at the grub prompt, without debug enabled, what output do you get for > set I think the most relevant are root, prefix, and blscfg_dir (or something like that). I think this needs a bug report against grub2. Include the blscfg debug info you provided. Also include the 'set' output, which are environment variables for GRUB. And also all of: /etc/default/grub /boot/grub2/grub.cfg /boot/grub2/grubenv /boot/loader/entries/*conf ## I think one is sufficient. -- Chris Murphy _______________________________________________ test mailing list -- test@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to test-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/test@xxxxxxxxxxxxxxxxxxxxxxx
