F30 Grub2-mkconfig and Grub2-install not Working Correctly?

[Stephen Morris]

Hi,

I have upgraded from F29 to F30 via the recommenced dnf method. I 
have Fedora running in a vm under vmware player. Grub2-mkconfig and 
grub2-install no longer seem to generate the grub menu as they did under 
F29, the menu seems to be that generated by grubby (it could be that 
turning off the suppression of sub-menu creation is now being ignored). 
Looking at /boot/grub2/grub.cfg I cannot see any references in there to 
kernels, so I have attached the file for reference. Am I missing 
something or is the functionality now different, /boot/grub2/grub.cfg is 
where I have always written the grub.cfg via this process?

regards,

Steve

[Tom H]

On Thu, May 23, 2019 at 12:55 AM Stephen Morris
 wrote:
> I have upgraded from F29 to F30 via the recommenced dnf method. I
> have Fedora running in a vm under vmware player. Grub2-mkconfig and
> grub2-install no longer seem to generate the grub menu as they did
> under F29, the menu seems to be that generated by grubby (it could
> be that turning off the suppression of sub-menu creation is now
> being ignored). Looking at /boot/grub2/grub.cfg I cannot see any
> references in there to kernels, so I have attached the file for
> reference. Am I missing something or is the functionality now
> different, /boot/grub2/grub.cfg is where I have always written the
> grub.cfg via this process?

You have

insmod blscfg
blscfg

on lines 128-129.

So grub's setting up a generic BLS grub.cfg and you should have your
kernel specifications in "/boot/loader/entries/*.conf".

Does "/boot/grub2/i386-pc/blscfg.mod" exist on your system?

IIRC, the common bugs page recommends "configfile
/boot/grub2/grub.cfg.rpmsave" or "configfile /grub2/grub.cfg.rpmsave"
(depending on whether "/boot" is a separate filesystem) at the grub
prompt to use the previous grub.cfg.

[Stephen Morris]

On 23/5/19 3:49 pm, Tom H wrote:
> On Thu, May 23, 2019 at 12:55 AM Stephen Morris
>  wrote:
> > I have upgraded from F29 to F30 via the recommenced dnf method. I
> > have Fedora running in a vm under vmware player. Grub2-mkconfig and
> > grub2-install no longer seem to generate the grub menu as they did
> > under F29, the menu seems to be that generated by grubby (it could
> > be that turning off the suppression of sub-menu creation is now
> > being ignored). Looking at /boot/grub2/grub.cfg I cannot see any
> > references in there to kernels, so I have attached the file for
> > reference. Am I missing something or is the functionality now
> > different, /boot/grub2/grub.cfg is where I have always written the
> > grub.cfg via this process?
>
> You have
>
> insmod blscfg
> blscfg
>
> on lines 128-129.
>
> So grub's setting up a generic BLS grub.cfg and you should have your
> kernel specifications in "/boot/loader/entries/*.conf".
>
> Does "/boot/grub2/i386-pc/blscfg.mod" exist on your system?
>
> IIRC, the common bugs page recommends "configfile
> /boot/grub2/grub.cfg.rpmsave" or "configfile /grub2/grub.cfg.rpmsave"
> (depending on whether "/boot" is a separate filesystem) at the grub
> prompt to use the previous grub.cfg.

Is it documented anywhere how to switch the system back to using, in my 
case, /boot/grub2/grub.cfg to provide the kernel menu structure via 
grub2-mkconfig and grub2-install as it was in previous versions of Fedora?

regards,

Steve
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]

[Tom H]

On Thu, May 23, 2019 at 11:12 AM Stephen Morris
 wrote:
