Messages in this thread | | | Date | Fri, 8 Jan 1999 21:08:59 -0500 | From | Wakko Warner <> | Subject | FWD: Re: 2.2.0-pre4 sound problems |
| |
I did a little more playing around looking for EBUSY in *.c in drivers/sound. Here's what I found out:
Jan 8 21:05:59 ani kernel: SB 4.13 detected OK (220) Jan 8 21:06:04 ani kernel: sb_audio.c: Opening device 0. Mode = 1 Jan 8 21:06:04 ani kernel: sb_audio.c: Device 0 opened Jan 8 21:06:06 ani kernel: sb_audio.c: Closing device 0 Jan 8 21:06:06 ani kernel: sb_audio.c: Device 0 closed Jan 8 21:06:11 ani kernel: sb_audio.c: Opening device 0. Mode = 2 Jan 8 21:06:11 ani kernel: sb_audio.c: Device 0 opened Jan 8 21:06:11 ani kernel: dmabuf.c: DMA_BUSY ^^^^^^^^^^^^^^^^^^ Jan 8 21:06:11 ani kernel: sb_audio.c: Closing device 0 Jan 8 21:06:11 ani kernel: sb_audio.c: Device 0 closed
I don't think I can fix this as I know nothing about programming sound cards. FOr that matter, I know almost nothing about how the kernel works <g> (any aspect)
> > Well, when I record from /dev/dsp2 (maj 14 min 3), It always says device or > > resource busy. > > Not sure, but it may be related
I just found something out about this. If I attempt to record from dev /dev/dsp (it's dsp2 on my machine until the kernel oops below is resolved) I get a nice recorded sound file. I can *STILL* record, but I can't play anything (I get dev or resource busy). If I unload it and load it back, I can play or record. Which ever one I do, I can't do the other until I unload it and load it back.. I haven't tried to see what happens if I open for RW (quake2 does it for some odd reason)
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/
| |