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

yadongzhu

macrumors newbie
Dec 24, 2015
2
0
Hi, I have successfully installed El Capitan and upgraded to 10.11.2, thanks to all of you who contributed to this great solution. Now everything works except the bluetooth 4.0 LE. My new bluetooth card is recognized correctly in Yosemite as bluetooth 4.0 LE (System report -> Hardware -> Bluetooth -> LMP Version: 0x6 ), while the in my El Capitan installation, it is recognized as : System report -> Hardware -> Bluetooth -> LMP Version: 0x3, which is NOT 4.0 LE anymore, I now have both Yosemite and El Capitan in two different partitions and I can switch them back and forth and the bluetooth works as 4.0 in Yosemite but NOT in El Capitan, any idea? thanks in advance!

my machine: Mac Pro 1,1, 16G Ram, Graphics: ATI Radeon HD 5770 1024 MB,
 

stesoell

macrumors newbie
Nov 18, 2015
4
2
Hi all,

1st thank u guys for your efforts :)

Maybe someone can help me:

I've installed El Capitan 10.11.1 on an external drive via MBP (late 2013). Changed the boot.efi at /usr , /System and on the Recovery Partition with Pike's 3.1

After connecting the external HD to my Mac Pro 2.1 I can boot into El Capitans Recovery without problems. Here I've disabled the SIP.

In normal boot mode I can see shortly the Desktop (background image, dock..) When the upper menu bar pops up an immediately freeze will occur and the system restarts ...

Maybe someone knows about the phenomenon and could help me. Thank u guys.

Hi all,

after upgrading the RAM from 4 GB (4x1GB) to 12 GB (2x4GB,4x1GB) everything is working now (no freezes, no restarts).

I don't know why, but wanted to let you know!

Regards,
Stefan
 
  • Like
Reactions: nsotiriou

macguyincali

macrumors member
Jul 10, 2004
46
8
Wow... I had not even thought of that. Of course! I will try booting off the Install disk. I guess I don't need a recovery partition after all.

Will report back in the next few days on this issue.

Thanks iMattux. Have a merry christmas and talk soon!

-JP

Hi guys... happy holidays to all. Back at the desktop. So, I tried to boot from the install disk and it appears that something is amiss with that disk. When I select the disk (after an Option-Restart), it goes to an progress indicator but then it boots back into the El Capitan boot disk (the one I am up and running on). So I can't get past that. As I scan down below I see there are other comments which may indicate I need to "bless" the drive. Being a pious person, I will bless the drive and see what happens.

Thanks again all.
 

macguyincali

macrumors member
Jul 10, 2004
46
8
I'm not sure about this one. My work is generally not so critical that I need to backup more than once a day and many days I don't do anything that requires backup. I stopped using Time Machine a long time ago. It made my system sluggish whenever it ran and it was copying gigs of data when all I'd done was write a few emails and browse the web. My entire digital world occupied ~650gigs and Time Machine filled the 1TB backup and needed manual attention every few months.

Have you ever used Time Machine to recover something? Do yourself a favor and pretend that you lost something important from, say July 15, 2015. Try to restore the file and not hose yourself in the process. Time it. If your work is time-sensitive, it's a very wise thing to know how long disaster recovery actually takes. Using Time Machine to go back 30 minutes ago is one thing, 6 weeks or 6 months ago is another. It's amazing to me that among the few who do backup regularly, even fewer have done a data-recovery fire drill.

You paid for CCC. I recommend you do a full (bootable) backup once you have your system configured the way you want it. Schedule a full incremental backup every month, or every week at the most. If you make major changes like System updates or installing new applications, do a manual backup on top of the scheduled backups. Schedule a backup of your entire Home folder once a week or every day if your stuff changes that much. Schedule a backup of your Documents folder (or whatever files you are actively working on) as often as really makes sense.

I have done rehearsal disaster recoveries. Following the advice above, I'm up and running in as long as it takes to reboot from the backup drive and drop my home folder into place - less than 10 minutes. I would be hosed if my house burned down. I keep saying I'll do a backup and drop it a friend's house.

Maybe tomorrow ;-)


Ok... by the way, I've disabled the Time Machine backups and Ethernet had not been knocked offline for days no. So, all evidence points to it being a Time Machine issue. My next test will be to set TM backups to a local drive (not Time Capsule) to see if that causes any problems. I suspect it won't.

In regards to backups, well, I have quite a few redundancies: CrashPlan to the cloud (everything), Dropbox for my business files, Carbon Copy Cloner for system drive and, until recently, Time Machine to a Drobo Pro. I've been able to recover files from TM when I've accidentally deleted folders, files, etc. I use CCC for the system backup and am always able to pull relevant files off TM and CCC if I ever have an issue.

At any rate, ethernet problem only seems to happen when backing up on TM to a Time Capsule. Other machines at the house (iMac, MB Pro) seem to backup fine via Wifi without going offline.
 

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
Pikify3.1 usually creates a fully usable Recovery HD. However, 10.11.2 update included a Recovery HD update too. If this has been run, it's likely that the /Volumes/Recovery\ HD/com.apple.recovery.boot/boot.efi file will need to be replaced with a Pike version. The BaseSystem.dmg was also updated so it might need modifying too. If I find the time over the next few days I'll try to publish a RRHD(™) (recover the Recovery HD)....

I have written a "recover the Recovery HD" script. It shares much of its code with the original Pikify3.1 scripts.

Use this tool if you want to utilise the Recovery HD. It is especially useful if you have run the 10.11.2 update and found that the Recovery HD has been updated and you can no longer boot from it.

As always the ZIP file contains the script plus supporting files. These all need to be kept together in the same folder. The ZIP file should extract to a folder called rrhd. Inside that folder is the script itself, also called rrhd (along with the supporting files). Open a Terminal, become the super user, execute the script with the volume name of the disk you want to update.

E.G. assuming you unzipped the ZIP file in your Downloads folder, and assuming your El Capitan drive is mounted as /Volumes/El Capitan (change these to suit your situation)
Code:
cd ~/Downloads/rrhd
sudo -s
[your password]
./rrhd /Volumes/El\ Capitan

For those people that run multiple disks with versions of Mac OS X installed, this rrhd script will present the Recovery HD in the boot picker as 'Recovery HD (Your El Capitan disk name)'. It makes it easier to identify which Recovery HD belongs to which main OS disk!

============== Version 2 =======================

I have amended the rrhd script to properly find the volume name of the associated recovery partition (stopped being a lazy programmer and did it properly!).

MD5 (rrhd.v2.zip) = b892486fdf4858f54c00e53771a9efae
 

Attachments

  • rrhd.v2.zip
    1.9 MB · Views: 234
Last edited:
  • Like
Reactions: owbp

macguyincali

macrumors member
Jul 10, 2004
46
8
I have noticed a loss of Ethernet connectivity a couple of times on my system. It has only happened since updating to 10.11.2. I've used System Preferences : Network, changed a value and hit Apply ( actually I have 2 locations, and I switch between them). This has brought the Ethernet connection back. I haven't done any web searches to see if it is affecting other Mac users (yet). It might be Time Machine related, or it might be wake-from-sleep related, not sure yet because it isn't happening repeatedly, nor regularly enough to be certain. (I hate tracking down apparently random issues).

Pikify3.1 usually creates a fully usable Recovery HD. However, 10.11.2 update included a Recovery HD update too. If this has been run, it's likely that the /Volumes/Recovery\ HD/com.apple.recovery.boot/boot.efi file will need to be replaced with a Pike version. The BaseSystem.dmg was also updated so it might need modifying too. If I find the time over the next few days I'll try to publish a RRHD(™) (recover the Recovery HD)....

See my message below to iMattux, but basically, for me, the Ethernet problems stopped when I stopped backing up to Time Machine (in this case, to a Time Capsule over the network). Next test is to see if a local TM backup causes an Ethernet drop-off. haven't seen much on the forums about this problem. Incidentally, I used a similar approach to regain ethernet connectivity: deactivate the ethernet port, apply, then reactivate and apply.
 

wolf1734

macrumors regular
Nov 9, 2014
147
17
France
Good evening RTHPJM

