Bug 834076
| Summary: | Fedora 17 does not install via bootable media on new (Mid-2012) MacBook Pro (9,2) | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Brian Smith <bcs296> | ||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | unspecified | ||||||||||
| Version: | 17 | CC: | bugzilla, ebassi, eroux, gansalmon, g.kaviyarasu, ian.dick01, info, itamar, jensk.maps, jonathan, joshua, kernel-maint, madhu.chinakonda, netllama, robin, ronan.forker, sog, vanmeeuwen+fedora | ||||||||
| Target Milestone: | --- | ||||||||||
| Target Release: | --- | ||||||||||
| Hardware: | x86_64 | ||||||||||
| OS: | Mac OS | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||||
| Doc Text: | Story Points: | --- | |||||||||
| Clone Of: | Environment: | ||||||||||
| Last Closed: | 2012-10-08 15:19:09 UTC | Type: | Bug | ||||||||
| Regression: | --- | Mount Type: | --- | ||||||||
| Documentation: | --- | CRM: | |||||||||
| Verified Versions: | Category: | --- | |||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||
| Embargoed: | |||||||||||
| Attachments: |
|
||||||||||
|
Description
Brian Smith
2012-06-20 18:33:17 UTC
Mysterious lockups are frequently the symptom of a kernel problem. Reassigning in the hopes that they'll know how to go about debugging this. It looks like adding noapic to the boot command gets the installation process a little further along. http://forums.fedoraforum.org/showthread.php?t=281038 Does the same problem occur when in step 3 (the first step 3) you select Windows as the boot option? Can you report the version of EFI compliance (using shellx64.efi or rEFIt or rEFInd)? Created attachment 594859 [details]
call trace 1
Here are some call traces (I don't know if they're useful). They are all from different boots. One time the boot actually succeeded to GNOME.
The kernel command line was with "rhgb" and "quiet" removed and "noapic" added.
Created attachment 594860 [details]
call trace 2
Created attachment 594861 [details]
call trace 3
By the way, kernel 3.3.4-5 works with the boot option "nointremap". 3.4.3-1 doesn't though. So far it's been a complete wash for me on my 2012 MacBook Pro 15” Fortunately Fedora seems to run just fine within a VM under Fusion. Same problem occurs on 2012 MacBook Air model FWIW, I used the F17 boot.iso to make a USB flash drive installer, and that worked flawlessly on my 2012 MacBook Air 13". If anyone working on this bug wants some diagnostic output (lspci, dmesg, whatever) to help fix this, please let me know. Sorry, forgot to add I used the i686 install. (In reply to comment #11) > Sorry, forgot to add I used the i686 install. Thanks Jens, also got F17 working using the i686 Live ISO however needed PAE to address all 8GB of RAM. I got my 2012 Macbook Pro 15 Retina laptop working with F17 x86_64 by booting to the netboot CD, and appending noapic to the kernel command line. post-install video is another matter... but at least it installs |