Contribute
Register

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

I was delighted to read about the Presonus Quantum fix, but unfortunately I can't get it to work despite @joevt 's wonderful template which fixed the permission issued I ran into before. When clearing the kextcache I get an error message about an invalid signature (-67030), but it also says the kext is allowed. Doing kextstat I can't see anything actually loaded. Are there any specific BIOS settings this kext-mod requires?
 
@joevt
@Mixerjack

Hi -
Finally setting up my Hackintosh.
No luck getting my PreSonus recognized
ie Plugged in >switched on Presonus > switched on Hackintosh > PreSonus shows some TB activity but ultimately reverts back to a solid red light. This is before and after replacing the .plist file in the Quantum kext file with an edited version as per your advised amendment below.

Note that TB *is* confirmed working as I have my Promise Pegasus R4 drives all happily connected, seen and transferring data to and from the machine just fine, at TB speeds.

I have attached a series of text files named after the terminal command used to retrieve the data they contain. The titles should be self explanatory. I have also attached system info. Note that unless the file name contains "WORKING IMAC", they are all from the Hackintosh.

I am extremely new to this, so I assume I have missed something important. Note that I am just guessing that I created suitable bootlog info files below.

Note that I will ultimately want to get this all working under my Sierra Hack system also (I have a dual Mojave / Sierra boot) but happy to deal w Mojave for now and keep it to one thing at a time.

Really hope you are able to help!


............

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.
 

Attachments

  • Info dot plist EDITED KEXT FILE.txt
    5.1 KB · Views: 176
  • ioreg -lw0 HACKINTOSH.txt
    1.5 MB · Views: 373
  • ioreg -lw0 WORKING IMAC.txt
    3 MB · Views: 299
  • ioreg WORKING IMAC.txt
    79.4 KB · Views: 124
  • kextstat | grep -v com.apple.txt
    2.2 KB · Views: 112
  • log show --predicate %22processID == 0%22 --start $(date %22+%Y-%m-%d%22) --debug.txt
    1.4 MB · Views: 272
  • MOJAVE SPECS.png
    MOJAVE SPECS.png
    226.4 KB · Views: 107
  • sudo dmesg.txt
    16.2 KB · Views: 180
  • ioreg HACKINTOSH.txt
    80.2 KB · Views: 185
No luck getting my PreSonus recognized
ie Plugged in >switched on Presonus > switched on Hackintosh > PreSonus shows some TB activity but ultimately reverts back to a solid red light. This is before and after replacing the .plist file in the Quantum kext file with an edited version as per your advised amendment below.

Note that TB *is* confirmed working as I have my Promise Pegasus R4 drives all happily connected, seen and transferring data to and from the machine just fine, at TB speeds.

I have attached a series of text files named after the terminal command used to retrieve the data they contain. The titles should be self explanatory. I have also attached system info. Note that unless the file name contains "WORKING IMAC", they are all from the Hackintosh.

I am extremely new to this, so I assume I have missed something important. Note that I am just guessing that I created suitable bootlog info files below.
Info dot plist EDITED KEXT FILE.txt shows your edited kext. It looks correct, and plutil "Info dot plist EDITED KEXT FILE.txt" says the format is ok.

ioreg without -lw0 is kind of useless (-lw0 is a superset of the info) so those two files can be ignored.

ioreg -lw0 WORKING IMAC.txt shows the Presonus working - the device is named pci1c67,101 which matches the Quantum1 personality that you edited in the kext.

ioreg -lw0 HACKINTOSH.txt shows that the pci1c67,101 device is connected but the kext driver didn't attach itself.

kextstat | grep -v com.apple.txt shows all the non apple kexts that are loaded. The Presonus kext is not among them.

log show --predicate %22processID == 0%22 --start $(date %22+%Y-%m-%d%22) --debug.txt shows log from current day only. It contains no info about Quantum/Presonus. Maybe the driver was completely skipped.

sudo dmesg.txt doesn't show info about Quantum/Presonus either.

Did you rebuild the kextcache? sudo kextcache -I /

Try loading the kext manually? sudo kextload -v 6 /path/to/kext
 
