"Progress report" on single OS

[anneranch]

On multiboot system I can option grub to enable " progress report - log " ( no flash) - so during boot I get ton of messages (log) on the monitor giving a reasonable indication what is happening during boot.
Is there a way to option SINGLE OS to do the same - assuming "grub" is really not used in single OS ( I may be wrong on that assumption ...)

 

[wizardfromoz]

If you copy and paste the content of your file

/etc/default/grub

here, you can paste it into the reply window, then select it/highlight and choose List - Ordered List from the toolbar to have the lines numbered such as I have done below, from one of my Linux Mints.

1. # If you change this file, run 'sudo update-grub' afterwards to update
2. # /boot/grub/grub.cfg.
3. # For full documentation of the options in this file, see:
4. # info -f grub -n 'Simple configuration'
5. 
   
6. GRUB_DEFAULT=saved
7. GRUB_TIMEOUT_STYLE=hidden
8. GRUB_TIMEOUT=10
9. GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
10. GRUB_CMDLINE_LINUX_DEFAULT="noquiet nosplash"
11. GRUB_CMDLINE_LINUX=""
12. 
    
13. # Uncomment to enable BadRAM filtering, modify to suit your needs
14. # This works with Linux (no patch required) and with any kernel that obtains
15. # the memory map information from GRUB (GNU Mach, kernel of FreeBSD ...)
16. #GRUB_BADRAM="0x01234567,0xfefefefe,0x89abcdef,0xefefefef"
17. 
    
18. # Uncomment to disable graphical terminal (grub-pc only)
19. #GRUB_TERMINAL=console
20. 
    
21. # The resolution used on graphical terminal
22. # note that you can use only modes which your graphic card supports via VBE
23. # you can see them in real GRUB with the command `vbeinfo'
24. # CRAP Obsolete! use videoinfo
25. #GRUB_GFXMODE=640x480
26. 
    
27. # Uncomment if you don't want GRUB to pass "root=UUID=xxx" parameter to Linux
28. #GRUB_DISABLE_LINUX_UUID=true
29. 
    
30. # Uncomment to disable generation of recovery mode menu entries
31. #GRUB_DISABLE_RECOVERY="true"
32. 
    
33. # Uncomment to get a beep at grub start
34. #GRUB_INIT_TUNE="480 440 1"
35. 
    
36. GRUB_BACKGROUND="/home/chris/Pictures/tessa_tgrimbert_santorini.png"
37. 
    
38. GRUB_SAVEDEFAULT=true

I can then easily show you what line/s to modify to what to effect the change.

Cheers

Wizard

 

[anneranch]

OK, I have two issues

1. I am not suppose to edit /boot/grub/grub.cfg
2. I am trying to help a fellow to find out why his Raspberry won't boot AFTER USB plug was apparently destroyed / shorted - he does not really know what caused the failure.

I am not sure if he is capable or wants to get into OS
and if it does not boot he cannot get into OS anyway.

He can verify that both SD memory and USB boot works on another RPi.

He gets power LED on , but no boot , hence no green LED.

I was hoping he can use similar "progress report" as I am getting running grub on my mutiboot system and somehow identify why his RPi , with ONE busted USB plug, won't boot.

Thanks for your help.

PS I did try to clean up my grub to get "next time boot to last saved "- it did not work and it is not my high priority for now . Sorry for no response.


#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#

### BEGIN /etc/grub.d/00_header ###
if [ -s $prefix/grubenv ]; then
set have_grubenv=true
load_env
fi
if [ "${initrdfail}" = 2 ]; then
set initrdfail=
elif [ "${initrdfail}" = 1 ]; then
set next_entry="${prev_entry}"
set prev_entry=
save_env prev_entry
if [ "${next_entry}" ]; then
set initrdfail=2
fi
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="${saved_entry}"
fi

if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi

export menuentry_id_option

if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi

function savedefault {

^G Help ^O Write Out ^W Where Is ^K Cut

 

[wizardfromoz]

1. I am not suppose to edit /boot/grub/grub.cfg

That is correct, it is like a System file under Windows. Also any changes will not be persistent unless you know what you are doing. When the next update to grub occurs (usually about monthly) the changes will be lost.

Even I do not monkey with grub.cfg, and I have 11 years experience and run 67 Linux.

You haven't said what Distro your friend is running on the Pi, but with every Linux I have used, there is usually a reference (Line 10 in my response at #22 above) where it features the words

quiet

and

splash

If you modify that, in /etc/default/grub, to read

noquiet nosplash

that will replace the usual graphical entry with a spooling of output on what is being loaded and run at startup.

Be sure you run

sudo update-grub

after editing /etc/default/grub

If the distro in use is other than a Debian-based distro or Manjaro, the syntax for updating is different, and may look something like

sudo grub-mkconfig -o /boot/grub/grub.cfg

so telling us the Distro would be useful.

I have no comprehensive knowledge of Pi's, so if there are problems which are intrinsic and exclusive to the Pi environment, then this Thread may be better relocated to Single Board Computers, if that occurs, let me know and I can relocate it.

Cheers

Wizard