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

[Jegriva]

Hello, beatiful people.

I have 10.15 installed with Martin's Package.

To upgrade to Mac Oss 11, I have to remove Martin's Package, THEN install OC with the new OC Installer without rebooting inbetween?

 

[trifero]

Hello, beatiful people.

I have 10.15 installed with Martin's Package.

To upgrade to Mac Oss 11, I have to remove Martin's Package, THEN install OC with the new OC Installer without rebooting inbetween?

Correct. You mount the EFI, delete the folders, and install OCLP.

 

[streak8047]

How to fix usb mouse not working on MacPro 5,1 MacOS Monterey 12.5 ,reset nvram working some times

 

[PeterHolbrook]

OC 0.8.3 was released yesterday. Are there any changes that require a modification of config.plist?

 

[hwojtek]

How to fix usb mouse not working on MacPro 5,1 MacOS Monterey 12.5 ,reset nvram working some times

Use an USB2 hub, on Monterey your computer will no longer work with USB1 devices.

 

[trifero]

Use an USB2 hub, on Monterey your computer will no longer work with USB1 devices.

USB 1.0 on a Mac Pro 5,1??

 

[tsialex]

USB 1.0 on a Mac Pro 5,1??

A lot of human interface devices are USB1.0/1.1, all recent Apple wired keyboards and mice, for example, are USB1.1, some of the older ones, like the Pro Keyboard from 2003 Apple USB keyboard from 1998~2000, are USB1.0.

Some BT controllers are also USB1.1.

 

[racer]

I've been running the vanilla OC from message 1 with the config.plist and Big Sur for over a year now with no problems whatsoever. Updated OC and Big Sur as updates became available all smooth sailing.

Until a couple of weeks ago I routinely updated to 11.6.8. On reboot I got the black screen with the "Your computer restarted because of a problem..." in 5 languages.

Booted my backup Mojave drive, all good.

Reinstalled OC on a usb drive, installed BS 11.6.1 on the internal SSD, installation went fine, first boot "Your computer restarted blah blah..."

Booted Mojave from new usb drive OC, fine.
Tried reinstalling different BS version (11.6.7). Same, installation runs fine, first reboot "Your computer restarted blah blah..."

Disconnected everything on the Mac, reinstalled to different drive and from different sources (usb,sdd) same result.
Tried installing Montery 12.4, installation runs fine, first reboot bang.

In my desperation even tried OCLP 0.4.9 with new installer from usb drive, again installation ran fine, first reboot crash.

I've cleared NVRAM 3 times on most reinstalls, I've tried multiple hw drives, Mojave runs perfectly with or without OC, but for the life of me I can get BS or Monterey to boot.

Totally baffled.

Answering my own post.
NVRAM problem.
Fixed.

 

[6DecadesLater]

OC 0.8.3 was released yesterday. Are there any changes that require a modification of config.plist?

None are indicated in the Maintenance section but I always walk through the whole config.plist post #1 process. Gives me a chance to review my previous choices in settings.
This time when I run ocvalidate I get
NOTE: This version of ocvalidate is only compatible with OpenCore version 0.8.3!

OCS: No schema for LegacyEnable at 2 index, context <NVRAM>!

OCS: Missing key LoadEarly, context <Drivers>!

OCS: Missing key LoadEarly, context <Drivers>!

Serialisation returns 3 errors!

Settings in config.plist these are referencing are identical in the 0.8.2 and 0.8.3 versions. ocivalidate for 0.8.2 validates the 0.8.3 config.plist without error.

@cdf

 

[trifero]

A lot of human interface devices are USB1.0/1.1, all recent Apple wired keyboards and mice, for example, are USB1.1, some of the older ones, like the Pro Keyboard from 2003 Apple USB keyboard from 1998~2000, are USB1.0.

Some BT controllers are also USB1.1.

I understand now. Confused with the USB ports on Mac pro 5,1.👍🏻

 

[sfalatko]

None are indicated in the Maintenance section but I always walk through the whole config.plist post #1 process. Gives me a chance to review my previous choices in settings.
This time when I run ocvalidate I get
NOTE: This version of ocvalidate is only compatible with OpenCore version 0.8.3!

OCS: No schema for LegacyEnable at 2 index, context <NVRAM>!

OCS: Missing key LoadEarly, context <Drivers>!

