Contribute
Register

[SUCCESS] Gigabyte Designare Z390 (Thunderbolt 3) + i7-9700K + AMD RX 580

Happy New year all,

I bought a new promise pegaus32 R8. It detected as RAID controller PCI via thunderbolt connection, but even after installing the driver it is not mounting or showing the device name in PCI. I have windows in the same machine and it detects the drive without any problem via TB3 though I had to update the thunderbolt driver for windows 10. It connects well via USB in Mac.
My os is Mojave 10.14.6

Thank you
 
Happy New year all,

I bought a new promise pegaus32 R8. It detected as RAID controller PCI via thunderbolt connection, but even after installing the driver it is not mounting or showing the device name in PCI. I have windows in the same machine and it detects the drive without any problem via TB3 though I had to update the thunderbolt driver for windows 10. It connects well via USB in Mac.
My os is Mojave 10.14.6

Thank you
Happy New Year too!

Have you flashed your TB Controller?
 
I have been conducting experiments on flashing my Alpine Ridge AIC v. 2 with several different firmware versions. my practice is to always read 3 times after flashing and confirm that the checksum from the 3 reads is the same as the firmware I just flashed.

before I flash a different firmware I do a read to confirm the clip is attached properly. I have noticed that the checksum on the read after using the card is different from the checksum before using the card. this is repeatable and is irrespective of which firmware I have loaded.

I assume this is benign but what causes this?

thanks
 
I have been conducting experiments on flashing my Alpine Ridge AIC v. 2 with several different firmware versions. my practice is to always read 3 times after flashing and confirm that the checksum from the 3 reads is the same as the firmware I just flashed.

before I flash a different firmware I do a read to confirm the clip is attached properly. I have noticed that the checksum on the read after using the card is different from the checksum before using the card. this is repeatable and is irrespective of which firmware I have loaded.

I assume this is benign but what causes this?

thanks
The flash ROM is 1MB in size and it is split into a number of predefined segments at fixed memory offsets. One of these segments is called “scratch area”. If you were to perform a binary comparison of the extracted firmware before and after, most likely the differences are exclusively in these scratch areas. HexFiend can perform binary comparisons.
 
No, I didn't. Is it necessary to do that? Also, my other tb3 device(Blackmagic Ultra Studio Monitor) works flawlessly.
Thunderbolt NAS drives typically require Thunderbolt Bus to be activated on the Mac, which in turn requires flashing the firmware. However, this can cause issues in Windows. Please refer to section 8 of the Quick Reference Guide for details. Flashing the firmware is risky and not to be taken lightly.
 
Happy New year all,

I bought a new promise pegaus32 R8. It detected as RAID controller PCI via thunderbolt connection, but even after installing the driver it is not mounting or showing the device name in PCI. I have windows in the same machine and it detects the drive without any problem via TB3 though I had to update the thunderbolt driver for windows 10. It connects well via USB in Mac.
My os is Mojave 10.14.6

Thank you
This may sound obvious, but if you want Thunderbolt connectivity for the R8, you need to install the Pegasus drivers for Mojave. After installing and restarting, you will need to "allow" the device in System Preferences.

If the device works just as well (the setup full theoretical bandwidth) with a simple USB connection, I'd just use that unless you need a ton of bandwidth. YMMV...
 

Attachments

  • Allow the driver here.png
    Allow the driver here.png
    75.7 KB · Views: 34
No, I didn't. Is it necessary to do that? Also, my other tb3 device(Blackmagic Ultra Studio Monitor) works flawlessly.
I wouldn't flash the Thunderbolt until you try and verify all software and drivers without it.
 
The flash ROM is 1MB in size and it is split into a number of predefined segments at fixed memory offsets. One of these segments is called “scratch area”. If you were to perform a binary comparison of the extracted firmware before and after, most likely the differences are exclusively in these scratch areas. HexFiend can perform binary comparisons.
thanks for the explanation.
 
Can I ask an off topic opencore question/ Why does the disk name in the Picker GUI not match the Big Sur Disk Utility and finder name? I have been through all the OC docs and don't see a clear reason for this....
 
Back
Top