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

[rthpjm]

Am I correct in thinking that all you're doing when you edit kext is telling your Mac that the card you're using is in fact one that it supports? Hence why I'm showing the correct gpu ram size, resolution, etc. with the nuances of it labeled as "ATI Radeon HD 5000" and I don't get a boot screen.

Yes. When you modify the Info.plist file inside the kext bundle, you are adding the manufacturer ID and the board ID as a unique single concatenated ID. The Mac can then match the board ID to the kext.

Having said that, your card seems to have matched against the AMD5000Controller, but then it has selected the RadeonFramebuffer, which I think may be the software renderer. If you compare your ioreg output with mine, my card matches the Vervet personality, this gives me full hardware acceleration (capabilities of the card).

The best online resource I have used for graphics mods (especially for the MacPros, as compared to hackintoshes) is the Netkas forums (osx86 tends to be mackintosh related). You might want/need to go have a read over there.....

This thread implies a reverse approach. Re-flash your 6770 BIOS using Radeon Bios Editor (RBE) to have a board ID of a 5770. then there is no need to modify kexts...
[doublepost=1491826755][/doublepost]

Thank you very much, for helping me out with installing El Capitan onto a 1TB SSD drive. It works well with small but noticeable speed increase.

I now have my 6TB System El Capitan HDD drive corrupted. It would not boot at all. However, I can access it from SSD drive and my data looks good. Looks like only the system is hurt. It was also backed up with a Time Machine every hour. I am not sure if the system on the time machine is corrupt, too. I tried to reinstall the El Capitan using the Recovery disk. But it also does not work. It looks like working a few seconds but it does not reinstall the system and the result is the same. My last hope is to reinstall the El Capitan downloaded from the purchased section of the App Store, which I already downloaded the Install OS X El Capitan.app and placed it into the applications folder. Then I saw rthpjm's amazing work on Pikify3.1 v14. Therefore, my questions please are:

1. If I do not erase my corrupted 6TB System disk and starting from my 1TB SSD System disk, which is running El Capitan can I use the new Pikify3.1 v14 and reinstall El Capitan onto my 6TB system hard disk, please? Will this keep my data on the 6TB system disk intact?

2. Or, shall I try to reinstall the El Capitan onto my 6TB system disk using the Install OS X El Capitan.app on the 1TB SSD System disk and then manually replace the boot.efi files, please? Will this keep my data intact, too? Will this be preferred way over using the Pikify 3.1 v14?

Thank you very much for all your kind help.

Hello TT01,

before going any further have you performed the simple checks to see if the boot.efi files have been overwritten with Apple versions?

I'm assuming you can boot from your SSD, and that your 6TB drive will be accessible from /Volumes/6TB (change that to match your actual volume name for the 6TB drive)

Both from your SSD
Open up a Terminal

ls -lh /Volumes/6TB/System/Library/CoreServices/boot.efi /Volumes/6TB/usr/standalone/i386/boot.efi

Look at the 5th column, it is the size of the file. It should read just over 300K (309K on my system). If it reads approx 600K on either file, then you have Apple versions of the boot.efi files.

