Tiamo deserves many props for his work. Previously I was using Chameleon to run Mavericks on my Mac Pro 1,1 and now I'm using his custom boot loader. To put it simply, running Mavericks on this unsupported machine went from feeling like a hack job to as if Apple had never left us behind. He just proved that a 32 bit EFI system can boot Mavericks gracefully and the fact that Apple didn't do this is indeed sad.
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
[Guide] Installing 10.9 Mavericks on older Macs. -HackerWayne
- Thread starter hackerwayne
- Start date
- Sort by reaction score
Tiamo deserves many props for his work. Previously I was using Chameleon to run Mavericks on my Mac Pro 1,1 and now I'm using his custom boot loader. To put it simply, running Mavericks on this unsupported machine went from feeling like a hack job to as if Apple had never left us behind. He just proved that a 32 bit EFI system can boot Mavericks gracefully and the fact that Apple didn't do this is indeed sad.
Was this a completely new installation or did you modified the previous chameleon installation? Could you detail the steps you took to do this? I currently have Maverick running on my Mac Pro 1,1 using chameleon. My preference would be to modify my current install.
I merely took the boot.efi file and replaced the ones in my then Chameleon/Mavericks install. The easiest way to do this without going to the Terminal to modify ownership is to log into the root account. From your current account logout and at the prompt choose Other. For the account name put 'root' and for the password use your admin account password that was used to install OS X. You should now be logged into the root account and staring at the default Mavericks desktop. At this point download the boot.zip file attached to tiamo's post. Open /System/Library/CoreServices and get info on the boot.efi already there. Deselect the Locked option so that you can move the file to the trash. While holding down the Option key drag the new boot.efi to the CoreServices folder. Get info on it again and re-enable the lock. Now, in the Finder open the Go menu at top and select Go to Folder. Type in /usr/standalone/i386 and hit return. Delete the boot.efi in this folder and copy over the one you downloaded. Run permissions repair in Disk Utility just to be thorough. At this point you're ready to switch back to native EFI boot. Reboot and hold down the Option key the second you hear the boot chime. Select whatever you named your Mavericks install as the boot disk. The screen will go black and you will see white text scrolling down the screen, this is verbose mode, get used to it. Once you're back at your desktop you can feel confident that it worked. Something to be aware of is that Chameleon is still present, just no longer used. To keep it this way open System Preferences->Startup Disk to set Mavericks as your default boot disk. What you do with your Chameleon partition is up to you.
Treksdot, I'm sorry but I'm a newbie. I didn't understand the how to log into the root account. In the desktop, when I logout, I see my main account and the guest account. I don't see a choice of other, what am I doing wrong? What prompt are you referring too? Thanks
I'm currently booted into Windows so I can't list the exact steps right now. What you need to do is open System Preferences and goto Users & Groups. Either there or under Login Options you should see an option to enable Other. If you still don't see it then just set the login window to display name & password under Login Options. Hope that helps.
It is easy in terminal to unlock the file:
to lock it
just drag the boot.efi file in the CoreServices folder in place of the 'PATH TO FILE'
Code:
sudo chflags nouchg 'PATH TO FILE'to lock it
Code:
sudo chflags uchg 'PATH TO FILE'just drag the boot.efi file in the CoreServices folder in place of the 'PATH TO FILE'
Ok, I tried it and I can't tell if the system is booting on the new efi or its using chameleon. After the chimes I picked my maverick drive rather than the Windows (chameleon boot drive) boot drive. The booting process looked identical to my chameleon. System Report also reads identical to chameleon. The only thing I haven't tried is changing the default starting drive in system preferences. Is there anything i can check to verify that I did this right? Even my hardware UUID is the same as in Chameleon (which is not the same that show when I boot in to Lion directly (apple's efi32).
Ok, I tried it and I can't tell if the system is booting on the new efi or its using chameleon. After the chimes I picked my maverick drive rather than the Windows (chameleon boot drive) boot drive. The booting process looked identical to my chameleon. System Report also reads identical to chameleon. The only thing I haven't tried is changing the default starting drive in system preferences. Is there anything i can check to verify that I did this right? Even my hardware UUID is the same as in Chameleon (which is not the same that show when I boot in to Lion directly (apple's efi32).
You could try blessing your chameleon drive/partition. If you are booted using chameleon then you would get this error "Legacy mode not supported on this system".
Are you holding option when booting into Chameleon? You don't need to but it seems that many people on here do for some reason. If you are booting in EFI mode then you should never see Chameleon. It would look just like you are booting 32bit Lion in Verbose mode.
Last edited:
Ok, I tried it and I can't tell if the system is booting on the new efi or its using chameleon. After the chimes I picked my maverick drive rather than the Windows (chameleon boot drive) boot drive. The booting process looked identical to my chameleon. System Report also reads identical to chameleon. The only thing I haven't tried is changing the default starting drive in system preferences. Is there anything i can check to verify that I did this right? Even my hardware UUID is the same as in Chameleon (which is not the same that show when I boot in to Lion directly (apple's efi32).
Your drive is formatted as MBR isn't it? If so then OS X can't boot from it natively. What's happening is the boot loader can't find anything to boot when you point it at your Mavericks install and so it is switching to the next thing it can find, Chameleon.
Bless appears to work - didn't get the error message
this is what I see in terminal
--------------------------------------------------------------------
Last login: Sun Nov 24 22:39:02 on console
michael-j-saiss-mac-pro:~ mjsais$ sudo bless --folder /Volumes/BOOT --file /Volumes/BOOT/boot --setBoot
WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.
To proceed, enter your password, or type Ctrl-C to abort.
Password:
michael-j-saiss-mac-pro:~ mjsais$ sudo bless --folder /Volumes/BOOT --file /Volumes/BOOT/boot --setBoot
michael-j-saiss-mac-pro:~ mjsais$
this is what I see in terminal
--------------------------------------------------------------------
Last login: Sun Nov 24 22:39:02 on console
michael-j-saiss-mac-pro:~ mjsais$ sudo bless --folder /Volumes/BOOT --file /Volumes/BOOT/boot --setBoot
WARNING: Improper use of the sudo command could lead to data loss
or the deletion of important system files. Please double-check your
typing when using sudo. Type "man sudo" for more information.
To proceed, enter your password, or type Ctrl-C to abort.
Password:
michael-j-saiss-mac-pro:~ mjsais$ sudo bless --folder /Volumes/BOOT --file /Volumes/BOOT/boot --setBoot
michael-j-saiss-mac-pro:~ mjsais$
Verify the disk then. Pop open Terminal and post the results of the following command:
Code:
bless -info /Volumes/Mountain\ Lion----------
The error comes up when using the -legacy flag with -setBoot.
Last edited:
run this:
sudo bless -folder /Volumes/BOOT -file /Volumes/BOOT/boot -setBoot -legacy
You dont have the legacy tag at the end.
Booting my cloned Mavericks install worked great with the new boot.efi file. I do like having a GUI to be able to choose a startup disc from on boot though by using Chameleon. Those of us with non-flashed PC Cards can't hold option and choose.
I have had some issues with the Chameleon install though. Parallels 9 won't let you install an OS X vm when booted in Mavericks using chameleon. Also can't enable AHCI mode for Windows in boot camp when using Chameleon.
I have had some issues with the Chameleon install though. Parallels 9 won't let you install an OS X vm when booted in Mavericks using chameleon. Also can't enable AHCI mode for Windows in boot camp when using Chameleon.
It may work with Clover, which has a 32bit efi mod which boots natively on macs (at least older versions). I can put up a guide if someone is interested. Actually it's quiet easy, but still different from chameleon. - The advancement would be a much shorter boot time (with the new boot.efi by tiamo).
I currently got less than 15 seconds with a FusionDrive build with a SATA 1 and a PATA (alias IDE) drive.
I'm going to play around more with this new efi boot option some more. I survived a long time booting back and forth between OS X and Windows without a boot screen. Boot Champ (a small program that sits in the menu bar) makes it quick and easy to select the Windows drive and then when in Windows just reboot and it goes back to OS X.
Alright, I've done everything. No matter what, it keeps stalling at "Still waiting for
" and all that, which it repeats every 1 or so minutes. I followed the instructions to the letter, and replaced the OSInstall with the "hacked" one from the link, and everything else is as instructed.
What is not occurring? I'm running a 1,1 Mac Pro, will try updating it to a 2,1.
Aggravated beyond belief; don't know how you all got it work; does NOT work, not for me.
What is not occurring? I'm running a 1,1 Mac Pro, will try updating it to a 2,1.
Aggravated beyond belief; don't know how you all got it work; does NOT work, not for me.
I once had this issue, too. I started from scratch and "suddenly" it worked. If you are using the guide I've posted (better refer to this link) than be sure you restore the BaseSystem.dmg to the partition you created and not to the drive (as one user pointed out - sorry, don't find who). Also you might be more successful using another drive as OS X seems too be very fastidious some times.
Good luck!
Here you will find the boot.efi mentioned in the linked post.
EDIT: And please do not double post...
***Before starting allover again you might try running those commands (edit them as needed).
Code:
sudo chown -R 0:0 /Volumes/{Your\ Install\ Drive}/System/Library/Extensions
sudo chmod -R 755 /Volumes/{Your\ Install\ Drive}/System/Library/Extensions
Last edited:
Weird - but I simply cannot get this to work. I copied over the boot.efi files in /System/Library/Core Services and /usr/standalone/i386, set the permissions manually (also ran repair permissions just to be safe), no dice.
Blessed the drive, nope.
Unblessed chameleon, nada.
Even tried pulling out all my other drives and just left the drive containing the mavericks install - "No bootable device found".
I expected this to be a piece of cake. Especially when it seems to have been effortless for everyone else. Nothing has worked - not even close. Back to Chameleon for now unless I can figure out what's wrong.
Blessed the drive, nope.
Unblessed chameleon, nada.
Even tried pulling out all my other drives and just left the drive containing the mavericks install - "No bootable device found".
I expected this to be a piece of cake. Especially when it seems to have been effortless for everyone else. Nothing has worked - not even close. Back to Chameleon for now unless I can figure out what's wrong.
Last edited: