All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: John Frankish <john.frankish@outlook.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: No sound from speakers with Realtek ALC3226
Date: Wed, 25 Feb 2015 10:15:35 +0100	[thread overview]
Message-ID: <s5h4mqa5p3c.wl-tiwai@suse.de> (raw)
In-Reply-To: <COL403-EAS2907AF9B8908D92F837F8E5F3170@phx.gbl>

At Wed, 25 Feb 2015 13:08:29 +0400,
John Frankish wrote:
> 
> > > 
> > > I posted this on the alsa-user list, but did not get a reply.
> > > 
> > > Although it occasionally works, I am usually unable to get any sound 
> > > out of the speakers on a dell latitude e7240 using alsa-1.0.28 and 
> > > linux-3.16.6 - see details at the end of the post.
> >
> > If so, Windows or BIOS is the problem.  It doesn't set up the pin
> configuration properly Linux driver relies on.
> >
> I just updated the bios to the latest version, but no change :(
> >
> > If you get the status where the speaker works (e.g. after Windows clean
> reboot), try to take alsa-info.sh snapshot.  Run alsa-> info.sh with
> --no-upload option, and save the generated output.  Then, take another
> alsa-info.sh snapshot while the speaker > doesn't work.  Compare these two
> outputs.  (At best, attach both (compressed) files.)
> >
> Alsa_info_works and alsa_info_no_works attached - diff didn't show an
> obvious difference between getting sound from the speakers and not getting
> sound from the speakers.

OK, then this is not about the pin configuration, but likely the EAPD
setup BIOS does.

Did you try the newer kernels?  There has been a fix for EAPD control,
and this might already fix your problem.


Takashi

  reply	other threads:[~2015-02-25  9:15 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-24  9:14 No sound from speakers with Realtek ALC3226 John Frankish
2015-02-24 15:00 ` Takashi Iwai
2015-02-25  9:08   ` John Frankish
2015-02-25  9:15     ` Takashi Iwai [this message]
2015-02-25  9:25       ` John Frankish
2015-02-25 10:35         ` Takashi Iwai
2015-02-25 11:56           ` John Frankish
2015-02-25 10:37         ` John Frankish

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=s5h4mqa5p3c.wl-tiwai@suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=john.frankish@outlook.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.