FS#45027 - [linux] alsa does not (re)store its state any more

Attached to Project: Arch Linux
Opened by Stefan Tatschner (rumpelsepp) - Wednesday, 20 May 2015, 13:20 GMT
Last edited by Doug Newgard (Scimmia) - Sunday, 15 October 2017, 14:15 GMT
Task Type Bug Report
Category Kernel
Status Closed
Assigned To Tobias Powalowski (tpowa)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 1
Private No

Details

Since kernel 4.0 my alsa does not restore its state on bootup any more:

$ systemctl status alsa-restore.service
● alsa-restore.service - Restore Sound Card State
Loaded: loaded (/usr/lib/systemd/system/alsa-restore.service; static; vendor preset: disabled)
Active: inactive (dead) since Mi 2015-05-20 15:11:41 CEST; 7min ago
Process: 429 ExecStart=/usr/bin/alsactl restore (code=exited, status=99)
Main PID: 429 (code=exited, status=99)

Mai 20 15:11:41 alderaan systemd[1]: Starting Restore Sound Card State...
Mai 20 15:11:41 alderaan alsactl[429]: No state is present for card
Mai 20 15:11:41 alderaan alsactl[429]: /usr/bin/alsactl: sysfs_init:48: sysfs path '/sys' is invalid
Mai 20 15:11:41 alderaan alsactl[429]: Found hardware: "HDA-Intel" "Intel PantherPoint HDMI" "HDA:10ec0887,10438445,00100302 HDA:80862806,80860101,00100000" "0x1043" "0x8445"
Mai 20 15:11:41 alderaan alsactl[429]: Hardware is initialized using a generic method
Mai 20 15:11:41 alderaan alsactl[429]: No state is present for card
Mai 20 15:11:41 alderaan systemd[1]: Started Restore Sound Card State.

There might be a prolem with that error "sysfs_init:48: sysfs path '/sys' is invalid".
This task depends upon

Closed by  Doug Newgard (Scimmia)
Sunday, 15 October 2017, 14:15 GMT
Reason for closing:  No response
Comment by Olivier Brunel (jjacky) - Friday, 11 March 2016, 19:12 GMT
So I've had a similar issue after upgrading kernel to 4.4.3, and after looking into it I have no idea where the bug is, but I might offer a hint to fix it.

Long story[1] short, your /var/lib/alsa/asound.state might not be "up-to-date" anymore, so:
mv /var/lib/alsa/asound.state{,-}
alsactl store
Then diff the 2 files and import back your settings, then `alsactl restore` should work again as expected. That is, assuming you're in a similar case as mine, of course. No guarantees.

[1] http://jjacky.com/2016-03-11-what-does-it-means-when-alsactl-restore-talks-invalid-sysfs/
Comment by mattia (nTia89) - Monday, 02 October 2017, 19:39 GMT
is this issue still valid?

Loading...