- Joined
- Jul 24, 2015
- Messages
- 2,191
- Motherboard
- MSI H81i
- CPU
- i5-4570
- Graphics
- RX 580
You might be right.Maybe instead of adding the file resetting the NVRAM would have worked as well.
You might be right.Maybe instead of adding the file resetting the NVRAM would have worked as well.
You might be right.
Weird... I updated to the supplemental update of High Sierra, and ended up in a boot-loop. I booted from my backup partition, and tried installing the updated Nvidia Driver on the updated system by using Pacifist. Still boot-loop.
Then I was going to remove the Nvidia driver, and just access the system through screen sharing(enabled screen sharing remotely through terminal), but to my surprise, after I removed the NVDAStartup.kext my system booted and was working perfectly(including full graphics support). So it seems the NVDAStartup.kext is no longer necessary.
So in short:
PROBLEM: Bootloop
SOLUTION: Remove NVDAStartup.kext
The driver configuration store isn't user visible at run time e.g with the nvram command. Some information form here:So when I remove EmuVariableUefi-64.efi I can no longer boot successfully. The system reboots when the progress bar is at 60%. In verbose mode it's so fast that I can't see what the last output is.
Maybe this is related to the nvda_drv NVRAM setting. Anyway, everything seems to work fine with EmuVariableUefi installed but not the RC scripts. I never installed them and the NVRAM still saves correctly across boots. I can see this because the computer name is saved correctly. Not sure what is going on here, but as long as it works it's fine for me.
Apple's EFI driver implementing this protocol, "AAPL,PathProperties", is a per-device key/value store which is populated by other EFI drivers. On macOS, these device properties are retrieved by the bootloader /usr/standalone/i386/boot.efi. The extension AppleACPIPlatform.kext subsequently merges them into the I/O Kit registry (see ioreg(8)) where they can be queried by other kernel extensions and user space.
These device properties contain vital information which cannot be obtained any other way (e.g. Thunderbolt Device ROM). EFI drivers also use them to communicate the current device state so that OS drivers can pick up where EFI drivers left (e.g. GPU mode setting).
What do the rc.scripts exactly do? Save NVRAM on shutdown and load them on boot?
This thread not the best place to search help how to install High Sierra properly on your comp.
Thanks, I just put that EmuVariableUEFI-64.efi in my Clover and It's working well now!So when I remove EmuVariableUefi-64.efi I can no longer boot successfully. The system reboots when the progress bar is at 60%. In verbose mode it's so fast that I can't see what the last output is.
Maybe this is related to the nvda_drv NVRAM setting. Anyway, everything seems to work fine with EmuVariableUefi installed but not the RC scripts. I never installed them and the NVRAM still saves correctly across boots. I can see this because the computer name is saved correctly. Not sure what is going on here, but as long as it works it's fine for me.
finally got it to work after 2 weeks of hardship. someone please help me with audio. i did fresh installation and cant get audio to work. need help please.
motherboard: Asus z170 pro gaming aura
thx
Please refer to this forum thread instead: https://www.tonymacx86.com/threads/audio-realtek-alc-applehda-guide.143757/
Basic procedure:
- Install SSDT-HDEF-HDAS-1.aml to make onboard sound discoverable (for 1xx-series boards)
- Restart
- Disable SIP
- Run toleda's cloverALC script to add patches for AppleHDA.kext
- Restart
- Run toleda's cloverALC_HDMI script to intsall NVIDIA-specific SSDT file
- Restart
- Onboard sound and GPU sound should now work
- Leave SIP disabled, otherwise sound doesn't work anymore
- Restart