Your message dated Sat, 23 May 2026 15:37:32 +0200
with message-id <[email protected]>
and subject line Re: CONFIG_UEVENT_HELPER=n kernel confuses alsactl restore
has caused the Debian Bug report #800572,
regarding CONFIG_UEVENT_HELPER=n kernel confuses alsactl restore
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
800572: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=800572
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: alsa-utils
Version: 1.0.29-1
Severity: minor
I spotted this message when studying alsa-utils' udev rules:
# alsactl -E HOME=/run/alsa --file /dev/null restore 0
No state is present for card PCH
** alsactl: sysfs_init:48: sysfs path '/sys' is invalid
Found hardware: "HDA-Intel" "Realtek ALC662 rev3"
"HDA:10ec0662,10ec0662,00100300" "0x10ec" "0x0662"
Hardware is initialized using a generic method
No state is present for card PCH
# echo $?
99
This code assumes that a working /sys will have a /sys/kernel/uevent_helper.
This is not a safe assumption in custom 3.16+ kernels.
See also https://bugs.debian.org/752742
Also /usr/share/doc/systemd/README.gz calls it a "legacy" interface,
though I think it is still essential elsewhere (e.g. busybox mdev).
alsactl/init_sysfs.c-32-static int sysfs_init(void)
alsactl/init_sysfs.c:46: strlcat(sysfs_test,
"/kernel/uevent_helper", sizeof(sysfs_test));
alsactl/init_sysfs.c-47- if (access(sysfs_test, F_OK)) {
alsactl/init_sysfs.c-48- error("sysfs path '%s' is
invalid\n", sysfs_path);
alsactl/init_sysfs.c-49- return -errno;
alsactl/init_sysfs.c-50- }
I don't know what sysfs_init() *should* check for.
I don't know what alsactl does differently if it thinks /sys is working.
alsactl restore *does* change my mixer levels, so this might be a non-issue:
# echo 1 >/sys/class/sound/hdaudioC0D2/reconfig
# amixer >before
# alsactl -E HOME=/run/alsa --file /dev/null restore 0
[...]
# amixer >after
# cmp before after
before after differ: byte 164, line 5
--- End Message ---
--- Begin Message ---
Version: 1.2.15.2-1
Should be fixed by https://github.com/alsa-project/alsa-utils/pull/27
On Thu, 01 Oct 2015 11:26:23 +1000 "Trent W. Buck" <[email protected]>
wrote:
Package: alsa-utils
Version: 1.0.29-1
Severity: minor
I spotted this message when studying alsa-utils' udev rules:
# alsactl -E HOME=/run/alsa --file /dev/null restore 0
No state is present for card PCH
** alsactl: sysfs_init:48: sysfs path '/sys' is invalid
Found hardware: "HDA-Intel" "Realtek ALC662 rev3" "HDA:10ec0662,10ec0662,00100300"
"0x10ec" "0x0662"
Hardware is initialized using a generic method
No state is present for card PCH
# echo $?
99
This code assumes that a working /sys will have a /sys/kernel/uevent_helper.
This is not a safe assumption in custom 3.16+ kernels.
See also https://bugs.debian.org/752742
Also /usr/share/doc/systemd/README.gz calls it a "legacy" interface,
though I think it is still essential elsewhere (e.g. busybox mdev).
alsactl/init_sysfs.c-32-static int sysfs_init(void)
alsactl/init_sysfs.c:46: strlcat(sysfs_test,
"/kernel/uevent_helper", sizeof(sysfs_test));
alsactl/init_sysfs.c-47- if (access(sysfs_test, F_OK)) {
alsactl/init_sysfs.c-48- error("sysfs path '%s' is
invalid\n", sysfs_path);
alsactl/init_sysfs.c-49- return -errno;
alsactl/init_sysfs.c-50- }
I don't know what sysfs_init() *should* check for.
I don't know what alsactl does differently if it thinks /sys is working.
alsactl restore *does* change my mixer levels, so this might be a non-issue:
# echo 1 >/sys/class/sound/hdaudioC0D2/reconfig
# amixer >before
# alsactl -E HOME=/run/alsa --file /dev/null restore 0
[...]
# amixer >after
# cmp before after
before after differ: byte 164, line 5
OpenPGP_signature.asc
Description: OpenPGP digital signature
--- End Message ---
