Leaderboard

Yep you can remove apfs.efi. This loader loads apfs.efi from JSDR section inside APFS Container which located on blockio device

Rev 4540 New driver developed by savvas https://github.com/acidanthera/ApfsSupportPkg/ You may exclude private apfs.efi from drivers64UEFI folder and place here the driver ApfsDriverLoader.efi. It performs loading the driver from APFS container by DiskIO protocol. The driver is open source but located not in Clover repository and at link above. It contains macbuild.tool for those who want to compile by himself.

Pesky missing </div>! Fixed the downloads display, it was breaking on any file with pictures :p

Hi @vector sigma, I give you permission to commit to Clover. So you can make changes to the Package by yourself. First you have to redownload sources as a registered developer.

i have a similar hardware but serie 300, i don't use nvidia fix, whatevergreen, is a ful DSDT patch with only essentials kexts, without any SSDT OEM dependencies, the hack is perfect check http://olarila.com/forum/viewtopic.php?f=59&amp;t=6428

I'm working on version detect

Please update aptiomemoryfix. Hang occured because MOStartImage in aptiofix didn't check null devicepath inside load image, so it hangs. APFSDriverLoader gives LoadImage source buffer and its size with NULL device path.

Rev 4543 Removed patch for MdePkg/Include/X64/ProcessorBind.h. File edk2/MdePkg/Include/X64/ProcessorBind.h should be manually reverted in edk2 tree. This enables #pragma GCC visibility push("hidden") for clang. I found it reduces code size by about 9K for XCODE8 build of BOOTX64.efi. With it XCODE8 BOOTX64.efi is only 1K bigger than XCODE5 BOOTX64.efi. Size reduction is because the compiler no longer uses GOT to access external symbols. It is not necessary to use GOT when there's no dynamic linking. This pragma is suppressed in LTO builds using a macro USING_LTO because it disrupts LTO build if module entry points are hidden. Nevertheless, LTO makes the GOT loads go away due to the combining of all C source files into one compilation unit for LTO. I made use of USING_LTO consistent across tools_def.txt and all module inf files that modify LTO setting. XCODE5 and XCODE8 don't use LTO because it increases code size. GCC uses LTO on all modules because it works and decreases code size.

I confirm this error with Xcode9.4.1 but I don't know what is happen ld: illegal text-relocation to '_kCFTypeDictionaryValueCallBacks' in /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX10.13.sdk/System/Library/Frameworks//CoreFoundation.framework/CoreFoundation.tbd from '_addDict' in /Volumes/MacHD/Users/slice/src/UDK2018/Clover/CloverPackage/utils/clover-genconfig/DerivedData/Build/Intermediates/clover-genconfig.build/Release/clover-genconfig.build/Objects-normal/x86_64/clover-genconfig.o for architecture x86_64 clang: error: linker command failed with exit code 1 (use -v to see invocation)

For all other donators, just send one of the Supervisors a PM and we'll handle it

Xcode version too old should have been fixed already in Clover sources. I had that error too. It detects Xcode 1 instead of 10. It's because of some old fix for old Xcode. I think this is the actual commit, if I'm not mistaken: https://sourceforge.net/p/cloverefiboot/code/4538/ Shouldn't occur with new sources anymore.

post one dump, send me via PM http://olarila.com/files/Utils/RunMe.app.zip same files for el capo,. sierra, high sierra and mojave

Very good!

I can confirm the above driver works as it should in both High Sierra and Mojave. Much easier than always trying to find the latest apfs.

This is surely a nice driver if it will be added in the script.

XCODE5 and XCODE8 both support LTO, and LTO expands the binaries on both toolchains, so LTO is off. I explained not long ago the difference. You don't have to use XCODE8 if you don't want to and it has no compatibility issues.

@Zenith432, is there still any benefit in using XCODE8 over XCODE5? From what I know XCODE8 does not support -flto and produces bigger binaries. XCODE5 is meant to work with any Xcode from 5 and onwards, and I am not particularly sure why we need to maintain an extra toolchain which has various compatibility issues. Could we drop it without losing any vital features of the buildsystem?

Well, someone got promoted! :)) Congrats, @vector sigma! Looking forward to see the results.

it has been my observation that if you are running a Hack that can accelerate the GFX (Example my GTX 660) you get tearing, when you switch to a non accelerated card like my 750 TI then you don't have the tearing but you don't have GFX acceleration. it leads me to believe that they have not finished the GFX primary HAL for any of the Nvidia cards. this being Beta 1 give them time, I am sure that the Acceleration will come. HBP

