Hi everybody, I have an x86_64 box running Suse Novell 10.0. I have been mentionning problems with the sound since 9.2 (at least). Most of the time, I dont care, but now, I can not play Ennemy Territory. Once, it worked properly, running it from root, but now (let's say there is some random effect somwhere), I cant run it from root or from user. The sound card is an "ES1370 [Audio PCI] and the graphic card is an NVidia Geforce3 Ti 200. Most of the time there is no KDE windows manager sounds, exepted when stating a session. But when I laungth xmms, it runs very well. Playing ET without sound is not possible... Does someone has an idea on the way to solve this problem ? I have an other box x86 bi-proc with 2 Athlon MP, with a RV100 QY [Radeon 700/VE] as graphical card and allso running Suse Novell 10.0. I did not find a 3D capable XOrg drver. Am I a good searcher but a bad finder ? Thank you for the attention you paid to that mail, Patrick
On Saturday 24 June 2006 13:00, Patrick Serru wrote:
Hi everybody,
I have an x86_64 box running Suse Novell 10.0. I have been mentionning problems with the sound since 9.2 (at least). Most of the time, I dont care, but now, I can not play Ennemy Territory. Once, it worked properly, running it from root, but now (let's say there is some random effect somwhere), I cant run it from root or from user. The sound card is an "ES1370 [Audio PCI] and the graphic card is an NVidia Geforce3 Ti 200. Most of the time there is no KDE windows manager sounds, exepted when stating a session. But when I laungth xmms, it runs very well. Playing ET without sound is not possible... Does someone has an idea on the way to solve this problem ?
I have an other box x86 bi-proc with 2 Athlon MP, with a RV100 QY [Radeon 700/VE] as graphical card and allso running Suse Novell 10.0. I did not find a 3D capable XOrg drver. Am I a good searcher but a bad finder ?
Thank you for the attention you paid to that mail, Patrick
Patrick, For me, the issue with no sound in ET, Doom3, and TC:E had to do with OSS. Here's a script I wrote that tells the OSS driver to allow ET to have sound. I placed it in /etc/rc.d and used chkconfig to activate it for runlevel 5. The heart of the script basically does this: echo "et.x86 0 0 direct" > /proc/asound/card0/pcm0p/oss That, I believe, needs to be done as root. I just found it easier to wrap that in a script that is executed by the system on boot, after alsasound is started. Hope this helps, Alvin --- START /etc/rc.d/gamesnd --- #!/bin/sh # Copyright (c) 2005, Alvin Beach # Script Name: gamesnd # Platform: SuSE 9.3 Professional # Date: June 20, 2005 # Description: Setups up sound for various games ### BEGIN INIT INFO # Provides: gamesnd # Required-start: alsasound # Required-stop: # Default-start: 5 # Default-stop: # Description: Setups up sound for various games ### END INIT INFO # List of games GAMES="et.x86 doom3" echo "Adding sound support for games:" for g in ${GAMES}; do echo -en "\t${g}\t" echo "${g} 0 0 direct" > /proc/asound/card0/pcm0p/oss if [ $? -eq 0 ]; then echo "done" else echo "failed" fi done --- END /etc/rc.d/gamesnd --- -- Please reply to the list.
Alvin wrote:
For me, the issue with no sound in ET, Doom3, and TC:E had to do with OSS. Here's a script I wrote that tells the OSS driver to allow ET to have sound. I placed it in /etc/rc.d and used chkconfig to activate it for runlevel 5.
The heart of the script basically does this: echo "et.x86 0 0 direct" > /proc/asound/card0/pcm0p/oss
Agreed, I had found that the line above was exactly what I needed in order to get sound with quake 3 arena on suse 10.0 and later Excellent script BTW (snipped) J
Le Samedi 24 Juin 2006 11:21, Alvin a écrit :
#!/bin/sh # Copyright (c) 2005, Alvin Beach # Script Name: gamesnd # Platform: SuSE 9.3 Professional # Date: June 20, 2005 # Description: Setups up sound for various games ### BEGIN INIT INFO # Provides: gamesnd # Required-start: alsasound # Required-stop: # Default-start: 5 # Default-stop: # Description: Setups up sound for various games ### END INIT INFO
# List of games GAMES="et.x86 doom3"
echo "Adding sound support for games:" for g in ${GAMES}; do echo -en "\t${g}\t" echo "${g} 0 0 direct" > /proc/asound/card0/pcm0p/oss
if [ $? -eq 0 ]; then echo "done" else echo "failed" fi done
Hi Alvin, hi everybody, Now, I am sure that "et.x86 0 0 direct" is well appended to proc/asound/card0/pcm0p/oss, on each KDE start. But still no sound for ET. Enyboby could help ?. Thank you for the attention you paid to theset mails, PatrickLe
Patrick Serru wrote:
Now, I am sure that "et.x86 0 0 direct" is well appended to proc/asound/card0/pcm0p/oss, on each KDE start. But still no sound for ET. Enyboby could help ?.
Could you verify? Please report result of the command: cat /proc/asound/card0/pcm0p/oss J
Le Jeudi 29 Juin 2006 12:13, J Sloan a écrit :
Patrick Serru wrote:
Now, I am sure that "et.x86 0 0 direct" is well appended to proc/asound/card0/pcm0p/oss, on each KDE start. But still no sound for ET. Enyboby could help ?.
Could you verify? Please report result of the command:
cat /proc/asound/card0/pcm0p/oss
Quiet sure: patrick:~ # cat /proc/asound/card0/pcm0p/oss et.x86 0 0 direct patrick:~ # ls /usr/local/games/enemy-territory/ . et etmain EULA_Wolfenstein_Enemy_Territory.txt .. etded et~.x86 openurl.sh CHANGES etded~.x86 et.x86 pb Docs etded.x86 ET.xpm pbcl.db Thank you, Patrick
On Thursday 29 June 2006 15:25, Patrick Serru wrote:
Le Jeudi 29 Juin 2006 12:13, J Sloan a écrit :
Patrick Serru wrote:
Now, I am sure that "et.x86 0 0 direct" is well appended to proc/asound/card0/pcm0p/oss, on each KDE start. But still no sound for ET. Enyboby could help ?.
Could you verify? Please report result of the command:
cat /proc/asound/card0/pcm0p/oss
Quiet sure: patrick:~ # cat /proc/asound/card0/pcm0p/oss et.x86 0 0 direct
patrick:~ # ls /usr/local/games/enemy-territory/ . et etmain EULA_Wolfenstein_Enemy_Territory.txt .. etded et~.x86 openurl.sh CHANGES etded~.x86 et.x86 pb Docs etded.x86 ET.xpm pbcl.db
Thank you, Patrick
Hmmm, try the various settings in ET itself. It was a long time since I configured it, so I can't remember if I changed something in ET's options menu. Perhaps there's something in the sound or audio sections, ie. a different driver? Alvin
On Thursday 29 June 2006 15:04, Patrick Serru wrote:
Hi Alvin, hi everybody,
Now, I am sure that "et.x86 0 0 direct" is well appended to proc/asound/card0/pcm0p/oss, on each KDE start. But still no sound for ET. Enyboby could help ?.
Thank you for the attention you paid to theset mails, PatrickLe
I'm not sure what the problem could be. Try using a console and navigate to the /proc/asound directory. See if you have more than one card# subdirectories (where # is a number: card0, card1, etc.). I only have onboard sound, but some people have onboard and an additional sound card. Perhaps you have a card1? If that is the case, try changing card0 to card1? Alvin
Le Jeudi 29 Juin 2006 12:16, Alvin a écrit :
On Thursday 29 June 2006 15:04, Patrick Serru wrote:
Hi Alvin, hi everybody,
Now, I am sure that "et.x86 0 0 direct" is well appended to proc/asound/card0/pcm0p/oss, on each KDE start. But still no sound for ET. Enyboby could help ?.
Thank you for the attention you paid to theset mails, PatrickLe
I'm not sure what the problem could be. Try using a console and navigate to the /proc/asound directory. See if you have more than one card# subdirectories (where # is a number: card0, card1, etc.). I only have onboard sound, but some people have onboard and an additional sound card. Perhaps you have a card1? If that is the case, try changing card0 to card1?
Alvin
Hi Alvin, hi everybody, You are right! Ther is on board sound and an addon sound card. ---------------------------- patrick:~ # ls /proc/asound . AudioPCI cards meminfo oss seq version .. card0 devices modules pcm timers ---------------------------- patrick:~ # cat /proc/asound/cards 0 [AudioPCI ]: ENS1370 - Ensoniq AudioPCI Ensoniq AudioPCI ENS1370 at 0xdc00, irq 169 ---------------------------- patrick:~ # ls /proc/asound/oss . .. devices sndstat ---------------------------- patrick:~ # cat /proc/asound/oss/devices 2: [0- 2]: raw midi 0: [0- 0]: mixer 3: [0- 3]: digital audio 12: [0-12]: digital audio ---------------------------- patrick:~ # cat /proc/asound/oss/sndstat Sound Driver:3.8.1a-980706 (ALSA v1.0.9b emulation code) Kernel: Linux patrick 2.6.13-15.10-default #1 Fri May 12 16:13:03 UTC 2006 x86_64 Config options: 0 Installed drivers: Type 10: ALSA emulation Card config: Ensoniq AudioPCI ENS1370 at 0xdc00, irq 169 Audio devices: 0: ES1370 DAC2/ADC (DUPLEX) Synth devices: NOT ENABLED IN CONFIG Midi devices: 0: ES1370 Timers: 7: system timer Mixers: 0: Asahi Kasei AK4531 ---------------------------- patrick:~ # ls /proc/asound/card0 . .. ak4531 audiopci id midi0 oss_mixer pcm0c pcm0p pcm1p ---------------------------- What can I do with all these things ? Yast shows only one card. I am going to reboot now to check the BIOS configuration... Di you know the names of configuration files for ET (before I search & them after rebooting :-) Thank you Patrick
Le Jeudi 29 Juin 2006 12:16, Alvin a écrit :
On Thursday 29 June 2006 15:04, Patrick Serru wrote:
Hi Alvin, hi everybody,
Now, I am sure that "et.x86 0 0 direct" is well appended to proc/asound/card0/pcm0p/oss, on each KDE start. But still no sound for ET. Enyboby could help ?.
Thank you for the attention you paid to theset mails, PatrickLe
I'm not sure what the problem could be. Try using a console and navigate to the /proc/asound directory. See if you have more than one card# subdirectories (where # is a number: card0, card1, etc.). I only have onboard sound, but some people have onboard and an additional sound card. Perhaps you have a card1? If that is the case, try changing card0 to card1?
Alvin
Hi Alvin, hi everybody, The BIOS was set "auto" about on board sound device. I set it to "Disabled". Yast allways sees only the addon card but when I try "test", the sound is output from both devices ! I placed this addon card because of these problems with KDE sound system, and because the driver for the onboard chip was not ready (if I well remember)... I am going to open the box, pull out the addon board, enable the on board chip with the Bios, reconfigure with yast and see what appends... Thank you, Patrick
Le Jeudi 29 Juin 2006 12:16, Alvin a écrit :
On Thursday 29 June 2006 15:04, Patrick Serru wrote:
Hi Alvin, hi everybody,
Now, I am sure that "et.x86 0 0 direct" is well appended to proc/asound/card0/pcm0p/oss, on each KDE start. But still no sound for ET. Enyboby could help ?.
Thank you for the attention you paid to theset mails, PatrickLe
I'm not sure what the problem could be. Try using a console and navigate to the /proc/asound directory. See if you have more than one card# subdirectories (where # is a number: card0, card1, etc.). I only have onboard sound, but some people have onboard and an additional sound card. Perhaps you have a card1? If that is the case, try changing card0 to card1?
Alvin
Hi Alvin, hi everybody, That was it! The sound is now correct with onboard sound device. And it has not been cacophonie when KDE starded. Here was the problem. But what I can see with help of yast is surprising: there is a card #0 ES1370 [audioPCI] and an unconfigured M5455 PCI AC-Link... The BIOS was talking about an AC97 and the chip of the addon board is an ES1370... could it be a bug? Do I have to modify the configuration with Yast while it is well working? Thank you very much, Patrick
Le Jeudi 29 Juin 2006 14:12, Patrick Serru a écrit :
Le Jeudi 29 Juin 2006 12:16, Alvin a écrit :
On Thursday 29 June 2006 15:04, Patrick Serru wrote:
I'm not sure what the problem could be. Try using a console and navigate to the /proc/asound directory. See if you have more than one card# subdirectories (where # is a number: card0, card1, etc.). I only have onboard sound, but some people have onboard and an additional sound card. Perhaps you have a card1? If that is the case, try changing card0 to card1?
Alvin
Hi Alvin, hi everybody,
That was it! The sound is now correct with onboard sound device. And it has not been cacophonie when KDE starded. Here was the problem. But what I can see with help of yast is surprising: there is a card #0 ES1370 [audioPCI] and an unconfigured M5455 PCI AC-Link... The BIOS was talking about an AC97 and the chip of the addon board is an ES1370... could it be a bug? Do I have to modify the configuration with Yast while it is well working?
Thank you very much, Patrick
Hi Alvin, hi everybody, Oh nooooo, I did it! Removing the phanthomatic addon sound card and replacing it by the real on board chip, and it does not work any longer... after re-boot. card does not disapear (it is shown by yast, and as set) but is unreachable (does not work). I have to enter yast, remove the card and re-enter quick configuration for it to work. Then still using yast, actualise the state of (the super script) gamesnd. Could someone help, please? Thank you, Patrick
On Thursday 29 June 2006 15:04, Patrick Serru wrote: Hi Alvin, hi everybody,
Oh nooooo, I did it! Removing the phanthomatic addon sound card and replacing it by the real on board chip, and it does not work any longer... after re-boot. card does not disapear (it is shown by yast, and as set) but is unreachable (does not work). I have to enter yast, remove the card and re-enter quick configuration for it to work. Then still using yast, actualise the state of (the super script) gamesnd.
Could someone help, please? Thank you, Patrick
Hi everybody, I tryed to modify the file file:///etc/modprobe.d/sound but after that Yast crached. I will not check it, but I think I made uncorrect modifications! Before the setting with yast, there was many "snd_ens1370" while typing «lsmod | grep snd» that disapire after setting, with "snd_intel8x0" instead... So, I decided to rename the file /lib/modules/2.6.13-15.10-default/kernel/sound/pci/snd-ens1370.ko to snd-ens1370~.ko and to create a symbolic link named snd-ens1370.ko pointing to snd-intel8x0.ko It is very huggly but IT WORKS !!!!!!!!!!!!! Thank you, Patrick
Le Samedi 24 Juin 2006 11:21, Alvin a écrit :
#!/bin/sh # Copyright (c) 2005, Alvin Beach # Script Name: gamesnd # Platform: SuSE 9.3 Professional # Date: June 20, 2005 # Description: Setups up sound for various games ### BEGIN INIT INFO # Provides: gamesnd # Required-start: alsasound # Required-stop: # Default-start: 5 # Default-stop: # Description: Setups up sound for various games ### END INIT INFO
# List of games GAMES="et.x86 doom3"
echo "Adding sound support for games:" for g in ${GAMES}; do echo -en "\t${g}\t" echo "${g} 0 0 direct" > /proc/asound/card0/pcm0p/oss
if [ $? -eq 0 ]; then echo "done" else echo "failed" fi done
Hi Alvin, hi everybody, I am unfortunatly far from beeing a (good) shell programer. Running the script "by hand" and as root gives this: patrick:/etc/init.d # ./gamesnd Adding sound support for games: ./gamesnd: line 24: syntax error near unexpected token `then' ./gamesnd: line 24: ` if [ $? -eq 0 ]; then' and I dont see anything in the script like hidden caracter or whatever... the command worked stand alone: patrick:/etc/init.d # cat /proc/asound/card0/pcm0p/oss patrick:/etc/init.d # echo "et.x86 0 0 direct" > \ proc/asound/card0/pcm0p/oss patrick:/etc/init.d # cat /proc/asound/card0/pcm0p/oss et.x86 0 0 direct So, after these last command, I tryed starting the game by cliking an icon on a user desktop... no sound. Placing "kdesu " in front of the command to play it as root did not change anything: sill no sound )-: Did I miss something in the explanation ? I modifyed the file copied past from kmail in vi running in a graphical terminal. There was caracters represented like "pipes". Changed them by spaces: no more problem. Then I can start the script with help of yast. But I still have no sound with ET, playing as user or as root. Thank you for the attention you paid to theset mails, Patrick
Hallo Patrick, Am Montag, 26. Juni 2006 03:06 schrieb Patrick Serru:
I am unfortunatly far from beeing a (good) shell programer. Running the script "by hand" and as root gives this:
patrick:/etc/init.d # ./gamesnd Adding sound support for games: ./gamesnd: line 24: syntax error near unexpected token `then' ./gamesnd: line 24: ` if [ $? -eq 0 ]; then'
and I dont see anything in the script like hidden caracter or whatever...
My proposal is to run this script in debug mode: Add -vx to the first line: #!/bin/sh -vx Maybe that gives more information. The if statment is in my opinon OK. Maybe $? results in a misleading value? Good luck Hugo
participants (4)
-
Alvin -
Hugo Mahr -
J Sloan -
Patrick Serru