Pegasus 2 R4: Problem loading PromiseSTEX.kext in 24" M1 iMac (Monterey macOS 12.0) version 6.2.17

  • 1.1K Views
  • Last Post 02 November 2021
Peter BANYS posted this 31 October 2021

Terminal Command:  sudo kextload /Library/Extensions/PromiseSTEX.kext
Password:
Executing: /usr/bin/kmutil load -p /Library/Extensions/PromiseSTEX.kext
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}

The system worked fine in Intel i7 iMac & Big Sur macOS. However, in brand new M1 iMac Promise RAID-5 is bolloxed. The individual drives are formatted in APFS.

1.  RAID-5 appears as text on desktop, but icon is grayed out.

2.  Time Machine will not work with it.

Order By: Standard | Latest | Votes
R P posted this 02 November 2021

Hi Peter,

I just tested the 6.2.17 driver on an M1 with Monterey and it works fine. You have to follow the instructions in the package and allow the driver to run in settings -> security, then everything works.

Please reload the 6.2.17 driver filename  R_MacDrv_V6_2_17.zip.

R P posted this 02 November 2021

Hi Peter,

Can you run the following command?

promise@Promise Contents % grep Version /Library/Extensions/PromiseSTEX.kext/Contents/Info.plist
        <string>Version: 6.2.17, Copyright (c) 2010-2021 Promise Technology, Inc.</string>

R P posted this 01 November 2021

Hi Peter,

The drivers should be unified binaries...

This is from a Big Sur Mac Pro.

promise-technology@Promises-Pro Extensions % file PromiseSTEX.kext/Contents/MacOS/PromiseSTEX
PromiseSTEX.kext/Contents/MacOS/PromiseSTEX: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [arm64e:Mach-O 64-bit kext bundle arm64e]
PromiseSTEX.kext/Contents/MacOS/PromiseSTEX (for architecture x86_64):  Mach-O 64-bit kext bundle x86_64
PromiseSTEX.kext/Contents/MacOS/PromiseSTEX (for architecture arm64e):  Mach-O 64-bit kext bundle arm64e
promise-technology@Promises-Pro Extensions % kextstat | grep -i stex
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
   67    0 0xffffff8003336000 0xb000     0xb000     com.promise.driver.stex (6.2.13) AE253556-66D8-38D2-B9D1-179B78F29153 <66 14 6 5 3>
promise-technology@Promises-Pro Extensions %

This is 6.2.13.

My Big Sur M1 Mac Mini with 6.2.17...

promise@Promise ~ % file  /Library/Extensions/PromiseSTEX.kext/Contents/MacOS/PromiseSTEX
/Library/Extensions/PromiseSTEX.kext/Contents/MacOS/PromiseSTEX: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit kext bundle x86_64] [arm64e:Mach-O 64-bit kext bundle arm64e]
/Library/Extensions/PromiseSTEX.kext/Contents/MacOS/PromiseSTEX (for architecture x86_64):      Mach-O 64-bit kext bundle x86_64
/Library/Extensions/PromiseSTEX.kext/Contents/MacOS/PromiseSTEX (for architecture arm64e):      Mach-O 64-bit kext bundle arm64e
promise@Promise ~ %
promise@Promise ~ % kextstat | grep -i promise
Executing: /usr/bin/kmutil showloaded
No variant specified, falling back to release
  224    0 0xfffffe0006e90000 0x4000     0x4000     com.promise.driver.stex (6.2.17) 69FB7EB9-DAAD-33B7-B348-8149A47F4B64 <223 61 5 4 3>
promise@Promise ~ %

So 6.2.17 is a unified binary,

I will escalate the issue with Monterey.

Search
Categories
Close