Bug 9560 - drakboot does not display current bootloader correctly
Summary: drakboot does not display current bootloader correctly
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: All Linux
Priority: release_blocker major
Target Milestone: ---
Assignee: Thierry Vignaud
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 416
  Show dependency treegraph
 
Reported: 2013-03-29 09:25 CET by Marcus Zurhorst
Modified: 2013-04-10 11:03 CEST (History)
1 user (show)

See Also:
Source RPM: drakxtools-curses-15.28-1.mga3
CVE:
Status comment:


Attachments

Description Marcus Zurhorst 2013-03-29 09:25:23 CET
Description of problem:
Some weeks ago, the grub2 menu lost the graphical interface and now defaults to the text mode.

Yesterday, I found time to take care and went to the Mageia Control Center to check the settings of the boot loader.
The drop-down field told me "Grub with graphical menu", but I definetely use Grub2.  Thus, I toggeled this to "Grub2 with graphical menu".

This morning, the boot process was still in text mode, and looking at the settings showed me that the Mageia Control Center settings were also back at "Grub with graphical menu".



Version-Release number of selected component (if applicable):
grub2-2.00-41.mga3




How reproducible:
?

I have no clue about reproducability of the original defect of the text mode boot menu.  I did not report this earlier since I had a) no time and b) assumed that it is really obvious to everyone.  
Since I haven't found a bug for this, I assume that it doesn't show up widely.


For the bug in the Mageia Control Center, where the settings are not stored, I can say that this seems reproducible (for me).  Tried it again this morning, and it was the same effect.


All packages updates.  Please instruct how I can support debugging this.

Reproducible: 

Steps to Reproduce:
Comment 1 Barry Jackson 2013-03-29 12:20:05 CET
Hi,
Regarding the missing theme, I suspect that a setting was lost during an update.
Do:
su
urpme grub2-mageia-theme && urpmi grub2-mageia-theme

then re-boot. Your theme should now be restored.


Regarding the mcc/drakboot problem, this looks like a grub2 integration bug.

Priority: Normal => release_blocker
CC: (none) => zen25000
Hardware: i586 => All
Blocks: (none) => 416
Assignee: bugsquad => thierry.vignaud
Source RPM: grub2-2.00-41.mga3 => drakxtools-curses-15.28-1.mga3
Severity: normal => major

Barry Jackson 2013-03-29 12:22:49 CET

Summary: Grub2 menu not graphical anymore => drakboot does not display current bootloader correctly

Comment 2 Marcus Zurhorst 2013-04-02 18:12:16 CEST
Hi Barry,

thanks for the hint.  I followed your instruction, and the grub2 menu is now graphical.

BUT:  Everything else between the boot menu and the GDM login screen is still not graphical.


The boot starts in text mode and prints all these messages about hardware and services etc. -- After some seconds, the screen flickers briefly and it goes into grahpical mode, but still printing all these messages.

My expectation of a graphical mode would be similar to MS Windows, where you see a logo and a progress bar, and nothing else.

I think Mandriva/Mageia had this as well in previous releases.


My message fits to my original bug report, but not anymore to the new bug title that you entered.  Shall I open another bug? --


Regards,
  Marcus
Comment 3 Barry Jackson 2013-04-03 17:24:55 CEST
> My message fits to my original bug report, but not anymore to the new bug
> title that you entered.  Shall I open another bug? --
> 

Yes open another bug against plymouth (guessing), for the screen appearance after grub2 but before login. If you have grub installed you could check for any vga=xxx in /boot/grub/menu.lst and check if a similar setting appears in /etc/default/grub (which is for grub2). 
Don't reply here on that topic, add it to your new bug report.
Comment 4 Barry Jackson 2013-04-10 11:03:07 CEST
This bug is too confusing now, involving three different issues which I suspect are fixed in other bug reports.

Closing as fixed.

If you feel that any ONE issue is not resolved that is not covered by another bug then please open a new bug report on that issue only. Thanks.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.