From: Corvus Corax <corvus-ml@cybertrench.com>
To: Peter Zubaj <pzad@pobox.sk>
Cc: Mikael Magnusson <mikaelmagnusson@glocalnet.net>,
alsa-devel@lists.sourceforge.net
Subject: Re: lo10K1 not working on x86_64 ?
Date: Wed, 9 Nov 2005 22:47:55 +0100 [thread overview]
Message-ID: <20051109224755.6241b354@VikingPC.home> (raw)
In-Reply-To: <1131562953.4679.12.camel@localhost.localdomain>
[-- Attachment #1: Type: text/plain, Size: 931 bytes --]
Am Wed, 09 Nov 2005 20:02:33 +0100
schrieb Peter Zubaj <pzad@pobox.sk>:
> Could you send output of lo10k1 when this happen ?
>
> lo10k1 --debug 1
> lo10k1 --debug 2
> lo10k1 --debug 3
> lo10k1 --debug 4
> lo10k1 --debug 5
> lo10k1 --debug 6
> lo10k1 --debug 7
> lo10k1 --debug 8
> lo10k1 --debug 9
>
> and for every loaded effect (less loaded effect will be better)
> lo10k1 --debug 100
> lo10k1 --debug 101
>
> up to last loaded (for example if there are 5 loaded last will be 104)
>
> lo10k1 --debug 104
>
> and content of fx8010_acode from /proc/asound card directory) too
yep, tar.gz has been attached for 5 different setups,
2 of them in "distorted condition".
when glancing at it I noticed that parts of the DSP memory seem to be zeroed out
once the distortion occurs, looks like something goes seriously wrong on
loading the patches.
tell me if you need any additional information.
thanks and best regards
Corvus
[-- Attachment #2: emu10k1_debug_corvus.tgz --]
[-- Type: application/x-compressed-tar, Size: 25511 bytes --]
prev parent reply other threads:[~2005-11-09 21:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-02 20:20 lo10K1 not working on x86_64 ? Corvus Corax
2005-11-03 12:01 ` Mikael Magnusson
2005-11-09 1:04 ` Corvus Corax
2005-11-09 13:13 ` Corvus Corax
2005-11-09 18:47 ` D. Hugh Redelmeier
2005-11-09 22:18 ` Corvus Corax
2005-11-09 22:36 ` Corvus Corax
2005-11-09 22:49 ` Corvus Corax
2005-11-10 17:09 ` D. Hugh Redelmeier
2005-11-10 22:24 ` Corvus Corax
2005-11-09 19:02 ` Peter Zubaj
2005-11-09 21:47 ` Corvus Corax [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=20051109224755.6241b354@VikingPC.home \
--to=corvus-ml@cybertrench.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=mikaelmagnusson@glocalnet.net \
--cc=pzad@pobox.sk \
/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.