Contribute
Register

Using a Presonus Quantum Thunderbolt 2 Audio Interface...HELP

Joined
Oct 20, 2019
Messages
10
Graphics
AMD Radeon Pulse RX580 8Gb (MVC modified)
Thanks Man, Yeah I know Joevt Seems to like the Guru of this Things!!!!
 
Joined
Apr 5, 2016
Messages
739
Motherboard
GIGABYTE Z170X-Gaming 7
CPU
i7-6700K
Graphics
GTX TITAN X
Mac
iMac, MacBook, MacBook Air, MacBook Pro, Mac mini, Mac Pro
Classic Mac
Apple, LC, Power Mac
Mobile Phone
iOS
The PCIe card worked ONLY after the issue with memory allocation was addressed. Basically I had to get thunderbolt to work in order to get the PCIe card to work. On a z390 Designaire, which has onboard Titan Ridge chipset and 2 thunderbolt ports, I had to scrap FakeSMC and replace with VirtualSMC. I'm not sure how the issue with VRAM is going to be addressed on a real Mac Pro without "hackintoshing" it as one would in order to implement Thunderbolt.
VRAM (actually DART/IOMMU) works on a real Mac Pro without hackintoshing it.

The single biggest reason that turns people away from running Thunderbolt on a real 2012 Mac Pro is that you have to wake up that same Thunderbolt driver in Windows using Bootcamp and then soft boot into macOS for it to function. The moment you disconnect your machine from power or do a regular shutdown, you have to boot into Windows and initialize the TH3 card again before soft booting into macOS again.
Takes a few minutes to boot Windows and warm boot to macOS. Or just never shutdown :)

This is actually normal until Slate finds a way around requiring too much memory upfront. Your workaround, for now, has to be resetting NVRAM each time you decide to restart your computer. @joevt is a lot smarter than me and he may have other ideas, but this seems to be the source of problems with cards like VRS-8 and PreSonus quantum.
I don't know why there would be a problem since DART/IOMMU works on the Mac Pro. Check the system logs for errors.
 
Joined
Oct 20, 2019
Messages
10
Graphics
AMD Radeon Pulse RX580 8Gb (MVC modified)
Hi guys there is another problem, resetting the NVRAM seems to be working BUT!, it doesn't work just like that I have to disconnect all the cables from the VRS8 and the PCI, connect them again and then reset the NVRAM that's the only way its seems to be connecting. I can do that right now because I have my desk moved off the wall since I'm fixing other stuffs in the studio, but once its back in place I won't be able to do it that way. I've been reading this whole thread over and over again and the more I read the more I'm getting to understand more parts of it, I'm willing to do what ever it takes to get this interface working with my computer and I'll do it at my own risk, I just need some guidance. I already downloaded: Clover configurator, IOResgistryExplorer, MaciASL not sure if I need them but just in case, I notice that after page 8 on this thread you guys started figuring out the work around, there are som parts I understand some parts I still not, I'm trying to get a coder friend here Miami that can help me with it, thank you I don't wanna be a bother but I really need the help thanks.
 
Joined
Apr 5, 2016
Messages
739
Motherboard
GIGABYTE Z170X-Gaming 7
CPU
i7-6700K
Graphics
GTX TITAN X
Mac
iMac, MacBook, MacBook Air, MacBook Pro, Mac mini, Mac Pro
Classic Mac
Apple, LC, Power Mac
Mobile Phone
iOS
Hi guys there is another problem, resetting the NVRAM seems to be working BUT!, it doesn't work just like that I have to disconnect all the cables from the VRS8 and the PCI, connect them again and then reset the NVRAM that's the only way its seems to be connecting. I can do that right now because I have my desk moved off the wall since I'm fixing other stuffs in the studio, but once its back in place I won't be able to do it that way. I've been reading this whole thread over and over again and the more I read the more I'm getting to understand more parts of it, I'm willing to do what ever it takes to get this interface working with my computer and I'll do it at my own risk, I just need some guidance. I already downloaded: Clover configurator, IOResgistryExplorer, MaciASL not sure if I need them but just in case, I notice that after page 8 on this thread you guys started figuring out the work around, there are som parts I understand some parts I still not, I'm trying to get a coder friend here Miami that can help me with it, thank you I don't wanna be a bother but I really need the help thanks.
If it's working, then I don't think there's anything else to do except figure out how to get it to work after a reboot (because you shouldn't have to reset NVRAM every time).

Turn the Mac off and the VRS8 off. Connect cables. Turn VRS8 on. Then turn Mac on. Does it work?

