Jump to content

fusion71au

Gurus
  • Content count

    950
  • Joined

  • Last visited

  • Days Won

    13

fusion71au last won the day on August 21

fusion71au had the most liked content!

3 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

    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
  2. 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.
  3. 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.
  4. 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>
  5. fusion71au

    Mojave and AirPortAtheros40.kext

    Click title bar of the Mojave installer window on top RHS to enable wifi and enter wifi password...
  6. 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.
  7. 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
  8. 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
  9. Just a heads up that @vit9696 has removed EfiMiscPkg (and added OcSupportPkg) in his latest commits to AppleSupportPkg. I had to edit the URLs in Build_Clover.command/ebuild.sh to get them to build external packages (ApfsDriverLoader-64.efi, AppleImageLoader-64.efi, VirtualSMC-64.efi etc) for Clover r4697 again... ThirdPartyList=( https://github.com/vit9696/AptioFixPkg.git https://github.com/acidanthera/OcSupportPkg https://github.com/acidanthera/EfiPkg https://github.com/acidanthera/AppleSupportPkg.git ) Build_Clover.command.zip ebuild.sh.zip Yes. As always, backup/make copy of original files.
  10. fusion71au

    Clover problems report & features request

    Try deleting problematic FV2 drivers (AppleKeyFeeder-64.efi, AppleKeyAggregator-64.efi) as mentioned in this post. Unfortunately, these new drivers are selected by default by the standard Clover package installer...
  11. Download, then open the corresponding English.dist file in a text editor. Eg BaseSystem.dmg and InstallESDDmg.pkg for Mojave Beta11_18A389 have the following URLs... http://swcdn.apple.com/content/downloads/42/45/091-62771/dsx32mbizk8mo8nx84umbwp5iknyxpgyxc/BaseSystem.dmg http://swcdn.apple.com/content/downloads/42/45/091-62771/dsx32mbizk8mo8nx84umbwp5iknyxpgyxc/InstallESDDmg.pkg Corresponding English.dist file URL is https://swdist.apple.com/content/downloads/42/45/091-62771/dsx32mbizk8mo8nx84umbwp5iknyxpgyxc/091-62771.English.dist Opening this file in text editor shows this ...
  12. 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)....
  13. 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...
  14. 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.
  15. 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
×