Description of problem: After the installation of minimal mode, some extra imformation like "ALSA sound ..." displays on the login screen, as the attachment shows. Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Created attachment 795478 [details] screen shot
This is not an anaconda problem, this is inside the installed system. I believe you're seeing kernel messages on tty1, which is somewhat expected? I'm not sure if they should be displayed while login screen is active, but it's certainly not a new problem, it has ever been this way. Changing component to util-linux, since it contains agetty. Can you give us some advice here? Should the kernel messages be blocked? Is this expected and wanted? Thanks.
Sounds like strange console-level setting for kernel messages. Try: $ cat /proc/sys/kernel/printk 4 4 1 7 The first number in the output is the console log level, the second is the default log level, third is the minimum log level and fourth is the maximum log level. See also dmesg --console-level level dmesg --console-on dmesg --console-off for more details. Anyway, I don't think this is util-linux issue, seems like kernel/init or your local misconfiguration.
Can observe this as well in up-to-date Rawhide installation (util-linux-2.30-1.fc27.x86_64, kernel 4.12.0-0.rc5.git2.1.fc27.x86_64). In my case, message like following is frequently emitted on the screen (in the same manner as demonstrated above) just about the time the login screen is reached during the boot process: mei_wdt: probe of mei::05b79a6f-4628-4d7f-899d-a91514cb32ab:02 failed with error -22 $ cat /proc/sys/kernel/printk > 4 4 1 7 Reopening for discussion. Is this expected?
This bug appears to have been reported against 'rawhide' during the Fedora 27 development cycle. Changing version to '27'.
I don't see a way how to fix this by login/agetty. Closing. (Please, if you want to reopen than against kernel or systemd.)
It's OK; to be honest, I haven't observed that for a while with this continually upgraded Rawhide installation (could be a matter of some kernel/dracut/systemd adjustments, more careful timing/waiting or whatnot).