[SOLVED] Issue with miniforums UM700

mixmac

New member
AMD OS X Member
Jul 27, 2024
13
2
3
France
CPU:
AMD Ryzen™ 7 7800X3D
Hello everyone,
I made my ryzentosh which everything is recognized except my GPU AMD Radeon RX Vega 10 (Picasso).
Capture d’écran 2024-08-05 à 17.19.00.png
I tried to add it in the boot argument:
Code:
-v swd_panic=1 keepsyms=1 debug=0x100 npci=0x3000 gfxrst=3 alcid=3 -wreddbg agdpmod=pikera -radcodec applblk=3
but without success.Is it possible to have a hand?
My setup is in my signature, I attach my EFI.
 

Attachments

Discrete GPU's in the Vega 10 Series - Vega 56/64 & Radeon Pro WX 9100, are all supported in Current macOS Sonoma and Sequoia Beta.

The CPU in this mini PC uses an AMD IGPU with a very similar name to the discrete GPU's in the Vega 10 Series, i.e. Radeon RX Vega 10 Graphics.

This APU/IGPU will require the addition of NootedRed.kext to the /EFI/OC/Kexts folder and config.plist, for the APU to provide full graphics acceleration in macOS (Sonoma or older).


When using NootedRed.kext you can't have any devices entered in the DeviceProperties > Add section of your config.plist. If you do have any entries these are likely to cause the system to kernel panic.

Screenshot 2024-08-05 194618.png These DeviceProperties need to be deleted from config.plist.
PowerPlay entries are not needed for your APU.

I would delete WhateverGreen.kext and WhateverRed.kext from the /EFI/OC/Kexts folder and the config.plist, as these will clash with NootedRed.kext.

I would also remove/delete the following kexts, as they are not required for your Mini PC.
  1. LiluWORK.kext
  2. AppleIGC.kext
  3. AtherosE2200Ethernet.kext
  4. RealtekRTL8111.kext
  5. SMCDellSensors.kext
Personally, I would also remove these kexts, as they commonly cause issues for AMD systems running macOS while using the APU.
  1. AMDRyzenCPUPowerManagement.kext
  2. SMCAMDProcessor.kext
You might want to look and see if your Mini PC uses a USB Audio codec, if it does you should replace AppleALC.kext with the USB version, i.e. AppleALCU.kext. This has been the case with most recent Mini PC systems.

As you don't have a custom USBMap.kext or UTBMap.kext & USBToolBox.kext in your setup I would recommend you enable the Kernel > Quirks > XhciPortLimit entry, so your USB ports work while you trouble shoot your system.

Screenshot 2024-08-05 195230.png Kernel > Quirks > XhciPortLimit entry set as True/Yes, viewed in ProperTree Plist editor.

I am not sure why you are using the SMBIOS for an iMacPro1,1. As this system lacks an IGPU and only has a discrete GPU in a real Apple system. You would be better served using an iMac SMBIOS with your Mini PC. I used iMac20,1 with mine.

You have the wrong entries for UEFI > APFS > MinDate & MinVersion config options. These should both be -1 or 0 if you are running any version of macOS newer than Catalina.

Screenshot 2024-08-05 200542.png MinDate is fine but MinVersion is wrong.

Setting both to 0 would be my choice.

You have HfsPlus.efi and OpenHfsPlus.efi in your Drivers folder & config. This is wrong. Remove the OpenHfsPlus driver, as HfsPlus is a better driver.

The only component in this Mini PC that might cause an issue when running macOS is the Kingston M.2 NVME drive. But only if it is used as the macOS Boot Drive, it is fine if used for Windows or Linux. I say this as the Kingston NVMe controller on this drive isn't fully compatible with macOS. I have one from the same series and it just kept throwing up issues. It is best to use Western Digital M.2 NVME drives, such as the SN570 or SN770. No point using the faster SN850 or SN850X drives as you wouldn't get any benefit from the faster drives and they are likely to be more expensive than the older SN570 & SN770 drives.
 
  • Like
Reactions: Shaneee and mixmac
Good evening,
Thank you very much for your help Edhawk, I also saw on the net that Vega 10 could be used with Sonoma and the sequoia betas.
I cleaned my config.plist as you advised me as well as the Kexts.I attach the updated EFI.
However I have a kernel panic at boot after emptying the nvram.
IMG_2598.jpeg
 

Attachments

There is a problem with the NootedRed.kext in your config.plist that is causing a kernel panic.

You need to use a different version of the kext to get around this issue. See the kext attached, it is from my GenMachine MiniPC and it works in Sonoma.
 

Attachments

Here is a copy of the NootedRed.kext from my current GenMachine EFI, running Sonoma 14.6.

This kext might work better than the other I provided.
 

Attachments

I replaced the Kext with the one attached above then cleaned the Nvram.
At boot the verbose mode scrolls at full speed then the mini PC reboots at the same stage.
Do not need other boot arguments?
Thanks for your help.
 
Where do you find the other versions of NooteRed.kext?
I added my SSDTTime path to config.plist.
I tested this EFI with WhateverGreen.kext and my hackintosh boot without graphics acceleration of course.
So it is indeed NooteRed that crashes the boot.
 

Attachments

You can find the Github repository for NootedRed below.


There is more information about the kext in the link below.

 
Ok after reading the NooteRed prerequisites, I had not disabled CSM (Legacy Boot)
IMG_2611.jpg
and I removed the boot arguments which now become:
Code:
-v debug=0x100 keepsyms=1 alcid=7 npci=0x2000
I rebooted and emptied the nvram but the boot stops at this level (see photos).
IMG_2612.jpg
I really don't see what else to do :d

Thanks for your patience and help.
 
Solved with lastest NootRed.kext, Thank a lot Edhawk for your Help

sonoma_14.6.1.png
 
Last edited:
  • Like
Reactions: Edhawk
  AdBlock Detected
Sure, ad-blocking software does a great job at blocking ads, but it also blocks some useful and important features of our website. For the best possible site experience please take a moment to disable your AdBlocker.