Ploddles

Looking forward to that to see if they will solve my lockup / reboot issue without the deprecated one.

I will wait for them to be released before I make any further changes to my EFI - there is no rush.

7 hours ago, fabiosun said:

 

Patch 20 is not anymore on official AMD OSX patches Github list

and 14 one should be enough also for you.

 

Without patch 20 my system will load and run but randomly either completely locks up or reboots without warning, usually within 5 minutes but 10 minutes at the most. With it enabled it is stable and does not lock up or reboot. Very strange.

I will retest by disabling it and changing my quirks etc to the ones you mention above in [AMD] - Kernel Patches - Riduzione Patches utilizzate (Big Sur e Monterey Beta 1)

6 minutes ago, fabiosun said:

Yes it is that kext

but in different case is not stable for us

Thanks, I have such a bad memory - I blame old age 😀. It has made no difference to the stability of my machine - it is fully stable as long as I have that last patch enabled. I could try again disabling that kext and the last patch and see if it makes a difference.

3 minutes ago, fabiosun said:

@Ploddlesare you using RestrictEvent.kext?

Yes I have that loaded. I started using it a little while back, I can't remember why, and just never disabled it again. Maybe that is what enabled the correct processor name to be displayed?

2 minutes ago, fabiosun said:

By the way

gain is you can use less kernel patches

With or without those quirks etc, my system will not boot without the extra patches as above.

2 hours ago, iGPU said:

 

I have WiFi/BT AIC working, including Airdrop (as I described here) in Monterey ß1.

 

See the Kernel/Add section in the EFI I uploaded for what needs to be on/off and for which macOS. If you are using an AIC for BT, you must inactivate the internal AX200 or you will have a conflict (I've commented on this several times in the past few posts; follow the links).

 

However, if you're using the internal AX200, a different scheme is needed and Airdrop is not presently supported.

Prior to updating to OC 0.7.1 I was using the internal BT/Wifi card with V 1.1.2 of the OpenIntelWireless BT drivers (THESE). They worked fine with a BT headset - I wasn't bothered about AirDrop but it would be nice to have it working, just for completeness. I updated the drivers to the V 2.0.0 RC1 alpha drivers, together with BlueToolFixup for Monterey, but they don't work for me in Monterey or Big Sur. The config.plist file was set up with the correct kexts depending on which version of macOS was booted.

I'll try downgrading to V 1.1.3 and see how they work out for me.

I need 4 extra patches in order to boot either BS or Monterey. Neither will boot at all without 3 of them and without the fourth the system will randomly lock up or reboot - even when doing nothing. They are the last 4 in the plist attached, starting with ???? in the comments section.

@fabiosunif I use the quirks in your link above rather than my own then whilst it does load I can't see what I gain but I loose the full Processor Information as shown in my screenshot above. It goes from "3.7 Ghz AMD Ryzen Threadripper 3970X 32-Core Proce..." to "3.7 Ghz Unknown". This is being read from the BIOS but I can't remember which of the quirks etc I enabled to get it to read and show - it has not been entered manually anywhere. At some point I could change each one and see when it changes but that is for another time when I have plenty of time on my hand to play, it is not a priority for now.

patches.plist.zip

I have updated to OC 0.7.1 and added new patches for Monterey. I seem to need a few more patches than the rest of you to be able to install and boot Monterey, but I still need to try a few more combinations of the patches to minimise the extra ones I am using. I will post my EFI once I have narrowed it down a bit.

Nice to see that the Threadripper Processor is still being automatically identified in System Info, but Bluetooth isn't working as yet.

If it boots back to the previous one then on the reboot during update it picked the wrong part to boot from. 
 

Reboot again and see if there is an extra entry in the picker. If there is then boot that and it will probably complete the update. If there isn’t then try the update again and keep an eye out for the extra picker option and choose that. Remember you only have 4-5 seconds if you leave it to choose itself. It happens occasionally. Just arrow across to another choice to stop the timer. 

New Big Sur 11.5 beta 4 (20G5052c) is out. Let's hope the new Monterey patch list plays nicely with it - I probably won't get a chance to play with either until the weekend.

Just downloaded the patches for Monterey, all 46 of them. It could take a while to go through them all and sanitise them (delete the ones we don't need).

11 hours ago, fabiosun said:

@Ploddles

try to read from here

you are using no one patch 

same behavior of patch 11 we do not know the ‘genesis’😂

Sorry, my mistake, I just looked at the patch number. 😇

7 hours ago, fabiosun said:

Attached are:

 

1) minimal set of patches to boot and work fine with OSX 11.4 release and 11.5.b3 with Opencore

2) minimal set of patches to boot and work fine with OSX 11.4 release and 11.5.b3 with Clover

 

latest patch is for aquantia ethernet, you can disable it if you do not use (Opencore patches plist)

 

Users that use Topology patch, maybe they have to add again this patch

I do not understand well why some users need of it...

 

I have not had your patch 11 enabled in my config.plist for many many months now. Have you tried without it?

Monterey Beta 2 has just landed, lets hope that the patches come out soon.

16 hours ago, iGPU said:

 

Supposedly, BlueToolFixup.kext is only needed for Monterey, and with Monterery you are NOT to use BrcmBluetoothInjector.kext.

 

The image below may help to explain if you carefully note the version restrictions that I've prepared in anticipation of Monterey.

 

Yes, that is what I was doing, getting things ready for Monterey, and I had set the Min & Max Kernel section for all 3 kexts, ie it wasn’t set to load the BluetoolFixup.kext with Big Sur.  However the new IntelBluetoothFirmware.kext was halting the boot with a critical error. Replacing that kext with the old (v 1.1.2) one and I was back to normal. I’ll retry on the next update of these kexts. 

@fabiosun disabling patch 12 boots to a black screen, nothing displayed on the monitor.

Sorry, I did not explain fully. Disabling the patch only stops Big Sur loading but the latest Bluetooth kexts stop Big Sur and Catalina loading. I now have an updated bluetoolfix kexts to try with the new Monterey enabling kexts. 
 

I will try disabling the other patch later as I am now away from home. I will be back in a few hours time. 

2 minutes ago, fabiosun said:

which OS?

11.4?

 

BS 11.4, BS 11.5 Beta and Catalina

4 hours ago, fabiosun said:

Done @Ploddles

could you try to disable patch 13 and see if your system boot fine the same in Big Sur (if you have a backup where you can boot again..just in the worst case) 🙂

 

Unfortunately my system immediately hangs at the Apple logo when I disable the patch.

Anyone using the internal Bluetooth module, on a Gigabyte motherboard, please be aware that the new kexts that are meant to add Monterey compatibility do not work, on my motherboard at least, and cause the system to hang and not boot into macOS. On the plus side I have now fixed the shutdown issue where the system would reboot about 5 seconds after shutdown - it now finally shuts down and stays shut down.😀

@fabiosun I can't remember exactly where it came from but I think it was needed mid way through the Catalina updates, probably about 10.15.3 or 10.15.4. I have enough trouble remembering my own name never mind something like this 🤪

My latest EFI (OC 0.7.0) for the Gigabyte Xtreme can be downloaded from HERE for you to update the OP.

I get the same error using Fusion. It looks like VirtualBox is the only one that works on AMD cpus. 

I only used the single core as an initial install to see if it would work. It is good that we now have another option to run a Windows program without rebooting.

I understand that Fusion Player 12 is free for home use so I will give that a try as well when I get the chance. I didn't realise at first that you can't pass through a graphics card, such as the RX6900XT, using VirtualBox as that option was removed a while back. I presume we still can with Fusion, and Parallels. Let's hope they work as well. The last time I used Fusion was about 6 years ago, and I have never used Parallels, so things will have changed a bit since then.

I've always read on here that you cannot run a Windows Virtual Machine on macOS on our Bare Metal Threadrippers.

As I was on day release from hospital today, I updated my machine to the latest OC release (0.7.0) and the latest BS Beta (11.5 beta 3). Whilst in hospital I had fixed a friends laptop that was continually crashing be wiping it and loading the latest Windows, Win10_21H1. As I had the ISO on a USB drive I decided to try a VM on the Threadripper, thinking it wouldn't work.

My copy of VM Fusion was very old, V6, so I downloaded the latest VirtualBox to play with. I know it isn't the best VM software but it is free.

It was with great surprise then that a Windows VM was up and running in a matter of minutes. No having to try and patch anything or anything else. I have always had SVM enabled in my BIOS setup so I didn't even have to change anything in there either.

So it works. I haven't tried passing through the RX 6900 XT or RX 6800 XT through to it yet, I was just astonished that it worked straight away.

So who is going to be the first to try it?

I'd love to but can't ATM. As soon as I get home I'll give it a play.

BS 11.5 beta 1 has been released.

23 minutes ago, fabiosun said:

 

11.4 is Out 😉

 

At 11.3 stage the RC came out and then further betas were released before the final release. Let's hope this doesn't continue like that one did.