9 ms·

Hackintosh: OpenCore EFI for HP Pavilion Aero 13 Laptop

486sx33 3y ago
Happy you are posting about hackintosh but generally sharing EFI folders isn’t at all best practice. Anyone who runs a hackintosh should learn how to build a proper config.plist with propertree for their own setup. Spread knowledge not scripts :)
- this_xor_that 3y ago
  Any references to tutorials for said proper config.plist designs?
  - jeroenhd 3y ago
    I think this guide is best when setting up a Hackintosh: https://dortania.github.io/OpenCore-Install-Guide/prerequisites.html https://dortania.github.io/OpenCore-Install-Guide/prerequisi... For parts of the config.plist, you can find generators, but when installing on raw hardware you will probably be combining presets based on your system specifics.
- mschuster91 3y ago
  Then OP would have 90% of their Github issues queue consist of "can't get XYZ to work" that's because something in the plist is broken and troubleshooting that can get very painful and annoying.
- colordrops 3y ago
  I'm confused, why are EFI folders unique in their need to be manually pieced together, as compared to pretty much any other of the thousands of subsystems on a computer?
  - hexagonwin 3y ago
    Every machine differs and the quirks needs to be set on the bootloader for hackintoshes. So the bootloader configuration file and required drivers (kexts) are added directly to a folder in the EFI partition.
- WesolyKubeczek 3y ago
  I would say that after a decade of hackintoshing, an EFI folder for a specific piece of hardware I happen to have is a good shortcut compared to reading tutorials with wildly varying quality of writing, language, and, crucially, information, most of which just describe where you need to go and get ready-made pieces and put them into predetermined locations. In 90% cases, "this tutorial should have been a script". The reason is twofold. First, tutorials are not "knowledge". They help you to get started, and then... You're on your own. Secondly, most hackintosh tutorials are not even that. Lots and lots of them are written by people who don't really know what they are doing and why. They put something together, they don't know how it works, but they rush to educate the masses nonetheless. Mechanistically putting the exact bits of configuration into a file and stringing some files in a directory does not make you magically learn how any of this works. Then again, I'm no CodeRush or usr-sse2 or vit9696 any other hackintosh star, but I've been tinkering with hackintoshes since 2009 and know a thing or two about how they work. However, I'm emphatically not fond of having to rediscover ACPI quirks of my machine on my own if someone else has done it, and done it better. Once the thing boots and works at its best, I promptly forget all the bootloader and ACPI intricacies I needed to juggle to make it work, this is not how I do my computering. Which is why premade EFI directories are good IMO, once you know what they are made of and why. Bonus points if well-commented .dsl files are published next to .amls, of course. Since OSX-KVM is out, though, I very happily confine my hackintoshing to a VM if I need it. With VFIO, you can even have accelerated desktop if it's what you fancy.
RecycledEle 3y ago
I wish Apple would apin off their x86 OSX as a separate company. I would love to see it compete with Microsoft Windows.
- OnlyMortal 3y ago
  They’re really a hardware company that builds appliances. Microsoft is a software company that builds some hardware. They’re coming from opposite directions.
  - CharlesW 3y ago
    > They’re really a hardware company… Nah, they're a software company that builds physical runtimes. "People who are really serious about software should make their own hardware." — Alan Kay
- wk_end 3y ago
  Why would they want to encourage people to buy x86 machines from vendors other than them?
  - rbanffy 3y ago
    Not that they would encourage people to buy machines from anyone but them, but, for x86, at least they don't make any machine with those chips anymore.
    - mrpippy 3y ago
      In a couple years they won’t make any software for those chips either
  - mschuster91 3y ago
    Lure a wider class of people into buying things from the App Store to generate more recurring revenue? Make macOS a more promising alternative to Windows in the corporate space?
