Asrock X300 Chipset
- Thread starter Ejh4286
- Start date
-
Hello Guest. Before you post check the Troubleshooting guide here, Dortania Troubleshooting
Main issue is it lacks a discrete GPU. The Ryzen AM4 CPU should be fine.
A lot depends on the development of WhateverRed, this is a kext that aims to get AMD Integrated GPU's working in macOS. Have a read see what you think.
github.com
I think @Middleman had some joy getting an AMD integrated GPU working on one of his 'Project' Hacks.
A lot depends on the development of WhateverRed, this is a kext that aims to get AMD Integrated GPU's working in macOS. Have a read see what you think.
GitHub - ChefKissInc/NootedRed: The AMD Vega iGPU support patch kext. No commercial use.
The AMD Vega iGPU support patch kext. No commercial use. - ChefKissInc/NootedRed
github.com
I think @Middleman had some joy getting an AMD integrated GPU working on one of his 'Project' Hacks.
I recently bought Asrock Deskmeet X300 with 5700G. I have MSI RX580 on another build but since the RX580 is a bit too long for the Asrock Deskmeet.
My plan is to get RX6600 ITX GPU (200mm length limit) and see how it goes.
My plan is to get RX6600 ITX GPU (200mm length limit) and see how it goes.
With the development of NootedRed, I have successfully installed and run MacOs Monterey on my Asrock X300 DeskMeet.
First of all, credit goes to craighazan's under success story for starting the thread of his build and the feedbacks from members that helped me resolving my issues.
The way I install MacOs is a bit unorthodox since I started with BIGSUR and never got to the installation screen. So I end up using my older IvyBridge hackintosh and install a fresh copy of BigSur on the SSD, copy the EFI and place inside SDD/USB enclosure to boot on the Asrock DeskMeet X300. At first, it went through the booting process with no error and I was presented with graphic artifact,[see post #38) on other occasion, I got black monitor. Read through the thread from craighazan, I see someone had this same issue, I capture the screen using Command + Shift +4 and confirmed and indeed it was a clean image with no artifact.
I went back to my IvyBridge hackintosh and install Monterey on top on the SSD and this time it booted successfully with full graphic acceleration. My next step was to sort out the WIFI and Bluetooth (AC3168) that came with the system and managed to get them both working.
MB: Asrock DeskMeet X300 (BIOS 1.40E)
APU: 5700G with graphic.
WIFI: AC3168 (Wifi + Bluetooth)
Audio: ALC897 [Using alcid=12)
iMacPro1,1 is the system platform I use for my system
Sleep: it's not working based on my recollection when I put it to sleep.
Sleep update: I test by forcing the system to sleep and wake up with the keyboard successfully. Will try to let the system running and auto sleep based on energy setting.
-->For Audio being ALC897, I use alcid=12 in boot argument. (tested with tiny BluePiston via 3.5mm cable and also tested with bluetooth after I sorted out the bluetooth below)
-->For Wifi on AC3168, I use AirportItlwm.kext
-->For Bluetooth on AC3168, I use BlueToolFixup.kext, IntelBTPatcher.kext and IntelBlueToothFirmware.kext. upon checking per instruction, IntelBlueToothFirmware.kext did not load.
resolution is to map USB: boot into Windows on the DeskMeet x300 using USB mapping tool to generate kext for my system being "UTBMap.kext"(generated) + "USBToolBox.kext" (download) and place them inside OC/Kext on the EFI partition.
Here is my EFI (57MB) running Monterey in case someone with an Asrock DeskMeet X300 want to analyze and compare against their own EFI.
Will try direct update to Ventura or Sonoma when I have free time.
First of all, credit goes to craighazan's under success story for starting the thread of his build and the feedbacks from members that helped me resolving my issues.
The way I install MacOs is a bit unorthodox since I started with BIGSUR and never got to the installation screen. So I end up using my older IvyBridge hackintosh and install a fresh copy of BigSur on the SSD, copy the EFI and place inside SDD/USB enclosure to boot on the Asrock DeskMeet X300. At first, it went through the booting process with no error and I was presented with graphic artifact,[see post #38) on other occasion, I got black monitor. Read through the thread from craighazan, I see someone had this same issue, I capture the screen using Command + Shift +4 and confirmed and indeed it was a clean image with no artifact.
I went back to my IvyBridge hackintosh and install Monterey on top on the SSD and this time it booted successfully with full graphic acceleration. My next step was to sort out the WIFI and Bluetooth (AC3168) that came with the system and managed to get them both working.
MB: Asrock DeskMeet X300 (BIOS 1.40E)
APU: 5700G with graphic.
WIFI: AC3168 (Wifi + Bluetooth)
Audio: ALC897 [Using alcid=12)
iMacPro1,1 is the system platform I use for my system
Sleep: it's not working based on my recollection when I put it to sleep.
Sleep update: I test by forcing the system to sleep and wake up with the keyboard successfully. Will try to let the system running and auto sleep based on energy setting.
-->For Audio being ALC897, I use alcid=12 in boot argument. (tested with tiny BluePiston via 3.5mm cable and also tested with bluetooth after I sorted out the bluetooth below)
-->For Wifi on AC3168, I use AirportItlwm.kext
-->For Bluetooth on AC3168, I use BlueToolFixup.kext, IntelBTPatcher.kext and IntelBlueToothFirmware.kext. upon checking per instruction, IntelBlueToothFirmware.kext did not load.
resolution is to map USB: boot into Windows on the DeskMeet x300 using USB mapping tool to generate kext for my system being "UTBMap.kext"(generated) + "USBToolBox.kext" (download) and place them inside OC/Kext on the EFI partition.
Here is my EFI (57MB) running Monterey in case someone with an Asrock DeskMeet X300 want to analyze and compare against their own EFI.
Will try direct update to Ventura or Sonoma when I have free time.
Last edited:
That's all well and good. I'm happy to see you have a partially functioning Hack on your system. Well done.
But the credit for NootedRed.kext should go to the developers of the kext, not the person who pointed out that the kext exists (sorry Craig!).
But the credit for NootedRed.kext should go to the developers of the kext, not the person who pointed out that the kext exists (sorry Craig!).
Yes I had absolutely zero input in the development of NootedRed, all credit goes to the developers.