ALSA Sound Problem

Greg Kedrovsky <[email protected]>
Newsgroups gmane.comp.video.ogle.user
Organization Very little, but I try...
Message-ID <20040109224423.GF4658@gregkedro>
Ogle is failing when it reaches my sound driver. I get the first
Interpol type warning screen, and then it stops and exits. 

When in oglerc I have <alsa> <name>default</name> </alsa>, this is the
output I get: 

  ALSA lib pcm_hw.c:1055:(snd_pcm_hw_open) open /dev/snd/pcmC0D0p
  failed: Device or resource busy
  ERROR[ogle_audio]: Opening alsa pcm device 'default': Device or
  resource busy
  FATAL[ogle_audio]: failed opening the alsa audio driver at default


When I change "default" to "iec958" I get this: 

  No accelerated IMDCT transform found
  ALSA lib pcm.c:1785:(snd_pcm_open_conf) Invalid type for PCM iec958
  definition (id: iec958, value: cards.pcm.iec958)
  ERROR[ogle_audio]: Opening alsa pcm device 'iec958': Invalid argument
  FATAL[ogle_audio]: failed opening the alsa audio driver at iec958


Changing it to "iec958:AES0=0x2,AES1=0x82,AES2=0x0,AES3=0x2" results in:

  ALSA lib pcm.c:1785:(snd_pcm_open_conf) Invalid type for PCM
  iec958:AES0=0x2,AES1=0x82,AES2=0x0,AES3=0x2 definition (id: iec958,
  value: cards.pcm.iec958)
  ERROR[ogle_audio]: Opening alsa pcm device
  'iec958:AES0=0x2,AES1=0x82,AES2=0x0,AES3=0x2': Invalid argument
  FATAL[ogle_audio]: failed opening the alsa audio driver at
  iec958:AES0=0x2,AES1=0x82,AES2=0x0,AES3=0x2

When I check my alsa mixer, it shows the Item PCM using Chip ICEnsemble
ICE1232. Don't know if that means anything.

I have a VIA VT82C686B chipset (352 BGA). It is DirectSound AC97 Audio,
ACPI. I think it's a pretty common integrated soundcard chipset. So,
maybe someone out there knows what I'm doing wrong. 

I have a standard Slack 9.1 install.

Thanks.
-Greg

-- 
Mutt 1.4.1i on Slackware 9.1 Linux
Curridabat, San Jose, Costa Rica
http://www.greg-and-sue.com/screenshot.jpg
Yahoo Instant Messenger ID: gregkedro
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.