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

[PeterHolbrook]

Mike, have you seen Pike's latest question to you in his blog?

"Does csrutil enable/disable work now?" (posted yesterday at 9:26 pm (Spanish/Central European Time, I guess), second page of the thread we've been participating in).

 

[mikeboss]

yes, saw it now...

it's still the same: csrutil: failed to modify system integrity configuration. This tool needs to be executed from the Recovery OS.

 

[PeterHolbrook]

Mike, read Pike's response. It may be very important.

 

[dfritchie]

So there I was running El Cap PB6, happy as a clam. Then I decided to remake my Yosemite installer USB stick using 10.10.5, Finished and booted system off the USB no problem. I then rebooted to El Cap, kernel panic! Tried all the usual fixes, no go. Re-installed El Cap using my original USB installer, gets to reboot part and it boots into Yosemite, will not boot El Cap at all. Do I need to bless it? It shows up in startup disk and also option boot.

 

[PeterHolbrook]

So, bless it, but make sure your two boot.efi files are either Pike's Yosemite boot.efi or the latest El Capitan edition boot.efi (still being developed).

 

[PeterHolbrook]

Dear Fellow Forum Members,

Due to family reasons, starting this coming Tuesday or this coming Wednesday at the latest, I will be away from my computer for several days (perhaps up to one entire week), so, even if I follow the progress of this project on my iPhone, I'll be unable to do any compiling for some time. It would be great if some other person, perhaps Hennesie2000 or other equally knowledgeable colleagues, can compile Pike's source code for mikeboss's crucial tests.

 

[mikeboss]

I have sent the first of the two reports to pike (not sure if I've got the right e-mail address to send them to...).

 

[PeterHolbrook]

Possibly as one last favour before I leave for a few days, here's a request that Pike has made. Can anyone with El Capitan installed on a real COMPATIBLE Mac (NOT an old Mac Pro) comment on the results of the following procedure?

1.) boot into El Capitan and run csrutil status
2.) nvram -xp and look for csr-data and csr-active-config
3.) nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:csr-data
4.) nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:csr-active-config
5.) run csrutil disable and before rebooting recheck the above.
6.) reboot and check the above once again.

What I need to know is if and when csr-data and/or csr-active-config can be found in NVRAM. Check with the above commands.

Thanks!

 

[mikeboss]

I ran the commands on a MacPro5,1 running El Capitan. results posted on Pike's blog.

 

[PeterHolbrook]

Presumably, my last build for several days until my return.

 

[mike.101]

Possibly as one last favour before I leave for a few days, here's a request that Pike has made. Can anyone with El Capitan installed on a real COMPATIBLE Mac (NOT an old Mac Pro) comment on the results of the following procedure?

1.) boot into El Capitan and run csrutil status
2.) nvram -xp and look for csr-data and csr-active-config
3.) nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:csr-data
4.) nvram 7C436110-AB2A-4BBB-A880-FE41995C9F82:csr-active-config
5.) run csrutil disable and before rebooting recheck the above.
6.) reboot and check the above once again.

What I need to know is if and when csr-data and/or csr-active-config can be found in NVRAM. Check with the above commands.

Thanks!

Running ElCap beta 6 on MacbookPro 2012.
1) status is enabled
2) No reference to csr in nvram
3 and 4) not found
5)Started from recovery and ran: csrutil disable and rebooted
6)csrutil status returned:

System Integrity Protection status: enabled (Custom Configuration).
Configuration:
Apple Internal: disabled
Kext Signing: disabled
Filesystem Protections: disabled
Debugging Restrictions: disabled
DTrace Restrictions: disabled
NVRAM Protections: disabled
This is an unsupported configuration, likely to break in the future and leave your machine in an unknown state.

and nvram -xp contained the following:
<key>csr-active-config</key>
<data>
dwAAAA==
</data>

After csrutil enable in recovery:
nvram -xp returned:
<key>csr-active-config</key>
<data>
EAAAAA==
</data>

Hope this helps

 

[a02]

Attempted to create a USB installer for the GM candidate. The installer boots to a kernel panic stating no driver for this platform "AHCPI". Can't perform kext scan: no kext summary. BSD process name corresponding to current thread: Unknown.

 

[VAGDesign]

Presumably, my last build for several days until my return.

Used this boot.efi and with @Hennesie2000 's guide for Yosemite I've installed the GM on my Mac Pro 2,1.
The only problems was:
After the installation you have to boot on another OS X to be able to replace the boot.efi file on the 2 known locations on the installed partition.
The boot.efi file above posts in verbose mode all the time. Do you know any working boot.efi file with black background and with no verbose that works?

Thanks to all contributors and I wait for a new guide so more people to succeed on the new "unreleased" OS X.

 

[VAGDesign]

The boot.efi file above posts in verbose mode all the time. Do you know any working boot.efi file with black background and with no verbose that works?

I found the right one here

 

[PeterHolbrook]

I found the right one here

Wrong. That isn't THE right one. The right one hasn't been compiled yet. If nobody does it first, I should be able to do it in less than one week.

 

[VAGDesign]

Thanks Peter, for what I need, it works fine. Black bg with white logo.
The final will support also booting to recovery partition?

 

[dfritchie]

Attempted to create a USB installer for the GM candidate. The installer boots to a kernel panic stating no driver for this platform "AHCPI". Can't perform kext scan: no kext summary. BSD process name corresponding to current thread: Unknown.

I tried as well, no matter which boot.efi I use it fails. Will start the boot process, then will switch from verbose to white apple on black background and will hang there, no progress bar or anything.

 