> On 23/5/19 3:49 pm, Tom H wrote:
> > On Thu, May 23, 2019 at 12:55 AM Stephen Morris
> >  wrote:
> > > I have upgraded from F29 to F30 via the recommenced dnf method. I
> > > have Fedora running in a vm under vmware player. Grub2-mkconfig
> > > and grub2-install no longer seem to generate the grub menu as
> > > they did under F29, the menu seems to be that generated by grubby
> > > (it could be that turning off the suppression of sub-menu
> > > creation is now being ignored). Looking at /boot/grub2/grub.cfg I
> > > cannot see any references in there to kernels, so I have attached
> > > the file for reference. Am I missing something or is the
> > > functionality now different, /boot/grub2/grub.cfg is where I have
> > > always written the grub.cfg via this process?
> >
> > You have
> >
> > insmod blscfg
> > blscfg
> >
> > on lines 128-129.
> >
> > So grub's setting up a generic BLS grub.cfg and you should have
> > your kernel specifications in "/boot/loader/entries/*.conf".
> >
> > Does "/boot/grub2/i386-pc/blscfg.mod" exist on your system?
> >
> > IIRC, the common bugs page recommends "configfile
> > /boot/grub2/grub.cfg.rpmsave" or "configfile
> > //grub2/grub.cfg.rpmsave"
> > (depending on whether "/boot" is a separate filesystem) at the
> > grub prompt to use the previous grub.cfg.
>
> Is it documented anywhere how to switch the system back to using,
> in my case, /boot/grub2/grub.cfg to provide the kernel menu
> structure via grub2-mkconfig and grub2-install as it was in
> previous versions of Fedora?

