Jump to content
br0adband

Catatalina Beta 10.15 - Anyone got it booting yet?

52 posts in this topic

Recommended Posts

So...

 

Here we go again with a new version of macOS and so far I haven't been able to get it booted in VMware Workstation, just curious if anyone else has either. Same old instructions to create a working bootable ISO function (same as Mojave but change the name of the installer app obviously). It won't boot past the Apple logo, can't boot into safe mode, or recovery either. Made several attempts so far to upgrade a clean Mojave VM using the Catalina installer app, still no joy on the reboot, it just hangs on the Apple logo with zero activity (no hard drive, network, nothing at all).

 

Of course Apple has made some changes, so now begins the troubleshooting and scoping out what's changed and how to work around it and get this thing up and running for some mucking around.

 

I suppose this would be a good thread to discuss all this in so, we'll see what happens. ;)

Share this post


Link to post
Share on other sites
Advertisement

Hm, here is working method to install Catalina in unlocked VMware Workstation:

First, you need working virtual machine with previous version of macOS. I used 10.13.6. Install macOSDeveloperBetaAccessUtility.dmg. Then download Catalina installer from AppStore, then run it. After preparing computer will be rebooted. And can't booted, you will see only apple logo, no disk activity, no processor activity. It's kernel panic. Just shutdown virtual machine, change type to Windows 10 x64 and start it again. Installation will continue. After next reboot virtual machine can not boot. Ok, shutdown it, change it type to macOS 10.14 back and start machine again. Installation will continue. That's all.

Share this post


Link to post
Share on other sites

I stuck on the Apple boot logo. When I switch the type to Windows X64 I only see error messages

Share this post


Link to post
Share on other sites

So I gave several attempts to this process as explained above by serezha and had no luck, even when I alter the machine type to Windows 10 x64 there's no activity once that kernel panic happens, no way apparently to get past it. I suppose we'll figure it out at some point, ain't in that much of a major hurry to get it working.

Share this post


Link to post
Share on other sites

VMware will likely need to fix something or it's an issue with the beta. I wouldn't expect proper support until Catalina is released which is usually when VMware release a new version of Fusion/Workstation. September timeframe.

Share this post


Link to post
Share on other sites

I managed to get Catalina 10.15 DP2/Public Beta1 working in VMware Workstation 12 on a Windows 7 host ...

 

macOS_catalina_apfs_orig.thumb.png.828926b673da034d91171388cfdfb90e.png

 

 

Link to procedure with ISO installer here (can clean install or upgrade over the top of your existing VM).  No need to use an unknown third party vmdk image from the internet - use the vanilla Apple Installer app to create the Installer ISO.

 

 

@Naki & all others stuck after first reboot upgrading to Catalina 10.15 Final Release_19A583 from an earlier version of macOS: Try the procedure below...

 

1.  If you have another OSX virtual machine eg High Sierra or Mojave, temporarily attach the vmdk undergoing the upgrade process to it as a secondary drive (so now have 2 disks attached to this VM - High Sierra or Mojave.vmdk, and the stalled Catalina.vmdk disk.  Don't detach the original High Sierra/Mojave drive)

 

2.  Boot to this "rescue" VM (boot into High Sierra or Mojave) and download

For DP5 copyprelinkedkernel_19A526h.zip

For DP6 copyprelinkedkernel_19A536g.zip

For DP7 copyprelinkedkernel_19A546d.zip

For DP8 copyprelinkedkernel_19A558d.zip

For DP9 copyprelinkedkernel_19A573a.zip

For Final Release copyprelinkedkernel_19A602.zip

 

3.  Next, run the "ShowAllFiles.app" to show the hidden "Locked Files" folder.  Note it is located inside the /macOS Install Data folder (on the "--Data" volume if upgrading from an earlier Catalina build eg DP1 to DP2)

4.  Next, we need to take ownership of the "Locked Files" folder.  Right click the "Locked Files" folder, click "Get Info", click the arrow next to Sharing & Permissions, click the lock icon and provide your admin password, click the plus button to add yourself to the list of owners and then select "Read & Write" to have custom read/write access privilege

5.  Run the copyprelinkedkernel script from terminal (the contents of the above zip file should first be extracted into your ~/Downloads folder) and confirm the Catalina volume as the target when it prompts you...

cd ~/Downloads/copyprelinkedkernel
./copyprelinkedkernel

If the script fails to find the target volume with the "macOS Install Data" folder, terminate it by pressing the <Ctrl> and <C> keys on your keyboard simultaneously.  Manually copy the provided prelinkedkernel to /macOS Install Data/Locked Files/Boot Files folder with Finder as described in the following post...

6.  Shutdown the "rescue" VM.  Restart the original VM undergoing the upgrade process and it should now complete :).

 

Explanation

Spoiler

VMware 15 presently cannot boot the native prelinkedkernel found in macOS Catalina's BaseSystem/installation media without panicking.  Temporarily changing the guest OS type from macOS to Windows 10 X64 can bypass this panic and enable the second installation phase to complete.  Paradoxically, once the prelinkedkernel is rebuilt on a completed installation (at the end of the install process), the VM is able to boot with guest setting back to macOS!  My script replaces the Target Partition/macOS Install Data/Locked Files/Boot Files/prelinkedkernel with the plk from a completed install.

 

Update

VMware Workstation 15.5.0 build-14665864 now has built in Catalina Support, patched with modified unlocker from this post.  Awaiting @Donk for official update to v3.0.2.

Edited by fusion71au
VMware Workstation 15.5.0 build-14665864 now officially supports macOS Catalina

Share this post


Link to post
Share on other sites

Just updated another virtual machine to Catalina without any problems. I am use unlocked Vmware workstation 15.1 on windows 7 x64 host. I started update with 10.13.6, virtual hardware version 15, guest OS type is macOS 10.13. First I removed vmware tools. It is only precausion, but vmware tools may contain incompatible kexts. I installed beta profile, then downloaded Catalina installer from AppStore. The I started installation. After first reboot was kernel panic (apple logo without any disk and processor activity). I shutdowned virtual machine, change it type to Windows 10 x64 and started it again. Installation was continued automatically. After next reboot virtual machine can not boot, I saw boot manager from EFI. I shutdowned it, changed type to macOS 10.14 and started it again. Installation was continued and finished without any problems.

You do not need boot partition or clover. You need vmware 15 (or may be 14) to boot up from APFS partition.

If you have any problems with first reboot: use compatible host hardware (intel's ivy bridge and higher), use vmware workstation 15, use virtual hardware version 15, try to upgrade from high sierra (I do not tried to upgrade from Mojave, may not works), try to uninstall vmware tools before upgrade.

Share this post


Link to post
Share on other sites
17 hours ago, fusion71au said:

I can’t install ver 15 on my desktop GA-P55aUD3/i5-750

Is Catalina work good with first generation of Core i processors? Is Ivy Bridge only marketing restriction or support of old processors will be dropped in next betas?


Did you try monitor.allowLegacyCPU = "true" option for VMware 14/15? Vmware workstation 14/15 only need EPT, all core i processors have EPT support. Unrestricted guest is optional requirement.

Share this post


Link to post
Share on other sites

I finally had the time to try macOS Catalina Beta these last few days. :) (Could not do it before due to other more important tasks & also going on sea vacation for 1 week. One task was get the iOS 13 Simulator working, via Xcode Beta)

I am using Windows 10 64-bit Pro, version 1903 as Host OS. CPU on that PC is Intel Core i5 Sandy Bridge with 4 cores/4 threads (no HT) and 32 GB DDR3 RAM. - Intel GPU (CPU-built it)+AMD Radeon RX 480 2nd GPU. 

Using VMware Workstation 15.0.3 - cannot update to 15.1.0 at this point, as it is hard to do on this PC due to bugs in the VMware installer/updater so please do not suggest that. (I am using latest 15.1.0 on my laptop however.)

 

