Pegasus2 R4 Mac Pro Big Sur 11.2.2

  • 227 Views
  • Last Post 25 March 2021
Eric Friday posted this 04 March 2021

None of the steps I've read about bringing up my Pegasus2 R4 have worked on this Mac Pro running Big Sur 11.2.2. Each time it crashes and reboots the OS when I turn on the drive array. 

Setting up the Secure boot sequence prior to installing the 6.2.16 driver to have access/permissions or changing the csrutil to disable for the boot sequence mentioned recently have not worked. Only once, the first time, did I see the message in Security and Privacy, and when I did, I enabled it. I also tried the terminal command to load it but only the prior version loads and still causes tjhe crash/reboot. The instructions in the downloaded PDF with the driver is inaccurate. There is no Reduced Security Option in the Startup Security Utility nor any mention of kernel extensions.

Software Extensions does list it, along with the previous version (6.2.13) but 6.12.16 never loads.

Any help would be great. This is a terrible situation. 

Thanks

 

Order By: Standard | Latest | Votes
R P posted this 25 March 2021

I'm not sure where the notion that the 6.2.16 was necessary to work on the Intel mac but that is not the case.

Intel macOS Big Sur has an inbox Pegasus driver, which is 6.2.13.

M1 macOS Big Sur does not have an inbox Pegasus driver and 6.2.16 (which supports M1) will have to be installed.

There may be some confision about this.

Eric Friday posted this 23 March 2021

At some point I was sure the asmedia.com.tw.AsmScsiPT was a driver in /System/Library/Extensions but it turned out that it was in /Library/Extensions.

A simple drag to the trash fixed the problem and with the 6.2.13 Promise driver installed for a MacPro Intel 2019 the PegasusR2 worked. I'm not sure where the notion that the 6.2.16 was necessary to work on the Intel mac but that is not the case.

 

R P posted this 18 March 2021

Thanks.That extension exists but is not loaded.

It can't cause a panic when it's not loaded. The panic is caused by the asmedia.com.tw.AsmScsiPT driver.

Based on a suggestion by Promise I ran sudo rm -r /Library/Extensions/PromiseSTEX.kext

As previousluy mentioned, you can't simply delete even a 3rd party driver in Big Sur.

I found this procedure, it's for Catalina but it might work.

I found that this extension is 6.2.13 which won't work on BigSur

Yes, the driver does work, it's the Big Sur inbox STEX driver. It's slightly downrev, but I've been using that driver in Big Sur for months with all manner of Pegasuses with no problems.  

Are my steps to turn off SIP by entering recovery mode and running csrutils disable? What command should I then use to remove the 6.2.13 kext and install the new 6.2.16 one.

I think the Catalina process is worth a try, but the 6.2.13 driver is still in the boot ramdisk and I think it will reapear after a reboot. I have not yet found a process specifically for Big Sur. In Cartalina you can delete a driver with the 'sudo rm -rf' command, Big Sur won't let you do that. Big Sur handles drivers differently, the Catalina process might not work.

Eric Friday posted this 18 March 2021

Thanks.That extension exists but is not loaded. It's also appears to be an extension from Apple as it exists in /System/Library/Extensions.

Based on a suggestion by Promise I ran sudo rm -r /Library/Extensions/PromiseSTEX.kext

That failed to remove the extension. I found that this extension is 6.2.13 which won't work on BigSur is also in the /System folder and the reason it cannot be removed:

~ % kmutil inspect | grep Promise
No variant specified, falling back to release
com.promise.driver.stex 6.2.13  /System/Library/Extensions/PromiseSTEX.kext 

Are my steps to turn off SIP by entering recovery mode and running csrutils disable? What command should I then use to remove the 6.2.13 kext and install the new 6.2.16 one. 

Thanks

R P posted this 18 March 2021

Hi Eric,

The stack trace says that this panic was caused by the asmedia.com.tw.AsmScsiPT driver calling the macOS iokit.

      Kernel Extensions in backtrace:
         asmedia.com.tw.AsmScsiPT(0.0)[DA0A5CBC-74D5-37F5-9B36-51829A86E246]@0xffffff7fb112a000->0xffffff7fb112bfff
            dependency: com.apple.iokit.IOSCSIArchitectureModelFamily(436.40.6)[E5CB0567-FBD1-39AE-8847-C559B51918B1]@0xffffff8011a5a000->0xffffff8011a6dfff
            dependency: com.apple.iokit.IOSCSIBlockCommandsDevice(436.40.6)[17662AB7-6B15-3342-9F23-AB161202B652]@0xffffff8011a7f000->0xffffff8011a8cfff
            dependency: com.apple.iokit.IOStorageFamily(2.1)[B5300908-BF34-3D47-8776-FB154A6DEE4C]@0xffffff8011b3f000->0xffffff8011b50fff

 

Unfortunatly, Big Sur won't let you just delete a driver as you can with Catalina and below, you'll need an uninstaller, many driver packages will also uninstall drivers, but not all will.

 

 

Eric Friday posted this 18 March 2021

I submited the MacReport two weeks ago and haven't heard back. When I logged in from an email saying there was a response, though that may have been a result of your first post in reply 2 weeks ago, there is no supporting claim matching the tech support case .

I finally realized that my Brave browser was blocking pop-ups without notifying me. When I changed to Chrome I got the response from tech support. I'll try the step he suggestedm and will report back after I can reboot and try again.

Eric Friday posted this 08 March 2021

No luck with the reset of nvram and SMC. I'm pretty sure those steps succeeded.

Installing the driver again however I never saw the pop up about allowing access from Security and Privacy. And even though the install took some time to complete. 

I submitted a Crash Report on the Promise Support site.

The 6.2.13 driver which is installed in /System/Library/Extensions always takes over, even if both drivers are not loaded and I run the kextload /Library/Extensions/PromiseSTEX.kext command only the earlier driver loads. I tried changing the name of the driver in the /System folder but even with sudo it is not allowed.

Ranjith kumar posted this 08 March 2021

Hi Eric,

Could check with reset of nvram and smc setting in your Mac, then install the 

latest driver 6.2.16 which need to be load. If you still have an issue, kindly reach us

through support.promise.com with Mac report.

thank you,

Regards,

Promise Team

Close