You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on May 4, 2020. It is now read-only.
I would prefer to keep this project as separate from Clover as possible, but the BootChimeDxe driver probably could be changed to use Clover's NVRAM variables if the AudioPkg ones don't exist.
right. BootChimeDxe need it.
also i suggest one more.
BootChimeDxe volume size is max.
i always listen 100% sound volume. my laptop demaged speaker with noise.
can you reduce default volume size?
also if there are no nvram(ex. clover.sounddevice or device), can you consider no gernerate sound like clover setting in BootChimeDxe?
so, if user dont't want bootsound with BootChimeDxe in Driver64UEFI folder, just dont need remove file, we just clear nvram with F11 key in CLOVER GUI
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
audiopkg use this nvrams
{ L"Device", &gBootChimeVendorVariableGuid }, { L"Volume", &gBootChimeVendorVariableGuid },
{ L"Index", &gBootChimeVendorVariableGuid }
to set, we have to enter shell to set nvram to use audiopkg.
now clover can set nvram in gui.
can we consider this nvram without command in shell?
thanks in advance
The text was updated successfully, but these errors were encountered: