Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

MP 1,1-5,1 OpenCore and the 2008 Mac Pro 3,1

Status
The first post of this thread is a WikiPost and can be edited by anyone with the appropiate permissions. Your edits will be public.
amstel78

amstel78

macrumors 6502a
Original poster
Aug 12, 2018
517
183
At the request of @tsialex, I've created this thread to consolidate questions, issues, and solutions revolving around OpenCore and its implementation on the early 2008 Mac Pro 3,1. If you have one of these machines and are interested in installing OpenCore, or already have OpenCore running, please contribute here. The main OC thread here still caters primarily to users of MP4,1 and MP5,1 machines.

Ultimately, my end goal for my MP3,1 is to get newer operating systems such as Mojave, Catalina, or Big Sur installed and running via OC without the need for extraneous patches such as those provided by DosDude1 or other developers (Big Mac).

FYI @Dayo @cdf @vit9696 @h9826790

OpenCore Resources for the MP3,1:
 
Last edited:
  • Like
  • Love
Reactions: eunix357, G4fanboy, freqrider and 7 others
I have not even been able to get OpenCore to boot on my Mac Pro 3,1.

I have a Mac Pro 3,1 with a flashed GTX 770. I have a HFS+ formatted HDD for data with no OS installed on it. I copied Martin LO's OC 0.6.6 package to the EFI partition. I tried both blessing OpenCore and starting it from the Mac's boot picker.

In the Apple boot picker I can see the OpenCore partition. I even managed to give it a VolumeIcon. If I select it, the Mac loads the /EFI/boot/BootX64.efi file, but hangs without showing the OpenCore boot screen.

Blessing OpenCore has no visible effect. The Mac boots directly to macOS. Using the efibootmgr command in Linux, I can see that the NVRAM variable Boot0080 is set to .../EFI/OC/OpenCore.efi with BootOrder set to 0080.
 
there is no magic to run OpenCore on ANY mac hardware, as it's the most versatile tool to do so.
beside of some issues ( BT2.0 / audio / wifi ) we build a config which allows you to run every macOS installer from a scratch el capitan or dosdude patched installation.
i released a instruction video to this already.
still in open beta, it allows to vanilla install Big Sur on a 3,1 ( spoofing a 6,1 board-id ), a previous version ( spoofing a complete 6,1 ) allows to install sierra, high sierra, mojave and catalina as well.
injecting older kext ( AppleHDA from high sierra, WiFi for your specific card ) is just some clicks away and running perfect.

see the video on YT...

any questions are very welcome, let's participate and share your knowledge.

edit: as i installed the VoodooHDA instead of AppleALC, audio issues still exist in Big Sur but a device is already present...
 
Last edited:
  • Like
Reactions: AlexMaximus, 0134168 and amstel78
Petri, the main reason people use opencore is to get a bootscreen and hw accel with AMD gpus. I had to turn off whatevergreen and lilu kexts in the config.plist and play with the GOP rendering settings before my flashed nVidia card worked with OC. (I now run an RX580 so I turned them back on for the AMD card) Maybe try that.
Petri Krohn said:
I have not even been able to get OpenCore to boot on my Mac Pro 3,1.

I have a Mac Pro 3,1 with a flashed GTX 770. I have a HFS+ formatted HDD for data with no OS installed on it. I copied Martin LO's OC 0.6.6 package to the EFI partition. I tried both blessing OpenCore and starting it from the Mac's boot picker.

In the Apple boot picker I can see the OpenCore partition. I even managed to give it a VolumeIcon. If I select it, the Mac loads the /EFI/boot/BootX64.efi file, but hangs without showing the OpenCore boot screen.

Blessing OpenCore has no visible effect. The Mac boots directly to macOS. Using the efibootmgr command in Linux, I can see that the NVRAM variable Boot0080 is set to .../EFI/OC/OpenCore.efi with BootOrder set to 0080.
Click to expand...
 
Last edited:
  • Like
Reactions: Petri Krohn
I for one am a fan of patched OS’s. That way I can tailor each one and run a more generic ooenCore setup. The 3,1 is considered antiquated in the computer realm these days and the hardware needs extra finessing to work with modern OS’. This has become more apparent with the advent of running Big Sur on the 3,1, which broke telemetry, wifi, USB 1.1 support, booting from firewire drives, audio AND BLOOTOTH2! Your choice is to install the needed kexts or load them with OC. I much prefer to patch the needed kexts than have to load them in OC for every OS. Besides, Progect Legacy method requires you to remove the BT2 card to boot BS and audio still does not work, whereas I have been running a patched Big Sur for months now, WITH VANILLA OPENCORE O.6.6 and wifi, audio, usb, firewire all work fine and I don’t have to remove my BT2 card so I can use it with my other OS’s! (Thanks to StarPlayrX Bigmac and JackLuke’s BigSur LEGACY BASESYSTEMFIX patches.)

Another issue to consider with running OpenCore on the 3,1 is how to boot Windows? As we know, you can not install Windows in UEFI mode on the 3,1. (It has been reported you can in fact install it on a pc and then transfer it to the 3,1 and finish setup on the mac and boot UEFI Windows on the 3,1!!!) The problem is OC does not recognise legacy installs. For this reason I recommend Dayo’s excellent RefindPlus OC chainload package which he diligently maintains. This lets you boot Windows legacy via refind and chainloads OC to boot MacOS! I can not reccomend it enough and for me is the ultimate 3,1 setup. ( I use some Windows Only SW for production, so this is necessary.)

I think Jörg and Alex’ work on Project Legacy is great and I commend them on their efforts and StarPlayrx and JackLuke for their brilliant patchers! This is all new territoty for the aging 3,1 and no system is without it’s faults but I have come to the conclusion that each method needn’t be exclusive of the others. It’s all about building a system that works best for you! And it will only get better, I’m sure, as the kinks are worked out :)
 
  • Like
Reactions: osxfr33k, pullman and Dayo
Petri Krohn said:
I have not even been able to get OpenCore to boot on my Mac Pro 3,1.

I have a Mac Pro 3,1 with a flashed GTX 770. I have a HFS+ formatted HDD for data with no OS installed on it. I copied Martin LO's OC 0.6.6 package to the EFI partition. I tried both blessing OpenCore and starting it from the Mac's boot picker.

In the Apple boot picker I can see the OpenCore partition. I even managed to give it a VolumeIcon. If I select it, the Mac loads the /EFI/boot/BootX64.efi file, but hangs without showing the OpenCore boot screen.

Blessing OpenCore has no visible effect. The Mac boots directly to macOS. Using the efibootmgr command in Linux, I can see that the NVRAM variable Boot0080 is set to .../EFI/OC/OpenCore.efi with BootOrder set to 0080.
Click to expand...
Unless you're familiar with building and validating OC's config.plist file, the easiest way to have OC up and running is via MyBootMgr. I've successfully used that package to chainload OpenCore via RefindPlus on my MP3,1 and install Mojave. Do note that via this method, onboard audio still does not work due to AppleHDA.kext not being patched. From what I've read, VoodoHDA also has problems. You can work around it by using a USB audio device however.
 
Last edited:
  • Like
Reactions: Petri Krohn, freqrider and Henninges
Henninges said:
playing arround with voodoo, an external device is of course an alternative., but nativ sound is possible.
how about your BT2.0 ? is it working?
Click to expand...
I've tried injecting AppleHDA kext from a working install of El Capitan but it broke kernel dependencies and wouldn't load even after refreshing S/L/E. Must it be from High Sierra to get onboard audio functioning? In the meantime, a USB audio dongle is a workaround...
 
Last edited:
i tried the HS version and could inject it, but cant get the permission to change the kext's write mode.
usual command like "sudo mount -u /" are not working and i always get a failure "66", no matter if i disable authenticated root and SIP on an unsealed drive...

edit: injecting the HS kext into mojave and catalina works just fine...
 
Could you please zip and upload that version of AppleHDA here? Will give it a try later.
 
Henninges said:
i tried the HS version and could inject it, but cant get the permission to change the kext's write mode.
usual command like "sudo mount -u /" are not working and i always get a failure "66", no matter if i disable authenticated root and SIP on an unsealed drive...

edit: injecting the HS kext into mojave and catalina works just fine...
Click to expand...
You have to delete the snapshot, then install kexts then rebuild the snapshot since Big Sur boots from a snapshot. OR disable snapshots alltogether, as I have, so I can edit filesystem at whim. Snapshots on BS are a PITA! Also, I believe the AppleHDA kext is patched to work on BS. Not 100% sure though. Welcome to Apple’s new ‘secure environment’. Soon OpenCore will be the only way to load kexts. BTW... did you try to load Apple HDA via opencore? This worked for me with DirectHW.kext when I was having trouble loading it from /Sys/Extensions. Worth a try?
 
Henninges said:
here you go...
Click to expand...
Thanks. BTW, BT and WiFi worked with OC 067. Only no-go was onboard audio. (This was Mojave... still getting KP's when installing BS. Will need to get a separate SSD for that experiment).
 
freqrider said:
You have to delete the snapshot, then install kexts then rebuild the snapshot since Big Sur boots from a snapshot. OR disable snapshots alltogether, as I have, so I can edit filesystem at whim. Snapshots on BS are a PITA! Also, I believe the AppleHDA kext is patched to work on BS. Not 100% sure though. Welcome to Apple’s new ‘secure environment’. Soon OpenCore will be the only way to load kexts. BTW... did you try to load Apple HDA via opencore? This worked for me with DirectHW.kext when I was having trouble loading it from /Sys/Extensions. Worth a try?
Click to expand...
Haven't tried injecting kexts via OC yet. Still a little unfamiliar as to how to properly setup config.plist for AppleHDA.
 
I just looked in my patched Big Sur install with WORKING AUDIO on my 3,1 and found TWO AppleHDA.kexts!?! One was loaded and the other (AppleHDA.kext2) had only a controller component loaded? These were patched by Jacklukem's Big Sur basesystemfix USB installer patch. Perhaps you can load them via OC and get audio to work?
Screen Shot 2021-03-08 at 12.49.24 PM.png
 

Attachments

  • AppleHDA Kexts.zip
    5.4 MB · Views: 345
amstel78 said:
Haven't tried injecting kexts via OC yet. Still a little unfamiliar as to how to properly setup config.plist for AppleHDA.
Click to expand...
You can simply copy an existing kext instruction from the config.plist and replace both xxxx.kext names with new yyyy.kext name and place the kext in EFI/OC/Kexts. OR just patch the damn thing with Jacklukem's basesystemfic like I did! LoL!
 

Attachments

  • Screen Shot 2021-03-08 at 1.26.47 PM.png
    Screen Shot 2021-03-08 at 1.26.47 PM.png
    208.5 KB · Views: 453
Last edited:
freqrider said:
You can simply copy an existing kext instruction from the config.plist and replace both xxxx.kext names with new yyyy.kext name and place the kext in EFI/OC/Kexts. OR just patch the damn thing with Jacklukem's basesystemfic like I did! LoL!
Click to expand...
That easy huh? Was thinking other keys like MaxKernel or MinKernel needed alteration.

And yes, forgot about AppleHDAController.kext. I believe that would have to be replaced as well. Thanks for providing both.
 
  • Like
Reactions: freqrider
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back