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

[gpatpandp]

So far it is a no go. They have either created or renamed another "mach_kernel". Without placing in either the Installer or OS X 10.10 System partition, Chameleon stops immediately and cannot find it. When placing it in either roots Chameleon begins to load the extensions then it just abruptly stops/stalls and goes completely blank.

 

[gpatpandp]

No more tricks up my proverbial sleeve...I have tried them all and nada/no dice.

Personally I am beginning to grow a tad weary of having to hack these once expensive, highly competent machines by having to continuously navigate around Apple's deliberate roadblocks and imposed obsolescence. I think I am going to let the Yosemite thing lay dormant for a while and see if a boot.efi surfaces in the Fall when the OS X 10.10 final is said to be released. If that doesn't surface in a reasonable amount of time, I will most likely kiss my Mac Pro goodbye via Ebay/Craigslist and also any further patronage in investing in official Apple machines and instead enter the strict realm of Hackintosh.

I am beginning to embrace the mind set that if I am going to go through all this trouble hacking, I might as well reward myself and enjoy the substantial savings on the front end.

On another note, I found a thread from quite a while ago where I had reported that when considering replacing Chameleon with Clover in booting Mountain Lion, that even then Clover could not read the ODD SATA ports on my Mac Pro's motherboard back then. And now with Yosemite, Clover still lacks the ability to recognize those ports and a Blu ray optical drive connected to one of them. This is getting very old.

 

[H2SO4]

No more tricks up my proverbial sleeve...I have tried them all and nada/no dice.

Personally I am beginning to grow a tad weary of having to hack these once expensive, highly competent machines by having to continuously navigate around Apple's deliberate roadblocks and imposed obsolescence.

I am feeling the same. Where once I’d defend Apple to the ends of the earth I now find myself resenting them.
I don’t think Windows is as bad as I once did. Hated ,98, didn’t like XP, wasn’t keen on 7, not tried 8. Who knows in 5 years or so when their OS is ‘nice'………..?

 

[Hennesie2000]

Success!!!!

So far it is a no go. They have either created or renamed another "mach_kernel". Without placing in either the Installer or OS X 10.10 System partition, Chameleon stops immediately and cannot find it. When placing it in either roots Chameleon begins to load the extensions then it just abruptly stops/stalls and goes completely blank.

I was able to install and boot Yosemite using the Chameleon package included in that link on the previous page. I installed it on my normal setup that I used for Mavericks. One HDD formatted with 3 partitions (Boot/Installer/Yosemite) and with a GUID partition table. Create the Installer partition as if you were creating a USB installer. Then install Chameleon on to the Boot partition. Once it is installed you will see a "mach_kernel" file in the Boot partition. Copy that file to the root of the Installer partition.

After installing Yosemite on the Yosemite partition I had to reboot back to my Mavericks drive and then copy the "mach_kernel" file to the root of the Yosemite partition.

I am not sure what happened but Chameleon wouldn't boot anymore. I was getting a "Could not find bootable disk..." error. I backed up my org.chameleon.Boot.plist and then reinstalled Chameleon over top of the existing install on the Boot partition. The replaced the org.chameleon.Boot.plist with the one that I had copied. Then bless and set legacy mode again. Yosemite booted right up but my USB mouse wouldn't work, still I was able to go through the setup using the keyboard.

Here is my org.chameleon.Boot.plist:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
	<key>Default Partition</key>
	<string>Yosemite</string>
	<key>GUI</key>
	<string>No</string>
	<key>Graphics Mode</key>
	<string>1024x768x32</string>
	<key>GraphicsEnabler</key>
	<string>Yes</string>
	<key>Kernel</key>
	<string>mach_kernel</string>
	<key>Kernel Flags</key>
	<string>kext-dev-mode=1 -f -v</string>
	<key>ShowInfo</key>
	<string>Yes</string>
	<key>Timeout</key>
	<string>5</string>
</dict>
</plist>

Update:
The USB issue I was having with my mouse was because of the Extensions included with the Chameleon package since it is for a Hackintosh. I removed all of the extensions and my USB was working fine then.

 

[PeterHolbrook]

So far it is a no go. They have either created or renamed another "mach_kernel". Without placing in either the Installer or OS X 10.10 System partition, Chameleon stops immediately and cannot find it. When placing it in either roots Chameleon begins to load the extensions then it just abruptly stops/stalls and goes completely blank.

Sorry to read your negative assessment. For what it's worth, the site I mentioned now has a SECOND download: "Chameleon r2377 OS X Yosemite.pkg". Have you tried that one? It is contributed by the hacker that sort of discovered the new coding of the kernel. If it works on regular PCs, I fail to see why exactly it wouldn't work on an old Mac Pro.

 

