Boot errors with QUIET ?

[ACRizona]

Boot parameter QUIET hids everything up to (((( read really fast )))) Busy-Box,,,, Route something... Some program text... more Busy-Box,,, Something Route...
And then boot continues... without further ado.
What the H---
Isn't this recorded in a boot.log somewhere ?   
   

[Juanito]

use the boot code "syslog" and then look at /var/log/messages or use dmesg

[curaga]

Use "pause" to be able to read them.

[ACRizona]

Anon quote:  It's often tricky to freeze them and you may need to hit Ctrl-Alt-Del while Linux is booting to start rebooting and try again. What these messages display may change as booting progresses and it's often tricky to freeze it at exactly the right words. 
I finally gave up on the "pause" key, when the battery went dead. 

I replaced boot option QUIET with SYSLOG.  I  find "route" in var/log/messages but there are no obvious messages.    Maybe you have a look-see ?

FYI: I un-plugged the wlan card for testing this problem.

[tinypoodle]

FYI: I un-plugged the wlan card for testing this problem.

Define: "this problem"
Just that you get some output when using boot param 'quiet', or anything else?

quiet      [KNL] Disable most log messages

[curaga]

Sorry, I meant the bootcode pause. "tinycore pause".