Bug 6779

Summary:	No boot up after installation
Product:	Mageia	Reporter:	Klaus Märker <klaus.maerker>
Component:	Installer	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED DUPLICATE	QA Contact:
Severity:	critical
Priority:	Normal
Version:	2
Target Milestone:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:

Description Klaus Märker 2012-07-14 02:47:41 CEST

Description of problem:
I installed Mageia 2 on my PC. The installation was sucessful but during the first boot up the PC hangs with a black screen. I tried to boot again but this wasn't sucessful but I saw the following error message:

Failed to start Wait for plymouth Boot Screen to Quit..............failed
See 'systemctl status plymouth quit wait.services' for details

After the second and the third installation (incl. format disk) I got the same error message.

How reproducible:
As discribed!

Hint:
On the same machine (other harddisc) Mageia 1 is running without any problem. 
I used 'Mageia-2-x86_64-DVD.iso' (Downloaded at 17. June 2012).
On a other machine (Shuttle XS35V2) I had no problems.

Hardware: 
Board: Asus M5A88-V EVO
SSD: Crucial CT128M
RAM: 4GB 
CPU: AMD Athlon II X2 250e
PowerSupply: BeQuiet

Comment 1 Manuel Hiebel 2012-07-15 15:20:18 CEST

What is your graphic card ?

Comment 2 Klaus Märker 2012-07-15 23:04:32 CEST

Klaus
(In reply to comment #1)
> What is your graphic card ?
Hello Manuel,
I use no additional graphic card. The graphic chip is on-board. It's an ATI Radeon HD 4250 GPU.

Comment 3 Manuel Hiebel 2012-07-16 12:10:59 CEST

And does it work with the instruction in the errata: https://wiki.mageia.org/en/Mageia_2_Errata#Proprietary_graphics_card_drivers ?

Comment 4 Klaus Märker 2012-07-17 09:11:50 CEST

(In reply to comment #3)
> And does it work with the instruction in the errata:
> https://wiki.mageia.org/en/Mageia_2_Errata#Proprietary_graphics_card_drivers ?
Hello Manuel,
yes, now it works. Why does the installer not use the vesa-driver in this case?
Klaus

Comment 5 Manuel Hiebel 2012-07-17 10:36:10 CEST

I don't know anymore, maybe there was a bug, anyway it's a duplicate

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

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