I downloaded a VMware image/disk file somewhere on the Internet, was about 6+ GBs compressed - and then followed this Guide (same one Filougarou mentions):

https://techsviewer.com/how-to-install-macos-10-15-catalina-on-vmware-on-windows-pc/

(including switching to Windows 10 OS setting for part of the process, then switching back to 10.14 Mojave again - and using slightly different steps due to using VMware Workstation and not Fusion)

but right now I am having issues with update from the older Catalina to latest Catalina Beta. 

 

At first, all is fine - macOS Catalina Beta runs and shows as .470-something version but then if I try to update to latest .48x-something, it shows the Apple logo and gets stuck.

Restarting or power off/on does not help any. Then I remembered I installed VMware Tools, and that I should not install VMware Tools until fully updated, so I went back to my snapshot I took, and uninstalled VMware Tools (then restarted).

But this made no difference - even without VMware Tools there was still just an Apple logo, no progress bar, system (VM) totally stuck/frozen. :(

Changing to Windows 10 OS at this point just produces errors and no booting (not even the Apple logo).

 

Any ideas how to fix/work around this, please? (Again, please do not suggest update to VMware Workstation 15.1.0, as I cannot do it for now. And I think it is not necessary, and all my other VMs work fine.)

 

NOTE: VMware Tools did not seem to work too well. I could copy/paste text from Host to Guest OS, but screen size was stuck at only 1024x768.

I assume if/when I can get latest Catalina Beta working, this will be better or if not, I can likely use that extension which allows to change resolutions manually.

This was similar last summer with the Mojave Betas - at some point, screen size worked badly then in a next version it became much better.

 

NOTE #2: All my other older VMs work fine, ranging from macOS 10.8, 10.9 up to latest Mojave - I have them all. :) (and I even have 10.7, but rarely turn that on)
Plus a few Windows OS VMs too, plus 1 Linux Ubuntu.

 

--------------------------

EDIT: I will also be trying the procedure fusion71au has given above later on today.

 

EDIT #2: Major hurdle as very FIRST step, you said:

1.  On your Mac or Hack, download/copy "Install macOS xxx.app" into your Applications folder.

 

---> Sorry, no idea what this file is, or where to get it. Care to elaborate, please?

EDIT: I am seeing an Install macOS Mojave.app with size around 6 GB on one of my VMs! So, you likely mean a similar file but for Catalina Beta. How/where to get this, please? 

Also, what exact size would it be? 

Edited by Naki
grammar/clarity, extra info

Share this post


Link to post
Share on other sites
On 6/6/2019 at 1:45 AM, serezha said:

Hm, here is working method to install Catalina in unlocked VMware Workstation:

First, you need working virtual machine with previous version of macOS. I used 10.13.6. Install macOSDeveloperBetaAccessUtility.dmg. Then download Catalina installer from AppStore, then run it. After preparing computer will be rebooted. And can't booted, you will see only apple logo, no disk activity, no processor activity. It's kernel panic. Just shutdown virtual machine, change type to Windows 10 x64 and start it again. Installation will continue. After next reboot virtual machine can not boot. Ok, shutdown it, change it type to macOS 10.14 back and start machine again. Installation will continue. That's all.

 

Seemed like an OK, good method, but for me did not work.
Tried same VM as you - one of macOS 10.13.6. Got stuck on Apple logo, just as you say and as my own try with older Beta I found.

Turn off VM, switch to Windows 10 64-bit. Looked OK, then around 50% in the process, Minutes XX remaining text (was around 47-45 minutes at some point) went away and was replaced with "Estimating time remaining.." (notice lack of any concrete number) and has been sitting there for 10 mins now.. :(
Did you uninstall VMware Tools from the old VM before trying the upgrade, or kept it, please?
What CPU do you use?

Edited by Naki

Share this post


Link to post
Share on other sites

fusion71au --- Sorry but I have a hard time understanding your edited steps.

YOU said:

1.  If you have another OSX virtual machine eg High Sierra or Mojave, temporarily attach the vmdk undergoing the upgrade process to it

2.  Boot to this "rescue" VM and download copyprelinkedkernel.zip

3.  Run the copyprelinkedkernel script from terminal (the contents of the above zip file should first be extracted into your ~/Downloads folder)

cd ~/Downloads/copyprelinkedkernel
./copyprelinkedkernel

4.  Shutdown the "rescue" VM.  Restart the original VM undergoing the upgrade process and it should now complete :).

----

but this seems to be missing a step or 2??

 

Is it something like this:
 

1) Power off (shutdown) the working VM with older macOS version. Then detach (disconnect) its original, main disk drive.

2) Now as 2nd step, attach the .vmdk file that is undergoing the upgrade process.

3) Boot the VM up, download the ZIP file you gave.
4) Run the script mentioned from Terminal.

5) Now as last, 5th step shutdown and detach disk, attach to the other, Catalina Beta VM and finish the process.

 

No? :unsure:
If not, please clarify - do we not need to detach the other VM main disk, or what?

Edited by Naki

Share this post


Link to post
Share on other sites
On 7/2/2019 at 10:41 PM, Naki said:

Hello? This is getting semi-urgent for me now, and I do not want to screw this up... Help?? :(

fusion71au -- sorry but all I get is total failure and time lost. Does not work!

I tried TWO ways:
One of my Catalina Beta VMs has Hardware Level 10.x (this is coming from an older VM, which works fine). I dare not change this hardware level on the older VM, as it has failed many times when I do that, and also it works well set that way.

2nd one has 15.x (this is coming from a VMDK file downloaded from the Internet, with an older Catalina Beta, I assume - D1). This was attempted to be upgraded to PB1 (i.e D2).

 

1) First one - wrong disk was shown in the Terminal script. After power on of Beta VM, it dies and cannot boot. Thankfully older VM still works (unsure is script actually touched that, maybe not?).

2) 2nd one - disk does not show at all, so the script cannot do anything.

Screenshot: https://cloud.mail.ru/public/yNLR/jE7WJY5et

 

