Was just wondering about this strange behaviour when booting. GRUB starts up and shows the different boot options.
When I press keys for selection there is no response. GRUB seems to be frozen... the timeout timer (bars on the top of the screen) also does not start yet.
After 4 seconds of nothingness... the timeout counter starts and the menu is responsive.
What is GRUB waiting for or doing for these 4 seconds?
I noticed that GRUB does not freeze when I do not have the USB-C hub connected.
The hub has peripherals attached and has 2 memory card slots that could initialize as drives.
Is this what GRUB would be waiting for... since there are no memory cards in the hub, it won't find any drive to mount. Is there a way to pass through that?
Great sleuthing.
Yes, HUBs can provide such issues, due to them operating rather independently. They must be able to initialize fully at boot and provide a service, even as the system is initializing.
A four second delay is... not the worst experience you can have. That is enough time to scratch your nose or stretch. I would ignore it if you have no other issues.
I will duly ignore it...
But I do then need to figure out how to make suspend work properly... then I wiĺl probably boot only once every few days or so anyways.
The challenge may well be that the laptop not waking up from suspend (may other question thread) could also be because of the dock. I have tried a non-docked situation for a few hours and had no issues waking the laptop.
With the dock for a short time, no problem... but for a few hours, no waking.
The sheer joy of implementing a completely new OS and workflow... more work than I thought though. Tx for the help so far by the way!