Thanks @joevt

Did you rebuild the kextcache? sudo kextcache -I /

Try loading the kext manually? sudo kextload -v 6 /path/to/kext

Rebuilding the kext cache - Terminal said: "No work to do; check options and try again."
Pasted:

Bens-iMac-Pro:~ ben$ sudo kextcache -I /
Password:
No work to do; check options and try again.
usage: kextcache -prelinked-kernel <filename> [options] [--] [kext or directory]

kextcache -system-prelinked-kernel
kextcache [options] -prelinked-kernel
kextcache -invalidate <volume>
kextcache -update-volume <volume> [options]
kextcache -system-caches [options]

use kextcache -help for an explanation of each option
----------------------------------------------------------

After running this command:
sudo kextload -v 6 /Library/Extensions/quantum_driver.kext

Pasted from Terminal after I ensured Library and Extensions and the kext file itself have comprehensively universal read and write permissions enabled:

Kext user-space log filter changed from 0xff2 to 0xfff.

Kext kernel-space log filter changed from 0xff2 to 0xfff.

Requesting load of /Library/Extensions/quantum_driver.kext.

/Library/Extensions/quantum_driver.kext failed to load - (libkern/kext) authentication failure (file ownership/permissions); check the system/kernel logs for errors or try kextutil(8).
__________________________________________

What next? I have no idea what "kextutil(8)" is - do I need to research and try it?
 
What version of macOS are you running?

Check owner/permission of all files and folders in the kext:
Code:
find /Library/Extensions/quantum_driver.kext -exec ls -dl {} \;

Fix owner/permissions of all files and folders in the kext:
Code:
sudo chown -R root:wheel /Library/Extensions/quantum_driver.kext
sudo find /Library/Extensions/quantum_driver.kext -type d -exec /bin/chmod 0755 {} \;
sudo find /Library/Extensions/quantum_driver.kext -type f -exec /bin/chmod 0644 {} \;

