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

dustinschings

macrumors 6502
Apr 8, 2011
279
72
I am still not clear what display you are using and how it is connected.

A DVI to VGA adapter merely runs the pins through that exist in DVI to carry analog video. To be a "VGA" signal, the display needs to be inputting via a VGA connection. As a for instance, Dell 24" displays let you choose from a variety of ports along the bottom. But you have to use the OSD to choose one. If I choose "VGA" and connect a DVI to VGA adapter on my card then run the VGA cable to the display, I am using VGA.

But if I put a DVI to VGA adapter on each end of the VGA cable, the only signal present will be VGA, there will be no DVI. Very few displays ever could pull the VGA from a DVI plug, so for most instances, this would not work.

If you use a DVI cable and the plug going into the display is DVI, then you are using the DVI part of signal.

If you use a DP or HDMI to DVI adapter, it is only passing through the SINGLE LINK part of DVI, just like the DVI was passing through the VGA. They are separate signals nested inside same plug. But using a DP or HDMI adapter only gives you single link, which means 1920x1200 is as big a display as it will run. Connecting to a 30" at 2560x1600 will either give you 1280x800 or a black screen.

Paying attention to which adapter, connecter, and cable you are using is important. It isn't like a water hose where any fitting will work as long as water comes out the end.

I am not quite sure if I am phrasing it wrong, so I will try to be more exact.

My monitor has DVI and VGA inputs. Originally, I was using a VGA cable from the display, and taking it to an adapter that would then plug into my DVI port on my GPU. No video from either card, with any configuration no matter what I tried from anybody here.

Then I thought that the adapter may have been the problem, so I removed the VGA cable and adapter all together, and connected my DVI CABLE from monitor DVI IN to my GPU DVI OUT (so, straight DVI). This allowed me to use my GT 610, yay! But, no GTX 750 no matter what I tried.

At this point, I am pretty sure this is just an incompatible version of the GTX 750 or something. If anyone can give me another idea, I will try it, but I am resigned to the fact that it will not work. I have quadruple checked that the proper Web Drivers are loaded, tried various different cables, tried the card in different slots, tried the card with no other expansion cards installed. Nothing out of my GTX 750.
 

MacVidCards

Suspended
Nov 17, 2008
6,096
1,056
Hollywood, CA
Get machine running on 610 with 750 in another slot.

Verify in System Profiler that the 750 shows up, and the Web Driver is loaded.

Hot plug the display with every port type you can try. If you have HDMI or DP to DVI, try those.

Definitely also try VGA. Make sure that you switch monitor to the inputs being tested. If 750 is one that has a power plug, have a cable connected. If after all this no output, it may in fact not work. Thanks for putting in the non-EFI thread.
 

toburr

macrumors newbie
Sep 5, 2015
1
0
I tried to install several unsupported versions of OS X on my Mac Pro 1,1 but no matter which method I use, after choosing the usb device in the boot manager the mac would just boot into os x lion as normally. I even tried sudo bless and using another usb port but it still won't work. Can anybody help me with?

toburr
 

dustinschings

macrumors 6502
Apr 8, 2011
279
72
I tried to install several unsupported versions of OS X on my Mac Pro 1,1 but no matter which method I use, after choosing the usb device in the boot manager the mac would just boot into os x lion as normally. I even tried sudo bless and using another usb port but it still won't work. Can anybody help me with?

toburr
I have read a lot about others with Mac pros who has issues with booting from USB. I don't have this issue, but have you tried a PRAM reset? Reboot your Mac and hold down Command Apple P R. Keep these keys held down until you hear the gong for the third time.

Here is a thread about it also:
http://apple.stackexchange.com/questions/162705/macbook-pro-not-detecting-bootable-usb-with-yosemite
 

donjames

macrumors member
Feb 20, 2015
89
7
Henderson, Texas
I tried to install several unsupported versions of OS X on my Mac Pro 1,1 but no matter which method I use, after choosing the usb device in the boot manager the mac would just boot into os x lion as normally. I even tried sudo bless and using another usb port but it still won't work. Can anybody help me with?

toburr
HI,