OCS: Missing key LoadEarly, context <Drivers>!

Serialisation returns 3 errors!

Settings in config.plist these are referencing are identical in the 0.8.2 and 0.8.3 versions. ocivalidate for 0.8.2 validates the 0.8.3 config.plist without error.

@cdf

Please note that the maintenance section of the first post has not been updated by @cdf for 0.8.3.

 

[PeterHolbrook]

NOTE: This version of ocvalidate is only compatible with OpenCore version 0.8.3!

OCS: No schema for LegacyEnable at 2 index, context <NVRAM>!

OCS: Missing key LoadEarly, context <Drivers>!

OCS: Missing key LoadEarly, context <Drivers>!

Serialisation returns 3 errors!

Yes, I ran ocvalidate myself. Mine returned a lot more errors. Although I suspect they are all minor, I have dared to attempt booting using OC 0.8.3 yet. May try later today.

 

[Gustav Holdoff]

OC 0.8.3 was released yesterday. Are there any changes that require a modification of config.plist?

as far as I read on the hackintosh forums, in this version of opencore,
in order to be able to work with Ventura on a hackintosh with unsupported motherboards (including cMP 5.1),
a fundamentally different work with nvram is organized.
so you need to wait for the config from cdf

 

[streak8047]

USB 1.0 on a Mac Pro 5,1??

As Per Apple Technician Guide MacPro 2009 shows USB 2.0, wired Mouse am using Dell & Logitech .it will was issue dell keyboard was working with out any issue.

 

[PeterHolbrook]

as far as I read on the hackintosh forums, in this version of opencore,
in order to be able to work with Ventura on a hackintosh with unsupported motherboards (including makpro 5.1),
a fundamentally different work with nvram is organized.
so you need to wait for the config from cdf

Indeed. In any case, I've just booted using OC 0.8.3 using my 0.8.2 config.plist. No issues.

 

[cdf]

The guide has been updated to OpenCore version 0.8.3. There are just a few minor changes (see the Maintenance section).

Thanks to the hard work of @Bmju, a notable addition to this version of OC is emulated NVRAM (useful not only for those with firmware chip issues but for touvlophobics as well). Configuration steps will be added to the guide as time permits.

 

[NC12]

As Per Apple Technician Guide MacPro 2009 shows USB 2.0, wired Mouse am using Dell & Logitech .it will was issue dell keyboard was working with out any issue.

The ports on the mac pro are USB 2.0 but to save money often times hardware manufacturers will use the minimum required connection. A keyboard for instance only need USB 1.1 bandwidth so there is no point using USB 2.0. Modern macOS doesn’t support USB 1

 

[joevt]

The ports on the mac pro are USB 2.0 but to save money often times hardware manufacturers will use the minimum required connection. A keyboard for instance only need USB 1.1 bandwidth so there is no point using USB 2.0. Modern macOS doesn’t support USB 1

I thought the problem is more like modern macOS supports USB 1 but it has problems with OHCI USB controllers. Classic Mac has OHCI and EHCI controllers for USB. An OHCI controller is used when a USB 1.1 device is connected. To force the EHCI controller, connect a USB 2.0 hub and connect the USB 1.1 device to the 2.0 hub.

 

[NC12]

I thought the problem is more like modern macOS supports USB 1 but it has problems with OHCI USB controllers. Classic Mac has OHCI and EHCI controllers for USB. An OHCI controller is used when a USB 1.1 device is connected. To force the EHCI controller, connect a USB 2.0 hub and connect the USB 1.1 device to the 2.0 hub.

Wait yeah that is 100% right

 

[6DecadesLater]

Have installed Monterey 12.5 via OTA after OC0.8.3 update.
Used:

• SecureBootModel is set to Default
• Hybridization is used
• Firmware features are updated

Update was smooth and all looks good so far.

As always, many thanks for all the effort.

 

[TECK]

It depends on your workflow. In fact, I have also never got any AVX-related panics that weren't intentionally triggered. As a quick test, try enabling Voice Control (System Preferences > Accessibility > Voice Control).

That makes sense, I don't use that feature. I updated the documentation and added the optional kext as example into build.kexts list of dictionaries:

    build.kexts = [
        {
            'project': 'NoAVXFSCompressionTypeZlib',
            'properties': {
                'MinKernel': '21.5.0'
            },
            'repo': 'dortania',
            'version': '12.3.1'
        }
    ]

 

