Ventura on an HP ProDesk 600 G3 Desktop Mini - Real-Time Clock Power Loss (005)

[common]

Greetings to all.

I'm trying to install macOS Ventura on an HP ProDesk 600 G3 Desktop Mini. Initially, it didn't even get to the start of the installation.

After adding SSDT-AWAC-DISABLE.aml or SSDT-RTC0.aml, it became possible to use the disk utility and start installing macOS.

After copying the files to the selected disk, and the first reboot, the BIOS displays the error message Real-Time Clock Power Loss (005). When macos installer is selected, a cyclic reboot occurs.

Adding a patch didn't do anything. The BIOS is installed last, wifi and bluetooth are disabled. In config.plist, I excluded kexts for wifi and bluetooth.

How can this be defeated?

CPU - i3-7300

GPU: Intel HD Graphics 630

RAM: DDR4 8GB 2133 MHz

 

EFI

https://disk.yandex.ru/d/xWN0fKcQd3P_Bw

patch.zip

err 005.zip

Edited November 6 by common

[MaLd0n]

https://github.com/acidanthera/RTCMemoryFixup

[common]

Thank you.

This fixed the Real-Time Clock Power Loss (005) error.

But later macosinstaller could only be started by installing SecureBootModel - Disabled.

 

During the installation process, the message "basesystem dmg could not be copied to" "appeared because there is not enough free space". I used two ssd drives, but realized that the problem wasn't with the drives.

After replacing the DmgLoading parameter with Any, the message "operation could not be completed (com.apple.DiskManagement.disenter, error -119930878)".

I take it this is a problem with access restrictions?

The installation is complete.

The parameters Misc-Security-

-DmgLoading has been replaced with Signed,

-ExposeSensitiveData has been replaced with 6,

-SecureBootModel has been replaced with Disabled.

 

But during the setup process, everything is very slow, both the mouse and the keyboard. This may be the result of applying RTCMemoryFixup with rtcfx_exclude=00-FF?

I have not yet identified the specific areas of the RTC.

Edited November 11 by common

[MaLd0n]

Use rtcfx_exclude=00-FF If solve start procedure with RTCMemoryFixup