Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Guillem Solà" <garanda@flumotion.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Issue with creative Xfi PCIe ca0110-IBG
Date: Wed, 14 Oct 2009 18:03:15 +0200	[thread overview]
Message-ID: <4AD5F643.3050908@flumotion.com> (raw)
In-Reply-To: <s5hmy3uvuwr.wl%tiwai@suse.de>

Takashi Iwai wrote:
> At Tue, 13 Oct 2009 18:59:23 +0200,
> Guillem Solà wrote:
>   
>> Takashi Iwai wrote:
>>     
>>> At Tue, 13 Oct 2009 17:01:35 +0200,
>>> Guillem Solà wrote:
>>>   
>>>       
>>>> Takashi Iwai wrote:
>>>>     
>>>>         
>>>>> At Tue, 13 Oct 2009 16:12:47 +0200,
>>>>> Guillem Solà wrote:
>>>>>   
>>>>>       
>>>>>           
>>>>>> Takashi Iwai wrote:
>>>>>>     
>>>>>>         
>>>>>>             
>>>>>>> At Tue, 13 Oct 2009 14:10:44 +0200,
>>>>>>> Guillem Solà wrote:
>>>>>>>   
>>>>>>>      
>>>>>>>> Takashi Iwai wrote:
>>>>>>>>     
>>>>>>>>                
>>>>>>>>                 
>>>>>>>>> It shows the address 1.  So, my patch doesn't work, as it assumes
>>>>>>>>> address 0.  Replace it with 1, and pass probe_mask=0x02.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> Takashi
>>>>>>>>>
>>>>>>>>>           
>>>>>>>>>                   
>>>>>>>> Yeah great, it's working again!
>>>>>>>>
>>>>>>>> I did modprobe snd-hda-intel probe_mask=0x03 instead of mask=0x02 to 
>>>>>>>> make it work
>>>>>>>>
>>>>>>>> and the patch let this way ( I changed both return 1 and addr=1)
>>>>>>>>     
>>>>>>>>         
>>>>>>>>             
>>>>>>>>                 
>>>>>>> Now the question is whether probe_mask=0x03 (or 0x02) works without
>>>>>>> this patch.  How is it?
>>>>>>>
>>>>>>>
>>>>>>> thanks,
>>>>>>>
>>>>>>>   
>>>>>>>       
>>>>>>>           
>>>>>>>               
>>>>>> Hi,
>>>>>>
>>>>>> after few tests I can conclude that it could work with and without the 
>>>>>> patch. The same happens with modprobe snd-hda-intel probe_mask=0x03 or 
>>>>>> 0x02 both can work.
>>>>>>     
>>>>>>         
>>>>>>             
>>>>> OK, good to hear.
>>>>>
>>>>>   
>>>>>       
>>>>>           
>>>>>> So it seems to be fickle because not all the times you modprobe the 
>>>>>> intel module it worked.
>>>>>>     
>>>>>>             
>>>>> Do you mean it's still unstable even with probe_mask option, or it is
>>>>> when without?
>>>>>
>>>>> If probe_mask fixes its fickleness (or flirtation :), the patch below
>>>>> should help.  It will set the default probe_mask for your device.
>>>>> Give it a try.
>>>>>
>>>>>
>>>>> Takashi
>>>>>           
>>>> Hi,
>>>>
>>>> By fickle I mean that when modprobing hda-intel module sometimes it 
>>>> works fine and others cannot get audio although the system seems to 
>>>> always recognize the card, and yes, I'm always using probe_mask=0x02 option.
>>>>
>>>> Actually, about one of five times I can successfully load the module. As 
>>>> I said the first patch doesn't affect, it has been only the casualty 
>>>> that made me believe it did something.
>>>>    
>>>>         
>>> Hm, then it's still puzzling what causes the problem in the recent
>>> kernel.  Or is it coincidence?
>>>
>>>       
>> Uff, really don't know what to say, when I thought I saw some light... 
>> I've been testing with 2.6.31-rc6 and 2.6.31 (final) with and without 
>> patches and maybe is only the probe_mask option what make it work sometimes.
>>
>> Perhaps I did bisect bad and wasn't 
>> deadff1665491afce124a8ff83f00f784161f660 first bad commit?
>>     
>
> Possible.  But, before bisecting, we should be really sure which
> release was really OK.  Did 2.6.30 work without any problems?
>
>   

Hi,

AFAIK in 2.6.30 ca0110 was not implemented. I see it start working in 
2.6.31-rc3 and did a two weeks running test with 2.6.31-rc5.

So I bisected from 2.6.31-rc6 to 2.6.31-rc5

regards,

Guillem Solà
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel

  reply	other threads:[~2009-10-14 16:03 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-09  9:19 Issue with creative Xfi PCIe ca0110-IBG Guillem Solà
2009-10-09  9:38 ` Takashi Iwai
2009-10-09 14:15   ` Guillem Solà
2009-10-09 14:36     ` Takashi Iwai
2009-10-09 15:17       ` Guillem Solà
2009-10-09 16:05       ` Guillem Solà
2009-10-09 16:13         ` Takashi Iwai
2009-10-13  8:48           ` Guillem Solà
2009-10-13  9:14             ` Takashi Iwai
2009-10-13  9:59               ` Guillem Solà
2009-10-13 10:06                 ` Takashi Iwai
2009-10-13 10:26                   ` Guillem Solà
2009-10-13 10:39                     ` Takashi Iwai
2009-10-13 11:28                       ` Guillem Solà
2009-10-13 11:31                         ` Takashi Iwai
2009-10-13 12:10                           ` Guillem Solà
2009-10-13 12:34                             ` Takashi Iwai
2009-10-13 14:12                               ` Guillem Solà
2009-10-13 14:20                                 ` Takashi Iwai
2009-10-13 15:01                                   ` Guillem Solà
2009-10-13 15:21                                     ` Takashi Iwai
2009-10-13 16:59                                       ` Guillem Solà
2009-10-14 15:48                                         ` Takashi Iwai
2009-10-14 16:03                                           ` Guillem Solà [this message]
2009-10-14 16:09                                             ` Takashi Iwai
2009-10-15  9:52                                               ` Guillem Solà
  -- strict thread matches above, loose matches on Subject: below --
2009-10-17 10:30 Philippe

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=4AD5F643.3050908@flumotion.com \
    --to=garanda@flumotion.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=tiwai@suse.de \
    /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