I would suggest two things if you are going to release these scripts for use. I know we all know these need to be executed as root, but I have seen several comments from people that had problems because they ran them as regular users. So, that should be checked.

The other thing that happens is the efi partition sometimes gets corrupted in such a way that it won't mount until it is checked. The code below is what I use in my mount script. use it if you wish.


I used a variable for diskID because I frequently work on an efi partition other than the one I booted from. There is my test partition and my emergency boot/maintenance partition both of which use efi partitions to boot.

A combination of your technique and mine could be used with a simple command line parameter and an if statement. Given a numeric parameter combine it with "disk$1s1" to make the drive ID, and if there is no parameter use your code as the default.

Just a thought.

btw: thanks for sharing - I should have done the same

anyone else lost the apple logo from the boot graphics since installing 6.1? don't know if it's something i did wrong. everything's still working fine so it's not an issue at all, just curious.

thanks,

Marc

Was removed to create more space for code. Munky mentions that in his post on 6.1.

munky thanks again for your work! I"m just wondering if V6.1 support apple software raid boot like the normal chameleon?

I was looking at their website, and Chameleon is on 1.0.11. So the above notice, is for whatever Chameleon number comes next after 1.0.11? I'm confused about the timing and dates. Building an i7 machine.

Another P4 user here.

I see Apple logo is gone, so v6.1 was successfully installed. But without disabler.kext, got panic on AppleIntelCPUPowerManagement.

No lucky for us, although I hope I can move forward 10.5.6 without issues.

Cheers

If your partition wasn't unmounted correctly, then you'll loose all of your data on it. It already happened to me
Basically you could just check if the partition is still mounted before calling rm.

@bladerunner: You are completely right about the root thing, I simply forgot. The fsck is a pretty nice idea as well, I am going to update my script!

- mcsmart

EDIT:
Already updated the script.

I just wish to express my thanks to munky for putting together this excellent guide.

Here's an overview of my AMD system and the files I used to get it working:

System specs:
Mainboard: K8T Neo2 v2.0 VIA K8T800 Pro + 8237R Plus Chipset Based
CPU: Athlon64 3200+ (supports SSE3)
RAM: 2GB DDR-400
Video: NVidia Geforce 7800GS 256MB (AGP)

Kernel Used: voodoo RC Using Voodoo Release 1 now (of course). LINK to release thread.

The Boot-132 ISO I used is named orig_boot-132.iso.

Additional Boot-132 files I used:
IONetworkingFamily.kext (from 10.5.2 Leo4All disk) to get my Realtek 8110C NIC working.
AppleVIAATA.kext (to avoid the "still waiting for root device..." problem)
System.kext (stock 10.5.5 version. It is required by the voodoo kernel to enable the USB hot-swapping functionality)

Other files:
I had originally included the AppleAC97Audio.kext file in my Boot-132 CD but it does not load at boot (this is a known issue).
The file has to be copied over to the /System/Library/Extensions/ folder of your Leo partition.

All files are attached to this post except for the kernel, which you can download from the dev's site.

I also wrote a little guide based on Sherry Haibara's discovery, that the slimbuild script was unable to create correctly working ISO images for AMD systems (the developer of slimbuild is working on a fix).
How to create a Boot-132 for AMD. (Thanks again for the help, Sherry).

Comments/Issues:
- I used the retail 10.5.4 DVD for the Leopard installation. I then started the "Software Update..." application from the OS X menu bar and everything worked perfectly.
- A few applications wouldn't run in 64bit mode, like the Samsung ML-2510 VISE-X based installer (VISE-X is not good, IMO).
- I am unable to use Sleep/Wake in 64bit at the moment but it could have something to do with my kext configuration.
- Video Injectors didn't work anymore, so I had to create an EFI string for my com.apple.Boot.plist file. Solution here.

Thank you, munky and all of the developers!! You have made a dream come true.


EDIT: Here's the thread with a collection of Boot-132 ISOs. LINK

Thank you, mcsmart. I LOVE your scripts.
It works flawlessly.

I should have mentioned this in my previous post. This section of your second script isn't needed because Munkys' update script already does it.



Also, the safest way to remove the directory is "rmdir /volumes/EFI". It will only function if the directory is empty.

Sorry for the oversight.

A better way to check if an operation actually did go okay, is to check the exit flags of the commands executed along the way. Using the above example, you could do (ok, I don't know why it's randomly indenting some of the code below):


If any of those commands fail, the end status will report that. Also very useful when calling unmount, which sometimes tends to fail (fseventsd?).

