Resolved 2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite

[Hennesie2000]

BREAKING NEWS / UPDATE from Pike:



Good news. I remembered something from like five months ago. Yes. I already figured this out but I forgot about this change. Luckily some part of my brain recalled it and that was when I asked Mikeboss – a great help by the way – to backup: /com.apple.recovery.com/kernelcache and to copy: /System/Library/Caches/com.apple.kext.com/Startup/kernelcache over it. BOOM. A successful boot from his Yosemite Recovery HD!



In other words. The missing 28 bytes (mach_header) at the start of the kernelcache, which was removed by Apple in BaseSystem.dmg and the one on the Recovery HD. No idea why Apple did this, but it is likely to break most boot loaders. With a few exceptions. And that ladies and gents was why the load routine in macosxbootloader is failing.



A fix to remedy this problem is being worked on and should soon be available.



https://pikeralpha.wordpress.com/2014/10/17/recover-hd-booting-with-macosxbootloader/

This is great news!!

 

[galletti1]

fwiw, I think the xar option for editing the Distribution file is an easier (and faster) solution than FPE.

Hi Morpheo. Can you point me in the direction of that method. I can't get FPE to run "because the identity of the developer cannot be confirmed."

 

[varsis]

Hi Morpheo. Can you point me in the direction of that method. I can't get FPE to run "because the identity of the developer cannot be confirmed."

Go to system preferences > privacy and here you can. Accept a single item or allow all. Non MAS items

 

[cwarren]

This might only be a Logitech issue. See if you can find out if this is an issue on supported systems. My Trittin AX Pro headset that uses a USB mic works fine for calls.

Seems it is not restricted to Logitech and is a Yosemite bug: https://discussions.apple.com/thread/6602025

 

[Hennesie2000]

Seems it is not restricted to Logitech and is a Yosemite bug: https://discussions.apple.com/thread/6602025

Ok, but at least we know it has nothing to do with the boot.efi because those are all experiencing the issue on supported Macs.

 

[atvusr]

fwiw, I think the xar option for editing the Distribution file is an easier (and faster) solution than FPE.

Can you point me in the direction of that method. I can't get FPE to run "because the identity of the developer cannot be confirmed."

Editing of the OSInstall.mpkg via Terminal - see Post #863.

 

[MrGame]

Kernel Panic

Hey guys,

I bought a Mac Pro 1.1 in January, but I still have a problem with several freezes/ hang ups by using OSX Mavericks or Yosemite.

If the machine has a cold start or was in standby, it sometimes just freeze.
There is no log about this freeze, but with verbose kernel option there is a kernel panic on the screen (see this link).
The Mac was checked by the seller (they have done AHT and testet the standby etc.). But they told me that there was no problem at testing.
Well, they tested the machine with 10.6 and 10.7. So I think the problem seems to be related to the using of Mavericks/Yosemite.
For Mavericks I have used tiamos boot.efi, for Yosemite I am using pika alphas boot.efi (by the way: great work ! thanks a lot for this !).
The installation went well in booth cases. I think it is maybe a hardware fault (because of the machine check), but the machine was testet in so many ways...

The Mac was sold with a flashed pc graphics card (well, they did not tell me this fact at selling). The RAM seems to be some deposits they had lying around (3 different manufactures, different timings and different speeds. see this link for details).

So here are the facts about this machine:

Model Name: Mac Pro
Model Type: 8-core
Model Identifier: MacPro2,1
Board Identifier: Mac-F4208DC8
Processor Name: Quad-Core Intel Xeon CPU X5355
Processor Model: Clovertown
Processor Speed: 2.66 GHz
Number of Processors: 2
Total Number of Cores: 8
Memory Size: 10 GB 667 MHz DDR2 FB-DIMM
Graphics Model: ATI Radeon HD 4870 1024 MB
Assembled in: Cork, Ireland
Manufactured during: November 2007
L1 Cache: 64 KB
L2 Cache: 8 MB (per CPU)
L3 Cache: -
Processor Bitrate: 64 bit
EFI Bitrate: 64 bit
Kernel Bitrate: 64 bit
Bus Speed: 1.33 GHz
Boot ROM Version: MP21.007F.B06
System SMC Version: 1.7f10
Power Source: AC Power.
Minimum Supported Operating System: Mac OS X 10.4.9 Build 8P4037 (Tiger)
Current Boot Operating System: OS X 10.10.0 Build 14A388a (Yosemite)
Maximum Supported Operating System: Mac OS X 10.7.5 Build 11G63 (Lion)

