Bug 18990

Summary:	X does not start correctly on boot after installation with the network media on Virtualbox.
Product:	Mageia	Reporter:	Sébastien B. <sb.cw>
Component:	Release (media or process)	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	normal
Priority:	Normal	CC:	sysadmin-bugs
Version:	5
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Sébastien B. 2016-07-19 18:21:52 CEST

Description of problem:On Virtualbox, after installation, X don't start correctly.
Temporary solution:
https://bugs.mageia.org/show_bug.cgi?id=18724#c28
"During the boot process select "Advanced options for Mageia"
Type "e" for edit
Scroll down to the "linux" line
Key End to get to the end of the line
add "nomodeset" to the end of the line
ctrl-x or F10 will restart the boot process
The M5 client will now boot to a working desktop
The change is only temporary and "nomodeset" will need to be entered every time"

Permanent solution:
https://bugs.mageia.org/show_bug.cgi?id=18802#c12
"can you as root do a:

echo "blacklist vboxvideo" >/etc/modprobe.d/vboxvideo.conf

and reboot..."


Version-Release number of selected component (if applicable):


How reproducible:Yes !!


Steps to Reproduce:
1.With boot-non free.iso, install Mageia 5 on Virtualbox 5.0.24
2.Reboot.
3.http://www.mageialinux-online.org/upload/virtualbox_mageia_14_07_2016_22_52_03.png

Comment 1 David Walser 2016-07-22 15:52:19 CEST

Blacklisting vboxvideo isn't a solution, just a workaround, but you lose some functionality that way.  In most cases, adding the "nomodest" kernel command line option is a real fix for this.  Anyway, this is a duplicate.

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

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

Comment 2 Sébastien B. 2016-07-22 17:01:36 CEST

(In reply to David Walser from comment #1)
> Blacklisting vboxvideo isn't a solution, just a workaround, but you lose
> some functionality that way.  In most cases, adding the "nomodest" kernel
> command line option is a real fix for this.  Anyway, this is a duplicate.
> 
> *** This bug has been marked as a duplicate of bug 18724 ***

Hello David,
Which durable solution would you recommend?
It is not productive to add "nomodest" has redemararge each machine.
Thank you for caring that alert :)