Any other ideas here?  :(

NOTE: When I use my older macOS VM the usual way, just ONE disk shows on the macOS desktop.

However, when I added the Rescue Disk to the VM as suggested  this caused 3 disk drives to show somehow - Disk 1 with regular name, plus Disk 1 with "- Data" added after the name, and the 3rd, rescue disk.

Opening said 2nd disk with "- Data" added to its name shows different folders than the main Disk #1.

 

Could this be an issue?

 

EDIT: Is there any way to modify the files that need a change without booting into a 2nd VM?
Such as boot into some Boot Loader as Clover, or maybe boot into a Rescue Disk (this works in Windows, unsure how it works in macOS, I guess it is very different).

And somehow edit the files that need editing, so the NEW/updated macOS Catalina Beta can then boot? 
Possible, or not? :huh:

 

Edited by Naki

Share this post


Link to post
Share on other sites
On 7/5/2019 at 10:34 PM, Naki said:

fusion71au -- sorry but all I get is total failure and time lost. Does not work!

 

@Naki, for some reason, the automated script is not seeing the hidden and locked "macOS Install Data/Locked Files/Boot Files" folder (probably a problem with Catalina's new "firmlinks", specific to updating Catalina physical disk partitions containing "--Data" volume). 


The extra "Data" volume you are seeing when booted into High Sierra or Mojave with Catalina vmdk attached is normal since Catalina splits its System Volume (read only) from its User's Data volume.  When booted into Catalina, this Data volume is hidden from the user (but can be seen from terminal with diskutil list command).


Here is the upgrade and rescue process from DP2 (build 19A487l) to DP3 (build 19A501i) done manually...


I have downloaded the full "Install macOS Catalina Beta.app" from Apple's software catalog with @crazybirdy's downloader script (keep a copy safe eg on 16GB USB drive).  The app is directly run while booted into DP2_19A487l and I have chosen to install over the top of the existing macOS_apfs volume (note diskutil list output shows the existence of macOS_apfs--Data volume)...

 

Spoiler

288576053_DP2toDP3upgrade1.thumb.png.8850706d3f6a24b6f79984863635c993.png6297822_DP2toDP3upgrade2.thumb.png.f5fdb13736d07f711aab3a462c5bcc2c.png1987314238_DP2toDP3upgrade3.thumb.png.32dd3bdd6494ac099e08b89b6fd7421e.png


On the first reboot into the second phase install, we are actually booting into the install files which have been placed by the installer in the macOS_apfs--Data volume @/macOS Install Data/Locked Files/Boot Files.  This is more clearly seen if you have Clover ---> can see the following verbose screens...

 

Spoiler

1508742264_DP2toDP3upgrade4.thumb.png.3cfd85bfe0da811df033332364dbea32.png1203380331_DP2toDP3upgrade5.thumb.png.d847ca4b65cd6fe00b1198c5128d8f94.png


Note the kp occurs due to "Error unserializing prelink plist" - VMware's firmware is unhappy about the vanilla prelinkedkernel used during the upgrade process.


Next, I have attached the Catalina vmdk to my Mojave virtual machine as an extra HD.  I have booted into Mojave to "rescue" the Catalina install.  I have run the "ShowAllFiles.app" to show the hidden "Locked Files" folder.  Note it is located inside the "macOS Install Data" folder on the macOS_apfs--Data volume.

 

Spoiler

775325664_DP2toDP3upgrade6.thumb.png.3a1d6189883861f9a9e9bfc41e9fdfc3.png878862588_DP2toDP3upgrade7.thumb.png.b481d759482e1a0aecc3591c96e0dcd3.png


In order to replace the prelinkedkernel, we need to take ownership of the "Locked Files" folder.  Right click the "Locked Files" folder, click "Get Info", click the arrow next to Sharing & Permissions, click the lock icon and provide your admin password, click the plus button to add yourself to the list of owners and then select "Read & Write" to have custom read/write access privilege...

 

Spoiler

338813320_DP2toDP3upgrade8.thumb.png.eed0e21b821fb55b99b6f204d2ac893d.png959344954_DP2toDP3upgrade9.png.3b8536ee257c1a01fb3eee84d5dc17a6.png1753630103_DP2toDP3upgrade10.png.e3dacb9b5a1a7b4009ad4acd17f16db9.png


The next steps involve renaming the original prelinkedkernel to prelinkedkernel_orig (in macOS_apfs--Data/macOS Install Data/Locked Files/Boot Files) and then copying the prelinkedkernel from copyprelinkedkernel_19A501i.zip into the same folder.  Note the original plk is 26.4MB in size compared to the 16.5MB plk provided.  Provide your admin password when Finder asks you...  

 

Spoiler

712866751_DP2toDP3upgrade11.thumb.png.caa7d8db334d687ebb4501a8d7a534c7.png1869148895_DP2toDP3upgrade12.thumb.png.75744b9a2644f961705f6d6fb831444f.png


Shutdown the Mojave VM (can also detach the Catalina vmdk now), then restart the Catalina VM.  You should now find the upgrade to DP3 proceeds normally...

 

Spoiler

1670094477_DP2toDP3upgrade13.thumb.png.f128b310781a060a633f41cdb19dd574.png744878375_DP2toDP3upgrade14.thumb.png.ffe19b75fd5288a3f24550c2bdd41476.png233325046_DP2toDP3upgrade15.thumb.png.4becfdb914bd87d072927755f967585e.png

 

2068610655_DP2toDP3upgrade16.thumb.png.c2e7f1074cdc29b53fc1d0b39631fb65.png

Edited by fusion71au
Extra info on problems due to Catalina's new firmlinks

Share this post


Link to post
Share on other sites

fusion71au -- Thanks! This sounded very hopeful and fairly easy.

However, after many attempts at 5-6+ hours with upgrade download failing for me at near the end of downloading the 6+ GBs file, I gave up on this - I was doing this from the older macOS Catalina Beta 478 Build, this I think is Beta 1.

Then I was able to locate Beta 2 (but not Beta 3) in DMG format on the Internet. 

It all worked as you say - shutdown the dead macOS Catalina VM, attach disk file as 2nd disk to macOS Mojave VM, locate the special Locked Files folder, take ownership/give rights, rename that file, copy modified file version, then shutdown Rescue VM, detach disk from it, power on Catalina Beta VM again. All went fine until the 1st restart! The macOS was upgraded from 478 to 487 Beta Build successfully.

 

However, it said VMware Tools was disabled, asked if I want to re-enable it, which I did because I obviously need VMware Tools to work, but it then asked to restart to enable it.

And now it is stuck - tried 2-3 times with force restart, no change - progress bar goes fine at first, then goes to 25%, 50%, 75%/etc just fine.

But then just BEFORE it should boot into the OS, with progress bar filled in 100%, the VM gets "stuck"/frozen with no way out. :(

Screenshot: https://s.mail.ru/2ZDi/v5q7Caqx4

 

Now what, please?

I will be trying to update to 501 instead of 487 later on... But would like ideas why 487 does not work? :)

Edited by Naki

Share this post


Link to post
Share on other sites
On 7/8/2019 at 9:04 PM, IvoH said:

@fusion71au

Would be interesting to know how to create copyprelinkedkernel_19A501i.zip. What are the particular steps? 

@IvoH,

 

I use Apple's kextcache utility to generate the prelinkedkernel with an automated script: BaseSystem_PLK.tool

 

Prerequisites

  1. Full installer "Install macOS Catalina Beta.app" for the specific Catalina build eg 19A501i
  2. Pacifist app
  3. Mojave or Catalina installation with SIP disabled to run the automated script in

 

Procedure

1.  Download and extract the attached BaseSystem_PLK.tool_Catalina.zip into your ~/Downloads folder.
2.  Copy BaseSystem.dmg from Install macOS Catalina Beta.app/Contents/SharedSupport (right click the installer app to show contents) to ~/Downloads/BaseSystem
3.  Extract the Catalina kernel with Pacifist from Install macOS Catalina Beta.app/Contents/SharedSupport/InstallESD.dmg/Packages/Core.pkg to ~/Downloads/BaseSystem/Kernels
 
Spoiler

1584072367_ExtractkernelfromCore_pkg.thumb.png.4c1c16fdf919cd332e109e75545a59a3.png

 

 
4.  Extract AppleActuatorDriver, AppleBluetoothDebugService, AppleConvergedIPCOLYBTControl, AppleConvergedPCI, IOSlaveProcessor, KernelRelayHost kexts from Install macOS Catalina Beta.app/Contents/SharedSupport/InstallESD.dmg/Packages/Core.pkg to ~/Downloads/BaseSystem/ExtraKexts with Pacifist
5.  Open terminal and run the following commands...
cd ~/Downloads/BaseSystem
chmod +x PLK.tool
./PLK.tool

---> supply your admin password ---> will place your new prelinkedkernel on the desktop.

 

Some background reading in the thread below:

How to create a macOS Installer which doesn't need bootloader kext injection (FakeSMC in pre-linked kernel), bypass High Sierra firmware and MBR check

 

 

On 7/9/2019 at 1:00 AM, Naki said:

fusion71au -- Thanks! This sounded very hopeful and fairly easy.

However, after many attempts at 5-6+ hours with upgrade download failing for me at near the end of downloading the 6+ GBs file, I gave up on this - I was doing this from the older macOS Catalina Beta 478 Build, this I think is Beta 1.

Then I was able to locate Beta 2 (but not Beta 3) in DMG format on the Internet. 

It all worked as you say - shutdown the dead macOS Catalina VM, attach disk file as 2nd disk to macOS Mojave VM, locate the special Locked Files folder, take ownership/give rights, rename that file, copy modified file version, then shutdown Rescue VM, detach disk from it, power on Catalina Beta VM again. All went fine until the 1st restart! The macOS was upgraded from 478 to 487 Beta Build successfully.

 

However, it said VMware Tools was disabled, asked if I want to re-enable it, which I did because I obviously need VMware Tools to work, but it then asked to restart to enable it.

And now it is stuck - tried 2-3 times with force restart, no change - progress bar goes fine at first, then goes to 25%, 50%, 75%/etc just fine.

But then just BEFORE it should boot into the OS, with progress bar filled in 100%, the VM gets "stuck"/frozen with no way out. :(

Screenshot: https://s.mail.ru/2ZDi/v5q7Caqx4

 

Now what, please?

I will be trying to update to 501 instead of 487 later on... But would like ideas why 487 does not work? :)

 

2 potential and related issues here. 

 

1.  You may have an old version of VMware tools that is incompatible with Catalina eg you may have used @Donk's unlocker a while ago on your VMware Workstation and it is only offering to install a 32bit darwin.iso ---> crashes your Catalina VM because macOS SIP setting won't let the VMware Tools kexts load (ie don't install the VMware tools offered automatically by VMware WorkStation).  I have attached a Catalina compatible 64bit VMware Tools here: darwin.iso

 

Boot the VM and download/extract it into your ~/Downloads folder ---> right click, open the iso ---> right click "Install VMware Tools.app", run the package installer.

 

2.  With Catalina's new "read only" system volume and security settings, you may need to mount the / folder as R/W and disable OSX gatekeeper + System Integrity Protection (SIP) before running the package installer.

 

In terminal, type the following lines, followed by <Enter>

sudo mount -uw /
sudo spctl --master-disable

Check System Preferences/Security & Privacy/Allow apps downloaded from ...VMware etc.

 

Also check that System Integrity Protection status is disabled eg

fusion71au@fusion71aus-iMac ~ % csrutil status
System Integrity Protection status: disabled.

 

You should be able to rescue the current installation by booting to Catalina with Clover in safe mode and disabling System Integrity Protection (Clover Options/System Parameters/SIP set to 0x0277, Allow Untrusted Kexts, Allow Unapproved Kexts) ---> uninstall old VMware Tools, reinstall new Tools...

 

1.  Attach Clover-v2.5k-5051-X64.iso to your Catalina VM as a virtual CD/DVD

2.  Close the VMware program, then edit the virtual machine's vmx file with WordPad to add the line bios.bootDelay = "3000" ---> allows the virtual machine enough time to register key presses during boot up

3.  Start the VM, press <F2> when you see the VMware logo to access the VMware BIOS, choose to boot from the CD ---> will see Clover main GUI ---> choose Catalina volume (or Preboot volume) to boot, then <Spacebar> for extra options, check Safe Mode (-x), then select "Boot macOS with selected options" + <Enter>... 

 

Spoiler

973091377_SIP0x0277.thumb.png.0bb8e23e401dd2cacf77066d30306882.png904508943_SafemodeCloverboot.thumb.png.3ff17c25dbf960d80ecd7b8a82cf6ece.png

 

Carefully observe the verbose output for errors.

 

Sometimes EFI memory error may be seen.  Usually OK to reboot VM and try step 3 again.

Edited by fusion71au
Explain need to disable SIP for full functioning of VMware Tools in Catalina

Share this post


Link to post
Share on other sites

What is the status of this issue as far as current month - August 2019 - and day is concerned?
I am seeing lots of people (2200 and counting) are reading this thread, but besides the helpers ZERO people confirmed it works for them! :unsure:

 

Is there a better/easier way to get the latest Catalina Beta working in VMware on a Windows PC?
What is the currently latest Public Beta? I guess it is a bit (or a lot) older than Developer Beta?
When is next Public Beta due?

 

EDIT: 1 more question, please.

To use Public Betas, it is easy - have a free Apple Beta account, login to that, then download Beta/etc as wanted.

However, Developer Betas require a paid Apple developer account, IIRC - $99/year.

Does the Installer Downloader script linked (attached) above skip this payment? Allowing anyone to download the Developer Beta, without needing a paid Apple developer account?
Please clarify. :)

Edited by Naki

Share this post


Link to post
Share on other sites

Guys, I have some positive progress! :)

Posting in a 2nd post, because the issue is different now plus text is lengthy, so I hope 2nd post is OK to do. :)

