Bug 9813 - Mageia 3 does not boot after install completes
Summary: Mageia 3 does not boot after install completes
Status: RESOLVED DUPLICATE of bug 9759
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: i586 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-04-21 06:17 CEST by bozonius
Modified: 2013-04-22 00:21 CEST (History)
1 user (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description bozonius 2013-04-21 06:17:42 CEST
Description of problem:
Install completes without incident, but installed system will not boot.  Momentarily get the splash graphics, but then returns to console mode with one or two kernel errors (but these look like the usual ones about the tsc timer, etc). After that, the system just hangs.  There is no access to a command console or the desktop after that.

Note that this is Mageia-3-RC-i586-DVD installed to a VirtualBox VM running the latest host software; never get far enough to check the guest additions.  Install of Mageia-2-i586-DVD works fine, however, using the exact same VM with no config changes.


Version-Release number of selected component (if applicable):
Mageia-3-RC-i586-DVD

How reproducible:
Very.  I was able to twice.


Steps to Reproduce:
1.  Install Mageia-3-RC-i586-DVD to VirtualBox 4.2.12 VM
2.  Choose updates or not; this made no difference
3.  Attempt to reboot into installed Mageia 3 system


Reproducible: 

Steps to Reproduce:
bozonius 2013-04-21 06:17:54 CEST

CC: (none) => bozonius

Comment 1 Manuel Hiebel 2013-04-21 15:39:13 CEST
seems related to bug 9759, maybe you can try with changing to the vesa driver 
(and please don't use the "3" version yet)

Version: 3 => Cauldron

Comment 2 bozonius 2013-04-22 00:21:11 CEST
Didn't go back far enough in searches, or didn't use right keywords, so I accidentally logged this bug.

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

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


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