Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

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

Usb not working in yosemite

Hi guys'
I've installed yosemite on my 2006 mac pro took me 4 weeks but managed it, shows you how poor iam at this stuff lol. everything fine except wifi greyed out which is not needed anyway but my usb's front and rear not working apart from my keyboard which is usb and plugged into middle usb at back and works anyone got ANY ideas please just to at least try. BIG THANKYOU TO ALL THE PEOPLE WHO MADE THIS HAPPEN ..

oh I've tried smc and pram and run kext utility THANX IN ADVANCE.

IM NEW TO THIS STUFF , HOPE THIS GETS ADDED TO THIS TREAD OK
 
I shouldn't have

I installed Yosemite on my 2006 Mac Pro several months ago. No problems at all. Yesterday, I clicked on the install for the 10.10.2 upgrade. Following reboot, the screen showed a flashing rectangle with a central "?", That disappeared and a black screen with white Apple logo froze requiring restart. I was not able to get past this on several tries. Now, on starting the machine, I get no signal to my display whatsoever. I do hear the startup tone from the computer and the power to the display card is working.

Could anyone please help me determine what my options would be at this point. Thank you
 
Sounds like you upgraded the OS and it wrote over your patched EFI. Is that possible? It would help if you included the method you used to install onto your 2006 Mac Pro.

Reread the first post on this thread please, you will see that there is a simple program that checks to ensure that the patched EFI files are replaced if an OS update overwrites them.

Good luck!
 
dermdoc said:
I installed Yosemite on my 2006 Mac Pro several months ago. No problems at all. Yesterday, I clicked on the install for the 10.10.2 upgrade. Following reboot, the screen showed a flashing rectangle with a central "?", That disappeared and a black screen with white Apple logo froze requiring restart. I was not able to get past this on several tries. Now, on starting the machine, I get no signal to my display whatsoever. I do hear the startup tone from the computer and the power to the display card is working.

Could anyone please help me determine what my options would be at this point. Thank you
Click to expand...

Same thing happened to me last night. The 10.10.2 update from the app store definitely overwrites the boot.efi files.

I was fortunate to have a second Mavericks drive in my Mac Pro that the machine defaulted to booting when the Yosemite update failed. If you look at the last page in this thread, you'll see what I tried.

