From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: andersen@codepoet.org
Cc: linux-kernel <linux-kernel@vger.kernel.org>, linux-via@gtf.org
Subject: Re: via82cxxx_audio doesn't play audio?
Date: Thu, 29 Nov 2001 21:38:29 -0500 [thread overview]
Message-ID: <3C06F125.A1D3EBD3@mandrakesoft.com> (raw)
In-Reply-To: <20011129190617.A3975@codepoet.org>
Erik Andersen wrote:
>
> I went out the other day and bought an Athlon to replace my aging
> celeron 400. I installed an Epox EP-8KHA+ with an Athlon XP 1600+.
> The VIA 8233 Southbridge on the motherboard has builtin audio
>
> 00:11.5 Multimedia audio controller: VIA Technologies, Inc. AC97 Audio Controller (rev 30)
> Flags: medium devsel, IRQ 11
> I/O ports at cc00 [size=256]
> Capabilities: [c0] Power Management version 2
>
> I have enabled CONFIG_SOUND_VIA82CXXX and CONFIG_MIDI_VIA82CXXX
> in 2.4.16 and everything seems to be fine. When I load the
> modules I see this:
>
> Via 686a audio driver 1.9.1
> ac97_codec: AC97 Audio codec, id: 0x414c:0x4710 (ALC200/200P)
> via82cxxx: board #1 at 0xCC00, IRQ 11
>
> When I go to play audio, no sound is produced. The mixer works.
> I can load up the bttv drivers and I actually hear audio from
> xawtv (so tvaudio is doing something right behind the scenes).
> But standard apps such as xmms produce no sound. Does this
> driver not work for anyone else?
You need ALSA drivers.
Via 686 audio is different from Via 8233 audio, and you have the
latter. The PCI ids were added to via82cxxx_audio, but they need to be
removed since they apparently do not work (contrary to one report I
received).
Jeff
--
Jeff Garzik | Only so many songs can be sung
Building 1024 | with two lips, two lungs, and one tongue.
MandrakeSoft | - nomeansno
next prev parent reply other threads:[~2001-11-30 2:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-30 2:06 via82cxxx_audio doesn't play audio? Erik Andersen
2001-11-30 2:38 ` Jeff Garzik [this message]
2001-11-30 2:50 ` James Cassidy
2001-11-30 3:45 ` Erik Andersen
2001-11-30 4:51 ` Sven.Riedel
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=3C06F125.A1D3EBD3@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=andersen@codepoet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-via@gtf.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.