[Abandoned] Help in understanding alsa and journalctl messages

d_fajardo · 2018-04-21 20:53:38

I've been trying to find a solution with my JACK setup not initialising properly on this page https://bbs.archlinux.org/viewtopic.php?id=236372.
I decided to investigate alsa and running journalctl -b|grep -i -e alsa -e sound -e snd, I get these messages:

Apr 21 17:47:07 TUF-Z270 systemd-udevd[377]: Process '/usr/bin/alsactl restore 1' failed with exit code 99.
Apr 21 17:47:08 TUF-Z270 systemd[1]: Starting Save/Restore Sound Card State...
Apr 21 17:47:08 TUF-Z270 alsactl[692]: /usr/bin/alsactl: set_control:1461: Cannot write control '2:0:0:Cambridge Audio Audio 2.0 Output Playback S:1' : Operation not permitted
Apr 21 17:47:08 TUF-Z270 alsactl[692]: /usr/bin/alsactl: set_control:1461: Cannot write control '2:0:0:Cambridge Audio Internal Clock Validity:0' : Operation not permitted
Apr 21 17:47:08 TUF-Z270 alsactl[692]: /usr/bin/alsactl: sysfs_init:48: sysfs path '/sys' is invalid
Apr 21 17:47:08 TUF-Z270 alsactl[692]: Found hardware: "HDA-Intel" "Realtek ALC1220" "HDA:10ec1168,10438724,00100003 HDA:8086280b,80860101,00100000" "0x1043" "0x8724"
Apr 21 17:47:08 TUF-Z270 alsactl[692]: Hardware is initialized using a generic method
Apr 21 17:47:08 TUF-Z270 alsactl[692]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #71 (No such file or directory)
Apr 21 17:47:08 TUF-Z270 alsactl[692]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #72 (No such file or directory)
Apr 21 17:47:08 TUF-Z270 alsactl[692]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #73 (No such file or directory)
Apr 21 17:47:08 TUF-Z270 alsactl[692]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #74 (No such file or directory)
Apr 21 17:47:08 TUF-Z270 alsactl[692]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #75 (No such file or directory)
Apr 21 17:47:08 TUF-Z270 alsactl[692]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #76 (No such file or directory)
Apr 21 17:47:08 TUF-Z270 alsactl[692]: /usr/bin/alsactl: set_control:1325: failed to obtain info for control #81 (No such file or directory)
Apr 21 17:47:08 TUF-Z270 systemd[1]: Started Save/Restore Sound Card State.
Apr 21 17:47:08 TUF-Z270 systemd[1]: Reached target Sound Card.
Apr 21 17:47:08 TUF-Z270 systemd[814]: Listening on Sound System.
Apr 21 17:47:09 TUF-Z270 systemd[825]: Listening on Sound System.
Apr 21 17:47:29 TUF-Z270 systemd[825]: Closed Sound System.

I'm trying to see if these messages have any bearing to my problem of initialising JACK as from the previous post.
Why is systemd-udevd failing restore?
What is the write control for the Cambridge Audio DAC?
Why failing to obtain info for control (I assume it's for the HDA-Intel or Realtek hardware)?

Last edited by d_fajardo (2018-04-30 11:57:08)

seth · 2018-04-21 21:18:21

Apr 21 17:47:08 TUF-Z270 alsactl[692]: /usr/bin/alsactl: sysfs_init:48: sysfs path '/sys' is invalid

The script is run before /sys is mounted?

d_fajardo · 2018-04-22 10:25:32

After this morning boot, I don't get these errors. Strange:

Apr 22 07:29:31 TUF-Z270 systemd[1]: Starting Save/Restore Sound Card State...
Apr 22 07:29:31 TUF-Z270 alsactl[683]: /usr/bin/alsactl: set_control:1461: Cannot write control '2:0:0:Cambridge Audio Audio 2.0 Output Playback S:1' : Operation not permitted
Apr 22 07:29:31 TUF-Z270 alsactl[683]: /usr/bin/alsactl: set_control:1461: Cannot write control '2:0:0:Cambridge Audio Internal Clock Validity:0' : Operation not permitted
Apr 22 07:29:31 TUF-Z270 systemd[1]: Started Save/Restore Sound Card State.
Apr 22 07:29:31 TUF-Z270 systemd[1]: Reached target Sound Card.
Apr 22 07:29:32 TUF-Z270 systemd[814]: Listening on Sound System.
Apr 22 07:29:33 TUF-Z270 systemd[825]: Listening on Sound System.
Apr 22 07:29:40 TUF-Z270 systemd[825]: Closed Sound System.
Apr 22 07:29:41 TUF-Z270 systemd[814]: Starting Sound Service...
Apr 22 07:29:42 TUF-Z270 systemd[814]: Started Sound Service.

I will explore further. My suspicion is it has to do with powering off the system perhaps some state not being written properly on exit.

d_fajardo · 2018-04-30 09:19:06

I haven't been able to replicate the error so I'll just close this thread.

seth · 2018-04-30 09:45:30

"[closed]" is only to be used by mods and locks the thread, please change that to sth. like "abandoned"

Also I'll once again point out that your script seems to run before /sys is mounted, so you should make that a requirement of the service.

Arch Linux

#1 2018-04-21 20:53:38

[Abandoned] Help in understanding alsa and journalctl messages

#2 2018-04-21 21:18:21

Re: [Abandoned] Help in understanding alsa and journalctl messages

#3 2018-04-22 10:25:32

Re: [Abandoned] Help in understanding alsa and journalctl messages

#4 2018-04-30 09:19:06

Re: [Abandoned] Help in understanding alsa and journalctl messages

#5 2018-04-30 09:45:30

Re: [Abandoned] Help in understanding alsa and journalctl messages

Board footer