All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joe Rouvier <joe@rouvier.net>
To: reneb@cistron.nl, linux-kernel@vger.kernel.org
Subject: Re: Trident sound does not work anymore!
Date: Tue, 28 Nov 2000 04:32:52 -0800	[thread overview]
Message-ID: <3A23A5F4.CF20D52D@rouvier.net> (raw)
In-Reply-To: <slrn927896.59.reneb@orac.aais.nl> <3A2395DD.70674662@rouvier.net>

At least, that worked for me.  I had this same problem on 2.2.17 with my
es1371 when I bought a new ASUS P3V4X motherboard.  If someone has a
better solution I'd love to hear about it!

Joe Rouvier wrote:
> 
> Try setting "PNP aware OS" (or something like that) to "NO" in your
> BIOS.
> 
> Rene Blokland wrote:
> >
> > Hi there, as the subject says the trident sound does not work since
> > 2.4.0-test9. this messages does dmesg:
> > Trident 4DWave/SiS 7018/ALi 5451 PCI Audio, version 0.14.6, 12:36:52 Nov 20 2000
> > trident: Trident 4DWave DX found at IO 0xd800, IRQ 0
> > trident: unable to allocate irq 0
> > any ideas?
> >
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > Please read the FAQ at http://www.tux.org/lkml/
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> Please read the FAQ at http://www.tux.org/lkml/
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2000-11-28 13:03 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-28 12:12 Trident sound does not work anymore! Rene Blokland
2000-11-28 11:24 ` Joe Rouvier
2000-11-28 12:32   ` Joe Rouvier [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=3A23A5F4.CF20D52D@rouvier.net \
    --to=joe@rouvier.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=reneb@cistron.nl \
    /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.