On Sun, October 9, 2005 10:08 pm, Christopher Sawtell said: >> >> what is the alsa daemon? Doesn't exist afaik! There is an init script on >> gentoo, and presumably other systems too, but it doesn't start a daemon, >> it loads kernel modules. > So it does. I misinterpreted the lines at the start of the alsasound file > in /etc/init.d/ > # alsasound This shell script takes care of starting and > stopping > # the ALSA sound driver. > > To me that would appear to indicate a daemon. Thanks for putting me > straight. > >> so, which alsa packages did you install? and how did you install them?
Sorry that question was for the OP. And here is why I asked: the alsa drivers were moved into the kernel for 2.6. However they are still developed separately. There are therefore two ways to get alsa sound card drivers onto your system: use the drivers in the kernel, or use the alsa-drivers package. The latter uses the separately developed drivers (which are sometimes a little more advanced, stuff seems to get in there before the kernel). If *your* kernel has the alsa sound drivers compiled in, or as modules, then installing alsa-drivers *will* break your sound. Now I don't have an installed ubuntu system here at home, but I do have a ubuntu x86 live cd. It has sound going (in vmware no less!) and definitely uses a driver from the kernel, not from alsa-drivers. alsa-drivers is not even installed. Based on that I believe that installing alsa-drivers would be a mistake on an installed ubuntu system, unless you recompile the kernel to get rid of the kernel based drivers. Therefore when MAtthew says he has kernel2.6.10-5-386, alsa driver 1.0.9b I am suspicious that he has installed alsa-driver and mucked up the whole sound thing. So Matthew let us know what you have done :-)
