Summary: | 1st instance of mixer doesn't see the PCM control on Intel HDA | ||
---|---|---|---|
Product: | Sisyphus | Reporter: | Ivan Zakharyaschev <imz> |
Component: | libalsa | Assignee: | Michael Shigorin <mike> |
Status: | CLOSED WORKSFORME | QA Contact: | qa-sisyphus |
Severity: | major | ||
Priority: | P3 | CC: | aspsk, boris, boyarsh, erthad, ldv, mike, mithraen, oddity, rider, shrek, silicium, sin, vitty, vsu, zerg |
Version: | unstable | ||
Hardware: | all | ||
OS: | Linux |
Description
Ivan Zakharyaschev
2010-07-01 04:38:13 MSD
No, I was wrong that this appeared with nthe new kernel -- I have just checked it on the older one: the same thing is reproduced. This is not kmix-specific. The same thing happens with alsa-mixer: after system boot, if I login on a console (as root, or as a user) and start alsa-mixer, it doesn't have the PCM control. If I don't exit from this instance of alsa-mixer, and login on another console, and start another instance of alsa-mixer, it still doesn't have the PCM control. But after I exit an instance of alsa-mixer (or log in to KDE), the next instances of alsa-mixer (or of kmix), do have the PCM control. Currently, I use the 2.6.32-un-def-alt5 kernel, but this doesn't matter. $ rpm -qf "$(which alsamixer)" alsa-utils-1.0.23-alt1 $ rpm -qf "$(which alsamixer)" --requires | cut -d' ' --fields=1 | xargs rpm -q --whatprovides | sort -u предупреждение: ни один из пакетов не предоставляет rpmlib(PayloadIsLzma) dialog-1.1-alt2 glibc-core-2.11.1-alt2 glibc-pthread-2.11.1-alt2 libalsa-1.0.23-alt2 libncursesw-5.7-alt3 libtinfo-5.7-alt3 $ (In reply to comment #2) > after system boot, if I login on a console (as root, or as a user) and start > alsa-mixer, it doesn't have the PCM control. If I don't exit from this instance > of alsa-mixer, and login on another console, and start another instance of > alsa-mixer, it still doesn't have the PCM control. > > But after I exit an instance of alsa-mixer (or log in to KDE), the next > instances of alsa-mixer (or of kmix), do have the PCM control. The kmix started on KDE startup doesn't have the PCM control. But new instances of alsamixer, or a new kmix (after exiting from the initial one) do have the PCM control. (no idea) Building 1.0.24 userspace, please check whether it will behave the same. Such bugs should better be filed upstream right away, btw. Still weird and so far works for me (mobile i945 and all the way up to 3.0.6). I'm afraid it's up to you to try and diagnose that weirdness, probably by taking /proc/asound/ snapshots and comparing them either. |