May be it's a time to think about EFI-based boot loader?
---------------
November 2012
Using git
http://www.projectosx.com/forum/index.php?...ost&p=21635
----------------
26.07.2012
Creating GCC46 toolset starting with Xcode 4.3.3
-------------------------------------------
31.03.2012
Automatic script by STVNUB to create Clover from zero.
-------------------------------------------
29.02.2012
Step by step instructions "How to make Clover from zero"
------------------------------------------
26.01.2012
Now Lion compilation method from jadran using recent gcc compiler.
http://www.projectosx.com/forum/index.php?...ost&p=16669
------------------------------------------
11.10.2011
New instructions how to make the bootloader
http://www.projectosx.com/forum/index.php?...ost&p=16010
One needed tool mtoc can be found here
http://www.projectosx.com/forum/index.php?...ost&p=15498

Instruction below are obsolete.
-------------------------------------------
posts #2,3 now can be performed automatically by jadran's script
Note; There is no more needed in the script to download CpuDxe from UDK2010. Now native UefiCpuDxe is working.

post#1 will be obsolete.
-------------------------------------------
Prepare tools:
Follow this guide.
1. Download prebuild tools from the site
http://www.osxbook.com/book/bonus/chapter4...0-2.3.6.tar.bz2
Copy to system

These utilities will be also usefull to compile bootsectors.
2. Set PATH variable

3. Download gnu-efi-3.x. There are many download locations found by google. May be you will find more recent sources then at the osxbook. Unpack.
4. EFI definitions in the package is too old. I want to modify them.
 gnu_efi.diff.zip ( 11.33K ) Number of downloads: 94

Briefly: I applied EFI definitions from Intel to file efiapi.h and some related files.
5. Correct Make.defaults for our tools

6. Compile and install headers


Now we can compile EFI applications using these tools. To do that we need to edit makefile and correct headers in the sources.
For example rEFIt. http://refit.sourceforge.net/
1. Download sources. Unpack.
2. Correct make.common as follows

3. First go to libeg folder

4. Next goto refit folder

There is refit.efi here!

Any more proposition?
Is there any way to do with UDK2010.UP3?

Lets continue with EDK2. Thank to Kabyl for providing guide how to.
But... as usual some steps should be revised.
http://sourceforge.net/apps/mediawiki/tian...s#Mac_OS_X_10.5
1. gmp library

Success!
2. mpfr library. It changed and this guide no more works! Do the follow. EDITED: goto step 2a.
Goto http://www.mpfr.org/mpfr-current/#fixed
Download mpfr-3.0.0.tar.gz into ~/src
Unpack.

Now copy all files from mpfr-3.0 to mpfr-3.0.0 because mpfr-3.0 have no some files.
Copy Makefile.in into tests folder. (it is a bug that later sould be corrected by authors)

Then stop. make is not working while with mpfr-2.4.2 there was success.
2a. So return to http://www.mpfr.org/mpfr-2.4.2/
Download the package, unpack.

Success!
3. efitool. Now new Guide.

Old guide
http://sourceforge.net/apps/mediawiki/tian...php?title=Xcode
Goto Apple. http://opensource.apple.com/release/mac-os-x-1066/
Download latest cctools. Now it is 750. Why SF told about 782? Unpack.
Goto http://llvm.org/releases/download.html#2.7. Namely version 2.7! We can't use recent version! Download and unpack LLVM source code.
Copy the include/llvm-c directory from LLVM into the cctools include directory.

It stops with error after strip.c. It is normal! Continue

4. EDK2 Tools

it takes a time. Even an hour is CPU is not fast enough. Or you can use binay package @post28 by Kabyl.
http://www.projectosx.com/forum/index.php?...ost&p=13179

At this point i can't understand why gcc-4.3.0 is not compiled. So the previous step may be

Or this guide.

Continue

Now edit Conf/tools_def.txt

Find the TARGET_ARCH definition in Conf/target.txt and change the corresponding line to match this


now build

Success!

5. Boot sectors files. They are present as binary ready to use. If you want to recompile look here.

Now attempt to build Duet



Look into CpuDxe. It is empty!
Download UDK2010.UP3
There is another DuetPkg but without build.sh scripts. Join projects. Namely take CpuDxe from UDK and replace in the project
 CpuDxe.zip ( 31.21K ) Number of downloads: 34

Some correction in project files DuetPkgIa32.dsc:

and in DuetPkg.fdf

Now repeat ./build.sh and see success.

Now postbuild

