Most times when I get something like that it has to do with the /dev/'s not being present. Could be that udev isn't running on your box. Or isn't configured for alsa. It could also be something else like snd-pcm-oss not auto loading. And it's friends, snd-mixer-oss snd-seq-oss. Basically cannot open means some sort of missing something or bad permissions. Is the user in the audio group? Do the /dev/audio* and /dev/dsp* stuff exist? In the old days we'd run ./snddevices from the alsa-driver source tree. But that's probably not the solution of choice these days. # /etc/init.d/alsa-utils restart # /etc/init.d/udev restart # groups <user> # grep -i "audio" /etc/group lsmod, dmesg, and all of the other stuff that's probably covered by that alsa-info.sh script thing. - James On 2/11/11, Jim Lesurf <jcgl@xxxxxxxxxxxxxxx> wrote: > In article > <AANLkTikA=hHDEy3pCsamVvgye7u9=_4PQqw_PScjbSKV@xxxxxxxxxxxxxx>, > Marcin Szyniszewski <mszynisz@xxxxxxxxx> wrote: >> > Is the file /usr/bin/alsamixer present, or /sbin/alsa ? >> > >> > Or the /usr/share/alsa directory? >> > >> > You should have these or equivalents IIUC. > >> /usr/bin/alsamixer is present and gives: cannot open mixer: No such file >> or directory > > Did you issue alsamixer as the command or the full pathname? If the former, > maybe something is wrong with your path/environment setup. > > Afraid I don't know what the problem is, so I can only suggest some ideas > and diagnostics to check. > > I am wondering if your OS install hasn't actually loaded the modules > correctly for your hardware. > > Try the command 'lsmod' to list the modules that are loaded. If the list is > too long use 'lsmod | grep snd' to just list the ones that have 'snd' in > their names. > > You can then use modinfo <module name> to check details of each module. > > Or modprobe (with care!) to alter what is loaded. > > Do you have another sound system like Pulse active? if so, that may be > interfering with the direct use of ALSA. > > You could also put a simple redefinition of the ALSA default into an > .asoundrc file and see if that can be made to work with aplay. But from > what you have said I have doubts about that. > > You might also consider trying to install the latest version of ALSA in > case what you have isn't suitable for your hardware or is furtled in some > way. > > Sorry I can't be more help. But I hope the above may be useful. > > Slainte, > > Jim > > -- > Electronics http://www.st-and.ac.uk/~www_pa/Scots_Guide/intro/electron.htm > Audio Misc http://www.audiomisc.co.uk/index.html > Armstrong Audio http://www.audiomisc.co.uk/Armstrong/armstrong.html > > ------------------------------------------------------------------------------ > The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: > Pinpoint memory and threading errors before they happen. > Find and fix more than 250 security defects in the development cycle. > Locate bottlenecks in serial and parallel code that limit performance. > http://p.sf.net/sfu/intel-dev2devfeb > _______________________________________________ > Alsa-user mailing list > Alsa-user@xxxxxxxxxxxxxxxxxxxxx > https://lists.sourceforge.net/lists/listinfo/alsa-user > ------------------------------------------------------------------------------ The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE: Pinpoint memory and threading errors before they happen. Find and fix more than 250 security defects in the development cycle. Locate bottlenecks in serial and parallel code that limit performance. http://p.sf.net/sfu/intel-dev2devfeb _______________________________________________ Alsa-user mailing list Alsa-user@xxxxxxxxxxxxxxxxxxxxx https://lists.sourceforge.net/lists/listinfo/alsa-user
