On Sunday 24 February 2008, raydar wrote: > in a terminal, got > > /dev/dsp: Device or resource busy
When something is busy, try seeing what's making it so with fuser. fuser /dev/dsp I can't get a return on that here and now to show an example, but I think it returns the PID of whatever process is holding the file open. If you then put it into ps... Say the above returned 1234, you'd use: ps 1234 Then I would expect it to belong to jackd. Could be totally wrong though. > /dev/dsp? (I'm thinking /dev/dsp1 might be the on-board sound that I'm > not using, while /dev/dsp is the PCI sound card which I am using and > have speakers & inputs plugged into. Maybe that onboard sound chip > wasn't an involuntary waste of $ after all?) Ah, that could well be what it is. I guess the best way to handle that would be to run a little cable with a 1/8" stereo jack on each end between the line out on the onboard sound chip (usually green) and the line in on the primary soundcard (usually blue) then dink around with the mixer on the primary soundcard until you can hear the other one (QAMix, the Capture tab, set to Line or Mix, unless the Capture tab is broken for you like that other guy I was dealing with a bit back.) It might actually work, though I can't play with testing that scenario out, as I disabled my onboard soundcard. It sounded like total crap. -- D. Michael McIntyre -- Ubuntu-Studio-users mailing list Ubuntu-Studio-users@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-studio-users
