All of lore.kernel.org
 help / color / mirror / Atom feed
From: James Cameron <quozl@laptop.org>
To: Simon Wolk <mistervertigo@web.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Sound not working after new kernel installed
Date: Thu, 15 Oct 2015 09:43:52 +1100	[thread overview]
Message-ID: <20151014224352.GI27911@us.netrek.org> (raw)
In-Reply-To: <trinity-85f74570-9abc-486a-82c3-4f14c20d1ad0-1444825379497@3capp-webde-bs37>

On Wed, Oct 14, 2015 at 02:22:59PM +0200, Simon Wolk wrote:
> I am using an old Benq notebook (Joybook S73) mit Xubuntu
> 15.04. When I installed a new kernel (then 3.19.0-16, but now I am
> using 3.19.0.28) the sound on the speakers stoped working and there
> were no more audible sounds. With headphones plugged in and a the
> highest possible volume I could hear very silent the music played on
> the PC.
> 
> Up to Kernel 3.2.0-70 the sound worked fine.

Does 3.2.0-70 still work fine?

A friend's laptop had an electrostatic discharge or electrical event
that damaged the audio codec chip, taking out the headphone detect and
headphone amp, and it showed almost same symptoms as you describe.  On
that laptop, patching the kernel to force the headphone not present
fixed playback from speakers.  I'm not suggesting that, but if you can
say the old kernel still works fine you can exclude damage as cause.

That leaves you with looking at the difference between 3.2.0 and
3.19.0, for the driver in use.

Try other kernels between the two, to figure out which kernel
introduced the change.

-- 
James Cameron
http://quozl.linux.org.au/

  reply	other threads:[~2015-10-14 22:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-14 12:22 Sound not working after new kernel installed Simon Wolk
2015-10-14 22:43 ` James Cameron [this message]
2015-10-15  8:34 ` Takashi Iwai
     [not found]   ` <trinity-2e394fe8-112e-4d76-a697-d35c721e754b-1444907835112@3capp-webde-bs08>
2015-10-15 12:19     ` James Cameron

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=20151014224352.GI27911@us.netrek.org \
    --to=quozl@laptop.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=mistervertigo@web.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is 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.