Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
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.
Hello guys,
I have gotten USB3 Boot with an FL1100 card working on the MacPro5,1 through OpenCore.

After messing with extracted UEFI drivers from the MacPro6,1 and injecting/installing them with OC, here it is:


View attachment 1933930
View attachment 1933927

can confirm it works :)

of course just with FL1100 cards.

tried USB Keyboard and Mouse on USB3 card with OpenCore and they worked In OC.

booted an USB3 Stick with a Monterey Installer on it and it worked.

also a USB3 - Sata adapter with a Sata SSD booted Montery 12.1 from USB3. Needed to press the space bar to find the device.

Screen Sharing Picture 26. December 2021 at 13.10.59 CET copy.png



injected all 3 efi Drivers.

Edit: after @Dayo mentioned details: Injected Xhci.efi and USBBusDxe.efi
seems UsbMassStorageDxe.efi is not needed, booted an USB Stick and a Big Sur SSD on that same USB3-Sata Adapter
 
Last edited:
  • Like
Reactions: dvbcheck
I tested a USB3 card with VLI VL805-06 controller. To my surprise it also booted an USB thumb drive.

USB3 - Sata adapter with Monterey 12.1 did not boot, it spit various USB errors in verbose mode.


---

and tested a USB3 card with asm1142 USB 3 / USB C

this thing booted the USB3 thumb drive, the USB3 - Sata adapter dont started to boot.

A USB2 - Sata adapter booted Monterey 12.1


don't have too much USB3 stuff here at home, but that's worth some more testing even with none FL1100 USB3 cards.
 
Last edited:
View attachment 1933710View attachment 1933711
Hi,

cMac Pro 5.1 OCLP 0.7.6

BCM94360CD It works fine in Big Sur and Monterey. It doesn't show Handoff and other features in Monterey, but it works. What could be the reason for this?
cMP with Monterey 12.1 set up via post #1. BCM94360CD works for mouse and keyboard but sometimes it doesn't work prior to log in (keep a USB keyboard and mouse connected for backup). Handoff still works on my old iPad mini 4 and on my iPhone 13. Safari logo showing iPhone or iPad Handoff available used to appear on left side of dock but is now on the right and is seen with Command-T to toggle apps.
Tried pairing my iPhone13 to the cMP. It briefly connected and then disconnected. Removed iPhone from BT list on cMP and iPhone and tried again. iPhone now tries to connect then says the cMP is not supported. But as above, Handoff works.
 
Hello guys,
I have gotten USB3 Boot with an FL1100 card working on the MacPro5,1 through OpenCore.

Edit: Testing from @Macschrauber shows that booting from VLI-based cards also works, if you have a USB3 card that isn't made by Fresco Logic or VLI, feel free to give the drivers a shot

Drivers are linked in this post: https://forums.macrumors.com/thread....2207814/page-391?post=30677096#post-30677096

After messing with extracted UEFI drivers from the MacPro6,1 and injecting/installing them with OC, here it is:


View attachment 1934236
View attachment 1933927
Works in the same way with iMac12,2 and FL1100 based legato thunderbolt 2 dock!
 
  • Like
Reactions: Macschrauber
Hello guys,
I have gotten USB3 Boot with an FL1100 card working on the MacPro5,1 through OpenCore.

Edit: Testing from @Macschrauber shows that booting from VLI-based cards also works, if you have a USB3 card that isn't made by Fresco Logic or VLI, feel free to give the drivers a shot

Drivers are linked in this post: https://forums.macrumors.com/thread....2207814/page-391?post=30677096#post-30677096

After messing with extracted UEFI drivers from the MacPro6,1 and injecting/installing them with OC, here it is:


View attachment 1934236
View attachment 1933927
Where are the drivers installed and how?

Thanks
 
Where are the drivers installed and how?
Read the OpenCore documentation - install them like the other EFI Drivers in the OC folder are installed - you'll have to edit the config.plist file as well.

Another option is to load the drivers using the NVRAM Driver#### boot variables.
https://forums.macrumors.com/threads/mac-pro-3-1-nvme-support-upgrade-guide-questions.2194878/
These will load before OpenCore or even the Apple Startup Manager (hold Option key at boot).

I haven't tried these drivers using either method so I don't know if there'll be a problem.
 
Where are the drivers installed and how?

Thanks

@Ausdauersportler posted something:

 
Hi, I have a Mac Pro 5.1 with Big Sur 11.6.1 with OCLP 0.33.
After 30 minutes or so of working and I select a file that is on my NVME on my PCI 3 the finder goes black and I have to turn off the computer with the button. do you have any solution? Thanks!
 
Hi, I have a Mac Pro 5.1 with Big Sur 11.6.1 with OCLP 0.33.
After 30 minutes or so of working and I select a file that is on my NVME on my PCI 3 the finder goes black and I have to turn off the computer with the button. do you have any solution? Thanks!
I would check the OCLP discord. This thread is focused on the method outlined in post #1. You won't get much OCLP advice here.
 
Read the OpenCore documentation - install them like the other EFI Drivers in the OC folder are installed - you'll have to edit the config.plist file as well.

Another option is to load the drivers using the NVRAM Driver#### boot variables.
https://forums.macrumors.com/threads/mac-pro-3-1-nvme-support-upgrade-guide-questions.2194878/
These will load before OpenCore or even the Apple Startup Manager (hold Option key at boot).

I haven't tried these drivers using either method so I don't know if there'll be a problem.
Can confirm that the OpenCore approach works, but I struggle to get the NVRAM Driver#### boot variable method working.

I mounted my EFI partition, created a directory named drivers, put all the EFI drivers into it:

Code:
install@P2 ~ % ls -sl /Volumes/EFI/drivers
total 659
 79 -rwxrwxrwx@ 1 install  staff   40260  7 Mai  2020 CoreEG2_x64.efi
 15 -rwxrwxrwx@ 1 install  staff    7204  7 Mai  2020 EDIDParser_x64.efi
362 -rwxrwxrwx@ 1 install  staff  185344  9 Dez 14:44 M370.efi
 50 -rwxrwxrwx@ 1 install  staff   25540  6 Dez 17:40 UsbBusDxe.efi
 25 -rwxrwxrwx@ 1 install  staff   12356  6 Dez 18:16 UsbMassStorageDxe.efi
 59 -rwxrwxrwx@ 1 install  staff   29924  6 Dez 17:39 XhciDxe.efi

added the drivers using your tools

Code:
install@P2 ~ % source ~/Downloads/gfxutil.sh
install@P2 ~ % setbootvar Driver0080 1 "UsbBusDxe.efi" /Volumes/EFI/drivers/UsbBusDxe.efi
install@P2 ~ % setbootvar Driver0081 1 "UsbMassStorageDxe.efi" /Volumes/EFI/drivers/UsbMassStorageDxe.efi
install@P2 ~ % setbootvar Driver0082 1 "XhciDxe.efi" /Volumes/EFI/drivers/XhciDxe.efi
install@P2 ~ % setdriverorder Driver0080 Driver0081 Driver0082

install@P2 ~ % dumpallbootvars            
BootCurrent: 
BootNext: 
Timeout: 5s

BootOrder: Boot0080
Boot0080 1 "Big Sur" "PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,D5C9EEDB-B461-4407-A746-A500430BE195,0x64028,0x3A321FE0)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,27AB7AA975BA884EA8273EC23D02C804)/\DDB4E1A5-A81D-49DD-8F60-62261C772D17\System\Library\CoreServices\boot.efi"
#Searching: Boot0000(1), Boot007F(-1), Boot0081(1)
Boot0081 1 "Mac OS X" "PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(1,GPT,198B56A2-6B68-4FF0-90A3-01296E64E13F,0x28,0x64000)/\drivers\UsbBusDxe.efi"
#Searching: BootFFFF(-1)

DriverOrder: Driver0080 Driver0081 Driver0082
Driver0080 1 "UsbBusDxe.efi" "PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(1,GPT,198B56A2-6B68-4FF0-90A3-01296E64E13F,0x28,0x64000)/\drivers\UsbBusDxe.efi"
Driver0081 1 "UsbMassStorageDxe.efi" "PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(1,GPT,198B56A2-6B68-4FF0-90A3-01296E64E13F,0x28,0x64000)/\drivers\UsbMassStorageDxe.efi"
Driver0082 1 "XhciDxe.efi" "PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(1,GPT,198B56A2-6B68-4FF0-90A3-01296E64E13F,0x28,0x64000)/\drivers\XhciDxe.efi"
#Searching: Driver0000(1), Driver007F(-1), Driver0083(1), DriverFFFF(-1)

but on the OC boot picker the USB3 devices are not shown while this works pretty well with OpenCore injection of the same drivers.

Really want to get this working to get a better understanding of the method :)
 
Can confirm that the OpenCore approach works, but I struggle to get the NVRAM Driver#### boot variable method working.

I mounted my EFI partition, created a directory named drivers, put all the EFI drivers into it:

Code:
install@P2 ~ % ls -sl /Volumes/EFI/drivers
total 659
 79 -rwxrwxrwx@ 1 install  staff   40260  7 Mai  2020 CoreEG2_x64.efi
 15 -rwxrwxrwx@ 1 install  staff    7204  7 Mai  2020 EDIDParser_x64.efi
362 -rwxrwxrwx@ 1 install  staff  185344  9 Dez 14:44 M370.efi
 50 -rwxrwxrwx@ 1 install  staff   25540  6 Dez 17:40 UsbBusDxe.efi
 25 -rwxrwxrwx@ 1 install  staff   12356  6 Dez 18:16 UsbMassStorageDxe.efi
 59 -rwxrwxrwx@ 1 install  staff   29924  6 Dez 17:39 XhciDxe.efi

added the drivers using your tools

Code:
install@P2 ~ % source ~/Downloads/gfxutil.sh
install@P2 ~ % setbootvar Driver0080 1 "UsbBusDxe.efi" /Volumes/EFI/drivers/UsbBusDxe.efi
install@P2 ~ % setbootvar Driver0081 1 "UsbMassStorageDxe.efi" /Volumes/EFI/drivers/UsbMassStorageDxe.efi
install@P2 ~ % setbootvar Driver0082 1 "XhciDxe.efi" /Volumes/EFI/drivers/XhciDxe.efi
install@P2 ~ % setdriverorder Driver0080 Driver0081 Driver0082

install@P2 ~ % dumpallbootvars            
BootCurrent: 
BootNext: 
Timeout: 5s

BootOrder: Boot0080
Boot0080 1 "Big Sur" "PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,D5C9EEDB-B461-4407-A746-A500430BE195,0x64028,0x3A321FE0)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,27AB7AA975BA884EA8273EC23D02C804)/\DDB4E1A5-A81D-49DD-8F60-62261C772D17\System\Library\CoreServices\boot.efi"
#Searching: Boot0000(1), Boot007F(-1), Boot0081(1)
Boot0081 1 "Mac OS X" "PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(1,GPT,198B56A2-6B68-4FF0-90A3-01296E64E13F,0x28,0x64000)/\drivers\UsbBusDxe.efi"
#Searching: BootFFFF(-1)

