Fedora 26 boot messages -

[Bob Goodwin]

I prefer not watching the blank screen with the egg turning into an F 
and normally remove rhgb from /etc/default/grub.

That is not having the desired effect on this Fedora-26 system.

[root@Box10 bobg]# grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
Found linux image: /boot/vmlinuz-4.11.11-300.fc26.x86_64
Found initrd image: /boot/initramfs-4.11.11-300.fc26.x86_64.img
Found linux image: /boot/vmlinuz-4.11.10-300.fc26.x86_64
Found initrd image: /boot/initramfs-4.11.10-300.fc26.x86_64.img
Found linux image: /boot/vmlinuz-4.11.8-300.fc26.x86_64
Found initrd image: /boot/initramfs-4.11.8-300.fc26.x86_64.img
Found linux image: /boot/vmlinuz-0-rescue-aa89d651e4d748019730a305625d3df0
Found initrd image: 
/boot/initramfs-0-rescue-aa89d651e4d748019730a305625d3df0.img
Found Fedora 25 (Twenty Five) on /dev/sdb3
done

It appears to be saving to the wrong system on another hard drive, 
Fedora 16 is on /dev/sda:

/dev/sda4           49G   25G   22G  53% /
tmpfs              3.9G   16K  3.9G   1% /tmp
/dev/sda2          976M  167M  742M  19% /boot
/dev/sda1          200M  9.5M  191M   5% /boot/efi
/dev/sda5          858G   13G  802G   2% /home

Obviously this is wrong? Whay should I be doing or is this something I 
can no longer change?

Bob

[Tom Horsley]

On Tue, 8 Aug 2017 13:03:46 -0400
Bob Goodwin wrote:
> Obviously this is wrong? Whay should I be doing or is this something I 
> can no longer change?

Nothing ever looks at /etc/default/grub or runs grub2-mkconfig unless
you manually run it.

I just edit the grub.cfg file itself. It works perfectly well
despite all the dire warnings. (The main problem being finding
the grub.cfg file if you have a uefi system - it is hidden
pretty well :-).

[Bob Goodwin]

On 08/08/17 13:10, Tom Horsley wrote:
> (The main problem being finding
> the grub.cfg file if you have a uefi system - it is hidden
> pretty well :-).

+

Then that must be my problem?

I see two boot partitions:

dev/sda2          976M  167M  742M  19% /boot
/dev/sda1          200M  9.5M  191M   5% /boot/efi

But it says "efi" not "uefi" and I dunno what the difference is. It's a 
Fedora 26 install on hard drive /dev/sda and that drive I select from 
the boot menu. I don't think /dev/sdb/ is even mounted, was surprised to 
see it working on that.

Confused ...

[Rick Stevens]

On 08/08/2017 10:24 AM, Bob Goodwin wrote:
> On 08/08/17 13:10, Tom Horsley wrote:
> > (The main problem being finding
> > the grub.cfg file if you have a uefi system - it is hidden
> > pretty well :-).
>
> Then that must be my problem?
>
> I see two boot partitions:
>
> dev/sda2          976M  167M  742M  19% /boot
> /dev/sda1          200M  9.5M  191M   5% /boot/efi
>
> But it says "efi" not "uefi" and I dunno what the difference is.

There really isn't. "efi" and "uefi" are synonymous in this context. If
you use UEFI booting, then the boot logic mounts the UEFI boot partition
at /boot/efi and that's where the UEFI boot magic happens. If you're not
sure if you use UEFI, try "ls /sys/firmware/efi". If you get:

[root@prophead ~]# ls /sys/firmware/efi
    ls: cannot access '/sys/firmware/efi': No such file or directory

then you're not using UEFI.

As far as the grub.cfg being hidden on UEFI systems, it really isn't.
The path to it is "/boot/efi/EFI/fedora/grub.cfg".
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    [e-mail] -
- AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
-                                                                    -
-           If it's stupid and it works...it ain't stupid!           -
----------------------------------------------------------------------

[Bob Goodwin]

