It doesn’t support AMD integrated Graphics it just works with your system with no 3D acceleration and I bet it’s pretty much unusable and extremely clunky.
MacOS doesn’t support AMD IGPUs and there are no tricks or kexts etc to make it work I’m afraid.
Sorry Buddy :(
For your Bluetooth and wifi you need to add these kexts.
Bluetooth - https://github.com/OpenIntelWireless/IntelBluetoothFirmware/releases/download/v2.0.0/IntelBluetooth.zip
WiFi -...
I just cast my eye over your config.plist and I don't see anything out of the ordinary.
Only thing that might be causing an issue is the SecureBootModel, Try setting it to j137 or Disabled instead of Default but everything else looks fine.
Make sure you are using OC 0.7.2 or newer and Change your SecureBootModel to j160 or j137 restart and try again. While you are downloading the update change the SecureBootModel back to default or disabled so when the system restarts the update wont fail.
7,1 is good, WhateverGreen is not needed with any card that’s supported natively but there’s down sides to not using it like the HDMI or the DP output won’t all always work without the kext. On the flip side WEG is also the number one culprit of breaking DRM. Try without the kext and with the...
That’s not going to fix darkwake Bud. There is no fix for that since the boot arguments for it stopped working when BigSur came out. You're flogging a dead horse trying to fix something that isn’t fixable. Just live with it like everybody else with a Intel or AMD hack does. LoL
Yo can leave it there for now as your testing it’s only a WEG related argument anyway I’m guessing so no effect, if the kext is disabled the boot argument won’t work or remove it if your OCD insists like mine would…lol
You don’t change the cpu name, you set the correct core count and that in turn sets the correct cpu.
Read the first post of this thread on how to set the correct core count for your cpu.
You have little to no chance of getting it working and even if you manage it the OS will be so clunky without any Acceleration that I really wouldn’t advise wasting your own time trying. :(
DP to HDMI converter is your only chance to get it working right I think personally but even that is 50/50 on if it works or not.
Theres nothing different in 0.7.3 that would correct the issue unfortunately.
Oh and by the way ASRock boards are Notorious for chucking out low resolutions in the bios with certain monitors and you can bet on Samsung being one of them…lol
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.
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.