[Hennesie2000]

Sorry to read your negative assessment. For what it's worth, the site I mentioned now has a SECOND download: "Chameleon r2377 OS X Yosemite.pkg". Have you tried that one? It is contributed by the hacker that sort of discovered the new coding of the kernel. If it works on regular PCs, I fail to see why exactly it wouldn't work on an old Mac Pro.

That is what I just used and it did work. I am typing this on Yosemite using Chameleon to boot.

Update:
I cannot seem to log into iMessage and putting the FileNVRAM.dylib file in the module folder causes an error and Yosemite will not boot.

 

[JoSch]

I am feeling the same. Where once I’d defend Apple to the ends of the earth I now find myself resenting them.
I don’t think Windows is as bad as I once did. Hated ,98, didn’t like XP, wasn’t keen on 7, not tried 8. Who knows in 5 years or so when their OS is ‘nice'………..?

Oh come on. Yosemite is the third MacOSX release in a row without dropping any machines from support. Even my old Macbook 13" (Late 2008) is still supported. Where is the forced obsolescence there?

 

[PeterHolbrook]

I cannot seem to log into iMessage and putting the FileNVRAM.dylib file in the module folder causes an error and Yosemite will not boot.

Am I right in assuming you've set up this Chameleon/Yosemite thing on an old Mac Pro? If so, there might be a "solution" for some of the problems you've reported. According to Jabbawok, the partition table of the disk where Chameleon resides should be MBR, not GUID, though that might be particularly applicable to older reincarnations of Chameleon and/or only on Hackintosh hardware. In case you have iPartition or a similar tool, you might want to check what happens if you non-destructively change the partition table of that disk to MBR. It might fix the NVRAM/Messages/FaceTime issue.

Can you comment whether your Yosemite "sees" the SATA connectors of the Mac Pro board? Do you have sound? Does everything else work?

 

[gpatpandp]

Sorry to read your negative assessment. For what it's worth, the site I mentioned now has a SECOND download: "Chameleon r2377 OS X Yosemite.pkg". Have you tried that one? It is contributed by the hacker that sort of discovered the new coding of the kernel. If it works on regular PCs, I fail to see why exactly it wouldn't work on an old Mac Pro.

Indeed the second version boots Yosemite fine. Placing the newly created "mach_kernel" in the root of both the installer and the OS X 10.10 System partition did not stop or stall as it did when I had installed the first version. As expected, my ODD SATA ports and the Blue ray optical drive connected to one of them is fully recognized. Interestingly enough and while true that Chameleon throws an error and stops when the NVRAM module is installed, the fact the I had booted this same system partition previously in Clover applied the "old fix" that I described in this thread a few pages back and therefore both iMessages and FaceTime are fully functional as well.

Also regarding the dialogue I had the other day concerning the need/requirement of Clover to "mask" the system in order for it to boot and function properly. I was remiss in forgetting that after booting successfully in any of these hacked OS X systems that all one needs to do is simply add the real Motherboard ID and machine version (i.e. Mac Pro 2,1) to the PlatformSupport.plist located in the System/Library/Core Services folder and then change over that same real system spec info using Clover configurator and that will enable anyone to boot Clover (or Chameleon for that matter) with there real unmasked machine information.

 

[PeterHolbrook]

Indeed the second version boots Yosemite fine. Placing the newly created "mach_kernel" in the root of both the installer and the OS X 10.10 System partition did not stop or stall as it did when I had installed the first version. As expected, my ODD SATA ports and the Blue ray optical drive connected to one of them is fully recognized. Interestingly enough and while true that Chameleon throws an error and stops when the NVRAM module is installed, the fact the I had booted this same system partition previously in Clover applied the "old fix" that I described in this thread a few pages back and therefore both iMessages and FaceTime are fully functional as well.

Great. The only missing thing, then, is for some genius or Tiamo himself to adapt his boot.efi to the new Yosemite environment.

 

[Hennesie2000]

Am I right in assuming you've set up this Chameleon/Yosemite thing on an old Mac Pro? If so, there might be a "solution" for some of the problems you've reported. According to Jabbawok, the partition table of the disk where Chameleon resides should be MBR, not GUID, though that might be particularly applicable to older reincarnations of Chameleon and/or only on Hackintosh hardware. In case you have iPartition or a similar tool, you might want to check what happens if you non-destructively change the partition table of that disk to MBR. It might fix the NVRAM/Messages/FaceTime issue.

Can you comment whether your Yosemite "sees" the SATA connectors of the Mac Pro board? Do you have sound? Does everything else work?

