mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Ian E. Morgan" <penguin.wrangler@gmail.com>
To: "Jan Engelhardt" <jengelh@linux01.gwdg.de>
Cc: LKML <linux-kernel@vger.kernel.org>,
	perex@suse.cz, alsa-devel@alsa-project.org
Subject: Re: Loud POP from sound system during module init w/ 2.6.19
Date: Sat, 9 Dec 2006 08:17:46 -0500	[thread overview]
Message-ID: <2a6e8c0d0612090517j5afe2161p591203c70ddfc890@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.61.0612091020450.8055@yvahk01.tjqt.qr>

Previous kernel was 2.6.18.3, which did not exhibit the problem. I was
aware of udev setting the mixer at module load time, but I disabled
that and the problem still exists.

-- 
Ian E. Morgan
penguin.wrangler@gmail.com

On 09/12/06, Jan Engelhardt <jengelh@linux01.gwdg.de> wrote:
>
> On Dec 8 2006 13:53, Ian E. Morgan wrote:
> >Subject: Loud POP from sound system during module init w/ 2.6.19
>
> What kernel did you have before?
>
> What you see is the same I am experiencing on every boot - when the sound
> module is loaded, udev loads the previous volume settings. The volume settings
> are normal for me, but I guess the instant jump from 0-70% (for Master) and
> 0-61% (for PCM) is not taken too heartly by the soundcard.
>
> > Since upgrading to 2.6.19, two of my boxes (one workstation, one
> > notebook) started making a very loud (and scary) POP from the sound
> > system when the alsa modules are loaded. Unloading and reloading the
> > modules will generate another pop.
> >
> > Anybody else seeing this behaviour and know how to stop it?

  reply	other threads:[~2006-12-09 13:17 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-08 18:53 Ian E. Morgan
2006-12-09  9:22 ` Jan Engelhardt
2006-12-09 13:17   ` Ian E. Morgan [this message]
2006-12-09 14:11     ` Jan Engelhardt
2006-12-19 10:06 ` [Alsa-devel] " Takashi Iwai

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=2a6e8c0d0612090517j5afe2161p591203c70ddfc890@mail.gmail.com \
    --to=penguin.wrangler@gmail.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=jengelh@linux01.gwdg.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=perex@suse.cz \
    /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

all inboxes | Powered by JetHome®