Somehow my previous Catalina Beta VM (with Apple logo stuck, and needing the copykernel steps given above) got all messed up, the Snapshots somehow failed so could not go back, and I had to delete it.
So, I copied my Mac OS X 10.10 Yosemite VM files - not too new version, not too old - just right - into a new Catalina folder.

Powered it on, then did a shutdown. And deleted all the Snapshots so that I can increase main HDD size, then upped the CPUs to 2 (was 1), upped the HDD from 40 GB (no space for Catalina Beta installation) to 86+ GB, and also upped the RAM from 3.something to 4.something GB.

 

Then used a 2nd VM with Mojave to download the Catalina Beta DMG installer, put that on a 16 GB USB flash drive as suggested, and then connected that to the 10.10 VM.

Copied the DMG installer into Applications, and ran it. All fine, followed the steps to change from macOS VM setting to Windows 10 64-bit.

Then change back to macOS 10.14 Setting - hardware level was at 10.x, upped that to 14.x level as prompted - then went on with Catalina Beta installation.

Did that, somehow it survived a restart! :w00t:

 

Tried a few more times, always works - the VM loads just fine after restart, unlike before. Great! Even VMware Tools works - at least partially - copy/paste of text into Guest VM works, Shared Folders also work.

Now, only issue left is the VM display resolution. This stays at only 1024x768, so the Catalina Beta VM is hard to use.

Tried to download this tool I use on older VMs:

https://github.com/MarLoe/VMware.PreferencePane

but no go, Catalina Beta refuses to run it at all, as it does not conform to the rules for protected and 64-bit Mac apps & extensions.

 

Any ideas how to get all resolutions working, or at least choose 1 higher than 1024x768, please? :)
NOTE: System this is on is: Windows 10 64-bit, Intel Core i5 CPU with 4 cores/4 threads (Ivy Bridge), 32 GBs of RAM, large C: drive with 2 SSDs in RAID0, several HDDs, using 2 monitors - 27" 1440p, 27" Full HD.

VMware Workstation version is 15.0.3. (dare not update to 15.1, as this PC has some strange issue with VMware installer failing, then it is hard to get back to VMware working..)

VMware Tools is the latest one linked/attached a bit above, I think it is the 64-bit version of VMware Tools. :)

 

EDIT: Strangely enough, Chrome and Opera browsers work, but Firefox latest version only crashes. :) Any way to get Firefox working too? 

Also, very oddball feature is some updates and/or applications cannot run "because Apple cannot check them for malware". Nice! WTF of a stupid feature is this? :unsure: I hope they improve this in the next Betas.

 

EDIT #2: Can somebody fix the thread title, please? Says: Catatalina Beta 10.15 right now -- one "ta" is extra.

Edited by Naki
grammar/clarity

Share this post


Link to post
Share on other sites

Bump. Any help, please? :( Donk, @fusion71au ??

 

EDIT: Also, https://9to5mac.com/2019/08/19/macos-catalina-beta-6/ is out!

Being no Apple Developer, somehow I was offered this one too in my current working (sans resolution & Firefox) macOS Catalina Beta. Great! :)

Not so great was --  As you can imagine, I tried to install it and it peacefully sits on the Apple logo for hours now... :unsure:
Is there an updated copykernel ZIP file and/or script for this new version?

