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

[wolf1734]

Ok.... Still don't understand.

bonsoir

vous pouvez m'envoyer le lien pour yosemite prêt a installer sur un mac pro 1.1 sur skype.
ou le dmg preparer en piece jointe
cordialement

 

[Hennesie2000]

bonsoir



vous pouvez m'envoyer le lien pour yosemite prêt a installer sur un mac pro 1.1 sur skype.

ou le dmg preparer en piece jointe

cordialement

I am not going to attach it here but I can send you a link to it via Skype but you haven't provided any way to contact you.

 

[wolf1734]

I am not going to attach it here but I can send you a link to it via Skype but you haven't provided any way to contact you.

bonjour sur skype mon speudo c'est petitbon1
mais dite moi ou vous voulez mettre le lien vous pouvez mettre le lien sur mac rumos ou sur netkas mon email c'est wolf1734@hotmail.fr
cordialement

 

[PeterHolbrook]

I mean the other way around, does Yosemite appear in Disk Utility when booted in Snow Leopard?

I hadn't been able to verify that until earlier today. I can confirm that the Snow Leopard Disk Utility DOES see the Yosemite disk without any problems. The claims that it doesn't are bogus, probably due to faulty hardware or faulty user procedures.

 

[H2SO4]

I hadn't been able to verify that until earlier today. I can confirm that the Snow Leopard Disk Utility DOES see the Yosemite disk without any problems. The claims that it doesn't are bogus, probably due to faulty hardware or faulty user procedures.

Or a bug. That’s a viable possibility surely?

 

[PeterHolbrook]

Or a bug. That’s a viable possibility surely?

If you can replicate the "bug" with a known set of circumstances, it might be a bug. Otherwise, it isn't a bug. For instance, if you can demonstrate that the SL (10.6.8) Disk Utility can't see Yosemite disks on one particular model of Mac with one particular model of hard drive, or of one particular capacity, and the claim is reproducible on all such machines with said components, then it would be a bug.

 

[ilegal31]

Hello,


OS X Yosemite was running fine these last 2 weeks on my Mac Pro 2,1, today suddenly the computer shut down and restarted twice, I did had an issue with overheating ram but I am running SMC Fan Control, when the computer shut down the temperature was at 30C degrees, any advise please?.


Thanks.

 

[Hennesie2000]

Hello,





OS X Yosemite was running fine these last 2 weeks on my Mac Pro 2,1, today suddenly the computer shut down and restarted twice, I did had an issue with overheating ram but I am running SMC Fan Control, when the computer shut down the temperature was at 30C degrees, any advise please?.





Thanks.

Do any of the lights on the RAM riser boards light up?

 

[trickbox]

Anyone have an issue installing update Little Snitch 3.5?

Hey Guys,

To start off just wanted to thank all those who have enabled me to be running Yosemite on my Mac Pro 1,1 for the past few weeks. It's been a great experience.

I just updated Little Snitch to 3.5. The boot took forever and then Little Snitch would not start, giving an error about "could not load extension". I reinstalled from a full download version but with the same result. This update also broke the shut down of my mac, which I had to hard reboot each time.

I'm currently restoring from a backup i made last night.

I just wondered if anyone else has experienced this issue, whether it was a problem with this update on Yosemite in general, or because we are running on unsupported devices.

Thanks for your help.

 

[Hennesie2000]

Hey Guys,



To start off just wanted to thank all those who have enabled me to be running Yosemite on my Mac Pro 1,1 for the past few weeks. It's been a great experience.



I just updated Little Snitch to 3.5. The boot took forever and then Little Snitch would not start, giving an error about "could not load extension". I reinstalled from a full download version but with the same result. This update also broke the shut down of my mac, which I had to hard reboot each time.



I'm currently restoring from a backup i made last night.



I just wondered if anyone else has experienced this issue, whether it was a problem with this update on Yosemite in general, or because we are running on unsupported devices.



Thanks for your help.

There were some issues with LittleSnitch mentioned in the past but if I remember correctly it was all due to a bad LittleSnitch installer. Search this thread for LittleSnitch and you should find some post. Yosemite was effected after doing an update to LittleSnitch.

 

[trickbox]

There were some issues with LittleSnitch mentioned in the past but if I remember correctly it was all due to a bad LittleSnitch installer. Search this thread for LittleSnitch and you should find some post. Yosemite was effected after doing an update to LittleSnitch.

Thanks Hennesie2000 for the reply. I had read about previous issues with Little Snitch, but hadn't experienced them myself. That's why I tried the full installer after the automatic update failed.

Hopefully I should be up and running after the backup restore. Looks like someone else is having the same issue on the Little Snitch User Forum, I'll hold off updating my other macs until this is fixed.

 

[the bug]

There have been a few folks over on the Objective Development forum who are having issues with version 3.5 of Little Snitch. I would hold off upgrading for now.

I was about to update, when I noticed comments on versionTracker which led me to the Little Snitch forums.

http://forums.obdev.at/viewtopic.php?f=1&t=9466

- Jay

 

[ilegal31]

Hello Henessie2000,



Yes they do, I will try to test all the ram, maybe there is a faulty one. Yosemite is just awesome, speed, looks and power. Is ti possible to enable trim support in Yosemite?.


Thanks.

Do any of the lights on the RAM riser boards light up?

 

[Hennesie2000]

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

Hello Henessie2000,







Yes they do, I will try to test all the ram, maybe there is a faulty one. Yosemite is just awesome, speed, looks and power. Is ti possible to enable trim support in Yosemite?.





Thanks.

If one lights up and stays red then that is the faulty one. You can enable trim using Trim Enabler but it requires kext-dev-mode=1

 

[Harry Muff]

My Mac Pro 1,1 has eaten quite a few sticks of RAM over the years. I'm currently running it on two sticks of 4GB. If either one of those goes I'll be screwed until I can track down some cheap RAM here in Toronto.

 

[Hennesie2000]

My Mac Pro 1,1 has eaten quite a few sticks of RAM over the years. I'm currently running it on two sticks of 4GB. If either one of those goes I'll be screwed until I can track down some cheap RAM here in Toronto.

Always had luck with OWC ram. The only two I have had go bad, they replaced free under warranty.

 

[Tower-Union]

I decided to try doing the target disk mode route but my stupid external wouldn't boot (on my friends laptop, but would boot/wouldn't install on my Mac Pro). Rebuilt it from scratch for the fourth time and it worked!

Just a huge thanks to Pike and Hennesey, I'll make a donation to Pike after I post this, is Hennesey accepting donations? I'm super stoked to have this running, and thank you all for the help!

 

[RyanNowlin]

Handoff for MacPro 2,1

MacVidCards sells an adapter that he has working in a 2,1. I personally haven't bought it or used it though. http://www.macvidcards.com/store/p33/Wifi_AC_&_Bluetooth_Airport_Card.html. It's the one for the 3,1.

----------



I purchased the Apple/Broadcom WiFi/Bluetooth card (BCM94360CD) on ebay and i also purchased the PCI-E to 1.x adapter from ebay:

http://www.ebay.com/itm/231370068228?_trksid=p2060778.m2749.l2649&ssPageName=STRK:MEBIDX:IT

Installed it in my MacPro 2,1 that is running Yosemite, booted up and WiFi was immediately recognized -- works great! But OS X doesn't see the bluetooth.

The adapter came with no documentation but it has a 2-pin USB connector and a cable that apparently needs to be plugged into the motherboard. Assuming this could be what I am missing...any idea if there are pins on the macpro motherboard to connect this? have not found anything.

Over on the tonymacx86 hackintosh site, they this configuration working great on various PC motherboards....just not sure if it will work on the MacPro.

Any help is appreciated!

 

[Peloche]

MacVidCards sells an adapter that he has working in a 2,1. I personally haven't bought it or used it though. http://www.macvidcards.com/store/p33/Wifi_AC_&_Bluetooth_Airport_Card.html. It's the one for the 3,1.

----------



I purchased the Apple/Broadcom WiFi/Bluetooth card (BCM94360CD) on ebay and i also purchased the PCI-E to 1.x adapter from ebay:

http://www.ebay.com/itm/231370068228?_trksid=p2060778.m2749.l2649&ssPageName=STRK:MEBIDX:IT

Installed it in my MacPro 2,1 that is running Yosemite, booted up and WiFi was immediately recognized -- works great! But OS X doesn't see the bluetooth.

The adapter came with no documentation but it has a 2-pin USB connector and a cable that apparently needs to be plugged into the motherboard. Assuming this could be what I am missing...any idea if there are pins on the macpro motherboard to connect this? have not found anything.

Over on the tonymacx86 hackintosh site, they this configuration working great on various PC motherboards....just not sure if it will work on the MacPro.

Any help is appreciated!

Hi,

Yeap you have to connect the 2 wires (D- and D+) to an USB port, on my side i've used an USB cable that i've cut and soldered D- and D+ to the 2 wires from the adapter, and i have connected the cable to external usb port.

If you have an original bluetooth (2006) you'll have also to remove all existing CSR bluetooth kexts (CSRBluetoothHostControllerUSBTransport.kext and CSRHIDTransitionDriver.kext) within System/Library/Extensions/IOBluetoothFamily.kext/Contents/Plugins/ and to delete cache.

It should work after reboot.

If it doesn't, have a look there:

https://forums.macrumors.com/threads/1803192/

 

[PeterHolbrook]

If you have an original bluetooth (2006) you'll have also to remove all existing CSR bluetooth kexts (CSRBluetoothHostControllerUSBTransport.kext and CSRHIDTransitionDriver.kext) within System/Library/Extensions/IOBluetoothFamily.kext/Contents/Plugins/ and to delete cache.

Your explanation is very interesting, as it seems to imply that uninstalling Apple's original MA687ZM/A Bluetooth adapter is NOT necessary. If that were true, would providing a wire between said old adapter and the Bcm94360cd maintain Bluetooth capabilities when booting, say, Snow Leopard?

How safe is simply erasing the kexts you've mentioned? I mean, is it likely that Apple will reinstall such kexts via Software Update?

 