mouse_ 3y ago
I can't believe it
kristopolous 3y ago
Help me on this. Do people really like say, macOS but not Apple hardware? Is this to lower cost? Just a hobby project? All the above? Forgive me. I've been on Linux since the 90s and don't really engage much with the Apple ecosystem. I don't mean this as a dig. I'm really ignorant on this stuff.
- dkjaudyeqooe 3y ago
  Apple hardware sucks for the following reasons: - it's expensive, especially if you want to load up on memory or disk space - there is limited choice - it's relatively unreliable - it's difficult to fix, you have to send it to Apple under warranty, third party repairs are difficult or impossible, self fix is impractical for most people With Hackintoshes you can have a solid desktop machine starting from $150 (motherboard and processor). You can easily fix it yourself by swapping out parts and get local warranty. You can upgrade and downgrade at will. You can use a much wider range of macOS versions. Laptops are a more complicated issue and much more marginal. I've used a Hackintosh as my daily driver for about 10 years ever since I had the misfortune of trying to get my brand new MacBook fixed by a "genius" who was actually a rude, condescending arsehole who spoke nonsense. Apple applied the trivial fix of a replacement internal cable and then held my laptop for nearly a week as a matter of policy.
  - moondev 3y ago
    hackintoshes also support a killer feature that new Mac computers do not - nested virtualization
    - nickpsecurity 3y ago
      Can you describe how you use that with what software packages?
      - moondev 3y ago
        A few examples: using vmware fusion provides an option to enable nested virtualization 1) running a windows vm from macos, and inside that windows vm you enable and use WSL2 or docker desktop. Both of those windows tools require nested virtualization 2) run a hypervisor such as esxi or proxmox as the vm OS, which in turn launches vms. Handy for simulating infra. 3) run a macos vm and inside that vm, install docker desktop for mac 4) experiment with any qemu/kvm tooling inside a linux vm, such as multipass or kubevirt Everything above is not possible on modern mac hardware but is on hackintosh
WillAdams 3y ago
I wish someone would be successful building a Hackintosh of one of the convertibles (or tablets) with Wacom EMR. It kills me that Microsoft crippled styluses in Fall Creator's Update, and it annoys me to no end having to toggle Settings to allow my stylus to work in Macromedia Freehand (though yes, I'll admit that's better than having to run it in a penalty box).
alarsama 3y ago
I have used this EFI folder for my own HP Pavilion Aero 13! It works for the most part! I even commented in some of the issues for that GitHub repo a few months back… However, I had issues with sleep/wake. This has been the common pain point for me when working with Hackintoshes. There are a lot of things that can break sleep/wake, and I rely heavily on that feature working without issue. As much as I love Hackintoshes, they can be a huge time sink if you want 1-1 feature parity with an equivalent Apple product. It is not too difficult getting Hackintoshes to install and boot to the desktop in this day and age thanks to Dortania’s OpenCore guide and contributions from groups like Acidanthera. However, it takes far more time, effort, research, and trial-and-error to get small things working because there are so many different variants and situations to account for. Examples - Wifi/BT and Continuity features require cards pulled directly from a recent MacBook, or a Fenvi card, both of which no longer work with Sonoma without using OCLP / CPU profiles might need adjustment to account for battery life and performance issues / Intel SST was never used with MacOS devices, so any computers using Ice Lake Intel CPUs and Intel SST can’t have a working built-in microphone or headphone jack, etc. Reliability is a pain as well. Anything can break at any time. At this point, I’ve come to learn that if you want a macOS device that just works, you are better off just getting a new Mac mini (desktop) or MacBook Air/Pro (laptop). I understand the arguments against this (high costs for specs, lack of repairability, intentional sabotage of repairs with third-party parts, used market is a gamble with ADE/MDM and iCloud locks, lack of customization with other computer components, etc). But I (fortunately) have never had issues with any of my MacBooks or Mac minis. And they have always “just worked” for my use cases. Hackintoshes make for great fun projects where you do not rely on that computer for day-to-day operations. Though the ability to Hackintosh may soon be impossible with newer OS versions. It is only a matter of time since Apple is moving away from Intel x86 processors, which is part of what allowed Hackintoshes to be possible in the first place.
- tracker1 3y ago
  I ran my old 4790K as a hackintosh for a couple years. I would up using a USB DAC for audio, but it otherwise worked for me as a desktop. Wound up back in windows for a bit and now have been on Linux for a few years. Much happier just running Linux at this point. I'm not sure how much longer it will be before Apple kills off x86 support altogether and a modern hackintosh is simply no longer an option.