I does not understand for created the key usb of starting up, you said " to Change directory in the file(case) of pikify3.1 of the zip file " I does not understand(include) what what it want to say.
And then in the terminal I what does not include what it is necessary to write has the place(square) of [" InstallerVolumeName] ]] thank you if you can me the explained kind regards
 

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
Good evening RTHPJM

I does not understand for created the key usb of starting up, you said " to Change directory in the file(case) of pikify3.1 of the zip file " I does not understand(include) what what it want to say.
And then in the terminal I what does not include what it is necessary to write has the place(square) of [" InstallerVolumeName] ]] thank you if you can me the explained kind regards

Bonjour wolf1734,

Je ne parle pas beaucoup le Français, je suis désolé

If you have a USB key named "Untitled", then InstallerVolumeName = /Volumes/Untitled

E.g.
Code:
cd ~/Downloads/pikify3.1
sudo -s
[your password]
./createpikeinstallmedia /Volumes/Untitled
 

wolf1734

macrumors regular
Nov 9, 2014
147
17
France
Thank you a lot I am going to try to make key the USB and I tells you if it works. I dézip the package and I leave in download, then I can make the key. Excuse I for my English I use Reverso I speak that French. Cordially
 

wolf1734

macrumors regular
Nov 9, 2014
147
17
France
I am to make the key I all well wrote in the terminal and I see write " done pikifying " and in the second line " bash_3.2
 

macguyincali

macrumors member
Jul 10, 2004
46
8
You might need to re-bless the installer volume, by the end of a successful install the installer volume is blessed with /S/L/C, and doesn't boot the second time of use (I haven't figured out where/when this happens so I haven't been able to fix it)

Code:
sudo bless --folder /Volumes/Install\ OS\ X\ El\ Capitan/.IABootFiles --file /Volumes/Install\ OS\ X\ El\ Capitan/.IABootFiles/boot.efi
:confused:

The blessing seemed to work as well as your Recovery Installer script which seemed to work perfectly. Was able to boot into the recovery disk, issue the commands to disable SIPS. Rebooted and installed the out of date Drobo software which was the last to include a SCSI initiator, without which my pricey DroboPro does not function. Also, OS X Java was installed. Read elsewhere that both Drobo and OS X Java won't install properly with SIPS enabled. After the restart, Drobo still didn't recognize the iSCSI interface so my 12TB worth of drives won't mount. Digging around in console, I found this: "ATTOiSCSI.kext has invalid signature; omitting." ATTO is the initiator that Drobo includes in its earlier versions of its software. I wonder if anyone knows what the heck that means and whether or not I can get rid of the error.

Thanks and talk soon.
 

mossman1120

macrumors newbie
Aug 4, 2010
22
1
So I am happy to report I am running 10.11 on my MacPro.

I did the CPU upgrade (thanks to everyone for the links to the videos) and I have a new hate for thermal paste but that is another story. I upgraded to 16GB of RAM. I did the Firmware Flash and the machine has been stable for over a week.

I just did the 10.11 upgrade via Target Mode and my MacBook Pro. It took a good 2+ hours to do and almost another hour to boot up so I could edit the Recovery Partition. After it was up and running I replaced the boot.efi file on the Recovery Partition and tried to boot off it. I did this by restarting the machine and holding Command + R. For whatever it didn't take. Do I need to bless it or something? Did I miss a step setting it up?

Luckily I had my Yosemite installer partition which I was able to mount my main drive with. I replaced the two boot.efi files and updated my path file. I then rebooted and installed the Boot64.V3. I then installed software updates and crossed my fingers. The machine came up perfectly have the 10.11.2 update.

Is there anything I need to do to make my Recovery Partition happy so I can use it in the future?

Thanks again for all the help from everyone.
 

drkheure

macrumors newbie
Nov 4, 2015
28
1
I am about to give up on 10.11.2.
I had zero problems with 10.11 running from a hard disk.
running on a macpro 1,1, original firmware. 5G ram geforce GTX 650. ( 2 screens )
currently running 10.10.5 booting with chimera and windows 7. zero problems. except I dont let it sleep on chimera. never bothered to fix that.

so I currently have 10.11.2 on a hard disk which is a clone from a mackbookpro. I thought it had figured an easy way to to update, so I used CCC to clone the macbookpro with some files not selected, like the boot.efi's. But I got constant reboots which I then blamed on what I did.
So decided to go for a clean install to a new SSD. Did the install on the mackbookpro to the SSD. stopped the machine when it was finished. ( at the fresh reboot ) did all the boot.efi stuff. got the recovery stuff working. ( this was with a fresh download from the app store )

Tried everything I could think off.
yesterday found the nvidia drivers for el cap on the nvidia web site. looked for a while that was the fix. but nope....

started to think the ssd was bad. ( new sandisk ) but ran ccc a few times on it with some big file copies ( 2 GIG ) with the corrupted files option checked and so far it hasn't copied a single byte on new runs.

A few days ago I ran it from the SSD for several hours watching a movie using VLC. no reboots. I thought it was fine because I removed a webcam from the front usb . but seems not.
Obviously something must have changed between 10.11 and 10.11.2
And it always seems to be some apple software doing it. ( safari, mail, photos, .... )

The hard drive is case sensitive and the SSD is not. ( just for steam )

I am using the boot.efi ( again ) from the github. ( https://github.com/Piker-Alpha/macosxbootloader/tree/El-Capitan/Prebuilt )
 

wolf1734

macrumors regular
Nov 9, 2014
147
17
France
Hello
I do not arrive it has to make the key of installation in the terminal write me " bash3.2 * " and after that makes nothing more thank you for those that he(it) can help me.
Cordially
 

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
Hello
I do not arrive it has to make the key of installation in the terminal write me " bash3.2 * " and after that makes nothing more thank you for those that he(it) can help me.
Cordially
Now you should have a volume called "Install OS X El Capitan", yes?

Reboot your machine. When you hear the startup chime, hold down the Alt/Option key
You will see the boot picker.
Select the "Install OS X El Capitan" disk to boot from...
 

rthpjm

macrumors 6502a
Jan 31, 2011
720
309
U.K.
After the restart, Drobo still didn't recognize the iSCSI interface so my 12TB worth of drives won't mount. Digging around in console, I found this: "ATTOiSCSI.kext has invalid signature; omitting."

Hi @macguyincali

Boot into the Recovery HD and then issue this command from the terminal:
Code:
csrutil enable --without kext

I believe it is the SIP equivalent of the former NVRAM setting kext-dev-mode=1.
Disclaimer: I haven't tried it myself
 

MacPro1comma1forever

macrumors newbie
Dec 29, 2015
1
0
Hallo everyone,
I have MacPro1,1 dualcore, running on Yosemite thanks to help from here last year. I would like to upgrade to Capitan. Where should I start? Is there a specific post here with a complete tutorial?

Looking forward to climbing El-Capitan

Thanks in advance.
 

Ant3000

macrumors 6502
Jul 20, 2015
374
46
UK
Just another big THANK YOU to everyone involved in making this work - especially Pike and rthpjm. After weeks of reading this forum I finally got around to installing El Capitan on my Mac Pro 1.1 - upgraded to 2.1. 32gb RAM. Installation was very straightforward thanks to the instructions provided and was done from a 16gb USB stick onto a 1TB HD. I have Yosemite on an SSD that I will eventually migrate from and perhaps add another, larger SSD and reinstall El Cap when I know everything is stable. This is a work machine so I need to know it will work without too many issues - hence the delay in installing.
As a side note, looking at your avatar rthpjm, are you in Nottingham? I have assumed (probably incorrectly) "rth" is "Robin The Hood" If so, I am other end of the A52. Thanks again.
 

splifingate

macrumors 68000
Nov 27, 2013
1,929
1,714
ATL
Some of the guys...

[...]

V7 adds error checking...

Just got-around to finally running your script, and have now only completed the creation of the modified installer. Before I proceed, two stdout responses post-"### DONE PIKIFYING ###":

Code:
2015-12-29 18:26:22.430 system_profiler[1051:73438] platformPluginDictionary: Can't get X86PlatformPlugin, return value 0
2015-12-29 18:26:22.432 system_profiler[1051:73438] platformPluginDictionary: Can't get X86PlatformPlugin, return value 0

More feedback, as time permits...

Regards, splifingate
 

donjames

macrumors member
Feb 20, 2015
89
7
Henderson, Texas
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.