Member Avatar for gordon52

Every time that I start my computer I have to run "alsaconf" to get my sound to work.
How do I get my system to keep this sound setting?

  • 2 Contributors
  • 2 Replies
  • 127 Views
  • 2 Weeks Discussion Span
  • Latest Post Latest Post by gordon52

Dani AI

Generated

correctly pointed out that the mixer state must be saved, but since still sees the problem after doing that, the fault is most often one of three things: the saved state file is never restored at boot, the state file is being written for a different card index, or a desktop/login component is changing mixer channels after restore. The steps below cover quick checks and fixes specific to a Suse 9.3 setup.

Common quick checks (run as root or inspect from a console before X starts):

ls -l /var/lib/alsa/asound.state
cat /proc/asound/cards
alsactl restore        # test restoring the saved state manually
alsamixer              # check Master/PCM channels are unmuted

If the state file exists and a manual restore works, confirm that the ALSA restore step is actually run during boot. On Suse 9.x the ALSA init script should be enabled in the default runlevel (use YaST runlevel editor or look for an /etc/init.d/alsasound script). As a reliable fallback, a restore command placed in Suse's boot-local script (for example /etc/init.d/boot.local) will run late in boot and ensure mixers are applied after other init jobs.

If the state is present but values reappear wrong, compare card listings before saving and after a reboot using the /proc/asound/cards output. If indexes shift, pin the card by setting module options (for example, giving the module a fixed index in an /etc/modprobe.d/ file). Also verify that desktop mixer/autostart apps are not changing volumes at login; these can overwrite the restored ALSA state. Typical debug data to collect for further diagnosis: the state-file listing, the /proc/asound/cards output after boot, and the ALSA init script (or boot.local) content used to restore settings.

Recommended Answers

All 2 Replies

Member Avatar for frrossk

After running alsaconf, you have to run alsactl store as root, to save your settings.

Member Avatar for gordon52

After running alsaconf, you have to run alsactl store as root, to save your settings.

Still did not solve my problem. :sad:

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.