08-29-2020, 11:41 AM
(08-28-2020, 09:11 PM)--frofro Wrote: I'm having the same problem. I created a alsa config file-after adding the headphone option- and a script to load the config. My issue now is trying to get the script to run on startup... I've tried adding it as a service and adding to the the start up menu. Nothing.I'd gotten as far as using``sudo alsactl store`` (with ``alsamixer`` still open, after I'd made the change I needed) to save the settings to /var/lib/alsa/asound.state BUT... while changes were stored to that file they were not automatically picked up by alsa the next time I rebooted. I had to run ``sudo alsactl restore`` to actually get the changes to register with alsa again. This didn't seem to be much better than simply opening alsamixer and making the changes manually (perhaps with a startup script: ``konsole -e alsamixer``).
the alsa config was generated using
sudo alsactl --file /home/frofro/Desktop/foostore store
and the script to load it
#!/bin/bash
alsactl --file /home/frofro/Desktop/foostore restore
if I run my bash script from the command line, the audio fix work. I just can't get it to run on startup. I'll update if I get it working
Maintaining a separate config file seems like a better solution, if it is possible to get it to work automatically, but it feels like there's something we're still missing.