From: Andrew Rodland <arodland@noln.com>
To: DevilKin <devilkin-lkml@blindguardian.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NM256: Sound playback pointer invalid!
Date: Thu, 13 Jun 2002 11:03:42 -0400 [thread overview]
Message-ID: <20020613110342.3eb63bf0.arodland@noln.com> (raw)
In-Reply-To: <200206131119.26862.devilkin-lkml@blindguardian.org>
On Thu, 13 Jun 2002 11:19:26 +0200
DevilKin <devilkin-lkml@blindguardian.org> wrote:
I have the identical symptom, I haven't come up with a cure.
Giving it a thought now, though, why not just sox out a very short (and
silent, if you want) wave file at boot? That way at least the first
thing played won't be something you really wanted to hear.
I've also noticed that while this is going on, whatever app is trying to
play sound generally gets bogged down, probably because the "noise"
plays about half as fast as the proper sound.
I've tried ALSA, but it always locks up after "Found IRQ X for pci
Y.Z:T" or whatever it is, for reasons unknown to me, even after adding
much printk. If anyone really cares, I might recreate my debug output.
Oddly enough, I'm also running 2.4.19-pre10-ac2+preempt+hobbs (the last
being a tiny hack to the mtrr code, and not related to the problem), and
I was running 2.4.18 at the time I got this laptop.
Are you saying that older kernels work properly? I've got a copy of
2.4.17 around here somewhere, I might look at the diffs...
Anyway, thanks for forcing me to think about it
--hobbs
> Hello,
>
> Since upgrading to 2.4.18 (tested with later kernels too, running
> 2.4.19-pre10-ac2 right now) I have the following problem: every time
> my soundchip is activated for the first time, it makes a horrible
> screetching noise. Just plain horrible. After that, playback is
> perfect.
>
> In the logs i get:
>
> NM256: Sound playback pointer invalid!
>
> I've looked on the net for some info, but I haven't been able to find
> anything that really cures this problem.
>
> Anything else I can try?
>
> Thanks!
>
> DK
>
> --
> You worry too much about your job. Stop it. You're not paid enough
> to worry.
>
> -
> 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:[~2002-06-13 15:04 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-13 9:19 NM256: Sound playback pointer invalid! DevilKin
2002-06-13 15:03 ` Andrew Rodland [this message]
2002-06-22 2:09 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-06-27 13:15 Drew Myers
2003-02-03 18:09 Orion Poplawski
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=20020613110342.3eb63bf0.arodland@noln.com \
--to=arodland@noln.com \
--cc=devilkin-lkml@blindguardian.org \
--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