People,
In the olden days I used to just edit the grub conf file and delete these args manually - now I am supposed to use grubby but doing this:
grubby --update-kernel=ALL --remove-args="quiet" grubby --update-kernel=ALL --remove-args="rhgb"
does not make any difference to the boot information I see before the graphical login . .
What am I missing?
Thanks,
Phil.
On 13.03.20 17:10, Philip Rhoades wrote:
People,
In the olden days I used to just edit the grub conf file and delete these args manually - now I am supposed to use grubby but doing this:
grubby --update-kernel=ALL --remove-args="quiet" grubby --update-kernel=ALL --remove-args="rhgb"
does not make any difference to the boot information I see before the graphical login . .
What am I missing?
I do:
- sudo vi /etc/default/grub - remove quiet rhgb - and run:
[ -d /sys/firmware/efi/efivars ] && sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg || sudo grub2-mkconfig -o /boot/grub2/grub.cfg
- last line is ONE line -
On 2020-03-14 03:21, sixpack13 wrote:
On 13.03.20 17:10, Philip Rhoades wrote:
People,
In the olden days I used to just edit the grub conf file and delete these args manually - now I am supposed to use grubby but doing this:
grubby --update-kernel=ALL --remove-args="quiet" grubby --update-kernel=ALL --remove-args="rhgb"
does not make any difference to the boot information I see before the graphical login . .
What am I missing?
I do:
- sudo vi /etc/default/grub
- remove quiet rhgb
- and run:
[ -d /sys/firmware/efi/efivars ] && sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg || sudo grub2-mkconfig -o /boot/grub2/grub.cfg
- last line is ONE line -
Did that but I still don't get the verbose boot . .
Thanks,
Phil.
On 13.03.20 23:03, Tom Horsley wrote:
On Sat, 14 Mar 2020 08:59:12 +1100 Philip Rhoades wrote:
Did that but I still don't get the verbose boot . .
Sounds an awful lot like you're booting something different than you think you're booting. That's the only idea I have left.
... +1
On 13.03.20 22:59, Philip Rhoades wrote: ...
[ -d /sys/firmware/efi/efivars ] && sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg || sudo grub2-mkconfig -o /boot/grub2/grub.cfg
...
Did that but I still don't get the verbose boot . .
then check after an addional run of the above "...grub2-mkconfig..."- command if the boot files have changed => new date/time:
sudo -s
and then
ll /boot/grub2/grub*
=> rw-rw-r--. 1 root root 6,4K 14. Mär 00:34 /boot/grub2/grub.cfg -rw-------. 1 root root 1,0K 14. Mär 00:34 /boot/grub2/grubenv
^^^^^^^^^^^^^^ ||
sixpack13, Tom,
On 2020-03-14 10:48, sixpack13 wrote:
On 13.03.20 22:59, Philip Rhoades wrote: ...
[ -d /sys/firmware/efi/efivars ] && sudo grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg || sudo grub2-mkconfig -o /boot/grub2/grub.cfg
...
Did that but I still don't get the verbose boot . .
then check after an addional run of the above "...grub2-mkconfig..."- command if the boot files have changed => new date/time:
sudo -s
and then
ll /boot/grub2/grub*
=> rw-rw-r--. 1 root root 6,4K 14. Mär 00:34 /boot/grub2/grub.cfg -rw-------. 1 root root 1,0K 14. Mär 00:34 /boot/grub2/grubenv
# cat /etc/default/grub GRUB_TIMEOUT=5 GRUB_DISTRIBUTOR="$(sed 's, release .*$,,g' /etc/system-release)" GRUB_DEFAULT=saved GRUB_DISABLE_SUBMENU=true GRUB_TERMINAL_OUTPUT="console" GRUB_CMDLINE_LINUX="resume=UUID=d98a1bbc-fdaf-484c-9dc9-2f5fd062077d" GRUB_DISABLE_RECOVERY="true" GRUB_ENABLE_BLSCFG=true
Current:
# find /boot -type f -mtime -10 -exec ls -al {} ; -rw-rw-r--. 1 root root 5709 Mar 14 08:46 /boot/grub2/grub.cfg -rw-r--r-- 1 root root 329 Mar 14 02:23 /boot/loader/entries/975d47e2dde64d12aefee7b93f8cdc77-0-rescue.conf -rw-r--r-- 1 root root 392 Mar 14 02:23 /boot/loader/entries/975d47e2dde64d12aefee7b93f8cdc77-5.3.7-301.fc31.x86_64.conf -rw-rw-r--. 1 root root 1024 Mar 14 20:28 /boot/efi/EFI/fedora/grubenv -rw-r--r-- 1 root root 5709 Mar 14 08:40 /boot/efi/EFI/fedora/grub.cfg.org
# [ -d /sys/firmware/efi/efivars ] && grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg || grub2-mkconfig -o /boot/grub2/grub.cfg Generating grub configuration file ... grub2-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map. grub2-probe: error: cannot find a GRUB drive for /dev/sdb3. Check your device.map. done
# find /boot -type f -mtime -10 -exec ls -al {} ; -rw-rw-r--. 1 root root 5709 Mar 14 22:14 /boot/grub2/grub.cfg -rw-r--r-- 1 root root 329 Mar 14 02:23 /boot/loader/entries/975d47e2dde64d12aefee7b93f8cdc77-0-rescue.conf -rw-r--r-- 1 root root 392 Mar 14 02:23 /boot/loader/entries/975d47e2dde64d12aefee7b93f8cdc77-5.3.7-301.fc31.x86_64.conf -rw-rw-r--. 1 root root 1024 Mar 14 22:14 /boot/efi/EFI/fedora/grubenv -rw-r--r-- 1 root root 5709 Mar 14 08:40 /boot/efi/EFI/fedora/grub.cfg.org
=> reboot
Odd thing: the grub menu font looks about double size . .
"Probing EDD . . ." - also in double size font
"Probing EDD . . ." - then changes to normal size font
but still not other text on the screen till the F31 login prompt . .
Thanks,
Phil.
Hi
On Sat, 14 Mar 2020 22:23:41 +1100 Philip Rhoades wrote:
# cat /etc/default/grub
...
GRUB_CMDLINE_LINUX="resume=UUID=d98a1bbc-fdaf-484c-9dc9-2f5fd062077d"
...
GRUB_ENABLE_BLSCFG=true
With this, grub2-mkconfig will generate in /boot/grub2/grub.cfg (your previous trace shows that your machine is not using EFI):
### BEGIN /etc/grub.d/10_linux ### ... # The blscfg command parses the BootLoaderSpec files stored in # /boot/loader/entries and populates the boot menu. Please refer to # the Boot Loader Specification documentation for the files format: # https://www.freedesktop.org/wiki/Specifications/BootLoaderSpec/.
set default_kernelopts="root=UUID=XXX YYY"
insmod blscfg blscfg ### END /etc/grub.d/10_linux ###
Where XXX is the UUID of the rppt filesystem, and YYY is deduced from GRUB_CMDLINE_LINUX present in /etc/default/grub Ex:
set default_kernelopts="root=UUID=509e4d95-a5f5-40e6-94e9-8bbff77f32cd resume=/dev/disk/by-uuid/d16bbc09-698b-4e97-9aa0-c37328b36422 "
then, in my case, the /boot/loader/entries/* files only use the default_kernelopts
Ex:
title Fedora (5.5.6-201.fc31.x86_64) 31 (Thirty One) version 5.5.6-201.fc31.x86_64 linux /boot/vmlinuz-5.5.6-201.fc31.x86_64 initrd /boot/initramfs-5.5.6-201.fc31.x86_64.img options $kernelopts grub_users $grub_users grub_arg --unrestricted grub_class kernel
Check if those files differ from mine, ex: set options differently.
# [ -d /sys/firmware/efi/efivars ] && grub2-mkconfig -o /boot/efi/EFI/fedora/grub.cfg || grub2-mkconfig -o /boot/grub2/grub.cfg
Generating grub configuration file ...
grub2-probe: error: cannot find a GRUB drive for /dev/sdb1. Check your device.map. grub2-probe: error: cannot find a GRUB drive for /dev/sdb3. Check your device.map. done
Have you checked /boot/grub2/device.map ?
On Sat, 14 Mar 2020 22:23:41 +1100 Philip Rhoades phil@pricom.com.au wrote:
GRUB_CMDLINE_LINUX="resume=UUID=d98a1bbc-fdaf-484c-9dc9-2f5fd062077d"
Are you really trying to resume instead of booting from the installed system?
As Francis already said, you are still booting using legacy grub, so your grub.cfg will be in /boot/grub2/ as grub.cfg. Maybe you could show the boot stanza from that file here?
If you want to boot from the grub.cfg you should comment out the above GRUB_CMDLINE_LINUX and replace it with the one from the most recent entry in the /boot/grub2/grub.cfg file. Then rerun the grub2-mkconfig -o grub.cfg file in the /boot/grub2 directory.
Odd thing: the grub menu font looks about double size . .
"Probing EDD . . ." - also in double size font
"Probing EDD . . ." - then changes to normal size font
but still not other text on the screen till the F31 login prompt . .
I think this is because of the resume from hibernate.
On Sat, 14 Mar 2020 11:33:00 -0700 stan via users wrote:
On Sat, 14 Mar 2020 22:23:41 +1100 Philip Rhoades phil@pricom.com.au wrote:
GRUB_CMDLINE_LINUX="resume=UUID=d98a1bbc-fdaf-484c-9dc9-2f5fd062077d"
Are you really trying to resume instead of booting from the installed system?
As far as I know this resume option is only used when resuming: it doesn't affect normal boot. The UUID should be the one of the swap partition.
As Francis already said, you are still booting using legacy grub, so your grub.cfg will be in /boot/grub2/ as grub.cfg. Maybe you could show the boot stanza from that file here?
I think the stanza will be instead in /boot/loader/entries/* except perhaps if the machine is multi-boot and then grub2-mkconfig generates legacy menu entries in the /etc/grub.d/30_os-prober section
If you want to boot from the grub.cfg you should comment out the above GRUB_CMDLINE_LINUX and replace it with the one from the most recent entry in the /boot/grub2/grub.cfg file. Then rerun the grub2-mkconfig -o grub.cfg file in the /boot/grub2 directory.
I don't think this is needed.
On Sat, 14 Mar 2020 03:10:04 +1100 Philip Rhoades wrote:
In the olden days I used to just edit the grub conf file and delete these args manually - now I am supposed to use grubby but doing this:
You're on olden days 2. Now you need to use grub2-editenv to edit the kernelopts variable that appears in grubenv:
[root@tomh boot]# grub2-editenv list saved_entry=978f7d029ece40bdb521840cbd5473a1-5.5.8-200.fc31.x86_64 menu_auto_hide=1 boot_success=1 kernelopts=root=UUID=cd806f62-fc1c-4d65-8a9e-ea638915001b ro selinux=0 audit=0 rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 boot_indeterminate=0
At least if you have the default new booting stuff who's name I don't remember.
On 2020-03-14 05:12, Tom Horsley wrote:
On Sat, 14 Mar 2020 03:10:04 +1100 Philip Rhoades wrote:
In the olden days I used to just edit the grub conf file and delete these args manually - now I am supposed to use grubby but doing this:
You're on olden days 2. Now you need to use grub2-editenv to edit the kernelopts variable that appears in grubenv:
[root@tomh boot]# grub2-editenv list saved_entry=978f7d029ece40bdb521840cbd5473a1-5.5.8-200.fc31.x86_64 menu_auto_hide=1 boot_success=1 kernelopts=root=UUID=cd806f62-fc1c-4d65-8a9e-ea638915001b ro selinux=0 audit=0 rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 boot_indeterminate=0
I get:
# grub2-editenv list saved_entry=975d47e2dde64d12aefee7b93f8cdc77-5.3.7-301.fc31.x86_64 kernelopts=root=UUID=e83e6521-3be4-4c4a-a012-89805709db3f ro resume=UUID=d98a1bbc-fdaf-484c-9dc9-2f5fd062077d boot_success=0 boot_indeterminate=0
- so the args are already removed but I still don't get the verbose boot . .
Thanks,
Phil.
On Sat, 2020-03-14 at 08:55 +1100, Philip Rhoades wrote:
On 2020-03-14 05:12, Tom Horsley wrote:
On Sat, 14 Mar 2020 03:10:04 +1100 Philip Rhoades wrote:
In the olden days I used to just edit the grub conf file and delete these args manually - now I am supposed to use grubby but doing this:
You're on olden days 2. Now you need to use grub2-editenv to edit the kernelopts variable that appears in grubenv:
[root@tomh boot]# grub2-editenv list saved_entry=978f7d029ece40bdb521840cbd5473a1-5.5.8-200.fc31.x86_64 menu_auto_hide=1 boot_success=1 kernelopts=root=UUID=cd806f62-fc1c-4d65-8a9e-ea638915001b ro selinux=0 audit=0 rd.driver.blacklist=nouveau modprobe.blacklist=nouveau nvidia-drm.modeset=1 boot_indeterminate=0
I get:
# grub2-editenv list saved_entry=975d47e2dde64d12aefee7b93f8cdc77-5.3.7-301.fc31.x86_64 kernelopts=root=UUID=e83e6521-3be4-4c4a-a012-89805709db3f ro resume=UUID=d98a1bbc-fdaf-484c-9dc9-2f5fd062077d boot_success=0 boot_indeterminate=0
- so the args are already removed but I still don't get the verbose boot
. .
I'm just wondering why your output says 'boot_success=0', surely that should be a '1'.
You could also run 'cat /proc/cmdline' to see what has actually been passed to the running kernel.
Final point is that your kernel version (5.3.7) seems to be somewhat older than the other one mentioned above (5.5.8 - although I'm on 5.5.11 at this very moment). Perhaps doing an update and then a reboot may help.
John.
-- John Horne | Senior Operations Analyst | Technology and Information Services University of Plymouth | Drake Circus | Plymouth | Devon | PL4 8AA | UK ________________________________ [http://www.plymouth.ac.uk/images/email_footer.gif]http://www.plymouth.ac.uk/worldclass
This email and any files with it are confidential and intended solely for the use of the recipient to whom it is addressed. If you are not the intended recipient then copying, distribution or other use of the information contained is strictly prohibited and you should not rely on it. If you have received this email in error please let the sender know immediately and delete it from your system(s). Internet emails are not necessarily secure. While we take every care, University of Plymouth accepts no responsibility for viruses and it is your responsibility to scan emails and their attachments. University of Plymouth does not accept responsibility for any changes made after it was sent. Nothing in this email or its attachments constitutes an order for goods or services unless accompanied by an official order form.
On Sat, 14 Mar 2020 03:10:04 +1100 Philip Rhoades phil@pricom.com.au wrote:
People,
In the olden days I used to just edit the grub conf file and delete these args manually - now I am supposed to use grubby but doing this:
grubby --update-kernel=ALL --remove-args="quiet" grubby --update-kernel=ALL --remove-args="rhgb"
does not make any difference to the boot information I see before the graphical login . .
What am I missing?
I think you just want to edit /etc/default/grub and remove them from the default kernel arguments. Maybe copy the line and comment the old one before changing. You could add a timeout so the menu is visible for a short time, GRUB_TIMEOUT=10
Then go to where the grub cfg file is, /boot/grub2 for non uefi /boot/efi/EFI/fedora for uefi and run grub2-mkconfig -o grub.cfg
Alternatively, you can keep hitting space bar during boot, and when the menu comes up, edit the kernel boot line to remove them. But this will have to be done each time you boot. Good for one time checks.
On 2020-03-14 05:13, stan wrote:
On Sat, 14 Mar 2020 03:10:04 +1100 Philip Rhoades phil@pricom.com.au wrote:
People,
In the olden days I used to just edit the grub conf file and delete these args manually - now I am supposed to use grubby but doing this:
grubby --update-kernel=ALL --remove-args="quiet" grubby --update-kernel=ALL --remove-args="rhgb"
does not make any difference to the boot information I see before the graphical login . .
What am I missing?
I think you just want to edit /etc/default/grub and remove them from the default kernel arguments. Maybe copy the line and comment the old one before changing. You could add a timeout so the menu is visible for a short time, GRUB_TIMEOUT=10
Then go to where the grub cfg file is, /boot/grub2 for non uefi /boot/efi/EFI/fedora for uefi and run grub2-mkconfig -o grub.cfg
Did that - but I still don't get the verbose boot . .
Alternatively, you can keep hitting space bar during boot, and when the menu comes up, edit the kernel boot line to remove them. But this will have to be done each time you boot. Good for one time checks.
Yes, I do that occasionally but this is for a machine that has a "null" keyboard attached (I usually only ssh to it).
Thanks,
Phil.
-
Francis.Montagnac＠inria.fr -
John Horne -
Philip Rhoades -
sixpack13 -
stan -
Tom Horsley