| Summary: | graphical startup animation not working | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Marcus Zurhorst <marcuszurhorst> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | zen25000 |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | plymouth-0.8.6.1-7.mga3.src.rpm | CVE: | |
| Status comment: | |||
|
Description
Marcus Zurhorst
2013-04-03 18:55:39 CEST
Please forget my previous message, I did not use the script properly. Handing over the name of the particular theme made it work: [marcus@mzlaptop ~]$ sudo plymouth-set-default-theme Mageia-Default -R Now the initrd was recreated. However, the next boot was still "talky", I did not see the graphical animation. Something is broken here. Barry asked me to check /etc/default/grub for an vga=XXX entry, but there is none in this file. Marcus, can you please post the output of cat /etc/default/grub|grep GRUB_CMDLINE_LINUX_DEFAULT CC:
(none) =>
zen25000 Sure! There is no output, this parameter is not defined in the file: [marcus@mzlaptop ~]$ cat /etc/default/grub|grep GRUB_CMDLINE_LINUX_DEFAULT [marcus@mzlaptop ~]$ Here is the full file, just in case this is the next question :-) [marcus@mzlaptop ~]$ cat /etc/default/grub GRUB_DISABLE_OS_PROBER=false GRUB_DISABLE_RECOVERY=true GRUB_TERMINAL_OUTPUT=gfxterm GRUB_DISTRIBUTOR=Mageia GRUB_GFXMODE=1024x768x32 GRUB_GFXPAYLOAD_LINUX=text GRUB_THEME=/boot/grub2/themes/maggy/theme.txt [marcus@mzlaptop ~]$ Ouch! I have no idea how that can happen - maybe Thierry can help. Add the line: GRUB_CMDLINE_LINUX_DEFAULT="splash quiet" I (re?)added the line per your instruction. However, this does not fix anything, I cannot see a difference. Do I have to trigger something like initrd recreation? -- Or is this supposed to have an immediate effect? Ah sorry: $ update-grub Well, that worked. Thanks! The situation is improving, but it is still not perfect. I have now the following findings: a) beween Grub2 and Plymouth, I see for 1-2 seconds the first line of the boot messages. Afterwards, the Mageia background is shown. b) I saw that there are these blue "bubbles" raising out of the pot, which seems to represent the progress bar. When Plymouth switches to another image, the screen is black for short while. c) With 2-3 more boots, the defect b) improves (maybe a learning curve for the pre-loading of data during boot), but I see with every boot another behavior. (sometimes 2-3 bubbles smoothly blended; once the screen got black after 2nd bubble and stayed there until GDM is loaded) d) when the last Plymouth image is shown, the screen goes black for a short while before GDM appears. While this as all booting, the following things showed up when shutting down: e) Triggering a shutdown from GDM --> animation works perfect f) Triggering a reboot from GDM --> animation does not work; I only see console output Some more testing: I switched the animation: [marcus@mzlaptop ~]$ sudo plymouth-set-default-theme glow -R [marcus@mzlaptop ~]$ sudo update-grub2 Now rebooting (triggered from within Gnome Desktop), I don't see any flaws (maybe because this is a still image and no animation?) The boot animation was much smoother as well. Nevertheless, here was also in between a very short black screen flickering, and the "gap" between Plymouth and GDM was also still there. (In reply to Marcus Zurhorst from comment #9) > Nevertheless, here was also in between a very short black screen flickering, > and the "gap" between Plymouth and GDM was also still there. I think that's as good as it gets, for this release - unless someone is working on it - I have never seen a totally smooth boot without the black dropouts ;) The missing theme was probably down to the grub2-mageia-theme package missing from the install DVD (https://bugs.mageia.org/show_bug.cgi?id=9608) which has been fixed for the next release, so I think this can be closed now. Closing as fixed. If you manage to reproduce the /etc/default/grub problem feel free to open another bug, but I cannot reproduce ;) Status:
NEW =>
RESOLVED |