DriverOrder: Driver0080 Driver0081 Driver0082
Driver0080 1 "UsbBusDxe.efi" "PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(1,GPT,198B56A2-6B68-4FF0-90A3-01296E64E13F,0x28,0x64000)/\drivers\UsbBusDxe.efi"
Driver0081 1 "UsbMassStorageDxe.efi" "PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(1,GPT,198B56A2-6B68-4FF0-90A3-01296E64E13F,0x28,0x64000)/\drivers\UsbMassStorageDxe.efi"
Driver0082 1 "XhciDxe.efi" "PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(1,GPT,198B56A2-6B68-4FF0-90A3-01296E64E13F,0x28,0x64000)/\drivers\XhciDxe.efi"
#Searching: Driver0000(1), Driver007F(-1), Driver0083(1), DriverFFFF(-1)

but on the OC boot picker the USB3 devices are not shown while this works pretty well with OpenCore injection of the same drivers.

Really want to get this working to get a better understanding of the method :)
Are they in the same order as OpenCore config?
Do you have a RefindPlus install to check if the drivers got loaded (using a EFIShell)?
Which Mac are you trying this with?
I've only tried Driver#### on my MacPro3,1 with the apfs.efi driver so that APFS volumes will appear in the Apple Startup Manager (such as Catalina).
Maybe another driver needs to be added to do some work that OpenCore does to get those drivers working.
 
Are they in the same order as OpenCore config?
Do you have a RefindPlus install to check if the drivers got loaded (using a EFIShell)?
Which Mac are you trying this with?
I've only tried Driver#### on my MacPro3,1 with the apfs.efi driver so that APFS volumes will appear in the Apple Startup Manager (such as Catalina).
Maybe another driver needs to be added to do some work that OpenCore does to get those drivers working.
Great you came back!!

I have OpenCore running and it offers the EfiShell access, too. What do I have to do there, just reading the EfiShell docs but uncertain how manage it.

- the only other drivers loaded by OpenCore are OpenCanopy and OpenRuntime
- USB driver load order is the same, tried already permutations
- renamed files to have small letters and 8:3

Edit:
Efishell drivers command does not show the Xhci driver loaded, just the USB Bus Driver and the USB Cbi0 Mass Storage Driver.
 
Last edited:
I'm suffering from a guilty conscience because I wandered off topic in a thread on Continuity & Handoff on a Mac Pro talking about OpenCore so I thought I'd pose my questions in the OpenCore thread...lets hope I don't get told off for cross-posting! ;)

System as signature but reproduced here for ease of reading;

Original 5,1 Mac Pro 2010
Dual X5690 3.46GHz 12-Core Xeon
96GB Samsung ECC RDIMM
1TB Samsung 970 Pro NVMe M.2 booting 10.13.6 High Sierra PCIe Slot 4
2TB Samsung 860 EVO SATA Drive Bay 2
16TB Seagate EXOS SATA Drive Bay 1
NVIDIA Quadro NVS 510 PCIe Slot 1
Sonnet Allegro USB 3.2 PCIe Slot 3
BCM94360CD 802.11ac & Bluetooth 4.0

I recently bought my cMP from a Mac Reseller here in the UK and only discovered it was running OpenCore when I was looking for the Boot ROM version in System Report to find it listed as 9144.0.7.3.1 when I expected to see 144.0.0.0.0 and after some research realised that OpenCore was spoofing the ROM version. I was somewhat disappointed that it had been installed as nothing had been mentioned and I thought I was buying a 'factory reconditioned' Mac Pro and not one that depended on a 3rd party utility for various functions.

Now as I have a Quadro NVS 510 and don't need any AMD GPU acceleration and am running 10.13.6 High Sierra I am left wondering whether I could/should disable/remove OpenCore altogether and run my cMP as Apple designed it and I prefer it?

I am quite happy to stay with High Sierra as it is tried & tested here as my 2011 iMac won't run 10.14 Mojave or above and I have held my other Macs at High Sierra because of this but part of me wonders whether I could still upgrade the cMP to Mojave if the idea ever took me without the help of OpenCore?

If yes then I'm happy to temporarily disable OpenCore for now...in fact I'll go further and say I might just remove it anyway if my current config will work properly without it. I don't even know which version of OpenCore is installed because the usual command line nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version returns the error nvram: Error getting variable - '4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version': (iokit/common) data was not found and it looks like I have to edit a config or plist file just to get round this restriction. Another reason to uninstall OpenCore IMHO.

In essence is there an easy way to temporarily disable OpenCore and re-enable it if I find I can't live without it?

And if I decide to remove it altogether how best do I go about it and might it impact installing Windows at a later date?

I realise most of the questions here will be about installing rather than removing OpenCore but then I've never conformed to anything like normal in my life! ?

Thanks & kind regards,
-=Glyn=-
 
Last edited:
Great you came back!!

I have OpenCore running and it offers the EfiShell access, too. What do I have to do there, just reading the EfiShell docs but uncertain how manage it.

- the only other drivers loaded by OpenCore are OpenCanopy and OpenRuntime
- USB driver load order is the same, tried already permutations
- renamed files to have small letters and 8:3
In OpenShell,
type help to get a list of commands.
type help drivers to get help with the drivers command.
type devices to get a list of devices. See if the USB controller is listed.
type dh to get a list of handles. some of those handles should be for the drivers.

try to find the file system that is your EFI partition.
map will output a bunch of aliases. Starting with fs0: list the contents of the directory to see if it is the EFI partition.
ls fs0:
(I think OpenShell should add a diskutil list command that can relate the file system aliases and volume names with the block devices in disk/partition order)
Anyway, if it is the EFI partition, then set the current file system:
fs0:
Then you can pipe the output of the shell commands to text files in the EFI partition.
help > help.txt
dh > dh.txt
Then you can share the files with us if there's anything interesting (because screenshots are dumb).
 
  • Like
Reactions: Ausdauersportler
In OpenShell,
type help to get a list of commands.
type help drivers to get help with the drivers command.
type devices to get a list of devices. See if the USB controller is listed.
type dh to get a list of handles. some of those handles should be for the drivers.

try to find the file system that is your EFI partition.
map will output a bunch of aliases. Starting with fs0: list the contents of the directory to see if it is the EFI partition.
ls fs0:
(I think OpenShell should add a diskutil list command that can relate the file system aliases and volume names with the block devices in disk/partition order)
Anyway, if it is the EFI partition, then set the current file system:
fs0:
Then you can pipe the output of the shell commands to text files in the EFI partition.
help > help.txt
dh > dh.txt
Then you can share the files with us if there's anything interesting (because screenshots are dumb).
- fs0: is the EFI partition and I had access (otherwise I could not have attached the files you asked for)
- tried at the very end to load the xhcidxe.efi from disk and got successfully loaded message but the shell stuck

Took while through that loop:

