I have not performed the trim force enable command. dev/disk2 is what I’m currently running El Capitan on (a single HDD). I used latest advice from this article to create the Fusion drive ģ: Apple_Boot Recovery HD 650.0 MB disk2s3Ģ: Apple_CoreStorage Fusion 127.7 GB disk3s2Ģ: Apple_CoreStorage Fusion 1.5 TB disk4s2ģ: Apple_Boot Recovery HD 784.2 MB disk4s3 I installed a Crucial M550 (128GB) SSD and am using a 1.5TB Western Digital HDD. Apologies if I have posted this in the wrong place.įusion drive is my own (hybrid). I have not replaced the boot.efi on the recovery partition (almost wondering if I should do that).Īnyway… I hope the feedback is valuable. There’s some extra special about the Fusion drive that I haven’t found yet. I can successfully reboot back into the 10.11 on the 1.5TB HDD. I’ve waited for 10 or 20 minutes and nothing. I get a black screen with an Apple logo and no loading progress bar. Now I’ve updated the boot.efi in coreservices and standalone/i386 and …. And 10.11 installed via my MacBookPro and working. What had worked on 10.10 for the setup of the Fusion drive would appear not to work anymore on 10.11 – so eventually I got a fusion drive created with a recovery partition (that’s the clue). So today I thought I’d switch this across to my fusion drive (in the same machine). Please take this on board as feedback into your development for boot.efi.Īlso my apologies if this is not the right place to post.Īs Indicated above I have 10.11 running successfully on the MacPro1,1 with boot.efi on a single 1.5TB HDD. I read somewhere you are not providing support – I understand that. boot.efi has worked really on both 10.9, and 10.10… and now on 10.11 (so far). Possibly only let unsigned kexts load and let the rest for what it is since that isn't required, and may open a door for exploits. Keeping as much protection up and running. What I mean here is that it is better to change as little as possible. People who set the NVRAM variable csr-data and/or csr-active-config in a way that it basically disables the System Integrity Protection, that is not in your best interest.
CLOVER EFI EL CAPITAN UPDATE
Note: If Clover has changed, but I missed it, then please let me know so that I can update it here. GSettings.CsrActiveConfig = (UINT32)GetPropertyInteger (Prop, 0圆7) //the value 0xFFFF means not set Prop = GetProperty (DictPointer, "CsrActiveConfig") Update-3: Clover is recently changed and now sets csr-active-config by default similar to rootless=0. Update-2: I have not yet been contacted by Clover developers, but then again they might not care about (your) security/privacy. Update: RevoBoot and the Enoch branch of Chameleon are no longer vulnerable and can now boot El Capitan without rootless=0 (the ‘all or nothing’ setting. Not that it really matters, because all* legacy boot loaders are still vulnerable. Note: You don’t need to replace boot.efi with a legacy boot loader – think Chameleon, Chimera and RevoBoot – to be vulnerable, because boot.efi isn’t used by legacy boot loaders. To let your modified kexts load without the need of rootless=0. This is why I am/will be working with boot loaders developers so that they can fix this.
Your hack won’t boot without rootless=0 but hang on. I would never do this, and that is why I urge you to listen to me: Please do NOT boot with rootless=0 Period!!! I can replace your boot.efi with a modified copy of mine and give myself access to all of your files. Nobody should open ‘a backdoor in OS X’ and rootless=0 helps to protect your filesystem – among others – and so please do not use it with installations that are connected to the Internet.
CLOVER EFI EL CAPITAN OFFLINE
I believe that Hacking Team ( currently offline ROFL) was hacked in late 2014 already, by the Dream Team, and that using rootless=0 as NVRAM/boot-arg is utterly stupid. \System\Library\Extensions\AMDFramebuffer.First. \System\Library\Extensions\AMD6000Controller.kext HzAgIFYAS88QAAAAAAAA/gBXNjU3RwAxNTRXUDEKAAAA/gAjMz1I Boot OS X 10.8.5 (12F36) Mountain Lion in Verbose Mode
0 kommentar(er)
