openSUSE Forums > Archives > SF Archives > ARCHIVES - Hardware » Realtek Alc889a Open /dev/dsp: Device Or Resource Busy

Go Back   openSUSE Forums > Archives > SF Archives > ARCHIVES - Hardware
Forums FAQ Members List Search Today's Posts Mark Forums Read

ARCHIVES - Hardware Questions about hardware installation or configuration in SUSE Linux

 
 
LinkBack Thread Tools Display Modes
  #1 (permalink)  
Old 13-Oct-2007, 14:53
Vanista Herion
Guest
 
Posts: n/a
Default

I'm having trouble getting sound to work for some legacy games which use /dev/dsp.
For Quake 3, Unreal Tournament, Heroes 3 and Descent 3 the pattern is the same :

open /dev/dsp: Device or resource busy

KDE apps can play sound fine and my user is part of the audio group so there is no permission issue. I've installed the latest driver from RealTek (20071002) but it didn't help.

I've found a lot of similar reported issues on google, but most of them date back to 2004

Here's all the info I could get on the device :

Code:
> dir /dev/dsp 
crw-rw----+ 1 root audio 14, 3 2007-10-13 15:45 /dev/dsp

> lspci
00:1b.0 Audio device: Intel Corporation 82801I (ICH9 Family) HD Audio Controller (rev 02)

> lsmod
snd_pcm_oss************55296**0 
snd_mixer_oss**********32384**1 snd_pcm_oss
snd_seq****************63412**0 
snd_seq_device******** 24332**1 snd_seq
snd_hda_intel******** 285984**4 
snd_pcm****************88196**3 snd_pcm_oss,snd_hda_intel
snd_timer**************37764**3 snd_seq,snd_pcm
snd_page_alloc******** 25992**2 snd_hda_intel,snd_pcm
snd_hwdep**************25220**1 snd_hda_intel
snd********************66740**14 snd_pcm_oss,snd_mixer_oss,snd_seq,snd_seq_device,snd_hda_intel,snd_pcm,snd_timer,snd_hwdep
soundcore**************23748**1 snd

> lshal
udi = '/org/freedesktop/Hal/devices/pci_8086_293e_sound_card_0_oss_pcm_0'
**info.callouts.add = {'hal-resmgr'} (string list)
**info.capabilities = {'oss'} (string list)
**info.category = 'oss'**(string)
**info.interfaces = {'org.freedesktop.Hal.Device.resmgr'} (string list)
**info.parent = '/org/freedesktop/Hal/devices/pci_8086_293e_sound_card_0'**(string)
**info.product = 'ALC882 Analog OSS PCM Device'**(string)
**info.udi = '/org/freedesktop/Hal/devices/pci_8086_293e_sound_card_0_oss_pcm_0'**(string)
**linux.device_file = '/dev/dsp'**(string)
**linux.hotplug_type = 2**(0x2)**(int)
**linux.subsystem = 'sound'**(string)
**linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1b.0/sound/card0/dsp'**(string)
**org.freedesktop.Hal.Device.resmgr.method_argnames = {'', ''} (string list)
**org.freedesktop.Hal.Device.resmgr.method_execpaths = {'hal-resmgr-grant', 'hal-resmgr-revoke'} (string list)
**org.freedesktop.Hal.Device.resmgr.method_names = {'Grant', 'Revoke'} (string list)
**org.freedesktop.Hal.Device.resmgr.method_signatures = {'', ''} (string list)
**oss.card = 0**(0x0)**(int)
**oss.card_id = 'HDA Intel'**(string)
**oss.device = 0**(0x0)**(int)
**oss.device_file = '/dev/dsp'**(string)
**oss.device_id = 'ALC882 Analog'**(string)
**oss.originating_device = '/org/freedesktop/Hal/devices/pci_8086_293e_sound_card_0'**(string)
**oss.physical_device = '/org/freedesktop/Hal/devices/pci_8086_293e_sound_card_0'**(string)
**oss.type = 'pcm'**(string)
**resmgr.class = 'sound'**(string)
**resmgr.device = '/dev/dsp'**(string)

Notice that OSS identifies the device as ALC882 ... Could that spell trouble considering it's ALC889A

Anyone can help with this?
  #2 (permalink)  
Old 14-Oct-2007, 18:37
Vanista Herion
Guest
 
Posts: n/a
Default

Finally figured part of the problem!

By searching for ways to identify which process are using file descriptors, I've discovered the fuser tool.

Code:
> fuser -m /dev/dsp
/dev/dsp:************ 2812m**3998**4056**4057**4100**4105**4125m**4141**4147**4251m 19416 19432 19537 19539

> ps -aef | grep 3998
4105**3998**0 16:31 ?********00:00:00 kwrapper ksmserver
Then I search for reasons why KDE would lock the device and stumbled on this thread from VMware Communities :

Quote:
Basically, use #lsof /dev/snd/* and #fuser /dev/snd/* to determine what programs have *these* sound files open. In my case, because I had turned on KDE's desktop icon preview feature for audio files, the kdesktop program had opened these files; it pipes its preview back through /dev/dsp. Other processes can do the same. They need to be killed to free /dev/dsp. There is a good chance that simply executing as root - #/etc/init.d/alsasound restart - will take care of it for you.
[/b]
That was it... I had enabled the preview option for all supported file types without consideration to how the audio files would be rendered. Bumped this option, restarted and finaly got sound for the Loki games!

This didn't help the issue with Quake, but now I got a different error :

Code:
------- sound initialization -------
Could not mmap dma buffer PROT_WRITE|PROT_READ
trying mmap PROT_WRITE (with associated better compatibility / less performance code)
/dev/dsp: Input/output error
Could not mmap /dev/dsp
------------------------------------
  #3 (permalink)  
Old 27-Nov-2007, 12:53
Razvan
Guest
 
Posts: n/a
Default

Hello. I get the same error(from bellow) with quake3 by using SUSE10.3 on a Gigabyte P35 DS3R board(also with Realtek ALC889A). I did not try yet, but I suppose I will have the same problem with Enemy Territory
Anyone could hive some hint?

Code:
------- sound initialization -------
Could not mmap dma buffer PROT_WRITE|PROT_READ
trying mmap PROT_WRITE (with associated better compatibility / less performance code)
/dev/dsp: Input/output error
Could not mmap /dev/dsp
------------------------------------
 


Bookmarks

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On




 

Search Engine Friendly URLs by vBSEO 3.3.0 RC2