Code:
Handle dump
01: 6C6148A4-97B8-429C-955E-4103E8ACA0FA LoadedImage
02: 5CB5C776-60D5-45EE-883C-452708CD743F
03: Decompress
04: E84CF29C-191F-4EAE-96E1-F46AECEAEA0B
05: 9A44198E-A4A2-44E6-8A1F-39BEFDAC896F
06: F496922D-172F-4BBC-A1EB-0EEB949C3486 53A4C71B-B581-4170-91B3-8DB87A4B5C46 389F751F-1838-4388-8390-CD8154BD27F8 7AA35A69-506C-444F-A7AF-694BF56F71C8 DevicePath(..d(0xB,0xFF981000,0xFFC8FFFF)) DE28BC59-6228-41BD-BDF6-A3B9ADB58DA1
07: F496922D-172F-4BBC-A1EB-0EEB949C3486 53A4C71B-B581-4170-91B3-8DB87A4B5C46 7AA35A69-506C-444F-A7AF-694BF56F71C8 DevicePath(..d(0xB,0xFFED8000,0xFFEFFFFF)) DE28BC59-6228-41BD-BDF6-A3B9ADB58DA1
08: 448F5DA4-6DD7-4FE1-9307-69224192215D
09: FFECFFFF-923C-14D2-9E3F-22A0C969563B
0A: LoadedImage
0B: B0732526-38C8-4B40-8877-61C7B06AAC45
0C: LoadedImage
0D: RuntimeArch
0E: LoadedImage
0F: FC1BCDB0-7D31-49AA-936A-A4600D9DD083
10: LoadedImage
11: AE80D021-618E-11D4-BCD7-0080C73C8881
12: LoadedImage
13: SmartCardReader
14: DA333D99-25F6-4BD0-BB24-7C70C6F14EAB
15: LoadedImage
16: LoadedImage
17: 470E1529-B79E-4E32-A0FE-6A156D29F9B2
18: LoadedImage
19: SecurityArch
1A: LoadedImage
1B: EBBE2D1B-1647-4BDA-AB9A-7863E396D41A
1C: B42B8D12-2ACB-499A-A920-DD5BE6CF09B1 LoadedImage
1D: LoadedImage
1E: LoadedImage
1F: DF2D868E-32FC-4CF0-8E6B-FFD95D1343D0
20: 466F3AEC-C266-4BAB-9984-A74031000206 LoadedImage
21: DebugSupport EBCInterpreter LoadedImage
22: LoadedImage
23: EA816D2C-CEE5-4F02-99B5-D3905CBBD077
24: DriverBinding DevicePath(..478A-4333-9062-155C47ECB4F7)) LoadedImage
25: LoadedImage
26: 8ECE08D8-A6D4-430B-A7B0-2DF318E7884A LoadedImage
27: BdsArch
28: LoadedImage
29: MetronomeArch
2A: LoadedImage
2B: 38321DBA-4FE0-4E17-8AEC-413055EAEDC1
2C: LoadedImage
2D: 1156EFC6-EA32-4396-B5D5-26932E83C313
2E: LoadedImage
2F: LoadedImage
30: F496922D-172F-4BBC-A1EB-0EEB949C3486 53A4C71B-B581-4170-91B3-8DB87A4B5C46 DE28BC59-6228-41BD-BDF6-A3B9ADB58DA1 DevicePath(..d(0xB,0xFFE82000,0xFFE91FFF))
31: F496922D-172F-4BBC-A1EB-0EEB949C3486 53A4C71B-B581-4170-91B3-8DB87A4B5C46 389F751F-1838-4388-8390-CD8154BD27F8 DE28BC59-6228-41BD-BDF6-A3B9ADB58DA1 DevicePath(..d(0xB,0xFFE92000,0xFFE94FFF))
32: F496922D-172F-4BBC-A1EB-0EEB949C3486 53A4C71B-B581-4170-91B3-8DB87A4B5C46 389F751F-1838-4388-8390-CD8154BD27F8 DE28BC59-6228-41BD-BDF6-A3B9ADB58DA1 DevicePath(..d(0xB,0xFFE95000,0xFFE97FFF))
33: F496922D-172F-4BBC-A1EB-0EEB949C3486 53A4C71B-B581-4170-91B3-8DB87A4B5C46 389F751F-1838-4388-8390-CD8154BD27F8 DE28BC59-6228-41BD-BDF6-A3B9ADB58DA1 DevicePath(..d(0xB,0xFFF00000,0xFFF6FFFF))
34: F496922D-172F-4BBC-A1EB-0EEB949C3486 53A4C71B-B581-4170-91B3-8DB87A4B5C46 389F751F-1838-4388-8390-CD8154BD27F8 DE28BC59-6228-41BD-BDF6-A3B9ADB58DA1 DevicePath(..d(0xB,0xFFF70000,0xFFFDFFFF))
35: F496922D-172F-4BBC-A1EB-0EEB949C3486 53A4C71B-B581-4170-91B3-8DB87A4B5C46 389F751F-1838-4388-8390-CD8154BD27F8 DE28BC59-6228-41BD-BDF6-A3B9ADB58DA1 DevicePath(..d(0xB,0xFFFE0000,0xFFFEFFFF))
36: F496922D-172F-4BBC-A1EB-0EEB949C3486 53A4C71B-B581-4170-91B3-8DB87A4B5C46 389F751F-1838-4388-8390-CD8154BD27F8 DE28BC59-6228-41BD-BDF6-A3B9ADB58DA1 DevicePath(..d(0xB,0xFFFF0000,0xFFFFFFFF))
37: LoadedImage
38: 3489A5BC-18F8-45C4-BFBD-ED74512C180C PciHostBridgeResourceAllocation
39: PCIRootBridgeIO(PciRootBridgeIo) DevicePath(PciRoot(0x0))
3A: LoadedImage
3B: 3792095A-E309-4C1E-AA01-85F5655A17F1
3C: LoadedImage
3D: E121EC07-9C42-45EE-B0B6-FFF8EF03C521
3E: LoadedImage
3F: 11FBFDFB-10D2-43E6-B5B1-B4386EDCCB9A D08B4902-5C78-402C-B6EC-3DA3B1B1BC32 CFB33810-6E87-4284-B203-A66ABE07F6E8
40: LoadedImage
41: AC5E4829-A8FD-440B-AF33-9FFE013B12D8
42: 37FA0524-D0CE-4A7A-A6DF-40E5EEA88618 LoadedImage
43: LoadedImage
44: 309DE7F1-7F5E-4ACE-B49C-531BE5AA95EF
45: LoadedImage
46: A9FBF34B-E2A2-41D1-BA00-A274A55CD164
47: LoadedImage
48: F8BFF014-18FB-4EF9-B10C-AE22738DBEED
49: LoadedImage
4A: E4518E76-19D8-4475-9094-73BDABDC3B0C
4B: LoadedImage
4C: C23DA58D-AEB4-4629-B115-01475FF20ABA
4D: VariableWriteArch VariableArch
4E: LoadedImage
4F: 9D7B16E6-3473-4035-BA63-7D6A3BA39498
50: E287D20B-D897-4E1E-A5D9-977763936A04 LoadedImage
51: LoadedImage
52: LoadedImage
53: MonotonicCounterArch
54: LoadedImage
55: D31F0400-7D16-4316-BF88-6065883B402B 5572E711-E375-436F-A99F-61FE0AF6A236 6F20F7C8-E5EF-4F21-8D19-EDC5F0C496AE CD2333D7-6A0A-4C76-8350-240ADA36A2C7 6F27E990-7BC8-42C9-8F71-9980063693E9 4B0165A9-61D6-4E23-A0B5-3EC79C2E30D5
56: 10F2B315-792D-40E4-A319-A9946F775E35
57: LoadedImage
58: SmbusHc
59: LoadedImage
5A: F0BBFCA0-684E-48B3-BAE2-6C84B89E5339
5B: ResetArch
5C: LoadedImage
5D: CpuArch
5E: 2C105279-89DD-460C-8985-B47296B429A8 F33261E7-23CB-11D5-BD5C-0080C73C8881
5F: LoadedImage
60: 125F2DE1-FB85-440C-A54C-4D99358A8D38
61: LoadedImage
62: TimerArch
63: LoadedImage
64: RealTimeClockArch
65: 2F18B731-C475-41F6-A210-69212F2E7796 LoadedImage
66: LoadedImage
67: LoadedImage
68: 066E1E40-FF9A-48F3-B9BF-2A677379C1BC
69: LoadedImage
6A: WatchdogTimerArch
6B: 75FAB4B4-6AC1-429A-A000-6B0B95E71CA1 LoadedImage
6C: 8D12E231-C667-4FD1-98F2-2449A7E7B2E5 LoadedImage
6D: LoadedImage
6E: 31CE593D-108A-485D-ADB2-78F21F2966BE
6F: ComponentName DriverBinding LoadedImage
70: LoadedImage
71: EF19DAF2-28DE-40B6-B591-0C747D4CD9E1
72: LoadedImage
73: DBFF9D55-89B7-46DA-BDDF-677D3DC0241D
74: LoadedImage
75: 91BD12FE-F6C3-44FB-A5B7-5122AB303AE0
76: LoadedImage
77: 5B213447-6E73-4901-A4F1-B864F3B7A172 584B9EBE-80C1-4BD6-98B0-A7786EC2F2E2
78: 08F9977D-1141-4E84-9376-5706CCC388AD LoadedImage
79: 89342532-E9D4-447F-A856-0D98CF1341EF
7A: LoadedImage
7B: FAC84806-0C21-4A00-8719-6F56E27FADDC
7C: LoadedImage
7D: F76761DC-FF89-44E4-9C0C-CD0ADA4EF983
7E: ComponentName DriverBinding LoadedImage
7F: ComponentName DriverBinding LoadedImage
80: 89342532-E9D4-447F-A856-0D98CF1341EF
81: LoadedImage
82: PciPlatform
83: ComponentName DriverBinding LoadedImage
84: LoadedImage
85: IncompatiblePciDeviceSupport
86: ComponentName DriverBinding LoadedImage
87: PciHotPlugRequest
88: ComponentName DriverBinding LoadedImage
89: ComponentName DriverBinding LoadedImage
8A: ComponentName DriverBinding LoadedImage
8B: ComponentName DriverBinding LoadedImage
8C: 89342532-E9D4-447F-A856-0D98CF1341EF
8D: ComponentName DriverBinding LoadedImage
8E: ComponentName DriverBinding LoadedImage
8F: DriverBinding LoadedImage
90: ComponentName DriverBinding LoadedImage
91: ComponentName DriverBinding LoadedImage
92: ComponentName DriverBinding LoadedImage
93: DriverBinding LoadedImage
94: ComponentName DriverBinding LoadedImage
95: ComponentName DriverBinding LoadedImage
96: ComponentName DriverBinding LoadedImage
97: ComponentName DriverBinding LoadedImage
98: ComponentName DriverBinding LoadedImage
99: 7737B6C2-5731-4A19-AF2D-70E4AE1B5670 449D678A-190E-4C4B-98CB-7529EC2DCC2E LoadedImage
9A: ComponentName DriverBinding LoadedImage
9B: ComponentName DriverBinding LoadedImage
9C: DriverBinding LoadedImage
9D: 957932CC-7E8E-433B-8F41-D391EA3C10F8 LoadedImage
9E: 004B07E8-0B9C-427E-B0D4-A466E6E57A62 LoadedImage
9F: DriverBinding LoadedImage
A0: 7542A2BB-D260-4CC2-896E-D613CD515069
A1: LoadedImage
A2: 17407E5A-AF6C-4EE8-98A8-00210453CDD9
A3: ComponentName DriverBinding LoadedImage
A4: ComponentName DriverBinding
A5: ComponentName DriverBinding LoadedImage
A6: ComponentName DriverBinding
A7: ComponentName DriverBinding
A8: ComponentName DriverBinding
A9: 5A68191B-9B97-4752-9946-E36A5DA942B1 SimpleTextOut
AA: E451DCBE-96A1-4729-A5CF-6B9C2CFF47FD SimplePointer SimpleTextIn
AB: 62BDF38A-E3D5-492C-950C-23A7F66E672E F42F7782-012E-4C12-9956-49F94304F721 GraphicsOutput(GraphicsOutput) SimpleTextOut
AC: ComponentName DriverBinding LoadedImage
AD: ComponentName DriverBinding LoadedImage
AE: ComponentName DriverBinding LoadedImage
AF: ComponentName DriverBinding LoadedImage
B0: ComponentName DriverBinding LoadedImage
B1: LoadedImage
B2: UnicodeCollation
B3: LoadedImage
B4: 89342532-E9D4-447F-A856-0D98CF1341EF
B5: LoadedImage
B6: HashServiceBinding
B7: LoadedImage
B8: 86DE9EF3-E869-440F-836A-8B09AF7D2770 998C6D8C-5500-4145-953E-B875517A7A34 LoadedImage
B9: LoadedImage
BA: DriverBinding LoadedImage
BB: 8FFEEB3A-4C98-4630-803F-740F9567091D LoadedImage
BC: LoadedImage
BD: 89342532-E9D4-447F-A856-0D98CF1341EF
BE: DriverBinding LoadedImage
BF: ComponentName DriverBinding LoadedImage
C0: 89342532-E9D4-447F-A856-0D98CF1341EF
C1: ComponentName DriverBinding LoadedImage
C2: ComponentName DriverBinding LoadedImage
C3: 89342532-E9D4-447F-A856-0D98CF1341EF
C4: ComponentName DriverBinding LoadedImage
C5: LoadedImage
C6: LoadedImage
C7: LoadedImage
C8: 074E1E48-8132-47A1-8C2C-3F14AD9A66DC
C9: LoadedImage
CA: 691E1AF0-8673-4C98-A9B3-042620E91498
CB: 910C9421-E512-4B29-9B2F-401CEE33D1DB 1390954D-DA95-4227-9328-7282C217DAA8 9CC55D7D-FBFF-431C-BC14-334EAEA6052B C1BDD34E-9EC0-48AA-806A-6C2EBA0DC445 LoadedImage
CC: 7FED72EE-0170-4814-9878-A8FB1864DFAF LoadedImage
CD: LoadedImage
CE: 21F302AD-6E94-471B-84BC-B14800403A1D LoadedImage
CF: D9DFF88F-F988-4995-A09F-0A018CCD4BBC ComponentName DriverBinding LoadedImage
D0: A4BB4654-9F72-4BC8-93EB-659FD8708B10
D1: LoadedImage
D2: PciHotPlugInit
D3: LoadedImage
D4: EFA6D060-4841-474B-9724-E1E40431C661
D5: LoadedImage
D6: 290AB2CB-6622-4D6B-AFA9-0008DFF11213
D7: LoadedImage
D8: LoadedImage
D9: LoadedImage
DA: A05B6FFD-87AF-4E42-95C9-6228B63CF3F3 9CCA03FC-4C9E-4A19-9B06-ED7B479BDE55 3920405B-C897-44DA-88F3-4C498A6FF736 C50B323E-9075-4F2A-AC8E-D2596A1085CC E541B773-DD11-420C-B026-DF993653F8BF 14FC52BE-01DC-426C-91AE-A23C3E220AE8 E0744B81-9513-49CD-8CEA-E9245E7039DA
DB: LoadedImage
DC: LoadedImage
DD: LoadedImage
DE: LoadedImage
DF: LoadedImage
E0: LoadedImage
E1: SmmIoTrapDispatch2
E2: LoadedImage
E3: LoadedImage
E4: LoadedImage
E5: LoadedImage
E6: D71DB106-E32D-4225-BFF4-DE6D77871761
E7: 493B5BAC-BB9E-4BF5-8379-20E2ACA98541 LoadedImage
E8: 0FC9013A-0568-4BA9-9B7E-C9C390A6609B
E9: CDC5DDDF-E79D-41EC-A9B0-6565490DB9D3
EA: LoadedImage
EB: D43E09B0-8B11-461D-8AC6-B34E97230B8F
EC: 356A1A6B-6C51-4964-9B6E-D623A0566E11 63FAECF2-E7EE-4CB9-8A0C-11CE5E89E33C ComponentName LoadedImage
ED: DriverBinding
EE: DriverBinding
EF: DriverBinding
F0: DriverBinding ComponentName LoadedImage
F1: PCIIO DevicePath(PciRoot(0x0)/Pci(0x0,0x0))
F2: PCIIO DevicePath(PciRoot(0x0)/Pci(0x1,0x0))
F3: A3249A94-CB66-43FC-92F3-8BA1889FD6C7 53CFEB0D-9B9E-4D0A-90B6-024A79906A58 BusSpecificDriverOverride PCIIO DevicePath(..0)/Pci(0x1,0x0)/Pci(0x0,0x0))
F4: PCIIO DevicePath(..0)/Pci(0x1,0x0)/Pci(0x0,0x1))
F5: PCIIO DevicePath(PciRoot(0x0)/Pci(0x2,0x0))
F6: PCIIO DevicePath(PciRoot(0x0)/Pci(0x16,0x0))
F7: PCIIO DevicePath(PciRoot(0x0)/Pci(0x16,0x1))
F8: PCIIO DevicePath(PciRoot(0x0)/Pci(0x16,0x3))
F9: 2B2F68CC-0CD2-44CF-8E8B-BBA20B1B5B75 USBHostController2 USBHostControler PCIIO DevicePath(PciRoot(0x0)/Pci(0x1A,0x0))
FA: 2B2F68CC-0CD2-44CF-8E8B-BBA20B1B5B75 USBHostController2 USBHostControler PCIIO DevicePath(PciRoot(0x0)/Pci(0x1A,0x1))
FB: 2B2F68CC-0CD2-44CF-8E8B-BBA20B1B5B75 USBHostController2 USBHostControler PCIIO DevicePath(PciRoot(0x0)/Pci(0x1A,0x2))
FC: 2B2F68CC-0CD2-44CF-8E8B-BBA20B1B5B75 USBHostController2 PCIIO DevicePath(PciRoot(0x0)/Pci(0x1A,0x7))
FD: PCIIO DevicePath(PciRoot(0x0)/Pci(0x1B,0x0))
FE: PCIIO DevicePath(PciRoot(0x0)/Pci(0x1C,0x0))
FF: PCIIO DevicePath(..)/Pci(0x1C,0x0)/Pci(0x0,0x0))
100: PCIIO DevicePath(PciRoot(0x0)/Pci(0x1C,0x1))
101: PCIIO DevicePath(..)/Pci(0x1C,0x1)/Pci(0x0,0x0))
102: PCIIO DevicePath(PciRoot(0x0)/Pci(0x1C,0x2))
103: 67708AA8-2079-4E4F-B158-B15B1F6A6C92 6599E869-96CA-4D13-90FD-AA9A07555903 PCIIO DevicePath(..)/Pci(0x1C,0x2)/Pci(0x0,0x0))
104: 2B2F68CC-0CD2-44CF-8E8B-BBA20B1B5B75 USBHostController2 USBHostControler PCIIO DevicePath(PciRoot(0x0)/Pci(0x1D,0x0))
105: 2B2F68CC-0CD2-44CF-8E8B-BBA20B1B5B75 USBHostController2 USBHostControler PCIIO DevicePath(PciRoot(0x0)/Pci(0x1D,0x1))
106: 2B2F68CC-0CD2-44CF-8E8B-BBA20B1B5B75 USBHostController2 USBHostControler PCIIO DevicePath(PciRoot(0x0)/Pci(0x1D,0x2))
107: 2B2F68CC-0CD2-44CF-8E8B-BBA20B1B5B75 USBHostController2 USBHostControler PCIIO DevicePath(PciRoot(0x0)/Pci(0x1D,0x3))
108: 2B2F68CC-0CD2-44CF-8E8B-BBA20B1B5B75 USBHostController2 PCIIO DevicePath(PciRoot(0x0)/Pci(0x1D,0x7))
109: ISAACPI PCIIO DevicePath(PciRoot(0x0)/Pci(0x1F,0x0))
10A: 372143D2-B1EA-43AD-BA13-DA06904CBDA1 PCIIO DevicePath(PciRoot(0x0)/Pci(0x1F,0x2))
10B: PCIIO DevicePath(PciRoot(0x0)/Pci(0x1F,0x3))
10C: PCIIO DevicePath(PciRoot(0x0)/Pci(0x1F,0x6))
10D: PCIIO DevicePath(PciRoot(0x0)/Pci(0x1C,0x4))
10E: 9F31F04E-0E3A-4EE2-A68A-95DF08C8E2C6 PCIIO DevicePath(..)/Pci(0x1C,0x4)/Pci(0x0,0x0))
10F: PCIIO DevicePath(..4)/Pci(0x0,0x0)/Pci(0x0,0x0))
110: 2CA35480-18C7-4F11-B29F-F5711062347B 73CDDA53-95F2-42B4-BC87-6E5F0D2C535B 506B81A0-0C3F-11DF-B1BE-0002A5D5C51B C649D4F3-D502-4DAA-A139-394ACCF2A63B PCIIO DevicePath(..0)/Pci(0x0,0x0)/Pci(0x0,0x0))
111: PCIIO DevicePath(..4)/Pci(0x0,0x0)/Pci(0x3,0x0))
112: PCIIO DevicePath(..4)/Pci(0x0,0x0)/Pci(0x4,0x0))
113: PCIIO DevicePath(..4)/Pci(0x0,0x0)/Pci(0x5,0x0))
114: PCIIO DevicePath(..4)/Pci(0x0,0x0)/Pci(0x6,0x0))
115: C649D4F3-D502-4DAA-A139-394ACCF2A63B DevicePath(..00200C9A66,0000000000000003))
116: 2EFA0873-5E02-45FC-A0A5-A1008114CD8D C649D4F3-D502-4DAA-A139-394ACCF2A63B DevicePath(..00200C9A66,0000000000000004))
117: 2EFA0873-5E02-45FC-A0A5-A1008114CD8D C649D4F3-D502-4DAA-A139-394ACCF2A63B DevicePath(..00200C9A66,0000000000000403))
118: DriverHealth DriverConfiguration DriverDiagnostics2 ComponentName2 DriverDiagnostics ComponentName DriverBinding LoadedImage
119: PCIIO DevicePath(..0)/Pci(0x4,0x0)/Pci(0x0,0x0))
11A: PCIIO DevicePath(..0)/Pci(0x0,0x0)/Pci(0x0,0x0))
11B: PCIIO DevicePath(..0)/Pci(0x0,0x0)/Pci(0x0,0x0))
11C: PCIIO DevicePath(..0)/Pci(0x0,0x0)/Pci(0x1,0x0))
11D: E3161450-AD0F-11D9-9669-0800200C9A66 BusSpecificDriverOverride PCIIO DevicePath(..0)/Pci(0x1,0x0)/Pci(0x0,0x0))
11E: PCIIO DevicePath(..0)/Pci(0x0,0x0)/Pci(0x4,0x0))
11F: PCIIO DevicePath(..0)/Pci(0x0,0x0)/Pci(0x5,0x0))
120: 74833284-39EB-414C-8544-59CFD6095DC9
121: C32332DF-FC56-4FE1-9358-BA0D529B24CD
122: E49D0DC9-9D03-4047-8CDC-812458BED435 DevicePath(..2F5752CAD6,0000000001000000)) CF611019-A212-4075-83A7-39F7364DEA6B
123: DevicePath(..2F5752CAD6,0000000002000000)) CF611019-A212-4075-83A7-39F7364DEA6B
124: DevicePath(..2F5752CAD6,0000000003000000)) CF611019-A212-4075-83A7-39F7364DEA6B
125: DevicePath(..2F5752CAD6,0000000004000000)) CF611019-A212-4075-83A7-39F7364DEA6B
126: DevicePath(..2F5752CAD6,0000000005000000)) CF611019-A212-4075-83A7-39F7364DEA6B
127: DevicePath(..2F5752CAD6,0000000006000000)) CF611019-A212-4075-83A7-39F7364DEA6B
128: DevicePath(..73B5026BA9,0000000000000000)) F977B8AE-9E24-46DD-92C6-B3B629E1877A
129: DevicePath(..73B5026BA9,0000000001000000)) F977B8AE-9E24-46DD-92C6-B3B629E1877A
12A: DevicePath(..73B5026BA9,0000000002000000)) F977B8AE-9E24-46DD-92C6-B3B629E1877A
12B: DevicePath(..73B5026BA9,0000000003000000)) F977B8AE-9E24-46DD-92C6-B3B629E1877A
12C: DevicePath(..73B5026BA9,0000000004000000)) F977B8AE-9E24-46DD-92C6-B3B629E1877A
12D: DevicePath(..73B5026BA9,0000000005000000)) F977B8AE-9E24-46DD-92C6-B3B629E1877A
12E: 13ABBCB6-E0EC-4DBC-A5EC-D2436ECF42BB
12F: USBIO DevicePath(..)/Pci(0x1A,0x7)/USB(0x0,0x0))
130: USBIO DevicePath(..7)/USB(0x0,0x0)/USB(0x0,0x0))
131: USBIO DevicePath(..0)/USB(0x0,0x0)/USB(0x0,0x0))
132: USBIO DevicePath(..0)/USB(0x0,0x0)/USB(0x0,0x1))
133: USBIO DevicePath(..0)/USB(0x0,0x0)/USB(0x0,0x2))
134: USBIO DevicePath(..0)/USB(0x0,0x0)/USB(0x0,0x3))
135: ConsoleIn 220AC432-1D43-49E5-A74F-4C9DA67AD23B SimpleTextIn USBIO DevicePath(..0)/USB(0x0,0x0)/USB(0x1,0x0))
136: SimplePointer USBIO DevicePath(..0)/USB(0x0,0x0)/USB(0x2,0x0))
137: USBIO DevicePath(..)/Pci(0x1A,0x7)/USB(0x1,0x0))
138: USBIO DevicePath(..)/Pci(0x1A,0x7)/USB(0x1,0x1))
139: USBIO DevicePath(..)/Pci(0x1A,0x7)/USB(0x1,0x2))
13A: USBIO DevicePath(..)/Pci(0x1D,0x7)/USB(0x0,0x0))
13B: DiskIO BlockIO 3B63DC5E-BA60-4159-A2B4-9B91D2B8F009 BC22EE2B-200A-4CF6-BA83-9FA2D018B7BD 2B2F68DA-0CD2-44CF-8E8B-BBA20B1B5B75 USBIO DevicePath(..7)/USB(0x0,0x0)/USB(0x0,0x0))
13C: EDA517B5-F953-40D6-B900-9AF50079CEE4 41A47978-023A-4C1F-8C79-A92A7E3BBAF8 USBIO DevicePath(..7)/USB(0x0,0x0)/USB(0x1,0x0))
13D: USBIO DevicePath(..7)/USB(0x0,0x0)/USB(0x2,0x0))
13E: ConsoleIn 220AC432-1D43-49E5-A74F-4C9DA67AD23B SimpleTextIn USBIO DevicePath(..0)/USB(0x2,0x0)/USB(0x1,0x0))
13F: ED1B1499-BDF2-4E8B-A1F7-5373169C74F7 USBIO DevicePath(..0)/USB(0x2,0x0)/USB(0x1,0x1))
140: SimplePointer USBIO DevicePath(..0)/USB(0x2,0x0)/USB(0x2,0x0))
141: 389F751F-1838-4388-8390-CD8154BD27F8 7AA35A69-506C-444F-A7AF-694BF56F71C8 DevicePath(..d(0xB,0x8D330000,0x8D357FFF)) DE28BC59-6228-41BD-BDF6-A3B9ADB58DA1
142: LoadedImage
143: LoadedImage
144: 783658A3-4172-4421-A299-E009079C0CB4
145: LoadedImage
146: LoadedImage
147: LoadedImage
148: 2A82FCE6-8BB6-413E-B9EB-45DFC0522DF3
149: 389F751F-1838-4388-8390-CD8154BD27F8 7AA35A69-506C-444F-A7AF-694BF56F71C8 DevicePath(..d(0xB,0x8D085000,0x8D24EFFF)) DE28BC59-6228-41BD-BDF6-A3B9ADB58DA1
14A: LoadedImage
14B: ComponentName DriverBinding
14C: LoadedImage
14D: 480F8AE9-0C46-4AA9-BC89-DB9FBA619806
14E: ComponentName DriverBinding LoadedImage
14F: ComponentName DriverBinding LoadedImage
150: ComponentName DriverBinding LoadedImage
151: ComponentName DriverBinding LoadedImage
152: ComponentName DriverBinding LoadedImage
153: ComponentName DriverBinding LoadedImage
154: ComponentName DriverBinding LoadedImage
155: ComponentName DriverBinding LoadedImage
156: ComponentName DriverBinding LoadedImage
157: ComponentName DriverBinding LoadedImage
158: LoadedImage
159: 081C8EB7-E98E-488A-A83F-035F520BC65C
15A: LoadedImage
15B: LoadedImage
15C: 35ED76B7-57E8-4575-B686-67457D08A239
15D: D94AD118-C02E-4DFC-860B-AFEA3442E627 LoadedImage
15E: D41E56B0-C8C7-45AB-A0EE-BD92F380EAED LoadedImage
15F: LoadedImage
160: LoadedImage
161: A0041CFA-5705-4AEA-83E9-2433AB6F5931
162: LoadedImage
163: 66E6E8AB-B0ED-4B43-B0F9-151817175FDB
164: 0DFCE9F6-C4E3-45EE-A06A-A8613B98A507 LoadedImage
165: 0DFCE9F6-C4E3-45EE-A06A-A8613B98A507 LoadedImage
166: 0DFCE9F6-C4E3-45EE-A06A-A8613B98A507 LoadedImage
167: 0DFCE9F6-C4E3-45EE-A06A-A8613B98A507 LoadedImage
168: LoadedImage
169: 11BE2251-CDA0-4494-93E8-8130C8B044D2
16A: LoadedImage
16B: 7EC21E57-CE8A-4FDE-B147-0F7C0959CD3F
16C: DriverDiagnostics DriverConfiguration ComponentName DriverBinding LoadedImage
16D: ConsoleOut SimpleTextOut 03622D6D-362A-4E47-9710-C238B23755C1 EDIDActive(EDIDActive) GraphicsOutput(GraphicsOutput) DevicePath(..D-91681E2C6F36,000000000000)) EDIDDiscovered(EDIDDiscovered)
16E: 78EE99FB-6A5E-4186-97DE-CD0ABA345A74 LoadFile D040351C-4C76-4457-9AB3-DA73716FEFCD 133D863F-B44C-421D-BCAF-611AE0B2CCF7 DHCPv4ServiceBinding A6CEA0BD-80A6-4B5F-A290-A6801582E608 TCPv4ServiceBinding MTFTPv4ServiceBinding UDPv4ServiceBinding IPv4Config IPv4ServiceBinding ARPServiceBinding ManagedNetworkServiceBinding SimpleNetwork BF71D7E3-4AE8-47F1-8605-9D576AAB4478 75E757D5-8571-4718-9E13-AFFBBA5CF38D DevicePath(..0,0x0)/MAC(A82066056501,0x0)) NetworkInterfaceIdentifier NetworkInterfaceIdentifier31
16F: ManagedNetwork
170: ManagedNetwork
171: ManagedNetwork
172: IPv4
173: IPv4
174: UDPv4
175: IPv4
176: IPv4
177: UDPv4
178: 5C4DE4E9-5143-4592-8015-2372427807E6
179: IPv4
17A: UDPv4
17B: IPv4
17C: UDPv4
17D: MTFTPv4
17E: IPv4
17F: UDPv4
180: 5C4DE4E9-5143-4592-8015-2372427807E6
181: EA0720C6-D05A-4BF0-B7F8-7FC1A7A97897
182: 78EE99FB-6A5E-4186-97DE-CD0ABA345A74 LoadFile D040351C-4C76-4457-9AB3-DA73716FEFCD 133D863F-B44C-421D-BCAF-611AE0B2CCF7 DHCPv4ServiceBinding A6CEA0BD-80A6-4B5F-A290-A6801582E608 TCPv4ServiceBinding MTFTPv4ServiceBinding UDPv4ServiceBinding IPv4Config IPv4ServiceBinding ARPServiceBinding ManagedNetworkServiceBinding SimpleNetwork BF71D7E3-4AE8-47F1-8605-9D576AAB4478 71B4903C-14EC-42C4-BDC6-CE1449930E49 DevicePath(..0,0x0)/MAC(20C9D0349EA4,0x0)) NetworkInterfaceIdentifier31
183: ManagedNetwork
184: ManagedNetwork
185: ManagedNetwork
186: IPv4
187: IPv4
188: UDPv4
189: IPv4
18A: IPv4
18B: UDPv4
18C: 5C4DE4E9-5143-4592-8015-2372427807E6
18D: IPv4
18E: UDPv4
18F: IPv4
190: UDPv4
191: MTFTPv4
192: IPv4
193: UDPv4
194: 5C4DE4E9-5143-4592-8015-2372427807E6
195: EA0720C6-D05A-4BF0-B7F8-7FC1A7A97897
196: ISAIO DevicePath(..0)/Pci(0x1F,0x0)/Serial(0x0))
197: 01A81704-3442-4A7D-8740-F4EC5BBE5977 DiskIO 5B27263B-9083-415E-889E-6432CAA9B813 19931CD1-FFA4-4F49-B8F3-BDC28701DE0B 5C38EA59-554B-431C-B3F5-CD6EE3D48A3E DiskInfo BlockIO DevicePath(..(0x1F,0x2)/Sata(0x0,0x0,0x0))
198: 09FC6B19-B8A1-4A01-8DB1-8794E7634CA5 SimpleFileSystem DiskIO EFISystemPartition 68425EE5-1C43-4BAA-84F7-9AA8A4D8E11E BlockIO DevicePath(..3-01296E64E13F,0x28,0x64000))
199: 14E1722E-F9C3-4610-A9CB-1128041130FF 03B8D751-A02F-4FF8-9B1A-5524AFA3945F DiskIO 68425EE5-1C43-4BAA-84F7-9AA8A4D8E11E BlockIO DevicePath(..430BE195,0x64028,0x3A321FE0))
19A: ComponentName DriverBinding LoadedImage()
19B: Hash
19C: 09FC6B19-B8A1-4A01-8DB1-8794E7634CA5 DevicePath(..AA975BA884EA8273EC23D02C804)) BlockIO SimpleFileSystem
19D: 09FC6B19-B8A1-4A01-8DB1-8794E7634CA5 DevicePath(..4DD1DA8DD498F6062261C772D17)) BlockIO SimpleFileSystem
19E: 09FC6B19-B8A1-4A01-8DB1-8794E7634CA5 DevicePath(..8AE2EACB340986EEF48A66140BD)) BlockIO SimpleFileSystem
19F: 09FC6B19-B8A1-4A01-8DB1-8794E7634CA5 DevicePath(..C65A233814594C678864853679C)) BlockIO SimpleFileSystem
1A0: 09FC6B19-B8A1-4A01-8DB1-8794E7634CA5 DevicePath(..A44E2274F469FE9739BFEA0AF92)) BlockIO SimpleFileSystem
1A1: 09FC6B19-B8A1-4A01-8DB1-8794E7634CA5 DevicePath(..234D41D774BAF58B1B12176DAEB)) BlockIO SimpleFileSystem
1A2: 09FC6B19-B8A1-4A01-8DB1-8794E7634CA5 DevicePath(..59534B7304A99C13E1ED16F2C16)) BlockIO SimpleFileSystem
1A3: 09FC6B19-B8A1-4A01-8DB1-8794E7634CA5 DevicePath(..8221625DF40AB0F2FB3D62DCB59)) BlockIO SimpleFileSystem
1A4: IPv4
1A5: UDPv4
1A6: ARP
1A7: DiskIO 5C38EA59-554B-431C-B3F5-CD6EE3D48A3E DiskInfo 2EA9743A-23D9-425E-872C-F615AA195788 BlockIO DevicePath(..(0x1F,0x2)/Sata(0x2,0x0,0x0))
1A8: 78EE99FB-6A5E-4186-97DE-CD0ABA345A74 LoadFile D040351C-4C76-4457-9AB3-DA73716FEFCD 133D863F-B44C-421D-BCAF-611AE0B2CCF7 DHCPv4ServiceBinding A6CEA0BD-80A6-4B5F-A290-A6801582E608 TCPv4ServiceBinding MTFTPv4ServiceBinding UDPv4ServiceBinding IPv4Config IPv4ServiceBinding ARPServiceBinding ManagedNetworkServiceBinding SimpleNetwork FirmwareManagement(FirmwareManagement) 34D59603-1428-4429-A414-E6B3B5FD7DC1 0E1AD94A-DCF4-11DB-9705-00E08161165F NetworkInterfaceIdentifier31 E3161450-AD0F-11D9-9669-0800200C9A66 DevicePath(..0,0x0)/MAC(000C6C09E446,0x0)) 51DD8B21-AD8D-48E9-BC3F-24F46722C748
1A9: ManagedNetwork
1AA: ManagedNetwork
1AB: ManagedNetwork
1AC: IPv4
1AD: IPv4
1AE: UDPv4
1AF: IPv4
1B0: IPv4
1B1: UDPv4
1B2: 5C4DE4E9-5143-4592-8015-2372427807E6
1B3: IPv4
1B4: UDPv4
1B5: IPv4
1B6: UDPv4
1B7: MTFTPv4
1B8: IPv4
1B9: UDPv4
1BA: 5C4DE4E9-5143-4592-8015-2372427807E6
1BB: EA0720C6-D05A-4BF0-B7F8-7FC1A7A97897
1BC: C21C44EA-489D-4EEF-9169-B6118D3DA846
1BD: Hash
1BE: 389F751F-1838-4388-8390-CD8154BD27F8 7AA35A69-506C-444F-A7AF-694BF56F71C8 DevicePath(..d(0xB,0x89C72068,0x8AB72067)) DE28BC59-6228-41BD-BDF6-A3B9ADB58DA1
1BF: D088A413-0A70-4217-BA55-9A3CB65C41B3
1C0: D088A413-0A70-4217-BA55-9A3CB65C41B3
1C1: D088A413-0A70-4217-BA55-9A3CB65C41B3
1C2: LoadedImage(\System\Library\CoreServices\boot.efi)
1C3: 33BE0EF1-89C9-4A6D-BB9F-69DC8DD516B9 LoadedImage(EFI\OC\OpenCore.efi)
1C4: BA1EB455-B182-4F14-8521-E422C325DEF6
1C5: DevicePath(..5B82-403D-87A5-D4676250EC59))
1C6: DBB6008F-89E4-4272-9881-CE3AFD9724D0
1C7: 62257758-350C-4D0A-B0BD-F6BE2E1E272C
1C8: DDFA34FB-FE1F-48EA-B213-FB4A4CD57BE3
1C9: D5B0AC65-9A2D-4D2A-BBD6-E871A95E0435
1CA: UnicodeCollation2
1CB: C5C5DA95-7D5C-45E6-B2F1-3FD52BB10077
1CC: E316E100-0751-4C49-9056-486C7E472903
1CD: 314735F0-26FE-11E8-A470-B8E8562CBAFA
1CE: 24B73556-2197-4702-82A8-3E1337DAFBF2
1CF: C7CBA84E-CC77-461D-9E3C-6BE0CB79A7C1
1D0: LoadedImage
1D1: 570332E4-FC50-4B21-ABE8-AE72F05B4FF7
1D2: LoadedImage
1D3: 53027CDF-3A89-4255-AE29-D6666EFE99EF
1D4: 8604716E-ADD4-45B4-8495-08E36D497F4F LoadedImage
1D5: Shell ShellParameters SimpleTextOut LoadedImage(VenHw(1237EC17-D3CE-401D-A841-B1D818F8AF1A))
1D6: SimpleTextOut