I haven't tried it but setting "GRUB_ENABLE_BLSCFG=false"
"/etc/default/grub" _should_ (given the variable's name) allow
"grub2-mkconfig" give you an upstream-style "grub.cfg".

[Stephen Morris]

On 23/5/19 9:07 pm, Tom H wrote:
> On Thu, May 23, 2019 at 11:12 AM Stephen Morris
>  wrote:
> > On 23/5/19 3:49 pm, Tom H wrote:
> > > On Thu, May 23, 2019 at 12:55 AM Stephen Morris
> > >  wrote:
> > > > I have upgraded from F29 to F30 via the recommenced dnf method. I
> > > > have Fedora running in a vm under vmware player. Grub2-mkconfig
> > > > and grub2-install no longer seem to generate the grub menu as
> > > > they did under F29, the menu seems to be that generated by grubby
> > > > (it could be that turning off the suppression of sub-menu
> > > > creation is now being ignored). Looking at /boot/grub2/grub.cfg I
> > > > cannot see any references in there to kernels, so I have attached
> > > > the file for reference. Am I missing something or is the
> > > > functionality now different, /boot/grub2/grub.cfg is where I have
> > > > always written the grub.cfg via this process?
> > >
> > > You have
> > >
> > > insmod blscfg
> > > blscfg
> > >
> > > on lines 128-129.
> > >
> > > So grub's setting up a generic BLS grub.cfg and you should have
> > > your kernel specifications in "/boot/loader/entries/*.conf".
> > >
> > > Does "/boot/grub2/i386-pc/blscfg.mod" exist on your system?
> > >
> > > IIRC, the common bugs page recommends "configfile
> > > /boot/grub2/grub.cfg.rpmsave" or "configfile
> > > //grub2/grub.cfg.rpmsave"
> > > (depending on whether "/boot" is a separate filesystem) at the
> > > grub prompt to use the previous grub.cfg.
> >
> > Is it documented anywhere how to switch the system back to using,
> > in my case, /boot/grub2/grub.cfg to provide the kernel menu
> > structure via grub2-mkconfig and grub2-install as it was in
> > previous versions of Fedora?
>
> I haven't tried it but setting "GRUB_ENABLE_BLSCFG=false"
> "/etc/default/grub" _should_ (given the variable's name) allow
> "grub2-mkconfig" give you an upstream-style "grub.cfg".

Thanks Tom, "/etc/default/grub" had a setting of 
"GRUB_ENABLE_BLSCFG=true" which I changed from "true" to "false" and 
that enabled the original grub2-mkconfig style menu. So everything is 
now good.

regards,

Steve
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]

[Tom H]

> On 23/5/19 9:07 pm, Tom H wrote:
> > I haven't tried it but setting "GRUB_ENABLE_BLSCFG=false"
> > "/etc/default/grub" _should_ (given the variable's name) allow
> > "grub2-mkconfig" give you an upstream-style "grub.cfg".
>
> Thanks Tom, "/etc/default/grub" had a setting of
> "GRUB_ENABLE_BLSCFG=true" which I changed from "true" to "false"
> and that enabled the original grub2-mkconfig style menu. So
> everything is now good.

Good. You're welcome.

[ But the BLS way is nice too. If you have the time, you should set up
a VM and check it out. ]

[ja]

On Mon, 2019-05-27 at 19:10 +0200, Tom H wrote:
> > On 23/5/19 9:07 pm, Tom H wrote:
> > > I haven't tried it but setting "GRUB_ENABLE_BLSCFG=false"
> > > "/etc/default/grub" _should_ (given the variable's name) allow
> > > "grub2-mkconfig" give you an upstream-style "grub.cfg".
> >
> > Thanks Tom, "/etc/default/grub" had a setting of
> > "GRUB_ENABLE_BLSCFG=true" which I changed from "true" to "false"
> > and that enabled the original grub2-mkconfig style menu. So
> > everything is now good.
>
> Good. You're welcome.
>
> [ But the BLS way is nice too. If you have the time, you should set up
> a VM and check it out. ]

+1

[Chris Murphy]

On Thu, May 23, 2019 at 5:08 AM Tom H  wrote:
> I haven't tried it but setting "GRUB_ENABLE_BLSCFG=false"
> "/etc/default/grub" _should_ (given the variable's name) allow
> "grub2-mkconfig" give you an upstream-style "grub.cfg".

It is also necessary to
# dnf install grubby-deprecated

I'm not sure how long that deprecated package will be maintained, so I
don't recommend reverting this change, instead it's better to move
forward, file bugs, and make it better.

[Chris Murphy]

On Mon, May 27, 2019 at 10:37 PM Chris Murphy  wrote:
> On Thu, May 23, 2019 at 5:08 AM Tom H  wrote:
> > I haven't tried it but setting "GRUB_ENABLE_BLSCFG=false"
> > "/etc/default/grub" _should_ (given the variable's name) allow
> > "grub2-mkconfig" give you an upstream-style "grub.cfg".
>
> It is also necessary to
> # dnf install grubby-deprecated
>
> I'm not sure how long that deprecated package will be maintained, so I
> don't recommend reverting this change, instead it's better to move
> forward, file bugs, and make it better.

Explanation: This package is the real grubby. The grubby package in
F30 is a wrapper script that has far less functionality and is there
just to help people familiar with grubby commands for changing kernel
boot behavior like boot parameters and default kernel. But if you
revert to the old way, you need the real grubby provided by the
grubby-deprecated package, because that's what rewrites the grub.cfg
when new kernels are installed and old kernels are removed.

[Stephen Morris]

On 28/5/19 3:17 am, ja wrote:
> On Mon, 2019-05-27 at 19:10 +0200, Tom H wrote:
> > > On 23/5/19 9:07 pm, Tom H wrote:
> > > > I haven't tried it but setting "GRUB_ENABLE_BLSCFG=false"
> > > > "/etc/default/grub" _should_ (given the variable's name) allow
> > > > "grub2-mkconfig" give you an upstream-style "grub.cfg".
> > >
> > > Thanks Tom, "/etc/default/grub" had a setting of
> > > "GRUB_ENABLE_BLSCFG=true" which I changed from "true" to "false"
> > > and that enabled the original grub2-mkconfig style menu. So
> > > everything is now good.
> >
> > Good. You're welcome.
> >
> > [ But the BLS way is nice too. If you have the time, you should set up
> > a VM and check it out. ]
>
> +1

I'd be quite happy to use the BLS methodology if it used the same menu 
structure as generated by grub2-mkconfig. I've never liked the way 
grubby produces the menus, and BLS seems to be exactly the same. Other 
OS menu entries are not required now, as I'm running F30 in a VM under 
Windows 10 now, with Ubuntu in a 2nd VM instead of tri-booting as I was 
previously. I actually wanted to run Windows 10 in a VM under Fedora, 
but Fedora wouldn't install in my hardware raid environment, nor would 
it install with UEFI active, the live cd hung at a black screen at the 
point of wanting to display the desktop, and I couldn't get it advance 
any further.

regards,

Steve
> users mailing list -- [e-mail]
> To unsubscribe send an email to [e-mail]
> 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/[e-mail]