I wrote some instructions on my website here: http://donaldbjames.com/yosemiteonmacpro.html

Let me know if it works. I updated the link to the pre-patched installer. It now works.
Regards,

Don James
 
Last edited:

cw48494

macrumors regular
Jun 17, 2015
172
46
Finally got around to installing Yosemite on my 1,1 and I had no issues whatsoever. Installed Yosemite on SSD via compatible mac, ran Pikes, restarted twice and threw it down in the 1,1 it works well.
 

Helchez

macrumors newbie
Sep 8, 2015
3
0
Alright, I have been fighting this 10.10.5 update for 3 days now with no success. I previously installed the pikeyose script and was able to update to 10.10.4 with no issues. So after hearing most people had no issues 10.10.5, I decided to give it a go. On reboot I got the folder with the question mark icon.

So I first tried booting into my second hard drive which has an install of 10.7.5. I copied the black boot.efi file to both the /System/Library/CoreServices and /usr/standalone/i386 folders. I then used the chflags uchg command to lock both efi files and tries to reboot to my Yosemite drive. No luck.

I also tried booting to my USB Yosemite install drive and coping the boot.efi from there but I keep getting errors trying to copy the boot.efi to the i386 folder. I'm getting operation not permitted.

I also tried repairing permissions on the drive while booted into the uab drive, bit I get errors trying to repair the permissions as well.

Any help will be appreciated.
 

Helchez

macrumors newbie
Sep 8, 2015
3
0
Alright, I have been fighting this 10.10.5 update for 3 days now with no success. I previously installed the pikeyose script and was able to update to 10.10.4 with no issues. So after hearing most people had no issues 10.10.5, I decided to give it a go. On reboot I got the folder with the question mark icon.

So I first tried booting into my second hard drive which has an install of 10.7.5. I copied the black boot.efi file to both the /System/Library/CoreServices and /usr/standalone/i386 folders. I then used the chflags uchg command to lock both efi files and tries to reboot to my Yosemite drive. No luck.

I also tried booting to my USB Yosemite install drive and coping the boot.efi from there but I keep getting errors trying to copy the boot.efi to the i386 folder. I'm getting operation not permitted.

I also tried repairing permissions on the drive while booted into the uab drive, bit I get errors trying to repair the permissions as well.

Any help will be appreciated.


Okay, I guess I just needed to get frustrated enough to post a request for help. On what would have been about the 16th attempt, I was finally able to boot to my Yosemite drive again. In case it helps anyone else I will list my steps. This will probably only help other people with a secondary drive or partition that still boots.

I booted into my old 10.7.5 drive.

Mount Yosemite Installer USB drive.

Copy the boot.efi file from the usr/standalone/i386 folder on the USB drive to the Desktop.

Navigate to the boot.efi file on your Yosemite hard drive. To help, in my example the drive name is Macintosh HD Yosemite: /Volumes/Macintosh\ HD\ Yosemite/System/Library/CoreServices/boot.efi
(I just used finder to navigate to this file, but it can be done in Terminal)


This file was locked for me, so I had to unlock it. chflags nouchg is the command to unlock a file:
Open Terminal and drag the boot.efi file into terminal.
Terminal will show the path to the file.
Use the arrow key to move the cursor to the front of the path.
Enter this command, then a space before the path to your boot.efi file: chflags nouchg
Example: chflags nouchg /Volumes/Macintosh\ HD\ Yosemite/System/Library/CoreServices/boot.efi

Now, that the file is unlocked, drag the existing boot.efi file from the CoreServices folder to the trash.

Copy the boot.efi file that you copied to the Desktop into the System/Library/CoreServices/ folder.

Next, re-lock the file. chflags uchg is the command to lock a file:
Open Terminal and drag the boot.efi file into terminal.
Terminal will show the path to the file.
Use the arrow key to move the cursor to the front of the path.
Enter this command, then a space before the path to your boot.efi file: chflags uchg
Example: chflags uchg /Volumes/Macintosh\ HD\ Yosemite/System/Library/CoreServices/boot.efi

Next, enable hidden files:
In Terminal enter this command defaults write com.apple.finder AppleShowAllFiles YES

