Skip to content

HorizonUnix/UXTU4Unix

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Powered by RyzenAdj and Python

GitHub Downloads (all assets, latest release)


Warning

  • With the end of Hackintosh support in macOS 26 Tahoe, UXTU4Unix v0.4.x series will be the last version to support macOS. After that, we will shift our focus solely to Linux until UXTU officially supports Linux.
  • Warning (macOS): Avoid using UXTU4Unix in conjunction with SMCAMDProcessor due to potential conflicts.

Supported APU & Operating Systems

  • Compatible with AMD Ryzen APUs supported by either NootedRed or the Premade Preset section in UXTU (or generally supported by RyzenAdj).
  • Operating Systems: macOS 10.9 through 26, and Linux (with upower and libpci installed).

Usage Instructions

  • Disable Secure Boot in the BIOS. (Unknown: Applying the Secure Boot certificate to UEFI may enable compatibility.)
  • Download the official build from the Releases.
  • Run UXTU4Unix.command (macOS only) or run UXTU4Unix.py using the command: python3 /path/to/UXTU4Unix.py or python /path/to/UXTU4Unix.py.
  • Follow the on-screen instructions.
  • [macOS] For enhanced temperature management and control with UXTU4Unix, disable Core Performance Boost in the BIOS using Smokeless_UMAF. Note that this may significantly reduce CPU performance, as the Core Performance Boost feature on macOS is not optimal.

Fixing Python Certificates on macOS

Frequently Asked Questions

1. Why is SIP disabled in macOS?

  • The binaries (ryzenAdj and DirectHW) are flagged as untrusted kexts in macOS. To ensure functionality, it is necessary to disable SIP and include the ALLOW_UNTRUSTED_KEXTS flag (0x1).

2. Why does UXTU4Unix lack comprehensive CPU support?

  • During the transition of AMD APU presets from UXTU to UXTU4Unix, some commands were incompatible with ryzenAdj. UXTU employs various methods to modify CPU/APU settings beyond those supported by ryzenAdj, particularly concerning CPU presets. Consequently, only select commands were retained as workarounds.

Advanced Users

For more detailed configurations, please refer to Custom.md.

Preview

Acknowledgments