Restart (warm boot) Mac. Works? If not, try cold boot (turn off Mac, then turn on Mac).

Does the VRS8 appear in the PCIe list in System Information.app? When it works? When it doesn't work?
 
Joined
Oct 20, 2019
Messages
10
Graphics
AMD Radeon Pulse RX580 8Gb (MVC modified)
If it's working, then I don't think there's anything else to do except figure out how to get it to work after a reboot (because you shouldn't have to reset NVRAM every time).

Turn the Mac off and the VRS8 off. Connect cables. Turn VRS8 on. Then turn Mac on. Does it work?

Restart (warm boot) Mac. Works? If not, try cold boot (turn off Mac, then turn on Mac).

Does the VRS8 appear in the PCIe list in System Information.app? When it works? When it doesn't work?
Well I actually I have been able to connect the interface three times only. Every time has been a different way If I try to replicate the exact same way to the prior time that I got the interface connected it doesn't work, so far I'm opting to just let the computer and the interface on the next time I get them to connect.

This picture is when the interface doesn't connect
Screen Shot 2019-10-24 at 1.48.06 PM.png
Screen Shot 2019-10-20 at 12.26.01 PM.png
Screen Shot 2019-10-30 at 5.51.29 PM.png


This is when the interface gets connected
Screen Shot 2019-10-30 at 4.22.30 PM.png
Screen Shot 2019-10-30 at 4.23.52 PM.png



I forgot to take a picture of System information when it was connected


Maybe it has nothing to do with this problem but it called my attention the other day I saw a guy re activating Bootcamp on a not supported Mac he right clicked on the Bootcamp assistant app when to Show package content and then went to info.plist there was a black list of unsupported Macs he deleted the name of his Mac from the list then he was able to open Bootcamp assistant I'm wondering if the work around for this could be something like that
 

Attachments

Last edited:
Joined
Apr 5, 2016
Messages
739
Motherboard
GIGABYTE Z170X-Gaming 7
CPU
i7-6700K
Graphics
GTX TITAN X
Mac
iMac, MacBook, MacBook Air, MacBook Pro, Mac mini, Mac Pro
Classic Mac
Apple, LC, Power Mac
Mobile Phone
iOS
Well I actually I have been able to connect the interface three times only. Every time has been a different way If I try to replicate the exact same way to the prior time that I got the interface connected it doesn't work, so far I'm opting to just let the computer and the interface on the next time I get them to connect.
Is it failing because the driver isn't loading or because the PCIe device isn't detected? Run lspci from pciutils when it works and when it doesn't work.
 
Joined
Jan 12, 2019
Messages
41
Motherboard
Aorus z390 Pro Rev. 1.0
CPU
i7 8700K
Graphics
RX-580
Hey there, so it looks like it knows there is an audio device on my mojave hack which is on an aorus z390 pro.

I can't get the Presonus 2 to get recognized. I have it hooked up to an alpine ridge card with a thunderbolt 2 adapter (startech).

Should I try figuring out how to do a soft boot from windows or change some settings with clover or something?

Please and thank you,

LSPCI says:
Code:
Abbys-iMac-Pro:~ abby$ lspci -b -nn

pcilib: 0000:00:1f.4 64-bit device address ignored.

pcilib: 0000:00:1f.3 64-bit device address ignored.

pcilib: 0000:00:1f.3 64-bit device address ignored.

pcilib: 0000:01:00.0 64-bit device address ignored.

pcilib: 0000:01:00.0 64-bit device address ignored.

pcilib: 0000:00:16.0 64-bit device address ignored.

pcilib: 0000:00:14.2 64-bit device address ignored.

pcilib: 0000:00:14.2 64-bit device address ignored.

pcilib: 0000:00:14.0 64-bit device address ignored.

pcilib: 0000:00:12.0 64-bit device address ignored.

00:00.0 Host bridge [0600]: Intel Corporation 8th Gen Core Processor Host Bridge/DRAM Registers [8086:3ec2] (rev 07)

00:01.0 PCI bridge [0604]: Intel Corporation Xeon E3-1200 v5/E3-1500 v5/6th Gen Core Processor PCIe Controller (x16) [8086:1901] (rev 07)

00:12.0 Signal processing controller [1180]: Intel Corporation Cannon Lake PCH Thermal Controller [8086:a379] (rev 10)

00:14.0 USB controller [0c03]: Intel Corporation Cannon Lake PCH USB 3.1 xHCI Host Controller [8086:a36d] (rev 10)

00:14.2 RAM memory [0500]: Intel Corporation Cannon Lake PCH Shared SRAM [8086:a36f] (rev 10)

