I was looking to migrate from a MacPro 2014 to a Mac Mini M1 for a storage server and currently use the SanLink2 10g sfp+. Is that device known to be compatible with the new M1 machines as of yet?
Support for M1
- 2.9K Views
- Last Post 4 weeks ago
R P
posted this
01 December 2020
Hi Alex,
The new M1 Big Sur will not use intel format drivers, the drivers must be native ARM. The drivers on the downloads page are currently all compiled for intel.
Promise is currently undergoing certification testing for the M1 Pegasus driver.
I do not know the status of M1 Sanlink drivers. But it's likely that they will be out soon after the M1 Pegasus driver is released.
Palle Jensen
posted this
03 December 2020
Speed it up :-)
I just got my mac mini M1 today, and it will not see my 3 Pegasusboxes, and the present utility will not execute.
Palle
- Liked by
-
Thomas Agatz
posted this
08 December 2020
Got the new Macbook Pro M1, but damn I miss my lovely Promise R6 back online, so I can continue my work. Any news about a driver?
Gautham Sakthi
posted this
08 December 2020
Hi Thomas,
Promise is currently undergoing certification testing for the M1 Pegasus driver. The driver should be available by mid to end of December.
- Liked by
-
Pat Govan
posted this
14 December 2020
Is there a timeline for updating firmware for Pegasus drivers that will work with the Mac M1? I hope the firmware update will include the Pegasus2 R4! I'm trying to decide what to do with my Intel Mac and need to make a decision very soon.
Pat
Thomas Agatz
posted this
14 December 2020
Is there a timeline for updating firmware for Pegasus drivers that will work with the Mac M1? I hope the firmware update will include the Pegasus2 R4! I'm trying to decide what to do with my Intel Mac and need to make a decision very soon.
Pat
I seriously can't wait for the driver to be released! Then it'll do what Promise is promising :) :)
R P
posted this
15 December 2020
- Last edited 15 December 2020
Hi All,
I have just discovered that the M1 Pegasus driver (v6.2.16) is now available for download on the Promise support page.
Or you can download it from this link...
Please read the install guide. Big Sur has security features that must be modified.
----
Enable System Extensions
M1 Mac running macOS 11 or later requires a one-time change to the Boot Policy before you install
the Promise Pegasus Driver. Follow the instruction in this section if the Boot Policy setting has not
yet been changed. First check to see if the Boot Policy needs to be changed
Alex Geis
posted this
15 December 2020
Any updates on the Sanlink drivers?
R P
posted this
15 December 2020
Hi Alex,
Sorry, I have raised the issue but have not gotten a response yet. I will ask again tomorrow.
- Liked by
-
Pat Govan
posted this
15 December 2020
- Last edited 15 December 2020
Is there a timeline for updating firmware for Pegasus drivers that will work with the Mac M1? I hope the firmware update will include the Pegasus2 R4! I'm trying to decide what to do with my Intel Mac and need to make a decision very soon.
Pat
I was able to install the Pegasus Driver for the M1 Mac with no problem but I'm not able to connect to the raid nor see the raid with Disk Utility. When I varified the the driver install from System information > Software > Extension > PromiseSTEX, I get the following.
Notarized: Yes
Loaded: No
Get Info String: Version: 6.2.16, Copyright (c) 2010-2021 Promise Technology, Inc.
Obtained from: Identified Developer
Kind: Universal
Architectures: arm64e, x86_64
Does Loaded: No mean that the Driver didn't install?
R P
posted this
15 December 2020
- Last edited 15 December 2020
Hi Pat,
Did you follow all the steps in the included Installation guide?
The STEX driver should work with the Pegasus2, but I'm not sure about the Pegasus2 R2+.
Alex Geis
posted this
15 December 2020
much appriciated!
Hi Alex,
Sorry, I have raised the issue but have not gotten a response yet. I will ask again tomorrow.
Pat Govan
posted this
15 December 2020
Yes, I followed the instructions and the install went well with no error messages.
R P
posted this
15 December 2020
Hi Pat,
Unfortunately, CA has a stay in place order and I can't check this now. I will go to the office tomorrow and test this.
R P
posted this
15 December 2020
Hi Pat,
I wonder if the kext can be manually loaded?
Please open a terminal and enter the following...
sudo kextload /Library/Extensions/PromiseSTEX.kext
Pat Govan
posted this
15 December 2020
- Last edited 15 December 2020
Kextload is dreprecated so I tryed sudo kextunload /Library/Extensions/PromiseSTEX.kext and got back "Executing: /usr/bin/kmutil unload -p /Library/Extensions/PromiseSTEX.kext" . It didn't seem to change anything.
Thomas Agatz
posted this
15 December 2020
Hi R P
YES!!! It's working! I got my old Promise R6 back online on my new MacBook Pro M1 - just followed the guide and installed the driver package. Lovely!
Thank you so much!
R P
posted this
15 December 2020
- Last edited 15 December 2020
Hi Pat,
We don't want to unload the driver, we want to load it. That's the problem, that it's not loaded.
Let's try kmutil then...
sudo /usr/bin/kmutil load -p /Library/Extensions/PromiseSTEX.kext
I knew kextload was deprecated, but it still worked in Catalina. Guess Big Sur is different.
Pat Govan
posted this
15 December 2020
Hi Pat,
We don't want to unload the driver, we want to load it. That's the problem, that it's not loaded.
Let's try kmutil then...
sudo /usr/bin/kmutil load -p /Library/Extensions/PromiseSTEX.kextI knew kextload was deprecated, but it still worked in Catalina. Guess Big Sur is different.
Tried Kmultil and got back,
Error Domain=KMErrorDomain Code=71 "Incompatible architecture: Binary is for x86_64, but needed arch arm64e" UserInfo={NSLocalizedDescription=Incompatible architecture: Binary is for x86_64, but needed arch arm64e}
Palle Jensen
posted this
16 December 2020
Speed it up :-)
I just got my mac mini M1 today, and it will not see my 3 Pegasusboxes, and the present utility will not execute.
Palle
Palle Jensen
posted this
16 December 2020
Got email 2020-12-16, about new M1 drivers, downloaded it and installed on my mac mini M1, running Big Sur 11.1. Works perfect... and the utility too... SUPER
Palle
Pat Govan
posted this
16 December 2020
Kextload is dreprecated so I tryed sudo kextunload /Library/Extensions/PromiseSTEX.kext and got back "Executing: /usr/bin/kmutil unload -p /Library/Extensions/PromiseSTEX.kext" . It didn't seem to change anything.
The Pegasus driver update for the M1 Mac is now working with the Pegasus2 R4. I was able to connect another drive on the second thunderbolt port on the Pegasus2 and the second drive worked as well. Thanks
Chakravarthy Cuddapah
posted this
17 December 2020
M1 MBP ... changed security settings, installed driver .. but after restart, driver didn't load. Followed above instructions and loaded PromiseSTEX.kext manually. But Pegasus R6 is not recognized. Loads on Intel MBP without any issues.
Mush Goose
posted this
20 December 2020
Tried Kmultil and got back,
Error Domain=KMErrorDomain Code=71 "Incompatible architecture: Binary is for x86_64, but needed arch arm64e" UserInfo={NSLocalizedDescription=Incompatible architecture: Binary is for x86_64, but needed arch arm64e}
I also tried to manually load the kext and got the same error. Every time it says:
REMY TEZIER
posted this
4 weeks ago
Hi
I can't connect PEGASUS 32 on my Mac Book pro M2 - OS : VENTURA 13.4
I use Pegasus DEXT Driver 21.1.0
I think it's a probleme with extension :
PromiseSTEX :
Version : 6.2.13
Dernière modification : 13/05/2023 00:29
ID du paquet : com.promise.driver.stex
Authentifié : Inconnu
Chargé : Non
Chaîne des informations : Version: 6.2.13, Copyright (c) 2010-2019 Promise Technology, Inc.
Obtenu de : Non signé
Emplacement : /System/Library/Extensions/PromiseSTEX.kext
Version de kext : 6.2.13
Chargeable : Non
Erreurs de validité :
Validation Failures :
Kext has a CFBundleExecutable property but the executable can't be found : PromiseSTEX
Erreurs de validation de la signature : Non signé
Dépendances : Incomplètes
Signé par : Non signé
Please i need help !
Rémy
REMY TEZIER
posted this
4 weeks ago
R P
posted this
4 weeks ago
- Last edited 4 weeks ago
Hi Remy,
Be advised that you are confusing the DEXT (user space driver) and the KEXT (kernel space driver).
This is the driver in our M1 Mac Mini.
To check for a DEXT:
promise@promises-Mac-mini ~ % systemextensionsctl list | grep pegasus
* * 268CCUR4WN com.promise.driverkit.pegasus (21.1.0/1) com.promise.driverkit.pegasus [activated enabled]
promise@promises-Mac-mini ~ %
This shows that the DEXT driver v21.1.0 is installed, activated and enabled.
If you want to check for the KEXT driver, as you are doing...
promise@promises-Mac-mini ~ % kextstat | grep promise
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
promise@promises-Mac-mini ~ %
No results, there is no KEXT installed. The KEXT driver has STEX in the driver name.
My best guess is that you installed the DEXT driver (although I can't be sure) and did not allow it in Privacy and Security. The installer tells you that you have to allow it and even provides a link to the Settings page where option to allow the driver to run is.
Run the first command to discover the status of the DEXT driver.