Many thanks in advance !
Chris

 

[ilegal31]

Hello gents,


I just realised that the person that had installed OS X Yosemite on my 1,1 computer, he had installed the Developer Version "Using the SFOTT method", so far if I am not wrong, there is no way to install the OS X Yosemite official release with the SFOTT method?. Currently I have another original mac pro 2,1 with OS X Mavericks "SFOTT Method Also", which will be the best method to update to OS X Yosemite?.


Thanks.

 

[Hennesie2000]

Hello gents,





I just realised that the person that had installed OS X Yosemite on my 1,1 computer, he had installed the Developer Version "Using the SFOTT method", so far if I am not wrong, there is no way to install the OS X Yosemite official release with the SFOTT method?. Currently I have another original mac pro 2,1 with OS X Mavericks "SFOTT Method Also", which will be the best method to update to OS X Yosemite?.





Thanks.

Just create a new installer using the final public release and install it over top of the existing install. Your documents, apps and settings will stay intact.

 

[splifingate]

Hey guys,

I bought a Mac Pro 1.1 in January, but I still have a problem with several freezes/ hang ups by using OSX Mavericks or Yosemite.

If the machine has a cold start or was in standby, it sometimes just freeze.
There is no log about this freeze, but with verbose kernel option there is a kernel panic on the screen (see this link).

[...]

Many thanks in advance !
Chris

Are any red LEDs evident on either memory riser?

I would suggest removing all but the four Elpida sticks (place two on Riser A and two on Riser B, of course), then re-boot.

Currently using an updated 1,1 to 2,1 with x5365s, and have eight 4G Nemix sticks: four Micron matched-set, and four Elpida matched-set, each two paired with the other two on separate risers.

I have had no kernel panics with multiple installs of Mavericks and Yosemite using a whole slave-ship full of frankensteinian boot.efi's

Eliminate the odds, and hopefully find the ends

Regards, splifingate

 

[Hennesie2000]

2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite

The RAM seems to be some deposits they had lying around (3 different manufactures, different timings and different speeds. see this link for details).

The ram in these machines MUST be installed pairs. Remove "Goldenmars" as it is the odd man out as you only have 7 sticks and it doesn't have a match.

I have 4 OWC 2GB sticks and 4 Apple 512MB sticks and have not had any issues. Make sure you follow the install configuration for the ram on the inside of the side panel.

 

[ilegal31]

Hennesie2000,


How are you, SFOTT will allow me to create another installer with the public final release of OS X Yosemite?, is there another recommended method?. I was looking a the latest SFOTT release but there no option to use the Yosemite final release.


Thanks.

 

[Hennesie2000]

2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite

Hennesie2000,





How are you, SFOTT will allow me to create another installer with the public final release of OS X Yosemite?, is there another recommended method?. I was looking a the latest SFOTT release but there no option to use the Yosemite final release.





Thanks.

Please read back a few pages. This was discussed and I assure you there is an option to use the final release of Yosemite with SFOTT. As I don't use that tool myself I am not sure of the exact process to use the final release but it is just an option while using SFOTT.

 

[ilegal31]

Hello,


While creating the usb key, I had noticed the error that appeared on the following picture, can anyone please provide details about it?.

Thanks.

 

[MrGame]

The ram in these machines MUST be installed pairs. Remove "Goldenmars" as it is the odd man out as you only have 7 sticks and it doesn't have a match.

I have 4 OWC 2GB sticks and 4 Apple 512MB sticks and have not had any issues. Make sure you follow the install configuration for the ram on the inside of the side panel.

I will try without the sticks, but I did not mentioned that my cam was too bad for the picture. There is a second Goldenmars stick (with ID:0 in the picture) - but it is just displayed as white bar because of the lightning. Sorry about that.

But thanks for you support, maybe I should open a single thread for this...

 

[Hennesie2000]

I will try without the sticks, but I did not mentioned that my cam was to bad for the picture. There is a second Goldenmars stick (with ID:0 in the picture) - but it is just displayed as white bar because of the lightning. Sorry about that.



But thanks for you support, maybe I should open a single thread for this...

Still install them as pairs according to the diagram on the inside panel. I'm not positive but I am guess you might need to switch the sticks so that Goldenmars are in 0 & 1. Then Nanya in 2 & 3. Im not sure if that's how they are laid out on the board though.

 