Using a GPT worked fine with Mavericks. This was discussed greatly in the Mavericks thread on here. To use iMessage with Mavericks the FileNVRAM.dylib was needed. I will try the other fix for imessage gpatpandp is talking about.

I think I need to put some of the extensions back for my blu ray drive to be recognized and to get sound. I'll mess with it this afternoon and report back as it seems gpatpandp has more functionality at the moment.

 

[H2SO4]

Oh come on. Yosemite is the third MacOSX release in a row without dropping any machines from support. Even my old Macbook 13" (Late 2008) is still supported. Where is the forced obsolescence there?

I’m pretty sure they drop things unnecessarily. In absolute terms it’s a matter of opinion I suppose but in relative terms…….

I have an SSD in my Pro that has a copy of Windows 7 that I use for gaming. Two things;
Boot camp for my pro does not support 7.
I also have 7 running on an old and cheap PC I bought for £20, (with no hacks), it installed without putting up a fight with a lot less than the minimum specified RAM.
This would not happen with ANYTHING that sports an Apple logo.

 

[gpatpandp]

I was able to install and boot Yosemite using the Chameleon package included in that link on the previous page.

Right, by the time you accessed the link version 2 was available. The original version 1 did not work and would not have worked for you either.

Am I right in assuming you've set up this Chameleon/Yosemite thing on an old Mac Pro? If so, there might be a "solution" for some of the problems you've reported. According to Jabbawok, the partition table of the disk where Chameleon resides should be MBR, not GUID, though that might be particularly applicable to older reincarnations of Chameleon and/or only on Hackintosh hardware. In case you have iPartition or a similar tool, you might want to check what happens if you non-destructively change the partition table of that disk to MBR. It might fix the NVRAM/Messages/FaceTime issue.

Although the fact that the NVRAM module not working in OS X 10.10 is not effected by this issue, for those reviewing, considering, attempting the method of installing the Chameleon BOOT, OS X Installer, and OS X System partition all one one GUID/HFS+ formatted hard drive know that while this technique works for some, IT DOES NOT work universally for all in the same manner that installing the Chameleon BOOT and the Installer on one MBR/HFS+ formatted hard drive and the OS X system on a formatted GUID/HFS+ separate hard drive does.

I know the “pied piper” of this technique is always quick to rebut this fact and has made the determination that ANYONE performing this procedure corectly will successfully be able to get it to work however this is simply not true. And while it might be said that those unable to get it to work are perhaps in the minority, nonetheless know that it will either work for you or it will not and that there is no rhyme or reason as to why it works for some and not others.

 

[Rough Edge]

Until the Tiamo boot loader is updated and until Chameleon sorts out the Yosemite issue, Use clover... its fairly simple and reread our previous posts on adding the needed files to the install disk.. thats it.. before Tiamo's boot.efi loader, I always used chameleon, but clover seems to function a lot better for Yosemite at the moment. Just remember on a mac pro, to use 3.1 bios in the clover config file (download clover Configurator)..

IM running Yosemite on a Mac Pro 1,1 upgraded to 2,1. I cloud, iMessage all working. There is a bluetooth fix in the previous posts and the audio fix. Id leave chameleon behind for now... And there is even a clover Config file that someone has posted.

Thats why its been quiet in here.. lol... we got it all working with clover and no need for chameleon at the moment until Tiamo does a new miracle boot loader (fingers crossed)

 

[Hennesie2000]

I know the “pied piper” of this technique is always quick to rebut this fact and has made the determination that ANYONE performing this procedure corectly will successfully be able to get it to work however this is simply not true. And while it might be said that those unable to get it to work are perhaps in the minority, nonetheless know that it will either work for you or it will not and that there is no rhyme or reason as to why it works for some and not others.

You really don't like me. My purpose of doing it this way is to be vanilla as possible and give a method for those who may have only one spare hdd and don't want to deal with the on board sata connections. If you don't like it that's fine.

------------------

On another note does any one have a sata.dylib file I can download? The module manager in the chameleon wizard isn't working.

*never-mind, I got the file. I'll check my blu ray drive when I get a chance.

 

[gpatpandp]

You really don't like me.

------------------

On another note does any one have a sata.dylib file I can download? The module manager in the chameleon wizard isn't working.

Firstly I do not even know you and I would never make any determination to dislike someone that I do not know or have never met in person. I will say that from any dialogue that we have conducted directly between one another that you appear to be quite defensive. The fact that our experiences differ greatly on utilizing the BOOT/Installer/OS X System all on one GUID/HFS+ partition certainly would never create justification for myself or I would hope anyone to dislike an individual based upon that fact.