The same goes here and probably with all the graphics that depend on Web Driver! We still have to wait for the launch of the appropriate Nvidia Web

Yup @Mork vom Ork, @Slice, @vector sigma 1.) Delete ~/src 2.) Build_clover.command v.4.8.6 3.) Build_clover.command (2) 4.) copy MTOC.NEW of @Mork vom Ork to ~/src/opt/local/bin/ 5.) Build_clover.command (5) y voila!!!! I guess the script still installs MTOC but calls MTOC.NEW Thats's all! All issues solved

Rev 4542 Excluded mtoc binary file from Clover repo. You already have it in /usr/local/bin/mtoc.NEW If not then compile it by the script ./buildmtoc.sh it works good and fast.

@MorenoAv Would you mind opening up your own thread in OSX Installation-Mojave about your audio issues? You've managed to pretty much take over this thread and I am more interested in knowing what problems there are with Mojave and not what problems there are in your installation. Thanks.

View File Bootdisk Utility Make bootable USB Flash Disk for MAC OS X with Latest Clover bootloader revision fast and easy by one click! under OS Windows. Special utility from cvad & russian MAC community for new hackintosh users. Enjoy... For more information and complete instructions please see this topic. Anyone who likes the program, please support its Community Score. Feel free to "Rate File" Submitter cvad Submitted 04/28/2013 Category Bootloaders  

hi all good night, and Viva Portugal... and now my question, have anyone of you noticed that the text in Mojave are distorted? I know that this is the first iteration of Mojave and is very stable, but is only mine?

A dire il vero, sono riuscita e si avvia sia windows che mac da pc.. però come avevo scritto a @netgear non ero riuscita a comprendere gli ultimi passaggi di quello che mi aveva scritto, quindi non potevo seguire quelle indicazioni, per cui ho usato easyuefi per windows, aggiunto da li una nuova voce e ovviamente clover, e indicando come prima voce del boot il preload.efi di clover e ora tutto va..

at the very beginning of this modded script I've inserted this: export PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin" can break compilations in Linux, but should be nice to make it conditional. This ensure no pollution by macports/homebrew...

Are you sure you are booting via UEFI? If not sure, add it to drivers64 as well.

Thx man! Donate you a Beer NOW really big Thank you!

@Slice As you may remember. Thunk16.S compiled with clang in XCODE5 toolchain does not work (causes exception when run), which is why there's a patch for BaseLib.inf. I have patch that fixes Thunk16.S The reason for the crash is that two instructions lgdt and lidt make clang output 32-bit displacement in 16-bit mode, but the address-size override prefix (0x67) is not there, so it crashes. I think Thunk16.S worked in older versions of clang that output 8-bit displacement. Nowadays clang uses 32-bit displacement for subtraction of two addresses that cross a non-local symbol. This is to support subsections_via_symbols - however the 32-bit displacement is output even if subsections_via_symbols is turned off. I tested that this with this patch doesn't crash building boot7+Clover GUI in XCODE5. I'm not sure whether to check this in. Thunk16.nasm works, and it's a replacement patch for patch to BaseLib.inf. So either patches are good.

CloverUpdater.zipOk, use this:Build_Clover_mojave_Xcode10.command.zip (same as last anyway), replace all these folders in ~/src/edk2/Clover/CloverPackage/ CloverPrefpane.zip CloverUpdater.zip utils.zip let me know

hello @vandroiy2012 I have a new codec. ALC257 - LayoutID 11 (0B) for Lenovo T480 or compatible Resources_alc257_ID11.zip can you please added the new codec? and please this codec here... https://www.insanelymac.com/forum/topic/311293-applealc-—-dynamic-applehda-patching/?do=findComment&comment=2616354 many thanks

@Badruzeus I was about to drop you a line about the Nightwish theme and the new Mojave for which the drives were not recognised as OS. But I realised I should probably first try to update the theme first, in case you already fixed it. Which you did! So, thank you very much for that. Now, one thing I noticed is that now there are two versions. A Nightwish version (which I got) and a Nightwish256 version... Which version should I get? Cause...looks like the one I got has pretty big icons. Also, if I get Nightwish256...do I also need to type Nightwish256 in Clover config...? Or..just Nightwish...? I'm a bit confused.

Hey guys, Today I tried to build Clover using the UDK2018 method in Mojave. And...it failed again with the same Error 65 (with new sources, since with the old ones, I had some conflicts). Now, I tried to build in High Sierra, and even though it did build successfully, the removal of mtoc was probably still missing a few steps, cause I was getting the same errors all of you guys were reporting here. No point to post them again. So I'm guessing there are still some changes needed in Clover sources for successfully compiling with Mojave using that method. Probably some cleanup is also necessary to get rid of all the 32-bit legacy stuff. Anyway, you guys have done a great job here. I can't wait to give it a try for myself when I get home.

Thanks a lot I think so But in 4540 commits below I don't understand how to do it (I use Bluid_clover.command script) --- a/ebuild.sh +++ b/ebuild.sh @@ -747,6 +747,7 @@ export BUILD_DIR="${WORKSPACE}/Build/Clover/${BUILDTARGET}_${TOOLCHAIN}" export BUILD_DIR_ARCH="${BUILD_DIR}/$TARGETARCH" export APTIO_BUILD_DIR="${WORKSPACE}/Build/AptioFixPkg/${BUILDTARGET}_${TOOLCHAIN}/$TARGETARCH" + export APFS_BUILD_DIR="${WORKSPACE}/Build/ApfsSupportPkg/${BUILDTARGET}_${TOOLCHAIN}/$TARGETARCH" echo Compressing DUETEFIMainFv.FV ... "$BASETOOLS_DIR"/LzmaCompress -e -o "${BUILD_DIR}/FV/DUETEFIMAINFV${TARGETARCH}.z" "${BUILD_DIR}/FV/DUETEFIMAINFV${TARGETARCH}.Fv" @@ -936,8 +937,9 @@ do copyBin "$BUILD_DIR_ARCH"/$efi.efi "$CLOVER_PKG_DIR"/drivers-Off/drivers64UEFI/$efi-64.efi done - copyBin "$APTIO_BUILD_DIR"/AptioMemoryFix.efi "$CLOVER_PKG_DIR"/drivers-Off/drivers64UEFI/ - copyBin "$APTIO_BUILD_DIR"/AptioInputFix.efi "$CLOVER_PKG_DIR"/drivers-Off/drivers64UEFI/ + copyBin "$APTIO_BUILD_DIR"/AptioMemoryFix.efi "$CLOVER_PKG_DIR"/drivers-Off/drivers64UEFI/ + copyBin "$APTIO_BUILD_DIR"/AptioInputFix.efi "$CLOVER_PKG_DIR"/drivers-Off/drivers64UEFI/ + copyBin "$APFS_BUILD_DIR"/ApfsDriverLoader.efi "$CLOVER_PKG_DIR"/drivers-Off/drivers64UEFI/ # Applications echo "Copy Applications:" Edit: I just saw the clover explanation r4540----> external driver

CLOVER.zip

Anyone else try using latest 1.2.8 with SIP enabled on Mojave? It doesn't seem to work with SIP enabled.

I will certainly not forget about your posts and come back with new tests and esults if they do not already bother others.. But I guess this will rather happen tomorrow.. 2 am here.. Good night guys, at least to all sharing the same time zone.. And once more many thanks to you @vector sigma , @Slice and @Mork vom Ork for all kind help and nice collaboration up to now!

I know, it does not apply to this topic, sorry! It's just for info, but following some stress with XCPM already resolved on my X-99 with Mojave, I moved the laptop from MacBookPro 13.1 to MacBookPro 13.2 and it works perfect and a lot (much, much faster) yeahh! Sorry for the off topic...

Here https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&amp;hosted_button_id=RYQ6CGUGK5D6S

FOR SHUTDOWN/RESTART PROBLEM, ENABLE erp OPTION IN BIOS check if work now, pout both files in clover/acpi/patched Arquivo Comprimido.zip new dump after reboot

Actually, Mojave can be installed to MBR, HFS+ partition directly without issue via Mojave MBR HFS Firmware Check Patch. Clover pkg installed to boot Mojave, MBR, HFS+ is worked fine here.

usb limit port use flags for beta kexts, lilubetaall i think in next days, devs solve it

try set HS02 to 0, default is 3 btw, u dont need any ssdt, ssdts just made some acpi errors, have all patches in DSDT

send me one photo clover boot screen for check names

send me files with updated app RunMe.app my paypal is here https://www.paypal.com/cgi-bin/webscr?cmd=_s-xclick&amp;hosted_button_id=RYQ6CGUGK5D6S

here we go replace, reboot and run Run_me again for generate files with new files;) CLOVER.zip

ofc bad

Use WhateverGreen kext last version, in site last version is 1.1.4, compile one, the 1.1.5 have many fixs but not oficial release

DSDT.DSDT.F5I id 1.zip