Jaroslav Kysela writes: > On Thu, 28 Feb 2002, Roger E Critchlow Jr wrote: > > > Dale Harris writes: > > > On Thu, Feb 28, 2002 at 03:14:53PM -0800, Dale Harris elucidated: > > > > This is seems to be a recurring problem in the archives, but I didn't > > > > see a resolution off hand. My problem, shown in /proc/asound/sndstat: > > > > > > > > Audio devices: NOT ENABLED IN CONFIG > > > > > > > > > > > > > Okay, I now see Dave Andruczyk's post on alsa-devel: > > > > > > http://www.geocrawler.com/lists/3/SourceForge/12349/25/7947484/ > > > > > > about all the snd-card-xxxx changing to just snd-xxxx, so I guess the > > > question is now is why isn't snd-sbawe configuring the audio devices? > > > > > > > /proc/asound/sndstat reports the status of oss emulation. > > > > If you try an oss application and recheck /proc/asound/sndstat you'll > > see the unenabled devices magically appearing as required. > > > > Yes, it is a wee bit confusing. > > It's not confusing. If you have not loaded OSS emulation modules, then > sndstat reports that given interfaces are not available. It's clear, > isn't? >
It's confusing because it calls itself /proc/asound/sndstat, but it isn't _the_ status of _the_ sound system, it's the status of a subsystem. If it were called /proc/asound/oss-sndstat, or if it's contents clearly identified itself as the oss emulation status, or if there were another status device which itemized the status of alsa itself in the same way, then it would be less confusing. -- rec -- _______________________________________________ Alsa-user mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-user
