[alsa-devel] Regression post-ALSA 1.0.22 for Lenovo G555 Internal mic
Roo - Andrew Baines
andrewmbaines at gmail.com
Tue May 24 14:04:22 CEST 2011
Ah, ok, so I opened the email as raw text and I'm getting somewhere... I
have attached the patch I am trying to apply, I apologise I have really very
little idea.
shark alsa-kernel # patch -p2 </home/roo/patch
patching file pci/hda/patch_conexant.c
Hunk #1 FAILED at 3484.
Hunk #2 succeeded at 3330 with fuzz 2 (offset -178 lines).
Hunk #3 FAILED at 3520.
Hunk #4 FAILED at 3704.
Hunk #5 succeeded at 3363 with fuzz 2 (offset -395 lines).
3 out of 5 hunks FAILED -- saving rejects to file
pci/hda/patch_conexant.c.rej
I have also attached the latest alsa-info. In alsamixer I dont seem to have
the auto-mute mixer, but I think I am running the latest snapshot:
roo at shark ~ $ cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version
1.0.24.13.g953fe.286.ge539e.
Compiled on May 24 2011 for kernel 2.6.38-2-amd64 (SMP).
I am compiling as follows:
./configure --with-cards=hda-intel --with-sequencer=yes
make
make install
If I include --with-card-options=hda-codec-conexant it doesnt seem to make a
difference.
Thanks
Andrew
On 24 May 2011 12:07, Takashi Iwai <tiwai at suse.de> wrote:
> At Tue, 24 May 2011 11:57:16 +0100,
> Roo - Andrew Baines wrote:
> >
> > I tried the patch but for some reason it fails, am i using patch wrong?
> When
> > I try and open it in Kompare it says its not a valid diff file.
>
> Did you save it as a raw file? Otherwise gmail interface breaks lines
> and spaces badly.
>
> > shark alsa-kernel # patch -p2 </home/roo/alsa-patch
> > patching file pci/hda/patch_conexant.c
> > Hunk #1 FAILED at 3484.
> > Hunk #2 FAILED at 3508.
> > Hunk #3 FAILED at 3519.
> > Hunk #4 FAILED at 3703.
> > Hunk #5 FAILED at 3757.
> > 5 out of 5 hunks FAILED -- saving rejects to file
> > pci/hda/patch_conexant.c.rej
> >
> > New alsa-info.sh output is attached also.
> >
> > When I ran arecord with pasuspender I got an error 'D is not a valid
> option'
> > so I killed pulse and did arecord.
>
> Then pass like "pasuspender -- arecord ....". Depending on PA
> version, you need "--".
>
> > What I got was a 0.00 second long
> > recording even if i specified --duration=10.
> >
> > There are no alsa records in /var/log/messages at all when I grep for
> ALSA,
> > alsa, conexant, snd, sound.
>
> You have the following kernel messages:
> [ 3798.888009] ALSA hda_intel.c:717: azx_get_response timeout, switching to
> polling mode: last cmd=0x001f000a
> [ 3799.892016] ALSA hda_intel.c:756: hda_intel: azx_get_response timeout,
> switching to single_cmd mode: last cmd=0x001f000a
>
> This is rather a fatal error, which makes impossible to get
> unsolicited events from the codec.
>
> And, judging from alsa-info.sh output, you are still using the old
> driver. With the new driver, you must have "Auto-Mute" enum mixer
> element. That is, the installation from the snapshot tarball failed
> somehow. Double-check what went wrong. The error above should have
> been fixed in the recent version.
>
> BTW, I fixed another issue in auto-mute mode, so try the latest
> snapshot tarball again.
>
>
> thanks,
>
> Takashi
>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: patch
Type: application/octet-stream
Size: 2120 bytes
Desc: not available
Url : http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20110524/569c192a/attachment-0002.dll
-------------- next part --------------
A non-text attachment was scrubbed...
Name: alsa-info.txt.aTVRpJvwkf
Type: application/octet-stream
Size: 16785 bytes
Desc: not available
Url : http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20110524/569c192a/attachment-0003.dll
More information about the Alsa-devel
mailing list