public inbox for alsa-devel@alsa-project.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000373]: Sound in Quake 3 does not work
Date: Sat, 9 Apr 2005 16:42:41 +0200	[thread overview]
Message-ID: <944851d9706717d0a2e0fe8adc484062@bugtrack.alsa-project.org> (raw)


The following issue has been ACKNOWLEDGED.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=373> 
======================================================================
Reported By:                damage
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   373
Category:                   PCI - via82xx
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     acknowledged
Distribution:               Suse Linux 9.1
Kernel Version:             2.6.5-7.95-default
======================================================================
Date Submitted:             07-09-2004 21:37 CEST
Last Modified:              04-09-2005 16:42 CEST
======================================================================
Summary:                    Sound in Quake 3 does not work
Description: 
I already tried several things to get sound working in Quake 3. It doesn't

work. Sound in other applications, such as xmms, works without problems.
My System: SUSE Linux 9.1 Pro 64bit, MSI K8T Neo FIS2R, Athlon 64 3200,
1GB 
RAM, VIA 8237 on board sound

I tried it with the ALSA version that comes with the Default Suse Kernel,
then 
with version 1.05a and at the moment I've installed a version from CVS two

days ago. I loaded the alsa module with dxs_support 0 to 4, that didn't 
resolve the issue.

Without changing anything in the ALSA configuration Quake 3 starts and the

game runs without problems, but there is no sound. The following error 
message is displayed when Quake 3 starts.
------- 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
------------------------------------

Enabling direct access to the OSS playback device and disabling the OSS 
capture device with 
echo "quake3.x86 0 0 direct" > /proc/asound/card0/pcm0p/oss
echo "quake3.x86 0 0 disable" > /proc/asound/card0/pcm0c/oss
I get sound in the Quake 3 menu, but as soon as I enter a map the game
hangs 
and the only way to get back to X is to kill the process.

I also tried the user space ALSA OSS wrapper library. With this library I
only 
get some crackling noises in the menu and in the game.

With xrun_debug 1 I get a few of the following messages (at least with the

actually installed drivers from CVS) in the system log. These messages are

also there when I run other applications than Quake 3.
Jul  8 19:07:48 mordor kernel: ALSA sound/core/pcm_lib.c:199: Unexpected 
hw_pointer value [1] (stream = 0, delta: -1024, max jitter = 8192): wrong

interrupt acknowledge?
Jul  8 19:07:48 mordor kernel: ALSA sound/pci/via82xx.c:731: invalid 
via82xx_cur_ptr, using last valid pointer
Jul  8 19:08:00 mordor last message repeated 194 times

I don't know whether that has something to do with the problem.

======================================================================

----------------------------------------------------------------------
 damage - 07-09-04 21:46 
----------------------------------------------------------------------
I did some minor corrections to the uploaded file and uploaded it a second
time, as the comments were wrong.

This bug seems to be related to the following bugs which are filed for
other sound cards:
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000254
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000015

----------------------------------------------------------------------
 tokugawa - 07-11-04 00:04 
----------------------------------------------------------------------
"I get sound in the Quake 3 menu, but as soon as I enter a map the game
hangs
and the only way to get back to X is to kill the process."

Hi, the same here...  i'm going on vacation right now, so i can't help
much... but:

1) open the pk3 (like baseq3/pak0.pk3) files (these are zip)
2) move from them music dir to some other (so q3 will not found them)
3) run q3
4) tada!! qukae3 works, music hangs the game, without it game works
5) But there are no 'turn off music' in quake3 (music volume option don't
work... hangs are happen even if you turn down music completly in
options), so I just deleted music dirs from my pk3's. (just run zip -vd
pak0.pk3 'music/*' )

Heh... but you can't play online, because you have a hacked pk3 files...,
so we have to wait for a real fix

I'm hope that will help in bug hunting. If you can, please confirm that
behaviour.

----------------------------------------------------------------------
 damage - 07-11-04 02:35 
----------------------------------------------------------------------
I can absolutely confirm all of what tokugawa said. Deleting the music
files makes the game work with sound. Of course then there is no music in
the game and you can't play online anymore. The latter makes the game
kinda boring ;) .

----------------------------------------------------------------------
 damage - 07-18-04 19:13 
----------------------------------------------------------------------
Does anybody have a tip on how to debug this? I tried several things, like
getting an strace, and running it in gdb, but neither was really helpful
at locating the reason for the freeze (at least for me). The strace looks
nearly identical when running with and without music. gdb doesn't tell me
much as I get either a _really_ big list when I want a backtrace after
interrupting the frozen game, or there is nothing at all in the backtrace.
Seems to depend on the time I interrupt the process.
Perhaps a debugging statement somewhere in the ALSA source could help?

----------------------------------------------------------------------
 Deelight - 07-26-04 16:20 
----------------------------------------------------------------------
Using kernel 2.6.7, i have a similar problem :

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

After typing :
echo "quake3.x86 0 0 direct" > /proc/asound/card0/pcm0p/oss
echo "quake3.x86 0 0 disable" > /proc/asound/card0/pcm0c/oss
I get :

------- sound initialization -------
/dev/dsp0: Invalid argument
Could not set /dev/dsp0 to stereo=1------------------------------------

----------------------------------------------------------------------
 badbunny - 10-27-04 00:37 
----------------------------------------------------------------------
Have you tried seting the dxs_support options yet. In modprobe.conf try
adding 
"options via82xx dxs_support=4".

Issue History
Date Modified  Username       Field                    Change              
======================================================================
07-09-04 21:37 damage         New Issue                                    
07-09-04 21:37 damage         File Added: alsa_q3_debug.txt                    
07-09-04 21:37 damage         Distribution              => Suse Linux 9.1  
07-09-04 21:37 damage         Kernel Version            => 2.6.5-7.95-default
07-09-04 21:41 damage         File Added: alsa_q3_debug.txt                    
07-09-04 21:46 damage         Note Added: 0001396                          
07-09-04 21:50 damage         Issue Monitored: damage                      
07-11-04 00:04 tokugawa       Note Added: 0001406                          
07-11-04 02:35 damage         Note Added: 0001407                          
07-18-04 19:13 damage         Note Added: 0001459                          
07-26-04 16:20 Deelight       Note Added: 0001474                          
10-27-04 00:37 badbunny       Note Added: 0002268                          
04-09-05 16:42 jdthood        Status                   new => acknowledged 
04-09-05 16:42 jdthood        Description Updated                          
04-09-05 16:42 jdthood        Additional Information Updated                    
======================================================================




-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click

             reply	other threads:[~2005-04-09 14:42 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-09 14:42 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-01-03 11:41 [ALSA - driver 0000373]: Sound in Quake 3 does not work bugtrack
2006-01-03 11:39 bugtrack
2005-06-01 18:38 bugtrack
2005-06-01 15:41 bugtrack
2005-05-29  6:07 bugtrack
2004-10-26 22:37 bugtrack
2004-07-18 17:13 noreply
2004-07-11  0:35 noreply
2004-07-10 22:04 noreply
2004-07-09 19:46 noreply
2004-07-09 19:37 noreply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=944851d9706717d0a2e0fe8adc484062@bugtrack.alsa-project.org \
    --to=bugtrack@alsa-project.org \
    --cc=alsa-devel@alsa-project.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox