Re: [Alsa-user] ./snddevice woes - where are my /dev/snd's going?
Brought to you by:
perex
From: Paul W. <pw_...@sl...> - 2002-11-03 19:42:34
|
On Sat, Nov 02, 2002 at 06:38:35PM +1100, de|ire wrote: > before i forget! > > i should also say that i believe alsaound has never* not been running* simply because i can 'restart' it. > restarting alsasound produces the same alsactl error, on shutdown and start. > also, attempting to start it gives the "alsa driver already running" reply. > > yet funnily enough ps ax reveals no 'alsasound'? is this because it is not a *process* so much as a driver? "alsasound" is just a shell script that starts the driver. it mostly just runs modprobe to load the appropriate kernel modules. then it exits. To see if alsa's running: ls /proc/asound If alsa's running, that directory will exist, and will contain lots of informative files. If alsa's not running, it will not exist. Also, /sbin/lsmod should show you what modules are loaded. Which ones depends on the soundcards you have. Here's what I get when I start alsa on my laptop with a nm256 soundcard: $ /sbin/lsmod Module Size Used by Not tainted snd-nm256 57892 0 snd-ac97-codec 23984 0 [snd-nm256] snd-pcm 53216 0 [snd-nm256] snd-timer 9280 0 [snd-pcm] snd 23208 0 [snd-nm256 snd-ac97-codec snd-pcm snd-timer] -- Paul Winkler http://www.slinkp.com "Welcome to Muppet Labs, where the future is made - today!" |