From: Takashi Iwai <tiwai@suse.de>
To: Daniel Blueman <daniel.blueman@gmx.net>
Cc: alsa-devel@lists.sourceforge.net, linux-kernel@vger.kernel.org
Subject: Re: [2.6.0-test4] [BUG, ALSA] no 44.1KHz sound for i8x0 ICH2...
Date: Tue, 09 Sep 2003 13:17:07 +0200 [thread overview]
Message-ID: <s5h7k4ius7g.wl@alsa2.suse.de> (raw)
In-Reply-To: <31962.1063013638@www28.gmx.net>
At Mon, 8 Sep 2003 11:33:58 +0200 (MEST),
Daniel Blueman wrote:
>
> I can't get any sound output with an Intel 815 chipset at 44.1KHz. ALSA
> reports the sound chipset can clock to 41KHz.
>
> What information do I need to post here?
>
> Please CC me on any replies.
>
> --- [ lspci -v ]
>
> 00:1f.5 Multimedia audio controller: Intel Corp. 82801BA/BAM AC'97 Audio
> (rev 11)
> Subsystem: Dell Computer Corporation: Unknown device 00be
> Flags: bus master, medium devsel, latency 0, IRQ 10
> I/O ports at c800 [size=256]
> I/O ports at cc40 [size=64]
>
> --- [ dmesg ]
>
> Advanced Linux Sound Architecture Driver Version 0.9.6 (Wed Aug 20 20:27:13
> 2003 UTC).
> PCI: Found IRQ 10 for device 0000:00:1f.5
> PCI: Sharing IRQ 10 with 0000:00:1f.3
> PCI: Setting latency timer of device 0000:00:1f.5 to 64
> hub 1-0:0: debounce: port 1: delay 100ms stable 4 status 0x301
> intel8x0: clocking to 41151 <----- should be 44100?
no, it doesn't mean that the chip supports 44.1kHz.
it shows that your sound chip is driven in the detected clock.
usually it's 48000, but in some cases, it's based on PCI clock and
runs in different speed.
or, it could be a bug of detection routine, which might be influenced
by cpufreq, etc.
if the sound is too slow, please give the option ac97_clock=48000
manually.
--
Takashi Iwai <tiwai@suse.de> SuSE Linux AG - www.suse.de
ALSA Developer ALSA Project - www.alsa-project.org
prev parent reply other threads:[~2003-09-09 11:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-08 9:33 [2.6.0-test4] [BUG, ALSA] no 44.1KHz sound for i8x0 ICH2 Daniel Blueman
2003-09-09 11:17 ` 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=s5h7k4ius7g.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=daniel.blueman@gmx.net \
--cc=linux-kernel@vger.kernel.org \
/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