> > As stated the solution for me was to update alsa-utils and alsa-libs
> > which fixed the issues I was getting - I found that if one of the
> > 'controls' (15, I think?) was invalid at boot, all the volume settings
> > in alsamixer got set to '0' (i.e. mute/turned off) - no sound.
>
> Such a problem is usually because of init script rather alsa-lib
> version. It should call alsactl with -F option.
I would agree - but I only have one asound.state file, and also doing
the upgrade to said alsa utils and libs *fixed* it...
On my system at least something was going awry.
Nick
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]