Search results

If you search online you will find the developer's repository with historical versions available as well as the latest. For this kind of testing it would be easier to simply change the kext in the kexts folder and reboot to test, rather than running MultiBeast each time.

You would have to buy old, se ond-hand hardware. No hackintosh build is "seemless" . That's just the nature of the beast. Best idea would be to look through some of our older Golden Builds.

Okay... We can see that the three screengrabs of the USB ports are all different. I suspect the one in post #235 looks the most likely to be correct. :thumbup: Remember that macOS has no knowledge of AMD USB controllers. We can see the Renoir ones but there is also an ASMedia hub included too...

Okay, you would need to install the OSs onto separate 2.5" SATA SSDs instead. That way you can disable one or the other in BIOS when necessary. But if you are not going to install macOS then maybe we aren't the experts you need? :)

Well the easiest option is to keep Windows and macOS on separate SSDs and use the BIOS boot-drive picker to choose which OS to boot into. Have you read @Going Bald 's excellent guides to multi-booting here? https://www.tonymacx86.com/threads/guide-multibooting-uefi.197352/ :)

Hi there. That's a clever idea as OpenCore bootloader should patch the DSDT on the fly during boot. However, the trouble might be that Windows spots the new hardware, not in the BIOS now, and adds it's own drivers to attach it. Much like it does if you add any hardware that didn't come with...

Good point @Edhawk. I'd forgotten about those. :thumbup: I checked them out with my own MediaTek problem and sadly they weren't the model needed. Worth checking again though.

Ah. Yes indeed, the MediaTek wireless chipset has no macOS drivers. My own recent B760 build featured one of those - and it had been renamed as an AMD RZ** chipset. As yours is an AMD chipset motherboard this doesn't surprise me, sadly. As for IOReg output, PO13 certainly looks like the...

Use the IORegistryExplorer app and scroll the left column down to find the USB section, usually about 2/3 the way down. Open the tree and find the sub-tree labelled Wireless_Device on PO13. There should be more detail, including any Bluetooth info when the USB port is active. :)

But is not USB's necessity to enable bluetooth, on topic? I am only advising after what I've seen in his uploaded EFI. I'll butt-out ... :banghead:

No, I'm saying that will be your Bluetooth header. As mentioned above you can double-check with the IORegistryExplorer.app as it allows you to step down lower in the tree. Further in on the IOUSBHostDevice sub-tree you should find the Bluetooth. :thumbup:

Craig, just realised what you are saying to me ... Do you get all those 23x ports without USBInjectAll.kext and without the XhciPortLimit quirk set?

Brilliant, Thanks. :thumbup: So port P09 looks the likely candidate then?

The easiest way to start, as you have an AMD-based board, is to load the USBInjectAll.kext along with the XhciPortLimit Quirk active. Reboot then open the Hackintool app at the USB tab, to survey your USB kingdom. This should show you at least the first 15x ports. Look for one with...

Use whichever guide you feel happy with. My own is fine That works with small PCs with a limited number of ports. No problem. BUT from what I can see on the MSI site, this motherboard has 20x possible ports.

Hey guys, have you missed what I said in post #12 above? No amount of jiggy-jiggling will work unless you do that. (Refresh the page).

Thank you for posting your EFI here. That's the way. Your problem is you have not configured the USB ports for your system. Specifically you need to ensure the internal USB port BT uses is active. :)

Ha!! Good afternoon! :D

Hello there. First things first. No need to post links off-site. Just ZIP and "Attach Files" your EFI folder to a post. (Otherwise your posts may get deleted) :thumbup: Okay then. AX200 Intel wireless and Bluetooth *will* work fine with Sonoma as long as you use the correct files and...

Clever and well-reasoned use-case for an old OS X system. Well done! :thumbup: