Search results

3840 x 2160 is correct res for 4K not 3400 x 1400, That’s a weird sizing, is it wide or something?

If you can try a DP cable instead and or set the resolution to 2560x1440 instead and turn off force resolution (try it both ways)

If you are using a DP cable try using a hdmi cable instead or vise versa if you have it connected the other way around. Samsung Monitors and TVs are funny old things and for some strange reason default to low resolutions with OpenCore. When I had a 4K HDR Samsung monitor it did exactly the same...

Post your EFI minus your SMBios details and I will amend it for you.

I can see them, I have one of the examples as a spoiler now to take up less space.

OpenCore 0.7.3 EFI Update (Monterey 12.0 Beta 6 Ready), 7th September 2021 The EFI has now been updated to the my latest version. Changes made include, Lilu 1.5.6, AppleALC 1.6.4, WhateverGreen 1.5.3, VirtualSMC 1.2.7, RestrictEvents 1.0.4, LucyRTL8125Ethernet 1.1.0 SMCAMDProcessor 0.7 New...

OpenCore 0.7.3 EFI Update (Monterey 12.0 Beta6 Ready), 7th September 2021 The EFI has now been updated to the my latest version. Changes made include, Lilu 1.5.6, AppleALC 1.6.4, WhateverGreen 1.5.3, VirtualSMC 1.2.7, RestrictEvents 1.0.4, LucyRTL8125Ethernet 1.1.0, SMCAMDProcessor 0.7, New...

@Graystarr I just checked your Config.plist and your using BrcmPatchRAM2.kext when you should be using BrcmPatchRAM3.kext for Big Sur. Try your Config again with the correct kexts added. BrcmPatchRAM3.kext, BrcmFirmwareData.kext & BrcmBluetoothInjector.kext

I’m not sure why it’s not working for him unless it’s just not compatible. @Graystarr i have a GMYLE Bluetooth 4.0 usb dongle sitting here and just plugged it in and that works fine with nothing doing to it. Just checked and you can pick one up from Amazon US for ten dollars. That might be the...

Are you using a Corsair AIO cos that breaks sleep if you are and have the internal USB conected? Forget it, I just noticed your parts list and you’re not.

MSI like to do there ACPI different to the point that Monterey from beta 3 onwards is unbootable with most if not all MSI X570 and B550 motherboards.

Weird, That should be universal across all Ryzen cpus so that is a first for it not to be working. what SSDTs are you using? @Shaneee MSI up to there tricks again…..😂

Did the one I sent you not work? it should do

If your running dual screens it performs much better with WEG disabled, you don’t need any WEG related boot arguments and it just seems smoother as a whole, the only downside is you loose the hdmi output.

@strong0 Here you go bud

Isn’t it 4105?

https://dortania.github.io/Getting-Started-With-ACPI/Universal/plug-methods/manual.html#finding-the-acpi-path

As long as your bios is up to date it’s a straight swap with no changes to your config needed.

SSDT-PLUG-DRTNIA.aml is NOT compatible with a Ryzen, You need to make your own if you want to use SSDT-PLUG fella

Nothing you can do about the double click to wake, It’s been that way since Bug Sur, In the past we used the dark wake boot argument to fix the problem but that method no longer works. as for the sluggish performance after sleep well if you haven’t mapped usb properly then that would cause it or...