Re: Persisting muted state and volume across reboots

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 2018-06-24 11:35 AM, David Woodfall wrote:
On Sunday 24 June 2018 11:29,
info <info@xxxxxxxxxxxxx> put forth the proposition:
On 2018-06-24 11:24 AM, David Woodfall wrote:
On Sunday 24 June 2018 11:09,
info <info@xxxxxxxxxxxxx> put forth the proposition:
On 2018-06-24 11:06 AM, info wrote:
On 2018-06-24 10:51 AM, David Wood fall wrote:
On Sunday 24 June 2018 08:58,
info <info@xxxxxxxxxxxxx> put forth the proposition:
Good morning,


Whenever I boot a Fedora 26 box, the front headphone jack is muted
and volume
set to zero. No insertion or removal of the cable is detected.

I have to use alsamixer to un-mute and bring the volume up. Then I
use alsactl
store command and I can see that /var/lib/alsa/asound.state is
being updated:

           control.11 {
                   iface MIXER
                   name 'Headphone Playback Switch'
                   value.0 false
                   value.1 false
                   comment {
                           access 'read write'
                           type BOOLEAN
                           count 2
                   }
           }

changes to

           control.11 {
                   iface MIXER
                   name 'Headphone Playback Switch'
                   value.0 true
                   value.1 true
                   comment {
                           access 'read write'
                           type BOOLEAN
                           count 2
                   }
           }

But these changes are never persisted across reboots. What is
missing which is
preventing the mute state and volume from being restored at boot time?

I am connecting to the card 0:

[use0@localhost asound]$ cat cards
    0 [SB             ]: HDA-Intel - HDA ATI SB
                         HDA ATI SB at 0xfe024000 irq 16
    1 [HDMI           ]: HDA-Intel - HDA ATI HDMI
                         HDA ATI HDMI at 0xfdefc000 irq 32



Thank you

Alex
What does alsamixer look like after doing a 'store' followed by a
'restore'?

If it looks OK, then do you have a startup script that runs 'alsactl
restore' on boot? Or does that Fedora version use systemd?
Fedora uses systems. I don't know what scripts it has and where.
Sorry, hit Enter prematurely. I meant to add, that if I store and restore,
everything is Okay, but after a reboot the headphones jack is muted again and
volumes set to zero.
It sounds like the systemd alsa service isn't enabled, or it's
missing.

I'm not that familiar with systemd nor the correct name of the
service file it uses on fedora, but usually something like:

systemctl enable/disable <service name>

is used. So try

systemctl enable alsa

If the name is wrong or the service file is missing it will output an
error.

-Dave
I wish systemd was not a thing! Alas,
http://slackware.com ;)
I wish all my users have been migrated. Until then, is Fedora distro builder misusing ALSA? What do I need to tell them to either enable detection of attached front panel cables, or storing and properly restoring the volume and mute state? Saving is working, but then something overwrites the configuration during the shutdown or boot process. Unfortunately I cannot remove PulseAudio, and it is my understanding that all these systemd services are needed as crutches to let PA run.

Thank you!
Alex



------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Alsa-user mailing list
Alsa-user@xxxxxxxxxxxxxxxxxxxxx
https://lists.sourceforge.net/lists/listinfo/alsa-user



[Index of Archives]     [ALSA Devel]     [Linux Audio Users]     [Fedora Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [Yosemite Photos]     [KDE Users]     [Fedora Tools]

  Powered by Linux