XMMS - Can't Open Audio

[Tachstar]

OS - RH 7.1
Soundcard - TB Montego II
SOundcard is detected upon bootup.

When I run XMMS all I get is:

Please check that:
1) You have the correct output plugin selected. (I have OSS driver 1.2.4 selected)
2) No other program is blocking the soundcard (how do I check this?)
3) Your soundcard is configured properly. (how do I check this too).

When I run XMMS
1) I get no sound
2) My CPU spikes to 80-90% util
3) My disk begins thrashing (based on gkrellm meter).

I know the soundcard works under Windows 98 and NT 2K. Maybe I will simply have to do without sound on this Linux OS. Arrghhhh.

Any ideas before I give up.

[evulish]

Turtle Beach Montego 2?

I was just talking to someone about that that couldn't get it working. I don't know...

[undef]

try running "sndconfig" or "soundconfig" (i don't know which one it is) if get command not found try "setup" or "setuptool"
from the list that pops up choose sound config from the list. hopefully that should detect your soundcard and install the drivers for you. if that doesn't work, you'll have to search for linux drivers for your soundcard and install it manually.

[Tachstar]

Been there and done that with sndconfig. It does detect the card, but says that it does not yet support it.

Thanks for the try though. Maybe the Aureal project will come up with a fix for the Montego II someday.

[Rob 'Feztaa' Park]

Originally posted by Tachstar:
<STRONG>1) You have the correct output plugin selected. (I have OSS driver 1.2.4 selected)</STRONG>

Have you actually tried using other drivers?

Troubleshooting rule #1: try the easier solutions first.

But if you say it's not supported yet, well that could be your problem.

But try changing the drivers. I had a similar problem today. without any warning, XMMS just decided to give me that error message (I didn't change any settings or do anything diferently at all). so I just changed the output driver, and it worked.

[Evil Jeff]

I have had that problem. Use sndconfig or edit your boot up files to modprobe your soundcard driver. Then, if you still get errors, cd into /dev as root, and:

chmod 666 dsp
chmod 666 audio

Then:

adduser yourusername audio

That always gets everything working for me. Good luck.

[Strike]

Originally posted by Evil Jeff:
<STRONG>I have had that problem. Use sndconfig or edit your boot up files to modprobe your soundcard driver. Then, if you still get errors, cd into /dev as root, and:

chmod 666 dsp
chmod 666 audio

Then:

adduser yourusername audio

That always gets everything working for me. Good luck.</STRONG>
No no no no no... not again.
Don't chmod 666 those files. Then ANY schmuck on your system (or any stupid daemon for that matter) can access those devices. Just make sure the group has read/write permissions and then add users to the appropriate group.

[Tachstar]

Okay Strike here is more information.

1) I tried the other I/O Plugins and the only one I got any kind fo response from was the Disk Writer 1.2.4 plugin. When I enabled it my CPU and Disk usage returned to normal levels and the display on XMMS responded when I hit the play button on the controls. Still no sound though even with the speakers cranked to max.

2) The following IO plugins returned the Can't Open Audio message entered above. They are:

eSound Output Plugin 1.2.4
OSS driver 1.2.4

3) The aRTS driver 0.4 caused disk thrashing and CPU rises to 45-50% but not sound, but also no 'Can't Open Audio' message.

These are the only four IO plugins I have loaded at this time.