[novaman_on_da_beat]

Hello everyone, Newbie here... JK! But I wanted make mention that I've been having a lot of trouble installing Big Sur and Monterey on my MacPro 5,1 (2009). When the installation was underway, it would seem as though it would go through the entire installation with no hiccups... until the "support.apple.com" message appeared, causing me to have to reboot (holding down the power button). When my MP rebooted it would resume the installation but I'd have to repeat that process at least 2-3 more times. Needless to say, my MP would eventually complete the installation.

Problems:
Restart does not work properly with Big Sur or Monterey; I have to hold down the power button on each restart to get back into the OS. (Mojave works like a charm!) <---Whenever I run into issues I always use my 10.14.6 BU.

Discovery:
I've discovered that my MP will only restart completely without having to hold down the power button if I had my hard drive (Samsung SSD) plugged in via Sata Cable in one of the USB slots on the front of the MP. When the drive is inserted in one of the bays, it has weird restart behavior and does not restart properly. As mentioned, Monterey will only boot back up normally after clicking Restart when I held down the power button. When I restart Monterey does not restart normally as it should; it hangs and makes me hit the power button.

Questions:
What can I do to get my MP running the OS properly?
Should I reset PRAM before installations? When should this be done?
On page 1 of this "OC on the MP "post, how effective are the settings such as Spoofing and enabling missing features? In this section it gets confusing because 1 sections to FIND one thing, but in another section below it appears as though its telling me to change things I've just changed. Just need a little guidance.

Installation Methods:
OCLP 0.4.9 (OCLP does not install the latest OC package; it installs OC 0.8.0)
OC 0.8.2

Currently Installed:
OCLP 0.4.9
Monterey 12.5 (was able to do an update without a hard boot restart.)

Working Peripherals:
Thunderbolt Titan Ridge 2.0
UAD Audio Interface (have to do some weird cycling and restart)
USB 3.0 Card (gotta find the vendor and model)
Mojave (SSD - Bay 1)
Time Machine Backup (HDD - Bay 3)
WD External USB 3.0 HDD

Can someone tell me what they see in this Problem Report for macOS? I'd like to work on this as well. This happened when I took a nap today. I stepped away after using my MP (Monterey) from 9am to 3pm and returned to find this:

panic(cpu 14 caller 0xffffff8014dd0773): Kernel trap at 0xffffff7fadccfa1b, type 14=page fault, registers:
CR0: 0x000000008001003b, CR2: 0x0000000000000000, CR3: 0x0000000019509000, CR4: 0x00000000000226e0
RAX: 0xffffff9563817500, RBX: 0xfffffff045223be7, RCX: 0xffffff9563817500, RDX: 0x0000000000000006
RSP: 0xfffffff045223b20, RBP: 0xfffffff045223bd0, RSI: 0x0000000000000008, RDI: 0x0000000000000007
R8: 0xffffffd0e768bdf0, R9: 0x00000000ffffffff, R10: 0x0000000000000000, R11: 0x00000000fffffffe
R12: 0x0000000000000000, R13: 0xfffffff045223be7, R14: 0xffffff95638413c0, R15: 0xffffff8bd0567900
RFL: 0x0000000000010206, RIP: 0xffffff7fadccfa1b, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x0000000000000000, Error code: 0x0000000000000002, Fault CPU: 0xe, PL: 0, VF: 1