Code:
     T   D
     Y C I
     P F A
CTRL E G G #P #D #C  Device Name
==== = = = == == === =========================================================
  39 R - -  0  1  43 PciRoot(0x0)
  AA D - -  4  0   0 Primary Console Input Device
  AB D - -  1  0   0 Primary Console Output Device
  F1 D - -  1  0   0 PciRoot(0x0)/Pci(0x0,0x0)
  F2 D - -  1  0   0 PciRoot(0x0)/Pci(0x1,0x0)
  F3 B - -  1  2  12 AMD Radeon Venus Video Adapter
  F4 D - -  1  0   0 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x1)
  F5 D - -  1  0   0 PciRoot(0x0)/Pci(0x2,0x0)
  F6 D - -  1  0   0 PciRoot(0x0)/Pci(0x16,0x0)
  F7 D - -  1  0   0 PciRoot(0x0)/Pci(0x16,0x1)
  F8 D - -  1  0   0 PciRoot(0x0)/Pci(0x16,0x3)
  F9 D - -  1  2   0 Usb Universal Host Controller
  FA D - -  1  2   0 Usb Universal Host Controller
  FB D - -  1  2   0 Usb Universal Host Controller
  FC B - -  1  2  11 Usb Enhanced Host Controller
  FD D - -  1  1   0 PciRoot(0x0)/Pci(0x1B,0x0)
  FE D - -  1  0   0 PciRoot(0x0)/Pci(0x1C,0x0)
  FF B X X  1  1   1 PciRoot(0x0)/Pci(0x1C,0x0)/Pci(0x0,0x0)
 100 D - -  1  0   0 PciRoot(0x0)/Pci(0x1C,0x1)
 101 B - -  1  1   1 Atheros PCI-E Adapter
 102 D - -  1  0   0 PciRoot(0x0)/Pci(0x1C,0x2)
 103 D - -  1  1   0 FireWire Open Host Controller
 104 D - -  1  2   0 Usb Universal Host Controller
 105 D - -  1  2   0 Usb Universal Host Controller
 106 D - -  1  2   0 Usb Universal Host Controller
 107 D - -  1  2   0 Usb Universal Host Controller
 108 B - -  1  2   7 Usb Enhanced Host Controller
 109 B - -  1  2   1 PciRoot(0x0)/Pci(0x1F,0x0)
 10A D - -  1  1   0 PCI AHCI Controller
 10B D - -  1  0   0 PciRoot(0x0)/Pci(0x1F,0x3)
 10C D - -  1  0   0 PciRoot(0x0)/Pci(0x1F,0x6)
 10D D - -  1  0   0 PciRoot(0x0)/Pci(0x1C,0x4)
 10E D - -  1  0   0 PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)
 10F D - -  1  0   0 PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)/Pci(0x0,0x0)
 110 B - -  1  1   3 Thunderbolt Native Host Interface
 111 D - -  1  0   0 PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)/Pci(0x3,0x0)
 112 D - -  1  0   0 PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)/Pci(0x4,0x0)
 113 D - -  1  0   0 PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)/Pci(0x5,0x0)
 114 D - -  1  0   0 PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)/Pci(0x6,0x0)
 115 D - -  1  0   0 Thunderbolt Device
 116 D - -  1  1   0 Thunderbolt Inter-domain Boundary
 117 D - -  1  1   0 Thunderbolt Inter-domain Boundary
 119 D - -  1  0   0 PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)
 11A D - -  1  0   0 PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)
 11B D - -  1  0   0 PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)/Pci(0x0,0x0)
 11C D - -  1  0   0 PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/Pci(0x1,0x0)
 11D B X X  1  1   1 PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)
 11E D - -  1  0   0 PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/Pci(0x4,0x0)
 11F D - -  1  0   0 PciRoot(0x0)/Pci(0x1C,0x4)/Pci(0x0,0x0)/Pci(0x4,0x0)/Pci(0x0,0x0)/Pci(0x5,0x0)
 122 D - -  1  1   0 AMD Radeon Venus Video Adapter
 123 D - -  1  1   0 AMD Radeon Venus Video Adapter
 124 B - -  1  1   1 AMD Radeon Venus Video Adapter
 125 D - -  1  1   0 AMD Radeon Venus Video Adapter
 126 D - -  1  1   0 AMD Radeon Venus Video Adapter
 127 D - -  1  1   0 AMD Radeon Venus Video Adapter
 128 D - -  1  1   0 AMD Radeon Venus Video Adapter
 129 D - -  1  1   0 AMD Radeon Venus Video Adapter
 12A D - -  1  1   0 AMD Radeon Venus Video Adapter
 12B D - -  1  1   0 AMD Radeon Venus Video Adapter
 12C D - -  1  1   0 AMD Radeon Venus Video Adapter
 12D D - -  1  1   0 AMD Radeon Venus Video Adapter
 12F D - -  1  0   0 PciRoot(0x0)/Pci(0x1A,0x7)/USB(0x0,0x0)
 130 D - -  1  0   0 PciRoot(0x0)/Pci(0x1A,0x7)/USB(0x0,0x0)/USB(0x0,0x0)
 131 D - -  1  0   0 PciRoot(0x0)/Pci(0x1A,0x7)/USB(0x0,0x0)/USB(0x0,0x0)/USB(0x0,0x0)
 132 D - -  1  0   0 PciRoot(0x0)/Pci(0x1A,0x7)/USB(0x0,0x0)/USB(0x0,0x0)/USB(0x0,0x1)
 133 D - -  1  0   0 PciRoot(0x0)/Pci(0x1A,0x7)/USB(0x0,0x0)/USB(0x0,0x0)/USB(0x0,0x2)
 134 D - -  1  0   0 PciRoot(0x0)/Pci(0x1A,0x7)/USB(0x0,0x0)/USB(0x0,0x0)/USB(0x0,0x3)
 135 B - -  1  3   1 Generic Usb Keyboard
 136 B - -  1  2   1 Generic Usb Mouse
 137 D - -  1  0   0 PciRoot(0x0)/Pci(0x1A,0x7)/USB(0x1,0x0)
 138 D - -  1  0   0 PciRoot(0x0)/Pci(0x1A,0x7)/USB(0x1,0x1)
 139 D - -  1  0   0 PciRoot(0x0)/Pci(0x1A,0x7)/USB(0x1,0x2)
 13A D - -  1  0   0 PciRoot(0x0)/Pci(0x1D,0x7)/USB(0x0,0x0)
 13B D - -  1  3   0 Usb Bot Mass Storage
 13C D - -  1  1   0 PciRoot(0x0)/Pci(0x1D,0x7)/USB(0x0,0x0)/USB(0x1,0x0)
 13D D - -  1  0   0 PciRoot(0x0)/Pci(0x1D,0x7)/USB(0x0,0x0)/USB(0x2,0x0)
 13E B - -  1  3   1 Generic Usb Keyboard
 13F D - -  1  1   0 PciRoot(0x0)/Pci(0x1D,0x7)/USB(0x0,0x0)/USB(0x2,0x0)/USB(0x1,0x1)
 140 B - -  1  2   1 Generic Usb Mouse
 16D B - -  1  3   1 PciRoot(0x0)/Pci(0x1,0x0)/Pci(0x0,0x0)/VenMsg(E9D6CAFB-E58B-4781-A8F2-FB2F5752CAD6,0000000003000000)/VenMsg(952DAE24-A51D-49C8-825D-91681E2C6F36,000000000000)
 16E B - -  1  2   3 Broadcom NetXtreme Gigabit Ethernet (BCM57765)
 182 B - -  1  2   3 PciRoot(0x0)/Pci(0x1C,0x1)/Pci(0x0,0x0)/MAC(20C9D0349EA4,0x0)
 196 D - -  1  1   0 PciRoot(0x0)/Pci(0x1F,0x0)/Serial(0x0)
 197 R - -  0  2   2 PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)
 198 D - -  1  2   0 FAT File System [FAT32] 200 MB
 199 B - -  1  2   8 APFS [Monterey]
 19C D - -  1  1   0 PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,D5C9EEDB-B461-4407-A746-A500430BE195,0x64028,0x3A321FE0)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,27AB7AA975BA884EA8273EC23D02C804)
 19D D - -  1  1   0 PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,D5C9EEDB-B461-4407-A746-A500430BE195,0x64028,0x3A321FE0)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,A5E1B4DD1DA8DD498F6062261C772D17)
 19E D - -  1  1   0 PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,D5C9EEDB-B461-4407-A746-A500430BE195,0x64028,0x3A321FE0)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,C9FF78AE2EACB340986EEF48A66140BD)
 19F D - -  1  1   0 PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,D5C9EEDB-B461-4407-A746-A500430BE195,0x64028,0x3A321FE0)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,E53ADC65A233814594C678864853679C)
 1A0 D - -  1  1   0 PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,D5C9EEDB-B461-4407-A746-A500430BE195,0x64028,0x3A321FE0)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,7F607A44E2274F469FE9739BFEA0AF92)
 1A1 D - -  1  1   0 PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,D5C9EEDB-B461-4407-A746-A500430BE195,0x64028,0x3A321FE0)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,D96BE234D41D774BAF58B1B12176DAEB)
 1A2 D - -  1  1   0 PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,D5C9EEDB-B461-4407-A746-A500430BE195,0x64028,0x3A321FE0)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,FA12759534B7304A99C13E1ED16F2C16)
 1A3 D - -  1  1   0 PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0x0,0x0)/HD(2,GPT,D5C9EEDB-B461-4407-A746-A500430BE195,0x64028,0x3A321FE0)/VenMedia(BE74FCF7-0B7C-49F3-9147-01F4042E6842,234DE8221625DF40AB0F2FB3D62DCB59)
 1A7 R - -  0  1   0 PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x2,0x0,0x0)
 1A8 B - -  1  2   3 Intel(R) I210 Gigabit  Network Connection
 

