Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
can't find boot. file

I can't find the usr/standalone part.
Can anyone help me out?

Furthermore; for steps 3 and 4 I need Flat Package Editor, don't I?
 
I've tried that but the files are still locked. How do I unlock them?

Luckily, if you do run into problems with a file that cannot be edited, either in the Terminal or in the Finder, you can unlock it by performing the following steps using the Terminal:
1. Open the Terminal.
2. Type the following command, followed by a single space (do not press enter yet).
sudo chflags nouchg
3. Drag the locked file from the Finder to the Terminal window to complete its full folder path.
4. Press Enter to run the command, supplying your password when prompted.
When run, this command will undo the lock flag for the file, regardless of whether you own the file.
 
Where to find board_id

I can't find any info about a board-id. Where should i find it? My install program doesn't run on my target mac, that's why I have to put it in manually

I successfully installed on MacMini2,1 and MacPro1,1.
this is great I made a small app to automate all this.

Tiamo's did a super great Job

Just input your board_id, your model and the USB key to use and click.
fully automated or step by step. you can even then patch "again" the key to add other computer Boards.
works great. was a personnal challenge to code and as it works fine I though I'd post it in here.

Tiamo thanks again.

If any of you are interested : go there http://oemden.com/?p=556
I've called this little app (shell script bundled in an Applescript App)
SFOTT aka Sixty Four On Thirty Two.

Enjoy as I did.


This is an ongoing Work, but I've tested again and again and it works OK.
 
I can't find any info about a board-id. Where should i find it? My install program doesn't run on my target mac, that's why I have to put it in manually

On the Mac you want to install mavericks onto.
Copy and paste the following into Terminal then press enter:-

Code:
ioreg -lp IOService | grep board-id
 
Luckily, if you do run into problems with a file that cannot be edited, either in the Terminal or in the Finder, you can unlock it by performing the following steps using the Terminal:
1. Open the Terminal.
2. Type the following command, followed by a single space (do not press enter yet).
sudo chflags nouchg
3. Drag the locked file from the Finder to the Terminal window to complete its full folder path.
4. Press Enter to run the command, supplying your password when prompted.
When run, this command will undo the lock flag for the file, regardless of whether you own the file.

Okay I was able to unlock one of the boot.efi files. Thanks to EJDwyer instructions. But I can't find the other one that needs to be replaced: usr/standalone/i386/boot.efi .Where is this located?
 
Okay I was able to unlock one of the boot.efi files. Thanks to EJDwyer instructions. But I can't find the other one that needs to be replaced: usr/standalone/i386/boot.efi .Where is this located?

It's located in /usr/standalone/i386/, which is hidden by default. In a Finder window, enter Command-Shift-G and enter the path indicated. Then replace boot.efi as necessary.
 
It's located in /usr/standalone/i386/, which is hidden by default. In a Finder window, enter Command-Shift-G and enter the path indicated. Then replace boot.efi as necessary.

Was not able to get into /usr/standalone/i386/ using the Command-Shift-G method. I used a FTP program I have called, Transmit to show hidden files. I found that there was no boot.efi file inside the “i386” folder, so I just dragged Tiamo's boot.efi into it and I was able to boot into Maverick on my Mac Pro 1,1. It seems to be running fine right now. I'll have to put it through some paces the next few days.

Thank you everybody for your help!

-Russ
 
Last edited:
I got OSX 10.9.1 running on my Mac Pro 1,1 (flashed to 2,1) with the crappy 7300GT card. Graphics are glitchy and plain terrible, so I booted back on to my main HD with Lion. Gotta get a 5770 sometime
 
I already had the 5770 cards and so far it's fine.

What is with "(flashed to 2,1)"? Is that something that has to be done if you have the 7300GT card? Or is it done for another reason?


I got OSX 10.9.1 running on my Mac Pro 1,1 (flashed to 2,1) with the crappy 7300GT card. Graphics are glitchy and plain terrible, so I booted back on to my main HD with Lion. Gotta get a 5770 sometime
 
