Search results

You won’t be able to run macOS on your laptop. Not without a patched Kernel. Then you would probably be restricted to some older versions such as Snow Leopard, Lion or Mountain Lion. That is assuming you can get the GMA graphics to work. A long time ago I ran Snow Leopard on a HP server that...

Check which display settings are enabled for the (extended) display when connected to the Mac and then with the display is connected to your AMD Hack. Are they using the same settings in System Settings > Displays tab, specifically are they using the same ‘Colour profile’? If not then try...

Yes, the Intel AX210NGW M.2 card is compatible with macOS, as long as you use the right kexts and application. There are some limitations when using an Intel WiFi/BT card, but aren't there always. For the WiFi module you need to add Itlwm.kext to your /EFI/OC/Kexts folder with a corresponding...

Is this the MSI motherboard you are using? https://www.msi.com/Motherboard/MAG-X870E-TOMAHAWK-WIFI That motherboard has a USB Audio so you shouldn't need any kexts to get it working. The kexts that Apple provide should work with the USB device. That assumes you have created a working...

While that WD drive looks like it should be OK for use as a macOS drive, I would be a little wary as it doesn’t use the same Controller as the other main stream WD drives. They all use ‘Polaris’ controllers, whereas the SN730 uses a ‘20-82-00705-A2 Triton MP28’ controller. The SN730 is...

Uses the Silicon Motion SM2263XT Controller, so while it doesn't use a Phison controller it will not be much better than your current drive. I have a KingSpec NVMe drive in my ASRock X300 system and ended up using it for Windows 11, as it wasn't great as a macOS boot drive. At least it...

Here is a copy of the original UTBMap.kext I created in Windows. These screenshots show the four USB Controllers and the ports active under each. I have also attache two screenshots (Windows SNIPS) showing the naming of the ports as discovered on my system in the Fractal Design R5...

Here are a few screenshots from the bios v3265, which I downgraded to from v3602.

Another recent build I have been playing with over the last month. This time an Asus AM5 build using the following components: Case: Fractal Design R5 (White) MB: Asus ROG STRIX B650E-F Gaming WiFi Intel Ethernet i226-V Realtek USB audio 3 x M.2 NVMe connectors 1 x M.2 WiFi/BT connector...

FYI. The PC601 SKhynix NVMe 256GB (Win 11) drive started causing issues, so I have removed it, plus Windows 11 for now. I will either install Windows 11 on another compatible NVMe drive or a spare SSD, if I feel the need for Windows on this system.

Have you at any point used a Full (17GB+) off-line installer, which you created using the CreateInstallMedia Terminal command?

Sorry to hear that. I am not sure what else to suggest.

I know you have downloaded the installer a few times, but I would still look at the macOS app as being the culprit for your problems. I assume you are using the CreateInstallMedia terminal command to create the installer on a HFS+ formatted USB pen drive, which is 32GB or larger, so it can...

If none of the USB controllers have more than 15 x ports, then yes you can activate all the ports in your system. I have only come across one AMD motherboard that has more than 15 x ports on a single controller (X670E), which had 17 x ports on one of the controllers. So I had to drop 2 x ports...

Tahoe requise a minimalist /EFI/OC/Kexts folder when being installed. As a lot of kexts can cause unnecessary issues if present when installing Tahoe. Your current Kexts folder contents are far from minimal, it should contain only the bare essentials for your system to boot. Lilu.kext...

Looking through your EFI folder attached to post #38 I would commend as follows: 1. You do not need the 3 x sensor kexts listed below, when installing or troubleshooting a macOS installation. AMDRyzenCPUPowerManagement.kext SMCAMDProcessor.kext SMCRadeonSensors.kext You should remove these...

No, I’ve been installing Sequoia on an Intel Z390 system for my son this afternoon & evening. So not had a chance to look as yet.

The kernel panic happened very quickly after the installation started, according to the log you posted. So leaving it overnight wouldn’t make any difference.

I will have a look at the EFI folder to see if anything needs editing later today.

Voodooi2c has added support for AMD systems since recently. Have you tried using the latest version 2.9 or 2.9.1 of the Voodooi2c kexts? https://github.com/VoodooI2C/VoodooI2C/releases