From: "Wilson" <defiler@null.net>
To: <linux-kernel@vger.kernel.org>
Subject: Re: Question concerning SBLIVE! driver.
Date: Sun, 7 Oct 2001 21:23:12 -0400 [thread overview]
Message-ID: <019201c14f97$cc16b220$c800000a@Artifact> (raw)
In-Reply-To: <3BC0F7DD.9129242A@starband.net>
Is your motherboard based on a Via chipset? If so, then this doesn't have
anything to do with Linux.. You'd have the same problems with Windows 2000..
I have a pair of SB Live! Platinums gathering dust in the room with me
because of the "Via/SBLive!" and "SMP/SBLive!" bugs.
----- Original Message -----
From: "war" <war@starband.net>
To: <linux-kernel@vger.kernel.org>
Sent: Sunday, October 07, 2001 8:48 PM
Subject: Question concerning SBLIVE! driver.
> I've noticed in Kernel 2.4.10 that the emu10k1 driver produces cracks in
> the sound output.
>
> Is there a stable emu10k1?
>
> The emu10k1 driver in all kernels < 2.4.7 is from 04-12-2000, which
> produce excellent sound.
>
> I've spoken with a few other guys on IRC, and they also have this
> problem [of crackling, etc].
>
> What would be the best course of action if one wants good sound in
> kernels > 2.4.7?
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2001-10-08 1:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-10-08 0:48 Question concerning SBLIVE! driver war
2001-10-08 1:23 ` Wilson [this message]
2001-10-08 10:49 ` Rui Sousa
2001-10-08 15:42 ` Nick Lockyer
2001-10-08 18:12 ` John Gluck
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='019201c14f97$cc16b220$c800000a@Artifact' \
--to=defiler@null.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 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.