Jump to content

fusion71au

Gurus
  • Content Count

    1,008
  • Joined

  • Last visited

  • Days Won

    15

fusion71au last won the day on July 18

fusion71au had the most liked content!

7 Followers

About fusion71au

  • Rank
    InsanelyMac Legend

Profile Information

  • Gender
    Male

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. @tarasis, Clean install method should work without stalling if you remember to boot back into the installer ISO CD on the first reboot ---> open terminal and run copyprelinkedkernel script (step3 under "Installation" in the guide post). Alternatively, as you described, temporarily changing the Guest Type to Windows 10 X64 also works but did you remember to switch it back to macOS (from Windows 10 X64) after you get past the stall and reboot to final end user setup? Re memory panic with Clover: often a reboot fixes it . Not sure about your specific keyboard issues...do you have another (different brand) USB keyboard to try? Some people reported a Caps lock problem on their logitech keyboards ---> disconnecting/disabling their keyboards in DP4/DP5 (but fixed in DP6). Also with Catalina's new "read only" system volume and security settings, you may need to mount the / folder as R/W and disable System Integrity Protection (SIP) + osx gatekeeper before running the package installer for VMware tools - see previous post. @Naki, Firefox bug fixed in DP6_19A536g. I have no problems with installing VMware tools and can change macOS guest window size/screen resolution on the fly. Do you have System Integrity Protection (SIP) in Catalina disabled? Besides using Clover, you can also disable SIP by booting to macOS Recovery or the Catalina Installer ISO and disabling it from terminal... csrutil status // This command shows whether SIP currently enabled or disabled csrutil disable // This command disables SIP when used in Recovery/Installer terminal and needs System Reboot. Reversed with csrutil enable Are VMware tools kexts loading? What is the output from terminal after typing kextstat | grep -v com.apple Do you see VMwareGfx.kext?......
  2. IMHO, I find VMware currently provides a faster/better experience than VirtualBox, mainly because of NVRAM and VMware tools support for the macOS guest (which is absent in VirtualBox).
  3. fusion71au

    [pre-release] macOS Catalina

    Cosmetic bugs in DP6, reported even in real macs eg @DuncanGarp reported the disk icon issue with Catalina installed on an external drive for his real MBP2012. Also noticed the "blank circle" issue when trying to change default profile picture as mentioned by @avz. Hopefully Apple will fix later.
  4. fusion71au

    [pre-release] macOS Catalina

    @dosdude and @ASentientBot deliver the goods again for legacy machines with non metal cards . Successful upgrade to Catalina DP6_19A536g on my legacy Dell XPS M1530 Core2Duo laptop with Nvidia Tesla 8600M GT accelerated graphics... Prepared USB installer from full app with @dosdude's latest macOS Catalina Patcher v1.0.7 ---> boot to installer with Clover r5018, bypassing machine compatibility checks. The patched InstallESD.dmg automatically installs the required legacy video kexts so no post install patching required. Also omits /System/Library/UserEventPlugins/com.apple.telemetry.plugin during the install, so we avoid any kps for Core2Duo CPUs.
  5. fusion71au

    Clover General discussion

    Caused by update to Ukrainian translation name commit r5038. Fixed by renaming /CloverPackage/package/po/uk_UA.po to shorter form - either uk.po (like before the commit) or ua.po
  6. fusion71au

    Clover General discussion

    Good question. Since I was using the Linux Mint 19.1 ISO as my template for a UEFI bootable CD/DVD, I reused its isohybrid-mbr and 2.4MB FAT efi.img for creating the Clover UEFI ISO. I have since created a larger 10MB FAT efi.img... mkfs.msdos -C ~/src/edk2/Clover/CloverPackage/sym/CloverCD/EFI/CLOVER/efi.img 10240 and compiled successfully with xorriso, Clover-v2.5k-5027-X64_UEFI.iso.zip. This also EFI boots Catalina DP4 OK on my VMware12 virtual machine.... Awaiting @arsradu's real world testing on his system <--- Edit: confirmed working on real hardware. Yes, MEMORY FIX drivers are just for UEFI booting. Never needed AptioMemoryFix.efi for Clover's legacy boot because Clover has its own EFI firmware (based on DUET, not Aptio).
  7. fusion71au

    Clover General discussion

    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.
  8. fusion71au

    [pre-release] macOS Catalina

    Haven't updated yet but what about with boot flag -nehalem_error_disable? Forget that. I was thinking of AppleTyMCEDriver.kext Edit @dosdude and @ASentientBot deliver the goods again Successful upgrade to Catalina DP4_19A512f on my legacy XPS M1530 Core2Duo laptop with Nvidia Tesla 8600M GT. Prepared installer USB from full app with @dosdude's macOS Catalina Patcher v1.0b11 ---> boot to installer with Clover r5018, bypassing machine compatibility checks ---> installed over existing DP3_19A501i apfs installation. The patched installer automatically omits /System/Library/UserEventPlugins/com.apple.telemetry.plugin during the install, so we avoid any kps for Core2Duo CPUs. Applied recommended post-install patches for MBP7,1 SMBIOS including @ASentientBot's latest acceleration patches for unsupported (non metal) legacy graphics cards. These include a new SkyLight framework wrapper. I also copied his CatalinaAutoMountWritable.plist into /Library/LaunchDaemons which auto mounts the root volume as R/W at login (sudo mount -uw /). End Result...
  9. fusion71au

    Clover General discussion

    No, I only installed hfs Catalina on a VMware virtual machine. For my physical machines, 10.15 is installed on apfs formatted HDs. Maybe your issue is SIP? Did you set CsrActiveConfig to 0x3E7, CSR_ALLOW_UNAPPROVED_KEXTS? What is the output of csrutil status in Catalina? Tried booting to Recovery HD and setting csrutil disable? I also use @ASentientBot's launch daemon - copy CatalinaAutoMountWritable.plist into /Library/LaunchDaemons which auto mounts the root volume as R/W at every login (sudo mount -uw /). That looks interesting and promising. If you can find out how the Ubuntu ISO is prepared and burnt to disk in linux, it should in theory be easy to do that for the Clover ISO as well. Somehow it has a FAT partition (like a FAT32 EFI?). Note Clover can also be compiled in Linux Mint/Ubuntu with the Build_Clover.command script. Edit: This post maybe relevant... In addition, see if you can manually add an extra UEFI BIOS entry for the Clover CD/DVD (linking to CLOVERX64.efi) in linux with efibootmgr, or with bcfg in UEFI shell. On macOS, have a look at man for hdiutil makehybrid. Maybe -udf format will allow the Clover CD/DVD to be recognised when BIOS set to UEFI Only? Finally, if you multi boot with UEFI Windows, then maybe you can manually create a UEFI-CloverCD/DVD entry with the EasyUEFI program. Link to my guide for adding a Clover entry in UEFI Windows here and @GhostRaider's how to for MSI H81 boards (should be similar or the same BIOS settings to your system). <--- only works with GUID HDs that have EFI partitions The Clover ISO at least is able to EFI boot into macOS Catalina with VMware EFI firmware (also boot7 in your case which is Clover's EFI DUET firmware)...Note Clover's boot log "Starting Clover Revision ... on VMware. Inc. EFI" The issue is getting the MSI UEFI Bios to recognise the Clover ISO burnt to CD/DVD as a UEFI bootable entry...
  10. fusion71au

    Clover General discussion

    At the moment, the Build_Clover.command script has not been updated to take into account the new /Drivers folder structure that you introduced. Before, AptioMemoryFix was automatically compiled and included in the final installer.pkg presented to the end user. btw, I found another typo in the makeiso.script...for latest r5000, boot? should be boot6 I assume...attached fixed makeiso.fixed typo.zip OK, it copies both boot6 and boot7
  11. fusion71au

    Clover General discussion

    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.
  12. fusion71au

    Clover General discussion

    @arsradu, I noticed the makeiso script formats the iso with -eltorito-boot, to allow for legacy BIOS booting, and it also uses boot6 instead of boot7 (BiosBlockIO) which works on your system. I'm guessing the presence of the legacy BIOS code is what makes the CD-DVD-ROM "invisible" to your firmware when it is set to boot to "UEFI only". Try the following modified makeiso files (place in ~/src/edk2/Clover/CloverPackage) to generate the Clover ISO instead of the default one... makeiso_boot7.zip ---> uses boot 7 instead of boot 6 for legacy boot makeiso_uefi_only.zip ---> removed -eltorito-boot formatting so only UEFI booting possible PS BiosBlockIO is still available in the latest Clover Pkg installer r4995. If the boot7/BosBlockIO installed by r4995 doesn't work, then simply replace it with the boot7 file from Clover r3911 (keep the rest of the files from Clover r4995, including CLOVERX64.efi, BOOTX64.efi and the new drivers folder file structure)... Good Luck! Clover_v2.4k_r4995.pkg.zip
  13. fusion71au

    Clover General discussion

    @arsradu, You still need to follow steps 2-4 in the post above so that the ISO contains the normal config.plist you use to boot your system and all your normal kexts (otherwise by default, only FakeSMC.kext is included in the ISO). Also, if you want to exclude the Clovy theme as the cause of your red screen error, you can use this script that uses the embedded theme instead makeiso_embedded.zip: 1. Copy my makeiso_embedded file above to ~/src/edk2/Clover/CloverPackage 2. Delete ~/src/edk2/Clover/CloverPackage/CloverV2/EFI/CLOVER/config-sample.plist. Copy your desired config.plist (which you know boots your system) to the same folder, giving it the name config-sample.plist 3. Copy all the kexts you normally need to inject with Clover to ~/src/edk2/Clover/CloverPackage/CloverV2/ThirdParty/kexts/Other 4. Copy the embedded theme folder from ~/src/edk2/Clover/CloverPackage/CloverV2/EFI/CLOVER/themes to ~/src/edk2/Clover/CloverPackage/CloverV2/themespkg 5. Run my new makeiso_embedded script in terminal... cd ~/src/edk2/Clover/CloverPackage chmod +x makeiso_embedded ./makeiso_embedded The custom ISO will be created in the ~/src/edk2/Clover/CloverPackage/sym folder. In addition, there might be a specific procedure for your particular brand/model of computer to boot in UEFI mode to CD/DVD-ROM eg google "boot in uefi mode to cd" might give relevant results. Another possibility is that your firmware in UEFI mode cannot read the CD/DVD-ROM because it lacks the necessary built in uefi file system drivers? Maybe try booting to an UEFI shell first, load CD drivers + HFS driver eg VBoxIso9600-64.efi, GrubUDF-64.efi and HFSPlus.efi (google procedure to load efi drivers with UEFI shell), then chain load to Clover on the CD? Good Luck!
  14. fusion71au

    Clover General discussion

    Yes, that would be good, and I understand it makes "logical" sense to keep some drivers in both locations if "Off" refers to "Off-line Repository", where all the efi drivers are kept for safekeeping. However for the moment, the Clover make pkg script will complain and fail if ApfsDriverLoader.efi is placed in both /drivers/UEFI (or /drivers/BIOS) and /drivers/off/UEFI(or BIOS)/FileSystem. Here's one possible arrangement. For the essential/recommended efi drivers needed to boot the system, these are placed in /drivers/BIOS or /drivers/UEFI... For the other drivers, they can be put in the "Off-line Repository"... Color coding: green = extra efi drivers from acidanthera repos. If I had to choose a recommended/preferred AptioFix driver (that works for the most systems), it would be AptioMemoryFix.efi. I realize, however, it doesn't work for everyone... blue = proprietory file system efi drivers red = efi drivers currently in the recommended folders that are not really necessary for booting eg AudioDxe.efi is just for the boot chime and can significantly slow down booting SMCHelper.efi can cause conflict if using VirtualSMC.kext with VirtualSMC.efi, and is it really necessary for booting macOS? @arsradu, Your compiled Clover ISO is missing apfs, HFS and AptioFix drivers, therefore the "Not found" error I assume... You can try this one Clover-v2.4k-4986-X64.iso.zip with ApfsDriverLoader, VBoxHfs and AptioMemoryFix in /Drivers/UEFI included. Note I have not changed the default config.plist provided by the Clover repo ---> may have to tweak settings to boot your system from the Clover GUI. The Clover ISO at least is able to EFI boot into macOS Catalina with VMware EFI firmware ...
  15. fusion71au

    Clover General discussion

    I think it refers to "official" like an "official" repository of optional uefi drivers. IMHO, ApfsDriverLoader.efi should be in both /drivers/BIOS and /drivers/UEFI as a mandatory/recommended driver, instead of located in /drivers/off/FileSystem as an optional driver. Likewise VBoxHfs.efi or HFSPlus.efi be in /drivers/UEFI as a mandatory/recommended driver.
×