All of lore.kernel.org
 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: Tue, 10 Feb 2004 12:43:13 +0100	[thread overview]
Message-ID: <s5hn07r17ou.wl@alsa2.suse.de> (raw)
In-Reply-To: <Pine.GSO.4.44.0402101256450.4333-100000@math.ut.ee>

At Tue, 10 Feb 2004 13:22:25 +0200 (EET),
Meelis Roos wrote:
> 
> > > Today mplayer was OK when I tested, didn't retry KDE login. But the
> > > kernel is the same, I have not rebooted inbetween.
> >
> > weird...  cpufreq is running?
> 
> No, it's a desktop Celeron 900.
> 
> > > Did try twice:
> > >
> > > intel8x0_measure_ac97_clock: measured 50040 usecs
> > > intel8x0: clocking to 41146
> > >
> > > intel8x0_measure_ac97_clock: measured 49395 usecs
> > > intel8x0: clocking to 41145
> >
> > and now you got the correct output?
> > if so, you can pass the value via ac97_clock option.
> 
> I did retest things more toroughly today after I booted up 2.6.3-rc2. I
> focused on testing KDE login since this is known to break. Startup
> scripts (discover) loaded also i810_audio, I unloaded it.
 
oh never load two these modules at the same time!
it can crash the system.
it must be a bug of i810_audio that can coexist with ALSA driver.

> Plain bootup gave
> PCI: Setting latency timer of device 0000:00:1f.5 to 64
> intel8x0_measure_ac97_clock: measured 49671 usecs
> intel8x0: clocking to 41136
> 
> and it did not work. Unloading and reloading snd-intel8x0 gave
> PCI: Setting latency timer of device 0000:00:1f.5 to 64
> intel8x0_measure_ac97_clock: measured 49281 usecs
> intel8x0: clocking to 41139
> 
> and it still did not work (way too fast, probably even more than twice).
> Now I tried
> modprobe snd-intel8x0 ac97_clock=41140
> It loads silently but still does not work.
> 
> Now I started to suspect that loading i810_audio might screw things up.
> Removed the module and rebooted, no i810_audio loaded, still the same.
> 
> Reproduced the problem with mplayer too. It depends on the input file
> bitrate!
> 
> mplayer /usr/share/sounds/KDE_Startup.wav
> gives the same very fast sound since it's a 22 KHz mono sample.
> 
> mplayer -srate 48000 /usr/share/sounds/KDE_Startup.wav
> works fine. Same applies to all files.

then VRA of ac97 seems not working correctly.
check /proc/asound/card0/codec97#0/* files for each case whether the
DAC rate is set correctly.  (it must be tuned with the detected ac97
clock, i.e. rate * clock / 48000).


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

  reply	other threads:[~2004-02-10 11:45 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
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 [this message]
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=s5hn07r17ou.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 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.