kextutil can also manually load a kext plus it can do other stuff.
The (8) part refers to a section of the manual (man) pages. For example, you can type man printf which gives you information about the printf command line in the (1) BSD General Commands Manual but to get the man page for the printf function (used in C code), you need to specify the 3rd manual like this man 3 printf where 3 is for (3) BSD Library Functions Manual. There's only one kextutil so man kextutil and man 8 kextutil will show the same result from (8) BSD System Manager's Manual. Type man man for more information. Actually, man pages are easier to look at in Terminal.app if you type the word (don't press return), then right click the word and select "Open man page".

After fixing the owner and permissions, try sudo kextload -v 6 /Library/Extensions/quantum_driver.kext again.

If it works then you can rebuild the kextcache with this: sudo kextcache -i / It seems that the forum post editor made the -i uppercase (probably a Safari thing).
 
@joevt

Check owner/permission of all files and folders in the kext:
Code:
find /Library/Extensions/quantum_driver.kext -exec ls -dl {} \;

Result:

Bens-iMac-Pro:~ ben$ find /Library/Extensions/quantum_driver.kext -exec ls -dl {} \;
drwxrwxrwx@ 3 ben wheel 96 9 Nov 04:25 /Library/Extensions/quantum_driver.kext
drwxrwxrwx 7 ben wheel 224 1 Jan 11:42 /Library/Extensions/quantum_driver.kext/Contents
-rwxrwxrwx 1 ben wheel 1653 9 Nov 04:25 /Library/Extensions/quantum_driver.kext/Contents/CodeResources
drwxrwxrwx 3 ben wheel 96 31 Dec 14:49 /Library/Extensions/quantum_driver.kext/Contents/_CodeSignature
-rwxrwxrwx 1 ben wheel 3102 9 Nov 04:25 /Library/Extensions/quantum_driver.kext/Contents/_CodeSignature/CodeResources
drwxrwxrwx 3 ben wheel 96 31 Dec 14:49 /Library/Extensions/quantum_driver.kext/Contents/MacOS
-rwxrwxrwx 1 ben wheel 627472 9 Nov 04:25 /Library/Extensions/quantum_driver.kext/Contents/MacOS/quantum_driver
drwxrwxrwx 5 ben wheel 160 31 Dec 14:49 /Library/Extensions/quantum_driver.kext/Contents/Resources
-rwxrwxrwx 1 ben wheel 20774 9 Nov 04:25 /Library/Extensions/quantum_driver.kext/Contents/Resources/__config
-rwxrwxrwx 1 ben wheel 121718 9 Nov 04:25 /Library/Extensions/quantum_driver.kext/Contents/Resources/type_traits
-rwxrwxrwx 1 ben wheel 2579 9 Nov 04:25 /Library/Extensions/quantum_driver.kext/Contents/Resources/cstddef
-rwxrwxrwx@ 1 ben wheel 5248 1 Jan 11:42 /Library/Extensions/quantum_driver.kext/Contents/Info.plist

Fix owner/permissions of all files and folders in the kext:
Code:
sudo chown -R root:wheel /Library/Extensions/quantum_driver.kext
sudo find /Library/Extensions/quantum_driver.kext -type d -exec /bin/chmod 0755 {} \;
sudo find /Library/Extensions/quantum_driver.kext -type f -exec /bin/chmod 0644 {} \;

Terminal log for subsequent commands:

Bens-iMac-Pro:~ ben$ sudo chown -R root:wheel /Library/Extensions/quantum_driver.kext
Password:
Bens-iMac-Pro:~ ben$ sudo find /Library/Extensions/quantum_driver.kext -type d -exec /bin/chmod 0755 {} \;
Bens-iMac-Pro:~ ben$ sudo find /Library/Extensions/quantum_driver.kext -type f -exec /bin/chmod 0644 {} \;
Bens-iMac-Pro:~ ben$ sudo kextload -v 6 /Library/Extensions/quantum_driver.kext
Kext user-space log filter changed from 0xff2 to 0xfff.
Kext kernel-space log filter changed from 0xff2 to 0xfff.
Requesting load of /Library/Extensions/quantum_driver.kext.
/Library/Extensions/quantum_driver.kext loaded successfully (or already loaded).
Bens-iMac-Pro:~ ben$

So far so good! I'll now restart and see what happens...
 
@joevt Darn, nothing's changed as far as the Presonus goes. See attached new data... does this info shed any light?
 

Attachments

  • ioreg -lw0 HACKINTOSH.txt
    1.5 MB · Views: 273
  • kextstat | grep -v com.apple.txt
    1.5 MB · Views: 105
  • sudo log show --predicate %22processID == 0%22 --start $(date %22+%Y-%m-%d%22) --debug.txt
    2 MB · Views: 99
@joevt Darn, nothing's changed as far as the Presonus goes. See attached new data... does this info shed any light?
kextstat is a duplicate of ioreg.

Why don't you show the results of the last commands I gave you? find and kextload?

Did kextcache succeed?
 
kextstat is a duplicate of ioreg.

Why don't you show the results of the last commands I gave you? find and kextload?

Did kextcache succeed?

I thought I did show the results in my posts? #311 to #313 above?
ie I cut and pasted everything from Terminal, including
"Requesting load of /Library/Extensions/quantum_driver.kext.
/Library/Extensions/quantum_driver.kext loaded successfully (or already loaded)."

Sorry @joevt, I am extremely, *extremely* new to this, but isn't this correctly reporting the outcomes of these commands? I can run a "find and kextload", sure - again, this is new to me, including the "find and kextload" command.

"Did kextcache succeed?"

See my post #311 above - I cut and paste everything Terminal gave me. Briefly:
"No work to do; check options and try again."

Maybe have a look at my last few posts from #311 onwards - I thought I was reporting back correctly but likely not...

Also, forgot to mention in response to your q that I am running 10.14.6 but I did provide this info in my first post w all attachments about my system info etc... I am trying to be thorough, despite my relative ignorance on how to do all of this....

Why don't you show the results of the last commands I gave you?

If I failed to do this in my replies #311 and #313, please slap me with a fish and tell me....

find and kextload?

I will read about how and try this as soon as I can - presently at work.
 
Last edited:
Back
Top