GenMachine Ren5000

[long08]

• You need to disable or remove the WiFi & Bluetooth kexts and set SecureBootModel to ‘Disabled’ not ‘Default’ in your config.plist.
• Run the Sonoma update.
• Then revert the changes you made in your config.plist for the Sonoma 14.4.1 upgrade.
• Make sure you use the latest Intel WiFi and Bluetooth kexts with Sonoma 14.4 or newer.

Advice courtesy of @Edhawk.

Thank you very much, I will try it right now.

 

[craighazan]

Thank you very much, I will try it right now.

The general opinion is that Ventura is much more stable than Sonoma when using the NootedRed.kext. When Apple changes stuff in there code it can lead to all sorts of headaches for developers like ChefKiss who do this out of the kindness of their heart.

 

[Edhawk]

What do I need to edit to be able to go to sonoma

Don't!

Get everything up and running correctly on Ventura, before you upgrade to Sonoma. As the latest macOS just introduces more issues, especially for someone new to AMD Hackintosh.

 

[craighazan]

Successfully installed macOS Sequoia Beta 2 on my GenMachine. Intel BT, tick, Sound, tick, Wi-Fi, via a Ethernet connected to a Netgear EX3700 Wi-Fi Extender/Access Point.

 

[Edhawk]

@craighazan as you have a Metal 3 GPU you don't need the revblock=media boot argument.

 

[craighazan]

@craighazan as you have a Metal 3 GPU you don't need the revblock=media boot argument.

View attachment 14451

That’s good to know, thanks Edhawk I will edit later and report back.

 

[craighazan]

I removed the 'revblock=media' boot-arg from my config and my GenMachine didn't burst into flames, phew!. Someone asked my alter ego, SalmonPete on NootedRed discussions to see if Sequoia was lagging in HIDPI scaled resolution, I switched it up to 2K and everything still seems smooth, certainly no system lag.

 

[long08]

Successfully installed macOS Sequoia Beta 2 on my GenMachine. Intel BT, tick, Sound, tick, Wi-Fi, via a Ethernet connected to a Netgear EX3700 Wi-Fi Extender/Access Point.View attachment 14447

What do I need to edit to be able to run macOS Sequoia Beta 2?

 

[craighazan]

What do I need to edit to be able to run macOS Sequoia Beta 2?

Hi long08
I did the following, update these kexts;

• AppleALCU 1.9.0 > 1.9.1 Link
• lilu 1.6.7 > 1.6.8 Link
• RestrictEvents 1.1.3 > 1.1.4 Link
• VirtualSMC 1.3.2 > 1.3.3 Link
• NootedRed, [commit e326a5f]
• BlueToolFixup 2.6.9
• IntelBluetoothFimware 2.5.0
• ForgedInvariant Link

For installation of macOS Sequoia I disabled the following kexts. Specifically for NootrdRed which can hang for a long time on igpu in verbose!. I learnt a trick, you can enable NootrdRed after the second restart, that way you wouldn’t have to endure 7MB VRAM enabling it again. Also Bluetooth and Wi-Fi are touch and go at the moment, some have had success using heliport with AirportItlwm

• Airportitlwm
• BlueToolFixup
• IntelBluetoothFirmware
• NootedRed
• Changed SecureBoot to Disabled

Hope that helps.

 

[long08]

Hi long08
I did the following, update these kexts;

• AppleALCU 1.9.0 > 1.9.1 Link
• lilu 1.6.7 > 1.6.8 Link
• RestrictEvents 1.1.3 > 1.1.4 Link
• VirtualSMC 1.3.2 > 1.3.3 Link
• NootedRed, [commit e326a5f]
• BlueToolFixup 2.6.9
• IntelBluetoothFimware 2.5.0
• ForgedInvariant Link

For installation of macOS Sequoia I disabled the following kexts. Specifically for NootrdRed which can hang for a long time on igpu in verbose!. I learnt a trick, you can enable NootrdRed after the second restart, that way you wouldn’t have to endure 7MB VRAM enabling it again. Also Bluetooth and Wi-Fi are touch and go at the moment, some have had success using heliport with AirportItlwm

• Airportitlwm
• BlueToolFixup
• IntelBluetoothFirmware
• NootedRed
• Changed SecureBoot to Disabled

Hope that helps.

Thank you very much, I installed it successfully.
i have intel 7265 wifi card. i found it not working, i added itlwm.kext, IntelBluetoothFimware 2.5.0, BlueToolFixup 2.6.8

 

[craighazan]

Thank you very much, I installed it successfully.
i have intel 7265 wifi card. i found it not working, i added itlwm.kext, IntelBluetoothFimware 2.5.0, BlueToolFixup 2.6.8

No, neither wi-fi or BT are working for me either, I did get BT with Shaneees fix in Beta 1 but it stopped working in 2. Some people have had success getting Wi-Fi working using Itlwm and Heliport but I haven't tried it myself. I'm currently getting internet via Ethernet connected to a Wi-Fi access point.

 

[long08]

No, neither wi-fi or BT are working for me either, I did get BT with Shaneees fix in Beta 1 but it stopped working in 2. Some people have had success getting Wi-Fi working using Itlwm and Heliport but I haven't tried it myself. I'm currently getting internet via Ethernet connected to a Wi-Fi access point.

BT didn't work, but wifi worked with Itlwm and Heliport

 

[Gustavson]

Hi all!
I registered in the community quite recently, and unfortunately I am not an experienced macOS user.
However, I am interested in the Hackintosh topic, I learn a lot of new things here and try to develop myself.
I was very interested in your successful experience installing macOS on mini pc Gen5000. In an attempt to follow your path, I installed macOS on a Genmachine of a similar configuration at my disposal:

Cpu: AMD 5825U
Mem: Kingston 3200 2x16GB
WiFi/ Bt: BCM 94360NG
Net: RTL 8168/8111
NVMe1: Fanxiang S542Pro 1Tb install Win11.
NVMe2: WD SN580 1Tb install MacOS
Periphery: Magic mouse 2 and Kb Satechi Slim X1

It looks like everything worked out, the system Ventura is installed and is working stably.
But there is one point that my knowledge is not enough to solve.
The system does not go into sleep mode as it should.
The monitor goes out, while the power cycles off/on and the cooler continues to work. Pressing a key on the mouse or keyboard successfully wakes up the system and monitor.
I have not used EFI from this topic, but understanding your experience, I ask for advice on what to do to fix this problem and where the mistake was made. I hope for your help.
P.S. Please forgive my bad english).
P.P.S. EFI file attached. I received a system report using the pmset -g assertions command, maybe this will help understand the problem:

Last login: Wed Aug 14 19:30:35 on ttys000
_@iMac ~ % pmset -g assertions
2024-08-14 19:35:58 +0300
Assertion status system-wide:
BackgroundTask 0
ApplePushServiceTask 0
UserIsActive 1
PreventUserIdleDisplaySleep 0
PreventSystemSleep 0
ExternalMedia 1
PreventUserIdleSystemSleep 1
NetworkClientActive 0
Listed by owning process:
pid 847(rcd): [0x0000014e00098435] 00:15:41 UserIsActive named: "com.apple.rcdevent"
Timeout will fire in 259 secs Action=TimeoutActionRelease
pid 94(powerd): [0x0000000200088000] 00:21:13 ExternalMedia named: "com.apple.powermanagement.externalmediamounted"
pid 489(sharingd): [0x000004cc000185f3] 00:00:46 PreventUserIdleSystemSleep named: "Handoff"
pid 143(bluetoothd): [0x000004a8000185b1] 00:01:22 PreventUserIdleSystemSleep named: "com.apple.BTStack"
pid 150(WindowServer): [0x00000028000980b1] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle serviceID:1000005e5 service:AppleUserHIDEventService product:Slim X1 Keyboard eventType:3"
Timeout will fire in 1200 secs Action=TimeoutActionRelease
Kernel Assertions: 0x10c=USB,BT-HID,MAGICWAKE
id=500 level=255 0x4=USB creat=14.08.2024, 19:24 description=com.apple.usb.externaldevice.80300000 owner=USB Audio and HID
id=501 level=255 0x4=USB creat=14.08.2024, 19:24 description=com.apple.usb.externaldevice.60300000 owner=BRCM20702 Hub
id=503 level=255 0x4=USB creat=14.08.2024, 19:27 description=com.apple.usb.externaldevice.80100000 owner=4-Port USB 2.0 Hub
id=505 level=255 0x4=USB creat=14.08.2024, 19:30 description=com.apple.usb.externaldevice.80110000 owner=4-Port USB 2.0 Hub
id=508 level=255 0x100=MAGICWAKE creat=14.08.2024, 19:23 description=en0 owner=en0
id=511 level=255 0x8=BT-HID creat=14.08.2024, 19:18 description=com.apple.driver.IOBluetoothHIDDriver owner=AppleHSBluetoothDevice
Idle sleep preventers: IODisplayWrangler
_@iMac ~ %

 

[Edhawk]

Mapping your USB ports would be a good place to start. As that is the normal issue for Sleep/wake issues on a Hack.

 

[Gustavson]

Mapping your USB ports would be a good place to start. As that is the normal issue for Sleep/wake issues on a Hack.

Thanks for the advice, I will definitely do it soon

 

[Gustavson]

Hello everyone!

With the help of kind people, I managed to match USB connectors and make edits. But it didn't have the expected effect. The miniPC still turns off the monitor and goes to sleep mode, but does not stop the fan. After a minute of operation, the fan turns off for a second and starts again. It happens cyclically. When you press the keyboard button, the monitor wakes from sleep as it should be.

I tried my and your EFI, the result is the same. Something prevents the system from falling asleep.

Maybe it's about the special settings of S3 mode in the BIOS?

 

[Gustavson]

Tell me, please, what additional settings of the BIOS section do you use in addition to those listed at the beginning of the topic?
It looks like the behavior of the system, I have S1 (POS) sleep mode enabled, not S3 (STR). It's a good mini-PC, but I can't make it work properly on my own.
On the other hand, there are no problems with sleep mode in Win11 and Linux KDE Neon. Everything works as it should.
Minor improvements were made to the case to cool the disks.

 

[Edhawk]

Post a screenshot showing the systemwide power settings for you system. These can be obtained in Hackintool > Power tab or via Terminal commands

See the link below for sleep related terminal options on a Mac or Hack

10 Things You Can Do With Power Management Commands in Terminal

macOS Ventura's System Settings app may be a downgrade for power management, but that's where these Terminal commands come in handy.

www.makeuseof.com

 

[Gustavson]

Post a screenshot showing the systemwide power settings for you system. These can be obtained in Hackintool > Power tab or via Terminal commands

See the link below for sleep related terminal options on a Mac or Hack

10 Things You Can Do With Power Management Commands in Terminal

macOS Ventura's System Settings app may be a downgrade for power management, but that's where these Terminal commands come in handy.

www.makeuseof.com

With the pmset -g command, I get the following parameters:

 

[Edhawk]

Use the ‘fix’ button on the Hackintool > power tab. This will set Hibernatemode and power nap to ‘0’. This is a start towards fixing your self/wake issues.