Happy you are posting about hackintosh but generally sharing EFI folders isn’t at all best practice. Anyone who runs a hackintosh should learn how to build a proper config.plist with propertree for their own setup. Spread knowledge not scripts :)

this_xor_that 3y ago
Any references to tutorials for said proper config.plist designs?
- jeroenhd 3y ago
  I think this guide is best when setting up a Hackintosh: https://dortania.github.io/OpenCore-Install-Guide/prerequisites.html https://dortania.github.io/OpenCore-Install-Guide/prerequisi... For parts of the config.plist, you can find generators, but when installing on raw hardware you will probably be combining presets based on your system specifics.
mschuster91 3y ago
Then OP would have 90% of their Github issues queue consist of "can't get XYZ to work" that's because something in the plist is broken and troubleshooting that can get very painful and annoying.
colordrops 3y ago
I'm confused, why are EFI folders unique in their need to be manually pieced together, as compared to pretty much any other of the thousands of subsystems on a computer?
- hexagonwin 3y ago
  Every machine differs and the quirks needs to be set on the bootloader for hackintoshes. So the bootloader configuration file and required drivers (kexts) are added directly to a folder in the EFI partition.
WesolyKubeczek 3y ago
I would say that after a decade of hackintoshing, an EFI folder for a specific piece of hardware I happen to have is a good shortcut compared to reading tutorials with wildly varying quality of writing, language, and, crucially, information, most of which just describe where you need to go and get ready-made pieces and put them into predetermined locations. In 90% cases, "this tutorial should have been a script". The reason is twofold. First, tutorials are not "knowledge". They help you to get started, and then... You're on your own. Secondly, most hackintosh tutorials are not even that. Lots and lots of them are written by people who don't really know what they are doing and why. They put something together, they don't know how it works, but they rush to educate the masses nonetheless. Mechanistically putting the exact bits of configuration into a file and stringing some files in a directory does not make you magically learn how any of this works. Then again, I'm no CodeRush or usr-sse2 or vit9696 any other hackintosh star, but I've been tinkering with hackintoshes since 2009 and know a thing or two about how they work. However, I'm emphatically not fond of having to rediscover ACPI quirks of my machine on my own if someone else has done it, and done it better. Once the thing boots and works at its best, I promptly forget all the bootloader and ACPI intricacies I needed to juggle to make it work, this is not how I do my computering. Which is why premade EFI directories are good IMO, once you know what they are made of and why. Bonus points if well-commented .dsl files are published next to .amls, of course. Since OSX-KVM is out, though, I very happily confine my hackintoshing to a VM if I need it. With VFIO, you can even have accelerated desktop if it's what you fancy.

RecycledEle 3y ago

I wish Apple would apin off their x86 OSX as a separate company. I would love to see it compete with Microsoft Windows.

OnlyMortal 3y ago
They’re really a hardware company that builds appliances. Microsoft is a software company that builds some hardware. They’re coming from opposite directions.
- CharlesW 3y ago
  > They’re really a hardware company… Nah, they're a software company that builds physical runtimes. "People who are really serious about software should make their own hardware." — Alan Kay
wk_end 3y ago
Why would they want to encourage people to buy x86 machines from vendors other than them?
- rbanffy 3y ago
  Not that they would encourage people to buy machines from anyone but them, but, for x86, at least they don't make any machine with those chips anymore.
  - mrpippy 3y ago
    In a couple years they won’t make any software for those chips either
- mschuster91 3y ago
  Lure a wider class of people into buying things from the App Store to generate more recurring revenue? Make macOS a more promising alternative to Windows in the corporate space?

mouse_ 3y ago

I can't believe it

kristopolous 3y ago

Help me on this. Do people really like say, macOS but not Apple hardware? Is this to lower cost? Just a hobby project? All the above? Forgive me. I've been on Linux since the 90s and don't really engage much with the Apple ecosystem. I don't mean this as a dig. I'm really ignorant on this stuff.