Panicked task 0xffffff9a2efb3670: 282 threads: pid 0: kernel_task
Backtrace (CPU 14), panicked thread: 0xffffff9564c8c540, Frame : Return Address
0xfffffff0452234d0 : 0xffffff8014c7fd6d mach_kernel : _handle_debugger_trap + 0x41d
0xfffffff045223520 : 0xffffff8014de1016 mach_kernel : _kdp_i386_trap + 0x116
0xfffffff045223560 : 0xffffff8014dd0383 mach_kernel : _kernel_trap + 0x4d3
0xfffffff0452235b0 : 0xffffff8014c1fa70 mach_kernel : _return_from_trap + 0xe0
0xfffffff0452235d0 : 0xffffff8014c8013d mach_kernel : _DebuggerTrapWithState + 0xad
0xfffffff0452236f0 : 0xffffff8014c7f8f6 mach_kernel : _panic_trap_to_debugger + 0x2b6
0xfffffff045223750 : 0xffffff8015514d93 mach_kernel : _panic + 0x84
0xfffffff045223840 : 0xffffff8014dd0773 mach_kernel : _sync_iss_to_iks + 0x2c3
0xfffffff0452239c0 : 0xffffff8014dd0456 mach_kernel : _kernel_trap + 0x5a6
0xfffffff045223a10 : 0xffffff8014c1fa70 mach_kernel : _return_from_trap + 0xe0
0xfffffff045223a30 : 0xffffff7fadccfa1b com.apple.driver.AppleFWOHCI : __ZN19AppleFWOHCI_SendDCL7compileER12IODCLProgramRb + 0xff
0xfffffff045223bd0 : 0xffffff7fadccb847 com.apple.driver.AppleFWOHCI : __ZN22AppleFWOHCI_DCLProgram7compileE9IOFWSpeedj + 0xd7
0xfffffff045223c10 : 0xffffff7fadc91229 com.apple.iokit.IOFireWireFamily : __ZN16IOFWIsochChannel15allocateChannelEv + 0x131
0xfffffff045223c60 : 0xffffff7faed9f129 tc.tctechnologies.driver.Saffire : __ZN7Saffire15AllocateStreamsEv + 0x85f
0xfffffff045223d50 : 0xffffff7faed9e65e tc.tctechnologies.driver.Saffire : __ZN7Saffire16RestartStreamingEv + 0xb5c
0xfffffff045223da0 : 0xffffff7faed9a9ed tc.tctechnologies.driver.Saffire : __ZN7Saffire10TimerFiredEP8OSObjectP18IOTimerEventSource + 0x7d
0xfffffff045223dd0 : 0xffffff801544a0b5 mach_kernel : __ZN18IOTimerEventSource15timeoutSignaledEPvS0_ + 0xa5
0xfffffff045223e40 : 0xffffff8015449fb8 mach_kernel : __ZN18IOTimerEventSource17timeoutAndReleaseEPvS0_ + 0xc8
0xfffffff045223e70 : 0xffffff8014cd2655 mach_kernel : _thread_call_delayed_timer + 0x505
0xfffffff045223ee0 : 0xffffff8014cd3722 mach_kernel : _thread_call_delayed_timer + 0x15d2
0xfffffff045223fa0 : 0xffffff8014c1f19e mach_kernel : _call_continuation + 0x2e
Kernel Extensions in backtrace:
com.apple.iokit.IOFireWireFamily(4.8.3)[35C42C8D-E356-3394-BD5B-2DDD902B1A01]@0xffffff7fadc79000->0xffffff7fadcacfff
com.apple.driver.AppleFWOHCI(5.7.5)[D177DC8F-74E6-336D-BDEA-32EE75BFD8CF]@0xffffff7fadcc3000->0xffffff7fadce2fff
dependency: com.apple.iokit.IOFireWireFamily(4.8.3)[35C42C8D-E356-3394-BD5B-2DDD902B1A01]@0xffffff7fadc79000->0xffffff7fadcacfff
dependency: com.apple.iokit.IOPCIFamily(2.9)[1C239712-AA61-3895-87E3-236603DBD253]@0xffffff8017835000->0xffffff8017861fff
tc.tctechnologies.driver.Saffire(4.3)[3563D1B5-FFE0-380D-B232-6D2D6CF819F7]@0xffffff7faed90000->0xffffff7faeda7fff
dependency: com.apple.iokit.IOAudioFamily(340.2)[2BC68A45-C1C1-30D1-A7A2-B911CFDB04F2]@0xffffff7fadc2c000->0xffffff7fadc49fff
dependency: com.apple.iokit.IOFireWireFamily(4.8.3)[35C42C8D-E356-3394-BD5B-2DDD902B1A01]@0xffffff7fadc79000->0xffffff7fadcacfff

Process name corresponding to current thread (0xffffff9564c8c540): kernel_task
Boot args: keepsyms=1 debug=0x100 -lilubetaall chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
21G72

