Description of problem: After install from Classical i586 media on two very different sets of real hardware, first and subsequent boots show a display of scrolling text between Grub and Log in screens, rather than the expected bubbling cauldron graphical sequence. It's as if "Esc" on the keyboard had been pressed. Version-Release number of selected component (if applicable): April 8, 2015 build of the i586 Classical DVD for Mageia 5 RC. Previous builds did not exhibit this. How reproducible: Always Steps to Reproduce: 1. Install from Classical media 2. Boot 3. Reproducible: Steps to Reproduce:
Still present in April 9 build of iso. Also observed scrolling text during shutdown.
I've been experiencing this bug since we switched to kernel 3.19 in Cauldron, but at first I thought it was hardware-dependent since I was the only one complaining about it. Now I guess I was the only one seeing it because I had forced the regeneration of my initrd to take plymouth properly into account, and some recent changes in this regard might have triggered this bug on a wider scale. Thomas, Colin, any idea about this issue? Basically (on my cauldron at least), plymouth's splash screen starts properly, but disappears after a couple of seconds and then shows the boot log instead (starting around the filesystem checks).
Priority: Normal => release_blockerCC: (none) => mageia, rverschelde, tmb
Created attachment 6236 [details] SVG plot by systemd-analyze On this plot the plymouth-start service seems to be running for ~2,5 s, that could correspond to the duration of the splash animation before it drops to the text log.
CC: (none) => yves.brungard_mageia
*** Bug 15657 has been marked as a duplicate of this bug. ***
CC: (none) => paiiou
Same issue here on my Cauldron x86_64 and KDE.
CC: (none) => geiger.david68210
On both of my machines, I get a brief blank screen after Mageia 5 is selected, and then it's right into the text. I don't see anything of the splash, or if I do it's too brief to spot. My hardware: Dell Dimension E310 desktop with 3.0MHz P4 processor, onboard graphics, Viewsonic VA912b monitor, connected with the analog cable.(No digital port on computer) (During the blank period, this monitor indicates twice that it's not getting a signal from the computer.) Home made desktop computer with Fujitsu D1711 motherboard, Sempron 3100+ processor, GeForce 6200OC AGP video card, using the digital cable to an AOC e2351F monitor. (I don't remember if this one indicated the same no-signal condition) Also, not seeing this after an install from the i586 KDE LiveDVD, on either machine.
Just checked, and I'm NOT seeing the "no signal" indicator on the AOC monitor. However, IMO this is most likely just because it is less sensitive to such things than the Viewsonic monitor.
CC: (none) => eeeemail
Valid latest RC isos (15th april)
Created attachment 6298 [details] journal.txt from a gnome 32 install
Created attachment 6299 [details] kdejournal.txt Attaching journal from a classic 32 kde install No sign of plymouth at all, text is displayed from very early in the boot process, before switching root.
Created attachment 6300 [details] plymouth-debug.log Found plymouth can produce debugging info with plymouth:debug kernel option. It drops plymouth-debug.log in /var/log (attached)
Seems to look for tty0 and fall back to stdio on tty1 initialize_environment:source built on Oct 17 2014 initialize_environment:checking if '/dev/tty1' exists check_for_consoles:checking for consoles add_consoles_from_file:opening /sys/class/tty/console/active add_consoles_from_file:reading file add_consoles_from_file:console /dev/tty0 found! check_for_consoles:After processing serial consoles there are now 0 text displays redirect_standard_io_to_device:redirecting stdio to /dev/tty1
In running system.. # cat /sys/class/tty/console/active tty0
Also valid after a 64-bit install from the DualDVD of April 15.
I pushed some fixes in plymouth-0.8.6.1-13.mga5 does it help anything ?
No change here, in a 64-bit install from the DualDVD, or in a 32-bit KDE install from the Classical i586 DVD.
Sorry, I forgot to state one thing.... you need to recreate initrd too in order to pick up the changes, so when you are running an affected system, open a terminal window, su - to root and do "dracut -f" that should regenerate initrd for running system
(In reply to Thomas Backlund from comment #15) > I pushed some fixes in plymouth-0.8.6.1-13.mga5 > > does it help anything ? Tried the new plymouth, run dracut -f no success :( Thomas, do you need some more info. I have not updated other things. Papoteur
Created attachment 6309 [details] Output in Konsole as dracut -f is executed
Tried "dracut -f" on i586 system, no joy. Several messages as dracut executed about things not done because the commands couldn't be found. File attached. System is "stock" KDE install with packages selected by the installer, tainted repositories activated, all updates performed, including latest kernel.
The dracut output is fine Thomas, it's just that it checks for every possible module, and it's method to know if the module exist is to check for the corresponding commands it seems. So the "command not found" message just mean that you are not using those modules.
OK, Remi. (Forgive the misspelling. American keyboard) To those of us among The Great Unwashed, it looked like something that ought to be checked.
I've just seen the same thing with 64-bit UEFI Live DVD and classic install using the latest RC ISOs. Check the boot kernel command line - it should include "splash quiet" to activate the plymouth splash screen. In my tests, the "splash" was missing on the Live DVD boot kernel command line, and both "splash" and "quiet" were missing in the classic install.
CC: (none) => mageia
Ha! Yes confirmed. "splash quiet" is missing. We were looking too deeply and ignored the obvious.
Ah, yes. When troubleshooting it's always wise to keep Occam's Razor in mind, filed right next to Murphy's Law.
commit 0ce20b33acee39ca684f12d213dc46ffb819825f Author: Thomas Backlund <tmb@...> Date: Mon Apr 20 23:15:18 2015 +0259 - bootloader: o dont override 'splash' and/or 'quiet' when adding 'noiswmd' (mga#15666) --- Commit Link: http://gitweb.mageia.org/software/drakx/commit/?id=0ce20b33acee39ca684f12d213dc46ffb819825f
Fixed in 5RC9.
Status: NEW => RESOLVEDResolution: (none) => FIXED