Attachments

  • devices.txt.zip
    1.9 KB · Views: 63
  • dh.txt.zip
    9.4 KB · Views: 62
  • help.txt.zip
    2.2 KB · Views: 70
Last edited:
I'm suffering from a guilty conscience because I wandered off topic in a thread on Continuity & Handoff on a Mac Pro talking about OpenCore so I thought I'd pose my questions in the OpenCore thread...lets hope I don't get told off for cross-posting! ;)

System as signature but reproduced here for ease of reading;

Original 5,1 Mac Pro 2010
Dual X5690 3.46GHz 12-Core Xeon
96GB Samsung ECC RDIMM
1TB Samsung 970 Pro NVMe M.2 booting 10.13.6 High Sierra PCIe Slot 4
2TB Samsung 860 EVO SATA Drive Bay 2
16TB Seagate EXOS SATA Drive Bay 1
NVIDIA Quadro NVS 510 PCIe Slot 1
Sonnet Allegro USB 3.2 PCIe Slot 3
BCM94360CD 802.11ac & Bluetooth 4.0

I recently bought my cMP from a Mac Reseller here in the UK and only discovered it was running OpenCore when I was looking for the Boot ROM version in System Report to find it listed as 9144.0.7.3.1 when I expected to see 144.0.0.0.0 and after some research realised that OpenCore was spoofing the ROM version. I was somewhat disappointed that it had been installed as nothing had been mentioned and I thought I was buying a 'factory reconditioned' Mac Pro and not one that depended on a 3rd party utility for various functions.