On 08/08/17 14:02, Rick Stevens wrote:
> > I see two boot partitions:
> >
> > /dev/sda2          976M  167M  742M  19% /boot
> > /dev/sda1          200M  9.5M  191M   5% /boot/efi
> >
> > But it says "efi" not "uefi" and I dunno what the difference is.
>
> There really isn't. "efi" and "uefi" are synonymous in this context. If
> you use UEFI booting, then the boot logic mounts the UEFI boot partition
> at /boot/efi and that's where the UEFI boot magic happens. If you're not
> sure if you use UEFI, try "ls /sys/firmware/efi". If you get:
>
> [root@prophead ~]# ls /sys/firmware/efi
>    ls: cannot access '/sys/firmware/efi': No such file or directory
>
> then you're not using UEFI.
>
> As far as the grub.cfg being hidden on UEFI systems, it really isn't.
> The path to it is "/boot/efi/EFI/fedora/grub.cfg".

+

Well I see:

[bobg@Box10 ~]$ ls /sys/firmware/efi
config_table  efivars  esrt  fw_platform_size  fw_vendor  runtime 
runtime-map  systab

And examining that file I see "rhgb quiet" in it. Can I edit that out of 
there? Is there a special procedure to make the change?

Or is what I wanted to do just not worth the effort? It's really nit 
picking as long as things work, but if something goes wrong and slows 
the boot process I feel better seeing what's going on ...

I have a vague recollection there was something in the MSI setup about 
uefi, maybe I need to have another look at that? Hate to risk hosing a 
working system!

[Rick Stevens]

On 08/08/2017 11:24 AM, Bob Goodwin wrote:
> On 08/08/17 14:02, Rick Stevens wrote:
> > > I see two boot partitions:
> > >
> > > /dev/sda2          976M  167M  742M  19% /boot
> > > /dev/sda1          200M  9.5M  191M   5% /boot/efi
> > >
> > > But it says "efi" not "uefi" and I dunno what the difference is.
> >
> > There really isn't. "efi" and "uefi" are synonymous in this context. If
> > you use UEFI booting, then the boot logic mounts the UEFI boot partition
> > at /boot/efi and that's where the UEFI boot magic happens. If you're not
> > sure if you use UEFI, try "ls /sys/firmware/efi". If you get:
> > [root@prophead ~]# ls /sys/firmware/efi
> > ls: cannot access '/sys/firmware/efi': No such file or directory
> >
> > then you're not using UEFI.
> >
> > As far as the grub.cfg being hidden on UEFI systems, it really isn't.
> > The path to it is "/boot/efi/EFI/fedora/grub.cfg".
>
> Well I see:
>
> [bobg@Box10 ~]$ ls /sys/firmware/efi
> config_table  efivars  esrt  fw_platform_size  fw_vendor  runtime
> runtime-map  systab
>
> And examining that file I see "rhgb quiet" in it. Can I edit that out of
> there? Is there a special procedure to make the change?
>
> Or is what I wanted to do just not worth the effort? It's really nit
> picking as long as things work, but if something goes wrong and slows
> the boot process I feel better seeing what's going on ...
>
> I have a vague recollection there was something in the MSI setup about
> uefi, maybe I need to have another look at that? Hate to risk hosing a
> working system!

So, yes, you're using UEFI to boot. All you need to do is edit the
/boot/efi/EFI/fedora/grub.cfg file and remove the "rhgb quiet" bit and
reboot. You should be fine.

Note that on your next kernel upgrade, however, the "rhgb quiet" will
reappear unless you edit the /etc/default/grub file and those bits from
the "GRUB_CMDLINE_LINUX" variable in there as well.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    [e-mail] -
- AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
-                                                                    -
-  Memory is the second thing to go, but I can't remember the first! -
----------------------------------------------------------------------

[Tom Horsley]

On Tue, 8 Aug 2017 11:50:54 -0700
Rick Stevens wrote:
> Note that on your next kernel upgrade, however, the "rhgb quiet" will
> reappear unless you edit the /etc/default/grub file and those bits from
> the "GRUB_CMDLINE_LINUX" variable in there as well.

That hasn't been my experience. The "grubby" tool seems to just copy the
existing kernel parameters from the previous kernel in grub.cfg. I don't
believe anyone uses /etc/default/grub or runs grub2-mkconfig (other
than a user explicitly doing it manually). I suppose grubby might act
different for efi?

[Rick Stevens]

On 08/08/2017 11:59 AM, Tom Horsley wrote:
> On Tue, 8 Aug 2017 11:50:54 -0700
> Rick Stevens wrote:
> > Note that on your next kernel upgrade, however, the "rhgb quiet" will
> > reappear unless you edit the /etc/default/grub file and those bits from
> > the "GRUB_CMDLINE_LINUX" variable in there as well.
>
> That hasn't been my experience. The "grubby" tool seems to just copy the
> existing kernel parameters from the previous kernel in grub.cfg. I don't
> believe anyone uses /etc/default/grub or runs grub2-mkconfig (other
> than a user explicitly doing it manually). I suppose grubby might act
> different for efi?

