Ahmad Rady Posted December 4, 2016 Share Posted December 4, 2016 I will be waiting for the full guide. I just bought a used one. BTW, did you find any solution for the USB3? Link to comment Share on other sites More sharing options...
Grattle Posted January 5, 2017 Share Posted January 5, 2017 Could you share how you were able to UEFI boot? I cannot get UEFI boot to work at all. Thanks! Link to comment Share on other sites More sharing options...
Administrators Hervé Posted January 5, 2017 Administrators Share Posted January 5, 2017 Make sure you define the correct path in BIOS if you choose UEFI mode. Caution with the OP's config file though because it carries some incorrect settings and that can lead to confusion. For instance: on the graphics side, he used the discrete nVidia GPU and correctly activated nVidia injection but kept some incorrect Haswell HD4600 Azul framebuffer layout-id at the same time, something obviously not applicable on a SandyBridge HD3000 platform. on the audio side, he used AppleHDA patches for ALC292 codec when the laptop appears fitted with IDT 92HD90 codec so it's quite normal he could not get audio through AppleHDA. on the SMBIOS side, he used MBP10,1 which is an IvyBridge platform with nVidia GPU. One could have expected SandyBridge models such as MBP8,1 (HD3000) or MBP8,2/8,3 (HD3000 + AMD). But maybe that was necessary to get the nVidia dGPU to work. Link to comment Share on other sites More sharing options...
Pupilliam Posted January 8, 2017 Author Share Posted January 8, 2017 Hey, sorry I was having some issues with my job. I'll be able to update the guide very soon. As for the UEFI boot, you need to make sure you have UEFI boot selected in BIOS. Additionally, if your EFI folder doesn't have /EFI/Boot/BOOTX64.efi , it won't load the Clover without custom-defining the path. Herve, thank you for pointing out the errors in my config file, I will fix them ASAP. I had based my config off of the M6800 one, so that would explain the first two issues. The SMBIOS configuration is because I would get a black screen whether or not I was using discrete vs. onboard. Changing to the odd profile fixed it. When I get my machine up and running again, I will see to these issues. Link to comment Share on other sites More sharing options...
Recommended Posts