Now as I have a Quadro NVS 510 and don't need any AMD GPU acceleration and am running 10.13.6 High Sierra I am left wondering whether I could/should disable/remove OpenCore altogether and run my cMP as Apple designed it and I prefer it?

I am quite happy to stay with High Sierra as it is tried & tested here as my 2011 iMac won't run 10.14 Mojave or above and I have held my other Macs at High Sierra because of this but part of me wonders whether I could still upgrade the cMP to Mojave if the idea ever took me without the help of OpenCore?

If yes then I'm happy to temporarily disable OpenCore for now...in fact I'll go further and say I might just remove it anyway if my current config will work properly without it. I don't even know which version of OpenCore is installed because the usual command line nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version returns the error nvram: Error getting variable - '4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version': (iokit/common) data was not found and it looks like I have to edit a config or plist file just to get round this restriction. Another reason to uninstall OpenCore IMHO.

In essence is there an easy way to temporarily disable OpenCore and re-enable it if I find I can't live without it?

And if I decide to remove it altogether how best do I go about it and might it impact installing Windows at a later date?

I realise most of the questions here will be about installing rather than removing OpenCore but then I've never conformed to anything like normal in my life! ?

Thanks & kind regards,
-=Glyn=-

First of all you need to read Post #1 in this thread about the basics of Opencore to understand what it does, where it is installed, how the files are structured, and how to edit the configuration file called config.plist.

