An optional console view of the kernel boot log and driver configuration stages Etc. all the stuff that you have to find out after the fact by retrieving a log through one of the alternate boot methods like the recovery console. Assuming you can even get to one of those.
Why can't this just be something you can tab over to instead of that stupid blank startup screen with occasional disingenuous, ambiguous feel-good messages on it? Why do Windows crash dump and recovery screens have to be still largely stuck in the cryptic and unhelpfully threadbare state they were in 20 years ago when there is so much more memory available to store say, a scrollable stack trace or even a large text table of meaningful errors or exception states so you don't need to go Googling around for these or checking your notes at 4:08 am on a Monday?
The bane of anyone who's ever had to get a production system back up and running from a non-bootable state and you're sitting there staring at spinning circles and featureless colorblock screens sometimes for minutes on end, wondering just what the hell is going on.
Why can't this just be something you can tab over to instead of that stupid blank startup screen with occasional disingenuous, ambiguous feel-good messages on it? Why do Windows crash dump and recovery screens have to be still largely stuck in the cryptic and unhelpfully threadbare state they were in 20 years ago when there is so much more memory available to store say, a scrollable stack trace or even a large text table of meaningful errors or exception states so you don't need to go Googling around for these or checking your notes at 4:08 am on a Monday?
The bane of anyone who's ever had to get a production system back up and running from a non-bootable state and you're sitting there staring at spinning circles and featureless colorblock screens sometimes for minutes on end, wondering just what the hell is going on.