From: Takashi Iwai <tiwai@suse.de>
To: Laurent Pinchart <laurent.pinchart@skynet.be>
Cc: alsa-devel@alsa-project.org
Subject: Re: Very faint sound on Dell Latitude E6500
Date: Thu, 29 Jan 2009 14:29:37 +0100 [thread overview]
Message-ID: <s5hljsutf3y.wl%tiwai@suse.de> (raw)
In-Reply-To: <200901291427.50098.laurent.pinchart@skynet.be>
At Thu, 29 Jan 2009 14:27:49 +0100,
Laurent Pinchart wrote:
>
> Hi Takashi,
>
> On Thursday 29 January 2009, Takashi Iwai wrote:
> > At Thu, 29 Jan 2009 02:47:45 +0100, Laurent Pinchart wrote:
> > > On Wednesday 28 January 2009, Takashi Iwai wrote:
> > > > At Tue, 27 Jan 2009 16:51:56 +0100, Laurent Pinchart wrote:
> > > > > Hi everybody,
> > > > >
> > > > > I've received a brand new Dell Latitude E6500 and found out that the
> > > > > sound card wasn't exactly well supported by ALSA.
> > > > >
> > > > > Sound is barely audible (so faint that I'm not even sure if the
> > > > > proper sound is output or if I just get garbage), with some loud
> > > > > noise here and there that seem to correspond to the saturated audio
> > > > > data parts.
> > > > >
> > > > > The sound card is an HDA-Intel with an IDT 92HD71B7X codec. Hardware
> > > > > information can be found at
> > > > > http://www.alsa-project.org/db/?f=30cac30e5b1ddd9c842481a830c250cc3e5
> > > > >93b0 d. A
> > > >
> > > > Please run with --no-upload and included the result in the post.
> > >
> > > Done, output included in this e-mail.
> > >
> > > > Anyway, this problem might be related with the volume-knob.
> > > > Install hda-verb and try the following
> > > >
> > > > hda-verb /dev/snd/hwC0D0 0x28 SET_VOLUME_KNOB 0xff
> > > > or
> > > > hda-verb /dev/snd/hwC0D0 0x28 SET_VOLUME_KNOB 0
> > >
> > > Unfortunately none of those make a difference.
> >
> > After doing this, check /proc/asound/card0/codec* whether this node
> > 0x28 is really changed.
> >
> > Then, try the latest alsa-driver snapshot from
> >
> > ftp://ftp.kernel.org/pub/linux/kernel/people/tiwai/snapshot/alsa-driver-sna
> >pshot.tar.gz
> >
> > This contains more fixes since 1.0.19. It's generated from the GIT
> > tree below:
> > git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/sound-2.6.git
> >
> > git://git.kernel.org/pub/scm/linux/kernel/git/tiwai/alsa-driver-build.git
>
> I will test the snapshot this evening.
>
> > Also, check the headphone output at first. The speaker output needs
> > more work than the headphone in general.
>
> The headphone output works properly with the stock 2.6.28 kernel without
> having to mess with volume-knob. I haven't tested it with alsa-driver 1.0.19
> yet.
Ah, so only the speaker output is the problem?
Takashi
next prev parent reply other threads:[~2009-01-29 13:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 15:51 Very faint sound on Dell Latitude E6500 Laurent Pinchart
2009-01-28 15:31 ` Takashi Iwai
2009-01-29 1:47 ` Laurent Pinchart
2009-01-29 8:34 ` Takashi Iwai
2009-01-29 13:27 ` Laurent Pinchart
2009-01-29 13:29 ` Takashi Iwai [this message]
2009-01-29 13:32 ` Laurent Pinchart
2009-01-29 21:33 ` Laurent Pinchart
2009-01-30 6:39 ` Takashi Iwai
2009-01-30 11:38 ` Laurent Pinchart
2009-01-30 11:55 ` Takashi Iwai
2009-01-30 12:12 ` Laurent Pinchart
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=s5hljsutf3y.wl%tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=laurent.pinchart@skynet.be \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox