MP 1,1-5,1 Manually Configured OpenCore on the Mac Pro

[Norbert Mikołajczyk]

hi guys!
Update to 0.5.9 went flawlessly, OpenCanopy is visible, fantastic work!
Right now I'm searching teh internet and this thread to find how to add to OpenCanopy Recovery and Reset Nvram to be visible in the Bootpicker menu. I read the manual. Could someone point me in the right direction please?

Also, my usb mouse is very choppy and inaccurate in OpenCanopy, can I fix this somehow?

 

[h9826790]

Also, my usb mouse is very choppy and inaccurate in OpenCanopy, can I fix this somehow?

This is a know issue, and developers advised that there are not much they can do about it.

 

[Norbert Mikołajczyk]

Hi, I managed to make Recovery partition visible in OpenCanopy but sadly my apple usb keyboard isn't working.
I activated KeySupport but still no response from keyboard in OpenCanopy.

Somehow keyboard started working, dunno why... ?

 

[Awediohead]

Sorry that this is off-topic - I just thought that people using OpenCore on Mac Pro's would be most likely to know the answer. I have a late 2011 MacBook Pro with a fried discrete graphics card - it works perfectly well with the iGPU thanks to my following a tutorial that had me booting into Linux to run a script that effectively turns off the dGPU. I've built a couple of hackintoshes to replace my original MP 1,1 that I've switched over to OpenCore from Clover recently, and I was wondering if it might be helpful with my MacBook Pro? This is currently on El Capitan and has been a nightmare trying to update the OS on because the process kills the EFI hack and then of course I can't see the screen to reinstall the hack. I know with OpenCore on Intel hackintoshes it's possible to set things up so it either prioritises the dGPU or for builds without a dGPU points the OS at the iGPU only. So could it replace the Linux based hack?
Just wondered if anyone knows if this has been covered/attempted, or maybe just that its a dead end? Getting it to 10.13 would be fine if possible. Cheers

 

[TECK]

The guide has been updated to OpenCore version 0.5.9.

I updated the Python repo.

I can confirm @vit9696's suggested fix (ExitBootServicesDelay >= 3000) works. I tested this several times, as soon as I set ExitBootServicesDelay to 0, Windows boot freezes. I just did a PR, maybe you should update also your tutorial.

Edit: After rebooting 3 times into Windows, the freeze issues made surface again. If I boot back to Catalina and try again to boot into Windows, I get either an Automatic Repair which fails to repair or a boot freeze. I know @startergo posted a fix for the partition, but I cannot find it anymore, found it. I'm not looking forward to re-install Windows.

