public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Cassidy <jcassidy@cs.kent.edu>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: via686/AD1886/Soundmax drivers
Date: Wed, 27 Feb 2002 17:12:57 -0500	[thread overview]
Message-ID: <20020227221257.GA603@qfire.net> (raw)
In-Reply-To: <20020227165412.62bbe066.christy@attglobal.net> <20020227191147.GA1119@telia.com>
In-Reply-To: <20020227191147.GA1119@telia.com>

[-- Attachment #1: Type: text/plain, Size: 984 bytes --]



	This affects Compaq's new Compaq Presario 700's that were released
last summer, which has been discussed on this list several times. Peter 
has a FIC A360+ board which he has managed to atleast play peripherals like
CD-ROM to work, this is one the HP laptops I believe.
	I haven't been able to do that, with any of the default_ops or 
eapd settings suggested on this list, on the Compaq presario I'm sending 
this e-mail from. Only that frustrating crosstalk sound I get by turning
the peripheral volumes all the way up. The master volume does nothing.
					-- James Cassidy (QFire)


On Wed, Feb 27, 2002 at 08:11:48PM +0100, Andr? Dahlqvist wrote:
> On Wed, Feb 27, 2002 at 04:54:12PM +0000, Peter Christy wrote:
> 
> > Ths saga continues..... (no sound on laptops using via686 and AD1886s -
> > mostly FIC A360+ and Compaq Presarios)
> 
> This is interesting. Have you given the ALSA drivers a shot? Do you know
> what Compaq Presario laptops this affects?

[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  reply	other threads:[~2002-02-27 22:13 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-02-27 16:54 via686/AD1886/Soundmax drivers Peter Christy
2002-02-27 19:11 ` André Dahlqvist
2002-02-27 22:12   ` James Cassidy [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-02-19  9:03 Peter Christy
2002-02-19 12:25 ` Vojtech Pavlik
2002-02-21  9:56   ` Peter Christy
2002-02-21 10:15     ` Vojtech Pavlik
2002-02-21 11:16       ` Peter Christy

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=20020227221257.GA603@qfire.net \
    --to=jcassidy@cs.kent.edu \
    --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