Re: [Alsa-devel] aplay: pcm_write:1025: write error& SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy
On Mon, 2003-06-02 at 07:25, Takashi Iwai wrote: > just add the following line to the end of /etc/modules.conf: > > options snd-via82xx dxs_support=2 > > (or dxs_support=3) > > and run "/etc/init.d/alsasound restart". > > note that the option above is available only on the very recent ALSA > version. A solution is found! But I'd like to understand why the other failed: Wizard root # aplay -D hw:0,1 /home/mark/data/wave/seque~10.wav Playing WAVE '/home/mark/data/wave/seque~10.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Mono And I get sound just fine... Why is specifying the device required? As root I have no .asoundrc file, but as a user I do: pcm.via82xx { type hw card 0 } ctl.via82xx { type hw card 0 } Apparently my version is not new enough for your new option: Wizard modules.d # /etc/init.d/alsasound restart * Shutting down ALSA modules [ ok ] * Initialising ALSA * Starting sound driver: snd-via82xx Warning: ignoring dxs_support=2, no such parameter in this module Module snd-via82xx loaded, with warnings [ ok ] Wizard modules.d # And pcm2p did not exist... Wizard root # ls /proc/asound/card0/ ac97#0 ac97#0regs id pcm0c pcm0p pcm1c pcm1p Wizard root # Wizard root # aplay -v /home/mark/data/wave/seque~10.wav Playing WAVE '/home/mark/data/wave/seque~10.wav' : Signed 16 bit Little Endian, Rate 44100 Hz, Mono Plug PCM: Hardware PCM card 0 'VIA 8235' device 0 subdevice 0 Its setup is: stream : PLAYBACK access : RW_INTERLEAVED format : S16_LE subformat: STD channels : 1 rate : 44100 exact rate : 44100 (44100/1) msbits : 16 buffer_size : 22050 period_size : 4410 period_time : 10 tick_time: 1 tstamp_mode : NONE period_step : 1 sleep_min: 0 avail_min: 4410 xfer_align : 4410 start_threshold : 22050 stop_threshold : 22050 silence_threshold: 0 silence_size : 0 boundary : 1445068800 aplay: pcm_write:1025: write error: Input/output error Wizard root # --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
RE: [Alsa-devel] aplay: pcm_write:1025: write error & SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy
> > > > aplay hw:1 sound.wav??? > > please use -D option, for example, > > % aplay -D hw:0,1 sound.wav > > for the second pcm device. the first 0 means the first "card" and you > cannot ommit it to specify the pcm device number. > Thanks. This explanation makes sense. I'll try it out this evening and get back to you then. Cheers, Mark --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] aplay: pcm_write:1025: write error & SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy
At Mon, 2 Jun 2003 07:35:49 -0700, Mark Knecht wrote: > > > > > anyway, in general, BIOS on some ASUS boards have a bug, and the first > > PCM device won't work on them. > > > > Can I tell aplay to use any other PCM device? The second device? How might I > do this? > > aplay hw:1 sound.wav??? please use -D option, for example, % aplay -D hw:0,1 sound.wav for the second pcm device. the first 0 means the first "card" and you cannot ommit it to specify the pcm device number. Takashi --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
RE: [Alsa-devel] aplay: pcm_write:1025: write error& SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy
most likely, aplay -D hw:1,0 sound.wav d! On Mon, 2003-06-02 at 10:35, Mark Knecht wrote: > > > > anyway, in general, BIOS on some ASUS boards have a bug, and the first > > PCM device won't work on them. > > > > Can I tell aplay to use any other PCM device? The second device? How might I > do this? > > aplay hw:1 sound.wav??? > > > > > --- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > ___ > Alsa-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/alsa-devel signature.asc Description: This is a digitally signed message part
Re: [Alsa-devel] aplay: pcm_write:1025: write error & SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy
At Mon, 2 Jun 2003 07:33:47 -0700, Mark Knecht wrote: > > > > > just add the following line to the end of /etc/modules.conf: > > > > options snd-via82xx dxs_support=2 > > > > (or dxs_support=3) > > > > and run "/etc/init.d/alsasound restart". > > > > note that the option above is available only on the very recent ALSA > > version. > > > > > > ciao, > > > > Takashi > > Thanks. That's very clear. I'll try it this evening. (At work right now.) > > As for Alsa versions, this is a Gentoo ebuild of Alsa. It identifies itself > as '0.9.3c-r1'. (Is that right? I might have thought 0.9.3-rc1?) Anyway, > that's what it says. New enough for these options? hmm.. sorry, i can't remember. just try and check /proc/asound/card0 whether pcm2p directory exists there :) Takashi --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
RE: [Alsa-devel] aplay: pcm_write:1025: write error & SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy
> > anyway, in general, BIOS on some ASUS boards have a bug, and the first > PCM device won't work on them. > Can I tell aplay to use any other PCM device? The second device? How might I do this? aplay hw:1 sound.wav??? --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
RE: [Alsa-devel] aplay: pcm_write:1025: write error & SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy
> > just add the following line to the end of /etc/modules.conf: > > options snd-via82xx dxs_support=2 > > (or dxs_support=3) > > and run "/etc/init.d/alsasound restart". > > note that the option above is available only on the very recent ALSA > version. > > > ciao, > > Takashi Thanks. That's very clear. I'll try it this evening. (At work right now.) As for Alsa versions, this is a Gentoo ebuild of Alsa. It identifies itself as '0.9.3c-r1'. (Is that right? I might have thought 0.9.3-rc1?) Anyway, that's what it says. New enough for these options? Thanks much! Mark --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] aplay: pcm_write:1025: write error & SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy
At Mon, 2 Jun 2003 07:20:05 -0700, Mark Knecht wrote: > > Takashi, >Thanks for the fast response. Can you give me the exact format for adding > the module options? I'm not sure which module to add this to, nor have I > ever added module options by hand before. Please be clear as I am not a > software person. /etc/modules.conf? Which line? just add the following line to the end of /etc/modules.conf: options snd-via82xx dxs_support=2 (or dxs_support=3) and run "/etc/init.d/alsasound restart". note that the option above is available only on the very recent ALSA version. ciao, Takashi --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
RE: [Alsa-devel] aplay: pcm_write:1025: write error & SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy
Takashi, Thanks for the fast response. Can you give me the exact format for adding the module options? I'm not sure which module to add this to, nor have I ever added module options by hand before. Please be clear as I am not a software person. /etc/modules.conf? Which line? Thanks, Mark > -Original Message- > From: Takashi Iwai [mailto:[EMAIL PROTECTED] > Sent: Monday, June 02, 2003 6:56 AM > To: Mark Knecht > Cc: Alsa-Devel > Subject: Re: [Alsa-devel] aplay: pcm_write:1025: write error & > SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy > > > At Mon, 2 Jun 2003 06:41:12 -0700, > Mark Knecht wrote: > > > > Takashi, > >While I find this interesting, it doesn't address the > problem. I sent a > > bunch of information and data in the last two emails. Have I > sent what you > > need? Are you able to make any assessment about why aplay will > not work with > > this this sound chip on my Asus motherboard? > > well, i'm still not sure how can it happen. > it looks like an unusual case. > > anyway, in general, BIOS on some ASUS boards have a bug, and the first > PCM device won't work on them. > > could you try to add the module option dxs_support=2 or 3 ? > the option 2 will disable the DXS channel support and works as > VIA8233A chip. the option 3 suppresses the sample rate 48k only. > > > Takashi > > > > > With best regards, > > Mark > > > > > -Original Message- > > > From: [EMAIL PROTECTED] > > > [mailto:[EMAIL PROTECTED] Behalf Of > Takashi Iwai > > > Sent: Monday, June 02, 2003 4:12 AM > > > To: Mark Knecht > > > Cc: Alsa-Devel > > > Subject: Re: [Alsa-devel] aplay: pcm_write:1025: write error & > > > SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy > > > > > > > > > At 29 May 2003 21:43:39 -0700, > > > Mark Knecht wrote: > > > > > > > > Sorry this is a bit long. Mostly just data. I hope it helps > figure this > > > > out. Sort of strange that the chip is identified in one place as a > > > > VIA8233 and in another place as a VIA8235 > > > > > > in fact, both VIA8233 and 8235 have the same PCI ID. that's why lspci > > > shows the same name (while 8235 has the revision 0x50). > > > > > > > > > Takashi > > > > > > > > > --- > > > This SF.net email is sponsored by: eBay > > > Get office equipment for less on eBay! > > > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > > > ___ > > > Alsa-devel mailing list > > > [EMAIL PROTECTED] > > > https://lists.sourceforge.net/lists/listinfo/alsa-devel > > > > > > > > > > > > --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] aplay: pcm_write:1025: write error & SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy
At Mon, 2 Jun 2003 06:41:12 -0700, Mark Knecht wrote: > > Takashi, >While I find this interesting, it doesn't address the problem. I sent a > bunch of information and data in the last two emails. Have I sent what you > need? Are you able to make any assessment about why aplay will not work with > this this sound chip on my Asus motherboard? well, i'm still not sure how can it happen. it looks like an unusual case. anyway, in general, BIOS on some ASUS boards have a bug, and the first PCM device won't work on them. could you try to add the module option dxs_support=2 or 3 ? the option 2 will disable the DXS channel support and works as VIA8233A chip. the option 3 suppresses the sample rate 48k only. Takashi > > With best regards, > Mark > > > -Original Message- > > From: [EMAIL PROTECTED] > > [mailto:[EMAIL PROTECTED] Behalf Of Takashi Iwai > > Sent: Monday, June 02, 2003 4:12 AM > > To: Mark Knecht > > Cc: Alsa-Devel > > Subject: Re: [Alsa-devel] aplay: pcm_write:1025: write error & > > SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy > > > > > > At 29 May 2003 21:43:39 -0700, > > Mark Knecht wrote: > > > > > > Sorry this is a bit long. Mostly just data. I hope it helps figure this > > > out. Sort of strange that the chip is identified in one place as a > > > VIA8233 and in another place as a VIA8235 > > > > in fact, both VIA8233 and 8235 have the same PCI ID. that's why lspci > > shows the same name (while 8235 has the revision 0x50). > > > > > > Takashi > > > > > > --- > > This SF.net email is sponsored by: eBay > > Get office equipment for less on eBay! > > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > > ___ > > Alsa-devel mailing list > > [EMAIL PROTECTED] > > https://lists.sourceforge.net/lists/listinfo/alsa-devel > > > > > > --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
RE: [Alsa-devel] aplay: pcm_write:1025: write error & SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy
Takashi, While I find this interesting, it doesn't address the problem. I sent a bunch of information and data in the last two emails. Have I sent what you need? Are you able to make any assessment about why aplay will not work with this this sound chip on my Asus motherboard? With best regards, Mark > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] Behalf Of Takashi Iwai > Sent: Monday, June 02, 2003 4:12 AM > To: Mark Knecht > Cc: Alsa-Devel > Subject: Re: [Alsa-devel] aplay: pcm_write:1025: write error & > SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy > > > At 29 May 2003 21:43:39 -0700, > Mark Knecht wrote: > > > > Sorry this is a bit long. Mostly just data. I hope it helps figure this > > out. Sort of strange that the chip is identified in one place as a > > VIA8233 and in another place as a VIA8235 > > in fact, both VIA8233 and 8235 have the same PCI ID. that's why lspci > shows the same name (while 8235 has the revision 0x50). > > > Takashi > > > --- > This SF.net email is sponsored by: eBay > Get office equipment for less on eBay! > http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 > ___ > Alsa-devel mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/alsa-devel > > --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] aplay: pcm_write:1025: write error & SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy
At 29 May 2003 21:43:39 -0700, Mark Knecht wrote: > > Sorry this is a bit long. Mostly just data. I hope it helps figure this > out. Sort of strange that the chip is identified in one place as a > VIA8233 and in another place as a VIA8235 in fact, both VIA8233 and 8235 have the same PCI ID. that's why lspci shows the same name (while 8235 has the revision 0x50). Takashi --- This SF.net email is sponsored by: eBay Get office equipment for less on eBay! http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5 ___ Alsa-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/alsa-devel
Re: [Alsa-devel] aplay: pcm_write:1025: write error &SNDRV_PCM_IOCTL_PREPAREfailed:device or resource busy
Sorry this is a bit long. Mostly just data. I hope it helps figure this out. Sort of strange that the chip is identified in one place as a VIA8233 and in another place as a VIA8235 On Wed, 2003-05-21 at 04:09, Takashi Iwai wrote: > At 18 May 2003 17:05:32 -0700, > Mark Knecht wrote: > > > > Hi, > >I brought up Alsa Friday on a Gentoo platform and used it for most of > > Friday evening and Saturday in one form or another. Along the way I was > > building some new kernels to fix some SCSI issues and a few other items, > > which required that Alsa get rebuilt also as per the Gentoo Alsa > > instructions. This process went on for most of the day. Later Saturday > > evening, following who knows how many 'unrelated' changes, Alsa stopped > > working. The error messages look like this: > > > > Wizard root # aplay wave/sequen~1.wav > > Playing WAVE 'wave/sequen~1.wav' : Signed 16 bit Little Endian, Rate > > 44100 Hz, Mono > > aplay: pcm_write:1025: write error: Input/output error > > Wizard root # > > > > or when trying to play a game like frozen-bubble, that app locks up hard > > and in my console I see: > > > > ALSA Lib pcm_hw.c:467:(snd_pcm_hw_prepare)SNDRV_PCM_IOCTL_PREPARE > > failed:device or resource busy > > > > alsaplayer starts to run, sees the CD (I.e. - shows track length) and > > then won't play the CD. > > > > I'll attach a bit of data, but can anyone point me toward what might be > > causing this? > > the chip looks like a VIA8235, so the (first) pcm device supports > multiple playbacks but with the same sample rate. > please check whether there is any other app running and using the pcm > device and if it uses different sample rates (e.g. 48kHz)... > > > Takashi Takashi-san, To the best of my knowledge there are no other apps using sound in any way. The environment is fluxbox, which doesn't use sound. I get the same results in a console after a cold boot before starting fluxbox also. I've tried playing 48KHz and 44.1KHz wave files and get the same results. There is a strange thing I noticed about how the chip is set up though. I've loaded the via82xx driver. In /proc/pci the chip identifies itself as an VIA8233: Wizard root # grep audio /proc/pci Multimedia audio controller: Xilinx, Inc. RME Hammerfall DSP (rev 104). Multimedia audio controller: VIA Technologies, Inc. VT8233 AC97 Audio Controller (rev 80). Wizard root # However, in aplay it identifies itself as a VIA 8235: bash-2.05b$ aplay -l List of PLAYBACK Hardware Devices card 0: 8235 [VIA 8235], device 0: VIA 8235 [VIA 8235] Subdevices: 4/4 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 Subdevice #3: subdevice #3 card 0: 8235 [VIA 8235], device 1: VIA 8235 [VIA 8235] Subdevices: 1/1 Subdevice #0: subdevice #0 bash-2.05b$ There are no processes running that are obviously usign audio, as far as I can see: bash-2.05b$ ps aux USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 1 0.2 0.0 1352 496 ?S20:54 0:04 init root 2 0.0 0.0 00 ?SW 20:54 0:00 [keventd] root 3 0.0 0.0 00 ?SWN 20:54 0:00 [ksoftirqd_CPU0] root 4 0.0 0.0 00 ?SW 20:54 0:00 [kswapd] root 5 0.0 0.0 00 ?SW 20:54 0:00 [bdflush] root 6 0.0 0.0 00 ?SW 20:54 0:00 [kupdated] root 8 0.0 0.0 00 ?SW 20:54 0:00 [khubd] root12 0.0 0.0 00 ?SW 20:54 0:00 [kjournald] root36 0.0 0.1 1748 916 ?S20:54 0:00 /sbin/devfsd /dev root 843 0.0 0.1 1428 572 ?S20:54 0:00 /usr/sbin/syslogd -m 0 root 846 0.0 0.1 1472 576 ?S20:54 0:00 /usr/sbin/klogd -c 3 -2 root 849 0.0 0.1 1472 568 ?S20:54 0:00 /usr/sbin/crond root 1089 0.0 0.2 2732 1284 ?S20:54 0:00 /usr/sbin/sshd xfs 1242 0.0 0.9 6264 4772 ?S20:54 0:00 [xfs] root 1252 0.0 0.2 2288 1236 ?S20:54 0:00 [login] root 1253 0.0 0.0 1336 424 vc/2 S20:54 0:00 /sbin/agetty 38400 tty2 linux root 1254 0.0 0.0 1336 424 vc/3 S20:54 0:00 /sbin/agetty 38400 tty3 linux mark 1322 0.0 0.2 2292 1372 vc/1 S20:54 0:00 -bash mark 1331 0.0 0.1 2036 976 vc/1 S20:55 0:00 /bin/sh /usr/X11R6/bin/startx mark 1342 0.0 0.1 2324 624 vc/1 S20:55 0:00 xinit /home/mark/.xinitrc -- -deferglyphs 16 root 1343 0.3 2.5 92644 13356 ? R20:55 0:06 [X] mark 1361 0.0 0.5 5212 2648 vc/1 S20:55 0:00 /usr/bin/fluxbox mark 1560 0.0 0.3 3692 1832 ?S21:13 0:00 /usr/bin/gconfd-1 12 mark 1628 0.0 0.8 6928 4332 ?R21:21 0:00 [xterm] mark 1629 0.0 0.2 2312 1396 pts/0S21:21 0:00 bash mark 1638 0.0