mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Voluspa <voluspa@bigfoot.com>
To: Zach Brown <zab@zabbo.net>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: Re: 2.4.19 MAESTRO sound /dev/dsp3 broken (luxury problem)
Date: Wed, 7 Aug 2002 03:11:49 +0200	[thread overview]
Message-ID: <20020807031149.7a9ea69f.voluspa@bigfoot.com> (raw)
In-Reply-To: <20020806155943.C15208@erasmus.off.net>

On Tue, 6 Aug 2002 15:59:43 -0400
Zach Brown <zab@zabbo.net> wrote:

> > Can you try and find out exactly which kernel it broke at. The only
> > maestro change Im aware of was in rc1-ac7 and wouldn't have that affect
> > in any way I can imagine..
> 
> I remember reports from the depths of time that dsp3 didn't work.  I
> wonder if there is some generation of chip that has a faulty set of high
> apus.

The embarrasing thing is, I can't boot back to a working kernel. Having completed a marathon compilation I discover that it doesn't work even where it used to. Almost as if something physical has been blown to smithereens.

I'm not (overly) crazy. It _did_ work in 2.4.19-pre10-ac1+preempt. RealOne Player was bound through the environment variable AUDIO=/dev/dsp3 and gqmpeg had been configured to use /dev/dsp2.

Btw, what I called 'a cry from the wilderness' is heavily distorted audio, at a volume about twice as high as the working channels are set to (which practically means maximum...)

You won't hear from me again unless a miracle happens...

Sorry to have wasted peoples time/bandwidth,
Mats Johannesson

      reply	other threads:[~2002-08-07  1:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-05 22:40 Voluspa
2002-08-06  0:20 ` Alan Cox
2002-08-06 19:59   ` Zach Brown
2002-08-07  1:11     ` Voluspa [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=20020807031149.7a9ea69f.voluspa@bigfoot.com \
    --to=voluspa@bigfoot.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zab@zabbo.net \
    /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

all inboxes | Powered by JetHome®