Did the update it went to kernel 6.17 would not get past the logo screen

General Help
1

After a bunch of pressing finally got to the advanced option to boot to 6.14 and it worked

Modified etc/default/grub to show the menu and set the time out to five seconds. This should be default!!!!!

Told it

GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=true
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=5

then did update-grub

Now if it craps out again I get the menu each time for advanced options no smashing keys and hoping. What a PAIN this was.

And it will remember what I last booted into

This should be default.

I have a ryzen 8500g no external GPU newer HP desktop.

I also tried reinstalling 6.17 and it did not work!

My guess is there will be others.

And if the working kernel 6.14 gets removed

sudo apt install --reinstall linux-image-6.14.0-37-generic linux-modules-extra-6.14.0-37-generic
sudo update-grub

2

I will watch the updates and report back when they release the next versions with the AMD fixes.

3

I really agree with you.

I think the reason that it is not is due to user push for the "Fastest possible boot."
One thing often asked on the forum is how to speed up boot. People do not want to wait forty seconds for the machine to fully initialize.

So, Grub Menu is one thing easy to shave a few seconds off of it.

4

with todays new update 6.17.0-14 is now the new one for all in Zorin OS 18

5

Something to do with AMD 8500g type APU. 6.17 and 6.18 have this bug however 6.19 has it fixed.

Pretty serious bug considering how hard it was to get the darn advanced menu to finally pop up to select older kernel. Told apt to hold 6.14 so it does not go away until 6.19 arrives. Normal user will not know about all this stuff

1 Like
6

I had that, too. When the Kernel was installed and I had to reboot, it hangs on the pulsing Z-Symbol. I pressed the Power Button to turn off my Machine and waited a couple Seconds.Then, I turned the Machine on and it started fine.

7

Nothing is wrong, but I want to be proactive.
Right now my GRUB shows this at the top:

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=hidden
GRUB_TIMEOUT=10
GRUB_DISTRIBUTOR=( . /etc/os-release; echo ${NAME:-Ubuntu} ) 2>/dev/null || echo Ubuntu
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""

I want to change it but don't want to bork it by doing so. (Have backed it up).

Should I choose what Perplexity.ai suggests:

GRUB_DEFAULT=0
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=30
GRUB_TIMEOUT_PURGE=0 # Optional: Shows menu even if just a single OS

Or would I be better off copying vonwallace and choosing this:

GRUB_DEFAULT=saved
GRUB_SAVEDEFAULT=true
GRUB_TIMEOUT_STYLE=menu
GRUB_TIMEOUT=5

8

This can help because on Zorin OS, it will default to a higher priority to hide the drub menu if not a dual boot, even if you set your grub file to menu.

This is number of seconds so - I recommend higher than three seconds - it can be however much time you think you will need.
If you are slower than a turtle swimming in molasses while sleepy, thirty seconds is fine.

1 Like
9

This is why I like distributions like PCLOS Debian and Q4OS - GRUB is always shown and timeout is set to 5 seconds default.

I have mentioned elsewhere, Ext4 FS is a journalling system like NTFS. Reducing timeout below 5 seconds can lead to a non-bootable OS. When I was an IT Contractor working for a local government provider I was told by their NT guru that one local government director had a naughty habit of changing NT4 workstation timeouts from 10 seconds to zero.

10

The Grub Menu timeout is in relation to the time interval before proceeding to boot and can be safely set below 5 - or to 0 without any risk of a non-bootable OS.

In journaling filesystems, a Commit timeout that is set below 5 seconds can lead to a non-bootable OS, since journals may not have time to clear.
But that is a Commit-x timeout, not the grub menu timeout.

1 Like
11

My bad!

12

Another Option for the Time would be -1 (in Combination with the menu Value). Then the GRUB Menu would stay until a User makes something.

3 Likes