I already had the 5770 cards and so far it's fine.

What is with "(flashed to 2,1)"? Is that something that has to be done if you have the 7300GT card? Or is it done for another reason?

Flashing a Mac Pro's logic board's firmware to 2,1 simply allows the system to recognize more CPUs like Intel's X5365 Xeon used in the Mac Pro 2,1! Both the 2,1 and 1,1 are identical, but the 2,1 has the 2,1 firmware to recognize the quad core CPUs.
 
can't get it to work (still)

[edited for posting in wrong thread. apologies]
 
Last edited:
Flashing a Mac Pro's logic board's firmware to 2,1 simply allows the system to recognize more CPUs like Intel's X5365 Xeon used in the Mac Pro 2,1! Both the 2,1 and 1,1 are identical, but the 2,1 has the 2,1 firmware to recognize the quad core CPUs.

I was thinking of changing out the CPU's in my Mac Pro 1,1 to something like the X5365 Xeon chips. I would need a matching pair. Do you know the best place to buy them? And then do you have instructions on how to the flash logic board to 2,1? I'm just trying to get a few more years out of my Mac.

Thanks, -Russ
 
Flashing a Mac Pro's logic board's firmware to 2,1 simply allows the system to recognize more CPUs like Intel's X5365 Xeon used in the Mac Pro 2,1! Both the 2,1 and 1,1 are identical, but the 2,1 has the 2,1 firmware to recognize the quad core CPUs.

I didn't do this when I added a pair of quad core Xeons to my MacPro 1,1. As far as I can see I have no issues with using the Xeons, i.e. eight cores seem to be used when using Handbrake etc.

What does flashing involve? Is it a big job? How can I tell its been done? Should I even care :)

Thanks,

Rob.
 
Do you know the best place to buy them?

Ebay.

And then do you have instructions on how to the flash logic board to 2,1?

http://forum.netkas.org/index.php/topic,1094.0.html (login approval required)

What does flashing involve? Is it a big job? How can I tell its been done?

Running a small program and rebooting the computer. No, it's just as big as any firmware update - run, enter password, reboot, wait a minute or two, reboot again, pronto. System Profiler should display "Model Identifier: macpro2,1" afterwards, instead of 1,1 you currently have.
 
Questions before installing

I have a mac 2,1 with an appropriate graphics card. I was working along fine until I got to the part about editing the OSInstall.mpkg with the flat package editor, which I can not obtain or find in my current XCode.

On post 28 in this forum there is a guide with some tools (including a working OSInstall.mpkg which I currently do not have.) but in the read me it says Ram may be limited to 4GB. Is this true?

If it's not true how can I edit OSInstall.mpkg so I can finish trying the installation.


Dan
 
Thanks to all the great information in this thread, I'm able to get a boot on my 2,1 and the installer runs fine, but dies in about 15 minutes trying to install the Essentials.pkg. I'm using the newest version of the Mavericks installer. I opened the package in Pacifist and got the following summary:

Package report for package Essentials.pkg on Wednesday, January 1, 2014 at 1:10:14 PM Eastern Standard Time

285940 files were scanned.

285625 of 285940 files were present on the hard disk.

0 of 285940 files had a file size of zero although a nonzero size was specified in the package.

1713 of 285940 files had file permissions that did not match those specified in the package.

1545 of 285940 files had checksums that did not match those specified in the package.

Anyone else encountered this? I've built an image from two separate downloads (both of which were able to install on my MacBook without a problem) and gotten the same result both times.

EDIT:
Fifth time must have been a charm, because it installed over my Lion and works just fine (except for X1900, but working on that). Don't know what I did differently.
 
Last edited:
my big thanks to tiamo and rastafabi for their incredible valuable efforts. I am running now 10.9.1 on my MacPro 1,1 with a AMD Radeon HD7750 1GB DDR5 just fine :)

However, some issues remain:

I still face some problems with my USB ports as they will not recognize all my USB devices (be it a USB thumbdrive, mouse or HDD). Some generic mouse works just fine, as well as my FireWire.

The most annoying part ATM is that neither my WiFi nor my BT is recognized. Does anybody know a workaround for that? I tried to use the Airport Utility 5.6.1 as some other users already reported problems after upgrading to Mavericks but it did not help at all? Are there any additional kext files I have to install and if yes how to proceed?

Thanks in advance!

eyseman
 
You are right, however most of the under the hood changes aren't clearly visible to an average end user, "it just works" (even though it works better than before). On the contrary, the cloud features are a highlight of current Apple technology that is readily available to anyone - the more iCloud-enabled devices one has got, the better. I do adore the new memory management and OpenCL integration, but I am quite sure my dad wouldn't even notice :)
OK, this is so off-topic. Let's get back to the topic now.

Just before we do get back to the topic. A lot of businesses and clients will not permit syncing their info to other peoples servers, (even though in reality I think it happens whether they like it or not), which makes it a deal breaker if you use the calendar on your iPhone for your work. There are a couple of workarounds involving Server.app if you are so inclined.
 
Finally got it to work with Tdm. I just installed mavericks into an external, swapped the efis. No need for USB. Thanks to tiamo. I suggest he make a video tutorial for this and run it on a twitch channel so people can subscribe and make some payment. It's much easier to do this than paypal.

I also have it running with a PC stock 660. Not sure if it is worth flashing just to get the boot screen. It is performing better than the old 4870 but maybe there is a PCI bottleneck.
 
I'm using the original Bluetooth and WiFi cards which shipped with my Mac Pro 1,1 (2006), and haven't had any sleep issues so far.

can you please tell me if you used any additional kext files or similar as my airport extreme card within my MacPro 1,1 is not working anymore under 10.9.1. I had no problems under 10.6.8 before.

thx!

cheers
eyseman
 
my airport extreme card within my MacPro 1,1 is not working anymore under 10.9.1. I had no problems under 10.6.8 before.
I remember there was a firmware update for AirPort in Mac Pro to support 802.11n. Did you apply it back then? Check supported PHY-modes in System Profiler.
 
Last edited:
iMessage not working

I was able to convert my Mac Pro 2,1 (upgraded from a 1,1 with 2x Xeon 4core @3GHz) with an ATI4870 from a Chameleon boot without much of a problem. All I had to do was switch the boot.efi and plists. I am running 10.9.2

However, I lost iMessage functionality. It stores a token in NVRAM and I get an error related to that, when signing in. This was at times a problem with Chameleon, too. But the latest version 10.9.2 fixed it.

Does iMessage work for anybody else?

Not using Chameleon not only improves the boot process, but makes switching between different OS versions a lot easier.

I can switch back to Chameleon easily without any changes, but it also lost iMessage due to the token issue.

-- Harald
 
However, I lost iMessage functionality. It stores a token in NVRAM and I get an error related to that, when signing in. This was at times a problem with Chameleon, too. But the latest version 10.9.2 fixed it.

Does iMessage work for anybody else?

The error msg is:
Your Apple ID " >>> " can't be used to set up iMessage at this time.

...

Customer code: ...-...-...
 
use this one if you prefer graph mode.

PS: system update may overwrite boot.efi, you should replace it after system update.

PS2: the bootloader is dedicated to 10.9, it DOSE NOT support 10.7's kernel, because 10.8+ kernel use a new version boot_arg. AND it will bypass drvier cache(mkext) in 10.8, because 10.9 does not use driver cache, please make sure kernel cache is always enabled if you want use it in 10.8. AND in 10.8 the bootloader will ALWAYS load 64bits kernel(the only one 10.9 has) even if you set arch=i386 in boot_args or press 32 on startup.

This post had a "graphics mode" boot.efi attached, but it reverts to the verbose debug mode. I have cleared NVRAM args to no avail. Is there anything else I need to do to avoid verbose mode?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.