Locate a copy of the Pike boot.efi files (the pikify zip file has copies of both the black and grey background variants, or download from Pike's web site).

Unlock the attributes (another layer of protection)

chflags nouchg /Volumes/6TB/System/Library/CoreServices/boot.efi

Copy the Pike version of the boot.efi file into place. Let's assume it is in your Downloads folder...

cd ~/Downloads
sudo -s

You will be prompted for your password, enter it carefully

cp boot.efi /Volumes/6TB/System/Library/CoreServices/boot.efi
cp boot.efi /Volumes/6TB/usr/standalone/i386/boot.efi
exit

Now try rebooting into your 6TB El Capitan volume....

 

[TT01]

.........

Hello TT01,

before going any further have you performed the simple checks to see if the boot.efi files have been overwritten with Apple versions?

I'm assuming you can boot from your SSD, and that your 6TB drive will be accessible from /Volumes/6TB (change that to match your actual volume name for the 6TB drive)

Both from your SSD
Open up a Terminal

ls -lh /Volumes/6TB/System/Library/CoreServices/boot.efi /Volumes/6TB/usr/standalone/i386/boot.efi

Look at the 5th column, it is the size of the file. It should read just over 300K (309K on my system). If it reads approx 600K on either file, then you have Apple versions of the boot.efi files.

Locate a copy of the Pike boot.efi files (the pikify zip file has copies of both the black and grey background variants, or download from Pike's web site).

Unlock the attributes (another layer of protection)

chflags nouchg /Volumes/6TB/System/Library/CoreServices/boot.efi

Copy the Pike version of the boot.efi file into place. Let's assume it is in your Downloads folder...

cd ~/Downloads
sudo -s

You will be prompted for your password, enter it carefully

cp boot.efi /Volumes/6TB/System/Library/CoreServices/boot.efi
cp boot.efi /Volumes/6TB/usr/standalone/i386/boot.efi
exit

Now try rebooting into your 6TB El Capitan volume....[/QUOTE]






Thank you very much for such a quick response. I did as you said and found that the two boot.efi were 309KB as you said they should. However, I changed them in case they were corrupted. Then I was able to boot into my 6TB drive. It was wonderful. However, it looked good for about an hour. Then it started giving me the same problems as I had before my 6TB drive stop working. What happens is that the windows would not work properly. The buttons inside applications stop working. The ball starts rotating continuously on those applications. I cannot quit those applications. I open the force quit window but I cannot force quit applications. They just would not quit. It says finder is not responding, but I cannot relaunch the Finder. Then I have to force shutdown my Mac Pro 2,1. These were the same problems happening before 6TB drive stopped working and would no longer boot up.

I really think that the El Capitan system on my 6TB system disk is not in good shape. I think I need to reinstall the system. I tried before to reinstall El Capitan using the Recovery disk but it did not work. This time I did not try it, because I think your Pikify3.1 v14 is the best way to go if it does not erase my data.

My question is, will Pikify3.1 v14 reinstall El Capitan system but leave my data intact, please? Is there anything I should be careful about, please? Would your Pikify3.1 v14 also setup the Recovery disk, too? Can I run it from my SSD system disk running El Capitan 10.11.6, please?

I am trying to avoid restoring the 6TB disk using the Time Machine as it may be also corrupt, unless I have no other choice.

Thank you very much for your very kind help.
[doublepost=1491908253][/doublepost]I am Sorry, rthpjm:

I did not know how to quote your text and reply to it. Please see my reply above, below your text.

 

[rthpjm]

.........




Thank you very much for such a quick response. I did as you said and found that the two boot.efi were 309KB as you said they should. However, I changed them in case they were corrupted. Then I was able to boot into my 6TB drive. It was wonderful. However, it looked good for about an hour. Then it started giving me the same problems as I had before my 6TB drive stop working. What happens is that the windows would not work properly. The buttons inside applications stop working. The ball starts rotating continuously on those applications. I cannot quit those applications. I open the force quit window but I cannot force quit applications. They just would not quit. It says finder is not responding, but I cannot relaunch the Finder. Then I have to force shutdown my Mac Pro 2,1. These were the same problems happening before 6TB drive stopped working and would no longer boot up.

I really think that the El Capitan system on my 6TB system disk is not in good shape. I think I need to reinstall the system. I tried before to reinstall El Capitan using the Recovery disk but it did not work. This time I did not try it, because I think your Pikify3.1 v14 is the best way to go if it does not erase my data.

My question is, will Pikify3.1 v14 reinstall El Capitan system but leave my data intact, please? Is there anything I should be careful about, please? Would your Pikify3.1 v14 also setup the Recovery disk, too? Can I run it from my SSD system disk running El Capitan 10.11.6, please?

I am trying to avoid restoring the 6TB disk using the Time Machine as it may be also corrupt, unless I have no other choice.

Thank you very much for your very kind help.

Hi TT01,

Okay, it really sounds like you may have an issue with the disk. But if you want to try re-installing, then yes, you should be okay to use pikify v14. (You should have a backup obviously)

 

[nycedit]

Hi Everyone,

Newbie here. I've been reading through the posts here and on the other forums linked to this one and am now a little overwhelmed at the prospect of trying to resurrect my computer without bricking it. I'm hoping someone could walk me through the easiest (and least expensive) steps to upgrade my macpro from 1.1 to 2.1 . Also the 3 main questions I have are:
1) Do I need to upgrade the RAM beyond 7gb? (the other forum said at least 8gb)
2) I'm running OSX 10.6.8 and am unable to upgrade the OS any further (is OSX 10.7 required? How can I get around this?
3) Should I change my graphics card (currently have NVIDIA GeForce 8800 GT)? Recs for decent inexpensive card?

