Volume seting doesn't survive reboot

89c51 · 2013-10-30 06:51:05

However if i log out and login again it works as expected. On reboots it stores the last volume change before a logout no matter if i changed it.

$ systemctl status alsa-restore.service alsa-state.service alsa-store.service 
alsa-restore.service - Restore Sound Card State
   Loaded: loaded (/usr/lib/systemd/system/alsa-restore.service; static)
   Active: inactive (dead) since Wed 2013-10-30 08:45:53 EET; 1min 50s ago
  Process: 320 ExecStart=/usr/bin/alsactl restore (code=exited, status=19)
 Main PID: 320 (code=exited, status=19)


alsa-state.service - Manage Sound Card State (restore and store)
   Loaded: loaded (/usr/lib/systemd/system/alsa-state.service; static)
   Active: inactive (dead)
           start condition failed at Wed 2013-10-30 08:45:53 EET; 1min 50s ago
           ConditionPathExists=/etc/alsa/state-daemon.conf was not met


alsa-store.service - Store Sound Card State
   Loaded: loaded (/usr/lib/systemd/system/alsa-store.service; static)
   Active: inactive (dead)

Using E17 in case its important.

jasonwryan · 2013-10-30 06:58:41

The exit status of alsa-restore should be 0/SUCCESS - look into the journal and see if there is more information about why it is failing (19).

Do you have an active session?

89c51 · 2013-10-30 07:17:23

The only thing related to alsa in the journal is this.

$ sudo journalctl -b | grep alsa
Oct 30 08:45:54 mainland alsactl[320]: /usr/bin/alsactl: load_state:1729: No soundcards found...

What you mean with active session??

jasonwryan · 2013-10-30 07:36:06

See https://wiki.archlinux.org/index.php/Ge … ermissions

Related: https://bugs.archlinux.org/task/31163

89c51 · 2013-10-30 07:53:39

$ loginctl show-session $XDG_SESSION_ID
Id=1
Timestamp=Wed 2013-10-30 08:45:59 EET
TimestampMonotonic=7732613
VTNr=1
TTY=tty1
Display=:0
Remote=no
Service=lxdm
Scope=session-1.scope
Leader=402
Audit=1
Type=x11
Class=user
Active=yes
State=active
IdleHint=no
IdleSinceHint=0
IdleSinceHintMonotonic=0
Name=userzzz

Probably hitting the bug you linked. Nothing more to do.

Jellicent · 2013-10-30 08:36:18

Maybe this is totally out of the blue, but have you tried

# alsactl store

?

89c51 · 2013-10-30 11:54:46

Thats what i get.

alsactl store
alsactl: state_lock:121: file /var/lib/alsa/asound.state lock error: File exists
alsactl: state_lock:121: file /var/lib/alsa/asound.state unlock error: File exists

89c51 · 2013-10-30 13:27:38

$ sudo journalctl -b | grep -i sound

Oct 30 08:45:53 mainland systemd[1]: Started Manage Sound Card State (restore and store).
Oct 30 08:45:53 mainland systemd[1]: Starting Restore Sound Card State...
Oct 30 08:45:53 mainland systemd[1]: Started Restore Sound Card State.
Oct 30 08:45:54 mainland alsactl[320]: /usr/bin/alsactl: load_state:1729: No soundcards found...
Oct 30 08:45:54 mainland kernel: input: HDA Intel PCH Front Headphone as /devices/pci0000:00/0000:00:1b.0/sound/card0/input4
Oct 30 08:45:54 mainland kernel: input: HDA Intel PCH Line Out CLFE as /devices/pci0000:00/0000:00:1b.0/sound/card0/input5
Oct 30 08:45:54 mainland kernel: input: HDA Intel PCH Line Out Surround as /devices/pci0000:00/0000:00:1b.0/sound/card0/input6
Oct 30 08:45:54 mainland kernel: input: HDA Intel PCH Line Out Front as /devices/pci0000:00/0000:00:1b.0/sound/card0/input7
Oct 30 08:45:54 mainland kernel: input: HDA Intel PCH Line as /devices/pci0000:00/0000:00:1b.0/sound/card0/input8
Oct 30 08:45:54 mainland kernel: input: HDA Intel PCH Rear Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input9
Oct 30 08:45:54 mainland kernel: input: HDA Intel PCH Front Mic as /devices/pci0000:00/0000:00:1b.0/sound/card0/input10
Oct 30 08:45:54 mainland systemd[1]: Starting Sound Card.
Oct 30 08:45:54 mainland systemd[1]: Reached target Sound Card.
Oct 30 08:45:54 mainland kernel: input: HD-Audio Generic HDMI/DP,pcm=3 as /devices/pci0000:00/0000:00:01.0/0000:01:00.1/sound/card1/input11
Oct 30 08:45:59 mainland systemd[403]: Stopped target Sound Card.

Just a question. Shouldn't the card restore functionality start after the sound card has started.

Jellicent · 2013-10-30 13:29:51

89c51 wrote:

Thats what i get.

alsactl store
alsactl: state_lock:121: file /var/lib/alsa/asound.state lock error: File exists
alsactl: state_lock:121: file /var/lib/alsa/asound.state unlock error: File exists

You should actually do it as root.
That's why there's a # there.

Well, I'm assuming you're not running the cmd as root since I only get that exact error as normal user.

89c51 · 2013-10-30 14:54:12

Yeah sorry missed that.

Nothing weird to report when i run it as root.

Jellicent · 2013-10-30 15:32:30

89c51 wrote:

Yeah sorry missed that.
Nothing weird to report when i run it as root.

Well, does it work now?

89c51 · 2013-10-31 06:48:07

Nope. It still doesn't survive the reboot. Same behavior as in the first post. And it shouldn't require me to do it manually.

Arch Linux

#1 2013-10-30 06:51:05

Volume seting doesn't survive reboot

#2 2013-10-30 06:58:41

Re: Volume seting doesn't survive reboot

#3 2013-10-30 07:17:23

Re: Volume seting doesn't survive reboot

#4 2013-10-30 07:36:06

Re: Volume seting doesn't survive reboot

#5 2013-10-30 07:53:39

Re: Volume seting doesn't survive reboot

#6 2013-10-30 08:36:18

Re: Volume seting doesn't survive reboot

#7 2013-10-30 11:54:46

Re: Volume seting doesn't survive reboot

#8 2013-10-30 13:27:38

Re: Volume seting doesn't survive reboot

#9 2013-10-30 13:29:51

Re: Volume seting doesn't survive reboot

#10 2013-10-30 14:54:12

Re: Volume seting doesn't survive reboot

#11 2013-10-30 15:32:30

Re: Volume seting doesn't survive reboot

#12 2013-10-31 06:48:07

Re: Volume seting doesn't survive reboot

Board footer