00:16.0 Communication controller [0780]: Intel Corporation Cannon Lake PCH HECI Controller [8086:a360] (rev 10)

00:17.0 SATA controller [0106]: Intel Corporation Cannon Lake PCH SATA AHCI Controller [8086:a352] (rev 10)

00:1b.0 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port #17 [8086:a340] (rev f0)

00:1b.4 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port #21 [8086:a32c] (rev f0)

00:1c.0 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port #1 [8086:a338] (rev f0)

00:1c.7 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port #8 [8086:a33f] (rev f0)

00:1d.0 PCI bridge [0604]: Intel Corporation Cannon Lake PCH PCI Express Root Port #9 [8086:a330] (rev f0)

00:1f.0 ISA bridge [0601]: Intel Corporation Z390 Chipset LPC/eSPI Controller [8086:a305] (rev 10)

00:1f.3 Audio device [0403]: Intel Corporation Cannon Lake PCH cAVS [8086:a348] (rev 10)

00:1f.4 SMBus [0c05]: Intel Corporation Cannon Lake PCH SMBus Controller [8086:a323] (rev 10)

00:1f.5 Serial bus controller [0c80]: Intel Corporation Cannon Lake PCH SPI Controller [8086:a324] (rev 10)

00:1f.6 Ethernet controller [0200]: Intel Corporation Ethernet Connection (7) I219-V [8086:15bc] (rev 10)

01:00.0 VGA compatible controller [0300]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere [Radeon RX 470/480/570/570X/580/580X/590] [1002:67df] (rev e7)

01:00.1 Audio device [0403]: Advanced Micro Devices, Inc. [AMD/ATI] Ellesmere HDMI Audio [Radeon RX 470/480 / 570/580/590] [1002:aaf0]

02:00.0 Non-Volatile memory controller [0108]: Samsung Electronics Co Ltd NVMe SSD Controller SM981/PM981/PM983 [144d:a808]

03:00.0 PCI bridge [0604]: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] [8086:15d3] (rev 02)

04:00.0 PCI bridge [0604]: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] [8086:15d3] (rev 02)

04:01.0 PCI bridge [0604]: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] [8086:15d3] (rev 02)

04:02.0 PCI bridge [0604]: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] [8086:15d3] (rev 02)

04:04.0 PCI bridge [0604]: Intel Corporation JHL6540 Thunderbolt 3 Bridge (C step) [Alpine Ridge 4C 2016] [8086:15d3] (rev 02)

08:00.0 System peripheral [0880]: Intel Corporation JHL6540 Thunderbolt 3 NHI (C step) [Alpine Ridge 4C 2016] [8086:15d2] (rev 02)

09:00.0 PCI bridge [0604]: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013] [8086:156d]

0a:00.0 PCI bridge [0604]: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013] [8086:156d]

0a:04.0 PCI bridge [0604]: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013] [8086:156d]

0a:05.0 PCI bridge [0604]: Intel Corporation DSL5520 Thunderbolt 2 Bridge [Falcon Ridge 4C 2013] [8086:156d]

0d:00.0 Multimedia audio controller [0401]: Unknown device [1c67:0102]

6f:00.0 Network controller [0280]: Broadcom Inc. and subsidiaries BCM43602 802.11ac Wireless LAN SoC [14e4:43ba] (rev 01)
 
Last edited:
Joined
Jan 12, 2019
Messages
41
Motherboard
Aorus z390 Pro Rev. 1.0
CPU
i7 8700K
Graphics
RX-580
The quantum_driver.kext has a lot of logging code in it (use the "strings quantum_driver.kext/Contents/MacOS/quantum_driver" command to see all of the possible messages and other stuff) but I don't know where the log goes.

You can try doing another boot log, but if it doesn't contain a log message from those listed by the strings command, then it's useless. The error I'm expecting to see that is similar to the error from the VRS8 driver is "IOBufferMemoryDescriptor::inTaskWithPhysicalMask failed" from the "TLSTATUS torilogic::DmaBuffer::Allocate(uint64_t, uint64_t)" method. Actually, that might not be the problem because it doesn't appear to be using the kIOMemoryPhysicallyContiguous option.

Maybe you can tell their tech support that the driver loads (as seen in "kextstat") but doesn't attach to the device (as seen in IORegistryExplorer.app), and that you would like to know how to see the driver log messages to find out why (since the driver log messages don't seem to appear in the system log in Console.app or with the "log show" command).

