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

MacVidCards

Suspended
Nov 17, 2008
6,096
1,056
Hollywood, CA
thank you for your offer, very kind and generous! I bought the GT 120 from you. the problem is that in Linux or during installation of Windows or while testing OS X (before the KEXT is loaded, or in single user mode) the fan is not spinning. after a few minutes the GFX card shuts off (or at least the screen goes dark) and the card also gets very hot. the fan is connected using 4 wires, the card has 2 DVI connectors.

Today I will watch the fan behavior on a 4 wire GT120 whilst booting. I had a 2 wire version in last night, it was whining so loud I could hear it in next room, but I think they just fire up as soon as PCIE bus gets power. As the 4 wire version uses logic to control speed, it may not fire at boot, I will know tonight.

To all the folks reporting trouble installing El Cap on older EFI32 machines, I wish to make 2 things clear.

1. This thread has "Mac Pro" in the title. I and others who have tried with other EFI32 Macs have found a huge road block. The USB ports work from EFI at boot but at some point El Cap disables them. I currently have the only non-MP EFI32 machine running El Cap on the planet, and it required a huge kludge that nobody would live with. There is another thread in this section about "El Cap on unsupported machines" where I have this detailed. So in addition to no GOU acceleration, you can't use a mouse, keyboard, or Bluetooth. There may eventually be a solution but right now there isn't. Those other EFI32 machines may have reached the end of the OSX road. Removing the right kexts might allow EFI drivers to allow basic USB function, someone should try.

2. Yesterday I updated my two EFI32 Macs from GM to Final release. It was, as I have mentioned before, crazy easy. But I do the install on newer machines, then boot those newer machines into 10.9 to replace the boot.efi files in all 3 places, then move the drive to the EFI32 machines. I did hit one snafu yesterday that may explain some failure reports. I dragged and dropped the boot.efi to the needed places and got no "it didn't happen" messages. But one of the drives wouldn't boot, it was a SATA drive that had been internally connected. The PCIE SSD and USB drives had no issue. When I went and looked the locked boot.efi hadn't been switched, even though I wasn't told this at the time. Here is the easy way to tell. SIZE MATTERS. The EFI32 one these guys built is 314K, the "real" one is 605K (or so). If you check the size and one is 600+ K, you didn't successfully switch it. I will recheck sometime if this was entirely dependent on whether it allowed on external but not on internal. So my advice to those who think they replaced the files it machine won't boot to El Cap, check the size of the boot.efi files. If they are 600+ K in size you didn't switch them. I had to use terminal to unlock that one, then switching it out worked. That was literally the only trouble I had.

It can be done.
 

Razieln64

macrumors newbie
Oct 1, 2015
8
0
This version boots the patched Installer (Release-version 30-Sept-2015) on a MBP2,2 - but when the Installer copies the files to the destination the MBP2,2 restarts suddenly after 2 minutes.

When the black progress bar (grey Boot.efi) has reached 100 percent (identical to the end of verbose mode) then a grey progress bar appears with firm 10 percent until later on the OSX Welcome screen appears.


Tried again making an installer with this new boot.efi. Also replaced bootbase.efi. Installs fine, but crashes on startup so it reboots my Yosemite drive.
 

RX2904

macrumors member
Aug 26, 2014
52
1
Hi.

I was planning to upgrade to El Cap tomorrow. I have the same card ATI 5770. So, no issues? Did you have to do anything else than replace the boot.efi in both locations?

Thanks!



OK, got OS X El Capitan running on my good old Mac Pro 1,1 flashed to 2,1.

As was mentioned before by Peter Holbrook, you really need an alternate startup drive from which to select Startup Disk from to boot OSXEC. The Yosemite Install up on Mega worked just fine for me for this purpose.

I've got it running with an ATI 5770 for now, seems respectably.. snappy. :)
 

RX2904

macrumors member
Aug 26, 2014
52
1
Hi!

I gotta admit I don't know a lot about graphics cards but it looks like if I want to run El Cap with all the bells and whistles I need to upgrade from my 5770 to a 7950.

I made an eBay search for a used one, but there's like different kinds. I mean they look completely different from each other. Could you please give me a tip what I'm looking for exactly?

I'm already running 10.10.5 on my 2,1 MacPro.

Thank you!


Yes, Metal works on any 7xxx card.
 

Sko

macrumors 6502
Oct 17, 2009
285
59
Germany
For me, modifying the installer doesn't work on an 8 GB stick. There's not enough space, just some hundred MB short. Am I missing something?
 

Razieln64

macrumors newbie
Oct 1, 2015
8
0
Use another working OS install to look at the 2 boot.efi locations. Are they 605Kb or 314Kb?

