Jump to content

Leaderboard

Popular Content

Showing content with the highest reputation on 07/18/2019 in all areas

  1. After a bit of digging around, the answer is definitively YES, it is possible to pure UEFI boot from CD/DVD, but a lot depends on the (U)EFI firmware doing the booting. The standard Clover ISO only consists of a single 10MB HFS+ volume which can be EFI booted by firmware that understands HFS+ eg Apple machines and VMware Virtual Machines. For it to boot on standard PCs, however, only the legacy pathway is available via the cdboot/eltorito pathway. On the other hand, Ubuntu and Linux Mint Installation ISOs have dual formats for UEFI boot or Legacy boot 1) A 2.4MB FAT efi.img that contains grubx64.efi and functions as a "mini" EFI, recognizable for UEFI booting by standard PCs 2) A much larger ISO9660 file system that has all of the installation files and can also boot via the legacy eltorito pathway. I was able to adapt this procedure from the Debian Wiki: RepackBootableISO, to repack the Clover ISO with an extra 2.4MB FAT efi.img containing CLOVERX64.efi, UEFI drivers, FakeSMC, the embedded theme and a custom config.plist that works for @arsradu to test on his system.... Note: the About Clover GUI screen that shows firmware booting by American Megatrends (not Clover EFI so NOT legacy boot).....and it boots his system fine . Ingredients needed to make a real UEFI bootable Clover CD/DVD 1) A special mbr_template that enables the booting off the 2.4MB FAT efi.img (extracted from Linux Mint 19.1 Installation ISO) ... isohdpfx.bin ---> I saved it to /home/fusion71au/Downloads/CLOVER/isohdpfx.bin 2) A 2.4MB FAT efi.img that contains CLOVERX64.efi, UEFI drivers, FakeSMC, the embedded theme and a config.plist 3) xorriso utility in Linux (Homebrew version for OSX here). I was able to compile Clover with Build_Clover.command, then repacked the Clover ISO with xorriso with the following terminal commands... new_files=~/src/edk2/Clover/CloverPackage/sym/CloverCD new_iso=~/src/edk2/Clover/CloverPackage/sym/CloverISO-5018/Clover-v2.5k-5018-X64_UEFI.iso xorriso -as mkisofs \ > -r -V 'Clover-v2.5k-5018-X64.iso' \ > -o "$new_iso" \ > -J -J -joliet-long -cache-inodes \ > -isohybrid-mbr '/home/fusion71au/Downloads/Clover/isohdpfx.bin' \ > -b /usr/standalone/i386/cdboot \ > -boot-load-size 4 -boot-info-table -no-emul-boot \ > -eltorito-alt-boot \ > -e /EFI/CLOVER/efi.img \ > -no-emul-boot -isohybrid-gpt-basdat -isohybrid-apm-hfsplus \ > "$new_files" End result....Clover-v2.5k-5018-X64_UEFI.iso PS: If you want to play around with that efi.img, you can mount it as a loop device in Linux... Say it is in your ~/Downloads folder Open terminal and type sudo mkdir /media/floppy1 sudo mount -o loop ~/Downloads/efi.img /media/floppy1/ Should then see something like this.... You can add/delete files to the volume as the root user. As you can see, I only have about 300kB left to play with . To unmount the volume, just click the "eject" icon.
    6 points
  2. Thank you for the Forks its work on my HP ProBook 6570B Forks
    2 points
  3. for those who have problems with ATIController::TestVRAM crashes during boot, i've created a patch for clover for solving this problem. second patch removes magenta-colored lines which appears at screen during video driver startup. <dict> <key>Comment</key> <string>ATIController TestVRAM boot failure patch</string> <key>Disabled</key> <false/> <key>Find</key> <data> uapVqlU7DJA= </data> <key>InfoPlistPatch</key> <false/> <key>Name</key> <string>AMDSupport</string> <key>Replace</key> <data> uapVqlU5yZA= </data> </dict> <dict> <key>Comment</key> <string>ATIController TestVRAM magenta-colored lines patch</string> <key>Disabled</key> <false/> <key>Find</key> <data> xwSxqlWqVQ== </data> <key>InfoPlistPatch</key> <false/> <key>Name</key> <string>AMDSupport</string> <key>Replace</key> <data> kJCQkJCQkA== </data> </dict> Insert this is KextsToPatch section. PS: patch is beta version, tested only with 10.14.5 + Vega64, but must be compatible with any AMD card. TestVRAM fills memory with 0xaa55aa55 bytes (it's magenta pixels you see at screen), and it's tries to test too much of address space, writing this bytes to framebuffer memory. If you have verbose mode enabled (as i have), there are possibility that framebuffer will scroll during this test, and TestVRAM will write 0xaa55aa55, but read 0x00000000 (because magenta-colored pixels are scrolled up).
    2 points
  4. @fusion71au I think it was a little more than "a bit of" digging around. :)) It was a lot of digging. In and around. All started from a simple question: if they can do it, why couldn't we? Cheers! And thank you! Edit: bdmesg added if you wanna take a look. Terminal Saved Output Clover ISO UEFI
    2 points
  5. I'm using Apple's USB keyboards and I have no issues using the Caps Lock (See? LOL) I guess as you said Apple's focus is to make us use real Macs BUT bit by bit, first we use Apple's peripherals and then the displays and so on and so forth until we completely switched to using real Macs
    2 points
  6. Yep the Clover installs the files on the root instead of the ESP here's the Diskutil list output: another update by @ricoc90 request:
    2 points
  7. I recently acquired the NUC Hades Canyon at a bargain and thought it was almost the perfect computer for me: extremely tiny, has a powerful GPU, and a lot of ports. The only downside is that it doesn't run OSX (well). Since this is my ideal Mac Mini, I called the project HaC mini and have been working on it for the past month. The goal is to have a perfect build that is indistinguishable from a real Mac. That means every hardware and software feature works perfectly. I have a background in hardware and platform engineering but no experience in Hackintosh, so this was a great learning opportunity for me as well. In the spirit of learning, I'm also releasing a series of writeups for various hard issues that I resolved in hope that it will help future hackintoshers. These writeups are independent of the NUC Hades Canyon. NUC Hades Canyon Installation Guide Writeup - Fixing Metal Drivers Writeup - Fixing Thunderbolt Hotplug Writeup - Fixing HDA Audio Some improvements to existing Hades Canyon work I've seen previously: Metal graphics issues fixed Workaround for 10.14.5+ GPU panics Thunderbolt 3 working including hot plug, usb-c + hot plug, boot without anything connected, sleep, wake, etc SDXC port working Second ethernet port working Power management working Some highlights in general: Full graphics acceleration Working services: iMessages, iCloud, Siri (with built in mics), Find My Mac, FileVault, etc Working Handoff, Continuity, Universal Clipboard, Apple Watch unlock with swapped Wifi card Multiple displays, two ethernet ports, TB3, eGPU with eject Pretty much everything works, there's some very specific hardware issues documented here and are being worked on. Front headphone doesn't work yet, SPDIF digital audio doesn't work yet Most USB ports have sleep/wake eject issues (this is a hardware/BIOS problem) For TB3 to work you must have at least one TB or USB-C device plugged in on boot and during wakeup (you are free to unplug and hot-plug while running)
    1 point
  8. Let me know when it's ready haha. I'd love to see it. By the way, remember to remove the Boot argument shikigva=60 from the clover for VDA decoder to work properly with Vega and iMac Pro 1.1 I forgot to mention that in the previous post.
    1 point
  9. You can use Hackintool to disable Gatekeeper and mount your disk as RW.
    1 point
  10. done. Thanks for the revision, I just wonder why it happened.
    1 point
  11. I agree with you. I have problem with OC with iGPU enabled, so here are what I've done: 1- Back up clover and bios profile 2- Remove the device properties for iGPU in Glasgood config. 3- Turn off iGPU completely in your bios 4- Change SMbios and redo iMessage config Enjoy the Vega power. If you're using rx580 or 590, iGpu will win, since Vega, it's much better to use Vega. Here is my result testing different SMBIOS on Vega 56 for your reference:
    1 point
  12. @vit9696 implemented this patches in WhateverGreen.kext. Changes already in master. https://github.com/acidanthera/WhateverGreen/commit/bcd3f2ef73266f4a320ccfd0686bef2a969b2bde Here is prebuild binary WhateverGreen-1.3.1-DEBUG.zip Anyone welcome to test it.
    1 point
  13. @CyberdevsThanks for giving your time to make apps. for others. I just ran the app and my TP-LINK 4800 WiFi card worked thanks again
    1 point
  14. The app work well for me on 10.15 Beta (19A512f) thank you
    1 point
  15. 1 point
  16. I hope the guys will find the solution to fail the Logitech keypad on macOS Catalina.
    1 point
  17. The error code 0xe00002ed refers to an IO error communicating with the Bluetooth device. Have you ever had Bluetooth working on your Hackintosh? You shouldn't need to edit any plist for your device (0a5c:6412) as it's already supported. It also has the latest firmware (12.0.1.1010).
    1 point
  18. Working now and finished updating, thank you
    1 point
  19. Congrats. Please now change the topic title to: [solved] Elan touchpad vodooi2c act strange
    1 point
  20. Solved since latest update installed¡¡¡ Thanks everybody for your help¡¡¡
    1 point
  21. Rev 5000+ Now Clover version 2.5k. It assumes new folder structures drivers BIOS off UEFI instead of older folders drivers64 (now drivers/BIOS) and drivers64UEFI (now drivers/UEFI). As well I have to note that there is no automatic update from 2.4 to 2.5. CloverUpdater can't switch versions. You have to install new version manually and carefully check drivers directories if all needed files presents here. Thanks Chris1111 for the picture!
    1 point
  22. There might be a bit of confusion here. Legacy boot should work now that you proved it does with r3911 . Install latest Clover r4996 with pkg installer in legacy mode targeting your USB drive (custom option: install in EFI etc) Make sure all your needed efi drivers are in EFI/CLOVER/drivers/BIOS, normal kexts, config.plist present in their respective folders etc Delete the file named "boot" at the root folder, / , of your USB drive's EFI partition (this is actually boot6=CloverEFI 64 bits SATA, renamed as "boot") Replace with boot7 = CloverEFI 64 bits BiosBlockIO (which I extracted from official Clover r3911 ISO on Sourceforge) on the root of the USB drive, renamed as "boot" Try legacy boot again to your USB... 46 minutes ago, arsradu said: Can't forget something I never knew I needed. :))) But yeah, that part was missing. Thank you! Make sure you put the working boot7 from Clover r3911 in ~/src/edk2/Clover/CloverPackage/CloverV2/Bootloaders/x64 before running makeiso_boot7 from your ~/src/edk2/Clover/CloverPackage folder. Otherwise it also won't be present in your Clover ISO . Also regarding the missing embedded theme in your ISO: Did you copy the embedded theme folder from ~/src/edk2/Clover/CloverPackage/CloverV2/EFI/CLOVER/themes to ~/src/edk2/Clover/CloverPackage/CloverV2/themespkg before running makeiso? Yes, this is an acidanthera project now. If you build Clover with Build_Clover.command and specify XCODE5 toolchain, you will still find it compiled in the ~/src/edk2/Build/AptioFixPkg/RELEASE_XCODE5/X64 folder ---> manually copy it to your ~/src/edk2/Clover/CloverPackage/CloverV2/EFI/CLOVER/drivers/off/UEFI/MemoryFix folder. Then cd to ~/src/edk2/Clover/CloverPackage and run ./makepkg to create the Clover installer.
    1 point
  23. Thanks for sharing your findings I know that there are issues with only using the AirPortAtheros40.kext, there are other dependencies and I'm already working on my Atheros Installer and it's working on my WiFi adapter by adding some extra kexts. I'm still testing it so it will be ready soon.
    1 point
  24. Please do not ping me into RGB nonsense, thank you.
    0 points
×
×
  • Create New...