Contribute
Register

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

@CaseySJ I updated this post and it’s attachments.
The "boot once" didn't work.

the PCI137a,8 is my motu interface, it says there's no drivers installed, but they are installed. As can be seen in the screenshot. I also allowed the system extension to load in the security and privacy window.

I attached my IOreg and the screenshots below.
This shows that Thunderbolt hot plug is enabled, but the MOTU drivers are not recognizing the device. It's possible that the new drivers require Thunderbolt Bus. We will have to flash the firmware for that, but it incurs some risk of damage and does not guarantee that the drivers will work. It would be the next logical step, but one that should be carefully considered. All of the details are in Section 8 of the Quick Reference spoiler at the top of Post 1. We should use a 3.3V USB CH341a reader/writer (link in Section 8.2.4 of Quick Reference spoiler).

However, I wonder if it's better to revert back to Catalina for the time being.

Is anyone successfully using a Thunderbolt MOTU audio interface with Big Sur?
 
Dear Forum Members,
I have question regarding the Login Screen and Desktop Screen resolution difference.
I am running lates OC and latest mac os (thanks to @CaseySJ and @Inqnuam).

The problem is nothing new. (I have the same problem from the first day of build but, I just started to think addressing that.)

I have an RX 580 graphics card connected to 4K monitor via Display Port.

In Opencore picker I have no problem, it is 4K. But the login screen is Full HD, and when I enter my passwd, it changes to 4K again.

I have enabled the root user and changed the resolution.

Do any of you have any solution ?

Best
This is a bit of a long shot, but try each of the highlighted boot arguments one by one:
  • gfxrst=1
  • gfxrst=4
These are optional arguments for WhateverGreen.

Screen Shot 2021-04-08 at 8.45.58 AM.png
 
This shows that Thunderbolt hot plug is enabled, but the MOTU drivers are not recognizing the device. It's possible that the new drivers require Thunderbolt Bus. We will have to flash the firmware for that, but it incurs some risk of damage and does not guarantee that the drivers will work. It would be the next logical step, but one that should be carefully considered. All of the details are in Section 8 of the Quick Reference spoiler at the top of Post 1. We should use a 3.3V USB CH341a reader/writer (link in Section 8.2.4 of Quick Reference spoiler).

However, I wonder if it's better to revert back to Catalina for the time being.

Is anyone successfully using a Thunderbolt MOTU audio interface with Big Sur?
I wonder if anyone else is already so far, since the drivers were only released yesterday.
Could you elaborate a bit on the risks involved flashing the firmware?
Can it be undone? Or could I also brick it for good?
 
** HackinDROM App 1.2.0 Released **
Now supports both Catalina and Big Sur

Credit: @Inqnuam


The HackinDROM application now supports Catalina as well! (Mojave support is not planned.) Version 1.2.0 will download and install automatically when the previous version is launched. Please wait a few extra seconds for the application icon to appear in the menu bar.

Other improvements:
  • Drivers section now detects disabled drivers correctly
  • Performance optimizations
  • Report Archive now includes System Report file, but without personal data
  • Small graphical changes for better experience
  • Added description for the new -wegnoigpu boot argument
First time users may download the application from the HackinDROM website. HackinDROM Application mini-guide located here.
 
I wonder if anyone else is already so far, since the drivers were only released yesterday.
Could you elaborate a bit on the risks involved flashing the firmware?
While most folks have flashed the controller successfully, there have been a few accidents that have left the board permanently damaged. These accidents all had one thing in common:
  • When attaching or detaching the 8-pin SOIC clip to the Winbond chip, a nearby surface mount device was accidentally dislodged.
  • To avoid this problem, the following guidelines are absolutely and unequivocally critical:
    • You must have excellent near-sightedness.
      • If you wear corrective lenses to see distant objects, remove those lenses and use your natural near-sightedness.
      • If you are far sighted and need corrective lenses to view nearby objects, determine whether you can see objects clearly when they are only 2 inches away from your eyes. If you cannot do this, please enlist the help of someone who can.
    • When attaching and detaching the spring-loaded 8-pin SOIC clip to the Winbond chip, use very steady hands and gentle motions. Position the clip directly over the chip and move it up-and-down over the chip. Never move it side-to-side otherwise nearby components can be hit and dislodged.

Can it be undone? Or could I also brick it for good?
Yes it can certainly be undone. We first extract three copies of the original firmware, compare their checksums and then flash the modified version. We can flash any of the three copies of the original firmware back to the chip at any time.
 
I came from Clover 10.15.7, and, since MOTU finally released their Big Sur drivers yesterday, I decided to start fresh.

BIOS: F9i (unmod'ed)
OC: 0.6.8
OS: 11.2.3
EFI: the latest 068 from @CaseySJ
config.plist: generated using https://hackindrom.zapto.org/

Now the system works fine so far, except for Thunderbolt. Which was working perfectly fine on 10.15.7

I've tried method 1 from this post: https://www.tonymacx86.com/threads/...700k-amd-rx-580.267551/page-1616#post-2086547



Not sure if I missed something here...

Help would be much appreciated.

Cheers
View attachment 514637

View attachment 514636
After installing the drivers you need to give permissions.
Try checking on System Preferences > Security & Privacy > click "Allow".
If you do not find any requests, try uninstalling the Motu drivers, reinstall them and check again on "Security & Privacy".
 
After installing the drivers you need to give permissions.
Try checking on System Preferences > Security & Privacy > click "Allow".
If you do not find any requests, try uninstalling the Motu drivers, reinstall them and check again on "Security & Privacy".
Yeah did that. Didn’t work.
 
My Samsung EVO 970 Plus 500GB SSD boot drive seems to be hemorrhaging available drive space for no reason.
I updated to OpenCore 0.6.8 the other day (otherwise it's been business as usual) and can't seem to find out what is causing the trouble. Has anyone else experienced anything like this? I've lost at least 100GB available to this leak today. I've got a backup but this is scary.

Thoughts?
 
Last edited:
Back
Top