Kernel version:
Darwin Kernel Version 21.6.0: Sat Jun 18 17:07:25 PDT 2022; root:xnu-8020.140.41~1/RELEASE_X86_64
Kernel UUID: E3E2BC4D-7B6F-39CC-8890-73A6FB513830
KernelCache slide: 0x0000000014a00000
KernelCache base: 0xffffff8014c00000
Kernel slide: 0x0000000014a10000
Kernel text base: 0xffffff8014c10000
__HIB text base: 0xffffff8014b00000
System model name: MacPro5,1 (Mac-27AD2F918AE68F61)
System shutdown begun: NO
Panic diags file available: NO (0xe00002bc)
Hibernation exit count: 0

System uptime in nanoseconds: 39245001035029
Last Sleep: absolute base_tsc base_nano
Uptime : 0x000023b170589769
Sleep : 0x000023aedd2051e3 0x00000000b3d2fed4 0x0000239d8250ee2c
Wake : 0x000023aee5d1222c 0x00000000b4e98a24 0x000023aee2d98f10
Compressor Info: 0% of compressed pages limit (OK) and 0% of segments limit (OK) with 0 swapfiles and OK swap space
Zone info:
Zone map: 0xffffff8092327000 - 0xffffffa092327000
. PGZ : 0xffffff8092327000 - 0xffffff80a2328000
. VM : 0xffffff80a2328000 - 0xffffff856c98e000
. RO : 0xffffff856c98e000 - 0xffffff870565a000
. GEN0 : 0xffffff870565a000 - 0xffffff8bcfcc0000
. GEN1 : 0xffffff8bcfcc0000 - 0xffffff909a326000
. GEN2 : 0xffffff909a326000 - 0xffffff956498c000
. GEN3 : 0xffffff956498c000 - 0xffffff9a2eff3000
. DATA : 0xffffff9a2eff3000 - 0xffffffa092327000
Metadata: 0xffffffd0d2977000 - 0xffffffd0f2977000
Bitmaps : 0xffffffd0f2977000 - 0xffffffd112977000


Thanks again community for your patience and guidance. I look forward to everyone's comment and advice.

 

[joevt]

0xfffffff045223a30 : 0xffffff7fadccfa1b com.apple.driver.AppleFWOHCI : __ZN19AppleFWOHCI_SendDCL7compileER12IODCLProgramRb + 0xff
0xfffffff045223bd0 : 0xffffff7fadccb847 com.apple.driver.AppleFWOHCI : __ZN22AppleFWOHCI_DCLProgram7compileE9IOFWSpeedj + 0xd7
0xfffffff045223c10 : 0xffffff7fadc91229 com.apple.iokit.IOFireWireFamily : __ZN16IOFWIsochChannel15allocateChannelEv + 0x131
0xfffffff045223c60 : 0xffffff7faed9f129 tc.tctechnologies.driver.Saffire : __ZN7Saffire15AllocateStreamsEv + 0x85f
0xfffffff045223d50 : 0xffffff7faed9e65e tc.tctechnologies.driver.Saffire : __ZN7Saffire16RestartStreamingEv + 0xb5c
0xfffffff045223da0 : 0xffffff7faed9a9ed tc.tctechnologies.driver.Saffire : __ZN7Saffire10TimerFiredEP8OSObjectP18IOTimerEventSource + 0x7d
0xfffffff045223dd0 : 0xffffff801544a0b5 mach_kernel : __ZN18IOTimerEventSource15timeoutSignaledEPvS0_ + 0xa5
0xfffffff045223e40 : 0xffffff8015449fb8 mach_kernel : __ZN18IOTimerEventSource17timeoutAndReleaseEPvS0_ + 0xc8
0xfffffff045223e70 : 0xffffff8014cd2655 mach_kernel : _thread_call_delayed_timer + 0x505
0xfffffff045223ee0 : 0xffffff8014cd3722 mach_kernel : _thread_call_delayed_timer + 0x15d2
0xfffffff045223fa0 : 0xffffff8014c1f19e mach_kernel : _call_continuation + 0x2e

Do you have FireWire devices connected? Seems like a bug in the driver tc.tctechnologies.driver.Saffire .

 

[amarmot]

Answering my own post.
NVRAM problem.
Fixed.

I seem to be having a similar problem. Can you explain what you mean by “nvram problem”, and how you overcame it?

 

[novaman_on_da_beat]

Do you have FireWire devices connected? Seems like a bug in the driver tc.tctechnologies.driver.Saffire .

I do have a Saffire FireWire device connected.