Bugzilla – Bug 1202605
Unnecessary/excessive messages are displayed during boot (even with silent/quiet grub kernel parameters)
Last modified: 2022-09-19 13:53:43 UTC
(I don't know if this goes into bootloader or base system/systemd). THE PROBLEM: Tumbleweed shows me a "dirty" boot process instead of the clean/next gen looking quiet boot shown by other distributions (Fedora, Manjaro,...) and Windows. It displays these messages found in dmesg: > [0.085254] x86/cpu: SGX disabled by BIOS. > [0.358421] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs ed40080 f80 >[0.358433] tpm_crb MSFT0101:00: [Firmware Bug]: ACPI region does not cover the entire command/response buffer. [mem 0xfed40000-0xfed4087f flags 0x200] vs ed40080 f80 Searching I found out that: 1. SGX is the onboard CPU graphics I have manually disabled in the bios. 2. ACPI tpm is a firmware bug found on some motherboards that will never be fixed. (my motherboard is a 2016 z170 chip-set ASUS that doesn't get any fixes anymore. Searching the web I have seen that other brands and boards have the same problem). I was using Fedora 36 up to 3 weeks ago when I switched to Tumbleweed. I NEVER had this problem before. Fedora is a CLEAN good looking next gen boot (that only shows errors like failing to mount a device, missing modules, etc...). The same goes for Manjaro, Windows 7/8/10/11, etc... I have the install default in /etc/default(grub): > GRUB_CMDLINE_LINUX_DEFAULT="splash=silent quiet" CONCLUSION: I have disabled the onboard GPU manually. I don't need to be reminded of this every boot. The same goes for the ACPI firmware bug. 1. I understand the purpose of this information, as I never even new about this firmware bug. But it isn't needed every boot.) 2. Can't you just add a button somewhere to acknowledge the information with a toggle to prevent it from being displayed again in the future (like the opensuse welcome screen after install. There's a toggle to not show it again). If not possible, then just disable these excessive unnecessary information like the other distros/OSes do. -> How to make Opensuse clean looking, like the other OSes/distributions ? Thanks.
That's before plymouth takes over and 'quiet' hides only *most* kernel messages. I don't know if you can make the kernel even 'quieter' in a sensible way. Assigning to kernel developers to have a look.
SGX has nothing to do with graphics. I guess this message can be downgraded from KERN_ERR to KERN_INFO; then it won't appear on the boot screen. Boris? (And, the remaining errors from tpm_crb look like a real error of the firmware, and you should blame rather the hardware vendor; other distros may not hit the problem because of difference of kernel config, the module loading order or whatever reason, but it's a bug in the firmware, after all.)
(In reply to Takashi Iwai from comment #2) > SGX has nothing to do with graphics. I guess this message can be downgraded > from KERN_ERR to KERN_INFO; then it won't appear on the boot screen. > > Boris? Yeah, you had already asked me about it in some other bug and I said yes and that patches are welcome. :-)
You can probably set loglevel to critical and then you won't see mere errors. As t the SGX error - we have some KVM functionality enabled in the kernel config that cannot be used because a CPU feature is disabled by BIOS. That sounds like something users generally might want to know about when building custom kernels, less so when using a generic distribution kernel.
(In reply to Borislav Petkov from comment #3) > (In reply to Takashi Iwai from comment #2) > > SGX has nothing to do with graphics. I guess this message can be downgraded > > from KERN_ERR to KERN_INFO; then it won't appear on the boot screen. > > > > Boris? > > Yeah, you had already asked me about it in some other bug and I said yes and > that patches are welcome. :-) OK, will try to submit later. (In reply to Michal Suchanek from comment #4) > You can probably set loglevel to critical and then you won't see mere errors. Right, e.g. passing "loglevel=2" boot option should suppress the all non-critical error messages. But it also hides the real errors as its side-effect, of course.