From: James Cassidy <jcassidy@nova.qfire.net>
To: linux-kernel@vger.kernel.org
Subject: Re: Via686b audio
Date: Fri, 16 Nov 2001 14:51:07 -0500 [thread overview]
Message-ID: <20011116145107.A13649@qfire.net> (raw)
In-Reply-To: <1005936427.3321.2.camel@smiddle>
In-Reply-To: <1005936427.3321.2.camel@smiddle>
> I also noticed that the audio driver (via82cxxx_audio) gives a message
> that it is for 82C686a (not 686b, which is what my motherboard is), and
> then errors about timeouts on the AC97 codec - is it possible the 686b
> is a little different than 686a in how the AC97 stuff is handled? I'm
> more than willing to apply patches or make small kernel tweaks, if
> anyone can tell me what I need to do to debug this and get it working.
>
> I've spoken with another person attempting to get Linux running on the
> same laptop series (Compaq Presario 700), and it seems we have similar
> issues. If that makes any difference to anyone. ^,^
I'm the one that Sean is refering to and I'd just like to
add some information I've noticed.
If I turn the volume all the way up I can faintly hear the
music playing, like I was hearing it because of crosstalk on the chip.
At first I thought it was just my wishful thinking playing tricks
on me but it is definetly there :). Now it appears if I adjust the
PCM volume it controls this faint whisper but controling the main volume
does nothing.
Also, I no longer see the timeouts on the AC97 codec with the
newer kernels. The ID for the codec is 0x41445361 (AD1886 according to alsa
drivers). This codec is not currently recognized by the kernel's ac97_codec
drivers.
I'm also willing to try any kernel tweaking/patches, and gather
more debug info if need be.
-- James (QFire)
prev parent reply other threads:[~2001-11-16 19:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 18:47 Via686b audio Sean Middleditch
2001-11-16 19:51 ` James Cassidy [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=20011116145107.A13649@qfire.net \
--to=jcassidy@nova.qfire.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