Re: The Sound of Silence

2001-08-28 Thread Mike McGuire
On Mon, Aug 27, 2001 at 09:33:21AM +0900, Curt Howland wrote: > Sorry for the multiple replies, but I have some new data. > > Adding to the audio group didn't work, because the SB modules never > loaded. I have figured out finally that the sound card modle is > "ES1869", but I have not yet found a

Fw: Re: [Fwd: Re: The Sound of Silence]

2001-08-27 Thread Timeboy
On Monday Aug 27, 08:08 Curt Howland wrote: > >Some success: Using the google search, I was able to find an example of >the ess1869 sound card under Linux. > >Now, at least the sound modules load, and YIFF sound driver says it's >working in the boot startup messages. > >However, I still cannot ope

Re: [Fwd: [Fwd: Re: The Sound of Silence]]

2001-08-27 Thread Rich Rudnick
* Oliver Elphick (olly@lfix.co.uk) wrote: > Curt Howland wrote: > > > >One more comment: > > > >I continue to get "/dev/dsp: Device or resource busy" when trying to use > >sound. If I "cat message.au > /dev/audio" even as root, I get the > >message "/dev/audio Device or resource busy".

Re: The Sound of Silence

2001-08-27 Thread Nathan E Norman
On Mon, Aug 27, 2001 at 04:22:11PM +0900, Curt Howland wrote: > Ok, finally something real. > > It's yiff that's dominating the sound files: > > #fuser -v /dev/dsp > USERPID ACCESS COMMAND > /dev/dsp root245 f yiff > > #ps auxwww > USER

Re: [Fwd: [Fwd: Re: The Sound of Silence]]

2001-08-27 Thread Oliver Elphick
Curt Howland wrote: > >One more comment: > >I continue to get "/dev/dsp: Device or resource busy" when trying to use >sound. If I "cat message.au > /dev/audio" even as root, I get the >message "/dev/audio Device or resource busy". Some other program has it open. -- Oliver Elphick

Re: The Sound of Silence

2001-08-27 Thread Curt Howland
Ok, finally something real. It's yiff that's dominating the sound files: #fuser -v /dev/dsp USERPID ACCESS COMMAND /dev/dsp root245 f yiff #ps auxwww USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND root 245 0.1

[Fwd: [Fwd: Re: The Sound of Silence]]

2001-08-27 Thread Curt Howland
One more comment: I continue to get "/dev/dsp: Device or resource busy" when trying to use sound. If I "cat message.au > /dev/audio" even as root, I get the message "/dev/audio Device or resource busy". Also, reading the sound HowTo has not been helpful, it's all well and good if things *work*,

[Fwd: Re: The Sound of Silence]

2001-08-27 Thread Curt Howland
Some success: Using the google search, I was able to find an example of the ess1869 sound card under Linux. Now, at least the sound modules load, and YIFF sound driver says it's working in the boot startup messages. However, I still cannot open /dev/dsp And yes, I did make the changes recommend

Re: The Sound of Silence

2001-08-26 Thread Curt Howland
Sorry for the multiple replies, but I have some new data. Adding to the audio group didn't work, because the SB modules never loaded. I have figured out finally that the sound card modle is "ES1869", but I have not yet found any information on manufacturer other than this model number. If anyone

Re: The Sound of Silence

2001-08-26 Thread Curt Howland
I'm getting the feeling that the module just isn't working, because on boot the error is: Starting Y Sound Server: /dev/dsp: Cannot open for playing. I believe now that the sbc60xxwdt module is wrong, I should be using the "sb" one. The problem is the module won't auto-probe, it dies with an err

Re: The Sound of Silence

2001-08-25 Thread harshu
hi, > > So I am using the sbc60xxwdt module. > > The error now is something like "Cannot Open /dev/dsp" and the sound > still does not work. This typically happens when the module is not yet loaded. It also happens if the permissions of /dev/dsp /dev/mixer are not correct. you could change the

Re: The Sound of Silence

2001-08-25 Thread Sean Quinlan
* Curt Howland <[EMAIL PROTECTED]> (2001-08-25 04:00): > The error now is something like "Cannot Open /dev/dsp" and the sound > still does not work. Add yourself to the audio group like this # adduser curt audio Logout, log in again, and then try your sound, it should work now. Cheers, Sean --