From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Ariel Molina Rueda <amolina@fismat.umich.mx>
Cc: linux-kernel@vger.kernel.org, Adrian Cox <adrian@humboldt.co.uk>
Subject: Re: Via82cxxx Codec rate locked at 48Khz
Date: Fri, 06 Jul 2001 14:29:33 -0400 [thread overview]
Message-ID: <3B46038D.5DA023B6@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0107061215400.32589-100000@garota.fismat.umich.mx>
Ariel Molina Rueda wrote:
>
> Greetings:
>
> When i used Redhat 7 and kernel 2.2.x y was happy with my souncard, now I
> use RedHat 7.1 and Kernel 2.4.x, but sndconfig doesn't configure my
> Via82c686 soundcard at all. At the ending it says
>
> via82cxxx codec rate locked at 48khz
>
> I use a Biostar MKE401B Matherboard with on-board sound (AC97)
>
> I've heard about patches for the intel chipsets, does anybody knows if one
> for my card has been released, or how to fix this problem...
> (my sound is choppy and XMMS crashes!)
>
> something weird is that sound is good when Linus says:
> "Hi, Im Linus Torvalds, and...."
> then after sndconfig ends and sound is crying...
Kernel 2.4.6 definitely includes fixes.
For the message "Codec rate locked at 48Khz", that is a hardware
limitation of your codec. You need to find software which supports
software rate conversion, so that you may play music at speeds other
than 48Khz.
Jeff
--
Jeff Garzik | A recent study has shown that too much soup
Building 1024 | can cause malaise in laboratory mice.
MandrakeSoft |
next prev parent reply other threads:[~2001-07-06 19:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-06 16:52 New Machine Check problem William Earnest
2001-07-06 17:26 ` Via82cxxx Codec rate locked at 48Khz Ariel Molina Rueda
2001-07-06 17:54 ` Adrian Cox
2001-07-06 18:21 ` Ariel Molina Rueda
2001-07-06 18:15 ` Masoud
2001-07-06 18:36 ` Via82cxxx Codec rate locked at 48Khz: ALSA Ariel Molina Rueda
2001-07-06 18:29 ` Jeff Garzik [this message]
2001-07-07 7:32 ` Via82cxxx Codec rate locked at 48Khz Adrian Cox
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=3B46038D.5DA023B6@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=adrian@humboldt.co.uk \
--cc=amolina@fismat.umich.mx \
--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 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.