Craig White wrote:
> On Fri, 2009-03-13 at 13:18 -0700, wayne wrote:
>   
>> Craig White wrote: 
>>     
>>> On Fri, 2009-03-13 at 11:20 -0700, wayne wrote:
>>>   
>>>       
>>>> Craig White wrote:
>>>>     
>>>>     
>>>>         
>>>>>>> ----
>>>>>>> that should have pulseaudio...
>>>>>>>
>>>>>>> how to check...from cli (fedora system)
>>>>>>>
>>>>>>> $ ps aux|grep pulse
>>>>>>> craig     3027  7.7  0.5 163604  5136 ?        Ssl  05:20
>>>>>>> 26:24 /usr/bin/pulseaudio --start
>>>>>>> craig     3074  0.0  0.2   7912  2076 ?        S    05:21
>>>>>>> 0:00 /usr/libexec/pulse/gconf-helper
>>>>>>>
>>>>>>>   
>>>>>>>       
>>>>>>>           
>>>>>>>               
>>>>>> I GET: wayne 13917 0.0 0.0 4064 780 pts/1 S+ 11:07 0:00 grep pulse
>>>>>>     
>>>>>>         
>>>>>>             
>>>>> ----
>>>>> it's not running.
>>>>>
>>>>> You might try executing (as user not root), 'pulseaudio --start' and see
>>>>> what happens. If the connection is refused, that would likely be caused
>>>>> by some program already attached to your sound hardware.
>>>>>
>>>>> This link might be useful...
>>>>> https://wiki.ubuntu.com/PulseAudio
>>>>>
>>>>>       
>>>>>           
>>>> wayne@Ivan:~$ pulseaudio --start
>>>> pulseaudio: unrecognized option `--start'
>>>> E: main.c: Failed to parse command line.
>>>> wayne@Ivan:~$ pulseaudio
>>>> W: alsa-util.c: Device hw:1 doesn't support 44100 Hz, changed to 16000 Hz.
>>>> W: alsa-util.c: Device hw:1 doesn't support 2 channels, changed to 1.
>>>>
>>>>
>>>> No idea what to do
>>>>     
>>>>         
>>> ----
>>> I would think that it should attach to hw:0 and not hw:1
>>>
>>> Try to ensure that nothing has attached to hw:0 by logging out and
>>> logging back in and then before you run anything else, open a terminal
>>> and start pulseaudio again.
>>>
>>> then see if it attaches to hw:0
>>>
>>> If it does, it should be started as a daemon...I think the command
>>> 'pulseaudio --start' is from a newer version and perhaps you might need
>>> to run 'pulseaudio -D' to get it to run as a daemon.
>>>
>>> If it won't attach to hw:0 - I would recommend that you go through the
>>> steps on the wiki I linked to.
>>>       
>
>   
>> TRIED THE STEPS:
>> root@Ivan:~# lsmod | grep snd
>> snd_cmipci             38528  0
>> gameport               16008  1 snd_cmipci
>> snd_pcm_oss            42144  0
>> snd_mixer_oss          17920  1 snd_pcm_oss
>> snd_pcm                78596  2 snd_cmipci,snd_pcm_oss
>> snd_page_alloc         11400  1 snd_pcm
>> snd_opl3_lib           12928  1 snd_cmipci
>> snd_hwdep              10500  1 snd_opl3_lib
>> snd_mpu401_uart         9728  1 snd_cmipci
>> snd_seq_dummy           4868  0
>> snd_seq_oss            35584  0
>> snd_seq_midi            9376  0
>> snd_rawmidi            25760  2 snd_mpu401_uart,snd_seq_midi
>> snd_seq_midi_event      8320  2 snd_seq_oss,snd_seq_midi
>> snd_seq                54224  6
>> snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_seq_midi_event
>> snd_timer              24836  3 snd_pcm,snd_opl3_lib,snd_seq
>> snd_seq_device          9612  6
>> snd_opl3_lib,snd_seq_dummy,snd_seq_oss,snd_seq_midi,snd_rawmidi,snd_seq
>> snd                    56996  13
>> snd_cmipci,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_opl3_lib,snd_hwdep,snd_mpu401_uart,snd_seq_dummy,snd_seq_oss,snd_rawmidi,snd_seq,snd_timer,snd_seq_device
>> soundcore               8800  1 snd
>> root@Ivan:~# lsof | grep dsp
>> root@Ivan:~# echo 'ioUrbanTerror.i386 0 0 direct'
>>     
>>> /proc/asound/card0/pcm0p/oss
>>>       
>> root@Ivan:~# echo 'ioUrbanTerror.i386 0 0 disable'
>>     
>>> /proc/asound/card0/pcm0c/oss
>>>       
>> root@Ivan:~#
>>
>> STILL, no sound from game
>>     
> Im going to try the Audigy card and see if that solves the problem.  Seems like certain cards have this issue and others, not.
>   

TNX FOR THE HELP EVERYONE!

---------------------------------------------------
PLUG-discuss mailing list - PLUG-discuss@lists.plug.phoenix.az.us
To subscribe, unsubscribe, or to change your mail settings:
http://lists.PLUG.phoenix.az.us/mailman/listinfo/plug-discuss