$ brew cask install gdisk
$ sudo gdisk /dev/disk0
GPT fdisk (gdisk) version 1.0.5

Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
The protective MBR's 0xEE partition is oversized! Auto-repairing.

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): p
Disk /dev/disk0: 976773168 sectors, 465.8 GiB
Sector size (logical): 512 bytes
Disk identifier (GUID): 6E061752-F6C4-48ED-9FCE-1616F69B1D36
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 976773134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2029 sectors (1014.5 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048         1085439   529.0 MiB   2700  Basic data partition
   2         1085440         1290239   100.0 MiB   EF00  EFI system partition
   3         1290240         1323007   16.0 MiB    0C01  Microsoft reserved ...
   4         1323008       976773119   465.1 GiB   0700  Basic data partition

Command (? for help): q

See:

Windows 10 partitions new drive with GPT table containing an invalid protective MBR.

My experience when using Windows 10 to partition a new, bare drive (i.e., a drive with no pre-existing partition table) of 2-terabytes in size or smaller shows that Windows 10 incorrectly denotes the

answers.microsoft.com

And (driver related):

After upgrading from Windows 7 to Windows 10, system thinks GPT partition is MBR

I have a Windows 7 system with 3 hard drives - Disc 0 is the boot disc formatted with MBR, Disc 1 is a 4 TB disc formatted with GPT, and Disc 2 is a 2 TB disc also formatted with GPT. Disc 1 has one

superuser.com

I'm running Windows on Syba SI-PEX40129 + Samsung 970 EVO Plus.

 

[Charles.tech]

i jast install windows with

You may try my 0.5.9 package. Or compare your config / EFI folder to my package.

I have OpenCanopy running since 0.5.9 beta
View attachment 920623

Can i get your's too?
URL is not working...

 

[startergo]

I updated the Python repo.

I can confirm @vit9696's suggested fix (ExitBootServicesDelay >= 3000) works. I tested this several times, as soon as I set ExitBootServicesDelay to 0, Windows boot freezes. I just did a PR, maybe you should update also your tutorial.

Edit: After rebooting 3 times into Windows, the freeze issues made surface again. If I boot back to Catalina and try again to boot into Windows, I get either an Automatic Repair which fails to repair or a boot freeze. I know @startergo posted a fix for the partition, but I cannot find it anymore, found it. I'm not looking forward to re-install Windows.

$ brew cask install gdisk
$ sudo gdisk /dev/disk0
GPT fdisk (gdisk) version 1.0.5

Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
The protective MBR's 0xEE partition is oversized! Auto-repairing.

Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): p
Disk /dev/disk0: 976773168 sectors, 465.8 GiB
Sector size (logical): 512 bytes
Disk identifier (GUID): 6E061752-F6C4-48ED-9FCE-1616F69B1D36
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 976773134
Partitions will be aligned on 2048-sector boundaries
Total free space is 2029 sectors (1014.5 KiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1            2048         1085439   529.0 MiB   2700  Basic data partition
   2         1085440         1290239   100.0 MiB   EF00  EFI system partition
   3         1290240         1323007   16.0 MiB    0C01  Microsoft reserved ...
   4         1323008       976773119   465.1 GiB   0700  Basic data partition

Command (? for help): q

See:

Windows 10 partitions new drive with GPT table containing an invalid protective MBR.

My experience when using Windows 10 to partition a new, bare drive (i.e., a drive with no pre-existing partition table) of 2-terabytes in size or smaller shows that Windows 10 incorrectly denotes the

answers.microsoft.com

And (driver related):

After upgrading from Windows 7 to Windows 10, system thinks GPT partition is MBR

I have a Windows 7 system with 3 hard drives - Disc 0 is the boot disc formatted with MBR, Disc 1 is a 4 TB disc formatted with GPT, and Disc 2 is a 2 TB disc also formatted with GPT. Disc 1 has one

superuser.com

I'm running Windows on Syba SI-PEX40129 + Samsung 970 EVO Plus.

I wonder why do you have partition 1 before the ESP partition? it should be something like this:

gdisk /dev/disk2
GPT fdisk (gdisk) version 1.0.4

Warning: Devices opened with shared lock will not have their
partition table automatically reloaded!
Partition table scan:
  MBR: protective
  BSD: not present
  APM: not present
  GPT: present

Found valid GPT with protective MBR; using GPT.

Command (? for help): p
Disk /dev/disk2: 488397168 sectors, 232.9 GiB
Sector size (logical): 512 bytes
Disk identifier (GUID): 803ED14A-61F2-4BE1-9B33-46F5B2159BA6
Partition table holds up to 128 entries
Main partition table begins at sector 2 and ends at sector 33
First usable sector is 34, last usable sector is 488397134
Partitions will be aligned on 8-sector boundaries
Total free space is 2349 sectors (1.1 MiB)

Number  Start (sector)    End (sector)  Size       Code  Name
   1              40          409639   200.0 MiB   EF00  EFI System Partition
   2          411648       488396799   232.7 GiB   0700

cMP5,1 and Apple BOOTCAMP assistant for creating Windows 10 partition

Here is a little study on the official BOOTCAMP for the cMP5,1. It may be valid for other Macs, but it is not guaranteed. As you may know BOOTCAMP assistant throws this message, when you try to open it in an APFS formatted drive (Mojave and Catalina): I modified the BOOTCAMP Info.plist from a...

forums.macrumors.com

This is how BOOTCAMP assistant creates the partition on a single drive. Note the partition one location and geometry.
Also OC has problems if the EFI partition is not the first one on the drive. It is in the OC manual.

 

[h9826790]

i jast install windows with

Can i get your's too?
URL is not working...

The link is working, even the link in your quotation is working.

 

[cdf]

Edit: After rebooting 3 times into Windows, the freeze issues made surface again.

Exactly. I could not confirm the fix proposed by @vit9696. The problem is something else. It is also not related to the partitioning. If you install Windows by following the guide, you will not not get those extra partitions. However, the issue still exists. In fact, the issue has existed since day 1:

There's something flakey in either OC, my configuration of OC, or Windows itself which will eventually result in your Windows installation failing to boot.

So the issue exists with three installation methods: dism (as in the guide), VirtualBox and direct installation.

 

[startergo]

Exactly. I could not confirm the fix proposed by @vit9696. The problem is something else. It is also not related to the partitioning. If you install Windows by following the guide, you will not not get those extra partitions. However, the issue still exists. In fact, the issue has existed since day 1:



So the issue exists with three installation methods: dism (as in the guide), VirtualBox and direct installation.

Strange I have never experienced freezing issue. Could it be related to video drivers?

 

[Norbert Mikołajczyk]

I've something interesting to report.

The keyboard in BootPicker doesn't work when my Windows Legacy Sata HDD is inserted.
Keys works just fine when I unplug the Windows Hdd.
Everything is working fine otherwise, I hope the keyboard will start working when I'll convert Windows Legacy to UEFI.

Solved: It is the usb 3.0 hub to blame, I connected the keyboard directly and it works every time.

 

[startergo]

I've something interesting to report.

The keyboard in BootPicker doesn't work when my Windows Legacy Sata HDD is inserted.
Keys works just fine when I unplug the Windows Hdd.
Everything is working fine otherwise, I hope the keyboard will start working when I'll convert Windows Legacy to UEFI.

I got legacy and UEFI Windows and my keyboard works. I remember it did not work (only the mouse) and I enabled Automatic key support. Now it is working although I see strange reports in the log file that it cannot find the keyboard and mouse.

 

[cdf]

Could it be related to video drivers?

Well, the issue also happens on the first reboots after installing, before the drivers are installed. Interestingly, the issue eventually becomes very infrequent. OpenCanopy, however, has apparently made the issue more frequent...

 

[startergo]

Well, the issue also happens on the first reboots after installing, before the drivers are installed. Interestingly, the issue eventually becomes very infrequent. OpenCanopy, however, has apparently made the issue more frequent...

I know sometimes Windows " freezes" the spinning logo, but this is actually a GOP /drivers issue. This behavior is different on MBR Windows and on EFI video card. I have observed the switchover from one screen to the other where one of the screens is connected to a regular GOP card and the other to EFI video card. So basically even if you see the screen freezing the Windows is loading meanwhile you just cannot see it.

 

[Norbert Mikołajczyk]

I got legacy and UEFI Windows and my keyboard works. I remember it did not work (only the mouse) and I enabled Automatic key support. Now it is working although I see strange reports in the log file that it cannot find the keyboard and mouse.

KeySupport isn't working for me sadly, keys work only when I unplug Windows Legacy hdd...

 

[startergo]

KeySupport isn't working for me sadly, Kays work only when I unplug Windows Legacy hdd...

I chain load OC from rEFInd which also loads some EFI drivers before OC and I wonder if that makes any difference?

 

[Norbert Mikołajczyk]

I chain load OC from rEFInd which also loads some EFI drivers before OC and I wonder if that makes any difference?

I did some extra testing. It is the usb 3.0 hub to blame, I connected the keyboard directly and it works every time.

 

[TECK]

Well, the issue also happens on the first reboots after installing, before the drivers are installed. Interestingly, the issue eventually becomes very infrequent. OpenCanopy, however, has apparently made the issue more frequent...

How should we proceed investigating? Even if we are in DEBUG mode, this issue happens after OC, while in Windows.

@startergo, when I boot with OpenCanopy, I get an automatic repair and then when I select Continue, Windows freezes. I left it there for 15min, is dead alright. The only fix I have is to disable OpenCanopy and re-install Windows.

 

[Norbert Mikołajczyk]

Windows Legacy to UEFI conversion Steps:
0. Boot Mojave with OpenCore 0.5.9
1. Load Windows 10 via Parallels
2. Change MBR to GPT in Recovery
3. Reboot cMP

Is that all?
I wonder if I should enable SecureBoot in config.plist or delete BOOTx64.efi in /Volumes/efi/boot before the conversion?

 

[startergo]

Windows Legacy to UEFI conversion Steps:
0. Boot Mojave with OpenCore 0.5.9
1. Load Windows 10 via Parallels
2. Change MBR to GPT in Recovery
3. Reboot cMP

Is that all?
I wonder if I should enable SecureBoot in config.plist or delete BOOTx64.efi in /Volumes/efi/boot before the conversion?

Yes, do that.

 

[cdf]

How should we proceed investigating? Even if we are in DEBUG mode, this issue happens after OC, while in Windows.

Unfortunately, nothing in the logs indicates the issue. Neither FirmwareFeatures (for UEFI Windows boot support) nor ExitBootServicesDelay has helped. Because there are no boot failures at all with macOS or Linux, I believe the issue is Windows...

The only fix I have is to disable OpenCanopy and re-install Windows.

I've reinstalled a few times. Although infrequent (in my case), the issue is always there.

 

[startergo]

How should we proceed investigating? Even if we are in DEBUG mode, this issue happens after OC, while in Windows.

@startergo, when I boot with OpenCanopy, I get an automatic repair and then when I select Continue, Windows freezes. I left it there for 15min, is dead alright. The only fix I have is to disable OpenCanopy and re-install Windows.

View attachment 920911
View attachment 920912

You need to get in safe mode with networking and update the video drivers.

 

[Macschrauber]

Does not work either, If I change Boot Picker to Builtin then I get the text mode.

ok, gonna do further testing on a 5.1 tomorrow evening.

Flashed Kepler GPU with bootscreen on a MP 3.1 btw.

self reply:

Attached the Disk with OpenCore 0.5.9 and OpenCanopy to a 5.1 with similar GPU (Kepler, bootscreen, no gop) and got the graphical boot picker.

So it's a MacPro 3,1 incompatibility

 

[iModFrenzy]

Soo while back I posted about my Sapphire Pulse 5700XT not displaying any text on the boot picker page when DirectGPORendering is set to false. However, now both options give me no text. So not sure what the issue is here...

 

[mangombia]

I was successful updating OC to 0.5.9 and changing from NDK to OpenCanopy. Operational-wise everything works as expected, and I was even able to apply the Catalina 10.15.5 Supplemental Update earlier today. However, I noted that it seems my boot chime has disappeared, so I commanded an NVRAM reset from the OC/OpenCanopy boot picker, and it rebooted with the chime the first time, but not since. Any ideas?