Now, navigate to /Volumes/Macintosh\ HD\ Yosemite/usr/standalone/i386/boot.efi

Drag the boot.efi file to the trash.

Copy the boot.efi file that you copied to the Desktop into the usr/standalone/i386/ folder.

Do not lock this file.

I then emptied the trash, probably not needed, but can't hurt.

Finally, I rebooted while holding Option.

I selected my Yosemite driver and booted...finally.

In the end, I am not entirely sure what I did differently on this attempt. I was locking the boot.efi file in the i386 folder before. Also, I tried a new copy of the black boot.efi I downloaded yesterday and the boot.efi file from the System/Library/CoreServices folder on my USB Yosemite Install driver before. So it could be the copy of the boot.efi from the i386 folder on the USB drive or not locking the boot.efi in the i386 folder. Maybe both, but this procedure worked for me.

I mainly wrote this long, response because I spent a while going through 100+ pages and never found a procedure that worked for me or was 100% correct, as far as paths or commands. I'm sure I probably got something wrong as well, but hopefully this will someone else.
 

sumer

macrumors regular
Mar 2, 2015
130
0
Toronto
Okay, I guess I just needed to get frustrated enough to post a request for help. On what would have been about the 16th attempt, I was finally able to boot to my Yosemite drive again. In case it helps anyone else I will list my steps. This will probably only help other people with a secondary drive or partition that still boots.

I booted into my old 10.7.5 drive.

Mount Yosemite Installer USB drive.

Copy the boot.efi file from the usr/standalone/i386 folder on the USB drive to the Desktop.

Navigate to the boot.efi file on your Yosemite hard drive. To help, in my example the drive name is Macintosh HD Yosemite: /Volumes/Macintosh\ HD\ Yosemite/System/Library/CoreServices/boot.efi
(I just used finder to navigate to this file, but it can be done in Terminal)


This file was locked for me, so I had to unlock it. chflags nouchg is the command to unlock a file:
Open Terminal and drag the boot.efi file into terminal.
Terminal will show the path to the file.
Use the arrow key to move the cursor to the front of the path.
Enter this command, then a space before the path to your boot.efi file: chflags nouchg
Example: chflags nouchg /Volumes/Macintosh\ HD\ Yosemite/System/Library/CoreServices/boot.efi

Now, that the file is unlocked, drag the existing boot.efi file from the CoreServices folder to the trash.

Copy the boot.efi file that you copied to the Desktop into the System/Library/CoreServices/ folder.

Next, re-lock the file. chflags uchg is the command to lock a file:
Open Terminal and drag the boot.efi file into terminal.
Terminal will show the path to the file.
Use the arrow key to move the cursor to the front of the path.
Enter this command, then a space before the path to your boot.efi file: chflags uchg
Example: chflags uchg /Volumes/Macintosh\ HD\ Yosemite/System/Library/CoreServices/boot.efi

Next, enable hidden files:
In Terminal enter this command defaults write com.apple.finder AppleShowAllFiles YES

Now, navigate to /Volumes/Macintosh\ HD\ Yosemite/usr/standalone/i386/boot.efi

Drag the boot.efi file to the trash.

Copy the boot.efi file that you copied to the Desktop into the usr/standalone/i386/ folder.

Do not lock this file.

I then emptied the trash, probably not needed, but can't hurt.

Finally, I rebooted while holding Option.

I selected my Yosemite driver and booted...finally.

In the end, I am not entirely sure what I did differently on this attempt. I was locking the boot.efi file in the i386 folder before. Also, I tried a new copy of the black boot.efi I downloaded yesterday and the boot.efi file from the System/Library/CoreServices folder on my USB Yosemite Install driver before. So it could be the copy of the boot.efi from the i386 folder on the USB drive or not locking the boot.efi in the i386 folder. Maybe both, but this procedure worked for me.

I mainly wrote this long, response because I spent a while going through 100+ pages and never found a procedure that worked for me or was 100% correct, as far as paths or commands. I'm sure I probably got something wrong as well, but hopefully this will someone else.


