On Sat, 12 Aug 2017 11:43:24 -0700 Ian Zimmerman wrote: > On 2017-08-12 13:21, John Covici wrote: > > > How about checking the various volumes rather than muting maybe some > > of them are 0 or rather some negative number or something? Also, you > > might delete the asound.state and let the system start over. Last > > resort, there is an alsa users mailing list. > > > > One other thought, get pulse audio out of the way and see if alsa is > > working. > > To clarify: it works for me (TM), I don't need a solution. I am just > curious because I don't heed the warning and it still works.
The warning is about old days when alsa init script loaded required kernel modules for your audio to work. These days kernel does the job well and it can autoload modules based on device IDs. So loading modules by alsa init script is no longer needed in general case and was removed. The warning is here is for the people with special setups (e.g. out of the tree modules) updating from very old systems. Best regards, Andrew Savchenko
pgp88LkgWGSge.pgp
Description: PGP signature
