Bug 4143

Summary:	bootup, in vbox as well as regular, gives some weird fb issues
Product:	Mageia	Reporter:	AL13N <alien>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	minor
Priority:	Normal	CC:	dmorganec, mageia, marja11
Version:	Cauldron
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:	plymouth	CVE:
Status comment:
Attachments:	bootup oddness

Description AL13N 2012-01-15 22:53:47 CET

Description of problem:
see screenshot

reproduce:
1. install alpha2
2. update regularly
3. reboot after kernel updates

Comment 1 AL13N 2012-01-15 22:55:45 CET

Created attachment 1367 [details]
bootup oddness

this is a vbox, it may/may not be related, this is after kernel updates and definately also vbox driver

Manuel Hiebel 2012-01-16 16:44:28 CET

Source RPM: (none) => plymouth
Severity: normal => minor

Comment 2 Marja Van Waes 2012-02-24 22:41:05 CET

this is/was not only in vbox, I've seen it, too, in a regular install. I suppose most of us were just too lazy to report it. I decided to blame systemd integration, which is a nice scapegoat for almost everything ;)

cc'ing dmorgan and coling so they can defend themselves :)

@ AL13N what do you mean by "fb", btw?

CC: (none) => dmorganec, mageia, marja11
Summary: bootup in vbox gives some weird fb issues => bootup, in vbox as well as regular, gives some weird fb issues

Comment 3 AL13N 2012-02-25 09:42:45 CET

fb == framebuffer

i think it happens when the framebuffer starts up and some error messages is show, which sort of gets out of framebuffer, but then it starts displaying the progress again like the image.

Comment 4 Colin Guthrie 2012-02-25 12:05:51 CET

I believe I fixed this with the most recent dracut. Since the latest kernels (with xz compressed modules) the KMS modules were not being included in the initrd. They should still have been loaded when the real filesystem kicked in and udev was started there, but for some reason this was intermittent.

Please update to latest cauldron and regenerate initrd with dracut and try and reproduce.

In the meantime, this is actually a duplicate too :)

*** This bug has been marked as a duplicate of bug 4559 ***

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