MP 1,1-5,1 testing TB3 AIC with MP 5,1

DSM2.Hackintosh · Mar 4, 2020

@Itconnects thanks for the reports. The problems are not related to the firmware itself it's a MacPro5.1 thing. But the issues you have with the Apollo and OpenCore are really strange.

Just to be sure, was this your process on the opencore part?

This EFI folder must be copied to the invisible EFI partition on the system disk. Delete the existing one there completely. Even if it has contents (APPLE\EXTENSIONS etc), delete it, it will be created again at the next system start anyway.

To mount your ESP (EFI system partition) open the terminal (utilities) and type there first:
diskutil list and hit enter

This will list all hard disks and their partitions. Here you can see which EFI partition belongs to your macOS disk. In my case this is just "disk4s1", this will be different for you. Now you type (with "your address":

sudo diskutil mount /dev/disk4s1 and hit enter

the EFI partition is mounted and you will find a HDD Drive called EFI on the desktop Delete the existing EFI folder in the Hard Drive itself and add the new one after.
Now start the "Restore" or "Recover" via terminal with :

sudo nvram "recovery-boot-mode=unused" && sudo reboot recovery and hit enter

This will perform a reboot and it will take a moment and you will find yourself in the "Restore". Here now nothing of all what is offered there, but go to the menu above and call the "Terminal" again. Here you type the command after all partitions are displayed (depending on the speed of the disks at boot time, the order may be different):

diskutil list and hit enter

find your EFI partition again and enter it in the already known command to mount (this time without "sudo" as you already have special rights here), don't forget to enter your "address" instead of the example:

diskutil mount /dev/disk4s1 and hit enter

after that only the "entry point" for booting has to be set again with :

bless --mount /Volumes/EFI --setBoot and hit enter

That's about it. Shut down your computer, unplug it for 15 seconds, then restart it. You will now see the boot loader "OpenCore" for a few seconds, then the default boot drive will be started automatically.

If you do not want to use OpenCore temporarily or want to run the native boot from macOS or other systems:

When booting the computer, keep the "Option-Key" pressed until the bootable drives are displayed on the screen (standard function of a Mac) and then select another boot drive instead of EFI:Boot.

In windows you don't see anything thunderbolt related since you normally would use the bootcamp driver for it.

I will upload something testwise for you later today, if you don't mind you could test this with the opencore method and an other firmware.

Itconnects · Mar 4, 2020

With my extremely limited knowledge. I don’t think the problem is the firmware because the firmware works fine in both windows and MacOS you just have to boot once, and then again and it will initialize.

DSM2.Hackintosh said:
@Itconnects thanks for the reports. The problems are not related to the firmware itself it's a MacPro5.1 thing. But the issues you have with the Apollo and OpenCore are really strange.

Just to be sure, was this your process on the opencore part?

This EFI folder must be copied to the invisible EFI partition on the system disk. Delete the existing one there completely. Even if it has contents (APPLE\EXTENSIONS etc), delete it, it will be created again at the next system start anyway.

To mount your ESP (EFI system partition) open the terminal (utilities) and type there first:
diskutil list and hit enter

This will list all hard disks and their partitions. Here you can see which EFI partition belongs to your macOS disk. In my case this is just "disk4s1", this will be different for you. Now you type (with "your address":

sudo diskutil mount /dev/disk4s1 and hit enter

the EFI partition is mounted and you will find a HDD Drive called EFI on the desktop Delete the existing EFI folder in the Hard Drive itself and add the new one after.
Now start the "Restore" or "Recover" via terminal with :

sudo nvram "recovery-boot-mode=unused" && sudo reboot recovery and hit enter

This will perform a reboot and it will take a moment and you will find yourself in the "Restore". Here now nothing of all what is offered there, but go to the menu above and call the "Terminal" again. Here you type the command after all partitions are displayed (depending on the speed of the disks at boot time, the order may be different):

diskutil list and hit enter

find your EFI partition again and enter it in the already known command to mount (this time without "sudo" as you already have special rights here), don't forget to enter your "address" instead of the example:

diskutil mount /dev/disk4s1 and hit enter

after that only the "entry point" for booting has to be set again with :

bless --mount /Volumes/EFI --setBoot and hit enter

That's about it. Shut down your computer, unplug it for 15 seconds, then restart it. You will now see the boot loader "OpenCore" for a few seconds, then the default boot drive will be started automatically.

If you do not want to use OpenCore temporarily or want to run the native boot from macOS or other systems:

When booting the computer, keep the "Option-Key" pressed until the bootable drives are displayed on the screen (standard function of a Mac) and then select another boot drive instead of EFI:Boot.

In windows you don't see anything thunderbolt related since you normally would use the bootcamp driver for it.

I will upload something testwise for you later today, if you don't mind you could test this with the opencore method and an other firmware.

Okay cool. I don’t think it’s the firmware, with my very very limited knowledge, because it works without open core you just have to boot twice. Just like in windows even without your firmware (only in windows of course). Did you see the video of the guy with 185 serial? What do you think about that?

Also I followed these steps:

RESTART in recovery

Open terminal

“csrutil disable”

“Reboot”

Login

Open clover Application

Mount Partition of boot drive

Replace EFI folder in newly mounted EFI partition with “OC 0.5.6 preview” EFI

Inject ssdt text in config

Add ssdt file in APCI

Bless Open Core Automator, type in password. Nothing happens. I assume it’s in the background.

Shutdown computer

Wait 30 seconds

Restart

Open Core menu #3 (Nvram Reset)

Login

For me I’m happy even with the strange behavior. I only did the test to be kind of the first rat in the maze

Itconnects · Mar 4, 2020

Last test

As it stands. Full shutdown and boot into MacOS does not initialize apollo even though thunderbolt section in system profile shows the apollo twin.

More details:

when I do a full shut down and boot into MacOs (apollo not initialized of course). I went to the system profile to see if the thunderbolt has the apollo twin listed in the Thunderbolt menu. Apollo twin is listed. Wait a a minute or so My computer screen went black and nothing, so I wait... all of a sudden im back into OC menu (No flute Chime)... so I chose option #1 wait for boot. log in. Apollo is fully initialized and working.

No random restart back to OC menu...

Maybe the apollo is trying to initialize the first time but fails and causes an error?

Maybe we need to load the string injection twice? lol

You say you’re a Mac guy, but this is the behavior I noticed on Windows too before your firmware. Windows needed to reload twice... maybe Mac was just doing the second reload which is why it was working? Because if you come back to windows it will work always... but it never works on Windows the first boot. It will show in thunderbolt device manager that Apollo is attached but you have to restart windows to use it...

I can do the first test again and give you the “your computer restarted because there was problem” log for you to see (attached)

I should also note that a long time ago. I added my self as a permission (attached) to my boot drive. I did this by disabling SIP, and then adding it, then renabling SIP

DSM2.Hackintosh · Mar 4, 2020

Yes, the firmware is not a problem but the initialization on the macpro5.1 is one.

But maybe I have a solution for others until everything works like it should via ssdt.

-

I can't follow why you did the nvram reset since this breaks the opencore boot.

You have to boot via opencore otherwise it won't load the ssdt.

But maybe I just misunderstood you - woke up a couple minutes ago.

I will send you something via PM in a couple of minutes. Would be awesome if you could try that and report back.

Itconnects · Mar 4, 2020

DSM2.Hackintosh said:
Yes, the firmware is not a problem but the initialization on the macpro5.1 is one.

But maybe I have a solution for others until everything works like it should via ssdt.

-

I can't follow why you did the nvram reset since this breaks the opencore boot.

You have to boot via opencore otherwise it won't load the ssdt.

But maybe I just misunderstood you - woke up a couple minutes ago.

I will send you something via PM in a couple of minutes. Would be awesome if you could try that and report back.

I did Nvram reset to enable SIP... am I not suppose to do that? Is SIP suppose to be disabled the whole time? I always did it after bless.

***I wrote that Nvram makes it work from full shutdown earlier. This is not true. I deleted that input. It causes the same behavior***

Please read my last post again I added some more brainstorms on the 5.1 behavior

Yes, I can

I can also do one more bless and leave SIP disabled and do a full shutdown. I never checked that one. I have to go to bed in 1 hour.

DSM2.Hackintosh · Mar 4, 2020

Just to be sure, Pin 3/5 is bridged correct ? @Itconnects

Itconnects · Mar 4, 2020

DSM2.Hackintosh said:
Just to be sure, Pin 3/5 is bridged correct ? @Itconnects

The same problem with SIP disabled

I have a wire going from 1 and 3... 1 assumed is the down arrow and not 5. Or should I not put it where the down arrow is?

joevt · Mar 4, 2020

qthegaijin said:
I tried all 3 commands but the last one just returns a message saying "
lspci: Cannot find any working access method."

Edit, had to reboot to get it to work. I have attached all 3 .txt files.

The lspci script contains different info than ioreg. lspci has bus 6a for device 1d4b:a140 while ioreg has bus 69 for pci1d4b,a140. All the commands need to be run at the same time (at least same boot) for the info to be consistent. The bar0 is 32 bit instead of 64 bit according to lspci - maybe you ran out of 32 bit memory? I pulled this info from your lspci - the GC-TITAN RIDGE upstream seems to have a corrupt header type of 00 (device) instead of 01 (bridge). Are you using the latest pciutils? Also, try my pcitree.sh script #1,444 . The command for lspci should be sudo lspci -nnvvv > lspci.txt

Code:

                00:1d.3 Class 0604: Device 8086:a11b (rev f1)
                    Bus: primary=00, secondary=4e, subordinate=7e, sec-latency=0
                    I/O behind bridge: 00002000-0000cfff
                    Memory behind bridge: ec300000-ec5fffff
                    Prefetchable memory behind bridge: 0000000060000000-00000000ebffffff

                    4e:00.0 Class 0604: Device 8086:15ea (rev 06)
                        !!! Invalid class 0604 for header type 00
                        Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B- DisINTx-
                        Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- >SERR- <PERR- INTx-
                        Latency: 0 (4500ns min)
                        Interrupt: pin A routed to IRQ 19
                        Region 2: Memory at <ignored> (type 3, prefetchable)
                        Region 3: I/O ports at <ignored>
                        Region 4: Memory at <ignored> (32-bit, non-prefetchable)
                        Region 5: I/O ports at <ignored>

                        4f:01.0 Class 0604: Device 8086:15ea (rev 06)
                            Bus: primary=4f, secondary=67, subordinate=6a, sec-latency=0
                            I/O behind bridge: 0000f000-00000fff
                            Memory behind bridge: ec500000-ec5fffff
                            Prefetchable memory behind bridge: fffffffffff00000-00000000000fffff

                            67:00.0 Class 0604: Device 8086:1549
                                Bus: primary=67, secondary=68, subordinate=6a, sec-latency=0
                                I/O behind bridge: 0000f000-00000fff
                                Memory behind bridge: ec500000-ec5fffff
                                Prefetchable memory behind bridge: fffffffffff00000-00000000000fffff

                                68:00.0 Class 0604: Device 8086:1549
                                    Bus: primary=68, secondary=6a, subordinate=6a, sec-latency=0
                                    I/O behind bridge: 0000f000-00000fff
                                    Memory behind bridge: ec500000-ec5fffff
                                    Prefetchable memory behind bridge: fffffffffff00000-00000000000fffff

                                    6a:00.0 Class 0000: Device 1d4b:a140 (rev 01)
                                        Region 0: Memory at ec500000 (32-bit, non-prefetchable)
                                           01: phys.hi: 02690010 phys.mid: 00000000 phys.lo: 00000000
                                               size.hi: 00000000 size.lo: 00010000
                                               bus: 105 dev: 0 func: 0 reg: 16
                                               type: Mem flags: rel

                                68:01.0 Class 0604: Device 8086:1549
                                    Bus: primary=68, secondary=69, subordinate=69, sec-latency=0
                                    I/O behind bridge: 0000f000-00000fff
                                    Memory behind bridge: fff00000-000fffff
                                    Prefetchable memory behind bridge: fffffffffff00000-00000000000fffff
                                    Secondary status: 66MHz- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- <MAbort- <SERR- <PERR-

Itconnects said:
The fix kills windows support for thunderbolt. im not sure if open core isthe cause of this too but windows only starts if the computer is fully shut down. Also after using bootcamp control panel OC is disabled

Don't use the Boot Camp control panel. It modifies NVRAM like Startup Disk preferences panel does. When you restart from Windows it should boot whatever was blessed last (from Open Core installation, Boot Camp control panel or Startup Disk preferences panel).

Keep a script on your EFI partition that has the bless command you need to rebless Open Core in case it gets changed by something later (such as a macOS update) so you don't need to remember the command. For example, I have a BBEdit worksheet file on my Catalina boot partition with the commands to restore my Catalina boot preference and disk label.

Code:

sudo bless --folder /Volumes/Catalina\ Boot/macOSCatalinaPatcher --file /Volumes/Catalina\ Boot/macOSCatalinaPatcher/ShellX64.efi --setBoot

source "/Volumes/Apps/File Utilities/diskutil:pdisk:fdisk:gpt/DiskUtil.sh"
makemultilinedisklabel "/Volumes/Catalina Boot/macOSCatalinaPatcher" $'Catalina\n10.15.3'

dump_label /Volumes/Catalina\ Boot/macOSCatalinaPatcher/.disk_label_2x
................................................................................................................................................................
................................................................................................................................................................
................................................................................................................................................................
................................................................................................................................................................
....................2a2a2af6....................................................................................................................................
..............f7abd6d6d6d6d6fef8..............................................................fed6f9..fad6ab....................................................
............f8d6d6d6d6d6d6d6d6d655..........................f6d6d6f7..........................d6d655..fbd6ff....................................................
..........f6d6d6d6fc2a..f6fbd6d6d6f7........................f7d6d62a..........................d6d655..f8fcfb....................................................
..........fcd6d6fb..........80d6d6fb........f7f8f6..........2ad6d6f8..........f7f8f6..........d6d655....................f7f8f6..............f7f8f6..............
..........d6d6ff............f6ffd6fc....80ffd6d6d6ff80....fbd6d6d6d6fe....80ffd6d6d6ff80......d6d655..fad6fe....d6d6fbffd6d6d6fef6......80ffd6d6d6ff80..........
........2ad6d6fa......................fad6d6d6ffd6d6d6fb..fbd6d6d6d6fe..fad6d6d6ffd6d6d6fb....d6d655..fbd6ff....d6d6d6d6d6d6d6d6fd....fad6d6d6ffd6d6d6fb........
........f9d6d6f9......................fed6ab....f6ffd6ab....f7d6d62a....fed6ab....f6ffd6ab....d6d655..fbd6ff....d6d6d680..f6fed6ff....fed6ab....f6ffd6ab........
........55d6d62a......................80fdf8......abd6fe....f7d6d62a....80fdf8......abd6fe....d6d655..fbd6ff....d6d6fd......fad6d6f6..80fdf8......abd6fe........
........f8d6d6f8........................2afbfcabd6d6d6fe....f7d6d62a......2afbfcabd6d6d6fe....d6d655..fbd6ff....d6d655......f8d6d6f6....2afbfcabd6d6d6fe........
........f7d6d6fa..............fcfefd..fbd6d6d6d6d6d6d6fe....f7d6d62a....fbd6d6d6d6d6d6d6fe....d6d655..fbd6ff....d6d6f9......f8d6d6f6..fbd6d6d6d6d6d6d6fe........
..........d6d6fe............f7d6d6fdf6d6d6fffbf9f780d6fe....f7d6d62a..f6d6d6fffbf9f780d6fe....d6d655..fbd6ff....d6d6f9......f8d6d6f6f6d6d6fffbf9f780d6fe........
..........fdd6d6fa..........fcd6d655fad6d6f7......abd6fe....f7d6d62a..fad6d6f7......abd6fe....d6d655..fbd6ff....d6d6f9......f8d6d6f6fad6d6f7......abd6fe........
..........f7d6d6d6802a..2afcd6d6fe..fad6d655....80d6d6fe....f7d6d655..fad6d655....80d6d6fe....d6d655..fbd6ff....d6d6f9......f8d6d6f6fad6d655....80d6d6fe........
............55d6d6d6d6d6d6d6d6ff2a..2ad6d6d6ffd6d6d6d6d6fe....d6d6d6ab2ad6d6d6ffd6d6d6d6d6fe..d6d655..fbd6ff....d6d6f9......f8d6d6f62ad6d6d6ffd6d6d6d6d6fe......
..............f8fed6d6d6d6d6fdf6......fad6d6d6d6fef9fed6d6....fbd6d6ff..fad6d6d6d6fef9fed6d6..ffd6f9..fad6fe....d6d6f8......2ad6d6f6..fad6d6d6d6fef9fed6d6......
..................f6f8f92a..............f6f8f8f6......2af7......f6f6f6....f6f8f8f6......2af7............................................f6f8f8f6......2af7......
................................................................................................................................................................
................................................................................................................................................................
................................................................................................................................................................
..........................f9fbf7............f655fb55f7..........................f6fb55..........2af9f9f9f9f9f9f9....................f75580fb55f6................
..........................d6d655..........80d6d6d6d6d6fb........................fad6ff..........fdd6d6d6d6d6d6d6f8................fad6d6d6d6d6d655..............
......................2afdd6d655........f9d6d6d6abffd6d6fa..................f655d6d6ff..........fed6d6d6d6d6d6d62a..............f9d6d6d6abffd6d6d6f7............
..................f9d6d6d6d6d655........ffd6fff6..f6ffd6ff................fed6d6d6d6ff..........d6d6f8..........................80d6fff7....fbd6d655............
..................f9d6d6d6d6d655......2ad6d655......55d6d6f8..............fed6d6d6d6ff........f7d6d6f6..........................fed680......f6d6d6fb............
....................f6f62ad6d655......f9d6d6f6......f7d6d655................f6f6fcd6ff........f8d6d6558080faf7..................fa80f8......55d6d6f8............
........................f6d6d655......fad6d6..........d6d6fa....................80d6ff........55d6d6d6d6d6d6d6fb......................2a80abd6d6ff..............
........................f6d6d655......fcd6ff..........d6d680....................80d6ff........fbd6d6fffdfdd6d6d655....................fbd6d6d6d680..............
........................f6d6d655......fcd6ff..........d6d6fb....................80d6ff........fbfefdf6....f8d6d6fe....................f780fed6d6d6fb............
........................f6d6d655......80d6d6........f6d6d6fa....................80d6ff......................fcd6d6..........................f6ffd6fe............
........................f6d6d655......fad6d6f7......2ad6d6f9....................80d6ff........f7f7..........80d6d6............2affff2a........80d6d6............
........................f6d6d655......f8d6d6fa......80d6d6f6....................80d6ff......f6d6d6fa........ffd6ff............2ad6d6fa........fcd6d6............
........................f6d6d655........ffd6d6f8..f9d6d6ab....55fdfd............80d6ff........ffd6fff8....fbd6d680....55fdfd....d6d6ff2a..f7fbd6d6fd............
........................f6d6d655........f9d6d6d6d6d6d6fff7....80d6d6............80d6ff........55d6d6d6d6d6d6d6fff6....80d6d6....fad6d6d6d6d6d6d6d62a............
........................f6d6d6f9..........55d6d6d6d6fff8......fbd6d6............fbd6fe..........faffd6d6d6d6abf7......fbd6d6......fbd6d6d6d6d6fef8..............
..............................................2af9f7................................................2af9f8f6........................f62af8f8f7..................
................................................................................................................................................................
................................................................................................................................................................
................................................................................................................................................................

tommy chen · Mar 5, 2020

DSM2.Hackintosh said:
I can't follow why you did the nvram reset since this breaks the opencore boot.

with nicos EFI folder i can do an NVRAM reset and every boot is with OC

DSM2.Hackintosh · Mar 5, 2020

Strange... I had one message from a Mac guy who had this behavior if he did a nvramreset.

However...

Glad and thankful that I can debug soon on a 5.1

You guys rock ?

cdf · Mar 5, 2020

DSM2.Hackintosh said:
Strange... I had one message from a Mac guy who had this behavior if he did a nvramreset.

OpenCore will survive an NVRAM reset if installed on the first bootable partition seen during boot. In my setup, this corresponds to the EFI partition of the drive in Bay 1.

qthegaijin · Mar 5, 2020

joevt said:
The lspci script contains different info than ioreg. lspci has bus 6a for device 1d4b:a140 while ioreg has bus 69 for pci1d4b,a140. All the commands need to be run at the same time (at least same boot) for the info to be consistent. The bar0 is 32 bit instead of 64 bit according to lspci - maybe you ran out of 32 bit memory? I pulled this info from your lspci - the GC-TITAN RIDGE upstream seems to have a corrupt header type of 00 (device) instead of 01 (bridge). Are you using the latest pciutils? Also, try my pcitree.sh script #1,444 . The command for lspci should be sudo lspci -nnvvv > lspci.txt

Attached are another batch from the same boot. I tried to install the PCITREE.sh script but it returns with a "setpci command not found" error.

joevt · Mar 5, 2020

qthegaijin said:
Attached are another batch from the same boot.

ioreg shows pci1d4b,a140 has assigned-addresses and the driver for pci1d4b,a140 has been installed. That means the problem went away? Also, this time your lspci output has no errors (no ! text).

qthegaijin said:
I tried to install the PCITREE.sh script but it returns with a "setpci command not found" error.

pcitree.sh is not a script that installs. You run it to get output that is similar to lspci -nnvt (I think pcitree.sh is more compact while showing more info).

Type cat /etc/paths to view the list of paths. If you followed the instructions, then /usr/local/sbin should be the last among them.

Type ls -l /usr/local/sbin to view the contents of /usr/local/sbin. It should contain lspci and setpci and update-pciids

Type where lspci and where setpci and where update-pciids to find where the commands are. They should all be in /usr/local/sbin. Delete them if they are elsewhere and redo pciutils install.

qthegaijin · Mar 5, 2020

Thank you for the quick reply!

The issue is still there, the device does not populate as an audio device and is not seen by Mac OS as useable, nor does the Antelope Control Panel software see the device as being available to use.

I will check on the locations now to see if everything installed correctly.

qthegaijin · Mar 5, 2020

Edit: I have attached a new batch of txt files using the latest pciutils update., updated pcitree in a later post.

joevt · Mar 5, 2020

qthegaijin said:

Finally got it installed, here is the PCITREE.SH readout.

Code:

#=========================================================================================
┬[0000:00]
├─00:00.0             #                [8086:191f] [0600] (rev 07) Host bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor Host Bridge/DRAM Registers
├┬00:01.0-[01-03]     # g3x8           [8086:1901] [0604] (rev 07) PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16)
│└┬01:00.0-[02-03]    # g3x16 > g3x8   [1022:1470] [0604] (rev c1) PCI bridge: Advanced Micro Devices, Inc. [AMD] Device
│ └┬02:00.0-[03]      # g3x16          [1022:1471] [0604] PCI bridge: Advanced Micro Devices, Inc. [AMD] Device
│  ├─03:00.0          # g3x16          [1002:687f] [0300] (rev c1) VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 XL/XT [Radeon RX Vega 56/64]
│  └─03:00.1          # g3x16          [1002:aaf8] [0403] Audio device: Advanced Micro Devices, Inc. [AMD/ATI] Vega 10 HDMI Audio [Radeon Vega 56/64]
├┬00:01.1-[04]        # g3x8 > g1x1    [8086:1905] [0604] (rev 07) PCI bridge: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x8)
│└─04:00.0            # g1x1           [14e4:43a0] [0280] (rev 03) Network controller: Broadcom Inc. and subsidiaries BCM4360 802.11ac Wireless Network Adapter
├─00:02.0             # g0x0           [8086:1912] [0380] (rev 06) Display controller: Intel Corporation HD Graphics 530
├─00:14.0             #                [8086:a12f] [0c03] (rev 31) USB controller: Intel Corporation 100 Series/C230 Series Chipset Family USB 3.0 xHCI Controller
├─00:16.0             #                [8086:a13a] [0780] (rev 31) Communication controller: Intel Corporation 100 Series/C230 Series Chipset Family MEI Controller #1
├─00:17.0             #                [8086:a102] [0106] (rev 31) SATA controller: Intel Corporation Q170/Q150/B150/H170/H110/Z170/CM236 Chipset SATA Controller [AHCI Mode]
├┬00:1b.0-[05]        # g3x4           [8086:a167] [0604] (rev f1) PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #17
│└─05:00.0            # g3x4           [1987:5012] [0108] (rev 01) Non-Volatile memory controller: Phison Electronics Corporation E12 NVMe Controller
├┬00:1c.0-[06]        # g3x1 > g1x0    [8086:a110] [0604] (rev f1) PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #1
├┬00:1c.1-[07]        # g3x1 > g2x1    [8086:a111] [0604] (rev f1) PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #2
│└─07:00.0            # g2x1           [1b73:1100] [0c03] (rev 10) USB controller: Fresco Logic FL1100 USB 3.0 Host Controller
├┬00:1c.2-[08]        # g3x1 > g1x1    [8086:a112] [0604] (rev f1) PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #3
│└─08:00.0            # g1x1           [8086:1539] [0200] (rev 03) Ethernet controller: Intel Corporation I211 Gigabit Network Connection
├┬00:1c.4-[09-41]     # g3x4 > g1x4    [8086:a114] [0604] (rev f1) PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #5
├┬00:1d.0-[42]        # g1x2 > g1x0    [8086:a118] [0604] (rev f1) PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #9
├┬00:1d.2-[43]        # g3x1 > g1x1    [8086:a11a] [0604] (rev f1) PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #11
│└─43:00.0            # g1x1           [11c1:5901] [0c00] (rev 08) FireWire (IEEE 1394): LSI Corporation FW643 [TrueFire] PCIe 1394b Controller
├┬00:1d.3-[4e-7e]     # g3x1           [8086:a11b] [0604] (rev f1) PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #12
│└┬4e:00.0-[4f-7e]    # g3x4 > g3x1    [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
│ ├┬4f:00.0-[51]      # g1x4           [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
│ │└─51:00.0          # g1x4           [8086:15eb] [0880] (rev 06) System peripheral: Intel Corporation JHL7540 Thunderbolt 3 NHI [Titan Ridge 4C 2018]
│ ├┬4f:01.0-[67-6a]   # g1x4           [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
│ │└┬67:00.0-[68-6a]  # g1x4           [8086:1549] [0604] PCI bridge: Intel Corporation DSL2210 Thunderbolt Controller [Port Ridge 1C 2011]
│ │ ├┬68:00.0-[6a]    # g2x4 > g1x1    [8086:1549] [0604] PCI bridge: Intel Corporation DSL2210 Thunderbolt Controller [Port Ridge 1C 2011]
│ │ │└─6a:00.0        # g1x1           [1d4b:a140] [0000] (rev 01) Non-VGA unclassified device: Device
│ │ └┬68:01.0-[69]    # g2x4 > g1x4    [8086:1549] [0604] PCI bridge: Intel Corporation DSL2210 Thunderbolt Controller [Port Ridge 1C 2011]
│ ├┬4f:02.0-[50]      # g1x1 > g1x4    [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
│ └┬4f:04.0-[52]      # g1x4           [8086:15ea] [0604] (rev 06) PCI bridge: Intel Corporation JHL7540 Thunderbolt 3 Bridge [Titan Ridge 4C 2018]
├┬00:1d.4-[4d]        # g3x2 > g1x0    [8086:a11c] [0604] (rev f1) PCI bridge: Intel Corporation 100 Series/C230 Series Chipset Family PCI Express Root Port #13
├─00:1f.0             #                [8086:a145] [0601] (rev 31) ISA bridge: Intel Corporation Z170 Chipset LPC/eSPI Controller
├─00:1f.2             #                [8086:a121] [0580] (rev 31) Memory controller: Intel Corporation 100 Series/C230 Series Chipset Family Power Management Controller
├─00:1f.3             #                [8086:a170] [0403] (rev 31) Audio device: Intel Corporation 100 Series/C230 Series Chipset Family HD Audio Controller
├─00:1f.4             #                [8086:a123] [0c05] (rev 31) SMBus: Intel Corporation 100 Series/C230 Series Chipset Family SMBus
└─00:1f.6             #                [8086:15b8] [0200] (rev 31) Ethernet controller: Intel Corporation Ethernet Connection (2) I219-V
BANZAIs-Mac-Pro-2:pcitree_fast BANZAI$

Edit: I have attached a new batch of txt files using the latest pciutils update.

Use a text editor to search and replace excessive line feeds. Or output to text file sudo pcitree.sh > pcitree.txt
I don't see anything wrong in the ioreg. The driver is loaded. Check for different errors in the system log. You don't get the BAR0 error anymore, correct?

miztahsparklez · Mar 5, 2020

so here is when i load OC and the SSDT files. No PCI slot 4 at all.

If i remove OC files and boot normal, PCI slot 4 works OK and card is recognized.

qthegaijin · Mar 5, 2020

The error still happens on cold boot. Here are a fresh batch of files from a cold start, with the device plugged in and turned on from boot.

There should be info populated like so:
I have included the IOreg from the working 10.12 alpine ridge so you can see what the driver should look like when populated correctly. The main points of observation are the IOAudioEngineUserClient not being created, clocking information and channels, as well as the proper device name and address not being populated.

Itconnects · Mar 6, 2020

IndioX said:
with nicos EFI folder i can do an NVRAM reset and every boot is with OC

Nicos EFI folder freezes my system on bless. Nvram reset didn’t break open core. Selecting a startup disk in windows did. Windows legacy is def not compatible with OC

DSM2.Hackintosh · Mar 6, 2020

Yes, windows should be EFI too, if so no problems will appear.

Just to give a small update: had yesterday an interesting conversation with @juantrix and he gave me an Idea which I didn't thought about since it runs on my hacks perfectly like on the real 7,1 with the config we setup our ssdt and also runs perfect on the 7,1 itself.

This conversation can possibly help to fix the issues with the MacPro5.1.

Can't guarantee you but it's worth the testing.

Did some debugging tonight as long it was possible for me with fever...

As soon the 5.1 arrives at my place I will start the debugging process on it and of course test the stuff I found out tonight.

powermusic · Mar 6, 2020

Waiting for this!!!

Itconnects · Mar 6, 2020

DSM2.Hackintosh said:
Yes, windows should be EFI too, if so no problems will appear.

Just to give a small update: had yesterday an interesting conversation with @juantrix and he gave me an Idea which I didn't thought about since it runs on my hacks perfectly like on the real 7,1 with the config we setup our ssdt and also runs perfect on the 7,1 itself.

This conversation can possibly help to fix the issues with the MacPro5.1.

Can't guarantee you but it's worth the testing.

Did some debugging tonight as long it was possible for me with fever...

As soon the 5.1 arrives at my place I will start the debugging process on it and of course test the stuff I found out tonight.

Get well soon.

I noticed on the apollo it had a firmware of 7.1 a little bit of a coincidence since your Mac is 7.1? Maybe ?

ampman · Mar 6, 2020

Itconnects said:
Nicos EFI folder freezes my system on bless. Nvram reset didn’t break open core. Selecting a startup disk in windows did. Windows legacy is def not compatible with OC

same here.But Nico is working on it to fix it.

Itconnects · Mar 6, 2020

ampman said:
same here.But Nico is working on it to fix it.

Why not just use DSM2’s? Or use official OC and inject DSM2 string and acpi ?

DSM2.Hackintosh · Mar 6, 2020

Nico is one of my team mates @Itconnects
There are a couple of ssdt versions...
Much more will come...

MP 1,1-5,1 testing TB3 AIC with MP 5,1

macrumors regular

macrumors 6502

macrumors 6502

Attachments

macrumors regular

macrumors 6502

macrumors regular

macrumors 6502

Attachments

macrumors 604

macrumors 6502a

macrumors regular

macrumors 68020

macrumors newbie

Attachments

macrumors 604

macrumors newbie

macrumors newbie

Attachments

macrumors 604

macrumors newbie

Attachments

macrumors newbie

Attachments

macrumors 6502

macrumors regular

macrumors newbie

macrumors 6502

macrumors member

macrumors 6502

macrumors regular

Our Staff