Then rename folder edk2/Build/DuetPkgIA32/DEBUG_XCODE32 to edk2/Build/DuetPkgIA32/DEBUG_UNIXGCC
EDITED.
It seems to be better to correct build.sh NO
Corrections to postbuild.sh


Go!

Success!

Create bootable USB stick. The script CreateBootDisk is not working. Do manually

Copy Efildr20 and Efivar.bin into UsbDuet root and some bootloader and support files into efi.
For example:
Place Shell_Full.efi into /efi/boot/ and rename it to bootIA32.efi. It will be autostart.

EDITED:
Now we have a method to boot from HFS+ partition. Credits to Kabyl.
 bootHFS.zip ( 3.53K ) Number of downloads: 88

Copy files to ~/src/edk2/Build/DuetPkgIA32/DEBUG_XCODE32/FV

These files differ from Chameleon's!
Be sure about rdisk1s2 - installation drive, /Volumes/Duet
No matter MBR or GPT.

I checked. These boot0 and boot1h works fine with Chameleon.

slice,
I can't compile cctools under Lion: it needs mach/ppc/thread_status.h (why does it need PowerPC headers???).
Or do I need to compile all that prerequisites for kernel compilation from the near thread?

This post has been edited by гык-sse2: Mar 5 2011, 06:49 PM

because it's for Leopard, Lion doesn't have ppc in its SDK, maybe if you get cctools for Lion

Did you try removing ppc flags from Makefile(s)?

Dunno about Lion. We still have no headers for it. Just use Snow for development.
I think kernel prerequisites are desirable although not obligatory.

For Duet I need HFS+ drivers and patches. Any help?

HFS+ EFI drivers: http://www.mediafire.com/?0q96g6ujx9t61r2

Thank you, but what about opensource? I know libsaio folder from Chameleon.
What do you think about creating new svn project? We dont need EDK2 as a hole just minimum sources from it. DuetForMac.

EDITED.
There are EDK2 patches including HFS+ driver in VBox by Oracle. Applying to our sources with precautions!

The files I posted were extracted from a VMWare firmware, so no sources, but I did find a good source for HFS+ and and did some work on it, back when I was playing with DUET.


I've done some work on this, I have boot.efi loading and booting the kernel; the minimum required is:
- Fat binary support.
- setting the IODeviceTree:/efi/platform/FSBFrequency property.

This is done in a module, works under QEMU, but not tested on real HW.

I need to find sometime to get my EDKII work environment set up, and I might create a new project on github or something.

VMWare no sources but VirtualBox by Oracle - yes! Including HFS+.

And you have most of what you need here: http://www.virtualbox.org/svn/vbox/trunk/s...kg/VBoxAppleSim

Done!

Now next questions.
1. I want to start from HFS+ so Start32.asm should be rewritten as for example boot1h or boot2.s. What do you think?
2. FAT binary. I need bootloader for IA32 because of hardware. But others want to have x64. Two builds? Or we can join both? As I think EfiRuntime should be the same arch as kernel. Or it is possible to make Efildr as IA32 but put *efi modules for both arch, for example DxeIpl.efi+DxeIpl64.efi?
3. Do we propose to use Shell.efi or Refit.efi or just start Apple's boot.efi?

We could probably adapt boot1h to load Efldr and jump to it, but it needs to be of a limited size.


Two builds, we don't have a choice since boot.efi doesn't include an EBC binary.


Shell is a necessity, especially at this stage, rEFIt could be used for its UI.

What do you think about differencies between DUET from EDK106 and EDK2. usr-sse2 and A.Woland told then EDK1 is better for us, more stable and USB works better.

Just rename Efildr20 to boot
But no. Start32.S uses FAT32 to work.

Same here, main problem from my tests is AHCI.
I couldn't find one for 32 bit build that works on this MCP79 crap that I have
Funny thing, this netbook use Insyde EFI BIOS, but even I took the BIOS in pieces I didn't found so far any AHCI driver, only IDE., must be somewhere hidden or no idea how it switch to AHCI mode, only AHCI string I found is in setup module...

Yes, ATM EDKI is more stable and even faster than EDKII, but it's not actively developed anymore.

This isn't a problem though, because you're going to write a module and it can be used on either.


Check the load and jump address of Efildr and change them to what is found in Start32.

You didn't understand me. I mean that Start32 is a part of Efildr

and Start32.com uses FAT32, so Efildr20 can't be installed into HFS+ partition as I wish.

What about

We can use IA32 and X64 simultaneously?

Actually I did, it's the other way around I was talking about boot1h which can be used on HFS+.

You can skip Start32 in this case.


erm... that's for FAT filesystem.

Just jump over Start32? Fine! Thank for trick.
but
???