If 605, replace them.

Hi,

I got it working with the latest boot.efi . Somehow the installer messes up things. So I just made a fresh install using my supported MBP on an external USB hard drive. After the installation I replaced both boot.efi files. I plugged the hard drive in my Mac Pro and it worked.

I am typing this message on my Mac Pro 1,1 running El Capitan.

Since I now know it works, I'd like to try to upgrade from my Yosemite install so I can keep my other applications.

Will let you know if it works.
 

atucker922

macrumors newbie
Oct 1, 2015
2
0
I did pretty much the same as Razieln64. Created installer the same way as Yosemite and performed a clean install. Afterwards I booted back into cloned install, unlocked the boot.efi file again, and replaced in both core services and i386. Rebooted and I am currently restoring from cloned drive.
 

gio64

macrumors member
Aug 22, 2005
44
0
Hi!

I gotta admit I don't know a lot about graphics cards but it looks like if I want to run El Cap with all the bells and whistles I need to upgrade from my 5770 to a 7950.

I made an eBay search for a used one, but there's like different kinds. I mean they look completely different from each other. Could you please give me a tip what I'm looking for exactly?

I'm already running 10.10.5 on my 2,1 MacPro.

Thank you!
I picked up a flashed MSI 7950 with 3 gigs of ram on kijijii. It works amazingly well. Boot screen, Metal and Windows too. The improvement from the 5770 was huge. Only noticeable "issue" is that the fans on the card get pretty noisy if you start pushing the card.
 

gio64

macrumors member
Aug 22, 2005
44
0
I had reported success a while back running El Capitan on MacPro 1.1. Somehow, I had an issue with the boot drive. I am not sure what happened, but it started giving me an error regarding ACPI (somebody else might have reported that in this very thread). I had to reinstall El Capitan after wiping the drive. I then reinstalled the two boot.efi and I'm back in business. Is there anyway to prevent writing/overwriting of these? I know that there was the Yosefix, but I am not aware of one existing for El Capitan. Any word on it being developed?
 
Last edited:

atucker922

macrumors newbie
Oct 1, 2015
2
0
I picked up a flashed MSI 7950 with 3 gigs of ram on kijijii. It works amazingly well. Boot screen, Metal and Windows too. The improvement from the 5770 was huge. Only noticeable "issue" is that the fans on the card get pretty noisy if you start pushing the card.

I Have been using the sapphire radeon hd 7950 mac edition. Works like a charm, and no issues.
 

Razieln64

macrumors newbie
Oct 1, 2015
8
0
I did pretty much the same as Razieln64. Created installer the same way as Yosemite and performed a clean install. Afterwards I booted back into cloned install, unlocked the boot.efi file again, and replaced in both core services and i386. Rebooted and I am currently restoring from cloned drive.

I tried updating my Yosemite install through my MBP and it didn't work either. I replaced the boot.efi files and it still rebooted into my Yosemite clone. So I guess my rebooting was related to a bad install of Yosemite or CS5 (there were lots of errors related to After Effects in the log). Luckily I kept my original drive with the clean install that worked, so I just cloned it to my SSD. I am currently copying back all my data from my Yosemite drive. I'll still keep it around just to be safe.

El Capitan runs really well compared to Yosemite. I still have some graphics glitches when the OS starts showing the desktop, but this may be because I have 3 monitors.

Also I had to configure the sound in the control panel. Digital out was set by default.
 

MacVidCards

Suspended
Nov 17, 2008
6,096
1,056
Hollywood, CA
I tried updating my Yosemite install through my MBP and it didn't work either. I replaced the boot.efi files and it still rebooted into my Yosemite clone. So I guess my rebooting was related to a bad install of Yosemite or CS5 (there were lots of errors related to After Effects in the log). Luckily I kept my original drive with the clean install that worked, so I just cloned it to my SSD. I am currently copying back all my data from my Yosemite drive. I'll still keep it around just to be safe.

El Capitan runs really well compared to Yosemite. I still have some graphics glitches when the OS starts showing the desktop, but this may be because I have 3 monitors.

Also I had to configure the sound in the control panel. Digital out was set by default.