[MrGame]

Still install them as pairs according to the diagram on the inside panel. I'm not positive but I am guess you might need to switch the sticks so that Goldenmars are in 0 & 1. Then Nanya in 2 & 3. Im not sure if that's how they are laid out on the board though.

Thanks a lot. I will try this tomorrow.
It is not easy to install them, because the sticks are relabeled without any information about manufacturer, timing etc.
I will check the sticks in system information, too. Maybe they are already in the right positions.

 

[Hennesie2000]

Thanks a lot. I will try this tomorrow.

It is not easy to install them, because the sticks are relabeled without any information about manufacturer, timing etc.

I will check the sticks in system information, too. Maybe they are already in the right positions.

There should be labels on the board itself. DIMM0, DIMM1 etc. You can match those up with the IDs from the memtest.

 

[atvusr]

While creating the usb key, I had noticed the error that appeared on the following picture, can anyone please provide details about it?.

SFOTT needs the Kernel file - you have to extract it with Pacifist. See also Post #863 how to create a patched Installer manually.

 

[PeterHolbrook]

Pike's boot.efi

I've been away for several days and I'm not sure how to interpret the last several entries in Pike's blog. I had thought that booting from the Yosemite Recovery HD was already possible on an early Mac Pro, but there seem to remain some problems, if I am reading correctly. Can someone summarise the situation?

 

[mikeboss]

I've been away for several days and I'm not sure how to interpret the last several entries in Pike's blog. I had thought that booting from the Yosemite Recovery HD was already possible on an early Mac Pro, but there seem to remain some problems, if I am reading correctly. Can someone summarise the situation?

nope, booting the Recovery HD was not possible. Apple did some funky stuff to the kernelcache on the recovery partition. but pike was able to solve this, too. now it works. but: if one does a fresh install, the installer routine somehow gets ahold of Apple's own boot.efi and then copies this version onto the recovery partition. thus it's not bootable (again). until you replace it with pike's boot.efi.

 

[PeterHolbrook]

nope, booting the Recovery HD was not possible. Apple did some funky stuff to the kernelcache on the recovery partition. but pike was able to solve this, too. now it works. but: if one does a fresh install, the installer routine somehow gets ahold of Apple's own boot.efi and then copies this version onto the recovery partition. thus it's not bootable (again). until you replace it with pike's boot.efi.

Thanks. Yes, I know that all initial compilations of Pike's boot.efi failed with the Yosemite Recovery HD, but, before I went away, someone reported successfully booting it thanks to a new commit. When I came back this morning there seemed to be conflicting reports. Al least one person said that he encountered a perpetual wait with the Yosemite Recovery HD and Pike's newest boot.efi. So it's great that if finally works flawlessly with the Recovery HD. Will you or Hennesie be posting new "Grey" and "Black", non-verbose, Recovery-HD-compatible versions of boot.efi, or are we expecting further imminent development from Pike?

 

[Hennesie2000]

2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite

Thanks. Yes, I know that all initial compilations of Pike's boot.efi failed with the Yosemite Recovery HD, but, before I went away, someone reported successfully booting it thanks to a new commit. When I came back this morning there seemed to be conflicting reports. Al least one person said that he encountered a perpetual wait with the Yosemite Recovery HD and Pike's newest boot.efi. So it's great that if finally works flawlessly with the Recovery HD. Will you or Hennesie be posting new "Grey" and "Black", non-verbose, Recovery-HD-compatible versions of boot.efi, or are we expecting further imminent development from Pike?

I think we are waiting for Pike to make some other changes. Mikeboss was able to boot the Recovery HD by manually replacing the boot cache on the Recovery HD if I understand and remember correctly.

EDIT:
Looks like Pike has finished it. I will build a new one this afternoon and test. Unless someone can do it earlier.

 

[Chung123]

Has anyone else experienced the hanging boot issue after a NVRAM/PRAM reset?

I don't recommend trying it out unless you have the USB stick installer to boot to and repair permissions to fix the boot drive.

Any idea what could be causing this?

 

[Hennesie2000]

2006/2007 Mac Pro (1,1/2,1) and OS X Yosemite

Updated black and grey boot.efi files with support for the Recovery HD. I will be testing this momentarily.

Update:
After replacing both boot.efi files on the Recovery HD I was able to boot into Recovery Mode just fine. This is a verbose boot.efi file though.