-
Posts
95,321 -
Joined
-
Last visited
Everything posted by MaLd0n
-
FIRST we need boot with one efi clean Try this efi folder if work extract sendme and ioreg https://www.transfernow.net/dl/20230303hTiVbuPo
-
This kext lose support Check if have some updated version
-
check ioreg
-
dgpu is full disable or do u used only bootarg to disable it?
-
DSDT Patching request For ASUS B550 F Gaming
MaLd0n replied to Sajid7890's topic in DSDT & Patch Requests
Post in topic bellow if you want someone to patch your DSDT, please don't open a new topic or PM, unless you are trying to learn how to do it yourself and need help. https://www.olarila.com/topic/923-dsdt-patch-requests/ Check link bellow about Donator and Premium users. https://www.olarila.com/topic/7717-important-premium-and-donators-users/ -
Help I have a problem with the installation.
MaLd0n replied to Briant Reyes's topic in Guides and Tutorials
Use Opencore MOD and try https://www.olarila.com/topic/20908-easy-fast-and-perfect-vanilla-hackintosh/ -
Donation with Paypal https://tinyurl.com/r7fchn9 Donation with Binance 0xdbe48ef6b158f1dd0035d7f49555c99e52f72714 Donation with Stripe https://tinyurl.com/2ssnydn6 Donation with BuyMeaCoffee https://tinyurl.com/bvsbpf6e Donation with BTC 33HeGCuCSh4tUBqdYkQqKpSDa1E7WeAJQ3 Donation with PicPay @danielnmaldonado Donation with PiX @danielnmaldonado@gmail.com Donation with Mercado Livre https://tinyurl.com/y9evkj5u A very and big special thanks to Vit9696 and XLR -Tutorial - https://tinyurl.com/y2dmt5af -USB Remap - https://tinyurl.com/2p88p2ff -Request your DSDT on forum - https://tinyurl.com/yc2zrkam -Request your DSDT on forum (Premium and Donator users) - https://tinyurl.com/2swmsnzk A very custom DSDT for best experience under macOS. Removed all unused devices, injected all Apple devices, essentials, cosmetics, real improvements. -My Hardware Mobo GA Z690 UD AX Processor i9-12900K GPU use one AMD card like Rx560, Rx580, Vega, Rx5500, Rx5700, Rx6600xt, Rx6800, Rx6900 -ScreenShots Credits: Opencore and Clover team, Mieze, RehabMan, etorix, metacollin, XLR and many others!
-
u can use a pre remap usb for easy installation if have only usb3 uia_exclude=HS08;HS09;HS10;HS11;HS12;HS13;HS14;USR1;USR2
-
u need follow here with OpenCore no acpi https://www.olarila.com/topic/24542-opencore-no-acpi-how-to-use-this-fork/
-
Dosdude1 MacOS Patcher is an all-new, easy-to-use tool that allows anyone to install macOS on unsupported Macs. Link HERE
-
HDMI Audio sound for AMD Radeon RX 5500 XT
MaLd0n replied to niypoo's topic in DSDT & Patch Requests
Inject things direct on DSDT or via ssdt Inject "onboard-2" on PEGP and HDAU -
Remove _PRW only in device XDCI
-
https://www.olarila.com/topic/20908-easy-fast-and-perfect-vanilla-hackintosh/
-
Automatic handling of brightness keys based on ACPI Specification. Link HERE Boot arguments -brkeysdbg to enable debug printing (available in DEBUG binaries). Special cases Typically no DSDT patches are required. Please remove old _Qxx to XQxx ones. On some models, may be required add ACPI patch _OSI to XOSI and SSDT-XOSI. Spoiler: On some old ThinkPad models, additional handling may be required. Credits Apple for macOS usr-sse2 for separating this driver from VoodooPS2 vit9696 for DeviceInfo API from Lilu zhen-zen for implementation
-
An open source kernel extension providing a way to emulate some offsets in CMOS (RTC) memory. It can help you to avoid some conflicts between macOS AppleRTC and firmware/BIOS of your PC. It can also help you to find out at which offsets you have a conflict. In most cases it is enough to boot with some offsets in boot-args, perform sleep, wake and reboot. If you don't see any CMOS errors or some unexpected reboots, it means you have managed to exclude conflicted CMOS offsets. Offsets in boot-args rtcfx_exclude can have value from 00 to FF (wihout prefix 0x). Be careful: Offsets from 0 to 0D usually are more or less 'compatible' and should not cause any conflicts. Offsets from 0x80 to 0xAB are used to store some hibernation information (IOHibernateRTCVariables). If any offset in this range causes a conflict, you can exclude it, but hibernation won't work. In my case it was only the one offset: B2. B0 - B4 offsets are used for PowerManagement features, but they don't work on hacks anyway) Link HERE Compilation This kext is not Lilu-plugin, but it still relies on some useful methods from Lilu libraries, so you have to put Lilu.kext into project folder. Boot-args rtcfx_exclude=offset1,offset2,start_offset-end_offset... - list of offsets or ranges of offsets where writing is not allowed -rtcfxdbg turns on debugging output Credits Apple for macOS vit9696 for Lilu.kext and great help in implementing some features lvs1974 for writing the software and maintaining it
-
Intel onboard LAN driver for macOS. Courtesy of Laura Müller. This copy includes alterations that are of concern in Acidanthera as well as kernel debugging support initially provided by aerror2 in IntelMausiEthernetWithKernelDebugger repository. Do use the original version when uncertain. No support or troubleshooting provided. Wake on LAN functionality should work out of the box. On misconfigured hardware one may try to force-enable it by injecting mausi-force-wol device property (with any value, recommended), or -mausiwol boot argument (for testing purposes). Link HERE A few days before Christmas I started my latest project, a new driver for recent Intel onboard LAN controllers. My intention was not to replace hnak's AppleIntelE1000e.kext completely but to deliver best performance and stability on recent hardware. That's why I dropped support for a number of older NICs. Currently the driver supports: 5 Series 82578LM 82578LC 82578DM 82578DC 6 and 7 Series 82579LM 82579V 8 and 9 Series I217LM I217V I218LM I218V I218LM2 I218V2 I218LM3 100 Series I219V I219LM I219V2 I219LM2 I219LM3 200 Series I219LM I219V 300 Series I219LM I219V Key Features of the Driver Support for multisegment packets relieving the network stack of unnecessary copy operations when assembling packets for transmission. No-copy receive and transmit. Only small packets are copied on reception because creating a copy is more efficient than allocating a new buffer. TCP, UDP and IPv4 checksum offload (receive and transmit). Support for TCP/IPv6 and UDP/IPv6 checksum offload. Makes use of the chip's TCP Segmentation Offload (TSO) feature with IPv4 and IPv6 in order to reduce CPU load while sending large amounts of data (disabled due to hardware bugs). Fully optimized for Mavericks or newer (64-bit architecture). Support for Energy Efficient Ethernet (EEE). VLAN support is implemented but untested as I have no need for it. The driver is published under GPLv2.
-
An open source kernel extension providing a set of patches required for non-native Airport Broadcom Wi-Fi cards. Link HERE Notes This repository should be compiled with Lilu v1.2.4 or greater, otherwise the compilation will fail! Currently requires macOS 10.10 or newer. Note: Debug version of Lilu.kext should be put in the same folder as BrcmWLFixup! And they should be also used together! Features Supports AirPort_Brcm4360, AirPort_BrcmNIC and AirPort_BrcmNIC_MFG Implements patch for chip identificator checking (0xaa52), in <=10.12 it's required for successful driver starting Implements patch for "Failed PCIe configuration patch", required for some cards Implements patch for "Third Party Device" (returns vendor name "Apple") Implements patch for removing of white-list check Implements 5Ghz and country code patch (US by default) Implements WOWL (WoWLAN) disabler (turned on by default) - no low speed after wake Implements patch to disable LPO panic in AirPortBrcmNIC Installation types Clover Airport Fix + AirportBrcmFixup Clover Airport Fix + AddProperties(fake device-id) + AirportBrcmFixup (preferable) Clover Airport Fix + AirportBrcmFixup + FakePCIID + FakePCIID_Broadcom_WiFi.kext AirportBrcmFixup + FakePCIID + FakePCIID_Broadcom_WiFi.kext Boot-args -brcmfxdbg turns on debugging output -brcmfxbeta enables loading on unsupported osx -brcmfxoff disables kext loading -brcmfxwowl enables WOWL (WoWLAN) - it is disabled by default -brcmfx-alldrv allows patching for all supported drivers, disregarding current system version (see Matching device-id and kext name in different macOS versions) Specific boot-args and ioreg properties brcmfx-country=XX changes the country code to XX (US, CN, #a, ...), also can be injected via DSDT or Properties → DeviceProperties in bootloader brcmfx-aspm overrides value used for pci-aspm-default brcmfx-wowl enables/disables WoWLAN patch brcmfx-delay delays start of native broadcom driver for specified amount of milliseconds. It can solve panics or missing wi-fi device in Monterey. You can start with 15 seconds (brcmfx-delay=15000) and successively reduce this value until you notice instability in boot. brcmfx-alldrv allows patching for all supported drivers, disregarding current system version (see Matching device-id and kext name in different macOS versions) brcmfx-driver=0|1|2|3 enables only one kext for loading, 0 - AirPortBrcmNIC-MFG, 1 - AirPortBrcm4360, 2 - AirPortBrcmNIC, 3 - AirPortBrcm4331, also can be injected via DSDT or Properties → DeviceProperties in bootloader Possible values for brcmfx-aspm (and pci-aspm-default): 0 disables ASPM kIOPCIExpressASPML0s = 0x00000001, kIOPCIExpressASPML1 = 0x00000002, kIOPCIExpressCommonClk = 0x00000040, kIOPCIExpressClkReq = 0x00000100 Credits Apple for macOS vit9696 for Lilu.kext and great help in implementing some features PMheart for the initial idea and implementation darkvoid & RehabMan for FakePCIID implementation (partly used in AirportBrcmFixup) al3xtjames for disabling LPO panic in AirPortBrcmNIC lvs1974 for writing the software and maintaining it Matching device-id and kext name in different macOS versions [10.8] AirPortBrcm4360: 43a0, IOProbeScore = 641 AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 615 [10.9] AirPortBrcm4360: 43a0, IOProbeScore = 842 AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 700 [10.10] AirPortBrcm4360: 43ba, 43a3, 43a0, 4331, 4353, IOProbeScore = 930 AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 900 [10.11] AirPortBrcm4360: 43ba, 43a3, 43a0, 4331, 4353, IOProbeScore = 1040 AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 800 [10.12] AirPortBrcm4360: 43ba, 43a3, 43a0, 4331, 4353, IOProbeScore = 1152 AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 800 [10.13] AirPortBrcm4360: 4331, 4353, IOProbeScore = 1240 AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 800 AirPortBrcmNIC: 43ba, 43a3, 43a0, IOProbeScore = 1241 AirPortBrcmNIC-MFG: 43ba, 43a3, 43a0, IOProbeScore = -1000 [10.14] AirPortBrcm4360: 4331, 4353, IOProbeScore = 1400 AirPortBrcm4331: 4331, 4353, 432b, IOProbeScore = 800 AirPortBrcmNIC: 43ba, 43a3, 43a0, IOProbeScore = 1400 AirPortBrcmNIC-MFG: 43ba, 43a3, 43a0, IOProbeScore = -1000 [10.15] AirPortBrcm4360: 4331, 4353, IOProbeScore = 1400 AirPortBrcm4331: removed AirPortBrcmNIC: 43ba, 43a3, 43a0, IOProbeScore = 1400 AirPortBrcmNIC-MFG: removed [11] AirPortBrcm4360: removed AirPortBrcm4331: removed AirPortBrcmNIC: 43ba, 43a3, 43a0, IOProbeScore = 1400 AirPortBrcmNIC-MFG: removed [12] AirPortBrcm4360: removed AirPortBrcm4331: removed AirPortBrcmNIC: 43ba, 43a3, 43a0, IOProbeScore = 1400, kext is moved to the new location - IO80211FamilyLegacy.kext/Contents/PlugIns AirPortBrcmNIC-MFG: removed [13] AirPortBrcm4360: removed AirPortBrcm4331: removed AirPortBrcmNIC: 43ba, 43a3, 43a0, IOProbeScore = 1400, kext is moved to the new location - IO80211FamilyLegacy.kext/Contents/PlugIns AirPortBrcmNIC-MFG: removed Until version [10.13] there were only two kexts and for the most cases FakeID = 43a0 was enough to get working Wi-Fi. In [10.13] (and later) one family was separated into AirPortBrcm4360 (probably will be removed in 10.15), AirPortBrcmNIC and AirPortBrcmNIC-MFG. A proper fake-id has to be considered to load appropriate kext. Some device-id have limitations in one kext (like 5 Ghz range), but do not have it another. Please pay attention In 11+ class AirPortBrcm4360 has been completely removed. Using of injector kext with such class name and matched vendor-id:device-id blocks loading of original airport kext. To address this issue and keep compatibility with older systems injectors for AirPortBrcm4360 and AirPortBrcmNIC were removed from main Info.plist file. Instead, the two new kext injectors are deployed in PlugIns folder: AirPortBrcm4360_Injector.kext and AirPortBrcmNIC_Injector.kext. You have to block (or remove) AirPortBrcm4360_Injector.kext in 11+. In OpenCore you can specify MaxKernel 19.9.9 for AirPortBrcm4360_Injector.kext. In Clover you can have two different AirportBrcmFixup.kext, but in kext folder with version name 11 and 12 and 13 AirportBrcmFixup.kext must not contain AirPortBrcm4360_Injector.kext. You don't need these injectors at all if your vendor-id:device-id is natively supported by AirPortBrcmNIC or AirPortBrcm4360 (your device-id is included into Info.plist in these kexts).
-
It is a Lilu plugin, combining functionality of VoodooTSCSync and disabling xcpm_urgency if TSC is not in sync. It should solve some kernel panics after wake. WARNING: CPUs without MSR_IA32_TSC_ADJUST (03Bh) are currently unsupported on macOS 12 and newer. WARNING: if you still get kernel panic like "Non-monotonic time: invoke at 0xxxxxxxxxxx, runnable....", you can try to add TSC_sync_margin=0 into your boot-args. Link HERE Boot-args -cputsdbg turns on debugging output -cputsbeta enables loading on unsupported osx -cputsoff disables kext loading -cputsclock forces using of method clock_get_calendar_microtime to sync TSC (the same method is used when boot-arg TSC_sync_margin is specified) Credits Apple for macOS vit9696 for Lilu.kext Voodoo Projects Team for initial idea and implementation RehabMan for improved implementation lvs1974 for writing the software and maintaining it
-
A Lilu plugin intended to enable debug output in the macOS kernel, the original idea belongs to Piker-Alpha, see https://github.com/Piker-Alpha/debugMachKernel.sh for more details. Link HERE Boot-args -dbgenhdbg turns on debugging output -dbgenhbeta enables loading on unsupported osx -dbgenhoff disables kext loading -dbgenhiolog redirect IOLog output to kernel vprintf (the same as for kdb_printf and kprintf)