Edited by Naki

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.

  • Similar Content

    • By miliuco
      Install macOS 10.15 Catalina on Gigabyte P55-USB3 with Radeon RX 580 graphics card using a USB device created with the createinstallmedia command and Clover as bootloader. Instructions to install macOS 10.14 Mojave on this computer are almost identical, replacing Catalina app with Mojave, so this article is suitable for both versions of macOS. The Gigabyte P55-USB3 motherboard (and some others from the same brand with the P55 / H55 chipset) have made it easy to build a hackintosh and install macOS since 10 years ago. Although it is an old motherboard, the behavior with Mojave or Catalina is very good after changing the classic hard drive (HDD) for a solid state drive (SSD).

      Components of the hackintosh
      Gigabyte GA-P55-USB3 motherboard: P55 chipset, 1156 socket, ALC892 audio, Gigabit RTL8111D network, DDR3 RAM Intel Core i5-750 processor for socket 1156: 4 cores, 8MB cache, clock rate 2.66 GHz Fenvi FV-T919 wireless + Bluetooth card: PCI-Express, wifi is ac type, detected by macOS as Airport and Apple Bluetooth Radeon RX 580 8 GB graphics card: works OOB but with a few details to be considered, it has its own article.  
      Previous requirements
      Install macOS Catalina app in /Applications folder USB flash drive with at least 16GB prepared from Disk Utility with MBR partition scheme and formatted as Mac Os Plus (on older Gigabyte boards like mine, USB sticks partitioned with GUID scheme instead of MBR usually hang the system when booting) Recent version of Clover (I have used r5117) Recent versions of Lilu (at least 1.4.4) and WhateverGreen (at least 1.3.9) to fine-tune the behavior of the graphics card Recent version of RealtekRTL8111 (I have used 2.2.2) FaceSMC version 6.26-322 (newer versions disable automatic mounting of USB devices on my system).  
      Create install USB
      Run this command from Terminal (assuming the target device is called USB):
      Bash: sudo /Applications/Install\ macOS\ Catalina.app/Contents/Resources/createinstallmedia --volume /Volumes/USB /Applications/Install\ macOS\ Catalina.app
      Clover must be installed on the USB memory, I choose the following options:
      Bootloader > Install boot0af on the MBR CloverEFi > CloverEFI 64-bit SATA BIOS Drivers, 64 bit > Recommended drivers > FSInject + SMCHelper + XhciDxe BIOS Drivers, 64 bit > File System drivers > ApfsDriverLoader Install RC scripts on selected volume Optional RC scripts > Disable sleep proxy client.  
      You have to copy 4 kexts to the EFI/CLOVER/kexts/Other folder of the USB device: FaceSMC 6.26-322, Lilu 1.4.4, WhateverGreen 1.3.9 and RealtekRTL8111 2.2.2. Regarding the config.plist file, the most significant is:
      Boot > kext-dev-mode = 1 in Boot arguments GUI > Theme embedded, EmbeddedThemeType Dark, Screen Resolution 1920x1080, Preboot in Hide Volume Graphics > blank, nothing is checked except if foxbox solution is used to have more than 2 connectors enabled RT Variables > 0x28 in BooterConfig and 0x67 in CsrActiveConfig SMBios > iMac14,2 Sytem Parameters> Yes in Inject Kexts and check Inject System ID.  
      Install macOS Catalina

      Boot from the USB device and choose Install macOS from Install macOS Catalina. The installation program runs until the PC restarts. Here choose Install macOS from HDD (the name of the volume you are installing macOS on). With RX 580 graphics card, the screen goes black in this second phase of the installation, it is a phase in which the user has nothing to do until the PC is restarted so you can let it work until the Clover menu again. You have to choose Boot macOS from HDDto boot the installed system from the hard disk, the screen is recovered and you can configure the account and the initial options. From this moment the screen works fine.

      In summary:
      Boot from USB > Clover menu > Install macOS from Install macOS Catalina > screen works fine Boot from USB > Clover menu > Install macOS from HDD > black screen Boot from USB > Clover menu > Boot macOS from HDD > screen works fine.  
      Install Clover and kexts on the hard drive

      Clover needs to be installed on the disk where we just installed macOS. Options are the same as when installing it on the USB memory. You also have to copy the 4 kexts (FaceSMC 6.26-322, Lilu 1.4.4, WhateverGreen 1.3.9 and RealtekRTL8111 2.2.2) into the EFI/CLOVER/kexts/Other folder on the EFI partition of the disk. And review the config.plist file remembering the comments for the USB.

      If everything goes well, the computer starts from the hard disk with a running copy of macOS Catalina.
       
       

    • By miliuco
      Radeon RX 580 8 GB graphics card on macOS High Sierra (as of 10.13.6), Mojave and Catalina on the P55-USB3 board: excellent performance with acceleration (Metal) OOB, no need for drivers (kexts), with 3 drawbacks, one has to do with the boot of the operating system (a solution is proposed), another with the number of rear connectors enabled (a solution is proposed) and another that only affects to one phase of the Mojave or Catalina installation (without clear solution for now).

      I have placed the XFX AMD Radeon RX-580 P8DFD6 8GB Triple X Edition GDDR5, 256BIT, DVI + HDMI + 3DP graphics card on a 10 year old motherboard (Gigabyte P55-USB3) in order to update the hackintosh to 10.14 Mojave and 10.15 Catalina because the card that I have used in past years, Nvidia Geforce GTX 750 1GB, has stopped working after 10.13.6 High Sierra since this was the last version for which Nvidia published the alternate web drivers that were necessary for the card to work well with graphic acceleration.

      The new RX 580 card needs considerably more space than the old one although it fits perfectly in an ATX case, and requires an additional power connector. It has 2 big fans that most of the time are stopped, at least in my case. In macOS it works perfectly, even with Metal acceleration, without additional drivers and without extra settings in Clover. But it has drawbacks that I comment below.

      Alterations during startup

      During the boot of the operating system, when the screen goes from the basic driver to the AMD driver, 2 artifacts appear randomly, they are very short in duration (from one to a few seconds):
      Very short flashing white screen that may or may not be accompanied by purple lines The fans runs for a few seconds (the noise is clearly audible). This behavior is solved with the installation of 2 kexts, Lilu and WhateverGreen. Lilu is an extension created by acidantheraand vit9696 among others whose function is to help to patch kexts, processes and libraries during macOS boot. It is accompanied by specific plugins for the task required, for example WhateverGreen that injects necessary patches for certain AMD, Intel and Nvidia graphics cards. It is mandatory to have both extensions together, one of them separately does not correct the problem.
      I have installed Lilu 1.4.4 and WhateverGreen 1.3.9 in the EFI/CLOVER/kexts/Other folder of the EFI partition and artifacts have disappeared. Remember that these 2 extensions are not necessary for the card to work properly, if you tolerate those very brief distortions of the screen or the noise of the fans running for a few seconds, you can live without Lilu and WhateverGreen.

      Note: authors recommend that when using Lilu and WhateverGreen with Radeon cards, NO graphic settings have to be added to Clover (Inject ATI, etc.).

      Note: these alterations, especially the brief white screen and less frequently purple lines and fan noise, are also seen in Windows and some real Macs with the same card.

      Alteration during macOS installation

      Boot from USB > Clover menu > Install macOS from Install macOS Catalina > screen works fine
      Boot from USB > Clover menu > Install macOS from MacintoshHD > black screen
      Booting from USB > Clover menu > Boot macOS from MacintoshHD > screen works fine.

      In the first and third stages, screen works fine. In the second stage the screen goes black although the installation continues. The user has nothing to do at this moment so you can leave the PC working until the Clover menu is shown again, the screen is recovered, the initial account options can be configured and you can enter into the newly installed system with correct resolution and acceleration.
      This behavior is not corrected even by placing Lilu and WhateverGreen into the USB device. At least in my case I have not found a solution for it. Yo can install macOS perfectly with that drawback of not seeing how it progresses during the second phase of the installation.

      Only 2 connectors of the 5 available work

      This card has 3 Display Port (DP) ports, 1 HDMI port and 1 DVI port. In my case, only 2 DP work, those that are further from the HDMI connector. It is enough if you use a single monitor or 2 monitors that can be connected by DP. But if you want to have 3 or more connected devices or some of them only have HDMI, it is necessary to enable the 5 connectors or at least 4 of them since the DVI is obsolete and does not allow resolutions as high as DP and HDMI.
      User foxbox has proposed a solution in a thread titled [Solved] Sapphire RX 580 Nitro + SE | black screen on HDMI and DVI. Must inject from Clover a modification to the Orinoco framebuffer (which is used in the RX 580 card) so that the 5 connectors lack a fixedly assigned address and, instead, receive it dynamically. This change is made from the KextsToPatch section of Clover. Read the post from foxbox.
      This has to be accompanied by 3 changes in the Graphics section of Clover: Orinoco in FB Name / Inject ATI / 5 in Video Ports. I have tested this solution in macOS Catalina and it effectively enables the 5 ports of the card but, since I only use 1 monitor, I have removed it and I am with Lilu and WhateverGreen.
       

    • By vinnytwice
      How to finish the Catalina installation.
      1. Use EasyMBR-Installer1015 to make USB Catalina Installer.
      2. Boot to USB Catalina Installer, open Utilities -> Disk Utility, format as MBR HFS+.         <==  won't boot..there is no boot loader in the created usb drive..also format "target drive"
          Install Catalina to blank MBR HFS+ "Target" partition.
      3. Boot to USB Catalina Installer, open Utilities -> Terminal, run the script command:         <== no Volumes gets listed to select
          copytempdata
      4. Boot to "Target" MBR HFS+ partition on single user mode (-s), run the script command:install.log
          hfsupdatecache
      5. Reboot to "Target" MBR HFS+ partition, setup user name and login, finish the installation.
       
       
       
      After trying many times of following the procedure for EasyMBR-Installer1015 creation I'm stuck at step 3.
      Basically what I've done is:
      1. I made the usb with EasyMBR-Installer1015.
      1b. Installed clover on it.
           Added Lilu,WhateverGreen, AppleAHCIPort AppleALC  kexts needed for my motherboard in other folder.
           Set RtVariables to BooterConfig 0x28 CsrActiveConfig 0x67.
           Set SystemParameters InjectKext to yes.
      2. Boot into the Usb installer fine, formatted the target drive and installed Catalina on it.
          Installation went smooth and system rebooted. At Clover screen dough I see a new Catalina recovery disk. ( not sure it's normal )
      3. Reboot into the Usb installer again and from terminal run the script copytempdata.
          The script asks to select a drive from the available ones to perform three things..
          but in script  "Available target volumes:" there's none to select and there I'm stuck.. 

      I checked the volume I installed Catalina on and it has this folder structure:
      private/var/log/install.log()114 kb
      vm (empty)  
      GetInfo shows 8,56 GB used.
      I attached the log so it might help understanding what's happening .
      What else can I check to see what's happening?
      Thank you very much
    • By tonyx86
      This guide is a work in progress and will be updated as I refine the installation.
       
      Background
      This is my first "modern" hack supporting UEFI and my first hack using Clover "on-the-fly" patches.  My previous hacks
       
      Laptop: Thinkpad T61 / Nvidia NVS 140m Laptop: Dell Latitude E6410 / Nvidia G3100m Desktop: Gigabyte G31 / GeForce 9600 Desktop: Biostar TH55HD / Sapphire Pulse RX580 (Google "Catalina Biostar TH55HD" and look for user name deeveedee)  
      are all perfectly running Catalina and I patched them all "manually" - all DSDT patches applied with MaciSL with virtually no Clover on-the-fly patching and all booted Legacy Clover.  This UEFI hack was MUCH easier and took about 20 hours vs. a combined hundreds of hours for the old hacks.  I wanted a hack that was a little more future proof and I think this is it.  I hope you enjoy this as much as I am enjoying it.  It is a perfect MacMini8,1.
       
      My system specs
      HP EliteDesk 800 G4 Mini (I7-8700T / UHD 630 / Q370 Chipset / 32GB DDR4 RAM) 3 x DP Ports (connected to monitors using DP -> DVI adapters) 6 x USB 3.1 1 x USB Type-C 3.1 2 x NVMe SSD (M.2 PCIe x4 2280/2230 combo ports) 1 x SATA6 SSD 1 x Intel Ethernet RJ-45 Conexant CX20632 Audio Codec SMBIOS MacModel MacMini 8,1 Unsupported M.2 PCIe x1 2230 Intel Wi-Fi (currently disabled in BIOS).  I may replace this with Brcm, but am using only Ethernet (IntelMausi) for now.  
      Installation Steps: To be provided
      See attached EFI and /L/E kexts in EliteDesk.zip archive See installation methodology here See references here  
      What is not working
      Wi-Fi / Bluetooth (intentional since I have not yet replaced my Intel card).  
      What is not tested
      USB c 3.1 port Microphone port  
      What is working
      Everything not mentioned above Sleep / Wake Multiple displays with IGPU graphics acceleration, hot pluggable display ports and DP->DVI adapters USB 3.1 ports Audio (internal speaker and headphone jack) Ethernet Auto-sensing headphone jack automatically switches to internal speaker when headphones removed  
      Known Issues and their solutions
      (Solved and included in the attached EliteDesk.zip archive) Unable to upgrade from 10.15.4 to 10.15.5 when using IntelMausiEthernet.kext.  Solution is to switch to IntelMausi.kext (Rev 1.0.2 here). (Solved and included in the attached EliteDesk.zip archive) Some USB devices were not recognized. My SSDT-UIAC.aml was incomplete and did not specify all required USB port types (missing SSxx ports). The attached EliteDesk.zip archive includes this fix. (Reported this as a possible Clover issue - no solution yet) Clover boot loader may default to Recovery volume after a normal shutdown.  Work-around is to select your normal macOS volume.  This may only happen when Clover is configured to boot LastBootedVolume and may be "fixable" by explicitly setting a boot volume (haven't tested this). (No longer observed) At least one display blanks (sleeps) when plugging / unplugging USB device (observed in front USB 3.1 ports).  Display wakes immediately on keyboard and mouse activity, so this is a minor issue but may be indicative of another issue. (Solved - this is a BIOS setting and requires no macOS changes) Safari has problems loading insanelymac web pages after sleep / wake.  I suspect that the problem is with the embedded video on the pages.  Also observed video problem in AppStore after sleep/wake.  Console: VideoDecodersUnavailable.  Solution is to enable Intel ME in BIOS. (Solved and included in the attached EliteDesk.zip archive) Display does not fully wake after resuming from sleep (needs an extra mouse or keyboard stimulus to fully wake).  Solution is to change boot arg darkwake=0 to darkwake=2.  Other values of darkwake may work as well, but this is the first I tried and it worked. (Solved and included in the attached EliteDesk.zip archive) -disablegfxfirmware boot arg is not required with WEG.  I inadvertently left this boot arg after I encountered an endless gfx firmware update boot loop while working on my FB patching.  This boot arg is no longer necessary after completing FB patching with WEG. (Solved and included in the attached EliteDesk.zip archive): Sometimes, CMOS time is lost on shutdown or restart.  Solution is to enable Clover's Apple RTC fix in config.plist. (Solved and included in the attached EliteDesk.zip archive) headphone jack doesn't work.  Solution is to change HDEF layout-id to 28. (Solved and included in the attached EliteDesk.zip archive) System freezes on wake from sleep because of a kernel panic related to hda-gfx (my system does not have HDMI and my DP->DVI adapters do not drive monitor speakers).  Solution is to add No-hda-gfx property to HDEF as described here.  This property is recognized as a Lilu flag and prevents loading hda-gfx. (Solved and included in the attached EliteDesk.zip archive) Device (PMCR) is not defined.  Solution is a SSDT that "injects" the missing device. (Solved and included in the attached archive) eficheck is loaded (not sure why this is bad, but may be a privacy issue - see here). Solution is to add updated EFICheckDisabler kext that include Q370 chipset.  See here.  
      BIOS Version / Configuration: To be provided
      Version: 02.11.01 Rev.A Intel ME must be enabled for proper sleep / wake of UHD 630
       
      Clover Configuration: To be provided
       
      UHD 630 Framebuffer Patching: To be provided
       
      Current Versions
      Catalina 10.15.4.02 Clover (UEFI) r5118 Lilu.kext 1.4.4 WhateverGreen.kext 1.3.9 AppleALC.kext 1.4.9 IntelMausi 1.0.2 (Not IntelMausiEthernet)  
      Credits To be provided
       
       




      EliteDesk800 G4 Mini - Rev 0.7.zip



    • By tonyx86
      This thread for installing Catalina on the Dell Latitude E6410 WITH NVIDIA GRAPHICS (BIOS A17, NVidia 3100m) will help you install a fresh installation of Catalina on your Dell Latitude E6410, it will help you upgrade from 10.15.2 to 10.15.x (if you originally installed Catalina from this thread) and it will also help you upgrade from Mojave 10.14.6 if you have already installed Mojave by following the instructions here.  The instructions in this first post assume that you are installing Catalina in an APFS container.  If you are curious about the evolution of this solution and how sleep/wake was solved, review the Mojave installation thread.
       
      Important: This Thread is NOT intended to help you install macOS on a Latitude E6410 with Intel HD Graphics (without Nvidia graphics).  The DSDT attached to this first post (in E6410-Catalina.zip) is VERY SPECIFIC to the Nvidia graphics implementation and has not been edited for HD Graphics - there are elements required for HD Graphics that are missing from the attached DSDT and there are DSDT mods that have not been tested with HD Graphics.  Also, the kexts attached to this first post are specific to a Broadcom Wi-Fi card which must replace the original Intel Wi-Fi card.
       
      This first post will be modified to reflect lessons learned and to reflect the most current working state of my Latitude E6410 (with NVidia 3100m discrete graphics) running Catalina.  Issues, observations and performance tips are recorded toward the bottom of this first post.  My recommended CLOVER configuration is specified toward the bottom of this first post.
       
      *** If you want help with your installation, please post your issue along with problem reporting files generated using @black.dragon74's problem reporting tool.  Google 'GENERATE PROPER PROBLEM REPORTING FILES black.dragon74' to find it. ***.  If Catalina's Read-Only protections block your installation of black.dragon74's gen_debug script, please copy the attached gen_debug script to your Desktop, change script properties with the terminal command 'chmod a+x ~/Desktop/gen_debug' and run the script from your Desktop.
       
      My system is as follows:
      Dell Latitude E6410 (I7-620m, Nvidia 3100M, 8GB DDR3, 512GB SSD, 1440x900 display, BIOS: A17) Wi-Fi: Broadcom BCM 94352HMB (replaced original Wi-Fi card) BIOS (version A17) configured as follows (leave default unless listed here): Boot Sequence: USB, Internal HDD, CD/DVD, Modular Bay HDD; Boot List Option: Legacy; Integrated NIC:Enabled; Parallel Port: Disabled; Serial Port: Disabled; SATA Operation: AHCI; Misc Devices: Enable Modular Bay, Camera, External USB, Microphone, Media Card and 1394; Latitude ON Reader: Disabled; Keyboard Illumination: Auto ALS and Input; Ambient Light Sensor: Enabled; OROM Keyboard Access: Disable; TPM Security: Disable; Computrace:Deactivate; CPU XD Support: Enable; Performance: Enable all options; Power Management: Disable Wake on AC, Disable Wake on LAN/WAN, Express Charge: Standard, Charge Behavior: Enabled; Keypad: Fn Key Only; Mouse/Touchpad: Touchpad/PS-2 Mouse; USB Emulation: Enable Legacy; Fn Key Emulation: Disabled; Fastboot: Thorough; Virtualization: Enable Intel Virtualization, Disable VT for Direct I/O, Disable Trusted Execution; Wireless Switch: Bluetooth and WLAN; Wireless Device Enable: Bluetooth and WLAN;   
      Versions of the software used in this installation are listed below the installation steps.  EFI and kexts for Catalina are attached to this first post in E6410-Catalina.zip.  CLOVER configuration is specified below the installation steps.
       
      Wi-Fi connection to an Access Point is delayed when using AppleALC for sound.  Do not use Apple ALC.  Use VoodooHDA pkg 2.9.2 v15 for sound.
       
      Steps to install Catalina on a Dell Latitude E6410 (BIOS A17, NVidia 3100m)
       
      If you want to upgrade to 10.15.5, see instructions at this post.
       
      If you want to upgrade to 10.15.4, see instructions at this post.  
       
      Follow instructions below for 10.15.2 and 10.15.3.
       
      Make sure that your system matches my system description above (including BIOS version, Wi-Fi card, BIOS settings) If performing an upgrade from Mojave or a previous version of Catalina, backup your Mojave or Catalina partition! (Carbon Copy or similar) Download Catalina Installer Download DosDude Catalina Patcher Use DosDude Patcher to create Catalina USB Installer Delete LegacyUSBInjector.kext (we're using @RehabMan's USBInjectAll.kext with custom SSDT) and delete SIPManager.kext (CLOVER is managing SIP) from Catalina USB Installer's /Library/Extensions folder Copy all but the FakeSMC sensor kexts in E6410-Catalina.zip (attached) LE folder to the Catalina USB Installer /Library/Extensions (copy all kexts (including FakeSMC.kext) but not the FakeSMC sensor kexts) Install CLOVER Bootloader (Legacy) on USB Installer using the EFI in the E6410-Catalina.zip (attached).  Use the CLOVER configuration specified below.  Be sure to replace the XX-MASKED-XX parameters in the attached config.plist with your own values. Reset your Latitude E6410 NVRAM by doing the following (this may be important if you're making changes to your existing EFI and won't hurt anything if you're not making any changes) turn-off your laptop remove A/C power and main battery press and hold the power button for 30 seconds restore A/C power and battery Boot your Latitude E6410 from the Catalina USB Installer that you created in steps 5-8. Select "Reinstall macOS" (note that I have existing installations of Mojave and High Sierra on my Latitude E6410, so it's possible that this menu item changes to "Install macOS" if you don't have any previous macOS installations). Select your Catalina destination partition (which will be your Mojave or previous Catalina partition if you are upgrading) After the Catalina Installer reboots the first time, boot from the "macOS Installer" partition on the disk that you selected as your Catalina destination (not the macOS installer on the USB) After the Catalina Installer reboots the second time, boot the Catalina macOS Installer on the USB Select the Post Install Patcher utility Select only the following Post Install Patches (no other patches / options) Install Patch Updater Legacy Video After the Post Install Patcher reboots,  boot from the newly installed (or upgraded) Catalina partition and complete the macOS configuration Remove these kexts (if they exist) from /Library/Extensions: LegacyUSBInjector.kext, LegacyUSBVideoSupport.kext and SIPManager.kext If you are performing a fresh installation of Catalina: Install CLOVER (LEGACY - NOT UEFI) on your boot disk and configure EFI using files in the attached E6410-Catalina.zip.  Use the CLOVER configuration below.  Be sure to replace the XX-MASKED-XX parameters in the attached config.plist with your own values. Install all kexts in the attached E6410-Catalina.zip LE folder to your /Library/Extensions folder. Copy HWMonitor from the application folder in the attached E6410-Catalina.zip to your Applications folder. Install VoodooHDA (I installed using the Classic method) Skip to Step 21 If you are upgrading from a previous version of Catalina using the instructions from this thread or from Mojave that you installed using the instructions here: Replace 3rd-party kexts in EFI/Clover/kexts/Other with those in the attached EFI folder.   Replace EFI/Clover config.plist with the attached config.plist (Be sure to replace the XX-MASKED-XX parameters in the attached config.plist with your own values) Replace EFI/Clover/ACPI/patched with the files in the attached EFI/Clover/ACPI/patched Replace 3rd-party kexts in /Library/Extensions with those in the attached LE folder Remove VoodooSDHC.kext from /Library/Extensions Re-install VoodooHDA if necessary (I installed using the Classic method for Catalina) Ensure PROPER kext installation: If you're manually installing kexts in /Library/Extensions, make sure that you execute the following (in terminal) cd /Library/Extensions sudo chown -R root:wheel *.kext sudo chmod -R 755 *.kext sudo kextcache -i / After you execute 'sudo kextcache -i /' you should observe that ALL kexts are allowed.  If not, your kext directory attributes are probably incorrect.  Repeat kext installation and try again. Reboot from your new/upgraded Catalina partition Welcome to macOS Catalina! Change the keyboard type to ISO (System Preferences > Keyboard > Change Keyboard Type) Swap the Command and Option keys (System Preferences > Keyboard > Modifier Keys) Set hibernatemode: In terminal, execute sudo pmset -a hibernatemode 0 sudo rm -f /var/vm/sleepimage sudo touch /var/vm/sleepimage sudo chflags schg /var/vm/sleepimage  
      Version Info at the time of this writing:
      Catalina Installer 10.15.5 CLOVER r5118 DosDude Catalina Patcher: v1.4.3 Lilu.kext 1.4.4 AirportBrcmFixup.kext 2.0.6 BrcmFirmwareData.kext 2.5.3 BrcmBluetoothInjector.kext 2.5.3 BrcmPatchRAM3.kext 2.5.3 IntelMausi.kext 1.0.2 (Not IntelMausiEthernet.kext)
      EFICheckDisabler.kext 0.5
      VoodooHDA.kext 2.9.2 v15 (NOT AppleALC)
       
      What is not working (that was working in Mojave)
      SD Card Slot (had to remove VoodooSDHC.kext which caused system freeze on wake)  
      Known Issues and Their Solutions
      (Solved - no further work required) Clover r5118 requires the config.plist key <key>NoDefaultProperties</key><false> to permit macOS to boot with Clover's "Inject Nvidia" = True.  See details here.  config.plist in the attached E6410-Catalina.zip archive includes this change. (Solved - no further work required) EFICheck is loaded.  Solution is to install EFICheckDisabler.kext which you can get here.  EFICheck.kext is included in the attached E6410-Catalina.zip archive. (Solved - no further work required) Some users experience display issues.  The solution is to remove Device (PNLF) from the DSDT.  Use the attached DSDT.  Removal of PNLF will disable sleep on lid closure.  Device (PNLF) can be added without modifying the DSDT by enabling the Clover PNLF ACPI patch.  The attached Clover config.plist enables the PNLF DSDT patch.  Disable the Clover PNLF patch if you experience display issues. (Solved - no further work required) USB sleep/wake power IORegistry keys are not injected (not included in Mojave's or Catalina's IOUSBHostFamily.kext).  Solution is to added SSDT-USBX.aml to EFI/CLOVER/ACPI/patched.  The attached SSDT-USBX.aml includes USB sleep/wake properties for MacBookPro6,2 from High Sierra 10.13.6 IOUSBHostFamily.kext. (No solution yet) Brightness slider does not work in System Preferences > Displays.  Brightness is easily controlled with Dell brightness keys.  There is some work on this later in this thread, but I will not be solving this as I'm content with the Dell brightness keys (and Ambient Light Sensor works to auto-adjust brightness). (No intention to solve) Display Settings in System Preferences are "garbled" when bright slider is visible.  This is a known issue with the legacy graphics patch and does not affect laptop operation. I continue to refine the DSDT and CLOVER config.plist to optimize my Latitude E6410 for multi-booting between various macOS versions (High Sierra, Mojave and Catalina at the time of this writing). If you upgrade your Latitude E6410 EFI using my attached EFI, you may find that your Latitude E6410 is stuck in a boot-loop that ends in a white screen and reboots.  Clear your system by doing the following: turn off your laptop, remove A/C power, remove the main battery, press and hold the power button for 30 seconds, restore A/C power and battery, boot normally.  I have only found this to be necessary (very rarely) after making an EFI change, but you may find it helpful if making kext changes in /Library/Extensions as well. (Solved - no further work required) Brcm firmware does not update when using BrcmFirmwareRepo.kext in /Library/Extensions.  Solution is to install BrcmFirmwareData.kext and BrcmPatchRAM3.kext in E/C/k/O with Clover "Inject Kexts" = YES. (Solved - no further work required) Laptop does not sleep when closing lid.  Solution appears to be a combination of adding Notify (LID0) code to Method (BTNV) and adding Device (PNLF) in the DSDT. I am using the same EFI for High Sierra 10.13.6, Mojave 10.14.6 and Catalina 10.15.3 and it works in all three macOSes. (No solution yet) No SD Card Slot (had to remove VoodooSDHC.kext) - I read somewhere that there is a solution that does not require any kexts (just a DSDT edit).  Haven't yet implemented this fix. (Not a problem that needs to be solved - leaving for historical purposes.  I am running Catalina without this.) - IOHWControl does not load under GFX0 (as observed in IORegistryExplorer).  Solution (if it needs to be solved) is to install AppleHWSensor.kext from a DosDude-patched Mojave /S/L/E in Catalina's /L/E.  Copy and install your own or use the kext attached to this post. (Solved - no further work required) Wi-Fi connection is delayed until a minute or so after boot - Use VoodooHDA and NOT AppleALC (Solved - no further work required) External USB ports do not work after waking from sleep (S3) - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Boot and shut-down time of Catalina is slower than Mojave - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Wi-Fi is not immediately available at OS startup - Upgrade Lilu.kext and replace BrcmFirmwareRepo.kext and BrcmPatchRAM2.kext (in /L/E) with latest BrcmBluetoothInjector.kext, BrcmFirmwareRepo.kext and BrcmPatchRAM3.kext. (Solved - no further work required) Laptop freezes on wake - Remove VoodooSDHC.kext from /Library/Extensions  
      Tips for Improved Performance (on this and other older systems)
      System Preferences > Spotlight > Search Results: Uncheck all options System Preferences > Spotlight > Privacy: Add all Volumes System Preferences > Accessibility > Display: Check "Reduce motion" System Preferences > Accessibility > Display: Check "Reduce transparency"  
      Other tips
      If your fan is always running and temps are good, try pressing Fn + z (I haven't noticed this issue for a while since I completed DSDT edits for Mojave, but keeping this here for historical purposes)  
      CLOVER Installation: Use these configuration options (Install Clover LEGACY - NOT UEFI)
      Install Clover in the ESP Boot Sectors Install boot0af in MBR Clover for BIOS (LEGACY - NOT UEFI) booting Clover EFI 64-bits SATA BIOS Drivers, 64-bit Recommended drivers FSInject File System drivers ApfsDriverLoader Install RC scripts on target volume Themes Choose your desired theme Install Clover Preference Pane After clicking "Continue", if prompted with "This Clover package is incompatible with this version of macOS," install anyway  
      After CLOVER installation is complete Copy the following from the attached E6410-Catalina.zip ACPI patched contents config.plist (change XX-MASKED-XX values to your own) kexts/Other (remove all other kext folders) Remove christmas and new year folders from themes (if present)  
      Credits
      Thanks to those who contributed to my Mojave solution and to the DosDude team (for the incredible macOS patchers), I think this Catalina installation was the easiest macOS installation that I have experienced (so far).  Many thanks to @Slice and his team for the incredible work on CLOVER and for continuing to support old legacy systems like this.  Also, thanks to @Mieze and @headkaze and others I'm sure for maintaining the Brcm kexts.  And finally, I still prefer to manually apply patches to the DSDTs in my systems.  CLOVER offers extensive patching functionality, but I'm old-school and like to have an error-free, fully-patched DSDT with a simple CLOVER config.plist.  I think that this manual DSDT patching approach (which required an extensive review and debugging of the original unpatched DSDT in this thread) is the reason that this Latitude E6410 is such a perfect MacBookPro6,2.  Thank you @RehabMan for being a great teacher and for always insisting on problem reporting files .
       
       

      AppleHWSensor.kext.zip
      gen_debug

      E6410 Catalina-5v1.zip
×