If after suspending or waking from sleep in GhostBSD you lose audio functionality, it’s commonly because the sound daemon sndiod is not running anymore. Without sndiod, audio devices are not properly managed, which leads to no sound.
The Problem
When the system wakes up from suspend or sleep mode, sndiod may not restart automatically. Checking the status using:
service sndiod status
might show sndiod is not running. Attempting to start it with service sndiod start results in an error:
Cannot 'start' sndiod. Set sndiod_enable to YES in /etc/rc.conf or use 'onestart' instead of 'start'.
The Cause
This happens because the sndiod service on GhostBSD expects to be enabled in the system configuration before it can be started with the standard start command.
The Fix
To immediately start the sound daemon without enabling it for startup, use the onestart command:
sudo service sndiod onestart
This launches sndiod for the current session, restoring sound functionality without reboot.
To ensure sndiod starts automatically on every reboot (recommended), add the following line to your system configuration file /etc/rc.conf:
sndiod_enable="YES"
This way, the sound daemon will start with your system and avoid audio loss after suspend or reboot.
Summary
- Check
sndiodstatus withservice sndiod status. - Start sndiod temporarily with
sudo service sndiod onestart. - Enable automatic startup by adding
sndiod_enable="YES"to/etc/rc.conf. - Reboot for changes to fully apply.
Additional Notes
This fix addresses the most common audio issues post-suspend on GhostBSD. If other audio problems persist, you may want to explore mixer settings, user groups, or Linux compatibility libraries if you use software like Brave browser or SimpleScreenRecorder depending on Linux subsystems.