After jumping though a few hoops getting RTCW Enemy Territory to install on my AMD 64 machine I had one remaining problem...no sound
I was getting the error "Could not mmap /dev/dsp"
Anyway after finding the ALSA FAQ I discovered that running echo "et.x86 0 0 direct" > /proc/asound/card0/pcm0p/oss
Resolves this issue for me.
However I want to make this change persistant, I can't add this the the et start up script as it requires root to set.
What would be the "clean" way of making this a permanent change. Or do I just drop it in an init script.
On Wed, 4 Aug 2004 22:15:15 +0100, Wayne Stallwood wayne@digimatic.plus.com was rumoured to have said:
After jumping though a few hoops getting RTCW Enemy Territory to install on my AMD 64 machine I had one remaining problem...no sound
I was getting the error "Could not mmap /dev/dsp"
Anyway after finding the ALSA FAQ I discovered that running echo "et.x86 0 0 direct" > /proc/asound/card0/pcm0p/oss
Resolves this issue for me.
However I want to make this change persistant, I can't add this the the et start up script as it requires root to set.
What would be the "clean" way of making this a permanent change. Or do I just drop it in an init script.
Not sure how much "cleaner" this is, but you could instead drop it in some (not autogenerated!) modules config file. With recent module-init-tools, something like this in, say, /etc/modprobe.d/alsa ought to work:
install snd_pcm /bin/echo "et.x86 0 0 direct" > /proc/asound/card0/pcm0p/oss; /sbin/modprobe --ignore-install snd_pcm
rgds, /-sb.
On Saturday 07 August 2004 11:27 am, Stelios Bounanos wrote:
Not sure how much "cleaner" this is, but you could instead drop it in some (not autogenerated!) modules config file. With recent module-init-tools, something like this in, say, /etc/modprobe.d/alsa ought to work:
install snd_pcm /bin/echo "et.x86 0 0 direct" > /proc/asound/card0/pcm0p/oss; /sbin/modprobe --ignore-install snd_pcm
Ahhh thanks for that, looks like a reasonable way to do things, I just hope I remember where I tucked it away if I ever need to remove it.
On Sat, 7 Aug 2004 14:52:54 +0100, Wayne Stallwood ALUGlist@digimatic.plus.com was rumoured to have said:
On Saturday 07 August 2004 11:27 am, Stelios Bounanos wrote:
Not sure how much "cleaner" this is, but you could instead drop it in some (not autogenerated!) modules config file. With recent module-init-tools, something like this in, say, /etc/modprobe.d/alsa ought to work:
install snd_pcm /bin/echo "et.x86 0 0 direct" > /proc/asound/card0/pcm0p/oss; /sbin/modprobe --ignore-install snd_pcm
Ahhh thanks for that, looks like a reasonable way to do things, I just hope I remember where I tucked it away if I ever need to remove it.
Argh, it just dawned on me that the /proc file may not actually exist until the module has been loaded, so the modprobe should go first. And it looks like the right module might be snd_pcm_oss...(?)
rgds, /-sb.
-
Stelios Bounanos -
Wayne Stallwood -
Wayne Stallwood