[alsa-devel] Backported sbxfi driver (UNTESTED!)

[The Source]

Xarteras пишет:
> Takashi Iwai wrote:
>> At Fri, 17 Oct 2008 10:26:27 +0400,
>> The Source wrote:
>>> Takashi Iwai пишет:
>>>> At Thu, 16 Oct 2008 22:18:07 +0400,
>>>> The Source wrote:
>>>>  
>>>>>>> Ok. OpenAL with alsa also seem to cause problems.
>>>>>>>             
>>>>>> In both cases, check the period_size and buffer_size values 
>>>>>> (shown in
>>>>>> the kernel message, or /proc/asound/card0/pcm0p/sub0/hw_params).
>>>>>> And, try to aplay with these parameters, whether you get the similar
>>>>>> problem.
>>>>>>
>>>>>>     % aplay -v --period-size=xxx --buffer-size=yyy foo.wav
>>>>>>
>>>>>>
>>>>>> Takashi
>>>>>>
>>>>>>         
>>>>> I'm sorry, but any attemp to play file with ossplay results in 
>>>>> complete system hang with error:
>>>>> unable to handle NULL ponter dereference at address 
>>>>> 0000000000000008.....(hang, no more output).
>>>>> I tried many wav formats. So I can't get error log or period and 
>>>>> buffer sizes, sorry.
>>>>>     
>>>> Can anyone confirm to reproduce Oops with OSS apps (ossplay)?
>>>>
>>>> I'm wondering whether this has anything to do with the capture.
>>>> Can you record the sound, and change the capture mixer element 
>>>> properly?
>>>>
>>>>
>>>> thanks,
>>>>
>>>> Takashi
>>>>
>>>>   
>>> Err, I'm not sure I understand. Could you please explain step-by-step?
>>
>> Just run arecord to record something.  And, change the recording
>> source via mixer.
>>
>> So far, I got little report about recording, and I'm not sure whether
>> it works at all.
>
> I just tested ossplay and arecord.
> For me both result in a spontanous crash back to BIOS without leaving 
> any traces in the log files.
> Everything else works fine so far.
>
> Jan Wolf
>
Seems that only one application at a time can use alsa. All other apps 
say they can't initialize sound until I close the first app.