Contribute
Register

OS X El Capitan Public Beta 3 is Now Available

Status
Not open for further replies.

tonymacx86

Administrator
Staff member
Joined
Nov 17, 2009
Messages
7,369
Motherboard
Z370N WIFI
CPU
i7 8700K
Graphics
HD 630
Mac
  1. MacBook Air
Classic Mac
  1. Apple
  2. PowerBook
Mobile Phone
  1. iOS
Screen Shot 2015-07-22 at 1.59.17 PM.jpg
Today Apple released the 3rd Public Beta of OS X El Capitan. If you've already installed the public beta, the update is available via the Mac App Store.

Enroll in the Free Apple Beta Software Program
https://beta.apple.com/sp/betaprogram/welcome

Related:
http://www.tonymacx86.com/el-capita...x-el-capitan-public-beta-2-now-available.html
http://www.tonymacx86.com/el-capita...s-x-el-capitan-public-beta-now-available.html
 
Please note that the boot flag rootless=0 is removed from this build, so it will be harder to install anything to protected folders.
 
take it kext-dev-mode=1 doesn't work no more then FakeSMC should load if your using Clover shouldn't it?
 
If rootless=0 is removed does that mean we can't use Chimera?
 
Can anyone confirm whether kext-dev-mode=1 working or not? Because I can boot my hack OK without rootless=0, but I believe it won't load FakeSMC and other Kexts that are in S/L/E/ if kext-dev-mode is disabled, and as of PB2 Clover can't inject kexts from the EFI partition.
It seems pretty risky to upgrade right now.
 
Clover actually has rootless resolved with 2350+ with this patch
http://sourceforge.net/p/cloverefiboot/code/3250/

It just doesn't have a tag yet so it still sits as 2341 for release version. Insanitymac has a built version from source of 2351 that helps though. You'd want to install 2350+ of clover before updating to public beta 3.

Asgorath explains the patch:
"Clover r3250 adds support for a config.plist setting called CsrActiveConfig that will set the same NVRAM variable as the utility in the recovery partition OS"

If you need to use it anyways. You shouldn't need to most of time.
 
That's marginally better. To clarify, "rootless=0" is being replaced by the CSR flags which allow more fine-grained control of what aspects of SIP are in place: http://www.idelta.info/archives/sip-rootless-internal-in-el-capitan/ I'm not clear why they're choosing 0x67, or what it will take to get kexts to be loaded from the EFI partition. My impression is that the system will ultimately need kexts installed to S/L/E under 0x67 then run normally under 0x1, but I'm curious to see what the reality is.
 
Status
Not open for further replies.
Back
Top