Further, to finally remove the /Volumes/EFI directory (I haven't checked the actual code) but I'm assuming "rm -rf" was called, hence clearing out someone's data (read above) when the unmount failed. A safer way to ensure only the empty directory and mount point is removed is to call "rmdir", instead. It will only succeed in removing an empty directory, which can be used together with umount and the error checking code above to report when a unmount has failed.

I see people talking about creating scripts so I thought I would add what I have done in case it helps anyone.

Awhile ago, I was also annoyed with mounting and unmounting my EFI partition. I also found it cumbersome to constantly use the terminal. So I created a simple Applescript application bundle that does the following:

Mounting:

Let you select an EFI partition if there are multiple partitions found on your computer.
Make the EFI volume directory.
Mount the partition.
Set all the permissions so that it can be edited by the user.
Open the folder in Finder for easy editing (also shows in the side bar).

Unmounting:

Run the update script (which also resets the permissions).
Unmount.
Ask for a force unmount if necessary.
Use "rmdir" to remove EFI directory.
Ask if you want to reboot.

This script was really only created for my own person use. It is not very fancy and there probably is not as much error handling as there should be. Although, I use it all the time and don't have many problems with it.

Feel free to use it, edit it, incorporate it, completely hack it up, or whatever you want. I just thought I would post it to help out.

DISCLAIMER: I take no responsibility for anything this script may do to your system! As with all scripts, look at the code before running it; and use at your own risk!

Here is the Applescript application bundle: Click to view attachment
Here is the Applescript text file: Click to view attachment

Nice job guys. We should ask munky to update the tutorial to use the scripts. Those will make things much easier and quicker for everyone.

great koen
but i have a problem with your Mounter after third time opening it he gives an error which makes no snense
maximal 3 tasten zulässig
which means
only 3 butoons allowed
????

Hmm... I can't say I have ever seen that. It is scripted to create a new button on the dialog for every EFI partition it finds. It might be that there is a max of 3 buttons allowed on the dialog box. Do you happen to have more than three GPT drives on your computer?

I have never had more than three GPT drives connected at one time, so I never noticed it.

Edit: I just tested it and that is the problem. The script will not work (without editing) if you have more than three GPT drives on your computer.

This is exactly the reason why you guys should stick to munky's fairly simple to follow procedure instead of wasting your time with some scripts. No disrespect to the authors of the scripts.

If you don't wan't to put the most minimal of efforts into this and expect to be spoon fed every time, you will remain a noob forever and have no idea of what you are actually doing and run into troubles time and time again.

Just my 2 cents.

I have to agree... These scripts are really not for noobs, they are just to help out with the repetitive tasks of mounting and unmounting. You should be familiar with doing these tasks manually before using any of these scripts.

If I had more time, I would've spruced it up a bit and added more comments and error handling to make it suitable for people that are unfamiliar with the process.

i did it manualy several times before.
I am now in a stage of testng lots of kexts, so a script like yours would be very helpfull.
I have 3 GPT drives plus a USB HD, but i think i have to restart.....
Are there any files in the App Support folder or something like this to delete/clean reinstall ( i think not).

But back to topic, munkys method works.
But i only use Appledecrypt.kext and a realtekr1000.kext also a DSDT.aml and a com.apple.boot.plist with 8800GT EFI strings.
All on 10.5.5
It seems to work but he shows my internal drives as externals.
When i try to add a AHCIPort.kext to my used kexts, he will not start anymore, same with JMicron.kext and several other kexts.
What did you guys do to show internal drives as internal?
What kext sholud i use else?
OHR.kext?
any bluetooh kext for my BT stick?
Jmicron for SATA HD on purple Jmicron Port?
P35 DS.4 Rev. bios f13 8800GT Q6600

If I can find some time, I might change the script to get rid of the limitation.


You can try the IOAHCIBlockStorageiconfix.kext that can be found in a post from atka here. It worked well for me.

hey, thanks for all the mad props

zef - great to hear from you... will be glad when new chameleon is unleashed and i dont have to maintain this booter anymore

You can fix the script like this - get rid of the buttons and use a list. Maybe like the example below.

Howdo you test.
DSDT file is load????

You dont have to fix the EFI Mounter, it was just my USB which was the 4th device, but the Mounter App also hangs after disconnecting the USB Drive!
This is a bit tricky, but who cares, GREAT APP, thanks a lot you saved my day.

For the drive problem i found a LegacyIOAHCIBlockStorage.kext

I patched my DSDT.aml wit the "885" Method, and it works with my P35 DS4 Rev.1 F13 Bios, Mic out is the line Out, but who cares.

The kext i am using now
LegacyIOAHCIBlockStorage.kext
Appledecrypt.kext
LegacyApplePIIIXATA.kext (but dont have any IDE, do i need?)
OHR.kext (do i need, will test.....)
RealtekR1000.kext (hmm, seems to be better)

Thanks to all you guys who this possible, never had such nich HackMac !

Yup! That'll work perfectly. Thanks!

Applescript application bundle: Click to view attachment
Applescript text file: Click to view attachment

Hey you guys,

I was wondering if anybody here has been able to replace the modified bootloader from this tutorial with the new EFIv9 bootloader from netkas. I copied it in the root folder of my EFI partition, but the computer just gets into a restart loop.

Thanks,

- hecker

Your Method is really Great.
My Harddisk is faster then it ever was before.
Xbench gave a plus of 50% now he have a about 80 score, before he had 50 !
I only use LegacyIOAHCIBlockStorage.kext

Everybody who have problems running 10.5.5, be sure you have working com.apple.boot.plist for your Graficcard in you EFI dir !

What made it go so much faster?? Using Munky's method in general or something else??

Hi,

Simple, now i can make boot w AppleIntelCPUPower...kext and in PCI CArd in system profile is showed my PCI devices

When booting it still says Darwin bootloader 5,0 ????

Have no idea weither it works

hum, I'm stumped.
Each time I try to create mkdir: /Volumes/EFI/.fseventsd is says file exists. and when i try
touch /Volumes/EFI/.fseventsd/no_log it says permission denied

Any help is welcome

Just to be sure, you are running the commands as root. Ccorrect? And, you have done a "ls -al " command to check the permissions on the .fseventsd directory. Correct?

Ok. Sorry about that, works better when logged in as root. This is great

Extensions not loading; I've read through a lot of comments but didn't find an answer for this. I'm able to install from the Retail DVD and get it to boot. But, none of the extensions are loading.
1. Do I put the whole package (after it's unzipped) into that folder? Or just parts of it?

If anyone can help me, I would appreciate it.

thanks

charlie

What do you mean "none of the extensions are loading"? What package are you talking about unzipping?

If you mean none of your extra/modified extensions are loading I find that hard to believe. Some of them, at least the decrypter, must be loading or the system would panic. If by package you are referring to the EFI partition boot package from the first post, the instructions in that same post tell you where to put everything.

Could you be more specific about what you have done and what is not working?

hello I have a question:

I'm actually dual booting vista and retail leopard on gpt using chameleon and the chain0 method (dunno if this worked for anybody else...). I made a mess with the leopard install when patching applehda and now I have to reinstall it. Is there any way to dual boot as I'm doing (with chain0) but using this efi partition?

Well, it works for me...

Asus striker Extreme (nforce680i),
Core2quad Q6600,
realtek gigabit pci-card
PNY Quadro FX 3500 (EFI string in boot.plist on EFI partition)

Kernel: voodoo final release 1
Kexts on EFI:
- AppleNforceATA (version 1.0.3 I think)
- SMBIOSenabler
- dsmos.kext
- CPUPMdisabler.kext (i could leave this out because kernel has extension-blocking feature)
using latest version of bootloader partition from first post, and always carefully following the steps given in howto.


Boot partition is a vannilla 10.5.4 install updated with delta updater to 10.5.5

I only have 2 problems left:
1: BIG PROBLEM:
I've got a PNY Quadro FX 3500, and i'm using it with an EFI-string in boot.plist on the EFI-partition. (CI/QE works like a charm)
But, but when doing some copying over the network my mouse starts stuttering, beachball appaears, and the screen freezes (the first couple of seconds i can still move the mouse, but within 10 seconds it becomes uncontrollable)
log always says: VChannel(GL): Graphics channel timeout! or VChannel(GL): Graphics channel exeption!
(I also get these errors with drop-in releases (except for iAtkos v4i, but had no succes with using kexts from that install), but after days of searching for a solution and trying everything possible I'm asking here.) Maybe someone has got an idea.

2. smaller problem:
can't get my audio (AD1988B) to work from efi-partition. used different appleHDA versions&patchers and Azalia kexts, to no avail.
Any howto on creating my own efi-string or patched appleHDA, search didn't help me much.

edit: regarding audio, i found some useful info in here: http://forum.insanelymac.com/index.php?sho...7819&st=100

I started trying to get a good install since 10.5.0 was released, but always got the graphics channel problem.
Don't need step by step help, just a direction where to look for solutions.

any help greatly appreciated!

This all looks great, thanks to all involved!, but I'm a bit new to this sort of hacking, so will wait for the new chameleon release...

I have a question tho: Can I convert my existing smooth running Kalyway based install to boot using this method? Or is a new install really required?

Yes I realise that I would then have some modified kexts in my system folder as well as on the EFI partition, the way I see it, if i can set this running to boot from EFI partition, then copy my modified kexts from my system to the efi partition, then I can update normally using system update, and my system will gradually revert to vanilla, while the modified stuff remains on the EFI partition.

Please let me know if I've misunderstood, or anything that would help me achieve this..

I'm already running an almost vanilla system,core2quad cpu P5W mob, just minimal additions for gfx card and using the darwin bootloader as per kalyway install..

EDIT: so reading thru the instructions again it seems the main reason that it is best practice to do a clean install is to make sure there are no other bootloaders on the disk.

If I were to do the install by copying my current system from another disk, using superduper, onto a recently repartitioned disk would that work to ensure that no bootloader is installed? and the go ahead as per the instructions?

alternatively, how could I delete the darwin bootloader currently being used by my kalyway install before going ahead with this project?

If you have another HD you can install to, you can do the install from within kalyway. I used a iDeneb install to do a retail install. Then went from the instructions from there. Worked so good that I got rid of iDeneb and now am using my EFI/Retail install only! The only non-vanilla kext i have in s/l/e is my kext for audio (targua patched hda).

I really don't understand bootloaders enought to have confidence in what I'm doing... since they seem to be the definitive difference between a hack and a real mac I'd like to read up on it.

is there a guide anywhere which explains what each stage0 stage1 stage2 etc bootloader does, where it is located, if its scope is disk wide or partition specific, how to delete or replace them etc etc??

BTW why does the audio kext have to be in s/l/e, why can it not load from the EFI partition like other modified kexts?

To find out about boot-loaders, do a google search for Chameleon or DFE 132. I haven't searched myself, but I am sure what you are looking for is out there. I have a basic understanding of how boot-loaders work, I don't want to give out any bad info, so see what you can come up with, with google. Someone may chime in and be able to provide details that I can't. As far as I am able to figure out, the audio kexts require other kexts that are not loaded till after the EFI partition hands off to the main for boot (I am sure I am overly simplifying it). I have seen that some are able to do "plist only" audio kexts in their EFI/Extensions, but I am not one of the lucky ones that have figured that out. 1 non-vanilla kext in my s/l/e is not bad in my book. Hope this helps somewhat...

Thanks =)

Hey you guys,

after reinstalling OS X from scratch (due to a damaged partition table) I am no longer able to boot from my EFI partition. Booting from the Boot-132 CD still works fine, though.

My current system disk is "disk3s2" and my EFI partition is "disk3s1". I re-created it according to munky's description and copied the kexts and kernel (voodoo) from my backup up EFI folder.
When I enter the following at the darwin prompt (my boot device is shown correctly as (0,2) Leopard):
I can see some files being loaded and then it stops and shows a bunch of "Property" fields (please see attachment).

I have tried entering bt(0,1), bt(2,0), bt(3,0) and a bunch of other combinations but the thing just refuses to boot simply reloading the darwin boot prompt.

Could someone please clarify what the "bt" parameter actually stands for?
Any suggestions are welcome.

Thanks,

- hecker

PS: My previous disk (although it's still the same physical unit) was labeled disk2 (thus disk2s2 and disk2s1 were my Leo and EFI partitions).

FIXED/SOLUTION: Just in case you run into this problem which apparently no-one here knew about: The problem was caused by a corrupt com.apple.Boot.plist file in the EFI boot partition. Replacing it with the system's boot file fixed it.

I used this method today to allow my Acer Aspire One to boot the retail install DVD off an external hard drive - saved me so much time!
Just shows how flexible this method can be though

Thanks again!

Boot with your boot132 CD instead and then reinstall EFI partition with bootloader and put your kexts in.

Yes, thanks. I already did that, as you can see in my previous post.

I guess the drive might still have some sort of weird partition table problem. I'll try re-partitioning it again tomorrow.

Make sure it's set to active.

first off, i doff my cap to mucky and everyone else who has worked on this. this is a brilliant solution that i;m really enjoying testing.

once slight prob tho. since i've started testing this method i've been looking into SMBios options that allow me to use Apple's vanilla SMBios. up untill now i've used netkas's SMBios. problem is, no matter which one i use, "about This Mac" crashes. is there a kext that affects this that i'm missing? i thought it was just the SMBios.

this is what i'm using in my extensions folder on my EFI partition so far.

I highly recommend using AppleSMBIOSEFI.kext attached, I don't remember what forum entry or version it is, But it solved the issue for me.

let me know if it Helps you as well.

HBP

lol, forgot to Add the File, sry about that

the next version of chameleon (coming soon!) will have SMBIOS enabling support built right in, along with DSDT patching and of course EFI partition booting.

cheers HBP, gonna check that out shortly.

munky, brilliant, that's great to hear.