Mailinglist Archive: opensuse (3378 mails)

< Previous Next >
Re: [SLE] AC97
  • From: Anders Johansson <andjoh@xxxxxxxxxxxxxxxxxxxxx>
  • Date: Sun, 14 Apr 2002 00:34:52 +0200
  • Message-id: <200204140034.52347.andjoh@xxxxxxxxxxxxxxxxxxxxx>
On Saturday 13 April 2002 21:28, Jesse Marlin wrote:
> Anders Johansson writes:
> > Hi,
> >
> > Trying to rephrase my question a little.
> >
> > I have a motherboard with a built in soundcard that the docs simply
> > lable as "AC97". I see a module ac97.o, and it doesn't complain when I
> > load it, but there's no sound.
> >
> > So here's my question: could someone shed some light on what exactly
> > AC97 is?
> >
> > I've read a few papers on the net. Am I right in thinking AC97 is an
> > application interface, as opposed to a chipset standard (in other words
> > the ac97 module is an API that still requires a chipset specific driver)
> > or have I misunderstood something?
> I think it is. ALSA have not released a stable version in a while, but
> I have been using the unstable series for a while with no problems. I have
> two cards right now using the unstable drivers (ALSA 0.9 series). I
> suggest trying them. Try lspci to see if it reports what kind of chip your
> motherboard has, here is some output from mine:
> 00:04.0 ISA bridge: VIA Technologies, Inc. VT82C686 [Apollo Super South]
> (rev 1b) 00:04.1 IDE interface: VIA Technologies, Inc. Bus Master IDE (rev
> 06) 00:04.2 USB Controller: VIA Technologies, Inc. UHCI USB (rev 0e)
> 00:04.3 USB Controller: VIA Technologies, Inc. UHCI USB (rev 0e)
> 00:04.4 SMBus: VIA Technologies, Inc. VT82C686 [Apollo Super ACPI] (rev 20)
> 00:04.5 Multimedia audio controller: VIA Technologies, Inc. AC97 Audio
> Controller (rev 21)
> So the chip is actually the VT82C686. As you can see this chip does a lot.
> Good luck!

Thanks to all who replied. You confirmed my suspicions that it's not enough
for a chip to be AC'97, the specific chipset has to supported as well. That
was what I though, especially considering that lspci called it an "unknown
device" and that yast2(alsaconf) didn't recognize it.


< Previous Next >
Follow Ups