Bug 6179 - After a fresh installation Mageia 2 doesn't boot
Summary: After a fresh installation Mageia 2 doesn't boot
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal critical
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-05-30 22:41 CEST by Tobias Endrigkeit
Modified: 2013-08-27 12:35 CEST (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Tobias Endrigkeit 2012-05-30 22:41:34 CEST
Description of problem:

I've installed Mageia 2 on my Acer Aspire 7530G succesfully, but when I restarted my laptop, the bootscreen is shown and stops working after a while. Sometimes the screen becomes black after a few seconds.

I also tried to look at the text-mode and there it shows in the last line that mageia is looking up a hotplugged network.

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

---

How reproducible:

Install Mageia 2 on Acer Aspire 7530G and boot the system

Steps to Reproduce:

1.Install Mageia
2.Restart Mageia as the installer says
3.wait a while
Comment 1 Manuel Hiebel 2012-06-27 21:52:22 CEST
your first part is an bug in our plymouth bug see https://bugs.mageia.org/show_bug.cgi?id=5891

for the second one, I don't know can you be more specific ?
Comment 2 Samuel Verschelde 2013-08-27 12:35:16 CEST
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information.

Closing as OLD.

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


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