Bug 4776 - After Installation of Mageia 2 Beta 1 on an Apple Macbook Pro 8,1, OS freezes on boot
Summary: After Installation of Mageia 2 Beta 1 on an Apple Macbook Pro 8,1, OS freezes...
Status: RESOLVED DUPLICATE of bug 1471
Alias: None
Product: Mageia
Classification: Unclassified
Component: Installer (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: High major
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-03-02 23:18 CET by Andy Liebman
Modified: 2012-03-03 00:28 CET (History)
0 users

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description Andy Liebman 2012-03-02 23:18:17 CET
After installing Mageia 2 Beta 1 on an Apple Macbook Pro 8,1 (Has , the OS freezes when you first try to reboot. You get the grub menu.  The boot up starts okay.  Then it freezes on the message: 

"fb:  conflicting fb hw usage radeonrmfb vs VESA VGA -- removing generic driver"

The screen becomes absolutely frozen. I waiting for 10 minutes and no progress. I rebooted again and again the OS froze at the same spot. 

A little Google search revealed that I should try modifying the grub command line by: 

a) adding the option "nomodeset"
b) removing the option "vga=788"

I had to do both of these things to get Mageia to boot.  After that, I modified /etc/grub/menu.lst to always run with those option choices and it would always reboot fine. 

FYI.  I was able to upgrade to the 3.2.9 kernel and install the amd (ati) proprietary driver and all is fine now. 

The graphics card on this Macbook Pro is identified by lshw as: 
Whistler XT [AMD Radeon HD 6700M Series]
Comment 1 Manuel Hiebel 2012-03-03 00:28:40 CET
Hi thanks for the bug report. This bug is a know one an it's the errata: https://wiki.mageia.org/en/Mageia_2_Errata#Radeon_HD_Issues
feel free to improve it if you have some ideas ;)

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

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


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