new mac mini M4Pro Sequoia 15.1
Pegasus DEXT Driver V21.1.0-2
installed
Pegasus DEXT Driver Installer.app in Applications
launching installer.cpp raises dialoge :awaiting approval. ... enable ...driver extension in P/S...
THERE is no such pending approval in Privacy and Securitiy
pegasus32 will not mount
Hi Chris,
For some reason Apple has moved and renamed the 'allow' button in Sequoia.
To allow a DEXT driver with Sequoia navigate to...
System Settings > General > Login Items & Extensions > Driver Extensions
Click on the button to enable the driver.
Hi RP,
thanks for responding
Have enabled extension... Pegasus will not boot
Unistalled ,disconnected Pegasus, repeated complete process, amended as per above - Pegasus will not boot
REPEAT same again, Pegasus will not boot
( reboot M4 after each)
appears to be installed
|
systemextensionsctl list | grep pegasus |
|
* * 268CCUR4WN com.promise.driverkit.pegasus (21.1.0/1) com.promise.driverkit.pegasus [activated enabled] |
/Library/Extensions
Driver running (?)
kextstat | grep stex
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
There is NO pegasus extension in sys info
Hi Chris,
Have enabled extension... Pegasus will not boot
If the Pegasus won't boot the driver is not the issue.
In order to power up the Pegasus32 requires 2 things.
1. It needs to be plugged into the wall socket.
2. It needs a Thunderbolt connection to a powered on computer.
I assume you have both, so the likely suspect is the Thunderbolt cable. If you have another TB3 cable please see if the Pegasus powers up with that cable. If you are using some a different cable than was shipped with the Pegasus, that may be the problem.
The DEXT drivers are not stored in /Library/Extensions to checking there is pointless. They also are not displayed in the System Report yet, so checking there is also of no value. But I don't see why you are checking these places after verifying that the driver is installed and loaded in the first place. This shows that the DEXT driver is installed, activated and enabled.
systemextensionsctl list | grep pegasus
* * 268CCUR4WN com.promise.driverkit.pegasus (21.1.0/1) com.promise.driverkit.pegasus [activated enabled]
Hi RP
1. same socket for the last 6 months...
2. same TB cable for last (year), no idea if it is the cable that shipped with the Pegasus
I generally only use either Apple or CableMatters.
>>The DEXT drivers are not stored in /Library/Extensions to checking there is pointless. They also are not displayed in the System Report yet, so checking there is also of no value. But I don't see why you are checking these places after verifying that the driver is installed and loaded in the first place.>>
Promise Installation Guide:
"How to check if Pegasus DEXT Driver is loaded
After installing the Pegasus DEXT Driver and connecting the Pegasus to your Mac, we can check
whether the Pegasus DEXT Driver is loaded using any of the following methods:
1. Check /Libray/Extensions folder, there will not be PromiseSTEX.kext (6.2.17, user installed) file,
after installing the Pegasus DEXT Driver (.pkg)."
I do note that the Libray/Extensions content
HighPointIOP.kext
HighPointRR.kext
is NOT the same as what the Installation Guide illustrates
HighPointIOP.kext
HighPointRR.kext
SoftRaid.ktext
-- documentation needs to updated there.
"They also are not displayed in the System Report yet"
"yet" Does that mean that Promise hasn't got to writing that entry ( if that is not a OS level auto entry), or that it would list there once the Pegasus had been connected.
If the latter, having now got it to boot, there is no Promise entry in System Report | Extensioins , as the (Ventura) Installation Guide suggests there shouud be
Checked the 240V powerboard connect, unplugged and re-plagged; no boot
added an extension cable, and plugged to a wall socket; boot
reconnected, sans extension cable, to same powerboard; boot
Thanks for the input.
Hi Chris,
I have checked the documentation that comes with the DEXT driver and you are correct in what it says, and the documentation is wrong. I was not aware of this documentation issue. This also explains the many forum posters looking for KEXT driver information to check on the DEXT driver, they were just following the included documentation.
I have reviewed a new document being prepared for Sequoia, and it had the same issues. Now that I am aware, I will try and get these issues in the documentation resolved.
Until then, please use (only) the 'systemextensionsctl list' command to check DEXT driver status, it tells you everything about installed DEXT drivers, nothing more is needed.
And I am assuming that at some point in the future, Apple will add DEXT informartion to the system report, but I have no input from Apple about this.
Hi R P,
ok, thanks for getting back to me (to us all)
