On 25 April 2012, at 20:49, [email protected] wrote:
> ...
> Just a shot in the dark here, Stroller, but I once had a problem with using
> a mixer app (not alsamixer, which worked). I couldn't get it to start, and
> it kept on giving an error like your's above for alsamixer. The problem was
> that the kernel module, snd-mixer-oss was not loading by default, and when I
> loaded that module, all was good. HTH.
Thanks for the suggestion, but that didn't work.
I had to recompile my kernel for the new module, then reboot:
# alsamixer
cannot open mixer: Invalid argumentxmbc ~ # lsmod | grep -i snd_mix
# lsmod | grep -i snd
snd_hda_codec_hdmi 23052 1
snd_hda_codec_realtek 311454 1
snd_hda_intel 23052 1
snd_hda_codec 77939 3
snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel
snd_hwdep 6540 1 snd_hda_codec
snd_pcm 81875 4 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec
snd_timer 20907 1 snd_pcm
snd 64619 8
snd_hda_codec_hdmi,snd_hda_codec_realtek,snd_hda_intel,snd_hda_codec,snd_hwdep,snd_pcm,snd_timer
soundcore 6858 1 snd
snd_page_alloc 8021 2 snd_hda_intel,snd_pcm
# modprobe -v snd-mixer-oss
insmod /lib/modules/3.0.3/kernel/sound/core/oss/snd-mixer-oss.ko
# alsamixer
cannot open mixer: Invalid argument
#
I didn't really expect it to work, to be honest, as the difference seems to be
entirely in the file.
If I start the music playing in one console using `aplay -vv file.wav` (i.e.
the /etc/asound.conf file is present and tells aplay to use HDMI out) then move
to another terminal window and run `alsamixer` then I get this "cannot open
mixer: Invalid argument" error. If I then delete /etc/asound.conf, alsamixer
works perfectly and I can mute and unmute the S/PDIF.
Stroller.
