Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 06/15/2018 in Posts

  1. Yep you can remove apfs.efi. This loader loads apfs.efi from JSDR section inside APFS Container which located on blockio device
    12 points
  2. 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.
    8 points
  3. Pesky missing </div>! Fixed the downloads display, it was breaking on any file with pictures :p
    5 points
  4. 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.
    4 points
  5. 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
    4 points
  6. I'm working on version detect
    3 points
  7. 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.
    3 points
  8. 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.
    3 points
  9. 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)
    2 points
  10. For all other donators, just send one of the Supervisors a PM and we'll handle it
    2 points
  11. 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.
    2 points
  12. 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
    2 points
  13. 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.
    2 points
  14. This is surely a nice driver if it will be added in the script.
    2 points
  15. 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.
    2 points
  16. @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?
    2 points
  17. Well, someone got promoted! :)) Congrats, @vector sigma! Looking forward to see the results.
    2 points
  18. 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
    2 points
  19. 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
    2 points
  20. 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
    2 points
  21. 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.
    2 points
  22. @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.
    2 points
  23. 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?
    1 point
  24. You may attach the text as zipped file or show three lines of mistake. ./buildmtoc.sh
    1 point
  25. 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..
    1 point
  26. We have a go 10.14, Xcode 10, 4545 and Build_Clover_mojave_Xcode10.command. Successful build out of the box. No need to copy CloverPrefPane, CloverUpdater or utils Clover_build_log.rtf
    1 point
  27. Yes, that fixed it. Nice work! By the way, if I have two APFS volumes, say High Sierra and Mojave, will it load the most recent driver?
    1 point
  28. Yeah, in my opinion, but this is just my opinion, and I'm definitely not an expert on the topic, Clover needs a cleanup of all the legacy code it still uses. If I'm not mistaken, it doesn't offer support for 32-bit anymore... At least not in the UI. So...I guess it's only a matter of cleaning up old, legacy code. But then again, I'm sure it's a lot easier said than done... And it's definitely a job for a team, not just a single guy.
    1 point
  29. but why would the script build 32 bit any ways if when you run the clover.command script and select the build process it actually asks you if you want to build for 64 bit or 32. so why is 64 building any form of 32 bit code. last time we even needed maybe some 32 bit code was lion for GMA950 and a few wifi cards... can clover still boot 10.4/ 10.5?
    1 point
  30. @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.
    1 point
  31. @KGP-iMacPro, @Pavo, found the reason and is my fault. @arsradu is right. Let me update something.
    1 point
  32. yes. in my case, if i don't use EmuVariableUefi, will get language issue after macOS update(example. 10.13.5 -> 10.13.6) this issue i reported(related prev-lang:kbd) long time ago in clover thread. but still there is a issue. so i'm still using OsxAptioFix2Drv-free2000 + EmuVariableUefi. EDIT1 first report https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?do=findComment&amp;comment=2565871 two report https://www.insanelymac.com/forum/topic/284656-clover-general-discussion/?do=findComment&amp;comment=2566330
    1 point
  33. 1 point
  34. Bro', is written to your screen shot, post the log at /Users/kgp/src/tools/logs/mtoc.make.log.txt ... working on it, thanks What to say, I like to play with these things
    1 point
  35. 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
    1 point
  36. Alright. Will try that when I get home. Update: Ok...so let's see. I downloaded both versions of Nightwish and added them BOTH to Clover/themes. I renamed Nightwish256 to Nightwish@2x. Clover configurator -> Theme Editor, set DesignHeight to 1110px GUI -> Remains unchanged (Nightwish) If that's correct, then I've got two issues to report: 1. non functional mouse and keyboard in Clover UI, so it's a good thing that it boots by default to the correct partition. I couldn't even take a screenshot since none of the keys worked. 2. huge icons. For comparison, this is what the old version I had looks like on the 1440p monitor.
    1 point
  37. I didn't notice any issues but ill have a look on my system.
    1 point
  38. 1 point
  39. DON"T Mind This Post, I Fixed It! I was missing IntelGraphicsDVMTFixup.kext. Guys, Has anyone succeeded with installing Mojave with iGPU (Intel HD530) and RX 580 active at the same time? I recently enabled my iGPU to test if I can fix the menu's transparency and did a clean install but once the macOS is installed and boots up I get black screen. I can hear the voice over but both displays are black. I tested with and without IntelGraphicsFixUp,WhateverGreen and -lilubetaall. macOS High Sierra doesn't have the same issue and everything works perfectly normal. Thanks for your precious input in advance.
    1 point
  40. 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!
    1 point
  41. i'm using High Sierra HFS, very fast as usual xD
    1 point
  42. run it, post generated files RunMe.app.zip
    1 point
  43. 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
    1 point
  44. Welcome, Enjoy! Now i apply generics patches for GPUs, all ppl can use same DSDT in same mobo
    1 point
×
×
  • Create New...