Like I see on your motherboard Asus PRIME Z370-A II extracted DSDT, you don't have any _Lxx specifically for Thunderbolt event. I have same thing on my Asus Maximus board.
You should, like me use _L6F for hot plug and copy native content by adding new line code for our SSDT :
Code:
Method (_L6F, 0, NotSerialized) // _Lxx: Level-Triggered GPE, xx=0x00-0xFF
{
If ((RTD3 == One))
{
If (CondRefOf (\_GPE.AL6F))
{
AL6F ()
}
}
If ((SGGP == One))
{
If (CondRefOf (\_GPE.P0L6))
{
P0L6 ()
}
}
If ((P1GP == One))
{
If (CondRefOf (\_GPE.P1L6))
{
P1L6 ()
}
}
If ((P2GP == One))
{
If (CondRefOf (\_GPE.P2L6))
{
P2L6 ()
}
}
If ((TBTS == One))
{
If (\_SB.ISME (CPGN))
{
\_SB.THDR (TBSE, CPGN)
}
}
}
Code:
Method (_L6F, 0, NotSerialized) // _Lxx: Level-Triggered GPE, xx=0x00-0xFF
{
If ((RTD3 == One))
{
If (CondRefOf (\_GPE.AL6F))
{
AL6F ()
}
}
If ((SGGP == One))
{
If (CondRefOf (\_GPE.P0L6))
{
P0L6 ()
}
}
If ((P1GP == One))
{
If (CondRefOf (\_GPE.P1L6))
{
P1L6 ()
}
}
If ((P2GP == One))
{
If (CondRefOf (\_GPE.P2L6))
{
P2L6 ()
}
}
If ((CF2T == One))
{
\_SB.CAGS (CPGN)
}
\_SB.PCI0.RPxx.UPSB.AMPE ()
}
By renaming RPxx (end of previous code) with your Root Port linked to thunderbolt device AND adding the following lines on top of our SSDT:
Yes. Have you tried playing a video in itunes, or appleTV app?
Or netflix in a browser?
My guess is they wont work, but will if you put shikigva=80 back
I had this activation issue with this software which was purchased, what happens from a cold boot the software sometimes misses its authorisation and says it needs reactivating.......This issue is solved by restarting the computer, Not shutting down , just restart. What could be different about the computer from a cold boot which is then fixed by a restart. Anyone had issues with Presonus Studio One or other software, once the program is running it runs very well.
I am not sure but I may have authorised the Software with a different smbios, then changed it to the current one although I have removed any old authorisations from my account. This is the only software I have seen do this, any input for solution very grateful.
@cheetoh, I had the same issue post upgrade, reattempted from a restored install several times and ultimately couldn't figure it out. I installed Catalina fresh to another 970EVO and other than the pain of getting the system loaded back up audio has worked fine on the clean install.
I am not sure but I may have authorised the Software with a different smbios, then changed it to the current one although I have removed any old authorisations from my account. This is the only software I have seen do this, any input for solution very grateful.
***If you are running Studio One version 3, and you have installed the Fall Creators Update for Windows 10, you will need to upgrade to version 3.5.6 or higher. If you are running Studio One ve...
***If you are running Studio One version 3, and you have installed the Fall Creators Update for Windows 10, you will need to upgrade to version 3.5.6 or higher. If you are running Studio One ve...
I have tried the recommendations for S1 as per your link. I have deleted Presonus OAuth from keychain access unplugged everything from my system and still has same issue. But when I get it a restart seems to resolve the issue
I know this is not really helpful, but I have Studio One, and I do not have this problem.
I wonder if it is an issue with your NIC, SMBIOS or NVRAM?[/URL]
Attempting to update EFI to clover 5103, clover walks through the whole process and then after package validation etc.... if pops up with an installation failed message. Looks like it is dieing right at the point where the new files would be written out. Anyone have any suggestions?
I seen this a few times. It usually happened to me when installing clover on a drive where I would take my current EFI folder and rename it to EFI Backup or EFI.backup etc.
In other words, make sure that you don't have any folders named EFI or EFI anything (like EFI backup) on the destination drive/partition. Name them to something completely different and try it again. Test and see if that helps?
I’m hoping someone can help. I just got my new Z390 DSIGNARE and update the BIOS to F9b. I’m following the Mini Guide and created the Catalina (10.5.3) bootable USB drive and used Clover 5103 (first time) and tried it again (from scratch and a new USB drive) with Clover 5102.
I’m installing to a single 2TB Samsung 930 Pro NVMe drive. I have 64GB of RAM (8GBx4). No other drives attached.
No issues getting to Disk Utility and formatting everything. But when I go to:
macOS Catalina -> Continue
“Agree” and “Agree” to the license agreement
Choose the newly APFS formatted 2TB “Catalina” drive to install and click “Install”
As soon as I click “Install” it goes right back to the “MacOS Utilities” window.
I’ve checked the BIOS settings multiple times (per the original guide for F8 and greater) and as mentioned have created two different (and new) USB 3.0 thumb drives just to make sure something wasn’t wrong with the first.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
