[alsa-devel] Bug 305
I tested Fedora 8 on my ThinkPad 600X. The 600X has a CS4264, and F8 uses a 2.6.23 kernel (I forget the version at the moment). The sound does not work after resume.
How should I check whether the fix for this issue is included in a kernel? Version number?
Thanks, Chris
At Thu, 9 Aug 2007 10:18:14 -0500 (CDT), chris@idlelion.net wrote:
I tested Fedora 8 on my ThinkPad 600X. The 600X has a CS4264, and F8 uses a 2.6.23 kernel (I forget the version at the moment). The sound does not work after resume.
I think it nevered worked after resume?
How should I check whether the fix for this issue is included in a kernel? Version number?
The fixes for cs46xx are already in 2.6.23-rc* kernel.
Takashi
On Thu, 9 Aug 2007, Takashi Iwai wrote:
At Thu, 9 Aug 2007 10:18:14 -0500 (CDT), chris@idlelion.net wrote:
I tested Fedora 8 on my ThinkPad 600X. The 600X has a CS4264, and F8 uses a 2.6.23 kernel (I forget the version at the moment). The sound does not work after resume.
I think it nevered worked after resume?
How should I check whether the fix for this issue is included in a kernel? Version number?
The fixes for cs46xx are already in 2.6.23-rc* kernel.
OK. That's in F8T1 stock kernel, so 305 is not fixed. Can I do anything else to help out?
Chris
At Fri, 10 Aug 2007 09:32:59 -0500 (CDT), chris@idlelion.net wrote:
On Thu, 9 Aug 2007, Takashi Iwai wrote:
At Thu, 9 Aug 2007 10:18:14 -0500 (CDT), chris@idlelion.net wrote:
I tested Fedora 8 on my ThinkPad 600X. The 600X has a CS4264, and F8 uses a 2.6.23 kernel (I forget the version at the moment). The sound does not work after resume.
I think it nevered worked after resume?
How should I check whether the fix for this issue is included in a kernel? Version number?
The fixes for cs46xx are already in 2.6.23-rc* kernel.
OK. That's in F8T1 stock kernel, so 305 is not fixed. Can I do anything else to help out?
Didn't you read my last mail?
You can build ALSA drivers externally from ALSA driver tree, at best, from HG repository. Please consult furhter on alsa-devel ML.
Takashi
On Fri, 10 Aug 2007, Takashi Iwai wrote:
At Fri, 10 Aug 2007 09:32:59 -0500 (CDT), chris@idlelion.net wrote:
On Thu, 9 Aug 2007, Takashi Iwai wrote:
At Thu, 9 Aug 2007 10:18:14 -0500 (CDT), chris@idlelion.net wrote:
I tested Fedora 8 on my ThinkPad 600X. The 600X has a CS4264, and F8 uses a 2.6.23 kernel (I forget the version at the moment). The sound does not work after resume.
I think it nevered worked after resume?
How should I check whether the fix for this issue is included in a kernel? Version number?
The fixes for cs46xx are already in 2.6.23-rc* kernel.
OK. That's in F8T1 stock kernel, so 305 is not fixed. Can I do anything else to help out?
Didn't you read my last mail?
You can build ALSA drivers externally from ALSA driver tree, at best, from HG repository. Please consult furhter on alsa-devel ML.
I did read your mail.
It is not at all clear that getting the latest build would be useful if the patch that was supposed to fix this bug is already in the kernel I'm using.
If I missed any traffic about more changes to the cs46xx driver, my apologies. I'll download the latest code as soon as my schedule allows.
Chris
At Fri, 10 Aug 2007 09:50:21 -0500 (CDT), chris@idlelion.net wrote:
On Fri, 10 Aug 2007, Takashi Iwai wrote:
At Fri, 10 Aug 2007 09:32:59 -0500 (CDT), chris@idlelion.net wrote:
On Thu, 9 Aug 2007, Takashi Iwai wrote:
At Thu, 9 Aug 2007 10:18:14 -0500 (CDT), chris@idlelion.net wrote:
I tested Fedora 8 on my ThinkPad 600X. The 600X has a CS4264, and F8 uses a 2.6.23 kernel (I forget the version at the moment). The sound does not work after resume.
I think it nevered worked after resume?
How should I check whether the fix for this issue is included in a kernel? Version number?
The fixes for cs46xx are already in 2.6.23-rc* kernel.
OK. That's in F8T1 stock kernel, so 305 is not fixed. Can I do anything else to help out?
Didn't you read my last mail?
You can build ALSA drivers externally from ALSA driver tree, at best, from HG repository. Please consult furhter on alsa-devel ML.
I did read your mail.
It is not at all clear that getting the latest build would be useful if the patch that was supposed to fix this bug is already in the kernel I'm using.
The ALSA tree is regularly changed everyday, so we need to keep the driver codes we're checking identical in both of developer and tester. 2.6.23-rc* doesn't contain the latest codes.
Once after we have both the latest codes, then we can start debugging. Also, please elaborate the symptom in the mail, instead of a number 305. Let's keep the information and proceed debugging on ML.
Takashi
participants (2)
-
chris＠idlelion.net -
Takashi Iwai