All of lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Andersen <andersen@codepoet.org>
To: Jeff Garzik <jgarzik@mandrakesoft.com>
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 20:45:43 -0700	[thread overview]
Message-ID: <20011129204543.A4717@codepoet.org> (raw)
In-Reply-To: <20011129190617.A3975@codepoet.org> <3C06F125.A1D3EBD3@mandrakesoft.com>
In-Reply-To: <3C06F125.A1D3EBD3@mandrakesoft.com>

On Thu Nov 29, 2001 at 09:38:29PM -0500, Jeff Garzik wrote:
> 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
[---------snip--------]
> > 
> > When I go to play audio, no sound is produced.  The mixer works.
[---------snip--------]
> 
> 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).

Thanks.  The ALSA drivers indeed work just great.  So yeah, do
pull the Via 8233 audio PCI IDs from via82cxxx_audio.  ALSA seems
to be the One True Path for these monsters.

 -Erik

--
Erik B. Andersen             http://codepoet-consulting.com/
--This message was written using 73% post-consumer electrons--

  parent reply	other threads:[~2001-11-30  3:46 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
2001-11-30  2:50   ` James Cassidy
2001-11-30  3:45   ` Erik Andersen [this message]
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=20011129204543.A4717@codepoet.org \
    --to=andersen@codepoet.org \
    --cc=jgarzik@mandrakesoft.com \
    --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.