I'm glad it worked out in the end for you. Locking the boot efi shouldn't matter as mine isn't locked and things are fine.

I actually re-installed Yosemite on my mac pro 1.1 today. I've been using my other tower that runs Yosemite and el cap natively. Anyway I used the TDM method installed 10.10.4. Booted back into the supported mac mounted the unsupported mac's HD then replaced the boot efi's. I used batCHmod to change permissions on the locked file in order to replace it. once I did that i was able to boot no problem. i set it up then ran pikes' Yosefix rebooted twice and updated to 10.10.5 without any issue. Took me about half an hour from start to finish:) When I first started on this journey
I used SFOTT then moved onto the pre patched Yosemite installer. There are few ways to get things done it's just finding what works best.

Cheers
 

donjames

macrumors member
Feb 20, 2015
89
7
Henderson, Texas
This first post is usually updated with recent summarized information.


Simply looking to download the Piker-Alpha macosxbootloader? Links:
________________________________________________________________

If you have OS X Yosemite up and running on your 2006/2007 Mac Pro with Pike's boot loader, this is how to make sure OS X Yosemite updates (like the OS X Yosemite 10.10.2 Update) don't break your ability to boot Yosemite:
  1. prerequisite: an installed and working OS X Yosemite system with Pike's boot.efi
  2. install the PikeYoseFix script
  3. reboot twice as the second boot is when the PikeYoseFix script is fully installed and executes!
Once the PikeYoseFix script is installed, it does not need to be installed again and it should be safe to install future OS X updates. It automatically runs at every system shutdown re-copying Pike's boot.efi to the proper locations just in case something like an OS X update overwrote it.

If you don't have PikeYoseFix script installed, or if you have OS X installed on a Fusion drive where the PikeYoseFix script doesn't work properly, you should disable "Install OS X updates" and "Install system data files and security updates" in System Preferences > App Store so that OS X doesn't automatically install any future updates that may overwrite Pike's boot.efi.

Lastly, if Pike's boot.efi boot loader was overwritten after an OS X update because you didn't take the precaution of installing the PikeYoseFix script, and you have a folder with question mark on boot, here is a link to instructions on how to restore Pike's boot.efi to restore the ability to boot.
________________________________________________________________

If you find Pike's boot loader valuable in keeping your 2006/2007 Mac up-to-date, please consider donating to him as a thank you and to encourage future continued development. He's had a tough time with hardware and been developing all this time without access to an actual 2006/2007 Mac Pro! His donation page is in euros, where €20 is around $23 USD, and PayPal will show the actual conversion used at time of donation. I know any amount is highly appreciated.

Even if you don't donate, you may consider simply thanking him via a comment on his blog, as he's done a lot of work without asking for anything in return or benefiting from this project. Thanks Pike!


How can these Macs run Yosemite?

Apple does not support OS X Yosemite on the original 2006/2007 Mac Pro and 2006 Xserve. These 64-bit Mac Pros and Xserves have EFI32 firmware and can't natively boot OS X Yosemite "out-of-the-box", but are easily capable of running it with a different boot loader. Once a new boot loader is used to launch the native 64-bit Yosemite kernel, OS X 10.10 boots and works normally exactly as it does on a 2008 Mac Pro or newer with EFI64 firmware.


Background:

OS X 10.6 Snow Leopard was the first OS X version with optional support for a 64-bit kernel, allowing booting either with a 32-bit or 64-bit kernel. However, Apple did not support booting the 64-bit kernel in Macs that shipped with EFI32 firmware, even if they had 64-bit processors capable of running the 64-bit kernel. When Apple dropped the 32-bit kernel entirely from OS X, starting with OS X 10.8 Mountain Lion, EFI32 Macs no longer had an Apple-supported mechanism to boot newer OS X versions.

The last version of OS X officially supported by Apple on the original 2006 Mac Pro MA356LL/A (MacPro1,1), 2007 Mac Pro (8-core) MA1186/A (MacPro2,1) and Xserve (Late 2006) MA409LL/A (Xserve1,1) models was OS X 10.7 Lion, and then only when booted with a 32-bit kernel due to their EFI32 firmware. However, these Macs were the most powerful and upgradable EFI32 models and have a 64-bit architecture, so the user community has been keeping them running with 64-bit kernels and newer OS X releases using a variety of methods.


