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...
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.