Basic step to disable OpenCore, you need to:
  1. Mount the EFI partition where OpenCore is installed
  2. Edit the config.plist file and change the value of the key for RequestBootVarRouting = false.
    That is, :
    XML:
    <key>RequestBootVarRouting</key><false/>
  3. Reboot
  4. Go into System Preferences and select your High Sierra drive as your startup disk
  5. Reboot again and this time your cMP will boot without Opencore

To re-enable Opencore, you have to RequestBootVarRouting = true and then Bless the Opencore (detailed in Post #1).
 
  • Like
Reactions: Macschrauber
I'm suffering from a guilty conscience because I wandered off topic in a thread on Continuity & Handoff on a Mac Pro talking about OpenCore so I thought I'd pose my questions in the OpenCore thread...lets hope I don't get told off for cross-posting! ;)

System as signature but reproduced here for ease of reading;

Original 5,1 Mac Pro 2010
Dual X5690 3.46GHz 12-Core Xeon
96GB Samsung ECC RDIMM
1TB Samsung 970 Pro NVMe M.2 booting 10.13.6 High Sierra PCIe Slot 4
2TB Samsung 860 EVO SATA Drive Bay 2
16TB Seagate EXOS SATA Drive Bay 1
NVIDIA Quadro NVS 510 PCIe Slot 1
Sonnet Allegro USB 3.2 PCIe Slot 3
BCM94360CD 802.11ac & Bluetooth 4.0

I recently bought my cMP from a Mac Reseller here in the UK and only discovered it was running OpenCore when I was looking for the Boot ROM version in System Report to find it listed as 9144.0.7.3.1 when I expected to see 144.0.0.0.0 and after some research realised that OpenCore was spoofing the ROM version. I was somewhat disappointed that it had been installed as nothing had been mentioned and I thought I was buying a 'factory reconditioned' Mac Pro and not one that depended on a 3rd party utility for various functions.

Now as I have a Quadro NVS 510 and don't need any AMD GPU acceleration and am running 10.13.6 High Sierra I am left wondering whether I could/should disable/remove OpenCore altogether and run my cMP as Apple designed it and I prefer it?

I am quite happy to stay with High Sierra as it is tried & tested here as my 2011 iMac won't run 10.14 Mojave or above and I have held my other Macs at High Sierra because of this but part of me wonders whether I could still upgrade the cMP to Mojave if the idea ever took me without the help of OpenCore?

If yes then I'm happy to temporarily disable OpenCore for now...in fact I'll go further and say I might just remove it anyway if my current config will work properly without it. I don't even know which version of OpenCore is installed because the usual command line nvram 4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version returns the error nvram: Error getting variable - '4D1FDA02-38C7-4A6A-9CC6-4BCCA8B30102:eek:pencore-version': (iokit/common) data was not found and it looks like I have to edit a config or plist file just to get round this restriction. Another reason to uninstall OpenCore IMHO.

In essence is there an easy way to temporarily disable OpenCore and re-enable it if I find I can't live without it?

And if I decide to remove it altogether how best do I go about it and might it impact installing Windows at a later date?

I realise most of the questions here will be about installing rather than removing OpenCore but then I've never conformed to anything like normal in my life! ?

Thanks & kind regards,
-=Glyn=-
Give opencore a try! It works great. OS beyond Sierra work smoothly.
 
Hi Everyone - Thank you for this great resource to keep the beautiful Mac Pro Classics alive with the latest Apple Operating Systems and features.

I have an issue that I am hoping someone can help me with. I am running the dosdude Catalina on my PC and I decided to take the plunge and install OpenCore (OC) so that I can move to Big Sur or Monterey. I followed the instructions from Post 1 on this thread.

I got as far as loading OC with the base configuration in Post 1. After that, I carefully made the edits for SurPlus, Firmware Features, Hardware acceleration and other features, Hybridization (and workaround for dual processor), and Internal PCIe drives. I am attaching my last configuration file.

Since then, I now end up in a reboot loop. I can get about 33% of the loading bar (black screen with apple logo) booting Catalina before my computer restarts itself. I am, however, able to boot into Safe Mode where I get an error report from Apple which is also attached.

The problem is that I cannot mount the EFI partition to make any edits. See below.
Code:
Mac-Pro:~ forevaclevah$ diskutil list
/dev/disk0 (internal, physical):


   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *512.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:                 Apple_APFS Container disk1         511.9 GB   disk0s2


/dev/disk1 (synthesized):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      APFS Container Scheme -                      +511.9 GB   disk1
                                 Physical Store disk0s2


   1:                APFS Volume Catalina - Data         308.2 GB   disk1s1
   2:                APFS Volume Preboot                 29.4 MB    disk1s2
   3:                APFS Volume Recovery                731.7 MB   disk1s3
   4:                APFS Volume VM                      1.1 MB     disk1s4
   5:                APFS Volume Catalina                11.1 GB    disk1s5
/dev/disk2 (internal, physical):


   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *3.0 TB     disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                 Apple_RAID                         3.0 TB     disk2s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk2s3
/dev/disk3 (internal, physical):


   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *1.0 TB     disk3
   1:                        EFI EFI                     209.7 MB   disk3s1
   2:                  Apple_HFS Sierra                  999.3 GB   disk3s2
   3:                 Apple_Boot Recovery HD             650.0 MB   disk3s3
/dev/disk4 (internal, physical):


   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *3.0 TB     disk4
   1:                        EFI EFI                     209.7 MB   disk4s1
   2:                 Apple_RAID                         3.0 TB     disk4s2
   3:                 Apple_Boot Boot OS X               134.2 MB   disk4s3

/dev/disk5 (internal, virtual):
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:                  Apple_HFS Storage                +3.0 TB     disk5

Mac-Pro:~ forevaclevah$ sudo diskutil mount disk0s1
Password:
Volume on disk0s1 failed to mount
If you think the volume is supported but damaged, try the "readOnly" option
Mac-Pro:~ forevaclevah$

I am not sure what to do next. I think I must have made an error somewhere when editing my EFI with OpenCore, but I don't know how to make any changes. Somewhat surprisingly, I now see that I can load Monterey via Apple Update, but I am hesitant to make any more changes before I can get a stable boot pattern.

Does anyone have any tips to access the EFI to make edits to my config?
 

Attachments

  • config.plist.zip
    4 KB · Views: 57
  • error report.pdf
    35 KB · Views: 90
Last edited:
- fs0: is the EFI partition and I had access (otherwise I could not have attached the files you asked for)
- tried at the very end to load the xhcidxe.efi from disk and got successfully loaded message but the shell stuck

Took while through that loop:
Doesn't look like the driver got loaded. Which device is the XHCI controller? Use pci > pci.txt to find out. Or better yet, use my FixPCIeLinkRate.efi app. Don't forget to include output for drivers. Also, devtree.

Remove the drivers from the OpenCore config.plist. Boot OpenCore. Load the drivers manually. Does it still hang? I wonder if OpenCore is setting something up that is required by the drivers. This is why I would prefer getting the XhciDxe driver source code working.
 
First of all you need to read Post #1 in this thread about the basics of Opencore to understand what it does, where it is installed, how the files are structured, and how to edit the configuration file called config.plist.

Basic step to disable OpenCore, you need to:
  1. Mount the EFI partition where OpenCore is installed
  2. Edit the config.plist file and change the value of the key for RequestBootVarRouting = false.
    That is, :
    XML:
    <key>RequestBootVarRouting</key><false/>
  3. Reboot
  4. Go into System Preferences and select your High Sierra drive as your startup disk
  5. Reboot again and this time your cMP will boot without Opencore

To re-enable Opencore, you have to RequestBootVarRouting = true and then Bless the Opencore (detailed in Post #1).
Thanks for taking the time to reply MacNB2.

Oh I've read Post 1 in this thread and many hundreds more and the more I read the more confused I get and the more I feel like OpenCore is not for me if my current setup can live without it!

Thanks also for the instructions to disable OpenCore. I was on the right track as I did have to bless the EFI partition once after trying an 870 SSD and losing the boot menu in the process so figured the config.plist was lurking in there somewhere.

Just needed it spelled out I guess...I'll give it a try and see how it goes.

Thanks & kind regards,
-=Glyn=-
 
Give opencore a try! It works great. OS beyond Sierra work smoothly.

Oh I've given it a try since I connected my cMP 3 weeks ago and the longer I have it the more I realise its not for me.

I've said before I didn't even realise OpenCore was installed until I checked my Boot ROM version hoping to see the latest 144.0.0.0.0 only to find it reported as 9144.0.7.3.1 and after researching realised it was spoofing the ROM version.

And simple things like editing the SystemParameters.plist file to change ContinuitySupport from false to true to enable Apple Watch Unlock for the upgraded BCM94360CD Airport card and a few other things like I did on my iMac only the other day are made more complex by OpenCore spoofing the motherboard ID so it is not clear how/which or even if I can modify the plist.

I would at this point in time sacrifice OpenCore completely if it made it straightforward just to modify the entry in the plist above to enable full Continuity/Handoff.

And that's just the tip of the iceberg for me. 10.000 replies in this thread alone means I will never be up to speed on it and thats not including the many thousands more on related subject matter. My Modus Operandi has always been KISS...Keep It Simple Stupid even more so since I turned 60 and am struggling to learn anything new and even printed manuals often don't make much sense to me any more! :confused:

That's not to take anything away from those geniuses who figure it out in the first place and share their knowledge with others who in turn share their experiences with the rest of us. I am in awe of the discoveries & workarounds and gladly contribute my own humble experiences when I can.

Things is I don't have any desire to upgrade beyond High Sierra as my 2011 iMac is stuck there for ever and I have held my other Macs on HS as for peace of mind I would prefer them to be all on the same macOS rather than mix 'n match.

Having said that I might be tempted to try Mojave on the cMP if I can safely do so without using OpenCore or any other jiggery pokery and if I like it might install on all but the iMac as although I have been inside to replace a faulty HDD and ended up fitting 2 SSD's and the BCM94360CD Airport card I have no desire to start playing around with graphics cards which could leave me dependant upon OpenCore or other workarounds on that machine.

I'm just waiting to see if by removing OpenCore it might impact anything else on the cMP before I disable it.

Thanks & kind regards,
-=Glyn=-
 
Hello

After reading the good news regarding mac os 12.1 final support (no need for SurPlus anymore), and needing hi-refresh display support, I decided to migrate from 11.6 to 12.1.

I first ran the upgrade to Open Core 0.7.6 without any issue (I was using a config based on this guide, with some some manual tweaks for GPU support, video acceleration...).

Then I ran the upgrade to Monterey 12.1 using Apple software update. It took some times, but overall it went well, until the first post-install boot. The boot went fine until the loading of graphic drivers, then the display flashed to a grey screen with woring cursor for 3 seconds, before reverting to a freezed Apple boot logo screen, sometimes black, sometimes grey.

I tried with a native GeForce 120GT I kept around for troubleshooting boot issues, same issue.
I tried resetting the PRAM multiple time (5 chimes), same issue.
I tried a brand new config with OCLP 0.3.3 and minimal spoofing, same issue.
I tried a reinstall of Monterey with a USB stick installer prep with OCLP, same issue.

Safe boot is working fine, but as soon as tried normal boot it hangs.

Even with OCLP verbose mode, it's really hard to get proper KP reports or relevant boot logs. When the issue happens, I get no KP report on the next safe mode boot.

Here the syptoms (verbose mode, sorry for the quality) :

- everything went fine up to this point
before-crash.jpg

- then the screen went black, and flash to this state (sometimes with working cursor) :
intermediate-screen.jpg

- and after 3 seconds fall back to :
freezed-screen.jpg


Looks like a remanent image in the framebuffer...

The boot lok seems to end on the successful loading of the Audio drivers :

2021-12-29 09:50:37.187620+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) - IOAudioEngine[<private>]::resumeAudioEngine() returns 0x0
2021-12-29 09:50:37.187624+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) IOAudioStream[<private>]::setFormat(<private>, <private>) returns 0x0
2021-12-29 09:50:37.187626+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) +- IOAudioEngine[<private>]::completeConfigurationChange()
2021-12-29 09:50:37.187747+0000 0x573 Default 0x0 0 0 kernel: (AppleHDA) levelControl->setValueChangeHandler ( &changeVolumeHandler <private>, this <private> ) for coreAudioChannelID 0
2021-12-29 09:50:37.187751+0000 0x573 Default 0x0 0 0 kernel: (AppleHDA) controlID: 5, coreAudioChannelID = 0 MASTER oldValue 0x3A, newValue 0x3A
2021-12-29 09:50:37.400790+0000 0x5bb Default 0x0 0 0 kernel: (HFS) hfs: mounted Data on device disk5s2
2021-12-29 09:50:37.466789+0000 0x275 Default 0x0 0 0 kernel: (Intel82574L) 0x1face001, 0x00000000 Intel82574L::setLinkStatus - not active
2021-12-29 09:50:37.494282+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) - IOAudioEngine[<private>]::start(<private>, <private>)
2021-12-29 09:50:37.494285+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) - IOAudioEngine[<private>]::start(<private>) returns 1
2021-12-29 09:50:37.494298+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) + IOAudioEngine[<private>]::registerService(0x0)
2021-12-29 09:50:37.494299+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) + IOAudioEngine[<private>]::updateChannelNumbers ()
2021-12-29 09:50:37.494303+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) o=2 i=10
2021-12-29 09:50:37.494310+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) - IOAudioEngine[<private>]::updateChannelNumbers ()
2021-12-29 09:50:37.494490+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) - IOAudioEngine[<private>]::registerService(0x0)
2021-12-29 09:50:37.494503+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) + IOAudioEngine[<private>]::start(<private>)
2021-12-29 09:50:37.494505+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) + IOAudioEngine[<private>]::start(<private>, <private>)
2021-12-29 09:50:37.494509+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) +-IOAudioEngine[<private>]::initHardware(<private>)
2021-12-29 09:50:37.494535+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) + IOAudioEngine[<private>]::updateChannelNumbers ()
2021-12-29 09:50:37.494538+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) o=0 i=0
2021-12-29 09:50:37.494539+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) - IOAudioEngine[<private>]::updateChannelNumbers ()
2021-12-29 09:50:37.494680+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) + IOAudioEngine[<private>]::setInputSampleOffset(0x1)
2021-12-29 09:50:37.494684+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) - IOAudioEngine[<private>]::setInputSampleOffset(0x1)
2021-12-29 09:50:37.494685+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) + IOAudioEngine[<private>]::addAudioStream(<private>)
2021-12-29 09:50:37.494705+0000 0x573 Default 0x0 0 0 kernel: (IOAudioFamily) - IOAudioEngine[<private>]::addAudioStream(<private>) returns 0x0


