-
-
Save 0xbb/ae298e2798e1c06d0753 to your computer and use it in GitHub Desktop.
#!/bin/bash | |
printf "\x07\x00\x00\x00\x00" > /sys/firmware/efi/efivars/SystemAudioVolume-7c436110-ab2a-4bbb-a880-fe41995c9f82 |
If anyone needs :)
#!/usr/bin/bash
# Mute MacBook Chime
## Make "chime" value mutable
sudo chattr -i /sys/firmware/efi/efivars/SystemAudioVolume-7c436110-ab2a-4bbb-a880-fe41995c9f82
## Change "chime" value to "muted"
sudo printf "\x07\x00\x00\x00\x00" > /sys/firmware/efi/efivars/SystemAudioVolume-7c436110-ab2a-4bbb-a880-fe41995c9f82
## Make "chime" value immutable again
sudo chattr +i /sys/firmware/efi/efivars/SystemAudioVolume-7c436110-ab2a-4bbb-a880-fe41995c9f82
printf "\n🎉️🔇️ Now you don't have startup chime anymore!"
Also, anyone knows is there a way to enable it back? (just want to know)
Can't find that path while running Debian on a Mac Mini a1347. Perhaps because I'm not even using UEFI and only MBR boot with grub?
I found that I had to specifically install efivar
before the SystemAudioVolume variable was available. I also had to run @daudix-UFO 's script as root (via sudo su
) as anything done as sudo
didn't work.
@daudix-UFO to reenable it, just clear the nvram. Cmd + Options + P + R at the same time right on boot. Hold it for 20 seconds, the mac will reboot a couple times. And now you have that startling sound again 🤣. At least this is what i got with a 2012 iMac.
I have a MacBook9,1
and a MacBookPro14,1
-- and on both of these models I needed to set the hex value to 80
Setting it to 00
did not work. I'm surprised no one has posted anything on this topic before.....
printf "\x07\x00\x00\x00\x80" > SystemAudioVolume-7c436110-ab2a-4bbb-a880-fe41995c9f82
# probably wasn't needed, but changed the value of SystemAudioVolumeDB to match SystemAudioVolume
printf "\x07\x00\x00\x00\x80" > SystemAudioVolumeDB-7c436110-ab2a-4bbb-a880-fe41995c9f82
it only worked when i use yours @leifliddy 🫡,thanks
on MacBookPro13,1
i didn't need to overwrite the SystemAudioVolumeDB-*
one
try just doing su before doing printf
its a pretty sensitive directory so it could be that your distro is being a bit extra cautious?