MatinDevs Posted July 15, 2025 Share Posted July 15, 2025 I realized that I have to post here in order to unlock my account, so I'll be using this opportunity to share my experiences with hackintoshing. I've had an HP ProDesk with i7-7700 and an HP EliteBook 1050 G1, and in almost every step of hackintoshing, there's a wired quirk for HP PCs. You'll just face problems that seems that nobody else in the world has, and that makes the whole thing PAINFUL 😖. I haven't seen much wired reports for Asus, Lenovo and ThinkPads, so I guess you'll have a more streamlined process with those. What is your experience with these brands? Quote Link to comment https://www.insanelymac.com/forum/topic/361349-dont-buy-hp/ Share on other sites More sharing options...
Slice Posted July 15, 2025 Share Posted July 15, 2025 The Clover bootloader has a special patch for HP: Quote <key>KernelLapic</key> <true/> There is a problem with lapic on HP laptops, which is solved by running with cpus=1, or now with this patch <true/>. The problem and solution have existed for a long time, since the Chameleon, but new developers have not yet reached HP laptops to understand more seriously what the trick is here. 1 Quote Link to comment https://www.insanelymac.com/forum/topic/361349-dont-buy-hp/#findComment-2837117 Share on other sites More sharing options...
fspkwonx86 Posted July 18, 2025 Share Posted July 18, 2025 (edited) AICPM Patch: just clearing the CPU0 CPU1 CPU2 CPU3 {} Functions so it just Returns but this takes someone more experienced than i... HPET: add IRQs... and Remove the IRQs of other conflicting devices, and.... RTC: Change the length to 0x02 or something like that add or remove irqs.. PCI0 = _UID=(0x01) = pciroot_uid=1 _ADR, Zero = _UID, Zero - npci=0x2000 Processor (CP00, 0x00, 0x00001810, 0x06) <- FIX LAPIC [Processor Local APIC] Processor ID : 10 Processor (CP00, 0x10, 0x00001810, 0x06) if it were this it would be correct but its not so the SSDT has to be patched and dropped with Clover meaning invoking one of the tickboxes.... im at doing non-standard things like including Low Level SuperIO using their Patch Method and Plugin Method, using the SMBUS/EC Controller..., and Native Platform Plugin.. .. like you said this is likely every HP Computer my first test subject was a HP Touchsmart , i was staying in california and had that to mess around with..... ..,,,,, just because it requires this little fixup doesnt make it any worse or better... itll run the same once fixed.. Edited July 18, 2025 by fspkwonx86 Quote Link to comment https://www.insanelymac.com/forum/topic/361349-dont-buy-hp/#findComment-2837377 Share on other sites More sharing options...
BeverlyLBourke Posted August 3, 2025 Share Posted August 3, 2025 (edited) On 7/15/2025 at 6:07 PM, MatinDevs said: I realized that I have to post here in order to unlock my account, so I'll be using this opportunity to share my experiences with hackintoshing. I've had an HP ProDesk with i7-7700 and an HP EliteBook 1050 G1, and in almost every step of hackintoshing, there's a wired quirk for HP PCs. You'll just face problems that seems that nobody else in the world has, and that makes the whole thing PAINFUL 😖. I haven't seen much wired reports for Asus, Lenovo and ThinkPads, so I guess you'll have a more streamlined process with those. What is your experience with these brands? solitaired Yikes, that sounds frustrating I’ve had similar issues and totally feel your pain Edited August 4, 2025 by BeverlyLBourke Quote Link to comment https://www.insanelymac.com/forum/topic/361349-dont-buy-hp/#findComment-2838329 Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.