mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Adrian Bunk <bunk@stusta.de>
To: Marcus Hartig <m.f.h@web.de>
Cc: linux-kernel@vger.kernel.org, Takashi Iwai <tiwai@suse.de>,
	perex@suse.cz, alsa-devel@lists.sourceforge.net
Subject: Re: 2.6.16-rcX - no more sound with ALSA snd-hda-intel / Sigmatel
Date: Sat, 18 Mar 2006 15:36:38 +0100	[thread overview]
Message-ID: <20060318143637.GB7471@stusta.de> (raw)
In-Reply-To: <441C13C1.7000902@web.de>

On Sat, Mar 18, 2006 at 03:05:53PM +0100, Marcus Hartig wrote:

> Hello!

Hi Marcus!

> Since the 2.6.16.rcX kernel versions I have no more sound with the ALSA 
> snd-hda-intel driver. All modules load without errors, all  channels are 
> unmuted, no errors in any log, but sound is death! :(
> 
> With kernel 2.6.15.6 (ALSA 1.0.10rc3) the sound is working, only that 
> the headphones output is not doing any noise and then the internal 
> speakers are not muted. With mplayer and ALSA sound output the CPU load 
> goes very high and it stutters, with OSS output in mplayer OSS device 
> not more.
> 
> This is an new DELL Inspiron 9400 Dual Core notebook with Sigmatel STAC 
> 92XX C-Major HD Audio.
> 
> lspci:
> 00:1b.0 Audio device: Intel Corporation 82801G (ICH7 Family) High 
> Definition Audio Controller (rev 01) Subsystem: Dell Unknown device 01cd
> 
> Module options:
> snd_hda_intel position_fix=1 index=0
>...

Does the patch from [1] help?

> Greetings,
> Marcus

cu
Adrian

[1] http://lkml.org/lkml/2006/3/17/279

-- 

       "Is there not promise of rain?" Ling Tan asked suddenly out
        of the darkness. There had been need of rain for many days.
       "Only a promise," Lao Er said.
                                       Pearl S. Buck - Dragon Seed


  reply	other threads:[~2006-03-18 14:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-18 14:05 Marcus Hartig
2006-03-18 14:36 ` Adrian Bunk [this message]
2006-03-18 18:32   ` Marcus Hartig
2006-03-20 11:59     ` 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=20060318143637.GB7471@stusta.de \
    --to=bunk@stusta.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=m.f.h@web.de \
    --cc=perex@suse.cz \
    --cc=tiwai@suse.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome