From: Takashi Iwai <tiwai@suse.de>
To: Julian Wollrath <jwollrath@web.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: Grey noise with HDA Intel PCH
Date: Sat, 23 Aug 2014 20:40:59 +0200 [thread overview]
Message-ID: <s5hvbpjt5fo.wl-tiwai@suse.de> (raw)
In-Reply-To: <20140822181828.7136684d@saldaea>
At Fri, 22 Aug 2014 18:18:28 +0200,
Julian Wollrath wrote:
>
> Am Fri, 15 Aug 2014 08:02:38 +0200
> schrieb Takashi Iwai <tiwai@suse.de>:
>
> > At Thu, 14 Aug 2014 18:29:19 +0200,
> > Julian Wollrath wrote:
> > >
> > > > > > > > Thanks. The setup looks OK, the path is:
> > > > > > > > DAC (0x02) -> mixer (0x0c) -> mixer (0x14)
> > > > > > > > and the mixer mutes the loopback path (index 1).
> > > > > > > >
> > > > > > > > Is it the state where you still hear the static noise?
> > > > > > > Yes, the alsa-info.sh script was executed, while hearing the
> > > > > > > static noise.
> > > > > >
> > > > > > OK. And if you mute "Speaker" or "Headphone", the noise is
> > > > > > gone, too, right?
> > > > > No, if I mute "Speaker" (the internal laptop speaker) it is not
> > > > > gone. It is only gone, if I mute "Master" or have a headphone
> > > > > plugged in and mute "Headphone" or "Master".
> > > >
> > > > Interesting. The "Speaker" mute changes "Speaker Playback
> > > > Switch", and as you can see in alsa-info.sh output, this toggles
> > > > the mute of the speaker pin NID 0x14, i.e. the endpoint. If
> > > > "Master" influences, it means to mute *both* Headphone and
> > > > Speaker mutes would work. Could you check this?
> > > Muting both Headphone and Speaker does not work for the static
> > > noise on the speaker.
> >
> > Then check what's the difference in codec proc content between the two
> > cases: Master=mute and Headphone+Speaker=mute.
> >
> > > > > More fascinating, it is not present, if the speaker is not muted
> > > > > and I disable powersaving via "echo '0' >
> > > > > '/sys/module/snd_hda_intel/parameters/power_save'" but even
> > > > > then, it is still present on the headphone.
> > > >
> > > > Hm. Is the noise audible when you playback a PCM stream, too?
> > > > For example, you can play a silent stream.
> > > Yes, then it is audible.
> > >
> > > > > > > > Also, what if you use the module option for snd-hda-intel
> > > > > > > > model=nofixup or model=generic?
> > > > > > > That did not change anything either. Passing the "mixer_nid
> > > > > > > = 0" hint also did not get rid of the static noise, when
> > > > > > > loading snd-hda-intel with model=nofixup resp.
> > > > > > > model=generic.
> > > > > >
> > > > > > Did you reboot with setting the option in /etc/modprobe.d/*?
> > > > > > Reloading the module might not work for such a problem.
> > > > > No, I just unloaded every sound-related module and than loaded
> > > > > the module via "modprobe snd-hda-intel model=..." again.
> > > >
> > > > Then always test with reboot. The problem is about the
> > > > vendor-specific setups, and it's often sticky unless the cold
> > > > boot. At best, do the cold boot. The warm boot doesn't cure
> > > > always.
> > > Ok, I tested with a reboot but that did not help.
> > >
> > > > > > In either way, there should be some difference in alsa-info.sh
> > > > > > output, e.g. more (or less) mixer items with the model option.
> > > > > The difference is their, all the "Dock ..." entries were
> > > > > missing, when loading with the model="..." option.
> > > >
> > > > Yes, and you should also see the difference in the kernel
> > > > messages.
> > > >
> > > > Another thing to check is to swap the DAC assignment. There was a
> > > > similar problem on some Sony laptops, and we had to swap the DAC
> > > > assignment since the hardware seems to have some implicit
> > > > assumption of the DAC. A test patch is below.
> > > Thanks, but sadly the patch did not help.
> >
> > I have no much other clue, so far. The rest you can test is to toggle
> > EAPD, toggle GPIO pin, and change the different pin setups, e.g. put
> > VREF or HP amp bit on any (even unused) pins.
> Toggling the EAPD got rid of the noise but I also did not get any sound
> output anymore. Playing with the other pins got me nowhere. Seems like
> I have to live with the noise.
Possibly a combination of something might work, but it needs really
many trial-and-error. In anyway, if you hit a good state
coincidentally, don't forget to take alsa-info.sh snapshot.
Takashi
prev parent reply other threads:[~2014-08-23 18:40 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-14 9:40 Grey noise with HDA Intel PCH Julian Wollrath
2014-08-14 10:20 ` Clemens Ladisch
2014-08-14 10:46 ` Julian Wollrath
2014-08-14 12:17 ` Takashi Iwai
2014-08-14 14:07 ` Julian Wollrath
2014-08-14 14:09 ` Takashi Iwai
2014-08-14 14:39 ` Julian Wollrath
2014-08-14 14:47 ` Takashi Iwai
2014-08-14 15:04 ` Julian Wollrath
2014-08-14 15:11 ` Takashi Iwai
2014-08-14 15:26 ` Julian Wollrath
2014-08-14 15:31 ` Julian Wollrath
2014-08-14 15:48 ` Takashi Iwai
2014-08-14 16:29 ` Julian Wollrath
2014-08-15 6:02 ` Takashi Iwai
2014-08-22 16:18 ` Julian Wollrath
2014-08-23 18:40 ` Takashi Iwai [this message]
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=s5hvbpjt5fo.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=jwollrath@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.