I would be willing to bet money (if it wasn't banned here at MR) that one of your boot.efi files was still 605Kb.

I have made more then 10 El Cap boot drives since the Beta program started, each time worked fine, and when I did have a bad one it was a single boot.efi that hadn't changed, despite me not seeing a dialog that it had failed to replace existing one.
 

PowerMac G4 MDD

macrumors 68000
Jul 13, 2014
1,900
277
Issue: I am now booted into El Capitan on my MBP (the HDD sits in my Mac Pro and is being read through Target Disk Mode). I was all ready to put the efi files into their correct locations, but I am NOT able to write to the i386 folder (and likely the other location as well). I unlocked the settings with my password, but when I select 'allow everyone to read and write,' it says that I don't have permission to do so... so, now, I've hit a wall. Would you know what to do in this instance? Hopefully you're there; I have everything running right now and need to place the boot efi in.
 

PeterHolbrook

macrumors 68000
Sep 23, 2009
1,625
441
I am NOT able to write to the i386 folder (and likely the other location as well)
That will work if you boot from another disk. Although you won't have the Finder in that setting, my advice is that you use the Terminal from the Installer media. In that setting, there's no rootless (no SIP) and everything you do will be as root. You don't even need "sudo" (there's no sudo), since you are already the "super user".
 

PowerMac G4 MDD

macrumors 68000
Jul 13, 2014
1,900
277
Can you use Terminal from the installer media anymore? I wouldn't be surprised if Apple left that feature out in El Capitan; they keep dumbing-down things like that. Upon installation, I saw nothing but the progress bar.
 

PeterHolbrook

macrumors 68000
Sep 23, 2009
1,625
441
Can you use Terminal from the installer media anymore? I wouldn't be surprised if Apple left that feature out in El Capitan; they keep dumbing-down things like that. Upon installation, I saw nothing but the progress bar.
Of course you can! I did it myself yesterday. And, as I say, it has no restrictions whatsoever.
 

PowerMac G4 MDD

macrumors 68000
Jul 13, 2014
1,900
277
Of course you can! I did it myself yesterday. And, as I say, it has no restrictions whatsoever.

Then I suppose I'll have to go through the installation process again... :-/ Where can you access it? All I saw was a grey screen. (BTW, it's the same command, right? The well-known one to disabling 'rootless.'?) Others have booted into recovery mode, and I need to find out how to do that correctly. (I'm reading my Mac Pro's HDD with TDM.)
 

mikeboss

macrumors 68000
Aug 13, 2009
1,524
813
switzerland
Tried again making an installer with this new boot.efi. Also replaced bootbase.efi. Installs fine, but crashes on startup so it reboots my Yosemite drive.

the problem is that the installer isn't using one of the boot.efi files on the volume anymore but takes it from
/Volumes/Install\ OS\ X\ El\ Capitan/System/Installation/Packages/Essentials.pkg

we would have to modify the Essentials.pkg in order to get a fully working clean installation procedure.
 

AppleTools

macrumors member
Dec 12, 2009
76
12
Success! And it works with a humble ATI 2600XT :D
Capi.png

Process:

1 - Made a bootable El Capi Installer (I did not modified anything on the installer)
2 - Installed from a newer tower (I swapped the drive but I guess target mode would've worked too)
3 - Used the rootless command to gain access to locked EFI (sudo nvram boot-args="rootless=0 kext-dev-mode=1")
4 - Replaced EFI files on both locations (cores services and i386)
5 - Repaired the disk (I used the new Disk Utility which does not have "repair permissions" button, just "repair")
6 - Replaced the drive on the old tower and that was it!

Aye Aye Captain!
 

mikeboss

macrumors 68000
Aug 13, 2009
1,524
813
switzerland
commit 81fa8702089b74dd292349865c6f1c4721eefd44: boots normal (both, El Capitan & Recovery HD) NO debug output.

peter, what about a boot.efi developers thread? it starts getting to be a bit crowdy in here with all the posts about installing El Capitan now.
 
  • Like
Reactions: VAGDesign

AppleTools

macrumors member
Dec 12, 2009
76
12
Issue: I am now booted into El Capitan on my MBP (the HDD sits in my Mac Pro and is being read through Target Disk Mode). I was all ready to put the efi files into their correct locations, but I am NOT able to write to the i386 folder (and likely the other location as well). I unlocked the settings with my password, but when I select 'allow everyone to read and write,' it says that I don't have permission to do so... so, now, I've hit a wall. Would you know what to do in this instance? Hopefully you're there; I have everything running right now and need to place the boot efi in.

Try this terminal command and see if you can gain access to those files:

sudo nvram boot-args="rootless=0 kext-dev-mode=1"

Remember to use Disk Utility of repair the volume after moving the new files in place.
 

PowerMac G4 MDD

macrumors 68000
Jul 13, 2014
1,900
277
Try this terminal command and see if you can gain access to those files:

sudo nvram boot-args="rootless=0 kext-dev-mode=1"

Remember to use Disk Utility of repair the volume after moving the new files in place.

Nothing happened. Am I supposed to reboot or something?
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.