Two approaches that can be used to boot OS X 10.10 Yosemite on unsupported Mac Pro models:


Piker-Alpha bootloader (preferred approach)

This method, a fork of boot.efi boot loader that thunks EFI64 calls from the 64-bit OS X kernel to the EFI32 firmware.

Additional information about Pike's boot.efi is available at Pike's blog, Universum. There are two variations available, one with a legacy light grey background/dark grey Apple logo boot screen boot.efi that blends with the native EFI32 pre-boot screen (2008-2012 Mac Pro-style), and a new black background/white Apple logo boot screen boot.efi (2013 Mac Pro-style).

With Pike's boot.efi, holding Command-R to start the OS X Recovery System that gets installed with Yosemite is supported, although holding Option/Alt at boot and selecting the "Recovery HD" may not work until the OS X install image in the Recovery system is updated with Pike's boot loader. 2006/2007 Mac Pros do not support Internet Recovery.

After an initial report of failure booting from a Fusion Drive, there has since been a report of success so Fusion Drives may have to be created manually before installing Yosemite.

While this method is preferred because it's a native EFI boot, there is some risk is that installing future Yosemite updates could overwrite Pike's EFI32 boot.efi if Apple were to update the stock EFI64 boot.efi. This would be unusual, but it has happened in a few previous OS X updates and is the case with the 10.10.2 update. If this were to happen, the system would no longer be natively bootable on a 2006/2007 Mac Pro until it had Apple's stock boot.efi replaced with Pike's boot.efi again. A simple approach to help protect against this is PikeYoseFix, a launch daemon that re-copies the EFI32 boot.efi file to proper locations at shutdown.


Hackintosh” boot loader

This method uses a legacy mode (CSM) boot loader to load the stock 64-bit OS X kernel while emulating EFI NVRAM. Note that the Xserve doesn't support legacy/PC BIOS emulation mode, so it can't directly use this approach.

The Chameleon boot loader was used in MacEFIRom's original approach to booting the 64-bit kernel on the 2006/2007 Mac Pro. Chameleon has since been updated to properly support the Yosemite kernel, and the Clover boot loader was always capable of booting Yosemite since it boots using the stock OS X boot.efi boot loader which in turn loads the Yosemite kernel. After an initial successful report here which used Clover, instructions were posted on how to use Clover to install and boot Yosemite DP1 along with an initial script. A full Mac Pro hardware configuration for Clover to support audio and the ODD SATA ports has been posted.

Booting with Chameleon/Clover is sometimes preferable in configurations with otherwise-unsupported hardware that needs to be initialized and usable in OS X, such as unsupported graphics cards or HDMI audio in certain situations.


Support for Handoff in Yosemite to allow AirDrop, Continuity and Instant Hotspot with iOS 8 devices:

The original Airport Extreme (802.11a/b/g/draft-n Wi-Fi) and Bluetooth 2.0+EDR options from Apple don't support Handoff. Several vendors, including MacVidCards, sell new add-on hardware kits to retrofit older Mac Pros with 802.11ac Wi-Fi and Bluetooth 4.0 LE that work in 2006/2007 Mac Pros to allow Handoff. There have been reports of needing to sign out of iCloud and then sign in again after replacing WiFi and Bluetooth hardware to enable Handoff.

There has been a report of an OEM Bluetooth 2.0+EDR card causing a conflict with USB devices. If you experience issues with the built-in USB ports under Yosemite, you may also consider removing or upgrading your Bluetooth card.

In Yosemite, both phone calls and SMS from OS X with an iPhone work with a 2006/2007 Mac Pro and are not dependent on OS X Handoff support.


Unsupported original legacy graphics cards vs. Yosemite-supported graphics cards:

Yosemite does not include 64-bit kernel extension device drivers for the original NVIDIA GeForce 7300 GT, ATI Radeon X1900 XT, and NVIDIA Quadro FX 4500 PCIe graphics cards that shipped with these Mac Pros, nor the ATI Radeon X1300 that shipped with the Xserve (Late 2006), so they do not work properly in Yosemite. These graphics cards display issues such as a very sluggish GUI with no QE/CI support, no framebuffer support (for DVD Player, Geekbench and other programs), graphics artifacts, mouse tearing, inability to change resolutions, bad refresh rates, and other system instabilities. If you need normal graphics support in Yosemite, you will need a newer PCIe graphics card, with popular options being the Apple ATI Radeon HD 5770 Graphics Upgrade Kit for Mac Pro, SAPPHIRE HD 7950 3GB GDDR5 MAC Edition, or many different options of stock and Mac-"flashed" PC cards.

Many, but not all, modern stock non-flashed PC graphics cards with AMD (for OpenCL/OpenGL support) or Nvidia chipsets (for CUDA/OpenCL/OpenGL support) work "plug and play" with Yosemite in 2006/2007 Mac Pros, although the display will remain off until after the OS X Desktop initializes. This means you won't see anything during the boot process.

Compatible properly-Mac-flashed PC cards offer two benefits over stock non-flashed PC cards: allowing a normal boot screen just like a Mac-specific graphics card, and better compatibility in OS X with the card's capabilities/performance/ports. Most, but not all, Mac-flashed ATI/AMD cards have EBC firmware that work in all PCIe-based 2006-2012 Mac Pro models with either EFI32 or EFI64. All newer Mac-flashed Nvidia cards have EFI64 firmware and will act like non-flashed PC cards with no boot screens in EFI32-based 2006/2007 Mac Pros, except for older Mac-flashed Nvidia GeForce 8800 GT/9800 GT/GT 120 cards with EFI32 firmware.
Note also that the 2006/2007 Mac Pro has PCIe 1.1 expansion slots, with the bottom double-wide slot capable of being configured to use a maximum 2.5 GT/s link speed when configured as a x16 lane graphics slot. Yosemite's Expansion Slot Utility, located in /System/Library/Core Services, supports the 2006-2007 Mac Pro to configure the number of lanes available in each slot. PCIe 2.0/3.0 cards that can run at 5.0 GT/s link speed in 2008-2012 Mac Pros can work in 2006/2007 Mac Pros, but only with a PCIe 1.1 maximum 2.5 GT/s link speed.

None of these options are officially supported in these Mac Pros by AMD, Apple, or Nvidia, but can work with either the Piker-Alpha or Chameleon/Clover boot loaders.


iMessage/FaceTime note:

Regardless of approach used, most users cannot initially login to iMessage or FaceTime using their Apple ID from their Mac Pro after installing Yosemite as a security precaution. When trying to login, they receive an iMessage Registration validation code. The solution is to contact Apple support, provide the Mac Pro's serial number, explain that Yosemite was installed and that iMessage isn't working and provide the validation code. Apple then unblocks the Mac Pro, allowing iMessage and FaceTime login immediately and in the future without other issues.
HI,

The link to the pre-patched Yosemite installer has changed. The new one is
https://mega.nz/#!q1IRFJzK!GUinePUGF3jAAu3oUym-GHBC9doWRTU1p6nnkXkJFdQ

Just thought you might want to know.

Regards,

Don James
 
  • Like
Reactions: electonic

Helchez

macrumors newbie
Sep 8, 2015
3
0
I'm glad it worked out in the end for you. Locking the boot efi shouldn't matter as mine isn't locked and things are fine.

I actually re-installed Yosemite on my mac pro 1.1 today. I've been using my other tower that runs Yosemite and el cap natively. Anyway I used the TDM method installed 10.10.4. Booted back into the supported mac mounted the unsupported mac's HD then replaced the boot efi's. I used batCHmod to change permissions on the locked file in order to replace it. once I did that i was able to boot no problem. i set it up then ran pikes' Yosefix rebooted twice and updated to 10.10.5 without any issue. Took me about half an hour from start to finish:) When I first started on this journey
I used SFOTT then moved onto the pre patched Yosemite installer. There are few ways to get things done it's just finding what works best.

Cheers

