Promise Utility / Pegasus2 and macOS High Sierra release working? Connected to it, a Pegasus R6, Pegasus2 R4, and Pegasus2 M4. Magellan roadmate 9055 lm manual Manualidades con tubos de papel higienico buhok Omron nt21 st 121 e-manual software Invacare lift battery charger. Pegasus2 Series Driver for Mac English (2017/05/10) More. Pegasus3 Series Utility for Mac. Pegasus2 R4/R6/R8/M4 Firmware English (2017/05/11).
The current kernel extension 6.2.9 does indeed work with macOS High Sierra 10.13 (17A365) 2. The Promise Utility Version 4.00.0000.09 (C02) also works with macOS High Sierra 10.13 (17A365) 3. Keep in mind that beta developer versions change with each beta release and we test all of them including the GM (Golden Master). Once the official build has been released to the public, we execute rigorous testing cycles to ensure that our hardware and applications are fully qualified. Expecting release/compatibility notes the day of the official release is highly unlikely as we need time to fully qualify the official release. That being said, nothing is broken with the latest release of the kernel extension and the Promise Utility.
We will release a new compatibility list illustrating that 10.13 is supported. MacOS Host running 10.13 (17A365): swvers ProductName: Mac OS X ProductVersion: 10.13 BuildVersion: 17A365 B. Kernel Extension Loaded on 10.13 (17A365): kextstat grep -i promise 80 0 0xffffff7f80b09000 0xd000 0xd000 com.promise.driver.stex (6.2.9) A98F7D05-34D3-3B2B-9EE4-C5AC7494B2A8 C. Promise Utility Version: mdls -name kMDItemVersion /Applications/Promise Utility.app/ kMDItemVersion = '4.00.0000.09 D. Thunderbolt Bus working properly (This machine has TB1): systemprofiler SPThunderboltDataType Thunderbolt: Thunderbolt Bus: Pegasus2-R: Vendor Name: Promise Technology, Inc. Device Name: Pegasus2-R Vendor ID: 0x2 Device ID: 0x9 Device Revision: 0x3 UID: 0x1B7FD0 Route String: 1 Firmware Version: 19.2 Port (Upstream): Status: Device connected Link Status: 0x2 Speed: Up to 10 Gb/s x2 Current Link Width: 0x1 Cable Firmware Version: 1.0.16 Cable Serial Number: C4M337401S1F798AT Link Controller Firmware Version: 0.13.0 Port: Status: No device connected Link Status: 0x7 Speed: Up to 10 Gb/s x2 Current Link Width: 0x1 Link Controller Firmware Version: 0.13.0 E.
SAS Info Excerpt: systemprofiler SPSASDataType SAS: SAS Domain 0: Initiator Identifier: SCSI Target Device @ 0: SAS Address: 22:C0:00:01:55:33:45:C6 SCSI Target Identifier: 0 SCSI Peripheral Device Type: 0 Manufacturer: Promise Model: Pegasus2 R8 Revision: 504 F. Kernel Logs illustrating Promise Kernel Extension initialization/sequences: 2017-09-27 15:23-0400 localhost kernel0: (PromiseSTEX) STEX: PromiseSTEX loaded up. 2017-09-27 15:69-0400 localhost kernel0: (PromiseSTEX) STEX: PromiseSTEX loaded up.
Db: 5.65:pegasus2 R4 Driver For Mac Free
Hello, I recently received my Mac Pro Late 2013; I had planned on using a Promise Pegasus2 R4; with Windows and OS X; in order to supplement the SSD storage. Everything went fine with OS X. However after I got Windows 8 installed. The Promise box didn't work because a driver for it wasn't installed. It was listed under the 'Other Devices' section of the Device Manager as a RAID Controller. The process I am about to outline worked for me and so I thought I'd share.
I eventually got the promise to work in Windows 8.1 x64 by using this driver as a base: This driver uses the same controller chip and the same amount of RAM as the Pegasus2. After downloading you will need to edit the following file: Open 'stexstpt' in a text editor. Look for the Promise.ntamd64 section of the file and add the following line below the header.%stexYosemiteDesc%=stexInst,PCI VEN105A&DEV8760 Save changes to the file. In light of the fact that we modified the driver.
We must tell Windows to accept unsigned drivers; (The drivers secure has no longer matches do to the fact that we modified the driver). To enable the installation of unsigned drivers follow the directions which are outlined here: After this process has been completed open the device manager and right click the RAID controller in the 'Other Devices' section.
R4 Driver Download
Select 'Update driver Software' Select 'Browse my computer for driver software' Select 'Browse' button and navigate to the folder which contains the driver. Select 'Next' The driver will now be installed. The RAID Controller device will now be referred to as a 'Promise Supertrak SAS 6G RAID Controller' and two additional 'Promise RAID console' devices will be added as well. They will all be listed in the 'Storage controllers' section of the Device Manager. Any any drives that you previously created within the Promise Utility and / or Disk Utility (From within OS X) will now be accessible from within Windows and con be covered over to NTFS at will.
This should satisfy anyone with similar needs until Promise releases a proper driver. This has worked well for me so far and performance has been very good within both OSes; however if it causes adverse effects to your hardware or data; you shall assume all the risk. With that being said I hope this process helps someone.
Hello, I recently received my Mac Pro Late 2013; I had planned on using a Promise Pegasus2 R4; with Windows and OS X; in order to supplement the SSD storage. Everything went fine with OS X. However after I got Windows 8 installed. The Promise box didn't work because a driver for it wasn't installed. It was listed under the 'Other Devices' section of the Device Manager as a RAID Controller. The process I am about to outline worked for me and so I thought I'd share.
I eventually got the promise to work in Windows 8.1 x64 by using this driver as a base: This driver uses the same controller chip and the same amount of RAM as the Pegasus2. After downloading you will need to edit the following file: Open 'stexstpt' in a text editor. Look for the Promise.ntamd64 section of the file and add the following line below the header.%stexYosemiteDesc%=stexInst,PCI VEN105A&DEV8760 Save changes to the file.
In light of the fact that we modified the driver. We must tell Windows to accept unsigned drivers; (The drivers secure has no longer matches do to the fact that we modified the driver). To enable the installation of unsigned drivers follow the directions which are outlined here: After this process has been completed open the device manager and right click the RAID controller in the 'Other Devices' section. Select 'Update driver Software' Select 'Browse my computer for driver software' Select 'Browse' button and navigate to the folder which contains the driver. Select 'Next' The driver will now be installed. The RAID Controller device will now be referred to as a 'Promise Supertrak SAS 6G RAID Controller' and two additional 'Promise RAID console' devices will be added as well. They will all be listed in the 'Storage controllers' section of the Device Manager.
Any any drives that you previously created within the Promise Utility and / or Disk Utility (From within OS X) will now be accessible from within Windows and con be covered over to NTFS at will. This should satisfy anyone with similar needs until Promise releases a proper driver. This has worked well for me so far and performance has been very good within both OSes; however if it causes adverse effects to your hardware or data; you shall assume all the risk.
With that being said I hope this process helps someone. Click to expand.I have a few questions about your Pegasus R4 if you don't mind. Did you buy the diskless R4?
If so what drives did you buy? Any issues with the selected drives? I chatted to a Pegasus rep and asked them if they supported Windows and I got a vague response. If you use bootcamp then probably. He seemed unsure. Did you use Bootcamp to load windows or another method?
Do you think Pegasus will eventually provide an updated driver? Thanks for your post. I have previously asked in other Pegasus threads if anyone had installed Windows and yours is the first positive response. Re: To Answer Your questions: 1) Yes I bought the diskless version at store.apple.com I bought the drives shown here: Not listed as compatible, however they seem to work, just fine. 2) Yes I used bootcamp to install windows. Nothing special about the windows install. I believe that promise will eventually provide a proper driver; most of their other products have one after all.
Further Thunderbolt is becoming more and more common on windows workstations from HP and Dell. Let me know if you have any other questions. To Answer Your questions: 1) Yes I bought the diskless version at store.apple.com I bought the drives shown here: Not listed as compatible, however they seem to work, just fine. 2) Yes I used bootcamp to install windows.
Nothing special about the windows install. I believe that promise will eventually provide a proper driver; most of their other products have one after all. Further Thunderbolt is becoming more and more common on windows workstations from HP and Dell.
Let me know if you have any other questions. Click to expand.I am not booting windows via a drive in the pegasus, I current just have an ntfs data drive in the pegasus and I access it while booted from within windows from the internal SSD. However with that being said I am confident that you could boot windows from the pegasus if you took the following steps: 1) Install windows as normal. 2) Install driver noted above (or the 'proper' one in the future) 3) Reboot into OS X and use Winclone to create an image of your windows partition.
4) Restore the win clone image to the Pegasus. 5) Delete windows from internal SSD. 6) Boot windows from the pegasus as normal. This works because Thunderbolt is a much lower level interface and is not reinitialized during the boot process of the windows kernel.
I have read in numerous places that this works; however I have little interest in trying it. I do however recommend that you backup your Windows partition with Winclone; this is always a good idea. I am not booting windows via a drive in the pegasus, I current just have an ntfs data drive in the pegasus and I access it while booted from within windows from the internal SSD. However with that being said I am confident that you could boot windows from the pegasus if you took the following steps: 1) Install windows as normal. 2) Install driver noted above (or the 'proper' one in the future) 3) Reboot into OS X and use Winclone to create an image of your windows partition. 4) Restore the win clone image to the Pegasus.
5) Delete windows from internal SSD. 6) Boot windows from the pegasus as normal. This works because Thunderbolt is a much lower level interface and is not reinitialized during the boot process of the windows kernel. I have read in numerous places that this works; however I have little interest in trying it. I do however recommend that you backup your Windows partition with Winclone; this is always a good idea.
I am not booting windows via a drive in the pegasus, I current just have an ntfs data drive in the pegasus and I access it while booted from within windows from the internal SSD. However with that being said I am confident that you could boot windows from the pegasus if you took the following steps: 1) Install windows as normal. 2) Install driver noted above (or the 'proper' one in the future) 3) Reboot into OS X and use Winclone to create an image of your windows partition. 4) Restore the win clone image to the Pegasus. 5) Delete windows from internal SSD. 6) Boot windows from the pegasus as normal. This works because Thunderbolt is a much lower level interface and is not reinitialized during the boot process of the windows kernel.
I have read in numerous places that this works; however I have little interest in trying it. I do however recommend that you backup your Windows partition with Winclone; this is always a good idea. Click to expand.Hi. Just a note that this doesn't work.
I've tried everything I could think of, and I'm yet to be able to boot windows using a disk in the R4 (be it jbod, raid or passthrough). My last attempt was extracting the drivers so windows installer could use them, and directly booting the windows 8.1 installation disk. I then loaded the drivers so I could select the Pegasus disk as installation. From that point on, windows 8.1 installer states that you can't install windows on that disk because the bios can't boot it and it should be activated in the bios. Very unhappy so far.
Several hours spent without much luck I had really hoped I could boot windows from the pegasus2.