linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Meelis Roos <mroos@linux.ee>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.3-rc1: snd_intel8x0 still too fast
Date: Mon, 09 Feb 2004 19:23:43 +0100	[thread overview]
Message-ID: <s5hn07s2jtc.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.GSO.4.44.0402071702310.4899-100000@math.ut.ee>

At Sat, 7 Feb 2004 17:10:31 +0200 (EET),
Meelis Roos wrote:
> 
> I tried 2.6.3-rc1 to see if the problems with intel 8x0 audio are fixed.
> Nope, the sound is still at least twice as fast as normal. KDE login
> sound, mplayer sound etc. This is I815 integrated audio on Intel
> D815EEA2 mainboard, Debian unstable up-to-date. 2.4.latest kernel with
> OSS is OK. 2.6 with ALSA was OK at about 2.6.0. 2.6 with OSS is also OK.

which ac97 codec chip?  check /proc/asound/card0/codec97#0/* files.
also, you must have seen a kernel message like
	intel8x0: clocking to 48000
check which value was detected.

> Also, I can load both i810_audio and snd_intel8x0 simultaneously in 2.6
> - probably a resource management problem.

hmm, i810_audio.c doesn't check the return value of request_region()...

--
Takashi Iwai <tiwai@suse.de>		ALSA Developer - www.alsa-project.org

  parent reply	other threads:[~2004-02-09 18:23 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-07 15:10 2.6.3-rc1: snd_intel8x0 still too fast Meelis Roos
2004-02-08 23:11 ` Bill Davidsen
2004-02-09 18:23 ` Takashi Iwai [this message]
2004-02-09 18:35   ` Meelis Roos
2004-02-09 18:46     ` Takashi Iwai
2004-02-10 11:22       ` Meelis Roos
2004-02-10 11:43         ` Takashi Iwai
2004-02-10 12:03           ` Meelis Roos
2004-02-11 11:58             ` Takashi Iwai
2004-02-11 16:40               ` Meelis Roos
2004-02-11 16:43                 ` Takashi Iwai
2004-02-11 16:49                   ` Meelis Roos
2004-02-11 19:26                     ` Takashi Iwai
2004-02-12 13:40                       ` Meelis Roos
2004-02-10 22:34         ` Peter Chubb

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=s5hn07s2jtc.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mroos@linux.ee \
    /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;
as well as URLs for NNTP newsgroup(s).