l i n u x - u s e r s - g r o u p - o f - d a v i s
Next Meeting:
July 7: Social gathering
Next Installfest:
Latest News:
Jun. 14: June LUGOD meeting cancelled
Page last updated:
2003 Dec 16 00:41

The following is an archive of a post made to our 'vox-tech mailing list' by one of its subscribers.

Report this post as spam:

(Enter your email address)
Re: [vox-tech] RTCW, sound problem
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [vox-tech] RTCW, sound problem

Yep. To get by this:
$ wolfmp
$ wolfsp
type one or the other to play with one or the other. I guessed that this
was caused by the sound resource still being in use when one was quitting
and the other was starting before sound resources were freed by the first
one quitting.


Jonathan Stickel said:
> Thanks for the few suggestions.  I should have mentioned that I had
> already made sure artsd and esd were not running; that isn't the problem
> here.  I've managed to get RTCW, single player, to work by starting with
> wolf +set s_initsound 0
> Of course, no sound now for the initial multiplayer menu.  But when I
> choose single player, sound gets initiated, and now it works!  There
> must be some bug with that transition from mp to sp...
> Jonathan
> Peter Jay Salzman wrote:
>> On Sat 13 Dec 03,  9:25 AM, Jonathan Stickel <jjstickel@sbcglobal.net>
>> said:
>>>I've recently decided to give gaming a try in Linux.  I managed to get
>>>Duke3D working, and it runs great.  So next I try Return to Castle
>>>Wolfenstein (RTCW).  I think I installed it all correctly (only a couple
>>>steps), but there is a problem with the sound.
>>>It starts in multi-player mode, I think, with a menu screen.  Here
>>>everything seems fine: sound, graphics, and I can change graphic
>>>options.  I haven't tried to play multiplayer because I'm not yet
>>>The problem is when I choose single-player mode on the menu.  When I
>>>first tried, I did not have ALSA installed.  Single-player would work
>>>but without sound (couldn't find /dev/dsp).  A google search indicated
>>>it might work with ALSA, so I installed ALSA and ALSA-OSS.  ALSA seems
>>>to work fine with all my other applications, but now when I choose
>>>single-player, RTCW hangs with a blank screen and movable mouse cursor.
>>> When I go to another terminal and kill "wolfsp.x86", I get back my
>>>Xterm and see it died at "sound initialization".  No other info is
>>> given.
>>>I can't seem to find this particular problem mentioned on the web.  Any
>>>ideas?  Supposedly the linux implementation of RTCW is similar to
>>> Quake3.
>> jon,
>> are you running a sound daemon?  enlightenment uses esd.  i'm sure gnome
>> and kde have their own sound daemons (i don't use gnome/kde, so i don't
>> know).
>> try killing the sound daemon and see if that helps.
>> if that doesn't work, you can pull out the big guns and try using ltrace
>> to see if you can get any more information about why sound isn't
>> working.
>> if ltrace doesn't give further information, then perhaps strace will.
>> i've solved MANY game related problems using ltrace and strace.
>> use ltrace first -- the output is less copious and easier to go through.
>> pete
> _______________________________________________
> vox-tech mailing list
> vox-tech@lists.lugod.org
> http://lists.lugod.org/mailman/listinfo/vox-tech

vox-tech mailing list

LUGOD Group on LinkedIn
Sign up for LUGOD event announcements
Your email address:
LUGOD Group on Facebook
'Like' LUGOD on Facebook:

Hosting provided by:
Sunset Systems
Sunset Systems offers preconfigured Linux systems, remote system administration and custom software development.

LUGOD: Linux Users' Group of Davis
PO Box 2082, Davis, CA 95617
Contact Us

LUGOD is a 501(c)7 non-profit organization
based in Davis, California
and serving the Sacramento area.
"Linux" is a trademark of Linus Torvalds.

Sponsored in part by:
O'Reilly and Associates
For numerous book donations.