- Joined
- Aug 7, 2022
- Messages
- 843
Sounds good. Just got back from lunch.@CaseySJ The 2 byte patch doesn't work for an MSI user, but the 4 byte one which you tested works fine, I guess we'll merge that one. Waiting for one more MSI tester.
EDIT: Another user got it working... You should try it too.
It works!!@CaseySJ The 2 byte patch doesn't work for an MSI user, but the 4 byte one which you tested works fine, I guess we'll merge that one. Waiting for one more MSI tester.
EDIT: Another user got it working... You should try it too.
@CaseySJ The 2 byte patch doesn't work for an MSI user, but the 4 byte one which you tested works fine, I guess we'll merge that one. Waiting for one more MSI tester.
EDIT: Another user got it working... You should try it too.
Not exactly... The actual minimal Method 3 patch has been added to the bottom of this post:
Please note that we should use either the boot argument or the kernel patches, but not both. The latest kernel patch is Method 3 (see my post directly above).I have used the patch and the boot arg to boot Ventura. I installed Ventura on an M.2 NVME drive using an intel iMac, then copying my EFI on to the EFI partition. My Asus Strip X670E-F with the Rysen 7950 boots into Ventura, I log in, then after about two minutes, it freezes. I repeated the process using a 2.5 inch SATA SSD and it is rock stable. I an unsure if this is related to the PCI issue or not. I was running Big Sur on a M.2 NVME drive and it was also very stable. Any advice out there?
If you’re using Monterey then yes, just try adding the boot argument e1000=0 and remove or disable all device properties for i225-V.
Not necessary because the boot argument is independent of OpenCore.I'm using Monterey. Do I need OC 0.85?
I'm glad to see the exciting work. Does it mean that the problem on MSI's motherboard on am4 has been solved?
New kext patch should work for newer macOS versions. It's preferred because Zen 4 and MSI only have problems with the 10 bit tags, but the boot arg also disables the 8 bit tags which don't have to be disabled.@ExtremeXT why a patches is advisable against the use of a bootarg 1revenger found in the kext code?
I mean is not more solid a bootarg if kext you patch change with an os upgrade?
Only to understand well
Thank you
Yes please do.@CaseySJ Should I send the PR with the 4 byte patch to the repo?
Are you referring to boot argument pci=0x8000000? We discovered it here:@ExtremeXT why a patches is advisable against the use of a bootarg 1revenger found in the kext code?
I mean is not more solid a bootarg if kext you patch change with an os upgrade?
Only to understand well
Thank you