Don't know for sure. Haven't really examined grubby (it is a binary),
but checking for files it may look at reveals this list:

root@prophead ~]# strings /usr/sbin/grubby | grep "^/" | uniq
/lib64/ld-linux-x86-64.so.2
/boof
/dev
/boot/grub/menu.lst
/etc/grub2-efi.cfg
/boot/grub/grub.cfg
/etc/grub.d/
/boot/grub2/grubenv
/etc/mtab
/boot
/etc/sysconfig/grub
/proc/mdstat
/boot/boot.b
/dev/md
/boot/grub/stage1
/etc/yaboot.conf
/etc/elilo.conf
/boot/extlinux/extlinux
/etc/grub2.cfg
/boot/grub2/grub.cfg
/boot/grub2-efi/grub.cfg
/etc/grub.conf
/boot/extlinux/extlinux.conf
/etc/zipl.conf
/etc/silo.conf
/etc/lilo.conf
/boot/efi/EFI/redhat/elilo.conf
/etc/grub.conf
/boot/grub/device.map
/etc/SuSE-release
/var/log/grubby

So based on that, no it doesn't look at /etc/default/grub. However,
grub2-mkconfig does seem to consult it. I suppose you could remove it
from both /boot/efi/EFI/fedora/grub.cfg AND /etc/default/grub.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    [e-mail] -
- AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
-                                                                    -
-     The trouble with troubleshooting is that trouble sometimes     -
-                             shoots back.                           -
----------------------------------------------------------------------

Rick Stevens  writes:
> <snip>
>
> root@prophead ~]# strings /usr/sbin/grubby | grep "^/" | uniq
> /lib64/ld-linux-x86-64.so.2
> /boof
> /dev
> /boot/grub/menu.lst
> /etc/grub2-efi.cfg
> /boot/grub/grub.cfg
> /etc/grub.d/
> /boot/grub2/grubenv
> /etc/mtab
> /boot
> /etc/sysconfig/grub
> /proc/mdstat
> /boot/boot.b
> /dev/md
> /boot/grub/stage1
> /etc/yaboot.conf
> /etc/elilo.conf
> /boot/extlinux/extlinux
> /etc/grub2.cfg
> /boot/grub2/grub.cfg
> /boot/grub2-efi/grub.cfg
> /etc/grub.conf
> /boot/extlinux/extlinux.conf
> /etc/zipl.conf
> /etc/silo.conf
> /etc/lilo.conf
> /boot/efi/EFI/redhat/elilo.conf
> /etc/grub.conf
> /boot/grub/device.map
> /etc/SuSE-release
> /var/log/grubby
>
> So based on that, no it doesn't look at /etc/default/grub.

/etc/sysconfig/grub is, at least on my system[1], a symlink to
/etc/default/grub.

[1]: Fedora 26

--
Mitchell Roe
[e-mail]

[Rick Stevens]

On 08/09/2017 07:59 AM, [e-mail] wrote:
> Rick Stevens  writes:
> > <snip>
> >
> > root@prophead ~]# strings /usr/sbin/grubby | grep "^/" | uniq
> > /lib64/ld-linux-x86-64.so.2
> > /boof
> > /dev
> > /boot/grub/menu.lst
> > /etc/grub2-efi.cfg
> > /boot/grub/grub.cfg
> > /etc/grub.d/
> > /boot/grub2/grubenv
> > /etc/mtab
> > /boot
> > /etc/sysconfig/grub
> > /proc/mdstat
> > /boot/boot.b
> > /dev/md
> > /boot/grub/stage1
> > /etc/yaboot.conf
> > /etc/elilo.conf
> > /boot/extlinux/extlinux
> > /etc/grub2.cfg
> > /boot/grub2/grub.cfg
> > /boot/grub2-efi/grub.cfg
> > /etc/grub.conf
> > /boot/extlinux/extlinux.conf
> > /etc/zipl.conf
> > /etc/silo.conf
> > /etc/lilo.conf
> > /boot/efi/EFI/redhat/elilo.conf
> > /etc/grub.conf
> > /boot/grub/device.map
> > /etc/SuSE-release
> > /var/log/grubby
> >
> > So based on that, no it doesn't look at /etc/default/grub.
>
> /etc/sysconfig/grub is, at least on my system[1], a symlink to
> /etc/default/grub.

