From: Martin Schlemmer <azarah@nosferatu.za.org>
To: "Martin J. Bligh" <mbligh@aracnet.com>
Cc: Linux Kernel Mailing Lists <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0 sound output - wierd effects
Date: Sat, 27 Dec 2003 00:52:47 +0200 [thread overview]
Message-ID: <1072479167.21020.59.camel@nosferatu.lan> (raw)
In-Reply-To: <1080000.1072475704@[10.10.2.4]>
[-- Attachment #1: Type: text/plain, Size: 1147 bytes --]
On Fri, 2003-12-26 at 23:55, Martin J. Bligh wrote:
> Upgraded my home desktop to 2.6.0.
> Somewhere between 2.5.63 and 2.6.0, sound got screwed up - I've confirmed
> this happens on mainline, as well as -mjb.
>
> If I leave xmms playing (in random shuffle mode) every 2 minutes or so,
> I'll get some wierd effect for a few seconds, either static, or the track
> will mysteriously speed up or slow down. Then all is back to normal for
> another couple of minutes.
>
> Anyone else seen this, or got any clues? Else I guess I'm stuck playing
> bisection search.
>
> Advanced Linux Sound Architecture Driver Version 0.9.7 (Thu Sep 25 19:16:36 2003 UTC).
> PCI: Found IRQ 11 for device 0000:00:02.7
> intel8x0: clocking to 48000
> ALSA device list:
> #0: SiS SI7012 at 0xdc00, irq 11
>
> AMD Athlon(tm) XP 2100+, no power management or ACPI compiled in.
>
I have had this as well, around there, and started using OSS, which
worked fine (ICH5 onboard - also). Somewhere when I tried again, it
worked fine, so this is what I am using now. What version userland
libs/utils ? OSS emulation?
--
Martin Schlemmer
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-12-26 22:50 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-26 21:55 2.6.0 sound output - wierd effects Martin J. Bligh
2003-12-26 22:27 ` Sven-Haegar Koch
2003-12-27 16:14 ` Martin J. Bligh
2003-12-26 22:52 ` Martin Schlemmer [this message]
2003-12-26 23:00 ` Martin J. Bligh
2003-12-26 23:17 ` Martin Schlemmer
2003-12-26 23:24 ` Martin J. Bligh
2003-12-26 23:50 ` Martin Schlemmer
2003-12-26 23:59 ` Martin J. Bligh
2003-12-27 0:44 ` Martin Schlemmer
2003-12-27 0:53 ` Martin Schlemmer
2003-12-27 4:34 ` Martin J. Bligh
2003-12-27 11:12 ` Martin Schlemmer
2003-12-27 16:17 ` Martin J. Bligh
2003-12-27 4:48 ` Stan Bubrouski
2003-12-27 4:57 ` Rob Love
2003-12-27 5:02 ` Martin J. Bligh
2003-12-27 5:10 ` Rob Love
2003-12-27 5:45 ` Stan Bubrouski
2003-12-27 22:44 ` szonyi calin
2003-12-27 7:50 ` OSS sound emulation broken between 2.6.0-test2 and test3 Martin J. Bligh
2003-12-27 11:11 ` Martin Schlemmer
2003-12-27 11:44 ` Edward Tandi
2003-12-27 12:24 ` Martin Schlemmer
2003-12-27 13:08 ` Edward Tandi
2003-12-27 14:33 ` Martin Schlemmer
2003-12-27 16:55 ` Edward Tandi
2003-12-27 17:22 ` Martin Schlemmer
2003-12-27 21:56 ` Henrik Storner
2003-12-27 22:51 ` Edward Tandi
2003-12-27 18:35 ` Martin J. Bligh
2003-12-27 19:56 ` Jaroslav Kysela
2003-12-27 20:12 ` Martin J. Bligh
2003-12-27 20:25 ` Martin Schlemmer
2003-12-27 20:44 ` Martin Schlemmer
2003-12-28 0:27 ` Martin J. Bligh
2004-01-03 0:53 ` Chris Shafer
2004-01-03 22:23 ` Martin Schlemmer
2003-12-28 5:06 ` Joshua Schmidlkofer
2003-12-26 22:59 ` 2.6.0 sound output - wierd effects Sander Sweers
2003-12-26 23:02 ` Martin J. Bligh
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=1072479167.21020.59.camel@nosferatu.lan \
--to=azarah@nosferatu.za.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mbligh@aracnet.com \
/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.