Does this issue look familiar to you ?
I'm wondering if it's a really a graphic driver issue, because it's the same behavior with the RX 5700 XT and the old GT 120...

I'm out of options right now, I don't know what to try next...

Thanks a lot for your help !
 
^I certainly don't truly know what might be wrong with your current OC setup, but, if I were you, I'd use the generic safe config.plist provided by @cdf (see post #1) and see if that solves the particular graphics problem you are experiencing. If it does, I would then customize config.plist and fine-tune it to your particular hardware, et cetera. If @cdf's config.plist doesn't solve your problem at all, chances are something is fundamentally wrong with your hardware.
 
Hello to everybody. In this days I thought to replace my ESP (nvme SSD on PCIe adapter), but get some trouble that made me go back to pervious ESP. So, which is the best way do replace my nvme SSD, having only one PCIe adapter?
I made a backup from main ESP partition (boot partition with Catalina) with CCC on a SATA drive, and then I copied entri EFI folder to another drive. Then I did a PRAM reset, replaced the nvme SSE and booted my computer with Mojave. But first surprise, CCC won't let my copy back Catalina boot partition because it's a newer OS than Mojave. I thought not so a problem, I copy my EFI folder to new nvme EFI partition, bless it and boot with Catalina from SATA drive. But nothing to do... if I let connected my SATA drive with Catalina, MacPro won't show up anything and after few minutes shuts down at all. If I disconnect SATA Catalina drive, it comes up with Mojave, but seems it won't be booted with OpenCore (no nvram variable), and I can't copy/clone my main boot drive to new nvme. So, did someone a similar operation (replace ESP on nvme SSD), without buying another PCIe adapter? Or is it essential for the operation (I won't use my old nvme on MacPro, because i promised to give it to my son for his 2015 MacBook Pro.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.