[MacVidCards]

MacVidCards sells an adapter that he has working in a 2,1. I personally haven't bought it or used it though. http://www.macvidcards.com/store/p33/Wifi_AC_&_Bluetooth_Airport_Card.html. It's the one for the 3,1.

----------



I purchased the Apple/Broadcom WiFi/Bluetooth card (BCM94360CD) on ebay and i also purchased the PCI-E to 1.x adapter from ebay:

http://www.ebay.com/itm/231370068228?_trksid=p2060778.m2749.l2649&ssPageName=STRK:MEBIDX:IT

Installed it in my MacPro 2,1 that is running Yosemite, booted up and WiFi was immediately recognized -- works great! But OS X doesn't see the bluetooth.

The adapter came with no documentation but it has a 2-pin USB connector and a cable that apparently needs to be plugged into the motherboard. Assuming this could be what I am missing...any idea if there are pins on the macpro motherboard to connect this? have not found anything.

Over on the tonymacx86 hackintosh site, they this configuration working great on various PC motherboards....just not sure if it will work on the MacPro.

Any help is appreciated!

You have officially made this 20x harder than it needs to be.

Does your PCIE x1 board have JUST the BRCM94360CD card or is that card in another carrier?

Point is, there is an adapter board that plugs into your original Airport card slot.

This connects all wires, everything is perfect. There is even the correct amount of antena wires.

This is one place where having a 1,1 is a blessing. The 4,1 and 5,1 have a much more difficult time.

We don't sell the adapter board by itself but we might soon.

Until then OSXWifi has them as do MANY Chinese sellers.

Using just the airport card adaper is cleaner, easier, less junk in the computer, etc.

 

[Peloche]

Your explanation is very interesting, as it seems to imply that uninstalling Apple's original MA687ZM/A Bluetooth adapter is NOT necessary. If that were true, would providing a wire between said old adapter and the Bcm94360cd maintain Bluetooth capabilities when booting, say, Snow Leopard?

How safe is simply erasing the kexts you've mentioned? I mean, is it likely that Apple will reinstall such kexts via Software Update?

I left original Bluetooth adapter (Mac Pro 2006) in place and connected, if I boot Snow Leopard it will work since I didn't modify this kext within SL.

Normaly Apple OS X in case of 2 Bluetooth adapters installed is selecting the one having better capabilities, but the first condition is that the new one is detected and mine wasn't despite the driver was installed for WiFi.

After removing CSR kexts Bluetooth 4.0 adapter was detected.

There is a command to force OS X to select the best adapter :

sudo nvram bluetoothHostControllerSwitchBehavior="always"

I bought the same adapter as RyanNowlin, because before to install on Mac i wanted to install it on my Hackint0sh to be sure that it was working and after that i moved it to my Mac Pro.

WiFi and Bluetooth work on Hack and Mac Pro allowing Handoff on both, so few days ago i ordered a Mini PCI-E Adapter for BCM94360CD/BCM94331CD to go to Airport port.

When this Mini PCI-E Adapter arrive and installed i have to buy another BCM94360CD for my Hack to try Handoff from Hack to Mac Pro but i don't know if it should work...

 

[H2SO4]

There have been a few folks over on the Objective Development forum who are having issues with version 3.5 of Little Snitch. I would hold off upgrading for now.

I was about to update, when I noticed comments on versionTracker which led me to the Little Snitch forums.

http://forums.obdev.at/viewtopic.php?f=1&t=9466

- Jay

I had problems with 3.5 too.
In after installation Little Snitch told me it could load a kernel extension and that my install was broken.
Lots of restarts, re-installs and no internet at all later I was forced to uninstall it, safe boot and then reboot before my Mac returned to normal.

 

[tdatsmrad]

If you could send a copy of the link to make a USB installer to my e-mail like for Wolf1734, I would be eternally grateful. tdatsmrad@aol.com

 

[tryingtimes]

Mac Pro 1,1 upgrade to Yosemite

First of thanks to Hennessie for the upgrade instructions. I'm not a IT person by any stretch of the imagination, but nonetheless I found them to be quite understandable and easy to follow. I am hoping for some help with a relatively minor but annoying problem:

Before upgrading I bought a Radeon 5770 video card that was supposed to be flashed for Mac. However, I get no apple logo when booting after upgrading to Yosemite. Perhaps associated with this when holding down the option (alt) key while booting I cannot see the screen listing the boot options. I got around this by trial and error, pressing the right arrow on successive reboot attempts until the machine booted from the thumb drive. All went smoothly after that. Is my video card not actually flashed for Mac as advertised or could something have gone wrong with the install?

Just to be sure:
After upgrading I noticed the addition of 2 steps, 14 & 15, to Hennessie's instructions under Creating the Yosemite thumb driver installer. These steps unlock and lock boot.efi. I'm assuming these weren't needed in my case since the upgrade worked. If that's a wrong assumption, please let me know.

Finally:
I would like to install tobyg's script make sure the correct boot.efi file is there for future upgrades. Will the fact that the boot.efi in the CoreServices directory is locked be a problem, and if so what's a safe work around?

Thanks!