You can use any bootable Linux ISO on a USB to boot the computer, and then modify the EFI for IGPU only configuration. Before you modify the config.plist, you can make a copy in the same EFI folder - this will help you restore easily when your RX580 is back.
@CaseySJ
Possibly related stuff. I used to get disconnections using an apple mouse when dual booting (linux and MacOs). The mouse would pair but would disconnect soon afterwards - I looked through the archwiki for bluetooth and they recommend a method for "Dual boot pairing". You basically set...
IOReg shows that the Thunderbolt controller is properly configured but I guess the Thunderbolt properties would be empty, the PCI section would show the info. Thats one of the draw backs of using only the SSDT. (if I remember correctly, the SSDT only method breaks sleep - the PC does not sleep)...
Thank you. From the pic it looks like you do not have native Thunderbolt support. With the SSDT the Thunderbolt device gets detected as a generic PCI bridge device and the devices get set up, enumerated, and show up on the bridge.
Now this works for most of us - however what is missing is "the...
I can confirm that it is status quo with Z390 itx MB - I have found no way to reconnect the TB device after sleep (tried a lot of combinations). So for now I have given up on sleep :).
I'm interested to see if anyone has managed to solve sleep with TB in an ITX form.
P.S - I use a flashed TB...
You'll get most of your answers reading the Dortania's OpenCore guide with the above config.plist as a reference. You'll realise that you'd need ar least 4 SSDT's to boot the system. Some of these were present as options in the Clover Configurator. (In OC they are present as SSDT's.)...
Are you facing any issues ?
Here's the config.plist. Fill own Values under - "PlatformInfo ?=> Generic"
I use an IGPU only configuration.
Have not activated the Thunderbolt port (ACPI section).
My EFI has a bunch of stuff that I use for testing and hence not sharing because it doesn't apply...
Yeah I have had the BigSur beta working for a while now ( latest on Beta 11.0) and using it as my daily work machine . I am on opencore 0.6.2. The only issues I've had are not related to the OS but related to the software that im using (little snitch, eset, Acronis etc.). I have found it to be...
- Clover or OpenCore should behave the same
- Your platform ID is correct.Post a pic of your Hackintool connecters screen. Goto Hackintool >Patch > Connecters screenshot. Make sure the connecter connected to the HDMI monitor is marked as HDMI.
- Try a cold reboot. Plug out the power - leave...
I have a Dell U2720Q connected via HDMI and a Dell U2417H connected via a DP cable to my ASRock z390 with IGPU only. On boot - both monitors light up and display the OpenCore boot menu. Both monitors display loading the apple boot menu - then halfway through the 27 inch (connected via HDMI) goes...
I suppose you found the issue. For me reads and writes were consistent when the power supply to the motherboard was completely detached (including no Thunderbolt device connected to the TB port). Give it a Few minutes after you disconnect the power supply and Then read.
Yeah same behaviour. I’ve given up for now. Worth a try - I read somewhere that you can try with setting thunderbolt option - sw smi on tbt hotplug to enable. If that doesn’t work try the other one -acpi notify on tbt hotplug. If that doesn’t work set both to enable. In all 3 tests start with a...
At this moment, I think the Thunderbolt SSDT is very unstable. I don't use a GPU, but even with the iGPU - I have had sleep wake issues, monitor disconnects etc. The modified firmware is known to not work with sleep wake. So I guess choices are limited.
The link speed is cosmetic. UUID will change at every reboot. There’s a way to hardcore it but I didn’t see any benefits of doing so. So your setup is all good.
Injecting a UUID did nothing for me. Looking through here - https://www.tonymacx86.com/threads/success-gigabyte-designare-z390-thunderbolt-3-i7-9700k-amd-rx-580.267551/post-2086071
Would you want to try injecting a real "Fixed-9-Byte-Value" in your DROM and then fixing CRC8. CRC32 and see if...
Failed CRC8 is actually a good thing. The Hackintool logs will show you the correct CRC8. Simply replace that in the SSDT DROM and reboot. You will get another error CRC32-C. Same step - use the correct number displayed in Hackintool to replace the current number in SSDT DROM. Look here -...
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.