Search the Community: Showing results for tags 'boot.efi'.
Found 3 results
Andy Vandijck posted a topic in CloverI updated Clover 2937. I added support for BlockIo2 and DiskIo2 in rEFIt_UEFI. I also added my (even more updated) efifs filesystem drivers to the build. They now are fully fixed (added suggested fixes for FreePool and updated the sources to not use some GNU functions but instead directly define them as their UEFI equivalents). The FS drivers are now about 50% in size of what they where and they really are a lot faster and more stable. I also include AppleHFSPlus-32.efi and AppleHFSPlus-64.efi in the installer (Apple's HFSPlus EFI driver). The Clover tools (bdmesg, etc...) are all built with signed binaries for i386 and x86_64, I used my apple developer certificate. I also signed the .efi binaries using the certificates included in Clover. I made some databases from those keys, they are included in the zip and installed to /etc/securebootdb along with the RC scripts. The binaries included are PK, KEK and DB. You can install these on some UEFI firmwares from within the UEFI BIOS menu (on AMI Aptio for example, as I tend to use those myself...). I built this version of Clover with my own custom blend of gcc-4.9.1 and also updated the ebuild.sh script to accept -gcc49. All nicely wrapped in the installer package, also built the 32-bit and 64-bit bootable .iso files. Source diff is included... EDIT: New updated version (and built for the latest official too). I figured out that in order for the mtoc tool to properly convert the binaries from Mach-O to PE(+) one must first strip the Mach-O file prior to running the mtoc command. I updated the build_rule.txt flile (to use the strip tool on the binaries before conversion) and also updated the tools_def.txt file (to define the strip tool so it can be used by the build process). This results in full building possibility using Xcode's Clang only. I had to update the sources in order to fully build all of the Clover parts using Clang. I updated also and optimized more my UEFI FS driver package. All 56 drivers can now be built using GCC or Clang and are also included in the installer package (including the GRUB FAT driver, built now directly as MINIFAT.efi). More updates to the ebuild.sh script where also done as I found a bug in which case it didn't properly set Clover's version and thus create a Version.h without a proper version added inside. In order to build Clover and it's package or ISO's, I have made a separate script as ebuild.sh made somehow a mess of the build. It directly builds all major versions of Clover (32 and 64 bit, regular and BIOS Block IO versions). I also did some updates to the BootSector files. efi64.com2 can now also be built as efi64.com64 (updated Makefile using GCC toolchain with build flags for 32 and 64 bit build). In case of building efi64.com64 it uses the x86_64 target and this meant I had to modify the efi64.S sources to make it compatible. I also optimized and fixed fully gptsync. The new version also builds using only the essential GUID definitions and libraries linked in. It works a lot better and I took also my time updating the source code. I fixed and optimized every .c file. gptsync.inf GUID's and libraries: [LibraryClasses] UefiApplicationEntryPoint UefiLib MemoryAllocationLib BaseMemoryLib BaseLib DevicePathLib [Protocols] gEfiBlockIoProtocolGuid gEfiBlockIo2ProtocolGuid This is all the dependencies that are required to properly build gptsync. I did similar updates to the UEFI FS package, I optimized everything and also removed some unnecessary files from some drivers. They work now perfectly. Source diff is included, as is my build script for building Clover and it's generated ISO's / package files. Both GCC 4.9.1 and Xcode 5.1 Clang versions are uploaded Enjoy Clover2341_Updates_Patch.diff.zip build_clover_xcode5_clang.sh.zip Clover-2941-Xcode-5.1-Clang-Bin.zip Clover-2941-GCC-4.9.1-Bin.zip
I created a hackintosh specific version of the MacOSX bootloader. I tested it so far under legacy Clover. Project page including more downloads: https://github.com/andyvand/macosxbootloader Built result hack specific is attached. Test please, I need feedback as this is a new version. Might need some more fixing here and there. When testing please note the following in the report: - Legacy boot / UEFI boot - 32 / 64 bit Clover use - Result This one is Yosemite optimized and should work (support for hackintosh in initial stage) EDIT: New version. Added strict warning, enable all warnings flag and set warnings as errors flags, fixed some issues, implemented -f support and finally made sure everything was built optimized. Also reimplemented driver loading (now works optimal and fast). EDIT2: Added Clover build tools version. boot.efi.zip boot.clovertools.efi.zip
cecekpawon posted a topic in OSx86 10.12 (Sierra)Been a week that Im bored with current black apple boot & trying to get something else with my macpro6,1 hack (without changing it). In contrary, we can found on other forum they (with older / unsupported real mac) had been struggle to get black apple boot & solve it by binary patching mac bootloader / with the help of a forked tiamos macosxbootloader with greats support. What Im willing to know, is there any hack (bin patch / storing NVRAM) other than this to feed my needs? Is all that possible on newer boot.efi (currently 10.12). Please share ... References: macosxbootloader, (boot.efi) binary it self, thread. Tools to use: Hopper, Clover (mod, which able to patch boot.efi onthefly). For drawing logo, in macosxbootloader, they have following process: But in binary, I got this: By patching a conditional jump below, it prevent the screen to be swap / filled with black color & allowed me to use my gray background previously set by Clover (ClearScreen (&StdBackgroundPixel)). But I got white apple logo with black rectangle with correct progress bar color (see attachment, kBootArgsFlagBlackBg to use white progrees bar). So I try to apply same patch for DrawDataRectangle (in 'sub_a532' ; ## 3 CspDrawRect) which seems identical for me. Yes now it draw gray rect on logo, but I lost the logo. After this, what I cannot figured out is what & where they compose the logo with CLUT things? Things that I also have tried: - Set bootcfg with kBootArgsFlagBlack | store NVRAM: "BlackMode" / "DefaultBackgroundColor" / "Background Color" take no effect. "BackgroundClear" currently obsolete? - Yes sometimes it show gray boot with a half of progress bar and then black.