Jump to content
37 posts in this topic

Recommended Posts

I created a hackintosh specific version of the MacOSX bootloader.

I tested it so far under legacy Clover.

 

Project page including more downloads:

https://github.com/andyvand/macosxbootloader

 

Built result hack specific is attached.

Test please, I need feedback as this is a new version.

Might need some more fixing here and there.

 

When testing please note the following in the report:

- Legacy boot / UEFI boot

- 32 / 64 bit Clover use

- Result

 

This one is Yosemite optimized and should work (support for hackintosh in initial stage)

EDIT: New version.

Added strict warning, enable all warnings flag and set warnings as errors flags, fixed some issues, implemented -f support and finally made sure everything was built optimized.

Also reimplemented driver loading (now works optimal and fast).

EDIT2: Added Clover build tools version.

boot.efi.zip

boot.clovertools.efi.zip

  • Like 2

Sorry Andy copy this file on usr/standalone/i386 folder or...?

I'm on UEFI Clover install.

This goes into /System/Library/CoreServices/boot.efi

First do sudo chflags nouchg /System/Library/CoreServices/boot.efi

Make sure to test on USB stick first...

  • Like 1

Does not work for me on Yosemite!!! :(

Any report to give?

After reboot my PC blocked on boot.

attachicon.gif2014-12-09 17.37.29.jpg

 

Now see where is the problem.

Thanks!!!

Try using legacy Clover boot.

Aptio reloc doesn't work yet (needs fix).

EDIT: Also note - this boot.efi is universal (32 + 64 bit arch).

You can also test 32-bit legacy Clover to boot into 64-bit kernel (works).

KP unable to find driver for this platform with Clover legacy for me.

Damn... do you have a patched DSDT in /EFI/CLOVER/ACPI/Patched?

If not, put one there...

Just to check...

Extremely fast boot after last update (If I can get the hackintosh specific bug fixed that doesn't enable ACPI platform init).

The new version has -f support (ignore kernel cache).

You might want to try this too...

EDIT: By the way - when I get home I'll add auto installer packages.... (need my dev certificates for signing these).

EDIT2: On the Github page you also find the regular built version (this can be used for real MacPro or so with only EFI32 to run Yosemite) with latest optimizations and strict flags and stuff and code modifications it should work real fast on such a machine...

  • Like 1

Anyone with an Ozmozis flashed mobo willing to test and report?

Would like to see reports there (as it's kind of weird that is doesn't load ACPI, should work as it does so on real Macs...)

Let me know please :D

Hi Andy unfortunately with boot.clovertools.efi get blank boot with uefi n legacy (intel machine)

And Apple version?

I allready noted some time ago that the combined 32+64 bit UEFI files only work when built from MS sources or Apple's..

You could easily rebuild though...

make CLOVERTOOLS=1

for 64 bit or

make CLOVERTOOLS=1 ARCH=i386

for 32 bit.

And don't combine them into and UEFI combined, I noticed it does not work...

Stay tuned currently updating project.

Post more on Github soon.

Hi Andy.

 

I send you a PM.

EDIT: you just reply in the meantime.

 


 

I'm going to move this topic in the bootloader section.

EDIT2: topic moved, and a temp link from previous source section as been given.

 

ErmaC

  • Like 1

BTW: Don't try any VM (VMWare, Virtualbox / Paralles) because don't work yet...

When I get that working: I'll post here ;)


Tested auto-installer,

Work insanely great.

It is integrated for build within main Makefile of Github sources too.

It execututes an universal  build and then packages it.

- make newinstaller (make flat style package).

- make legacy-installer (make Tiger style package.

Greetz

Andy

I added the packages and also the script.

It works great and makes booster (2 scripts and one Makefile ;))

Hey Andy, I know I already asked this but this has piqued my curiosity. I know the macpro1,1 requires a 32-bit bootloader but I don't really understand what this is for as far as hackintoshes go. Would I benefit from this on my 2600k build? It still needs another boot loader like clover or chameleon right? Sorry if it's a dumb question...

  • 1 month later...

I noticed that you use ARCHCFLAGS -target x86_64-pc-win32-macho for the 64-bit version of boot.efi but there is no target set for the 32-bit variants. What about using i386-pc-win32-macho?

It doesn't work, try it...

I tested and noticed it didn't want to use it.

It doesn't work, try it...

I tested and noticed it didn't want to use it.

Oops. That should have read: x86-pc-win32-macho

 

Anyway. I guess that you will still get the backend triplet error. I know that x86-pc-darwin-macho compiles, but that is probably also wrong. You better ask on the EDKII mailing list what to use for 32-bit EFI applications. I would have asked it myself, but I can't (work related limitation). Or file a clang bug report perhaps (since x86_64-pc-win32-macho works)?

  • Like 1

Oops. That should have read: x86-pc-win32-macho

 

Anyway. I guess that you will still get the backend triplet error. I know that x86-pc-darwin-macho compiles, but that is probably also wrong. You better ask on the EDKII mailing list what to use for 32-bit EFI applications. I would have asked it myself, but I can't (work related limitation). Or file a clang bug report perhaps (since x86_64-pc-win32-macho works)?

Tried all of those...

Found nothing with stock clang for 32 bit win target...

So I implemented it the way it is now

×
×
  • Create New...