Just a little query, as I know you use ubuntu.

I'm trying to help someone with a sound problem on Ubuntu. he can't access 
alsamixer on the CLI.

Ironically on booting my Kubuntu install (Dapper) , I too have no access to 
alsamixer, and consequently no sounds.

I've had problems with the asound.state file before on various distros, so 
renamed the one in /var/lib/alsa to asound.state.old. Then I shut the machine 
down, and booted up again. Now I have access to alsamixer on the CLI again, 
and sounds are working.

The question is though. What has happened to the asound.state file, which is 
apparently being used for the various settings on alsamixer. I can no longer 
find an asound.state file. Looking in /var/lib/alsa, all I find there is the 
asound.state file, that I renamed to asound.state.old, and there is nothing 
in the /etc directory where the asound.state file is on fedora distros.

Any ideas where I can find the asound.state file on Kubuntu/Ubuntu

btw. I have been experimenting on various distros with upgrading the alsa 
driver, just to see how easy it is. The alsa driver on Kubuntu Dapper is 
1.0.10, and I upgraded the alsa driver for one of the kernels on Dapper to 
1.0.15. I'm not sure if I may have created problems here, but is just a bit 
more info.

Mind you, I've also upgraded the alsa driver on other distros, and havn't had 
any sound problems after doing so.

Thanks for any suggestions.

Nigel.

-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Alsa-user mailing list
Alsa-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/alsa-user

Reply via email to