Below are the specs for my machine, hopefully someone can offer some expert advice.

Mid 2006 - Mac Pro 2.66GHz Xeon
Model Identifier: MacPro1,1
System Identifier : MA356LL/A
Processor Name: Dual-Core Intel Xeon
Processor Speed: 2.66 GHz
Number Of Processors: 2
Total Number Of Cores: 4
L2 Cache (per processor): 4 MB
Memory: 7 GB
Model #: A1186
Bus Speed: 1.33 GHz
Boot ROM Version: MP11.005C.B08
SMC Version (system): 1.7f10

Graphics Card: NVIDIA GeForce 8800 GT:

System Software Overview:
System Version: Mac OS X 10.6.8 (10K549)
Kernel Version: Darwin 10.8.0

 

[rthpjm]

Hi Everyone,

Newbie here. I've been reading through the posts here and on the other forums linked to this one and am now a little overwhelmed at the prospect of trying to resurrect my computer without bricking it. I'm hoping someone could walk me through the easiest (and least expensive) steps to upgrade my macpro from 1.1 to 2.1 . Also the 3 main questions I have are:
1) Do I need to upgrade the RAM beyond 7gb? (the other forum said at least 8gb)
2) I'm running OSX 10.6.8 and am unable to upgrade the OS any further (is OSX 10.7 required? How can I get around this?
3) Should I change my graphics card (currently have NVIDIA GeForce 8800 GT)? Recs for decent inexpensive card?

Below are the specs for my machine, hopefully someone can offer some expert advice.

Mid 2006 - Mac Pro 2.66GHz Xeon
Model Identifier: MacPro1,1
System Identifier : MA356LL/A
Processor Name: Dual-Core Intel Xeon
Processor Speed: 2.66 GHz
Number Of Processors: 2
Total Number Of Cores: 4
L2 Cache (per processor): 4 MB
Memory: 7 GB
Model #: A1186
Bus Speed: 1.33 GHz
Boot ROM Version: MP11.005C.B08
SMC Version (system): 1.7f10

Graphics Card: NVIDIA GeForce 8800 GT:

System Software Overview:
System Version: Mac OS X 10.6.8 (10K549)
Kernel Version: Darwin 10.8.0

Hello nycedit

To upgrade your machine to a 2,1 involves a hardware upgrade of the CPUs to newer chips (relative to the current CPUs), and a firmware upgrade so that the Mac Pro realises it's now a 2,1. If you check the history of the classic Mac Pro Intel version, you'll find that the mother board did not significantly alter between the 1,1 and 2,1 releases. The 2,1 was a "bump" with newer processors. We do not really cover the 1,1 -> 2,1 upgrade on this thread. Have a search around, you'll find other threads on these forums, and many others, including a lot of walk through videos on YouTube...

To get your 1,1 or 2,1 running El Capitan doesn't "require" any changes. However, history has taught us many lessons.
Read post #1 of this thread. There are two approaches to installing El Capitan on a 1,1 or 2,1. Both highlighted on post #1.
Things you "should" upgrade:

• Memory