[splifingate]

Dear Fellow Forum Members,

Due to family reasons, starting this coming Tuesday or this coming Wednesday at the latest, I will be away from my computer for several days (perhaps up to one entire week), so, even if I follow the progress of this project on my iPhone, I'll be unable to do any compiling for some time. It would be great if some other person, perhaps Hennesie2000 or other equally knowledgeable colleagues, can compile Pike's source code for mikeboss's crucial tests.

Here's the latest, per your request.

Successfully boots ElCap and the 10.11 RecoveryHD

I finally have the Dell T5500 Win7 system up for VS compiles, and the GM Candidate installed (gah, but that was a horrendously-awful lot of trouble)--all on the same network.

I'll try to be of further help....

 

[PeterHolbrook]

Please, test the compilation of the latest commit. Everybody should bear in mind that this it NOT the final version of boot.efi, El Capitan edition, for old Mac Pros.

 

[PeterHolbrook]

Here's the latest, per your request.

Successfully boots ElCap and the 10.11 RecoveryHD

I finally have the Dell T5500 Win7 system up for VS compiles, and the GM Candidate installed (gah, but that was a horrendously-awful lot of trouble)--all on the same network.

I'll try to be of further help....

Many thanks. It appears that, unknowingly, we both were compiling at the same time.

PS The difference in size is presumably due to slightly different compilation environments between splifingate and me. I've compiled using one particular version of Microsoft Visual Studio 2013, with one particular version of MASM, on Windows 8.1 running on a VMware Fusion 8 virtual machine. If the compilation tools had been different, or if they were run in a different operating system, et cetera, the size of boot.efi might have been different. In any case, both versions ought to work exactly the same.

 

[splifingate]

yes, that is correct. in order to get a working Recovery HD in the end, it is mandatory to modify the BaseSystem.dmg. but AFAIK there (in Yosemite) are only the usual two copies of boot.efi, not three. I've never seen or heard about this bootbase.efi before yesterday. a search on Google for "bootbase.efi" gives zero results...

Bit late to the game, here....

Thank you, Mike and Peter, for your diligence.

bootbase.efi is new to the process with ElCap (albeit, only in the installation phase (I can only find it in the stock BaseSystem.dmg on the Recovery HD after installation)).

Interestingly-enough, I only modded the PlatformSupport.plist for my F4208DC8, and replaced the boot.efi in the 10.11 Recovery HD partition (per your report) with the latest commit from Piker, and can now enter into the Recovery environment with ease.

Thankfully so, as adding the modified boot.efi to BaseSystem.dmg is a tedious, time-consuming process I'd not wish upon anyone

 

[VAGDesign]

Thanks for the contribution @splifingate the community needs more people
A quick question to you and also @PeterHolbrook:
How I edit the Recovery partition to add your new boot.efi files?
ATM I have on my Mac Pro:
SSD with Yosemite
HDD with Mavericks
HDD with El Capitan

I see 3 recovery partitions ( 10.10 / 10.10.3 and 10.11).
None of them boot because I don't know how to edit them and add the right boot.efi files.

Thanks in advance!

 

[splifingate]

Thanks for the contribution @splifingate the community needs more people
A quick question to you and also @PeterHolbrook:
How I edit the Recovery partition to add your new boot.efi files?
ATM I have on my Mac Pro:
SSD with Yosemite
HDD with Mavericks
HDD with El Capitan

I see 3 recovery partitions ( 10.10 / 10.10.3 and 10.11).
None of them boot because I don't know how to edit them and add the right boot.efi files.

Thanks in advance!

Make sure Disk Utility is closed, then enter this at the Terminal prompt:

defaults write com.apple.DiskUtility DUDebugMenuEnabled 1

You will then be able to choose the Disk Utility menu > Debug > 'Show every partition' to be able to Mount the Recovery HD partition.

There is one boot.efi in the com.apple.recovery.boot folder, and two inside BaseSystem.dmg (three (including the bootbase.efi) in the one delivered with ElCap)

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

I replaced the one in c.a.r.boot on my 10.11 Recovery partition, and can enter it easily; I had to replace the ones inside BaseSystem.dmg (per the steps, above) in my 10.9/10.x partitions before I could boot them.

Good luck.

 

[mikeboss]

welcome back peter! tests done using your latest boot.efi.

cleared PRAM prior to first boot into El Capitan. checked PRAM -> NO csr-active. reboot into Recovery HD -> csrutil status: enabled (Apple Internal). nvram -xp -> NO csr-active in NVRAM. csrutil disable -> failed to modify...

 

[VAGDesign]

Make sure Disk Utility is closed, then enter this at the Terminal prompt:

defaults write com.apple.DiskUtility DUDebugMenuEnabled 1

You will then be able to choose the Disk Utility menu > Debug > 'Show every partition' to be able to Mount the Recovery HD partition.

There is one boot.efi in the com.apple.recovery.boot folder, and two inside BaseSystem.dmg (three (including the bootbase.efi) in the one delivered with ElCap)

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

I replaced the one in c.a.r.boot on my 10.11 Recovery partition, and can enter it easily; I had to replace the ones inside BaseSystem.dmg (per the steps, above) in my 10.9/10.x partitions before I could boot them.

Good luck.

Thanks a lot @splifingate I just made my El Capitan Recovery HD bootable!
But, as @mikeboss just wrote, we cannot still change the csrutil from enabled to disabled... this will happen I guess on the final boot.efi version

Thanks to all who spend time and effort on this!
Cheers!