Contribute
Register

Multibeast 10.3.0 failed to install Realtek ALC, ALC1220

Status
Not open for further replies.
Joined
Dec 31, 2016
Messages
193
Motherboard
AsrockZ270M Extreme4
CPU
i5-7600K
Graphics
RX 560
Mac
  1. iMac
  2. Mac mini
Classic Mac
  1. Apple
Mobile Phone
  1. iOS
  1. macOS version: 10.13.5
  2. MultiBeast version: 10.3.0
  3. MultiBeast choices: Drivers, Audio, Realtek ALCxxx, ALC1220
  4. Destination files system type, HFS+ or APFS: APFS
  5. MultiBeast.log contents:
06/05/18 16:40:25 - Starting MultiBeast 10.3.0-20180516
06/05/18 16:41:50 - Mounting EFI
06/05/18 16:41:50 - Installing 'Drivers > Audio > Realtek ALCxxx > 100 / 200 / 300 Series Audio Support'
06/05/18 16:41:52 - Finished Installing.
06/05/18 16:41:52 - Releasing XPC connection.
06/05/18 16:50:59 - Starting MultiBeast 10.3.0-20180516
06/05/18 16:51:28 - Mounting EFI
06/05/18 16:51:29 - Installing 'Drivers > Audio > Realtek ALCxxx > ALC1220'
06/05/18 16:51:30 - Install of '/private/var/folders/p_/t9k_pbkx7qq3nds2r_wt91kh0000gp/T/AppTranslocation/59FC56AA-A5FC-4846-A0B6-87C5620796E3/d/MultiBeast.app/Contents/Resources/Clover-ALC1220.pkg' failed.
'installer: Package name is Clover ALC1220
installer: Installing at base path /
installer: The install failed (The Installer encountered an error that caused the installation to fail. Contact the software manufacturer for assistance.)
'. Exiting.
6. install.log contents for the choices that you are installing: No install log
 
Without an install.log it is impossible to determine why the install failed.
Hi -- I'm a newbie in this area, but I found the Multibeast log in ~/Library/Logs/Multibeast log. Previously I couldn't find Install.log content for the time of the Multibeast log, but now there is a lot there. I really have no idea where the reliant content starts, but I have taken a chunk that could apply. I'm not sure where the relevant content ends. I've inserted a line of dashes where I think the end is. Below that I think was for later activity. So the attached text file is the portion of the install log.
I hope this is OK.
 

Attachments

  • 18_0605-Install.log extract.txt
    25.3 KB · Views: 250
Error:

Domain=PKInstallErrorDomain Code=120 "An unexpected error occurred while moving files to the final destination."

This is most likely due to either a permissions error or using the wrong SIP setting.
 
Error:

Domain=PKInstallErrorDomain Code=120 "An unexpected error occurred while moving files to the final destination."

This is most likely due to either a permissions error or using the wrong SIP setting.
Thanks very much for all of your work, MacMan. As the attached screenshot shows, I have the Booter and CSR config settings in Clover Configurator as recommended. I can also set "No SIP" in Clover boot options, and use csrutil in Recovery mode to disable SIP, but it doesn't survive the reboot. csrutil status shows enabled.

I know this is off-topic, but I want to explain. I read that CSR settings are not stored in macOS but in NVRAM, so I wonder if the Clover r4509 Emulate NVRAM has an issue. This SIP problem is what stops audio_cloverALC-130 from executing.
 

Attachments

  • 18_0607-Clover Rt Variable.png
    18_0607-Clover Rt Variable.png
    176.1 KB · Views: 221
  • 18_0607-csruitil status.png
    18_0607-csruitil status.png
    29.4 KB · Views: 219
Error:

Domain=PKInstallErrorDomain Code=120 "An unexpected error occurred while moving files to the final destination."

This is most likely due to either a permissions error or using the wrong SIP setting.
Hi MacMan -- another thought: for HS 10.13.5, I changed to apfs. Could that be a factor?
 
Only if the conversion wasn't' 100% successful.
Even though I deleted all emulation-related drivers etc. from my High Sierra build, and the test detailed in the Native NVRAM available? forum indicates my motherboard (Asrock Z270M Extreme4) has NVRAM, and a Recover mode csrutil disable was accepted, after reboot csrutil shows SIP is enabled. Because SIP is enabled I can't install the audio_cloverALC-130 command that I previously used to get audio working.

So the audio issue is not worth the time and frustration. I've ordered a USB audio device.
 
Status
Not open for further replies.
Back
Top