public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Hetfield <hetfield666@virgilio.it>
To: linux-kernel@vger.kernel.org
Subject: [BUG] 2.6.x ALSA sound is pretty broken
Date: Fri, 18 Jun 2004 16:03:53 +0200	[thread overview]
Message-ID: <1087567432.9282.17.camel@blight.blight> (raw)

i've got hard problems with sound in all 2.6.x, even 2.6.7 kernels.

with 2.4.2x or windows i've got no problems, so i'm sure it's kernel and
not hardware related.

the problem is that sound jumps, flickers and isn't good when harddisk
reads lots of data (i mean not 1-2mb but 60-100mb and more)

i checked irq and there is not conflict, i setted a higher and lower
value of latency and nothing changed.

i've the same problems since 2.6.0 kernels. Vanilla and Gentoo too.
I've tried lots of solutions, like disabling preemptile kernel, adding
alsa and oss, only oss, only alsa, as module or built-in.
nothing changes.

my audio card is a Creative SB PCI128, found by linux as


0000:00:0b.0 Multimedia audio controller: Ensoniq ES1370 [AudioPCI] (rev
01)
        Subsystem: Unknown device 4942:4c4c
        Flags: bus master, slow devsel, latency 32, IRQ 10
        I/O ports at b000

while on Windows i use es1371/3 drivers.
however with 2.4.x i always used es1370 alsa module without problems.
When harddisk is sleeping sound is normally good.

Thanks for support


             reply	other threads:[~2004-06-18 14:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-18 14:03 Hetfield [this message]
2004-06-18 14:12 ` [BUG] 2.6.x ALSA sound is pretty broken Hetfield
2004-06-18 14:35   ` Takashi Iwai
2004-06-18 15:34     ` Hetfield
2004-06-21 18:27       ` Takashi Iwai
2004-06-18 15:57   ` Jeff Garzik
2004-06-18 14:20 ` Lenar Lõhmus
2004-06-18 15:23   ` Hetfield
2004-06-18 14:33 ` Takashi Iwai

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=1087567432.9282.17.camel@blight.blight \
    --to=hetfield666@virgilio.it \
    --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