2 posts in this topic
Recently Browsing 0 members
No registered users viewing this page.
So I managed to get a Catalina 10.15 vm up and running in ESXi 6.7u2.
When I try to install Catalina updates, however, it goes to the Apple logo, status bar moving ever so slightly, reboots again and this time hangs on the Apple logo. To fix this, I either remove or disable "Mac OS" as an option in the bootloader. Is there a way to get these updates to install?
In the meantime...
I instead of restarting Catalina after choosing to update it, I shutdown the guest. After a restart it SEEMED to update with the time duration countdown.
Prior to this I did run disk utility and checked Untitled and Untitled-Data for errors (I don't think it found any).
So I just logged back onto the VM and the version is still 10.15 and NOT 10.15.2 as hoped. So weird.
Anyone else having issues with the latest security update 2019-001 10.14.6 for Mojave?
Have never had issues updating since 10.14.2 in the past. But this once gets stuck on these last 4 lines:
Adding AGDP mode validate property
iMac.local com.apple.xpc.launchd (org.ntp.sntp.188) <Warning>: Servuce exited with abnormal code: 1
considerRebuildOfPrelinkedKernel com.apple.nke.webcontentfilter trigger reguild
Forcing CS_RUNTIME for entitlement: com.apple.rootless.install iMac.Local com.apple.xpc.launchd (com.apple.displaypolicyd.200) <Warning>: Service exited with abnormal code: 1
The only way to boot is to force shutdown and overide boot from the system volume and bypass the Mac OS Install volume.
Doing a bit of research from similar issues with users and security updates most boot problems are caused/resolved by fixing:
Location of Kexts (virtualsmc in Clover's "/kexts/Other/", latest kexts installed with ##### in L/E/ with cache updated by Kext utility)
The Injection of Kexts (i've tried both detect and inject = yes)
Mismatched Kext (fakesmc + virtual smc both in use, which they are not)
A bad config.plist (works booting the normal system voluem, i've attached)
A graphic injector issue (currently using iMac18,3 + RX580 with the UHD630 in a headless state)
Multiple Drivers Folder - The old clover /driversuefi64/ folder present and conflicting with the latest /drivers/uefi/ folder (only /drivers/uefi/ present)
The only thing that is different from this update than previous updates is that I transitioned to VirtualSMC from previously using FAKESMC/ FAKESMCsensors kexts with previous Mojave releases.
I uninstalled the FAKESMC and all the sensors kexts using terminal and the following command and can confirm they are not present in the Clover "other folder" or the /L/E/ folder.
sudo rm -rf /Library/Extensions/".....".kext
After transitiong to VirtualSMC I did read with the readme that the VirtualSmc.efi should be placed in the /drivers/UEFI/ folder in clover. So I have added that to the EFI/CLOVER/DRIVERS/UEFI/ folder manually. Can anyone confirm if this is necessary?
I've attached my config.plist file and screenshots of the verbose readout stalling as well.
Any guidance would be great!
KEXTS I'VE INSTALLED IN /L/E/:
I-5 Skylake/520 graphics/4gig RAM/UEFI boot/GPT
Any one had issues with supplemental updates and/or security updates booting very slowly after install and using approx. 750 more megs of memory? This has happened with recent updates to Catalina 10.15.1, Mojave security update 2019-001, and High Sierra security update 2019-006. I know that the first reboot after updates is usually slow but this problem with slow booting and hard drive thrashing persists after multiple reboots. It seems as though hard drive access is being channeled though a buffer. In one instance Catalina paused for a long time on reboot and a message appeared indicating that enough information had been found to re-enable the soft bloc. afterward Catalina booted normally but Mojave was booting so slow that it was practically unusable. After multiple reboots High sierra takes around a minute for the desktop to fully initialize after the login, but it was usable.
Does mac os use some kind of software input-output hard disk buffer that can be manually reset from the terminal? Disabling/enabling virtual memory paging seems to have no effect and the vm compressor mode is set to 2. The laptop only has 4 gig of memory but this has been enough to run all three os without boot issues in the past. Catalina on APFS, Mojave and High Sierra on HFS+.
Any help appreciated.
Use this thread to link / talk about of the future Nvidia Web Driver updates for macOS Sierra.
Nvidia Web Driver - 378.05.05.25f19 --> build 16G2136 (thanks to BreBo) New!
Nvidia Web Driver - 378.05.05.25f18 --> build 16G2028 (thanks to Riley Freeman)
Nvidia Web Driver - 378.05.05.25f16 --> build 16G2016 (thanks to Cyberdevs)
Nvidia Web Driver - 378.05.05.25f15 --> build 16G1918 (thanks to BreBo)
Nvidia Web Driver - 378.05.05.25f14 --> build 16G1917 (thanks to BreBo)
Nvidia Web Driver - 378.05.05.25f13 --> build 16G1815 (thanks to flowrider)
Nvidia Web Driver - 378.05.05.25f12 --> build 16G1710 (thanks to BreBo)
Nvidia Web Driver - 378.05.05.25f11 --> build 16G1618 (thanks to Frank Nitty)
Nvidia Web Driver - 378.05.05.25f10 --> build 16G1510 (thanks to BreBo)
Nvidia Web Driver - 378.05.05.25f09 --> build 16G1408 (thanks to BreBo)
Nvidia Web Driver - 378.05.05.25f08 --> build 16G1314 (thanks to BreBo)
Nvidia Web Driver - 378.05.05.25f07 --> build 16G1314 (thanks to haring)
Nvidia Web Driver - 378.05.05.25f06 --> build 16G1212 (thanks to WeBeRiO)
Nvidia Web Driver - 378.05.05.25f04 --> build 16G1114 (thanks to lukazm)
Nvidia Web Driver - 378.05.05.25f03 --> build 16G1036 (thanks to Gradou)
Nvidia Web Driver - 378.05.05.25f01 --> build 16G29 (thanks to Badruzeus)
Nvidia Web Driver - 378.05.05.15f01 --> build 16F73 (see this post)
Nvidia Web Driver - 378.05.05.05f02 --> build 16E195(thanks to crachmaster4999)
Nvidia Web Driver - 378.05.05.05f01 --> build 16E195 (thanks to Moviemakergr) Pascal support!!!
Nvidia Web Driver - 322.214.171.124f01 --> build 16E195 (thanks to Lanc)
Nvidia Web Driver - 3126.96.36.199f01 --> build 16D32 (thanks to shatterhenner)
Nvidia Web Driver - 3188.8.131.52f02 --> build 16C68 (see this post)
Nvidia Web Driver - 3184.108.40.206f01 --> build 16C67 (see this post)
Nvidia Web Driver - 3220.127.116.11b06 --> build 16C60b/16C63a (see this post)
Nvidia Web Driver - 318.104.22.168f03 --> build 16B2657/16B2659 (thanks to Moviemakergr).
Nvidia Web Driver - 322.214.171.124f01 --> build 16B2555 (thanks to Moviemakergr)
Nvidia Web Driver - 367.15.10.05f01 --> build 16A323 (thanks to phi777)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A323 (same driver since DP4/PB3)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A322 (see this post)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A320 (see this post)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A313a (DP8 & PB7) (see this post)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A304a (DP7 & PB6) (see this post)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A294a (DP6 & PB5) (see this post)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A286a (DP5 & PB4) (see this post)
Nvidia Web Driver - 367.10.10.05b01 --> build 16A270f (DP4 & PB3) (thanks to TheRacerMaster)
Nvidia Web Driver - 367.05.10.05b07 --> build 16A254g (DP3 & PB2) (see this post)
Nvidia Web Driver - 367.05.10.05b07 --> build 16A238m (PB1) (thanks to Faun)
Nvidia Web Driver - 367.05.10.05b07 --> build 16A239j (DP2) (thanks to Faun)
Nvidia Web Driver - 367.05.10.05b03 --> build 16A201w (DP1) (thanks to Xmedik)
you can use this thread to link / talk about of the future Nvidia Web Driver updates for El Capitan
Nvidia Web Driver - 346.03.15f16 --> build 15G22010 (thanks to BreBo) New!
Nvidia Web Driver - 346.03.15f15 --> build 15G21013 (thanks to BreBo)
Nvidia Web Driver - 346.03.15f14 --> build 15G20015 (thanks to DMCrimson)
Nvidia Web Driver - 346.03.15f13 --> build 15G20015 (thanks to Louvier)
Nvidia Web Driver - 346.03.15f12 --> build 15G19009 (thanks to WeBeRiO)
Nvidia Web Driver - 346.03.15f11 --> build 15G18013 (thanks to BreBo)
Nvidia Web Driver - 346.03.15f10 --> build 15G17023 (thanks to Badruzeus)
Nvidia Web Driver - 346.03.15f09 --> build 15G1611 (thanks to Badruzeus)
Nvidia Web Driver - 346.03.15f08 --> build 15G1510 (thanks to Badruzeus)
Nvidia Web Driver - 346.03.15f07 --> build 15G1421 (thanks to bb1045)
Nvidia Web Driver - 346.03.15f06 --> build 15G1217 (thanks to bb1045)
Nvidia Web Driver - 346.03.15f05 --> build 15G1212 (thanks to WeBeRiO)
Nvidia Web Driver - 346.03.15f04 --> build 15G1108 (see this post)
Nvidia Web Driver - 346.03.15f03 --> build 15G1004 (thanks to BreBo)
Nvidia Web Driver - 346.03.15f02 --> build 15G31 (thanks to Moviemakergr)
Nvidia Web Driver - 346.03.15f01 --> build 15G31 (thanks to WeBeRiO)
[uPDATE_3]Nvidia Web Driver - 346.03.15b01 --> build 15G24b (thanks to DMCrimson)
Nvidia Web Driver - 346.03.10f02 --> build 15F34 (thanks to marcozardi)
Nvidia Web Driver - 346.03.10f01 --> build 15F34 (thanks to WeBeRiO)
[uPDATE_2] Nvidia Web Driver - 346.03.10b01 --> build 15F31a (see this post)
Nvidia Web Driver - 346.03.06f01 --> build 15E65 (see this post)
Nvidia Web Driver - 346.03.06b01 --> build 15E (see this post)
Nvidia Web Driver - 346.03.05f02 --> second release for build 15D21 (thanks to Fljagd)
Nvidia Web Driver - 346.03.05f01 --> build 15D21 (see this post)
Nvidia Web Driver - 346.03.05b02 --> build 15D (see this post)
Nvidia Web Driver - 346.03.04f02 --> second public release (see this post)
Nvidia Web Driver - 346.03.04f01 --> build 15C50 (see this post)
Nvidia Web Driver - 346.03.04b02 --> build 15C48a (see this post)
Nvidia Web Driver - 346.03.04b01 --> build 15C47a (see this post)
Nvidia Web Driver - 346.03.03f02 --> second public release (see this post)
Nvidia Web Driver - 346.03.03f01 --> build 15B42 (thanks to jperkins909)
Nvidia Web Driver - 346.03.02f02 --> build 15A284 (thanks to MTWomg)
Nvidia Web Driver - 346.03.02f01 --> build 15A284 (see this post)
Nvidia Web Driver - 346.03.01b07 --> GM/DB/PB6/DB7/PB5 (thanks to BreBo)
Nvidia Web Driver - 346.03.01b06 --> build 15A (thanks to MTWomg)