Jump to content


  • Content count

  • Joined

  • Last visited

  • Days Won


fusion71au last won the day on August 21

fusion71au had the most liked content!


About fusion71au

  • Rank
    InsanelyMac Legend

Profile Information

  • Gender

Recent Profile Visitors

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

  1. fusion71au

    [pre-release] macOS Mojave

    Agree. Since the build number is not automatically shown, this "beta" is probably the GM. Build number appears when you click your mouse in area next to "Version 10.14" . All my systems also upgraded without incident through App Store or @crazybirdy's script (for XPS M1530 Mojave on HFS+, used installScript_1014 and mojave2core patcher)....
  2. fusion71au

    Clover problems report & features request

    Unfortunately, boot still hangs with problematic FV drivers, even if I use CLOVERX64.efi/BOOTX64.efi from the above post (UEFI booting into my non FV macOS volumes (10.13.6 hfs and 10.14beta10 apfs) on my NUC6i5SYH). 2 problematic r4667 drivers: AppleKeyFeeder-64.efi ---> freeze/unresponsive Clover Main Menu GUI AppleKeyAggregator-64.efi ---> boot hang after launching macOS as shown below... Deleting both drivers from /EFI/CLOVER/drivers64UEFI ---> I can boot again normally with CLOVERX64.efi r4667. I vote for Clover package installer not selecting these problematic FV drivers by default...
  3. fusion71au

    Clover problems report & features request

    I also had boot hang with r4667 UEFI driver AppleKeyAggregator-64.efi on my NUC6i5SYH. Actually was able to reach Clover main menu but hang occurs after selecting the macOS entry. Still boots fine if I use CLOVERX64.efi/BOOTX64.efi r4667 with UEFI drivers from r4664.
  4. fusion71au

    Cannot log in any more

    Try booting into your OSX partition in single user mode and force it to create a new admin user - How to Re-Run the OS X Setup Assistant. Afterwards, try to recover any data from your old account... fsck -fy mount -uw / rm /var/db/.AppleSetupDone reboot It is a hidden file. Note - the name starts with a period .AppleSetupDone
  5. fusion71au

    Mojave and AirPortAtheros40.kext

    @SpiderCab To get Atheros wifi working for your installer, you need to replace its prelinked kernel with one that includes IO80211Family.kext from High Sierra eg attached to this post is prelinked kernel from Developer Beta 10 that has this kext inside. To generate your own prelinked kernel, see post#1 in this thread. Follow instructions for "Custom Prelinkedkernel Generator Tool", running the PLK.tool in Mojave (after adding Mojave BaseSystem.dmg and IO80211Family.kext to "ExtraKexts" folder). @XLNC's post in that same thread is useful if you make an installer with createinstallmedia. Mojave prelinkedkernel with Atheros Wifi.zip
  6. fusion71au

    [pre-release] macOS Mojave

    No, transparency is at default. Iris Graphics 540 for my Skylake NUCi5SYH is natively supported in Mojave . Thanks @crazybirdy for your script. It works to update Mojave on either apfs or HFS+ partition. Updated both my legacy systems from DB9--->DB10 (GA-P55aUD3/apfs desktop, Dell XPSM1530/HFS+ notebook) with this method. Note - App Store update does not appear automatically with Mojave on an HFS+ partition, hence need for script... Yes, you can reuse the installer.pkg to update Mojave on another machine, as long as it is at the same starting point as the original machine eg update from DB9 to DB10. I copied installer.pkg from /tmp/041-03373 to a USB thumb drive, then ran it on the second machine. Don't forget to update dyld cache afterwards.... sudo update_dyld_shared_cache -force
  7. fusion71au

    [pre-release] macOS Mojave

    Works OK here with Clover r4658, App Store upgrade to DB10_18A384a on my Skylake NUC6i5SYH...
  8. fusion71au

    AppleALC — dynamic AppleHDA patching

    You were right . With Lilu 1.2.6 and AppleALC 1.3.1, there were error messages saying "alc-layout-id was not provided by controller at HDEF" in debug log... 2018-09-01 16:22:37.226609+1000 localhost kernel[0]: Security policy loaded: Lilu Kernel Extension 1.2.6 DEBUG build (Lilu) 2018-09-01 16:23:11.249818+1000 localhost kernel[0]: (kernel) AppleALC: alc @ alc-layout-id was not provided by controller at HDEF In this situation, I had to inject both layout-id=7 and alc-layout-id=1 through Clover config.plist/Devices/Properties. With newly compiled kexts from source (Lilu 1.2.7 and AppleALC 1.3.1), remapping layout-id works again, even using my old Clover config.plist - Devices/Audio/Inject=1 and no Devices/Properties injection... Thanks @vit9696 Latest Kexts.zip
  9. fusion71au

    AppleALC — dynamic AppleHDA patching

    I also lost sound when upgrading AppleALC to v1.3.1 from v1.2.8. Confirm that remapping layout-id broken by v1.3.0. What is your codec/layout? Realtek ALC888S-VD, normally works with layout-id=1 (Devices/Audio/Inject=1 set in Clover confg.plist). Layout-id remapped automatically to 7 by AppleALC.kext v1.2.8... When did it break? When upgraded to v1.3.1 from v1.2.8 Is the issue 10.14 only or 10.13.6 too? Fails in both 10.13.6 & 10.14 Does adding alcapplid=X boot-arg, where X is your layout-id, solve the issue? Test on 10.13, because some layouts are missing in 10.14. No, still fails on 10.13, even with alcapplid=7 or alcid=1 and alcapplid=7. IORegistryExplorer confirms layout-id not remapped and no alc-layout-id property created. Fixed by manually injecting device properties in Clover config.plist/Devices/Properties. Procedure 1. Create config-imprint with clover-genconfig utility, after booting 10.13 with old working config.plist (with Devices/Audio/Inject=1) and AppleALC v1.2.8. clover-genconfig > config-imprint.plist 2. Edit config.plist by importing PciRoot Dictionary containing layout-id from config-imprint.plist to Devices/Properties of config.plist (see screenshot). I added alc-layout-id=1 and remapped layout-id to 7. Then deleted Devices/Audio/Inject=1. 3. Upgraded AppleALC to v1.3.1. 4. Reboot system ---> Audio working again in both 10.13.6 and 10.14beta9 .
  10. fusion71au

    [pre-release] macOS Mojave

    Upgrade to beta9 OK on my Skylake NUC6i5SYH and all the legacy systems in signature. Same upgrade procedure as previous betas for my legacy BIOS Dell XPSM1530: Core2Duo mojave2core patcher after making full installer USB with @dosdude1's Mojave patcher.
  11. Yes, both are release versions of High Sierra 10.13.6: http://swcdn.apple.com/content/downloads/29/03/091-94326...---> corresponds to build http://swcdn.apple.com/content/downloads/07/20/091-95774...---> corresponds to build (with latest security update).
  12. fusion71au

    [pre-release] macOS Mojave

    Hi @Matgen84, From the readme for ApfsDriverLoader, it is an Open source apfs.efi loader based on reverse-engineered Apple's ApfsJumpStart driver Loads apfs.efi from ApfsContainer located on block device. Apfs driver verbose logging suppressed. Version system: connects each apfs.efi to the device from which it was retrieved Supports AppleLoadImage protocol provides EfiBinary signature check WARNING: Please load AppleImageLoader.efi right before ApfsDriverLoader, or just put it inside drivers64uefi folder of your Clover bootloader In other words, it is chain loading the apfs.efi driver that is already embedded in the apfs volume, just like Apple's EFI firmware. Advantages include much smaller file size compared to including apfs.efi in the Clover.pkg, no verbose output and no need to update Clover.pkg with each macOS update (the driver always loads the correct version of apfs.efi that is appropriate to the macOS being loaded).
  13. fusion71au

    [pre-release] macOS Mojave

    Successful upgrade of all my systems in signature to DB8_18A371a. Skylake NUC6i5SYH, legacy BIOS GA-P55AUD3 desktop and legacy notebook Dell XPSM1530... The legacy systems were upgraded in place after making a full installer USB, patched with @dosdude's macOS Mojave patcher - XPS with Mojave on HFS+ and P55AUD3 with Mojave on apfs volume. The AMD HD5770 works OK but unfortunately without graphics acceleration, despite adding graphics kexts for HD5000 from High Sierra. On the other hand, QE/CI was still possible with legacy GeForce tesla kexts for the 8600M GT. As before, on first boot (in single user mode) for my Core2Duo laptop, I ran @crazybirdy's mojave2core ---> patch com.apple.telemetry.plugin, then updated system caches/prelinked kernel... fsck -fy mount -uw / /usr/bin/mojave2core touch /System/Library/Extensions && kextcache -u / reboot The Skylake NUC upgraded painlessly by directly running the full installer "Install macOS Mojave Beta.app" . Hi @Fergarth, Your kernel panic log unfortunately doesn't point to a specific culprit . However, I noticed that unlike my Skylake NUC, your system needs IntelGraphicsDVMTFixup.kext. The version in your EFI folder is 1.2.0, but the latest v1.2.2 requires Lilu 1.2.4 or newer (you have v1.2.3) ---> maybe worth upgrading both your Lilu & IntelGraphicsDVMTFixup kexts. Alternatively, you might be able to substitute IntelGraphicsDVMTFixup.kext with Clover patching of AppleIntelSKLGraphicsFramebuffer.kext. On an unrelated note, I would recommend @savvamitrofanov's ApfsDriverLoader-64.efi instead of apfs.efi and ApfsJumpStart.efi in /drivers64UEFI. Good Luck!
  14. fusion71au

    [pre-release] macOS Mojave

    What is the verbose output from setting the following Clover boot options (-v keepsyms=1 debug=0x100, keep symbols + no reboot on panic)? Sometimes old versions of lilu or its plugin kexts can ---> kp during Mojave install, so make sure you have the latest versions (maybe try temporarily blocking them through Clover menu). Also consider using a single phase installer eg @dosdude1's macOS Mojave Patcher, or @crazybirdy MbrEasyInstallerMaker. These are based on the old "BaseSystem.dmg restore" method ---> can easily manipulate/rebuild the installer's prelinked kernel (or replace prelinkedkernel with known working one from High Sierra).
  15. A user named @anmool has managed to get High Sierra running on his Lifebook AH512/FJNBB29/Corei3-2328M/HD3000. His Clover config (attached) was posted on Voldemort's forum and installed in legacy mode - should hopefully work for you also (no guarantees though)... anmool AH512 Clover config.zip Check the SHA1 checksum of your downloaded "Install macOS Sierra.app" at this website. You can actually make a patched installer USB that will allow installation with MBP4,1 SMBIOS with @dosdude 's macOS Sierra Patch Tool. Sometimes happens if target disk or installer has corrupted sectors. Erase and reformat target drive as GUID, macOS extended/journaled in Disk Utility. To be safe, reformat & remake your installer on different USB or separate partition on hard drive (approx 10GB).