Jump to content
2 posts in this topic

Recommended Posts

Hello all.

 

I am trying to Hackintosh my Asus Eee PC 900 with OpenCore. Back in the day someone did it with iPC OSx86 10.5.6, but the exact tools that were used to do it have been lost to time. I scoured the internet and I got things working to some extent, but in the end I decided to go with current OpenCore and do it myself. I am following Dortania's guide.

 

The Eee PC 900 from 2008 uses a 32-bit 900MHz Celeron M of the Penryn family.

 

I've worked through setting up the appropriate EFI drivers and config.plist etc. I had to compile RehabMan's VoodooPS2 from source on OSX 10.7 in order to get a 32-bit build of that.

 

For ACPI, since there is nothing specific to 32-bit Penryn laptops, so I decompiled the DSDT myself, and found the edge case mentioned in the documentation - "PNP0C09 already named EC." None of the other patches seemed relevant. So I don't have a DSDT.aml on my stick.

 

My GMA 915's PCI ID should already be supported out of the box, so I shouldn't need to do anything there.

 

Since this is a 32-bit BIOS system, I installed DuetPkg and OpenCore IA32 to my USB stick (I am working from macOS 26 x86_64).

 

For EFI drivers, I have HFSPlus32, OpenRuntime, OpenVariableRuntimeDxe, PS2KeyboardDxe, and PS2MouseDxe based on what the documentation said is necessary for DuetPkg and for HFS+ on 32-bit CPUs. I ignored the suggestion about the USB keyboard driver and opted for the PS2 keyboard and mouse drivers instead, given that's what this laptop has.

 

My config.plist has been updated appropriately according to the documentation, using the recommended tools. (I followed the Desktop Penryn section, since that's the closest to what I have).

 

Whenever I try to boot my USB stick, it takes a minute to load files, and then outputs "BOOT MISMATCH!" and then "BOOT FAIL!". Nothing more. The documentation says to double check the directory heirarchy and make sure OpenCore.efi is in the right place. I have verified that. I also checked the contents of the MBR and VBR, and they looked correct.

 

I'd attach logs, but there is literally nothing other than those two lines.

What am I doing wrong here? Is there any way to capture more debugging information?

OpenCoreEeePC900.tar.zst

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.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...