dkjaudyeqooe 3y ago
Apple hardware sucks for the following reasons: - it's expensive, especially if you want to load up on memory or disk space - there is limited choice - it's relatively unreliable - it's difficult to fix, you have to send it to Apple under warranty, third party repairs are difficult or impossible, self fix is impractical for most people With Hackintoshes you can have a solid desktop machine starting from $150 (motherboard and processor). You can easily fix it yourself by swapping out parts and get local warranty. You can upgrade and downgrade at will. You can use a much wider range of macOS versions. Laptops are a more complicated issue and much more marginal. I've used a Hackintosh as my daily driver for about 10 years ever since I had the misfortune of trying to get my brand new MacBook fixed by a "genius" who was actually a rude, condescending arsehole who spoke nonsense. Apple applied the trivial fix of a replacement internal cable and then held my laptop for nearly a week as a matter of policy.
- moondev 3y ago
  hackintoshes also support a killer feature that new Mac computers do not - nested virtualization
  - nickpsecurity 3y ago
    Can you describe how you use that with what software packages?
    - moondev 3y ago
      A few examples: using vmware fusion provides an option to enable nested virtualization 1) running a windows vm from macos, and inside that windows vm you enable and use WSL2 or docker desktop. Both of those windows tools require nested virtualization 2) run a hypervisor such as esxi or proxmox as the vm OS, which in turn launches vms. Handy for simulating infra. 3) run a macos vm and inside that vm, install docker desktop for mac 4) experiment with any qemu/kvm tooling inside a linux vm, such as multipass or kubevirt Everything above is not possible on modern mac hardware but is on hackintosh

WillAdams 3y ago

I wish someone would be successful building a Hackintosh of one of the convertibles (or tablets) with Wacom EMR. It kills me that Microsoft crippled styluses in Fall Creator's Update, and it annoys me to no end having to toggle Settings to allow my stylus to work in Macromedia Freehand (though yes, I'll admit that's better than having to run it in a penalty box).

alarsama 3y ago

I have used this EFI folder for my own HP Pavilion Aero 13! It works for the most part! I even commented in some of the issues for that GitHub repo a few months back… However, I had issues with sleep/wake. This has been the common pain point for me when working with Hackintoshes. There are a lot of things that can break sleep/wake, and I rely heavily on that feature working without issue. As much as I love Hackintoshes, they can be a huge time sink if you want 1-1 feature parity with an equivalent Apple product. It is not too difficult getting Hackintoshes to install and boot to the desktop in this day and age thanks to Dortania’s OpenCore guide and contributions from groups like Acidanthera. However, it takes far more time, effort, research, and trial-and-error to get small things working because there are so many different variants and situations to account for. Examples - Wifi/BT and Continuity features require cards pulled directly from a recent MacBook, or a Fenvi card, both of which no longer work with Sonoma without using OCLP / CPU profiles might need adjustment to account for battery life and performance issues / Intel SST was never used with MacOS devices, so any computers using Ice Lake Intel CPUs and Intel SST can’t have a working built-in microphone or headphone jack, etc. Reliability is a pain as well. Anything can break at any time. At this point, I’ve come to learn that if you want a macOS device that just works, you are better off just getting a new Mac mini (desktop) or MacBook Air/Pro (laptop). I understand the arguments against this (high costs for specs, lack of repairability, intentional sabotage of repairs with third-party parts, used market is a gamble with ADE/MDM and iCloud locks, lack of customization with other computer components, etc). But I (fortunately) have never had issues with any of my MacBooks or Mac minis. And they have always “just worked” for my use cases. Hackintoshes make for great fun projects where you do not rely on that computer for day-to-day operations. Though the ability to Hackintosh may soon be impossible with newer OS versions. It is only a matter of time since Apple is moving away from Intel x86 processors, which is part of what allowed Hackintoshes to be possible in the first place.

tracker1 3y ago
I ran my old 4790K as a hackintosh for a couple years. I would up using a USB DAC for audio, but it otherwise worked for me as a desktop. Wound up back in windows for a bit and now have been on Linux for a few years. Much happier just running Linux at this point. I'm not sure how much longer it will be before Apple kills off x86 support altogether and a modern hackintosh is simply no longer an option.