1. 1. El Capitan runs much more smoothly/reliably within a larger RAM footprint
   2. Remove and discard any original 512Mb RAM cards - these are know to cause repeated crashes (kernel panics) on MacPro 1,1 or 2,1 running El Capitan
   3. There are some reports that 1Gb RAM cards are also causing trouble
   4. Buy pairs of 2GB FB ECC RAM of the correct specification (or 4GB cards in pairs)
   5. If you aim to use the pikify method (see page-56 post #1390 - links in my signature), then aim for a total RAM footprint of 12Gb or more
      • Strictly speaking you only "need" 12Gb to perform the install, so if you're scavenging RAM from other machines, you can drop back down the RAM size after install
      • Having said that, re-read point 1 above

• Graphics card

1. El Capitan does not have drivers for the 8800. It will use the software render. Since the GUI makes use of hardware accelerated features extensively now, the usability will feel like like treacle.
2. The Netkas forums have a lot of information about graphics cards and patching them to give boot screens (too much!). I have a patched AMD Radeon 5770 (XFX brand)

• Upgrading to El Capitan
  1. if you have another "newer" and "supported" mac (e.g. a macbook or iMac) and you can connect a disk drive to it (take a disk out of your MacPro and put it into a caddy/external HDD enclosure, you can use target disk mode if both machines have firewire!), then you can run the Apple installer on the supported machine directly targeting the MacPro disk. After the install and before trying to boot the MacPro, you must manually replace two files with the community modified (by Pike) boot.efi file. See post #1...
  2. If you don't have another supported Mac, then you can use Pikify. This is a set of files I put together. This method requires 12GB or more of RAM (some users reported success with less than 12Gb RAM, i.e. 10Gb, but 7Gb is certainly not enough). see post #1390.

 

[Tony.Skid]

• if you have another "newer" and "supported" mac (e.g. a macbook or iMac) and you can connect a disk drive to it (take a disk out of your MacPro and put it into a caddy/external HDD enclosure, you can use target disk mode if both machines have firewire!), then you can run the Apple installer on the supported machine directly targeting the MacPro disk. After the install and before trying to boot the MacPro, you must manually replace two files with the community modified (by Pike) boot.efi file. See post #1...

Sorry to grab a part of your message, but I ask you a question: in this way, the recovery partition will work?

Thanks

 

[rthpjm]

Sorry to grab a part of your message, but I ask you a question: in this way, the recovery partition will work?

Thanks

If you use the "supported Mac" method of installing, then no the Recovery HD will not work without further modification...
Search this thread for rrhd (my script and files to recover the Recovery HD)

 

[nycedit]

Hello Rthpjm,

Thank you so much for taking the time to write a detailed response. It's much appreciated. I'm planning on following the Pikify method to upgrade the machine. I definitely need to research more on the other threads and youtube . Just a quick question, do you recommend upgrading the CPUs as well or will the existing dual core Xeon processors work?

 

[F1Mac]

@nycedit, I would also highly recommend upgrading your system drive to SSD. Since Yosemite the latest OSes can be painfully slow on spinning drives. Not unusable, but not a very pleasant experience either...

 

[rthpjm]

Hello Rthpjm,

Thank you so much for taking the time to write a detailed response. It's much appreciated. I'm planning on following the Pikify method to upgrade the machine. I definitely need to research more on the other threads and youtube . Just a quick question, do you recommend upgrading the CPUs as well or will the existing dual core Xeon processors work?

The existing Xeons will work. Again though, the leap in performance from what is a "relatively easy" upgrade is worth the effort in my mind. Obviously "relatively easy" depends on your skill level and confidence in replacing CPUs. My system had stock dual/dual-core, and I upgraded to dual/quad-cores. Extra cores help for a lot of the work flows I have.

 

[Tony.Skid]

If you use the "supported Mac" method of installing, then no the Recovery HD will not work without further modification...
Search this thread for rrhd (my script and files to recover the Recovery HD)

Thanks, I downloaded the .zip file, will try tomorrow to reinstall the o.s. to a new ssd with MacBookPro.
Actually, the Mac Pro is working great at 10.11.6 (but there's no recovery, because I installed it via an image), and a Video card AMD 5670, not flashed; El Cap recognise it as "5000 series", but everything is working well. Don't think that it's "flashable", BTW; took a look at netkas, but I didn't find info about this card.

 

[camacho]

Thanks for all your help rthpjm. For some reason everything is working better with a single 6770 so I have stuck with that until I get more time to troubleshoot.

I have been having another issue however. Since I've upgraded to El Capitan, my bluetooth will not pick up anything. magic mouse, keyboard, nothing. I read on the original post about handoff but that wouldn't effect this would it? I'm just trying to connect a keyboard and mouse.

 

[rthpjm]

Thanks for all your help rthpjm. For some reason everything is working better with a single 6770 so I have stuck with that until I get more time to troubleshoot.

I have been having another issue however. Since I've upgraded to El Capitan, my bluetooth will not pick up anything. magic mouse, keyboard, nothing. I read on the original post about handoff but that wouldn't effect this would it? I'm just trying to connect a keyboard and mouse.

Sorry camacho, I don't know. My MacPro works nicely with the "stock" Apple Bluetooth. Just recently I even upgraded that to a newer (iMac) Bluetooth card.

You could try a PRAM reset, and an SMC reset. If you read back a few pages I wrote some posts on these resets.

The only other thing I can think of is the validity of the "Install OS X El Capitan" app. Did you use a copy direct from Apple, or did you "find" a copy on the web? If you "found" a copy, then it might have been modified, perhaps with a modified Bluetooth kernel extension (kext). I believe the older MacBook and MacMini models have struggled with Bluetooth, and there may be modified kexts.

 

[camacho]

Sorry camacho, I don't know. My MacPro works nicely with the "stock" Apple Bluetooth. Just recently I even upgraded that to a newer (iMac) Bluetooth card.

You could try a PRAM reset, and an SMC reset. If you read back a few pages I wrote some posts on these resets.

The only other thing I can think of is the validity of the "Install OS X El Capitan" app. Did you use a copy direct from Apple, or did you "find" a copy on the web? If you "found" a copy, then it might have been modified, perhaps with a modified Bluetooth kernel extension (kext). I believe the older MacBook and MacMini models have struggled with Bluetooth, and there may be modified kexts.

So check it out. Got my bluetooth working better than ever. I'm not sure if this is known information or not but here's what I found out.

After resetting PRAM, SMC, and deleting bluetooth.plist to no avail, I looked at my bluetooth module and found that the antenna was off a bit. Plugged it back in and got a bluetooth connection although it was a very poor connection. Unstable and the mouse was unusable. So I cracked the case back open to find 4 different antennas (with labels #1-4). I never use wifi since I'm on ethernet so I just tried antenna #1 connected to the bluetooth module and voila! I'm getting a much better range on my bluetooth devices (keyboard, mouse, ps3 remote).

 

[MJK2017]

Hello MJK2017,

Older versions of pikify would not run on any version of MacOS X older than Lion. Some of the tools it uses wouldn't run due to version incompatibility. However, v14 uses a different technique, I haven't tested v14 on Snow Leopard. If you want to be a pioneer, you can simply try to run pikify v14 on your snow leopard machine.

If it doesn't complete there will be no harm done. Just delete the OS Install Data folder that gets created on the target drive/volume.

If it does work, great. Please report back, so that others might benefit.

If you need a copy of Lion, a trip to eBay seems in order

You will need 12 GB or more of RAM, and please do not use the original 512Mb RAM cards. Something, possibly an assumption by Apple, doesn't like the use of 512mb or 1Gb RAM cards. You might get the system installed, but if you have any of the 512m/1G RAM sticks, users report frequent crashes. Removing those lower capacity RAM cards, possibly replacing them with either 2GB or 4Gb RAM card, users report no crashes.

If you still have the gtx7300, then yes get a better gfx card. I'd recommend at least an ATI 5770 or better. The original card will load and work, but you will not have any acceleration. Without acceleration the experience will feel horrible.

[doublepost=1492820264][/doublepost]Got lion installed and followed v14 of pikefy installed and works great thanks for this forum now it is as if I have a new Mac Pro from 1,1 ...almost. I did install boot 64 as well, this insures I can update El Capitan to newer versions before going to sierra? Will there be a similar modifier to run sierra on Mac Pro 1,1? Thanks again works great, just wondering about updates.

 

[OGNerd]

[doublepost=1492820264][/doublepost]Will there be a similar modifier to run sierra on Mac Pro 1,1? Thanks again works great, just wondering about updates.

No, there is no path to upgrade the Mac Pro 1,1 or 2,1 to macOS Sierra, as the family of CPU's they support do not encompass the the required SSE 4.1 instruction set.

 

[rthpjm]

[doublepost=1492820264][/doublepost]Got lion installed and followed v14 of pikefy installed and works great thanks for this forum now it is as if I have a new Mac Pro from 1,1 ...almost. I did install boot 64 as well, this insures I can update El Capitan to newer versions before going to sierra? Will there be a similar modifier to run sierra on Mac Pro 1,1? Thanks again works great, just wondering about updates.

Hello MJK2017

I did try to run pikify v14 from snow leopard 10.6.8 and I found it works okay. I know it's too late for you now, but the changes I made for v14 seems to remove the "Lion 10.7 or higher" requirement of v12 or lower....

I will update post 1390...

 

[128kmacintosh]

I am stuck here a little. I used my mac pro 5.1 to install El Capitan for my mac pro 2.1. When installed it it words fine , I changed the Boot EFI files and when I put it in the mac pro 2.1 I get the folder flashing.

 

[rthpjm]

I am stuck here a little. I used my mac pro 5.1 to install El Capitan for my mac pro 2.1. When installed it it words fine , I changed the Boot EFI files and when I put it in the mac pro 2.1 I get the folder flashing.

After replacing the boot.efi files, you often need to "bless" the volume.

If the disk is in the MacPro 2,1, hold down the ALT key when you hear the boot chime.
Assuming you replaced the correct files, you should be able to choose that disk.
It should boot.
Once booted, go to the System Preferences, Startup Disk, and select the disk there.

If the disk is connected to the 5,1 you should perhaps use the command line from a Terminal.

If it will not boot, then you probably did not replace the correct boot.efi files. Check the size of the boot.efi files, the Pike versions are just over 300Kb, the Apple versions are just over 600Kb.

 

[128kmacintosh]

After replacing the bot.efi files, you often need to "bless" the volume.

If the disk is in the MacPro 2,1, hold down the ALT key when you hear the boot chime.
Assuming you replaced the correct files, you should be able to choose that disk.
It should boot.
Once booted, go to the System Preferences, Startup Disk, and select the disk there.

If the disk is connected to the 5,1 you should perhaps use the command line from a Terminal.

If it will not boot, then you probably did not replace the correct boot.efi files. Check the size of the boot.efi files, the Pike versions are just over 300Kb, the Apple versions are just over 600Kb.

Awesome, I'll try that. yes , the drive is in the 2.1. Will keep you posted on the outcome.
Gray screen for a long time... ~5 mins and counting.
[doublepost=1493058618][/doublepost]Update: I used my SFOTT installer disk I had laying around, went into the setup and from there set the EL capitan HD drive in slot 1 as start up drive, then rebooted. it's booting now

 

[MJK2017]

Hello everyone,

If you have been using my Boot64 package to allow seamless upgrades to El Capitan (10.11.1 and 10.11.2), then be aware that I found the 10.11.2 update caused Boot64.v2 an issue. I believe that I have fixed the issue, and Boot64.v3.mpkg.zip is now posted back at #1391

However, those of you that have been using Boot64, and have already upgraded to 10.11.2 might wish to check if your system is working well with Boot64.

To check:
On your normal working El Capitan partition, open a Terminal and type

sudo -s
[your password]
touch /System/Library/CoreServices/boot.efi

If you get a response 'Operation not permitted', then we need to fix it. Sorry!

To fix it:

• Download and install Boot64.v3.mpkg.zip from post #1391
• Boot from the Recovery Partition
• Once in the Recovery HD, open a Terminal from the Utilities menu

• csrutil disable

• Reboot back to your normal working El Capitan partition

sudo -s
[your password]
/usr/libexec/rootless-init
exit

• Reboot back into your Recovery HD
• Once in the Recovery HD, open a Terminal from the Utilities menu
  

• csrutil enable

• Reboot back to your normal working El Capitan partition

You can test that the fix has worked by re-running the check code above again. This time there should be no message returned after the touch command is executed.

[doublepost=1493172988][/doublepost]Was able to install El Capitan 10.11.6 and saw this... did run test and get 0perations not permitted reply does this mean I should follow your fix procedure although I'm at 10.11.6 am wondering about recent security upgrades , will they install? And subsequent updates. When new update for sierra comes out, I understand El Capitan will be unavailable to download, if I have my installer still in applications folder (lion... pikify start point) can I redo the pickify process or will this become obsolete? I now have a Mac Pro 1,1 that is now like a new computer running El Capitan ... how long will this last, to good to be true.

 

[rthpjm]

[doublepost=1493172988][/doublepost]Was able to install El Capitan 10.11.6 and saw this... did run test and get 0perations not permitted reply does this mean I should follow your fix procedure although I'm at 10.11.6 am wondering about recent security upgrades , will they install? And subsequent updates. When new update for sierra comes out, I understand El Capitan will be unavailable to download, if I have my installer still in applications folder (lion... pikify start point) can I redo the pickify process or will this become obsolete? I now have a Mac Pro 1,1 that is now like a new computer running El Capitan ... how long will this last, to good to be true.

I believe 10.11.6 SIP has finally stopped Boot64 from working in the way it is designed to work, with SIP enabled. It will work with SIP disabled.

El Capitan will only ever receive security updates now, which historically do not include updates to the boot.efi files.

I'll leave Boot64 available for those new installations that start at anything less than 10.11.6.

If you want to change the background colour, boot into the Recovery HD and change the files from there, or disable SIP.

 

[thierrybeginl]

Hello Mr. Zarniwoop, and everyone!

My father has a MacPro 2,1 with an ATI Radeon HD 5770 1024 MB graphic card and we could manage to install it from a custom system (The downloaded version from the App Store and pikyfied v.12 would crash on 3/4 boot from the USB Drive). But two things happenned :
- not a single USB ports works

in "About this mac/system report/USB" it shows (4xUSB 1.0 (UHC), 1xUSB 2.0 (EHC) and an Inatek KT4004 USB 3.0 PCI card)
But they are suppose to be 5x USB 2.0 so it doesn't even recognise it.

I just don't understand what to modify. I downloaded the Rehabman Injectorall, there again don't know what to do with the files... USB ports works before El Capitan boots and it works on Lion. So it is clearly El Capitan.

Thank you for your help and great post!!!!

 

[rthpjm]

Hello Mr. Zarniwoop, and everyone!

My father has a MacPro 2,1 with an ATI Radeon HD 5770 1024 MB graphic card and we could manage to install it from a custom system (The downloaded version from the App Store and pikyfied v.12 would crash on 3/4 boot from the USB Drive). But two things happenned :
- not a single USB ports works

in "About this mac/system report/USB" it shows (4xUSB 1.0 (UHC), 1xUSB 2.0 (EHC) and an Inatek KT4004 USB 3.0 PCI card)
But they are suppose to be 5x USB 2.0 so it doesn't even recognise it.

I just don't understand what to modify. I downloaded the Rehabman Injectorall, there again don't know what to do with the files... USB ports works before El Capitan boots and it works on Lion. So it is clearly El Capitan.

Thank you for your help and great post!!!!

Try removing the Inatek card as a test....

SIP may be preventing any custom driver from loading as it did under previous versions of Mac OS X.

 

[fragmoider71]

Hi all,

I just managed to upgrade my mac pro 1.1, dual 3.0ghx eons, 32gb ram to elcappitan - I also upgraded the gfx card to a radeon 4870 1GB from the standard radeon x1900XT that I bought for 10 bucks.

So all is well except the following issue - machine boots up, everything works except dual monitor support.

Both monitors connected via DVI
Both monitors detected correctly as Samsung 2350

Only problem is monitor 2 - seems to be up and running and 1 doesn't fire up at all so I am running single monitor which is a bit lame as I am a writer so like to use one in A4 and the other as normal.

Just not sure if I am missing a vital step...duals worked fine on my old ATI :-(