The driver doesn't have a probe routine. It has an init routine that doesn't do much. The start routine is interesting. It looks for a "IOPCITunnelled" property. If it's not found then the "virtual bool com_presonus_quantum_driver_Device::start(IOService *)" routine will log a "no thunderbolt" message (to whatever the unknown logging system is). You should tell their tech support to fix their driver so it doesn't look for Thunderbolt related properties such as "IOPCITunnelled" if it doesn't affect the functioning of the device.

Maybe edit the info.plist of the quantum_driver.kext so the Quantum1 personality includes the following two lines:
Code:
            <key>IOPCITunnelled</key>
            <true/>
Update the kext cache. Reboot. See if it works. Dump a new ioreg to see if the IOPCITunnelled property was added and to show if the driver gets attached.
Hey I see this now, @joevt, I found the quantum_driver.kext . I added the IOPCTUnnelled code as indicated, but when I go to rebuild the kext chache I get errors:

Code:
sudo kextcache -i /


Kext rejected due to improper filesystem permissions: <OSKext 0x7f8d91db4d40 [0x7fff977f38e0]> { URL = "file:///Library/Extensions/quantum_driver.kext/", ID = "com.presonus.pae-quantum" }


/Library/Extensions/quantum_driver.kext does not authenticate; omitting.


Kext with invalid signatured (-67062) allowed: <OSKext 0x7f8d9186a550 [0x7fff977f38e0]> { URL = "file:///System/Library/Extensions/lspcidrv.kext/", ID = "com.evosx86.driver.lspcidrv" }


KernelCache ID: 908A62F57967B7A47CAC60ECACC6956A


Kext with invalid signatured (-67062) allowed: <OSKext 0x7f82ecb6aa20 [0x7fff977f38e0]> { URL = "file:///System/Library/Extensions/lspcidrv.kext/", ID = "com.evosx86.driver.lspcidrv" }


Kext rejected due to improper filesystem permissions: <OSKext 0x7f82ee9f2440 [0x7fff977f38e0]> { URL = "file:///Library/Extensions/quantum_driver.kext/", ID = "com.presonus.pae-quantum" }
Thanks!
 
Last edited:
Joined
Jan 12, 2019
Messages
41
Motherboard
Aorus z390 Pro Rev. 1.0
CPU
i7 8700K
Graphics
RX-580
So I used kext beast, then

Code:
 Repair permissions in /S/L/E (System/Library/Extensions) and /L/E (Library/Extensions) folders

Type each of the following commands (separately) in Terminal:
[LIST]
[*]sudo chmod -Rf 755 /S*/L*/E*
[*]sudo chmod -Rf 755 /L*/E*
[*]sudo chown -Rf 0:0 /S*/L*/E*
[*]sudo chown -Rf 0:0 /L*/E*
[/LIST]

Rebuild Kext Cache
Type the following command in the Terminal:
[LIST]
[*]sudo kextcache -i /
[/LIST]
Restart your computer for the repairs to take effect.
Still tries to connect during boot, blue flashes, and fails :'(
 
Last edited:
Joined
Apr 5, 2016
Messages
739
Motherboard
GIGABYTE Z170X-Gaming 7
CPU
i7-6700K
Graphics
GTX TITAN X
Mac
iMac, MacBook, MacBook Air, MacBook Pro, Mac mini, Mac Pro
Classic Mac
Apple, LC, Power Mac
Mobile Phone
iOS
Hey there, so it looks like it knows there is an audio device on my mojave hack which is on an aorus z390 pro.

I can't get the Presonus 2 to get recognized. I have it hooked up to an alpine ridge card with a thunderbolt 2 adapter (startech).

Should I try figuring out how to do a soft boot from windows or change some settings with clover or something?

LSPCI says:
Code:
Abbys-iMac-Pro:~ abby$ lspci -b -nn
0d:00.0 Multimedia audio controller [0401]: Unknown device [1c67:0102]
Use [ code] [ /code] when quoting text from command line or source code. The device is in your lspci output (lspci -nnvt might be more informative) but the driver didn't load.

Kext rejected due to improper filesystem permissions: <OSKext 0x7f8d91db4d40 [0x7fff977f38e0]> { URL = "file:///Library/Extensions/quantum_driver.kext/", ID = "com.presonus.pae-quantum" }
I like BBEdit.app because it restores the permission when you save. If the kext cache was updated properly, then you should be able to see errors now in the log. Use kexstat to make sure the kext is working. Then use Console.app to check for errors. Maybe there aren't any? #219 #222
Mixerjack says the IOPCITunnelled key with true value ( #222 ) was sufficient #224 .

Is VT-d enabled in BIOS and DART=0 removed from config.plist?
 
Top