Re: [alsa-devel] REGRESSION: Webcam mic for 145f:015b not longer working with 1.0.24 and above (OK with 1.0.23)
On 27.08.2012 12:33, Kostas wrote:
On 27/08/2012 12:26 μμ, Daniel Mack wrote:
On 27.08.2012 11:00, Kostas wrote:
Hi All,
I have a 'Trust Webcam' (USB ID: 145f:015b) that comes with a microphone. The microphone works with Alsa 1.0.23 but it does not work with the latest Alsa 1.0.25 neither with Alsa 1.0.24. Apparently this is a regression.
What shall I do to figure out the source of the problem?
Here are attached my alsa-infos, with Alsa 1.0.23 (working), 1.0.24 (NOT working) and 1.0.25 (NOT working).
Can you provide dmesg protocols for both a working and a non-working case please?
Below are attached the dmesg files.
Thanks - the logs look both good, I guess the interesting messages are only generated once you try to start the stream. Can you try this?
On 27/08/2012 02:44 μμ, Daniel Mack wrote:
On 27.08.2012 12:33, Kostas wrote:
On 27/08/2012 12:26 μμ, Daniel Mack wrote:
On 27.08.2012 11:00, Kostas wrote:
Hi All,
I have a 'Trust Webcam' (USB ID: 145f:015b) that comes with a microphone. The microphone works with Alsa 1.0.23 but it does not work with the latest Alsa 1.0.25 neither with Alsa 1.0.24. Apparently this is a regression.
What shall I do to figure out the source of the problem?
Here are attached my alsa-infos, with Alsa 1.0.23 (working), 1.0.24 (NOT working) and 1.0.25 (NOT working).
Can you provide dmesg protocols for both a working and a non-working case please?
Below are attached the dmesg files.
Thanks - the logs look both good, I guess the interesting messages are only generated once you try to start the stream. Can you try this?
How i do that? I tried to make a test call in skype and also recording a video in cheese but no changes in dmesg. Is there another way to start the stream?
On 27/08/2012 06:54 μμ, Kostas wrote:
On 27/08/2012 02:44 μμ, Daniel Mack wrote:
On 27.08.2012 12:33, Kostas wrote:
On 27/08/2012 12:26 μμ, Daniel Mack wrote:
On 27.08.2012 11:00, Kostas wrote:
Hi All,
I have a 'Trust Webcam' (USB ID: 145f:015b) that comes with a microphone. The microphone works with Alsa 1.0.23 but it does not work with the latest Alsa 1.0.25 neither with Alsa 1.0.24. Apparently this is a regression.
What shall I do to figure out the source of the problem?
Here are attached my alsa-infos, with Alsa 1.0.23 (working), 1.0.24 (NOT working) and 1.0.25 (NOT working).
Can you provide dmesg protocols for both a working and a non-working case please?
Below are attached the dmesg files.
Thanks - the logs look both good, I guess the interesting messages are only generated once you try to start the stream. Can you try this?
How i do that? I tried to make a test call in skype and also recording a video in cheese but no changes in dmesg. Is there another way to start the stream?
Also tried to record voice with sound recorder...with alsa 1.0.23 recording is fine..i hear my voice when playback the file but with alsa 1.0.24 and above nothing is recorded. In both cases nothing is changed in dmesg output. What else could i do to help you out?
On 28.08.2012 00:19, Kostas wrote:
On 27/08/2012 06:54 μμ, Kostas wrote:
On 27/08/2012 02:44 μμ, Daniel Mack wrote:
On 27.08.2012 12:33, Kostas wrote:
On 27/08/2012 12:26 μμ, Daniel Mack wrote:
On 27.08.2012 11:00, Kostas wrote:
Hi All,
I have a 'Trust Webcam' (USB ID: 145f:015b) that comes with a microphone. The microphone works with Alsa 1.0.23 but it does not work with the latest Alsa 1.0.25 neither with Alsa 1.0.24. Apparently this is a regression.
What shall I do to figure out the source of the problem?
Here are attached my alsa-infos, with Alsa 1.0.23 (working), 1.0.24 (NOT working) and 1.0.25 (NOT working).
Can you provide dmesg protocols for both a working and a non-working case please?
Below are attached the dmesg files.
Thanks - the logs look both good, I guess the interesting messages are only generated once you try to start the stream. Can you try this?
How i do that? I tried to make a test call in skype and also recording a video in cheese but no changes in dmesg. Is there another way to start the stream?
Also tried to record voice with sound recorder...with alsa 1.0.23 recording is fine..i hear my voice when playback the file but with alsa 1.0.24 and above nothing is recorded. In both cases nothing is changed in dmesg output. What else could i do to help you out?
Comparing the two dmesg logs, I'm under the impression that in the second case (the newer kernel), the hda driver kicks in and creates a sound device before the usb audio driver does. Hence, the default card changes and you're recording from your internal sound card rather than the Webcam.
Could you please send the output of 'aplay -l' in both cases?
Daniel
On 28/08/2012 08:44 Ïμ, Daniel Mack wrote:
On 28.08.2012 00:19, Kostas wrote:
On 27/08/2012 06:54 μμ, Kostas wrote:
On 27/08/2012 02:44 μμ, Daniel Mack wrote:
On 27.08.2012 12:33, Kostas wrote:
On 27/08/2012 12:26 μμ, Daniel Mack wrote:
On 27.08.2012 11:00, Kostas wrote: > Hi All, > > I have a 'Trust Webcam' (USB ID: 145f:015b) that comes with a > microphone. > The microphone works with Alsa 1.0.23 but it does not work with the > latest Alsa 1.0.25 neither with Alsa 1.0.24. > Apparently this is a regression. > > What shall I do to figure out the source of the problem? > > Here are attached my alsa-infos, with Alsa 1.0.23 (working), > 1.0.24 (NOT > working) and 1.0.25 (NOT working). Can you provide dmesg protocols for both a working and a non-working case please?
Below are attached the dmesg files.
Thanks - the logs look both good, I guess the interesting messages are only generated once you try to start the stream. Can you try this?
How i do that? I tried to make a test call in skype and also recording a video in cheese but no changes in dmesg. Is there another way to start the stream?
Also tried to record voice with sound recorder...with alsa 1.0.23 recording is fine..i hear my voice when playback the file but with alsa 1.0.24 and above nothing is recorded. In both cases nothing is changed in dmesg output. What else could i do to help you out?
Comparing the two dmesg logs, I'm under the impression that in the second case (the newer kernel), the hda driver kicks in and creates a sound device before the usb audio driver does. Hence, the default card changes and you're recording from your internal sound card rather than the Webcam.
Could you please send the output of 'aplay -l' in both cases?
Daniel
Output of working case **** List of PLAYBACK Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Â Subdevices: 1/1 Â Subdevice #0: subdevice #0 card 0: SB [HDA ATI SB], device 1: AD198x Digital [AD198x Digital] Â Subdevices: 1/1 Â Subdevice #0: subdevice #0 card 2: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Â Subdevices: 1/1 Â Subdevice #0: subdevice #0
Output of non-working case (newer kernel) **** List of PLAYBACK Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Subdevices: 1/1 Subdevice #0: subdevice #0 card 0: SB [HDA ATI SB], device 1: AD198x Digital [AD198x Digital] Subdevices: 1/1 Subdevice #0: subdevice #0 card 2: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Subdevices: 1/1 Subdevice #0: subdevice #0
In a greek forum where i also submitted my problem a user noticed that in newer kernel in alsa info there is the below text card 1: Webcam [Trust 2MP Auto Focus Webcam], device 0: USB Audio [USB Audio] Subdevices:0/1
In alsa 1.0.23 alsa-info gave card 1: Webcam [Trust 2MP Auto Focus Webcam], device 0: USB Audio [USB Audio] Subdevices:1/1
I don't know if that helps.
On 28.08.2012 10:47, Kostas wrote:
On 28/08/2012 08:44 Ïμ, Daniel Mack wrote:
On 28.08.2012 00:19, Kostas wrote:
On 27/08/2012 06:54 μμ, Kostas wrote:
On 27/08/2012 02:44 μμ, Daniel Mack wrote:
On 27.08.2012 12:33, Kostas wrote:
On 27/08/2012 12:26 μμ, Daniel Mack wrote: > On 27.08.2012 11:00, Kostas wrote: >> Hi All, >> >> I have a 'Trust Webcam' (USB ID: 145f:015b) that comes with a >> microphone. >> The microphone works with Alsa 1.0.23 but it does not work with the >> latest Alsa 1.0.25 neither with Alsa 1.0.24. >> Apparently this is a regression. >> >> What shall I do to figure out the source of the problem? >> >> Here are attached my alsa-infos, with Alsa 1.0.23 (working), >> 1.0.24 (NOT >> working) and 1.0.25 (NOT working). > Can you provide dmesg protocols for both a working and a non-working > case please? > > Below are attached the dmesg files.
Thanks - the logs look both good, I guess the interesting messages are only generated once you try to start the stream. Can you try this?
How i do that? I tried to make a test call in skype and also recording a video in cheese but no changes in dmesg. Is there another way to start the stream?
Also tried to record voice with sound recorder...with alsa 1.0.23 recording is fine..i hear my voice when playback the file but with alsa 1.0.24 and above nothing is recorded. In both cases nothing is changed in dmesg output. What else could i do to help you out?
Comparing the two dmesg logs, I'm under the impression that in the second case (the newer kernel), the hda driver kicks in and creates a sound device before the usb audio driver does. Hence, the default card changes and you're recording from your internal sound card rather than the Webcam.
Could you please send the output of 'aplay -l' in both cases?
Daniel
Output of working case **** List of PLAYBACK Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Â Subdevices: 1/1 Â Subdevice #0: subdevice #0 card 0: SB [HDA ATI SB], device 1: AD198x Digital [AD198x Digital] Â Subdevices: 1/1 Â Subdevice #0: subdevice #0 card 2: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Â Subdevices: 1/1 Â Subdevice #0: subdevice #0
Sorry, there's of course no playback on a webcam. Try 'arecord -l' instead, please.
Daniel
On 28/08/2012 11:50 πμ, Daniel Mack wrote:
On 28.08.2012 10:47, Kostas wrote:
On 28/08/2012 08:44 Ïμ, Daniel Mack wrote:
On 28.08.2012 00:19, Kostas wrote:
On 27/08/2012 06:54 μμ, Kostas wrote:
On 27/08/2012 02:44 μμ, Daniel Mack wrote:
On 27.08.2012 12:33, Kostas wrote: > On 27/08/2012 12:26 μμ, Daniel Mack wrote: >> On 27.08.2012 11:00, Kostas wrote: >>> Hi All, >>> >>> I have a 'Trust Webcam' (USB ID: 145f:015b) that comes with a >>> microphone. >>> The microphone works with Alsa 1.0.23 but it does not work with the >>> latest Alsa 1.0.25 neither with Alsa 1.0.24. >>> Apparently this is a regression. >>> >>> What shall I do to figure out the source of the problem? >>> >>> Here are attached my alsa-infos, with Alsa 1.0.23 (working), >>> 1.0.24 (NOT >>> working) and 1.0.25 (NOT working). >> Can you provide dmesg protocols for both a working and a non-working >> case please? >> >> > Below are attached the dmesg files. > Thanks - the logs look both good, I guess the interesting messages are only generated once you try to start the stream. Can you try this?
How i do that? I tried to make a test call in skype and also recording a video in cheese but no changes in dmesg. Is there another way to start the stream?
Also tried to record voice with sound recorder...with alsa 1.0.23 recording is fine..i hear my voice when playback the file but with alsa 1.0.24 and above nothing is recorded. In both cases nothing is changed in dmesg output. What else could i do to help you out?
Comparing the two dmesg logs, I'm under the impression that in the second case (the newer kernel), the hda driver kicks in and creates a sound device before the usb audio driver does. Hence, the default card changes and you're recording from your internal sound card rather than the Webcam.
Could you please send the output of 'aplay -l' in both cases?
Daniel
Output of working case **** List of PLAYBACK Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Â Subdevices: 1/1 Â Subdevice #0: subdevice #0 card 0: SB [HDA ATI SB], device 1: AD198x Digital [AD198x Digital] Â Subdevices: 1/1 Â Subdevice #0: subdevice #0 card 2: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Â Subdevices: 1/1 Â Subdevice #0: subdevice #0
Sorry, there's of course no playback on a webcam. Try 'arecord -l' instead, please.
Daniel
Output of non-working case **** List of CAPTURE Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Subdevices: 3/3 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 card 1: Webcam [Trust 2MP Auto Focus Webcam], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0
Output of working case **** List of CAPTURE Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Subdevices: 3/3 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 card 1: default [Trust 2MP Auto Focus Webcam ], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0
On 28.08.2012 10:56, Kostas wrote:
On 28/08/2012 11:50 πμ, Daniel Mack wrote:
On 28.08.2012 10:47, Kostas wrote:
On 28/08/2012 08:44 Ïμ, Daniel Mack wrote:
On 28.08.2012 00:19, Kostas wrote:
On 27/08/2012 06:54 μμ, Kostas wrote:
On 27/08/2012 02:44 μμ, Daniel Mack wrote: > On 27.08.2012 12:33, Kostas wrote: >> On 27/08/2012 12:26 μμ, Daniel Mack wrote: >>> On 27.08.2012 11:00, Kostas wrote: >>>> Hi All, >>>> >>>> I have a 'Trust Webcam' (USB ID: 145f:015b) that comes with a >>>> microphone. >>>> The microphone works with Alsa 1.0.23 but it does not work with the >>>> latest Alsa 1.0.25 neither with Alsa 1.0.24. >>>> Apparently this is a regression. >>>> >>>> What shall I do to figure out the source of the problem? >>>> >>>> Here are attached my alsa-infos, with Alsa 1.0.23 (working), >>>> 1.0.24 (NOT >>>> working) and 1.0.25 (NOT working). >>> Can you provide dmesg protocols for both a working and a non-working >>> case please? >>> >>> >> Below are attached the dmesg files. >> > Thanks - the logs look both good, I guess the interesting messages are > only generated once you try to start the stream. Can you try this? How i do that? I tried to make a test call in skype and also recording a video in cheese but no changes in dmesg. Is there another way to start the stream?
Also tried to record voice with sound recorder...with alsa 1.0.23 recording is fine..i hear my voice when playback the file but with alsa 1.0.24 and above nothing is recorded. In both cases nothing is changed in dmesg output. What else could i do to help you out?
Comparing the two dmesg logs, I'm under the impression that in the second case (the newer kernel), the hda driver kicks in and creates a sound device before the usb audio driver does. Hence, the default card changes and you're recording from your internal sound card rather than the Webcam.
Could you please send the output of 'aplay -l' in both cases?
Daniel
Output of working case **** List of PLAYBACK Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Â Subdevices: 1/1 Â Subdevice #0: subdevice #0 card 0: SB [HDA ATI SB], device 1: AD198x Digital [AD198x Digital] Â Subdevices: 1/1 Â Subdevice #0: subdevice #0 card 2: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Â Subdevices: 1/1 Â Subdevice #0: subdevice #0
Sorry, there's of course no playback on a webcam. Try 'arecord -l' instead, please.
Daniel
Output of non-working case **** List of CAPTURE Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Subdevices: 3/3 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 card 1: Webcam [Trust 2MP Auto Focus Webcam], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0
Output of working case **** List of CAPTURE Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Subdevices: 3/3 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 card 1: default [Trust 2MP Auto Focus Webcam ], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0
Try 'arecord -f cd -Dplughw:1 foo.wav' and see if that works. For whatever reason, the webcam is not the default in the non-working case. Are you using the same userspace and configs in both cases?
Daniel
On 28/08/2012 12:06 μμ, Daniel Mack wrote:
On 28.08.2012 10:56, Kostas wrote:
On 28/08/2012 11:50 Ïμ, Daniel Mack wrote:
On 28.08.2012 10:47, Kostas wrote:
On 28/08/2012 08:44 ÃÂü, Daniel Mack wrote:
On 28.08.2012 00:19, Kostas wrote:
On 27/08/2012 06:54 üü, Kostas wrote: > On 27/08/2012 02:44 üü, Daniel Mack wrote: >> On 27.08.2012 12:33, Kostas wrote: >>> On 27/08/2012 12:26 üü, Daniel Mack wrote: >>>> On 27.08.2012 11:00, Kostas wrote: >>>>> Hi All, >>>>> >>>>> I have a 'Trust Webcam' (USB ID: 145f:015b) that comes with a >>>>> microphone. >>>>> The microphone works with Alsa 1.0.23 but it does not work with the >>>>> latest Alsa 1.0.25 neither with Alsa 1.0.24. >>>>> Apparently this is a regression. >>>>> >>>>> What shall I do to figure out the source of the problem? >>>>> >>>>> Here are attached my alsa-infos, with Alsa 1.0.23 (working), >>>>> 1.0.24 (NOT >>>>> working) and 1.0.25 (NOT working). >>>> Can you provide dmesg protocols for both a working and a non-working >>>> case please? >>>> >>>> >>> Below are attached the dmesg files. >>> >> Thanks - the logs look both good, I guess the interesting messages are >> only generated once you try to start the stream. Can you try this? > How i do that? > I tried to make a test call in skype and also recording a video in > cheese but no changes in dmesg. > Is there another way to start the stream? Also tried to record voice with sound recorder...with alsa 1.0.23 recording is fine..i hear my voice when playback the file but with alsa 1.0.24 and above nothing is recorded. In both cases nothing is changed in dmesg output. What else could i do to help you out?
Comparing the two dmesg logs, I'm under the impression that in the second case (the newer kernel), the hda driver kicks in and creates a sound device before the usb audio driver does. Hence, the default card changes and you're recording from your internal sound card rather than the Webcam.
Could you please send the output of 'aplay -l' in both cases?
Daniel
Output of working case **** List of PLAYBACK Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Ã Subdevices: 1/1 Ã Subdevice #0: subdevice #0 card 0: SB [HDA ATI SB], device 1: AD198x Digital [AD198x Digital] Ã Subdevices: 1/1 Ã Subdevice #0: subdevice #0 card 2: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Ã Subdevices: 1/1 Ã Subdevice #0: subdevice #0
Sorry, there's of course no playback on a webcam. Try 'arecord -l' instead, please.
Daniel
Output of non-working case **** List of CAPTURE Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Subdevices: 3/3 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 card 1: Webcam [Trust 2MP Auto Focus Webcam], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0
Output of working case **** List of CAPTURE Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Subdevices: 3/3 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 card 1: default [Trust 2MP Auto Focus Webcam ], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0
Try 'arecord -f cd -Dplughw:1 foo.wav' and see if that works. For whatever reason, the webcam is not the default in the non-working case. Are you using the same userspace and configs in both cases?
Daniel
Unfortunately it doesn't work...voice is recorded only in 1.0.23 alsa version. In above version nothing is recorded. I use the same Ubuntu release just the kernel changes 1.0.23 alsa is in kernel 2.6.38 newer alsa versions that don't work are in newer kernels.
On 28.08.2012 11:18, Kostas wrote:
On 28/08/2012 12:06 μμ, Daniel Mack wrote:
On 28.08.2012 10:56, Kostas wrote:
On 28/08/2012 11:50 Ïμ, Daniel Mack wrote:
On 28.08.2012 10:47, Kostas wrote:
On 28/08/2012 08:44 ÃÂü, Daniel Mack wrote:
On 28.08.2012 00:19, Kostas wrote: > On 27/08/2012 06:54 üü, Kostas wrote: >> On 27/08/2012 02:44 üü, Daniel Mack wrote: >>> On 27.08.2012 12:33, Kostas wrote: >>>> On 27/08/2012 12:26 üü, Daniel Mack wrote: >>>>> On 27.08.2012 11:00, Kostas wrote: >>>>>> Hi All, >>>>>> >>>>>> I have a 'Trust Webcam' (USB ID: 145f:015b) that comes with a >>>>>> microphone. >>>>>> The microphone works with Alsa 1.0.23 but it does not work with the >>>>>> latest Alsa 1.0.25 neither with Alsa 1.0.24. >>>>>> Apparently this is a regression. >>>>>> >>>>>> What shall I do to figure out the source of the problem? >>>>>> >>>>>> Here are attached my alsa-infos, with Alsa 1.0.23 (working), >>>>>> 1.0.24 (NOT >>>>>> working) and 1.0.25 (NOT working). >>>>> Can you provide dmesg protocols for both a working and a non-working >>>>> case please? >>>>> >>>>> >>>> Below are attached the dmesg files. >>>> >>> Thanks - the logs look both good, I guess the interesting messages are >>> only generated once you try to start the stream. Can you try this? >> How i do that? >> I tried to make a test call in skype and also recording a video in >> cheese but no changes in dmesg. >> Is there another way to start the stream? > Also tried to record voice with sound recorder...with alsa 1.0.23 > recording is fine..i hear my voice when playback the file but with alsa > 1.0.24 and above nothing is recorded. > In both cases nothing is changed in dmesg output. > What else could i do to help you out? > Comparing the two dmesg logs, I'm under the impression that in the second case (the newer kernel), the hda driver kicks in and creates a sound device before the usb audio driver does. Hence, the default card changes and you're recording from your internal sound card rather than the Webcam.
Could you please send the output of 'aplay -l' in both cases?
Daniel
Output of working case **** List of PLAYBACK Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Ã Subdevices: 1/1 Ã Subdevice #0: subdevice #0 card 0: SB [HDA ATI SB], device 1: AD198x Digital [AD198x Digital] Ã Subdevices: 1/1 Ã Subdevice #0: subdevice #0 card 2: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] Ã Subdevices: 1/1 Ã Subdevice #0: subdevice #0
Sorry, there's of course no playback on a webcam. Try 'arecord -l' instead, please.
Daniel
Output of non-working case **** List of CAPTURE Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Subdevices: 3/3 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 card 1: Webcam [Trust 2MP Auto Focus Webcam], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0
Output of working case **** List of CAPTURE Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Subdevices: 3/3 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 card 1: default [Trust 2MP Auto Focus Webcam ], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0
Try 'arecord -f cd -Dplughw:1 foo.wav' and see if that works. For whatever reason, the webcam is not the default in the non-working case. Are you using the same userspace and configs in both cases?
Daniel
Unfortunately it doesn't work...voice is recorded only in 1.0.23 alsa version. In above version nothing is recorded. I use the same Ubuntu release just the kernel changes 1.0.23 alsa is in kernel 2.6.38 newer alsa versions that don't work are in newer kernels.
I still think it is all related to configs and settings. Can you please go check all relevant volume settings and routing switches with amixer or alsamixer? The fact that the default changes tells me that something's different in the behaviour in which ALSA handles the devices.
Also note that 1.0.24 is rather ancient already, and while the driver has seen quiet some refactoring lately, I haven't heard about regressions in that version yet - and I'm sure we would have gotten a whole lot of reports if there was such a tremendous breakage. And there's no signs of errors in the kernel logs either. But you never know, of course.
Daniel
On 28/08/2012 12:30 μμ, Daniel Mack wrote:
On 28.08.2012 11:18, Kostas wrote:
On 28/08/2012 12:06 μμ, Daniel Mack wrote:
On 28.08.2012 10:56, Kostas wrote:
On 28/08/2012 11:50 Ïμ, Daniel Mack wrote:
On 28.08.2012 10:47, Kostas wrote:
On 28/08/2012 08:44 ÃÂü, Daniel Mack wrote: > On 28.08.2012 00:19, Kostas wrote: >> On 27/08/2012 06:54 üü, Kostas wrote: >>> On 27/08/2012 02:44 üü, Daniel Mack wrote: >>>> On 27.08.2012 12:33, Kostas wrote: >>>>> On 27/08/2012 12:26 üü, Daniel Mack wrote: >>>>>> On 27.08.2012 11:00, Kostas wrote: >>>>>>> Hi All, >>>>>>> >>>>>>> I have a 'Trust Webcam' (USB ID: 145f:015b) that comes with a >>>>>>> microphone. >>>>>>> The microphone works with Alsa 1.0.23 but it does not work with the >>>>>>> latest Alsa 1.0.25 neither with Alsa 1.0.24. >>>>>>> Apparently this is a regression. >>>>>>> >>>>>>> What shall I do to figure out the source of the problem? >>>>>>> >>>>>>> Here are attached my alsa-infos, with Alsa 1.0.23 (working), >>>>>>> 1.0.24 (NOT >>>>>>> working) and 1.0.25 (NOT working). >>>>>> Can you provide dmesg protocols for both a working and a non-working >>>>>> case please? >>>>>> >>>>>> >>>>> Below are attached the dmesg files. >>>>> >>>> Thanks - the logs look both good, I guess the interesting messages are >>>> only generated once you try to start the stream. Can you try this? >>> How i do that? >>> I tried to make a test call in skype and also recording a video in >>> cheese but no changes in dmesg. >>> Is there another way to start the stream? >> Also tried to record voice with sound recorder...with alsa 1.0.23 >> recording is fine..i hear my voice when playback the file but with alsa >> 1.0.24 and above nothing is recorded. >> In both cases nothing is changed in dmesg output. >> What else could i do to help you out? >> > Comparing the two dmesg logs, I'm under the impression that in the > second case (the newer kernel), the hda driver kicks in and creates a > sound device before the usb audio driver does. Hence, the default card > changes and you're recording from your internal sound card rather than > the Webcam. > > Could you please send the output of 'aplay -l' in both cases? > > > Daniel > Output of working case **** List of PLAYBACK Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] à Subdevices: 1/1 à Subdevice #0: subdevice #0 card 0: SB [HDA ATI SB], device 1: AD198x Digital [AD198x Digital] à Subdevices: 1/1 à Subdevice #0: subdevice #0 card 2: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] à Subdevices: 1/1 à Subdevice #0: subdevice #0
Sorry, there's of course no playback on a webcam. Try 'arecord -l' instead, please.
Daniel
Output of non-working case **** List of CAPTURE Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Subdevices: 3/3 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 card 1: Webcam [Trust 2MP Auto Focus Webcam], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0
Output of working case **** List of CAPTURE Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Subdevices: 3/3 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 card 1: default [Trust 2MP Auto Focus Webcam ], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0
Try 'arecord -f cd -Dplughw:1 foo.wav' and see if that works. For whatever reason, the webcam is not the default in the non-working case. Are you using the same userspace and configs in both cases?
Daniel
Unfortunately it doesn't work...voice is recorded only in 1.0.23 alsa version. In above version nothing is recorded. I use the same Ubuntu release just the kernel changes 1.0.23 alsa is in kernel 2.6.38 newer alsa versions that don't work are in newer kernels.
I still think it is all related to configs and settings. Can you please go check all relevant volume settings and routing switches with amixer or alsamixer? The fact that the default changes tells me that something's different in the behaviour in which ALSA handles the devices.
Also note that 1.0.24 is rather ancient already, and while the driver has seen quiet some refactoring lately, I haven't heard about regressions in that version yet - and I'm sure we would have gotten a whole lot of reports if there was such a tremendous breakage. And there's no signs of errors in the kernel logs either. But you never know, of course.
Daniel
Alsamixer working case http://imagebin.org/226143 Alsamixer non-working case http://imagebin.org/226142
I also attach amixer output for both cases.
On 28.08.2012 11:47, Kostas wrote:
On 28/08/2012 12:30 μμ, Daniel Mack wrote:
On 28.08.2012 11:18, Kostas wrote:
On 28/08/2012 12:06 μμ, Daniel Mack wrote:
On 28.08.2012 10:56, Kostas wrote:
On 28/08/2012 11:50 Ïμ, Daniel Mack wrote:
On 28.08.2012 10:47, Kostas wrote: > On 28/08/2012 08:44 ÃÂü, Daniel Mack wrote: >> On 28.08.2012 00:19, Kostas wrote: >>> On 27/08/2012 06:54 üü, Kostas wrote: >>>> On 27/08/2012 02:44 üü, Daniel Mack wrote: >>>>> On 27.08.2012 12:33, Kostas wrote: >>>>>> On 27/08/2012 12:26 üü, Daniel Mack wrote: >>>>>>> On 27.08.2012 11:00, Kostas wrote: >>>>>>>> Hi All, >>>>>>>> >>>>>>>> I have a 'Trust Webcam' (USB ID: 145f:015b) that comes with a >>>>>>>> microphone. >>>>>>>> The microphone works with Alsa 1.0.23 but it does not work with the >>>>>>>> latest Alsa 1.0.25 neither with Alsa 1.0.24. >>>>>>>> Apparently this is a regression. >>>>>>>> >>>>>>>> What shall I do to figure out the source of the problem? >>>>>>>> >>>>>>>> Here are attached my alsa-infos, with Alsa 1.0.23 (working), >>>>>>>> 1.0.24 (NOT >>>>>>>> working) and 1.0.25 (NOT working). >>>>>>> Can you provide dmesg protocols for both a working and a non-working >>>>>>> case please? >>>>>>> >>>>>>> >>>>>> Below are attached the dmesg files. >>>>>> >>>>> Thanks - the logs look both good, I guess the interesting messages are >>>>> only generated once you try to start the stream. Can you try this? >>>> How i do that? >>>> I tried to make a test call in skype and also recording a video in >>>> cheese but no changes in dmesg. >>>> Is there another way to start the stream? >>> Also tried to record voice with sound recorder...with alsa 1.0.23 >>> recording is fine..i hear my voice when playback the file but with alsa >>> 1.0.24 and above nothing is recorded. >>> In both cases nothing is changed in dmesg output. >>> What else could i do to help you out? >>> >> Comparing the two dmesg logs, I'm under the impression that in the >> second case (the newer kernel), the hda driver kicks in and creates a >> sound device before the usb audio driver does. Hence, the default card >> changes and you're recording from your internal sound card rather than >> the Webcam. >> >> Could you please send the output of 'aplay -l' in both cases? >> >> >> Daniel >> > Output of working case > **** List of PLAYBACK Hardware Devices **** > card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] > à Subdevices: 1/1 > à Subdevice #0: subdevice #0 > card 0: SB [HDA ATI SB], device 1: AD198x Digital [AD198x Digital] > à Subdevices: 1/1 > à Subdevice #0: subdevice #0 > card 2: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] > à Subdevices: 1/1 > à Subdevice #0: subdevice #0 Sorry, there's of course no playback on a webcam. Try 'arecord -l' instead, please.
Daniel
Output of non-working case **** List of CAPTURE Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Subdevices: 3/3 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 card 1: Webcam [Trust 2MP Auto Focus Webcam], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0
Output of working case **** List of CAPTURE Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Subdevices: 3/3 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 card 1: default [Trust 2MP Auto Focus Webcam ], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0
Try 'arecord -f cd -Dplughw:1 foo.wav' and see if that works. For whatever reason, the webcam is not the default in the non-working case. Are you using the same userspace and configs in both cases?
Daniel
Unfortunately it doesn't work...voice is recorded only in 1.0.23 alsa version. In above version nothing is recorded. I use the same Ubuntu release just the kernel changes 1.0.23 alsa is in kernel 2.6.38 newer alsa versions that don't work are in newer kernels.
I still think it is all related to configs and settings. Can you please go check all relevant volume settings and routing switches with amixer or alsamixer? The fact that the default changes tells me that something's different in the behaviour in which ALSA handles the devices.
Also note that 1.0.24 is rather ancient already, and while the driver has seen quiet some refactoring lately, I haven't heard about regressions in that version yet - and I'm sure we would have gotten a whole lot of reports if there was such a tremendous breakage. And there's no signs of errors in the kernel logs either. But you never know, of course.
Daniel
Alsamixer working case http://imagebin.org/226143 Alsamixer non-working case http://imagebin.org/226142
I also attach amixer output for both cases.
Both in the images and in the text output you seem to have missed pointing amixer/alsamixer the correct device. alsamixer is also in the playback pane, which doesn't exist for the Webcam.
Try 'alsamixer -c1 -V capture'
On 28/08/2012 12:55 μμ, Daniel Mack wrote:
On 28.08.2012 11:47, Kostas wrote:
On 28/08/2012 12:30 μμ, Daniel Mack wrote:
On 28.08.2012 11:18, Kostas wrote:
On 28/08/2012 12:06 μμ, Daniel Mack wrote:
On 28.08.2012 10:56, Kostas wrote:
On 28/08/2012 11:50 Ïμ, Daniel Mack wrote: > On 28.08.2012 10:47, Kostas wrote: >> On 28/08/2012 08:44 ÃÂü, Daniel Mack wrote: >>> On 28.08.2012 00:19, Kostas wrote: >>>> On 27/08/2012 06:54 üü, Kostas wrote: >>>>> On 27/08/2012 02:44 üü, Daniel Mack wrote: >>>>>> On 27.08.2012 12:33, Kostas wrote: >>>>>>> On 27/08/2012 12:26 üü, Daniel Mack wrote: >>>>>>>> On 27.08.2012 11:00, Kostas wrote: >>>>>>>>> Hi All, >>>>>>>>> >>>>>>>>> I have a 'Trust Webcam' (USB ID: 145f:015b) that comes with a >>>>>>>>> microphone. >>>>>>>>> The microphone works with Alsa 1.0.23 but it does not work with the >>>>>>>>> latest Alsa 1.0.25 neither with Alsa 1.0.24. >>>>>>>>> Apparently this is a regression. >>>>>>>>> >>>>>>>>> What shall I do to figure out the source of the problem? >>>>>>>>> >>>>>>>>> Here are attached my alsa-infos, with Alsa 1.0.23 (working), >>>>>>>>> 1.0.24 (NOT >>>>>>>>> working) and 1.0.25 (NOT working). >>>>>>>> Can you provide dmesg protocols for both a working and a non-working >>>>>>>> case please? >>>>>>>> >>>>>>>> >>>>>>> Below are attached the dmesg files. >>>>>>> >>>>>> Thanks - the logs look both good, I guess the interesting messages are >>>>>> only generated once you try to start the stream. Can you try this? >>>>> How i do that? >>>>> I tried to make a test call in skype and also recording a video in >>>>> cheese but no changes in dmesg. >>>>> Is there another way to start the stream? >>>> Also tried to record voice with sound recorder...with alsa 1.0.23 >>>> recording is fine..i hear my voice when playback the file but with alsa >>>> 1.0.24 and above nothing is recorded. >>>> In both cases nothing is changed in dmesg output. >>>> What else could i do to help you out? >>>> >>> Comparing the two dmesg logs, I'm under the impression that in the >>> second case (the newer kernel), the hda driver kicks in and creates a >>> sound device before the usb audio driver does. Hence, the default card >>> changes and you're recording from your internal sound card rather than >>> the Webcam. >>> >>> Could you please send the output of 'aplay -l' in both cases? >>> >>> >>> Daniel >>> >> Output of working case >> **** List of PLAYBACK Hardware Devices **** >> card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] >> à Subdevices: 1/1 >> à Subdevice #0: subdevice #0 >> card 0: SB [HDA ATI SB], device 1: AD198x Digital [AD198x Digital] >> à Subdevices: 1/1 >> à Subdevice #0: subdevice #0 >> card 2: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] >> à Subdevices: 1/1 >> à Subdevice #0: subdevice #0 > Sorry, there's of course no playback on a webcam. Try 'arecord -l' > instead, please. > > > Daniel > Output of non-working case **** List of CAPTURE Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Subdevices: 3/3 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 card 1: Webcam [Trust 2MP Auto Focus Webcam], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0
Output of working case **** List of CAPTURE Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Subdevices: 3/3 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 card 1: default [Trust 2MP Auto Focus Webcam ], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0
Try 'arecord -f cd -Dplughw:1 foo.wav' and see if that works. For whatever reason, the webcam is not the default in the non-working case. Are you using the same userspace and configs in both cases?
Daniel
Unfortunately it doesn't work...voice is recorded only in 1.0.23 alsa version. In above version nothing is recorded. I use the same Ubuntu release just the kernel changes 1.0.23 alsa is in kernel 2.6.38 newer alsa versions that don't work are in newer kernels.
I still think it is all related to configs and settings. Can you please go check all relevant volume settings and routing switches with amixer or alsamixer? The fact that the default changes tells me that something's different in the behaviour in which ALSA handles the devices.
Also note that 1.0.24 is rather ancient already, and while the driver has seen quiet some refactoring lately, I haven't heard about regressions in that version yet - and I'm sure we would have gotten a whole lot of reports if there was such a tremendous breakage. And there's no signs of errors in the kernel logs either. But you never know, of course.
Daniel
Alsamixer working case http://imagebin.org/226143 Alsamixer non-working case http://imagebin.org/226142
I also attach amixer output for both cases.
Both in the images and in the text output you seem to have missed pointing amixer/alsamixer the correct device. alsamixer is also in the playback pane, which doesn't exist for the Webcam.
Try 'alsamixer -c1 -V capture'
working http://imagebin.org/226212 non working http://imagebin.org/226214
Looks the same to me...except dB gain I can't figure out how to point amixer to Webcam.
On 28/08/2012 12:55 μμ, Daniel Mack wrote:
On 28.08.2012 11:47, Kostas wrote:
On 28/08/2012 12:30 μμ, Daniel Mack wrote:
On 28.08.2012 11:18, Kostas wrote:
On 28/08/2012 12:06 üü, Daniel Mack wrote:
On 28.08.2012 10:56, Kostas wrote:
On 28/08/2012 11:50 ÃÂü, Daniel Mack wrote: > On 28.08.2012 10:47, Kostas wrote: >> On 28/08/2012 08:44 ÃÂÃÂÃÂü, Daniel Mack wrote: >>> On 28.08.2012 00:19, Kostas wrote: >>>> On 27/08/2012 06:54 ÃÂüÃÂü, Kostas wrote: >>>>> On 27/08/2012 02:44 ÃÂüÃÂü, Daniel Mack wrote: >>>>>> On 27.08.2012 12:33, Kostas wrote: >>>>>>> On 27/08/2012 12:26 ÃÂüÃÂü, Daniel Mack wrote: >>>>>>>> On 27.08.2012 11:00, Kostas wrote: >>>>>>>>> Hi All, >>>>>>>>> >>>>>>>>> I have a 'Trust Webcam' (USB ID: 145f:015b) that comes with a >>>>>>>>> microphone. >>>>>>>>> The microphone works with Alsa 1.0.23 but it does not work with the >>>>>>>>> latest Alsa 1.0.25 neither with Alsa 1.0.24. >>>>>>>>> Apparently this is a regression. >>>>>>>>> >>>>>>>>> What shall I do to figure out the source of the problem? >>>>>>>>> >>>>>>>>> Here are attached my alsa-infos, with Alsa 1.0.23 (working), >>>>>>>>> 1.0.24 (NOT >>>>>>>>> working) and 1.0.25 (NOT working). >>>>>>>> Can you provide dmesg protocols for both a working and a non-working >>>>>>>> case please? >>>>>>>> >>>>>>>> >>>>>>> Below are attached the dmesg files. >>>>>>> >>>>>> Thanks - the logs look both good, I guess the interesting messages are >>>>>> only generated once you try to start the stream. Can you try this? >>>>> How i do that? >>>>> I tried to make a test call in skype and also recording a video in >>>>> cheese but no changes in dmesg. >>>>> Is there another way to start the stream? >>>> Also tried to record voice with sound recorder...with alsa 1.0.23 >>>> recording is fine..i hear my voice when playback the file but with alsa >>>> 1.0.24 and above nothing is recorded. >>>> In both cases nothing is changed in dmesg output. >>>> What else could i do to help you out? >>>> >>> Comparing the two dmesg logs, I'm under the impression that in the >>> second case (the newer kernel), the hda driver kicks in and creates a >>> sound device before the usb audio driver does. Hence, the default card >>> changes and you're recording from your internal sound card rather than >>> the Webcam. >>> >>> Could you please send the output of 'aplay -l' in both cases? >>> >>> >>> Daniel >>> >> Output of working case >> **** List of PLAYBACK Hardware Devices **** >> card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] >> àSubdevices: 1/1 >> àSubdevice #0: subdevice #0 >> card 0: SB [HDA ATI SB], device 1: AD198x Digital [AD198x Digital] >> àSubdevices: 1/1 >> àSubdevice #0: subdevice #0 >> card 2: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] >> àSubdevices: 1/1 >> àSubdevice #0: subdevice #0 > Sorry, there's of course no playback on a webcam. Try 'arecord -l' > instead, please. > > > Daniel > Output of non-working case **** List of CAPTURE Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Subdevices: 3/3 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 card 1: Webcam [Trust 2MP Auto Focus Webcam], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0
Output of working case **** List of CAPTURE Hardware Devices **** card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] Subdevices: 3/3 Subdevice #0: subdevice #0 Subdevice #1: subdevice #1 Subdevice #2: subdevice #2 card 1: default [Trust 2MP Auto Focus Webcam ], device 0: USB Audio [USB Audio] Subdevices: 1/1 Subdevice #0: subdevice #0
Try 'arecord -f cd -Dplughw:1 foo.wav' and see if that works. For whatever reason, the webcam is not the default in the non-working case. Are you using the same userspace and configs in both cases?
Daniel
Unfortunately it doesn't work...voice is recorded only in 1.0.23 alsa version. In above version nothing is recorded. I use the same Ubuntu release just the kernel changes 1.0.23 alsa is in kernel 2.6.38 newer alsa versions that don't work are in newer kernels.
I still think it is all related to configs and settings. Can you please go check all relevant volume settings and routing switches with amixer or alsamixer? The fact that the default changes tells me that something's different in the behaviour in which ALSA handles the devices.
Also note that 1.0.24 is rather ancient already, and while the driver has seen quiet some refactoring lately, I haven't heard about regressions in that version yet - and I'm sure we would have gotten a whole lot of reports if there was such a tremendous breakage. And there's no signs of errors in the kernel logs either. But you never know, of course.
Daniel
Alsamixer working casehttp://imagebin.org/226143 Alsamixer non-working casehttp://imagebin.org/226142
I also attach amixer output for both cases.
Both in the images and in the text output you seem to have missed pointing amixer/alsamixer the correct device. alsamixer is also in the playback pane, which doesn't exist for the Webcam.
Try 'alsamixer -c1 -V capture'
I finally figured it out with amixer command non working version gives me this output
kostas@kostas-home:~$ amixer -c1 Simple mixer control 'Mic',0  Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum  Capture channels: Mono  Limits: Capture 0 - 4096  Mono: Capture 2723 [66%] [10.63dB] [on]
The working version gives this output kostas@kostas-home:~$ amixer -c1 Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 4096 Mono: Capture 4096 [100%] [16.00dB] [on]
On 29.08.2012 00:16, Kostas wrote:
On 28/08/2012 12:55 μμ, Daniel Mack wrote:
On 28.08.2012 11:47, Kostas wrote:
On 28/08/2012 12:30 μμ, Daniel Mack wrote:
On 28.08.2012 11:18, Kostas wrote:
On 28/08/2012 12:06 üü, Daniel Mack wrote:
On 28.08.2012 10:56, Kostas wrote: > On 28/08/2012 11:50 ÃÂü, Daniel Mack wrote: >> On 28.08.2012 10:47, Kostas wrote: >>> On 28/08/2012 08:44 ÃÂÃÂÃÂü, Daniel Mack wrote: >>>> On 28.08.2012 00:19, Kostas wrote: >>>>> On 27/08/2012 06:54 ÃÂüÃÂü, Kostas wrote: >>>>>> On 27/08/2012 02:44 ÃÂüÃÂü, Daniel Mack wrote: >>>>>>> On 27.08.2012 12:33, Kostas wrote: >>>>>>>> On 27/08/2012 12:26 ÃÂüÃÂü, Daniel Mack wrote: >>>>>>>>> On 27.08.2012 11:00, Kostas wrote: >>>>>>>>>> Hi All, >>>>>>>>>> >>>>>>>>>> I have a 'Trust Webcam' (USB ID: 145f:015b) that comes with a >>>>>>>>>> microphone. >>>>>>>>>> The microphone works with Alsa 1.0.23 but it does not work with the >>>>>>>>>> latest Alsa 1.0.25 neither with Alsa 1.0.24. >>>>>>>>>> Apparently this is a regression. >>>>>>>>>> >>>>>>>>>> What shall I do to figure out the source of the problem? >>>>>>>>>> >>>>>>>>>> Here are attached my alsa-infos, with Alsa 1.0.23 (working), >>>>>>>>>> 1.0.24 (NOT >>>>>>>>>> working) and 1.0.25 (NOT working). >>>>>>>>> Can you provide dmesg protocols for both a working and a non-working >>>>>>>>> case please? >>>>>>>>> >>>>>>>>> >>>>>>>> Below are attached the dmesg files. >>>>>>>> >>>>>>> Thanks - the logs look both good, I guess the interesting messages are >>>>>>> only generated once you try to start the stream. Can you try this? >>>>>> How i do that? >>>>>> I tried to make a test call in skype and also recording a video in >>>>>> cheese but no changes in dmesg. >>>>>> Is there another way to start the stream? >>>>> Also tried to record voice with sound recorder...with alsa 1.0.23 >>>>> recording is fine..i hear my voice when playback the file but with alsa >>>>> 1.0.24 and above nothing is recorded. >>>>> In both cases nothing is changed in dmesg output. >>>>> What else could i do to help you out? >>>>> >>>> Comparing the two dmesg logs, I'm under the impression that in the >>>> second case (the newer kernel), the hda driver kicks in and creates a >>>> sound device before the usb audio driver does. Hence, the default card >>>> changes and you're recording from your internal sound card rather than >>>> the Webcam. >>>> >>>> Could you please send the output of 'aplay -l' in both cases? >>>> >>>> >>>> Daniel >>>> >>> Output of working case >>> **** List of PLAYBACK Hardware Devices **** >>> card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] >>> àSubdevices: 1/1 >>> àSubdevice #0: subdevice #0 >>> card 0: SB [HDA ATI SB], device 1: AD198x Digital [AD198x Digital] >>> àSubdevices: 1/1 >>> àSubdevice #0: subdevice #0 >>> card 2: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] >>> àSubdevices: 1/1 >>> àSubdevice #0: subdevice #0 >> Sorry, there's of course no playback on a webcam. Try 'arecord -l' >> instead, please. >> >> >> Daniel >> > Output of non-working case > **** List of CAPTURE Hardware Devices **** > card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] > Subdevices: 3/3 > Subdevice #0: subdevice #0 > Subdevice #1: subdevice #1 > Subdevice #2: subdevice #2 > card 1: Webcam [Trust 2MP Auto Focus Webcam], device 0: USB Audio [USB > Audio] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > > > Output of working case > **** List of CAPTURE Hardware Devices **** > card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] > Subdevices: 3/3 > Subdevice #0: subdevice #0 > Subdevice #1: subdevice #1 > Subdevice #2: subdevice #2 > card 1: default [Trust 2MP Auto Focus Webcam ], device 0: USB Audio [USB > Audio] > Subdevices: 1/1 > Subdevice #0: subdevice #0 > Try 'arecord -f cd -Dplughw:1 foo.wav' and see if that works. For whatever reason, the webcam is not the default in the non-working case. Are you using the same userspace and configs in both cases?
Daniel
Unfortunately it doesn't work...voice is recorded only in 1.0.23 alsa version. In above version nothing is recorded. I use the same Ubuntu release just the kernel changes 1.0.23 alsa is in kernel 2.6.38 newer alsa versions that don't work are in newer kernels.
I still think it is all related to configs and settings. Can you please go check all relevant volume settings and routing switches with amixer or alsamixer? The fact that the default changes tells me that something's different in the behaviour in which ALSA handles the devices.
Also note that 1.0.24 is rather ancient already, and while the driver has seen quiet some refactoring lately, I haven't heard about regressions in that version yet - and I'm sure we would have gotten a whole lot of reports if there was such a tremendous breakage. And there's no signs of errors in the kernel logs either. But you never know, of course.
Daniel
Alsamixer working casehttp://imagebin.org/226143 Alsamixer non-working casehttp://imagebin.org/226142
I also attach amixer output for both cases.
Both in the images and in the text output you seem to have missed pointing amixer/alsamixer the correct device. alsamixer is also in the playback pane, which doesn't exist for the Webcam.
Try 'alsamixer -c1 -V capture'
I finally figured it out with amixer command non working version gives me this output
kostas@kostas-home:~$ amixer -c1 Simple mixer control 'Mic',0  Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum  Capture channels: Mono  Limits: Capture 0 - 4096  Mono: Capture 2723 [66%] [10.63dB] [on]
The working version gives this output kostas@kostas-home:~$ amixer -c1 Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 4096 Mono: Capture 4096 [100%] [16.00dB] [on]
Ok, thanks. In the given case, I have to ask you to do a git bisect. That will point us to the commit that causes your problems. Sorry that I can't help you any further right now, it's just unclear which commit in the ancient history causes your problem.
See here for instructions on how to do that:
https://www.kernel.org/pub/software/scm/git/docs/git-bisect.html http://git-scm.com/book/en/Git-Tools-Debugging-with-Git
Thanks for your help and patience, Daniel
On 29/08/2012 01:51 πμ, Daniel Mack wrote:
On 29.08.2012 00:16, Kostas wrote:
On 28/08/2012 12:55 μμ, Daniel Mack wrote:
On 28.08.2012 11:47, Kostas wrote:
On 28/08/2012 12:30 μμ, Daniel Mack wrote:
On 28.08.2012 11:18, Kostas wrote:
On 28/08/2012 12:06 üü, Daniel Mack wrote: > On 28.08.2012 10:56, Kostas wrote: >> On 28/08/2012 11:50 ÃÂü, Daniel Mack wrote: >>> On 28.08.2012 10:47, Kostas wrote: >>>> On 28/08/2012 08:44 ÃÂÃÂÃÂü, Daniel Mack wrote: >>>>> On 28.08.2012 00:19, Kostas wrote: >>>>>> On 27/08/2012 06:54 ÃÂüÃÂü, Kostas wrote: >>>>>>> On 27/08/2012 02:44 ÃÂüÃÂü, Daniel Mack wrote: >>>>>>>> On 27.08.2012 12:33, Kostas wrote: >>>>>>>>> On 27/08/2012 12:26 ÃÂüÃÂü, Daniel Mack wrote: >>>>>>>>>> On 27.08.2012 11:00, Kostas wrote: >>>>>>>>>>> Hi All, >>>>>>>>>>> >>>>>>>>>>> I have a 'Trust Webcam' (USB ID: 145f:015b) that comes with a >>>>>>>>>>> microphone. >>>>>>>>>>> The microphone works with Alsa 1.0.23 but it does not work with the >>>>>>>>>>> latest Alsa 1.0.25 neither with Alsa 1.0.24. >>>>>>>>>>> Apparently this is a regression. >>>>>>>>>>> >>>>>>>>>>> What shall I do to figure out the source of the problem? >>>>>>>>>>> >>>>>>>>>>> Here are attached my alsa-infos, with Alsa 1.0.23 (working), >>>>>>>>>>> 1.0.24 (NOT >>>>>>>>>>> working) and 1.0.25 (NOT working). >>>>>>>>>> Can you provide dmesg protocols for both a working and a non-working >>>>>>>>>> case please? >>>>>>>>>> >>>>>>>>>> >>>>>>>>> Below are attached the dmesg files. >>>>>>>>> >>>>>>>> Thanks - the logs look both good, I guess the interesting messages are >>>>>>>> only generated once you try to start the stream. Can you try this? >>>>>>> How i do that? >>>>>>> I tried to make a test call in skype and also recording a video in >>>>>>> cheese but no changes in dmesg. >>>>>>> Is there another way to start the stream? >>>>>> Also tried to record voice with sound recorder...with alsa 1.0.23 >>>>>> recording is fine..i hear my voice when playback the file but with alsa >>>>>> 1.0.24 and above nothing is recorded. >>>>>> In both cases nothing is changed in dmesg output. >>>>>> What else could i do to help you out? >>>>>> >>>>> Comparing the two dmesg logs, I'm under the impression that in the >>>>> second case (the newer kernel), the hda driver kicks in and creates a >>>>> sound device before the usb audio driver does. Hence, the default card >>>>> changes and you're recording from your internal sound card rather than >>>>> the Webcam. >>>>> >>>>> Could you please send the output of 'aplay -l' in both cases? >>>>> >>>>> >>>>> Daniel >>>>> >>>> Output of working case >>>> **** List of PLAYBACK Hardware Devices **** >>>> card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] >>>> àSubdevices: 1/1 >>>> àSubdevice #0: subdevice #0 >>>> card 0: SB [HDA ATI SB], device 1: AD198x Digital [AD198x Digital] >>>> àSubdevices: 1/1 >>>> àSubdevice #0: subdevice #0 >>>> card 2: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] >>>> àSubdevices: 1/1 >>>> àSubdevice #0: subdevice #0 >>> Sorry, there's of course no playback on a webcam. Try 'arecord -l' >>> instead, please. >>> >>> >>> Daniel >>> >> Output of non-working case >> **** List of CAPTURE Hardware Devices **** >> card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] >> Subdevices: 3/3 >> Subdevice #0: subdevice #0 >> Subdevice #1: subdevice #1 >> Subdevice #2: subdevice #2 >> card 1: Webcam [Trust 2MP Auto Focus Webcam], device 0: USB Audio [USB >> Audio] >> Subdevices: 1/1 >> Subdevice #0: subdevice #0 >> >> >> Output of working case >> **** List of CAPTURE Hardware Devices **** >> card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] >> Subdevices: 3/3 >> Subdevice #0: subdevice #0 >> Subdevice #1: subdevice #1 >> Subdevice #2: subdevice #2 >> card 1: default [Trust 2MP Auto Focus Webcam ], device 0: USB Audio [USB >> Audio] >> Subdevices: 1/1 >> Subdevice #0: subdevice #0 >> > Try 'arecord -f cd -Dplughw:1 foo.wav' and see if that works. For > whatever reason, the webcam is not the default in the non-working case. > Are you using the same userspace and configs in both cases? > > > Daniel > Unfortunately it doesn't work...voice is recorded only in 1.0.23 alsa version. In above version nothing is recorded. I use the same Ubuntu release just the kernel changes 1.0.23 alsa is in kernel 2.6.38 newer alsa versions that don't work are in newer kernels.
I still think it is all related to configs and settings. Can you please go check all relevant volume settings and routing switches with amixer or alsamixer? The fact that the default changes tells me that something's different in the behaviour in which ALSA handles the devices.
Also note that 1.0.24 is rather ancient already, and while the driver has seen quiet some refactoring lately, I haven't heard about regressions in that version yet - and I'm sure we would have gotten a whole lot of reports if there was such a tremendous breakage. And there's no signs of errors in the kernel logs either. But you never know, of course.
Daniel
Alsamixer working casehttp://imagebin.org/226143 Alsamixer non-working casehttp://imagebin.org/226142
I also attach amixer output for both cases.
Both in the images and in the text output you seem to have missed pointing amixer/alsamixer the correct device. alsamixer is also in the playback pane, which doesn't exist for the Webcam.
Try 'alsamixer -c1 -V capture'
I finally figured it out with amixer command non working version gives me this output
kostas@kostas-home:~$ amixer -c1 Simple mixer control 'Mic',0  Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum  Capture channels: Mono  Limits: Capture 0 - 4096  Mono: Capture 2723 [66%] [10.63dB] [on]
The working version gives this output kostas@kostas-home:~$ amixer -c1 Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 4096 Mono: Capture 4096 [100%] [16.00dB] [on]
Ok, thanks. In the given case, I have to ask you to do a git bisect. That will point us to the commit that causes your problems. Sorry that I can't help you any further right now, it's just unclear which commit in the ancient history causes your problem.
See here for instructions on how to do that:
https://www.kernel.org/pub/software/scm/git/docs/git-bisect.html http://git-scm.com/book/en/Git-Tools-Debugging-with-Git
Thanks for your help and patience, Daniel
Command git bisect good 1.0.23 gives me the output fatal: Needed a single revision Bad rev input: 1.0.23
How can i figure out the revision number?
On 29.08.2012 02:13, Kostas wrote:
On 29/08/2012 01:51 πμ, Daniel Mack wrote:
On 29.08.2012 00:16, Kostas wrote:
On 28/08/2012 12:55 μμ, Daniel Mack wrote:
On 28.08.2012 11:47, Kostas wrote:
On 28/08/2012 12:30 μμ, Daniel Mack wrote:
On 28.08.2012 11:18, Kostas wrote: > On 28/08/2012 12:06 üü, Daniel Mack wrote: >> On 28.08.2012 10:56, Kostas wrote: >>> On 28/08/2012 11:50 ÃÂü, Daniel Mack wrote: >>>> On 28.08.2012 10:47, Kostas wrote: >>>>> On 28/08/2012 08:44 ÃÂÃÂÃÂü, Daniel Mack wrote: >>>>>> On 28.08.2012 00:19, Kostas wrote: >>>>>>> On 27/08/2012 06:54 ÃÂüÃÂü, Kostas wrote: >>>>>>>> On 27/08/2012 02:44 ÃÂüÃÂü, Daniel Mack wrote: >>>>>>>>> On 27.08.2012 12:33, Kostas wrote: >>>>>>>>>> On 27/08/2012 12:26 ÃÂüÃÂü, Daniel Mack wrote: >>>>>>>>>>> On 27.08.2012 11:00, Kostas wrote: >>>>>>>>>>>> Hi All, >>>>>>>>>>>> >>>>>>>>>>>> I have a 'Trust Webcam' (USB ID: 145f:015b) that comes with a >>>>>>>>>>>> microphone. >>>>>>>>>>>> The microphone works with Alsa 1.0.23 but it does not work with the >>>>>>>>>>>> latest Alsa 1.0.25 neither with Alsa 1.0.24. >>>>>>>>>>>> Apparently this is a regression. >>>>>>>>>>>> >>>>>>>>>>>> What shall I do to figure out the source of the problem? >>>>>>>>>>>> >>>>>>>>>>>> Here are attached my alsa-infos, with Alsa 1.0.23 (working), >>>>>>>>>>>> 1.0.24 (NOT >>>>>>>>>>>> working) and 1.0.25 (NOT working). >>>>>>>>>>> Can you provide dmesg protocols for both a working and a non-working >>>>>>>>>>> case please? >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>> Below are attached the dmesg files. >>>>>>>>>> >>>>>>>>> Thanks - the logs look both good, I guess the interesting messages are >>>>>>>>> only generated once you try to start the stream. Can you try this? >>>>>>>> How i do that? >>>>>>>> I tried to make a test call in skype and also recording a video in >>>>>>>> cheese but no changes in dmesg. >>>>>>>> Is there another way to start the stream? >>>>>>> Also tried to record voice with sound recorder...with alsa 1.0.23 >>>>>>> recording is fine..i hear my voice when playback the file but with alsa >>>>>>> 1.0.24 and above nothing is recorded. >>>>>>> In both cases nothing is changed in dmesg output. >>>>>>> What else could i do to help you out? >>>>>>> >>>>>> Comparing the two dmesg logs, I'm under the impression that in the >>>>>> second case (the newer kernel), the hda driver kicks in and creates a >>>>>> sound device before the usb audio driver does. Hence, the default card >>>>>> changes and you're recording from your internal sound card rather than >>>>>> the Webcam. >>>>>> >>>>>> Could you please send the output of 'aplay -l' in both cases? >>>>>> >>>>>> >>>>>> Daniel >>>>>> >>>>> Output of working case >>>>> **** List of PLAYBACK Hardware Devices **** >>>>> card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] >>>>> àSubdevices: 1/1 >>>>> àSubdevice #0: subdevice #0 >>>>> card 0: SB [HDA ATI SB], device 1: AD198x Digital [AD198x Digital] >>>>> àSubdevices: 1/1 >>>>> àSubdevice #0: subdevice #0 >>>>> card 2: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] >>>>> àSubdevices: 1/1 >>>>> àSubdevice #0: subdevice #0 >>>> Sorry, there's of course no playback on a webcam. Try 'arecord -l' >>>> instead, please. >>>> >>>> >>>> Daniel >>>> >>> Output of non-working case >>> **** List of CAPTURE Hardware Devices **** >>> card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] >>> Subdevices: 3/3 >>> Subdevice #0: subdevice #0 >>> Subdevice #1: subdevice #1 >>> Subdevice #2: subdevice #2 >>> card 1: Webcam [Trust 2MP Auto Focus Webcam], device 0: USB Audio [USB >>> Audio] >>> Subdevices: 1/1 >>> Subdevice #0: subdevice #0 >>> >>> >>> Output of working case >>> **** List of CAPTURE Hardware Devices **** >>> card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] >>> Subdevices: 3/3 >>> Subdevice #0: subdevice #0 >>> Subdevice #1: subdevice #1 >>> Subdevice #2: subdevice #2 >>> card 1: default [Trust 2MP Auto Focus Webcam ], device 0: USB Audio [USB >>> Audio] >>> Subdevices: 1/1 >>> Subdevice #0: subdevice #0 >>> >> Try 'arecord -f cd -Dplughw:1 foo.wav' and see if that works. For >> whatever reason, the webcam is not the default in the non-working case. >> Are you using the same userspace and configs in both cases? >> >> >> Daniel >> > Unfortunately it doesn't work...voice is recorded only in 1.0.23 alsa > version. > In above version nothing is recorded. > I use the same Ubuntu release just the kernel changes > 1.0.23 alsa is in kernel 2.6.38 > newer alsa versions that don't work are in newer kernels. I still think it is all related to configs and settings. Can you please go check all relevant volume settings and routing switches with amixer or alsamixer? The fact that the default changes tells me that something's different in the behaviour in which ALSA handles the devices.
Also note that 1.0.24 is rather ancient already, and while the driver has seen quiet some refactoring lately, I haven't heard about regressions in that version yet - and I'm sure we would have gotten a whole lot of reports if there was such a tremendous breakage. And there's no signs of errors in the kernel logs either. But you never know, of course.
Daniel
Alsamixer working casehttp://imagebin.org/226143 Alsamixer non-working casehttp://imagebin.org/226142
I also attach amixer output for both cases.
Both in the images and in the text output you seem to have missed pointing amixer/alsamixer the correct device. alsamixer is also in the playback pane, which doesn't exist for the Webcam.
Try 'alsamixer -c1 -V capture'
I finally figured it out with amixer command non working version gives me this output
kostas@kostas-home:~$ amixer -c1 Simple mixer control 'Mic',0  Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum  Capture channels: Mono  Limits: Capture 0 - 4096  Mono: Capture 2723 [66%] [10.63dB] [on]
The working version gives this output kostas@kostas-home:~$ amixer -c1 Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 4096 Mono: Capture 4096 [100%] [16.00dB] [on]
Ok, thanks. In the given case, I have to ask you to do a git bisect. That will point us to the commit that causes your problems. Sorry that I can't help you any further right now, it's just unclear which commit in the ancient history causes your problem.
See here for instructions on how to do that:
https://www.kernel.org/pub/software/scm/git/docs/git-bisect.html http://git-scm.com/book/en/Git-Tools-Debugging-with-Git
Thanks for your help and patience, Daniel
Command git bisect good 1.0.23 gives me the output fatal: Needed a single revision Bad rev input: 1.0.23
How can i figure out the revision number?
When working with the kernel git, you have to take the kernel version numbers.
On 29/08/2012 09:23 πμ, Daniel Mack wrote:
On 29.08.2012 02:13, Kostas wrote:
On 29/08/2012 01:51 πμ, Daniel Mack wrote:
On 29.08.2012 00:16, Kostas wrote:
On 28/08/2012 12:55 μμ, Daniel Mack wrote:
On 28.08.2012 11:47, Kostas wrote:
On 28/08/2012 12:30 μμ, Daniel Mack wrote: > On 28.08.2012 11:18, Kostas wrote: >> On 28/08/2012 12:06 üü, Daniel Mack wrote: >>> On 28.08.2012 10:56, Kostas wrote: >>>> On 28/08/2012 11:50 ÃÂü, Daniel Mack wrote: >>>>> On 28.08.2012 10:47, Kostas wrote: >>>>>> On 28/08/2012 08:44 ÃÂÃÂÃÂü, Daniel Mack wrote: >>>>>>> On 28.08.2012 00:19, Kostas wrote: >>>>>>>> On 27/08/2012 06:54 ÃÂüÃÂü, Kostas wrote: >>>>>>>>> On 27/08/2012 02:44 ÃÂüÃÂü, Daniel Mack wrote: >>>>>>>>>> On 27.08.2012 12:33, Kostas wrote: >>>>>>>>>>> On 27/08/2012 12:26 ÃÂüÃÂü, Daniel Mack wrote: >>>>>>>>>>>> On 27.08.2012 11:00, Kostas wrote: >>>>>>>>>>>>> Hi All, >>>>>>>>>>>>> >>>>>>>>>>>>> I have a 'Trust Webcam' (USB ID: 145f:015b) that comes with a >>>>>>>>>>>>> microphone. >>>>>>>>>>>>> The microphone works with Alsa 1.0.23 but it does not work with the >>>>>>>>>>>>> latest Alsa 1.0.25 neither with Alsa 1.0.24. >>>>>>>>>>>>> Apparently this is a regression. >>>>>>>>>>>>> >>>>>>>>>>>>> What shall I do to figure out the source of the problem? >>>>>>>>>>>>> >>>>>>>>>>>>> Here are attached my alsa-infos, with Alsa 1.0.23 (working), >>>>>>>>>>>>> 1.0.24 (NOT >>>>>>>>>>>>> working) and 1.0.25 (NOT working). >>>>>>>>>>>> Can you provide dmesg protocols for both a working and a non-working >>>>>>>>>>>> case please? >>>>>>>>>>>> >>>>>>>>>>>> >>>>>>>>>>> Below are attached the dmesg files. >>>>>>>>>>> >>>>>>>>>> Thanks - the logs look both good, I guess the interesting messages are >>>>>>>>>> only generated once you try to start the stream. Can you try this? >>>>>>>>> How i do that? >>>>>>>>> I tried to make a test call in skype and also recording a video in >>>>>>>>> cheese but no changes in dmesg. >>>>>>>>> Is there another way to start the stream? >>>>>>>> Also tried to record voice with sound recorder...with alsa 1.0.23 >>>>>>>> recording is fine..i hear my voice when playback the file but with alsa >>>>>>>> 1.0.24 and above nothing is recorded. >>>>>>>> In both cases nothing is changed in dmesg output. >>>>>>>> What else could i do to help you out? >>>>>>>> >>>>>>> Comparing the two dmesg logs, I'm under the impression that in the >>>>>>> second case (the newer kernel), the hda driver kicks in and creates a >>>>>>> sound device before the usb audio driver does. Hence, the default card >>>>>>> changes and you're recording from your internal sound card rather than >>>>>>> the Webcam. >>>>>>> >>>>>>> Could you please send the output of 'aplay -l' in both cases? >>>>>>> >>>>>>> >>>>>>> Daniel >>>>>>> >>>>>> Output of working case >>>>>> **** List of PLAYBACK Hardware Devices **** >>>>>> card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] >>>>>> àSubdevices: 1/1 >>>>>> àSubdevice #0: subdevice #0 >>>>>> card 0: SB [HDA ATI SB], device 1: AD198x Digital [AD198x Digital] >>>>>> àSubdevices: 1/1 >>>>>> àSubdevice #0: subdevice #0 >>>>>> card 2: Generic [HD-Audio Generic], device 3: HDMI 0 [HDMI 0] >>>>>> àSubdevices: 1/1 >>>>>> àSubdevice #0: subdevice #0 >>>>> Sorry, there's of course no playback on a webcam. Try 'arecord -l' >>>>> instead, please. >>>>> >>>>> >>>>> Daniel >>>>> >>>> Output of non-working case >>>> **** List of CAPTURE Hardware Devices **** >>>> card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] >>>> Subdevices: 3/3 >>>> Subdevice #0: subdevice #0 >>>> Subdevice #1: subdevice #1 >>>> Subdevice #2: subdevice #2 >>>> card 1: Webcam [Trust 2MP Auto Focus Webcam], device 0: USB Audio [USB >>>> Audio] >>>> Subdevices: 1/1 >>>> Subdevice #0: subdevice #0 >>>> >>>> >>>> Output of working case >>>> **** List of CAPTURE Hardware Devices **** >>>> card 0: SB [HDA ATI SB], device 0: AD198x Analog [AD198x Analog] >>>> Subdevices: 3/3 >>>> Subdevice #0: subdevice #0 >>>> Subdevice #1: subdevice #1 >>>> Subdevice #2: subdevice #2 >>>> card 1: default [Trust 2MP Auto Focus Webcam ], device 0: USB Audio [USB >>>> Audio] >>>> Subdevices: 1/1 >>>> Subdevice #0: subdevice #0 >>>> >>> Try 'arecord -f cd -Dplughw:1 foo.wav' and see if that works. For >>> whatever reason, the webcam is not the default in the non-working case. >>> Are you using the same userspace and configs in both cases? >>> >>> >>> Daniel >>> >> Unfortunately it doesn't work...voice is recorded only in 1.0.23 alsa >> version. >> In above version nothing is recorded. >> I use the same Ubuntu release just the kernel changes >> 1.0.23 alsa is in kernel 2.6.38 >> newer alsa versions that don't work are in newer kernels. > I still think it is all related to configs and settings. Can you please > go check all relevant volume settings and routing switches with amixer > or alsamixer? The fact that the default changes tells me that > something's different in the behaviour in which ALSA handles the devices. > > Also note that 1.0.24 is rather ancient already, and while the driver > has seen quiet some refactoring lately, I haven't heard about > regressions in that version yet - and I'm sure we would have gotten a > whole lot of reports if there was such a tremendous breakage. And > there's no signs of errors in the kernel logs either. But you never > know, of course. > > > Daniel > Alsamixer working casehttp://imagebin.org/226143 Alsamixer non-working casehttp://imagebin.org/226142
I also attach amixer output for both cases.
Both in the images and in the text output you seem to have missed pointing amixer/alsamixer the correct device. alsamixer is also in the playback pane, which doesn't exist for the Webcam.
Try 'alsamixer -c1 -V capture'
I finally figured it out with amixer command non working version gives me this output
kostas@kostas-home:~$ amixer -c1 Simple mixer control 'Mic',0  Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum  Capture channels: Mono  Limits: Capture 0 - 4096  Mono: Capture 2723 [66%] [10.63dB] [on]
The working version gives this output kostas@kostas-home:~$ amixer -c1 Simple mixer control 'Mic',0 Capabilities: cvolume cvolume-joined cswitch cswitch-joined penum Capture channels: Mono Limits: Capture 0 - 4096 Mono: Capture 4096 [100%] [16.00dB] [on]
Ok, thanks. In the given case, I have to ask you to do a git bisect. That will point us to the commit that causes your problems. Sorry that I can't help you any further right now, it's just unclear which commit in the ancient history causes your problem.
See here for instructions on how to do that:
https://www.kernel.org/pub/software/scm/git/docs/git-bisect.html http://git-scm.com/book/en/Git-Tools-Debugging-with-GitThanks for your help and patience, Daniel
Command git bisect good 1.0.23 gives me the output fatal: Needed a single revision Bad rev input: 1.0.23
How can i figure out the revision number?
When working with the kernel git, you have to take the kernel version numbers.
Sorry i really can't understand what to do. The steps i did were git clone git://git.alsa-project.org/alsa-kernel.git alsa-kernel git bisect start alsa-kernel/ git bisect bad git bisect good (Here i don't know what number to give)
I will keep reading because the whole thing is interesting to me...but for now i can't understand anything.
On 29.08.2012 14:04, Kostas wrote:
On 29/08/2012 09:23 πμ, Daniel Mack wrote:
On 29.08.2012 02:13, Kostas wrote:
[...]
Command git bisect good 1.0.23 gives me the output fatal: Needed a single revision Bad rev input: 1.0.23
How can i figure out the revision number?
When working with the kernel git, you have to take the kernel version numbers.
Sorry i really can't understand what to do. The steps i did were git clone git://git.alsa-project.org/alsa-kernel.git alsa-kernel git bisect start alsa-kernel/ git bisect bad git bisect good (Here i don't know what number to give)
I will keep reading because the whole thing is interesting to me...but for now i can't understand anything.
No problem. According to your dmesg logs, kernel 2.6.38 was working for you, and 3.2.0 isn't.
First, clone the mainline Linux git:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux cd linux
Test again that 2.6.38 is working:
git checkout v2.6.38 compile + test
test again that 3.2.0 is not working:
git checkout v3.2 compile and test
Then do the bisect:
git bisect start git bisect good v2.6.38 git bisect bad v3.2
Compile and test each step the bisect drops you to, and then call either "git bisect good" or "git bisect bad". If a step cannot be compiled or tested, call "git bisect skip".
If all goes well, you will be told which commit is the first one that does not work anymore.
Daniel
On 29/08/2012 03:12 μμ, Daniel Mack wrote:
On 29.08.2012 14:04, Kostas wrote:
On 29/08/2012 09:23 πμ, Daniel Mack wrote:
On 29.08.2012 02:13, Kostas wrote:
[...]
Command git bisect good 1.0.23 gives me the output fatal: Needed a single revision Bad rev input: 1.0.23
How can i figure out the revision number?
When working with the kernel git, you have to take the kernel version numbers.
Sorry i really can't understand what to do. The steps i did were git clone git://git.alsa-project.org/alsa-kernel.git alsa-kernel git bisect start alsa-kernel/ git bisect bad git bisect good (Here i don't know what number to give)
I will keep reading because the whole thing is interesting to me...but for now i can't understand anything.
No problem. According to your dmesg logs, kernel 2.6.38 was working for you, and 3.2.0 isn't.
First, clone the mainline Linux git:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux cd linux
Test again that 2.6.38 is working:
git checkout v2.6.38 compile + test
test again that 3.2.0 is not working:
git checkout v3.2 compile and test
Then do the bisect:
git bisect start git bisect good v2.6.38 git bisect bad v3.2
Compile and test each step the bisect drops you to, and then call either "git bisect good" or "git bisect bad". If a step cannot be compiled or tested, call "git bisect skip".
If all goes well, you will be told which commit is the first one that does not work anymore.
Daniel
I can't compile the kernel from git source. After i enter the command|CONCURRENCY_LEVEL=`getconf _NPROCESSORS_ONLN` fakeroot make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers |i get after a while this error
/tmp/ccCeI2GY.s: Assembler messages: /tmp/ccCeI2GY.s: Error: .size expression for do_hypervisor_callback does not evaluate to a constant make[3]: *** [arch/x86/kernel/entry_64.o] Error 1 make[2]: *** [arch/x86/kernel] Error 2 make[1]: *** [arch/x86] Error 2 make[1]: *** Waiting for unfinished jobs.... LD init/mounts.o LD init/built-in.o make[1]: Leaving directory `/home/kostas/linux' make: *** [debian/stamp/build/kernel] Error 2
On 29.08.2012 18:03, Kostas wrote:
On 29/08/2012 03:12 μμ, Daniel Mack wrote:
On 29.08.2012 14:04, Kostas wrote:
On 29/08/2012 09:23 πμ, Daniel Mack wrote:
On 29.08.2012 02:13, Kostas wrote:
[...]
Command git bisect good 1.0.23 gives me the output fatal: Needed a single revision Bad rev input: 1.0.23
How can i figure out the revision number?
When working with the kernel git, you have to take the kernel version numbers.
Sorry i really can't understand what to do. The steps i did were git clone git://git.alsa-project.org/alsa-kernel.git alsa-kernel git bisect start alsa-kernel/ git bisect bad git bisect good (Here i don't know what number to give)
I will keep reading because the whole thing is interesting to me...but for now i can't understand anything.
No problem. According to your dmesg logs, kernel 2.6.38 was working for you, and 3.2.0 isn't.
First, clone the mainline Linux git:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux cd linux
Test again that 2.6.38 is working:
git checkout v2.6.38 compile + test
test again that 3.2.0 is not working:
git checkout v3.2 compile and test
Then do the bisect:
git bisect start git bisect good v2.6.38 git bisect bad v3.2
Compile and test each step the bisect drops you to, and then call either "git bisect good" or "git bisect bad". If a step cannot be compiled or tested, call "git bisect skip".
If all goes well, you will be told which commit is the first one that does not work anymore.
Daniel
I can't compile the kernel from git source. After i enter the command|CONCURRENCY_LEVEL=`getconf _NPROCESSORS_ONLN` fakeroot make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers |i get after a while this error
/tmp/ccCeI2GY.s: Assembler messages: /tmp/ccCeI2GY.s: Error: .size expression for do_hypervisor_callback does not evaluate to a constant make[3]: *** [arch/x86/kernel/entry_64.o] Error 1 make[2]: *** [arch/x86/kernel] Error 2 make[1]: *** [arch/x86] Error 2 make[1]: *** Waiting for unfinished jobs.... LD init/mounts.o LD init/built-in.o make[1]: Leaving directory `/home/kostas/linux' make: *** [debian/stamp/build/kernel] Error 2
Set CONFIG_XEN=n in your .config
On 29/08/2012 07:21 μμ, Daniel Mack wrote:
On 29.08.2012 18:03, Kostas wrote:
On 29/08/2012 03:12 μμ, Daniel Mack wrote:
On 29.08.2012 14:04, Kostas wrote:
On 29/08/2012 09:23 πμ, Daniel Mack wrote:
On 29.08.2012 02:13, Kostas wrote:
[...]
Command git bisect good 1.0.23 gives me the output fatal: Needed a single revision Bad rev input: 1.0.23
How can i figure out the revision number?
When working with the kernel git, you have to take the kernel version numbers.
Sorry i really can't understand what to do. The steps i did were git clone git://git.alsa-project.org/alsa-kernel.git alsa-kernel git bisect start alsa-kernel/ git bisect bad git bisect good (Here i don't know what number to give)
I will keep reading because the whole thing is interesting to me...but for now i can't understand anything.
No problem. According to your dmesg logs, kernel 2.6.38 was working for you, and 3.2.0 isn't.
First, clone the mainline Linux git:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux cd linux
Test again that 2.6.38 is working:
git checkout v2.6.38 compile + test
test again that 3.2.0 is not working:
git checkout v3.2 compile and test
Then do the bisect:
git bisect start git bisect good v2.6.38 git bisect bad v3.2
Compile and test each step the bisect drops you to, and then call either "git bisect good" or "git bisect bad". If a step cannot be compiled or tested, call "git bisect skip".
If all goes well, you will be told which commit is the first one that does not work anymore.
Daniel
I can't compile the kernel from git source. After i enter the command|CONCURRENCY_LEVEL=`getconf _NPROCESSORS_ONLN` fakeroot make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers |i get after a while this error
/tmp/ccCeI2GY.s: Assembler messages: /tmp/ccCeI2GY.s: Error: .size expression for do_hypervisor_callback does not evaluate to a constant make[3]: *** [arch/x86/kernel/entry_64.o] Error 1 make[2]: *** [arch/x86/kernel] Error 2 make[1]: *** [arch/x86] Error 2 make[1]: *** Waiting for unfinished jobs.... LD init/mounts.o LD init/built-in.o make[1]: Leaving directory `/home/kostas/linux' make: *** [debian/stamp/build/kernel] Error 2
Set CONFIG_XEN=n in your .config
So many hours in front of the computer and still can't compile the kernel...now it gives me the error
ld: drivers/watchdog/wm8350_wdt.o: bad reloc symbol index (0x20000033 >= 0x50) for offset 0x7a28 in section `.debug_info' drivers/watchdog/wm8350_wdt.o: could not read symbols: Bad value make[2]: *** [drivers/watchdog/wm8350_wdt.ko] Error 1 make[2]: *** Waiting for unfinished jobs.... make[1]: *** [modules] Error 2 make[1]: Leaving directory `/home/kostas/linux' make: *** [debian/stamp/build/kernel] Error 2
Advice me if you can what to do...i started to have a headache. Will continue tomorrow...
On 29.08.2012 20:59, Kostas wrote:
On 29/08/2012 07:21 μμ, Daniel Mack wrote:
On 29.08.2012 18:03, Kostas wrote:
On 29/08/2012 03:12 μμ, Daniel Mack wrote:
On 29.08.2012 14:04, Kostas wrote:
On 29/08/2012 09:23 πμ, Daniel Mack wrote:
On 29.08.2012 02:13, Kostas wrote:
[...]
> Command git bisect good 1.0.23 gives me the output > fatal: Needed a single revision > Bad rev input: 1.0.23 > > How can i figure out the revision number? > When working with the kernel git, you have to take the kernel version numbers.
Sorry i really can't understand what to do. The steps i did were git clone git://git.alsa-project.org/alsa-kernel.git alsa-kernel git bisect start alsa-kernel/ git bisect bad git bisect good (Here i don't know what number to give)
I will keep reading because the whole thing is interesting to me...but for now i can't understand anything.
No problem. According to your dmesg logs, kernel 2.6.38 was working for you, and 3.2.0 isn't.
First, clone the mainline Linux git:
git clone git://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux cd linux
Test again that 2.6.38 is working:
git checkout v2.6.38 compile + test
test again that 3.2.0 is not working:
git checkout v3.2 compile and test
Then do the bisect:
git bisect start git bisect good v2.6.38 git bisect bad v3.2
Compile and test each step the bisect drops you to, and then call either "git bisect good" or "git bisect bad". If a step cannot be compiled or tested, call "git bisect skip".
If all goes well, you will be told which commit is the first one that does not work anymore.
Daniel
I can't compile the kernel from git source. After i enter the command|CONCURRENCY_LEVEL=`getconf _NPROCESSORS_ONLN` fakeroot make-kpkg --initrd --append-to-version=-custom kernel_image kernel_headers |i get after a while this error
/tmp/ccCeI2GY.s: Assembler messages: /tmp/ccCeI2GY.s: Error: .size expression for do_hypervisor_callback does not evaluate to a constant make[3]: *** [arch/x86/kernel/entry_64.o] Error 1 make[2]: *** [arch/x86/kernel] Error 2 make[1]: *** [arch/x86] Error 2 make[1]: *** Waiting for unfinished jobs.... LD init/mounts.o LD init/built-in.o make[1]: Leaving directory `/home/kostas/linux' make: *** [debian/stamp/build/kernel] Error 2
Set CONFIG_XEN=n in your .config
So many hours in front of the computer and still can't compile the kernel...now it gives me the error
ld: drivers/watchdog/wm8350_wdt.o: bad reloc symbol index (0x20000033 >= 0x50) for offset 0x7a28 in section `.debug_info' drivers/watchdog/wm8350_wdt.o: could not read symbols: Bad value make[2]: *** [drivers/watchdog/wm8350_wdt.ko] Error 1 make[2]: *** Waiting for unfinished jobs.... make[1]: *** [modules] Error 2 make[1]: Leaving directory `/home/kostas/linux' make: *** [debian/stamp/build/kernel] Error 2
Yes, it can be hard at times, as you have to fight with all sorts of build breakage.
Advice me if you can what to do...i started to have a headache. Will continue tomorrow...
Run "make localmodconfig". That will generate a .config based on the modules currently loaded in your kernel. That will also speed up the bisect as way less drivers have to be built.
HTH, Daniel
participants (2)
-
Daniel Mack -
Kostas