Jump to content

fusion71au

Gurus
  • Content Count

    957
  • Joined

  • Last visited

  • Days Won

    13

fusion71au last won the day on August 21 2018

fusion71au had the most liked content!

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

    macOS Mojave on Legacy PC ? Yes we can

    I successfully updated from 10.14.1 to 10.14.2 on my Mojave HFS partition by creating a full installer USB ---> in place upgrade installation. This avoided the missing frameworks/app opening problems associated with the updater script discussed above... * Can use either @dosdude1's macOS Mojave patcher tool or @crazybirdy's MBR-EasyInstallerMaker script to make USB installer from full 10.14.2 app * Boot system to USB installer and target the 10.14.1 partition to perform upgrade install * After upgrade completes, boot system to Mojave in single user mode to patch/replace com.apple.telemetry.plugin (eg with mojave2core script). Can also replace legacy kexts from High Sierra if overwritten by update eg in single user mode, type the following commands followed by <Enter> after each line ... fsck -fy mount -uw / /usr/bin/mojave2core cp -R /Volumes/USB/Kexts/* /System/Library/Extensions //Assuming you put legacy NVidia/other needed kexts in "Kexts" folder on your USB touch /System/Library/Extensions && kextcache -u / reboot
  2. fusion71au

    Clover General discussion

    Attached Clover r4784 compiled with XCODE 8.2.1 in 10.11.6: Clover_v2.4k_r4784.zip Alternatively, you can use GCC instead of XCODE to build Clover eg if you use the Build_Clover.command script, edit the BuildCloverConfig.txt file like below... GNU=GCC53 Build_Tool=GNU Unfortunately, this expertise is beyond my pay grade...calling @Zenith432 for help? Disabled optimization during compilation with -O0 flag in tools_def.txt still results in bad boot6,7 using XCODE 10.1. Looks like new rules for XCODE10 will be required...
  3. fusion71au

    Clover General discussion

    I believe compilation with XCODE 10.1 is the problem. From your debug log, you are compiling Clover with XCODE 10.1 (with toolchain set to XCODE8) on your system... Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/pkovacs/src/edk2/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 9 | OS: 10.13.6 | XCODE: 10.1] I already mentioned in this post that other XCODE versions eg 8.2.1, 8.3.3, 9.2, or GCC5.3, generate working boot6 and boot7 for my legacy desktop (system 2 in signature) but not XCODE 10.1 ---> boot hanging on stuck underscore "_" symbol. Also interesting to note that the officially released Clover r4741 was compiled with XCODE 8.3.3 but r4769 (which also fails for your system) with XCODE 10.1. No, still bad boot6,7 if Clover r4760 compiled with XCODE 10.1 (toolchain set to XCODE8, edk2 r27956). I think the problem/bug is intrinsic to XCODE 10.1.
  4. Yes, you are correct. Apple removed the URLs for 10.14_18A391 from the software catalog and replaced them with URLs for 10.14.1_18B75. I just hadn't gotten around to updating the links for 10.14.1 in the first post . Yes, you need the partition number of the hfs BaseSystem image for the next step... sudo dmg2img -v -i BaseSystem.dmg -p 4 -o /dev/sdb3
  5. fusion71au

    Clover General discussion

    @Slice, Notice that commit r4761 includes a change to Variable.c in /Patches_for_UDK2018/MdeModulePkg/Universal/Variable/RuntimeDxe/ ... Also noticed that official Clover r4769 was compiled with XCODE 10.1 (with tool chain set to XCODE8) but r4741 was compiled with XCODE 8.3.3 ---> successful boot... 6:891 0:000 Starting Clover revision: 4741 on CLOVER EFI 6:891 0:000 Build with: [Args: -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D NO_GRUB_DRIVERS_EMBEDDED -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 10.12.6 | XCODE: 8.3.3] Edit Further to XCODE 10.1 being the problem, my legacy desktop boots fine with Clover r4772 compiled with XCODE 8.2.1 or XCODE 9.2 (both with tool chain set to XCODE8).... 6:897 0:000 Starting Clover revision: 4772 on CLOVER EFI 6:897 0:000 Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/fusion71au/src/edk2/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 3 | OS: 10.11.6 | XCODE: 8.2.1] 6:911 0:000 Starting Clover revision: 4772 on CLOVER EFI 6:911 0:000 Build with: [Args: -mc --no-usb -D NO_GRUB_DRIVERS_EMBEDDED -D USE_APPLE_HFSPLUS_DRIVER -t XCODE8 | -D DISABLE_USB_SUPPORT -D NO_GRUB_DRIVERS_EMBEDDED --conf=/Users/fusion71au/src/edk2/Conf -D USE_BIOS_BLOCKIO -D USE_LOW_EBDA -a X64 -b RELEASE -t XCODE8 -n 5 | OS: 10.13.6 | XCODE: 9.2] If I swap out the boot6 "boot" file with one compiled with XCODE 10.1, the boot hangs ---> after seeing "6" on the screen, it stops at an underscore symbol "_" and no GUI appears.
  6. fusion71au

    Clover General discussion

    Try replacing just the "boot" file with the one attached, compiled with GCC53. I have also attached Clover_v2.4k_r4772 package installer compiled with GCC53... I noticed that for the latest officially released Clover r4769 from Sourceforge, the boot process would hang on my legacy desktop after seeing "6" on the screen. It seems that CloverEFI (the boot6/boot7 "boot" file) compiled with XCODE 10.1 fails to chainload CLOVERX64.efi but CloverEFI compiled with GCC53 works OK. Bug possibly due to latest edk2 28338 sync with commit r4761? Clover_v2.4k_r4772.pkg.zip boot.zip
  7. Yes, after installing High Sierra graphics kexts and patched GeForceTesla.kext as described before in this post... Process of install and post install patching can be automated with @dosdude's macOS Mojave Patcher.
  8. fusion71au

    Vector Themes

    My legacy desktop (system 2 in signature with ATI HD5770) reboots immediately after scanning volumes but before reaching Main GUI when using Clovy theme or switching to Clovy theme after commit r4750. Debug boot log attached. System boots fine when using other themes eg BGM. My other systems have no issues booting with Clovy theme, but I noticed a stray semi colon ";" just below the text "Boot macOS from macOS" in the screenshot of the initial GUI screen below... debug_r4750.log
  9. The prelinkedkernel used by the installer is not the read only file inside BaseSystem.dmg. It is in a hidden folder (unhide with ShowAllFiles.app), full path is /Volumes/Install\ macOS\ Mojave/System/Library/PrelinkedKernels/prelinkedkernel... The terminal app for the installer can be opened by clicking on the Utilities Menu at the top. However, easier for noob to continue installation on the hard drive (click "My computer does not connect to the internet") ---> set up the new user, then install AirPortAtheros40.kext through terminal or kext utility ---> reboot and wifi can now be set up.
  10. For questions 1-3, these are unfortunately unresolved issues/bugs with VirtualBox itself. Native audio in Mojave doesn't work at present (never tried with VoodooHDA inside VM), VirtualBox BIOS does not remember previously "saved" settings and NVRAM is also non functional (these maybe related). Ofc, AptioMemoryFix driver would be useless since the BIOS is not Aptio ... If you want a "smoother" experience with native sound and working NVRAM, better to try running Mojave in VMware patched with @Donk's unlocker program. Installing VMware tools also improves graphics performance and allows dynamic resizing of the VM window (unlike VirtualBox which doesn't provide macOS guest tools at all). Sorry, don't know about Ozmosis inside VM.
  11. No need to copy both IO80211Family.kext and AirPortAtheros40.kext, just IO80211Family.kext IO80211Family.kext from High Sierra already contains AirPortAtheros40.kext inside its /IO80211Family.kext/Contents/PlugIns folder. Yes. On first boot to the newly installed Mojave on your hard dive, AirPortAtheros40.kext will be absent in /System/Library/Extensions. Copy the kext into /S/L/E and rebuild kext caches/prelinkedkernel eg In terminal... sudo cp -R AirPortAtheros40.kext /System/Library/Extensions sudo chown -R 0:0 /System/Library/Extensions/AirPortAtheros40.kext && sudo chmod -R 755 /System/Library/Extensions/AirPortAtheros40.kext sudo touch /System/Library/Extensions && sudo kextcache -u / then reboot your system. Your Atheros wifi should now work. Confirm the kext has loaded by typing kextstat | grep Atheros. I get the result Mac-Pro:~ fusion71au$ kextstat | grep Atheros 67 0 0xffffff7f81df4000 0x148000 0x148000 com.apple.driver.AirPort.Atheros40 (700.74.5) 9753F22E-5C85-3E95-B543-0870CF03838A <66 15 12 7 5 4 3 1>
  12. fusion71au

    Mojave and AirPortAtheros40.kext

    Click title bar of the Mojave installer window on top RHS to enable wifi and enter wifi password...
  13. Unfortunately to generate a working prelinked kernel for Mojave, the PLK tool needs to be run in Mojave (with Mojave's kextcache binary), otherwise you see the errors about the missing dependencies. Try the prelinked Mojave kernel that I have already posted here Mojave and AirPortAtheros40.kext.
  14. Troubleshooting 1) Check SHA1 hashes of your downloaded files with eg HashMyFiles utility. Compare with verified hashes from this website and the screenshot below for files from 10.13.6_ 17G65 ... 2) Maybe due to incorrectly edited InstallInfo.plist in \SharedSupport folder. Replace with InstallInfo.plist.zip from 10.13.6 attached to this post. InstallInfo.plist.zip Update for How to install High Sierra or Mojave on a VirtualBox Guest from scratch (without access to Mac or App Store Installer.app) I've simplified steps 1-8 with BaseSystem_vmdk_generator and added apfs support with Clover r4699 in macOS_apfs.vmdk. 1) Download & extract the contents of BaseSystem_vmdk_generator.zip to your USB. For my system, the drive letter was D: 2) Convert \SharedSupport\BaseSystem.dmg to vmdk by double clicking BaseSystem_vmdk_generator.bat. The file BaseSystem.vmdk is automatically created in the root directory \ of the USB. Deleting any existing image files and vmdk files... Could Not Find D:\*.vmdk Could Not Find D:\qemu-img-win-x64-2_3_0\*.img Converting BaseSystem.dmg to BaseSystem.img with dmg2img... dmg2img v1.6.7 (c) vu1tur (to@vu1tur.eu.org) \SharedSupport\BaseSystem.dmg --> \qemu-img-win-x64-2_3_0\BaseSystem.img decompressing: opening partition 0 ... 100.00% ok opening partition 1 ... 100.00% ok opening partition 2 ... 100.00% ok opening partition 3 ... 100.00% ok opening partition 4 ... 100.00% ok opening partition 5 ... 100.00% ok opening partition 6 ... 100.00% ok opening partition 7 ... 100.00% ok Archive successfully decompressed as \qemu-img-win-x64-2_3_0\BaseSystem.img Converting BaseSystem.img to BaseSystem.vmdk... BaseSystem.vmdk created in root directory of USB drive! Press any key to continue . . . 3) Copy BaseSystem.vmdk from your USB into the VirtualBox macOS guest folder 4) Attach BaseSystem.vmdk and macOS_apfs.vmdk to your macOS guest as extra hard drives 5) Boot your VM to the macOS Utilities screen. Attach the usb (named "USB" and containing the \SharedSupport folder) to the VM and open Disk Utility, show all devices ---> will see blank 50GB drive for installation, 2GB "OS X Base System" and the USB volume "USB" 6) Erase blank drive, format it to apfs named "macOS"  7) Close DU and start Terminal... -bash-3.2# cd /Volumes/USB -bash-3.2# ./startosinstall.command The startosinstall.command script builds the full "Install macOS ******.app" and chain loads the startosinstall utility on the "macOS" target volume. It combines both the "small" installer app (approx 15MB in size on "OS X Base System") and the SharedSupport folder from the NTFS volume (mounted on /Volumes/USB). Note the full installer app is >5GB in size 8) After a few minutes, Apple's Software License agreement will appear ---> type "A" to agree to the License Agreement etc InstallInfo.plist.zip BaseSystem_vmdk_generator.zip macOS_apfs.vmdk.zip
  15. fusion71au

    VirtualSMC — SMC Emulator

    Try copying the attached nasm, mtoc and mtoc.NEW files into /usr/local/bin. I compiled VirtualSMC 1.0.1 release version with XCODE 9.2 in 10.13.6... bin.zip Virtual SMC v1.0.1 package.zip
×