I think it may have been more of a permissions issue, but I didn't repair/modify permissions at all the time it worked. What really confused me is that I had Pikes Yosefix installed and was able to update to 10.10.4 without an issue. Not sure what caused the script to fail or stop working.
 

Joe1974

macrumors newbie
Sep 14, 2015
20
0
Romania
Hi mac lovers :) Im new here, and i glad to see this helful mac forum.
I have a big problem. I bout a second hand mac from ebay.uk two weeks ago. http://www.ebay.co.uk/itm/252058297464
Apple Mac Pro 8 Core Intel Xeon 2.33Ghz 8GB RAM 250GB HD nVidia 8800GT 512MB j.
yesterday i updated the mac.. and the display start to flashing and freezing.. i restarted and won't boot anymore in any mode.. only with the option key, i see the HD Macintos and Recovery 10.10.5 , bot if i click does not respond..
I found this forum, and i folloved the instructions from the 1 page , i installed the pached yosemite to usb flash drive 8 giga with my laptop apple macbook pro late 2010, i used the disk utility to restore pached yosemite to usb drive.
and now want to install, the install starting but in 30% starting to flashing the screen, and it's frozing..
Please help me , what ca i do :(
 

Attachments

  • 12011198_1079020885449378_7130468386348449614_n.jpg
    12011198_1079020885449378_7130468386348449614_n.jpg
    38.6 KB · Views: 116

Ant3000

macrumors 6502
Jul 20, 2015
374
46
UK
Did you install Yosefix before updating? Or had it been installed previously? Have you checked the graphic card is compatible with Yosemite 10.10.5? Not clear why you updated the OS in the way described if it was already running 10.10.4 when you bought it. You could have just installed Yosefix - if not already installed, and downloaded the 10.10.5 update from Apple.
 

Joe1974

macrumors newbie
Sep 14, 2015
20
0
Romania
Did you install Yosefix before updating? Or had it been installed previously? Have you checked the graphic card is compatible with Yosemite 10.10.5? Not clear why you updated the OS in the way described if it was already running 10.10.4 when you bought it. You could have just installed Yosefix - if not already installed, and downloaded the 10.10.5 update from Apple.
I did not instaled Yosefix, I do not know if it was instaled previously. And
I don't know that I should not install new version yosemite :(
 

donjames

macrumors member
Feb 20, 2015
89
7
Henderson, Texas
Hi mac lovers :) Im new here, and i glad to see this helful mac forum.
I have a big problem. I bout a second hand mac from ebay.uk two weeks ago. http://www.ebay.co.uk/itm/252058297464
Apple Mac Pro 8 Core Intel Xeon 2.33Ghz 8GB RAM 250GB HD nVidia 8800GT 512MB j.
yesterday i updated the mac.. and the display start to flashing and freezing.. i restarted and won't boot anymore in any mode.. only with the option key, i see the HD Macintos and Recovery 10.10.5 , bot if i click does not respond..
I found this forum, and i folloved the instructions from the 1 page , i installed the pached yosemite to usb flash drive 8 giga with my laptop apple macbook pro late 2010, i used the disk utility to restore pached yosemite to usb drive.
and now want to install, the install starting but in 30% starting to flashing the screen, and it's frozing..
Please help me , what ca i do :(

Try resetting the nvram: https://support.apple.com/en-us/HT204063

See if it will boot.

Regards,
Don James
Henderson, Texas USA
 

Ant3000

macrumors 6502
Jul 20, 2015
374
46
UK
I did not instaled Yosefix, I do not know if it was instaled previously. And
I don't know that I should not install new version yosemite :(
On the ebay link it says it is running 10.10.4 - depending on how this was achieved you may need to install Yosefix (referred to in the 1st post of this thread). This ensures that the updated files required to enable Yosemite to run on your Mac Pro are not overwritten by any future Apple update. How did you perform the update that seems to have caused the problem?
 

Joe1974

macrumors newbie
Sep 14, 2015
20
0
Romania
It was normal update from the internet ..
I thinking about my NVIDIA GF 8800 GTS 512 MB OC DUAL DVI, maybe is Dead ?? How can make a test to be shore ?
 
Last edited:
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.