I think you misunderstand my remarks though please know that it is absolutely nothing personal.

 

[gpatpandp]

Until the Tiamo boot loader is updated and until Chameleon sorts out the Yosemite issue, Use clover... its fairly simple and reread our previous posts on adding the needed files to the install disk.. thats it.. before Tiamo's boot.efi loader, I always used chameleon, but clover seems to function a lot better for Yosemite at the moment. Just remember on a mac pro, to use 3.1 bios in the clover config file (download clover Configurator)..

IM running Yosemite on a Mac Pro 1,1 upgraded to 2,1. I cloud, iMessage all working. There is a bluetooth fix in the previous posts and the audio fix. Id leave chameleon behind for now... And there is even a clover Config file that someone has posted.

Thats why its been quiet in here.. lol... we got it all working with clover and no need for chameleon at the moment until Tiamo does a new miracle boot loader (fingers crossed)

While I preface this statement by stating that I am ONLY speaking for myself, then mere fact that my Blu ray optical drive is being recognized as it always has is enough for me to commit to Chameleon until a better option (namely a updated boot.efi) is produced. I just reinstalled the original OS X 10.10 AppleHDA.kext and I am getting native audio again in booting from Chameleon as well. In Clover the "script" that was supposed to fix the audio did not work and therefore I installed VoodooHDA.kext in the meantime. As I do not use or own any bluetooth devices, the fact that it is not working doesn't effect me.

PS. A quick "pit stop" to System/Library/Core Services/Menu Extras folder and clicking on the "Volume.menu" placed the volume slider nicely back in Finder.

 

[Hennesie2000]

So far I have been unsuccessful getting native audio or the onboard SATA ports to work with Chameleon. This might be a MBR vs GUID issue I will have to test that later. I tired re-installing the AppleHDA.kext like gpatpandp said but it was a no go with me.

 

[gpatpandp]

So far I have been unsuccessful getting native audio or the onboard SATA ports to work with Chameleon. might be a MBR vs GUID issue I will have to test that later. I tired re-installing the AppleHDA.kext like gpatpandp said but it was a no go with me.

While I suppose it is possible and certainly it's a situation where one can point directly at our respected set ups and an obvious difference, though as was the case in both instances with Chameleon crashing/freezing with the NVRAM module installed no matter what the OS system partition was formatted in, I doubt that is the cause of your present inability to get recognition if your SATA ports and native audio/AppleHDA.kext to load

 

[genex]

Clover

Am i the only one that has problem booting installer from Clover, i mean i have followed guide , few times, everything works i place plist file in root of Boot drive but one i reboot mac pro i got option EFI BOOT , i choose that disk and it boots clover, problem is once i select installer disk, screen just flickers after few seconds staying in clover botooloader. ?? Any IDEA

MAC PRO 1.1, 16 GB RAM, ATI Radeon HD 5770

 

[Hennesie2000]

While I suppose it is possible and certainly it's a situation where one can point directly at our respected set ups and an obvious difference, though as was the case in both instances with Chameleon crashing/freezing with the NVRAM module installed no matter what the OS system partition was formatted in, I doubt that is the cause of your present inability to get recognition if your SATA ports and native audio/AppleHDA.kext to load

After seeing your screenshot I realized that I am missing one very key component. I didn't have the dsdt.aml file in place (stupid mistake). Going to give it another try now.

 

[gpatpandp]

Am i the only one that has problem booting installer from Clover, i mean i have followed guide , few times, everything works i place plist file in root of Boot drive but one i reboot mac pro i got option EFI BOOT , i choose that disk and it boots clover, problem is once i select installer disk, screen just flickers after few seconds staying in clover botooloader. ?? Any IDEA

MAC PRO 1.1, 16 GB RAM, ATI Radeon HD 5770

sounds as though you need to run the boot bless legacy command in terminal on your "BOOT" partition.

sudo bless --folder /Volumes/BOOT --file /Volumes/BOOT/boot --setBoot --legacy

 

[genex]

sounds as though you need to run the boot bless legacy command in terminal on your "BOOT" partition.

sudo bless --folder /Volumes/BOOT --file /Volumes/BOOT/boot --setBoot --legacy

i did, and i do enter clover boot loader i just cant boot in Installer partition

 

[gpatpandp]

After seeing your screenshot I realized that I am missing one very key component. I didn't have the dsdt.aml file in place (stupid mistake). Going to give it another try now.

check your inbox

 

[genex]

check your inbox

Oh, so i have to have dsdt.aml Where do i get one for Mac Pro ?
Any Idea about my problem ?