artur_pt Posted January 12, 2018 Share Posted January 12, 2018 hello Vit9696 since I'm using ur efi driver I get this to send to apple I'm in 10.13.3 beta 4 eficheck.dump.zip i'm not sure is related this is what I have in drivers64UEFI thanks Link to comment Share on other sites More sharing options...
vit9696 Posted January 12, 2018 Author Share Posted January 12, 2018 Should not be. From what I remember this is the firmware check introduced in 10.12 or 10.13, and which verifies the hashes(?) for your firmware. If there is a mismatch, you firmware dump cleaned from personal information is sent to Apple for analysis. AptioFix should not be related anyhow. 1 Link to comment Share on other sites More sharing options...
Slice Posted January 12, 2018 Share Posted January 12, 2018 How much this driver differs from Clover's AptioFix? I have inconvenience to compile all if they are located in several places. Link to comment Share on other sites More sharing options...
vit9696 Posted January 12, 2018 Author Share Posted January 12, 2018 While they have a lot in common, this new one most notably implements a whole new technique for ASLR support, some special boot.efi patches, and changes to mapping handling. I'd say with this driver Clover's AptioFixes are pretty much obsolete, although I could imagine some time to be needed to fully tune the config for general audience. For example, at this moment I may consider enabling your sleep patch (with some alterations), because it kind of starts to make some sense. Link to comment Share on other sites More sharing options...
Slice Posted January 12, 2018 Share Posted January 12, 2018 I think about having OsxAptioFix3Drv in Clover repo with some of your achievements. 1 Link to comment Share on other sites More sharing options...
vit9696 Posted January 12, 2018 Author Share Posted January 12, 2018 @Slice, I think it is the wrong approach, just like I and the rest told apianti above. If you do not think that integrating external repositories to the clover build system is worth the effort, I could suggest just using binary blobs of both AptioInputFix and AptioMemoryFix, which I could distribute on releases pages when they are stable enough. This should make things easier to both of us, especially to avoid issues that may arise during the backport/import. 7 Link to comment Share on other sites More sharing options...
Balamut Posted January 13, 2018 Share Posted January 13, 2018 Same things with the latest aptiofix, slide 0, 8, 64, 128 Still stuck at +++++++ I guess I’m the only unicorn that stuck on the old version. Link to comment Share on other sites More sharing options...
Guest Posted January 13, 2018 Share Posted January 13, 2018 Same things with the latest aptiofix, slide 0, 8, 64, 128 Still stuck at +++++++ I guess I’m the only unicorn that stuck on the old version. ciao Balamut, with vit9696 aptiofix no need of any slide setting which clover are you using? Are you using automatic KernelXCPM features? if so try to use old method for our cpu.. Link to comment Share on other sites More sharing options...
Riley Freeman Posted January 13, 2018 Share Posted January 13, 2018 I'm trying this on the three machines in my sig and it appears to be working fine. With AptioFix2Drv on the X79 and Samsung I would occasionally get a failed boot. It's too early to tell if this will also happen with AptioMemoryFix, but so far it hasn't. My Z68 needed AptioFixDrv (and SIP allow NVRAM) in order to boot as AptioFix2Drv failed almost every time. With AptioMemoryFix it's working fine and I can have SIP fully enabled. So it's a welcome improvement here so far. Link to comment Share on other sites More sharing options...
cecekpawon Posted January 13, 2018 Share Posted January 13, 2018 latest bin. X64.rar 8 Link to comment Share on other sites More sharing options...
goodwin_c Posted January 13, 2018 Share Posted January 13, 2018 @vit9696 Btw, with this two efi drivers - NVRAM works as expected, but keyboard in Clover menu is now almost unusable - it works in very weird manner, sometimes it accepts every button press but sometimes only after 3-5 retries. Is there any conflict with default Clover drivers that we should be aware, or this is issue directly related with your driver and we have to debug what's going on? P.S. If you need, you can find my hardware description in my signature on Applelife forum 1 Link to comment Share on other sites More sharing options...
bronxteck Posted January 14, 2018 Share Posted January 14, 2018 I believe AptioInputFix.efi is only for FileVault 2 use. if your not using FileVault 2 then you do not need to add AptioInputFix.efi. I think this was already mentioned here in this thread it is also stated on the repo. Link to comment Share on other sites More sharing options...
artur_pt Posted January 14, 2018 Share Posted January 14, 2018 Should not be. From what I remember this is the firmware check introduced in 10.12 or 10.13, and which verifies the hashes(?) for your firmware. If there is a mismatch, you firmware dump cleaned from personal information is sent to Apple for analysis. AptioFix should not be related anyhow. hello vit9696 the problem is in Aptioinputfix if use only the aptiomemoryfix I have no problems thanks 1 Link to comment Share on other sites More sharing options...
HmO Posted January 14, 2018 Share Posted January 14, 2018 how do you build the .efi from the source? macbuild.tool Link to comment Share on other sites More sharing options...
camillionario Posted January 14, 2018 Share Posted January 14, 2018 someone could share the files built to EFI. Or confirm if they correspond to these http://www.insanelymac.com/forum/topic/331381-aptiomemoryfix/page-3?do=findComment&comment=2568662 Thank you Link to comment Share on other sites More sharing options...
chris1111 Posted January 14, 2018 Share Posted January 14, 2018 I try but no Luck XCODE5/X64/MdePkg/Library/BaseLib/BaseLib/OUTPUT/X64/WriteTr.obj] Error 1 build.py... : error 7000: Failed to execute command make tbuild [/users/chris/Desktop/AptioFixPkg-master/edk2/Build/AptioFixPkg/DEBUG_XCODE5/X64/MdePkg/Library/BaseLib/BaseLib] build.py... : error F002: Failed to build module /Users/chris/Desktop/AptioFixPkg-master/edk2/MdePkg/Library/BaseLib/BaseLib.inf [X64, XCODE5, DEBUG] - Failed - Build end time: 12:39:23, Jan.14 2018 Build total time: 00:00:05 Edit ***** nevermind Fix Done Link to comment Share on other sites More sharing options...
cecekpawon Posted January 14, 2018 Share Posted January 14, 2018 If you may already have edk2 somewhere (with Clover, etc): cd edk2 git clone https://github.com/vit9696/AptioFixPkg.git export NASM_PREFIX="<path-to-bin>/" source edksetup.sh build -a X64 -b DEBUG -t XCODE5 -p AptioFixPkg/AptioFixPkg.dsc <path-to-bin> could be "/Users/${USER}/src/opt/local/bin" 2 Link to comment Share on other sites More sharing options...
chris1111 Posted January 14, 2018 Share Posted January 14, 2018 Working very well in my Optiplex 790 UEFI Mode No spam verbose boot, Drivers loading well all is perfect Thank you all DEVS Link to comment Share on other sites More sharing options...
Pavo Posted January 14, 2018 Share Posted January 14, 2018 Think I might try to figure out a way to build this inside a docker container Link to comment Share on other sites More sharing options...
bronxteck Posted January 14, 2018 Share Posted January 14, 2018 it seems to work on my clover legacy non UEFI desktop I put it in drivers64 and removed rc scripts and nvram.plist . my nvram var stayed but I guess some one else also needs to confirm as I see nvram.plist regenerated in efi volume Link to comment Share on other sites More sharing options...
PMheart Posted January 14, 2018 Share Posted January 14, 2018 Wrote a quick messy script some days ago, wish this might help someone else: [REMOVED DUE TO NEW FILE STRUCTURE] [EDIT] PLEASE SEE #90 1 Link to comment Share on other sites More sharing options...
bronxteck Posted January 14, 2018 Share Posted January 14, 2018 the link shows up as forbidden pmheart Link to comment Share on other sites More sharing options...
PMheart Posted January 14, 2018 Share Posted January 14, 2018 the link shows up as forbidden pmheart Oops. Yes I realised it, and I found that @vit9696 has changed the file structure, so I'll have to slightly modify the script, and will post the new one as an attachment [EDIT] HERE U GO [EDIT 2] Please see #90 for the new script. 3 Link to comment Share on other sites More sharing options...
bronxteck Posted January 15, 2018 Share Posted January 15, 2018 pmheart your script works it builds on desktop 1 Link to comment Share on other sites More sharing options...
Pavo Posted January 15, 2018 Share Posted January 15, 2018 Oops. Yes I realised it, and I found that @vit9696 has changed the file structure, so I'll have to slightly modify the script, and will post the new one as an attachment [EDIT] HERE U GO AptioMemory_Builder.sh.zip This doesn't work Cloning into 'AptioFix'... remote: Counting objects: 168, done. remote: Compressing objects: 100% (110/110), done. remote: Total 168 (delta 83), reused 141 (delta 56), pack-reused 0 Receiving objects: 100% (168/168), 221.55 KiB | 4.82 MiB/s, done. Resolving deltas: 100% (83/83), done. Missing mtoc or mtoc.NEW! To build mtoc follow: https://github.com/tianocore/tianocore.github.io/wiki/Xcode#mac-os-x-xcode You may also use one in external directory. % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 100 2262k 100 2262k 0 0 2489k 0 --:--:-- --:--:-- --:--:-- 2488k Missing mtoc or mtoc.NEW! To build mtoc follow: https://github.com/tianocore/tianocore.github.io/wiki/Xcode#mac-os-x-xcode You may also use one in external directory. cp: ./edk2/Build/AptioFixPlatform/RELEASE_XCODE*/X64/*.efi: No such file or directory Link to comment Share on other sites More sharing options...
Recommended Posts