You're right. I didn't check the symlinks. My bad.

The question still stands...does grubby actually create a new entry
based on things such as /etc/sysconfig/grub or /etc/default/grub (e.g.
by using grub2-mkconfig) or does it clone the last entry from
/boot/grub2/grub.cfg itself and switch out the kernel and such? The man
page doesn't say anything about HOW it does what it does and I don't
have the time right now to pull down the source RPM and have a looksee.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    [e-mail] -
- AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
-                                                                    -
-        Is it progress if a cannibal uses a knife and fork?         -
-                                  -- Stanislaw J. Lec               -
----------------------------------------------------------------------

[Ahmad Samir]

On 8 August 2017 at 20:59, Tom Horsley  wrote:
> On Tue, 8 Aug 2017 11:50:54 -0700
> Rick Stevens wrote:
> > Note that on your next kernel upgrade, however, the "rhgb quiet" will
> > reappear unless you edit the /etc/default/grub file and those bits from
> > the "GRUB_CMDLINE_LINUX" variable in there as well.
>
> That hasn't been my experience. The "grubby" tool seems to just copy the
> existing kernel parameters from the previous kernel in grub.cfg. I don't
> believe anyone uses /etc/default/grub or runs grub2-mkconfig (other
> than a user explicitly doing it manually). I suppose grubby might act
> different for efi?

That matches my experience on UEFI; grubby copies the kernel
parameters from the previous kernel cmdline. So I just mostly edit
/boot/efi/EFI/fedora/grub.cfg directly.

FTR, /etc/grub2-efi.cfg is a symlink to /boot/efi/EFI/fedora/grub.cfg.

[Bob Goodwin]

On 08/08/17 14:50, Rick Stevens wrote:
> So, yes, you're using UEFI to boot. All you need to do is edit the
> /boot/efi/EFI/fedora/grub.cfg file and remove the "rhgb quiet" bit and
> reboot. You should be fine.
>
> Note that on your next kernel upgrade, however, the "rhgb quiet" will
> reappear unless you edit the /etc/default/grub file and those bits from
> the "GRUB_CMDLINE_LINUX" variable in there as well.

+

Well that seems to have achieved the desired end. I'll see what happens 
after the next kernel upgrade, hopefully it will remain.

"So based on that, no it doesn't look at /etc/default/grub. However,
grub2-mkconfig does seem to consult it. I suppose you could remove it
from both /boot/efi/EFI/fedora/grub.cfg AND /etc/default/grub."

I had already done that routine on "/etc/default/grub" and rhgb quiet was already gone from that.

Anyway I rebooted and it worked as expected, the boot data shows instead of the egg and "f".

Thanks for the help.

[Rick Stevens]

On 08/08/2017 12:26 PM, Bob Goodwin wrote:
> On 08/08/17 14:50, Rick Stevens wrote:
> > So, yes, you're using UEFI to boot. All you need to do is edit the
> > /boot/efi/EFI/fedora/grub.cfg file and remove the "rhgb quiet" bit and
> > reboot. You should be fine.
> >
> > Note that on your next kernel upgrade, however, the "rhgb quiet" will
> > reappear unless you edit the /etc/default/grub file and those bits from
> > the "GRUB_CMDLINE_LINUX" variable in there as well.
>
> Well that seems to have achieved the desired end. I'll see what happens
> after the next kernel upgrade, hopefully it will remain.
>
> "So based on that, no it doesn't look at /etc/default/grub. However,
> grub2-mkconfig does seem to consult it. I suppose you could remove it
> from both /boot/efi/EFI/fedora/grub.cfg AND /etc/default/grub."
>
> I had already done that routine on "/etc/default/grub" and rhgb quiet
> was already gone from that.
>
> Anyway I rebooted and it worked as expected, the boot data shows instead
> of the egg and "f".
>
> Thanks for the help.

Glad you got it sorted out. Time will tell if that's the final fix, but
at least you have a workaround.
----------------------------------------------------------------------
- Rick Stevens, Systems Engineer, AllDigital    [e-mail] -
- AIM/Skype: therps2        ICQ: 226437340           Yahoo: origrps2 -
-                                                                    -
-  "Men occasionally stumble over the truth, but most of them pick"  -
-     themselves up and hurry off as if nothing had happened."       -
-                                  -- Winston Churchill              -
----------------------------------------------------------------------