Was looking through the boot log and encountered this, which I haven’t noticed before. Is this a bug? Is anyone else seeing this?
Kernel command line: BOOT_IMAGE=(hd5,gpt2)/vmlinuz-6.3.6-200.fc38.x86_64 root=UUID=365d160f-bac9-4a1c-9ee5-7be7b4f7207d ro rhgb quiet
Unknown kernel command line parameters “rhgb BOOT_IMAGE=(hd5,gpt2)/vmlinuz-6.3.6-200.fc38.x86_64”, will be passed to user space
It is common to add stuff to the kernel command line that is used to change how early boot works.
I’d assume that you will find BOOT_IMAGE being used in initrd, but have not checked.
The “rhgb” is the signal to initrd to use RedHat Graphical Boot. aka use plymouth to show the friendly splash screen.
So… you’re saying this is a hack? In other words, the kernel complains what is being entered is unrecognized and ignores it, but the entered parameters are intended for other processes and were just thrown into kernel command line because it was more convenient at the time? If that’s the case it kind of defeats the purpose of error messages and makes analysis more confusing because some error messages are meaningless,
Messages are not always error messages. They can be warning messages or just information messages. If you run journakctl -k -p err you get just the error messages, and with journalctl -k -p warning you get the error and warning messages. That kernel command line parameters are just passed on to user space has always been the case, whether you get a message about it or not.
Good to know. Thanks for the clarification. Yeah, the log is rather chatty, using those commands you mentioned is very helpful.