I was lucky to still have the modded Yosemite install files on an external HD, so I reinstalled Yosemite. It worked fine. All my data and apps are untouched and working, and I am now booting into 10.10. I will wait for some more feedback before trying the 10.10.2 update again (even 10.10.1 isn't that important to me right now).

Good luck.
 
If you have the TobyG script modded for Yosemite as in post #1584 or 666Sheep's version then updating via the App Store should not be a problem.
 
stmp said:
Sounds like you upgraded the OS and it wrote over your patched EFI. Is that possible? It would help if you included the method you used to install onto your 2006 Mac Pro.

Reread the first post on this thread please, you will see that there is a simple program that checks to ensure that the patched EFI files are replaced if an OS update overwrites them.

Good luck!
Click to expand...

The problem is now I can't get anywhere on the computer that would even allow me to run the program. I don't have another drive with the 10.10.1 on it...
HELP
 
dermdoc said:
The problem is now I can't get anywhere on the computer that would even allow me to run the program. I don't have another drive with the 10.10.1 on it...

HELP
Click to expand...


Do you have another Mac with FireWire that you can use target disk mode or perhaps a sata to USB adapter and another computer to replace the boot.efi files? Or do you you have the modified installer you can boot to and reinstall 10.10.0? Then installed the update script/fix before running he 10.10.2 update again.
 
Hennesie2000 said:
Do you have another Mac with FireWire that you can use target disk mode or perhaps a sata to USB adapter and another computer to replace the boot.efi files? Or do you you have the modified installer you can boot to and reinstall 10.10.0? Then installed the update script/fix before running he 10.10.2 update again.
Click to expand...

Thanks for your response.

I have a Macbook Air running Yosemite 10.10.2. It has a firewire connection. What is target mode?

Also, the fact that I have no screen input at all, not even an apple or ?, does that point to a deeper issue?
 
Yosemite 10.10.2 update

Hi, Guys,
just letting you know i applied latest update to yosmite (10.10.2 ). to my drive the operating system then failed to boot so i just replaced efi boot (which i had saved) again and bang no problems . JUST STILL NO USB'S
 
dermdoc said:
Thanks for your response.

I have a Macbook Air running Yosemite 10.10.2. It has a firewire connection. What is target mode?

Also, the fact that I have no screen input at all, not even an apple or ?, does that point to a deeper issue?
Click to expand...


Turn both computers off. Connect the Mac Pro and the MacBook Air using a FireWire cable. Turn on the Mac Pro and hold in "T". Then turn on the MacBook Air. The Mac Pros hdd should show up in finder on the MacBook Air. You can then replace the boot.efi files again.
 
Hennesie2000 said:
Turn both computers off. Connect the Mac Pro and the MacBook Air using a FireWire cable. Turn on the Mac Pro and hold in "T". Then turn on the MacBook Air. The Mac Pros hdd should show up in finder on the MacBook Air. You can then replace the boot.efi files again.
Click to expand...

Again, thank you

I'm not very computer literate, so please excuse me....

In looking at the macbook, I now think the connection is a thunderbolt??? a lightening icon with arrow? I guess I would need a thunderbolt to firewire cable? Would this still work? Could I connect the two using USB?

If it does work, and I'm able to get in, how would I find the boot.efi files, and what would I replace them with?

Thank you
 
Last edited:
dermdoc said:
Again, thank you

I'm not very computer literate, so please excuse me....

In looking at the macbook, I now think the connection is a thunderbolt??? a lightening icon with arrow? I guess I would need a thunderbolt to firewire cable? Would this still work? Could I connect the two using USB?

If it does work, and I'm able to get in, how would I find the boot.efi files, and what would I replace them with?

Thank you
Click to expand...


It needs to be either FireWire to FireWire or Thunderbolt to Thunderbolt. You won't be able to use target disk mode. I suggest you build an installer on a USB drive an run the installer to take you back to a working 10.10.0 or 1. Then install the update fix and run the 10.10.2 update again. Everything you need to know about replacing the boot.efi files is in the first post guides.

The other option is to buy a SATA to USB adapter. They are cheap and very handy to have.
 
kelmondo said:
Hi, Guys,
just letting you know i applied latest update to yosmite (10.10.2 ). to my drive the operating system then failed to boot so i just replaced efi boot (which i had saved) again and bang no problems . JUST STILL NO USB'S
Click to expand...

Funny, I tried that exact same approach last night when my update failed, and it did NOT work for me. I ended up having to reinstall back to 10.10.

Wonder why it worked for you but not for me?
 
I downloaded diskmaker and created a usb install thumb drive. I inserted the drive into the mac pro. Startup while holding the ALT key still gives me no video to work with.
 
jfalberti said:
I followed these instructions to the letter to create and format the Fusion drive.

http://www.macworld.com/article/2014011/how-to-make-your-own-fusion-drive.html

I originally had a 250 GB HDD volume in my Mac Pro. I bought and installed a 128 GB SSD and a 1 TB HHD. I then followed the instructions in the link above to create and format the new Fusion volume. Lastly, I downloaded Carbon Copy Cloner and used it to clone the original 250 GB drive to the new Fusion volume. Changed startup disk to the new Fusion drive and rebooted. Worked like a charm. Also, it is important to note that support for Fusion volumes didn't come out until OS X 10.8.2 Mountain Lion, so you MUST be running that, or a newer release for OS X. I kept the original 250 GB volume as an emergency boot disk, in case the Fusion drive failed. So far I have had no problems what so ever.
Click to expand...
I followed those too, I used mavericks to create the drive, I just didn't use CCC, I installed to the drive.
 
I feel like I am giving an acceptance speech at the Oscars. I really want to thank Tiamo, Hennesie2000, Pike, 666sheep, Tobyg and everyone who has contributed to this process.

I am 70 and have no idea of how all this works but I can follow instructions. I first installed Yosemite, when it was released, using Hennessie2000's instructions. Today I used 666sheep's script, restarted, and then installed 10.10.2 right from the App store. So my 2006 Mac Pro is now running Os 10.10.2.

I am in awe of you guys.

Thanks for keeping my old beast as up to date as it can be.
 
Last edited:
  • Like
Reactions: StructAural
So I tried again tonight to get to 10.10.2, this time using the recommended approach. The result this time was the computer wouldn't boot at all--not even into my Mavericks backup drive. I had to power everything down after about 15 minutes, then restart, at which point it picked up the Mavericks drive.

I had a look in the folders on the Yosemite drive where the boot-efi files are located, and they would appear to be the modded ones (you can tell by the file size differential). The pike file is also there, so it would seem clear that the script ran successfully, but I still can't boot.

Just to double-check, here are the steps taken:

1) DL 666sheep's file called PikeYoseFix-Black from post #2166.
2) Run the package script contained therein.
3) When prompted to restart, instead went to App Store and DL'd 10.10.2
4) Once app store download complete, allowed computer to reboot.

Seems pretty straight-forward and simple, but I'm not getting the result most others seem to. Last night I tried doing the upgrade from 10.10.1; tonight, it was from 10.10.

Any thoughts on what the issue might be?

Thanks.
 
lurkingbf said:
So I tried again tonight to get to 10.10.2, this time using the recommended approach. The result this time was the computer wouldn't boot at all--not even into my Mavericks backup drive. I had to power everything down after about 15 minutes, then restart, at which point it picked up the Mavericks drive.



I had a look in the folders on the Yosemite drive where the boot-efi files are located, and they would appear to be the modded ones (you can tell by the file size differential). The pike file is also there, so it would seem clear that the script ran successfully, but I still can't boot.



Just to double-check, here are the steps taken:



1) DL 666sheep's file called PikeYoseFix-Black from post #2166.

2) Run the package script contained therein.

3) When prompted to restart, instead went to App Store and DL'd 10.10.2

4) Once app store download complete, allowed computer to reboot.



Seems pretty straight-forward and simple, but I'm not getting the result most others seem to. Last night I tried doing the upgrade from 10.10.1; tonight, it was from 10.10.



Any thoughts on what the issue might be?



Thanks.
Click to expand...


You need to do the restart that you, for some reason, chose not to do. The launch daemon was installed but it wasn't running yet. So when you installed 10.10.2 it over wrote the boot.efi files again. With TobyG's original script he recommended rebooting twice but the second time wad just to verify that it was working by checking the timestamp on the boot.efi files.
 
White screen on install

I've tried re-formatting USB keys and re-downloading the file.

Clearly there is something else wrong.

Has anyone else run into this?
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back