All of lore.kernel.org
 help / color / mirror / Atom feed
From: Corvus Corax <corvus-ml@cybertrench.com>
To: Mikael Magnusson <mikaelmagnusson@glocalnet.net>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: lo10K1 not working on x86_64 ?
Date: Wed, 9 Nov 2005 02:04:51 +0100	[thread overview]
Message-ID: <20051109020451.1cc1eb72@VikingPC.home> (raw)
In-Reply-To: <20051103120117.GA27985@skinner.hem.za.org>

Am Thu, 3 Nov 2005 13:01:17 +0100
schrieb Mikael Magnusson <mikaelmagnusson@glocalnet.net>:

> On Wed, Nov 02, 2005 at 09:20:09PM +0100, Corvus Corax wrote:
> > 
> > Hi
> > 
> > It seems like lo10k1 is not working correctly on x86_64
> > 
> > the emu10k1 driver itself works ok, but loading anything (for example
> > with emu_init) results either in
> > 
> > - no change at all
> > - sound in front left speaker distorted
> > - no sound
> > 
> > just running emu_init results in distorted sound
> > 
> > i tried qlo10k1 and loaded several patches manually or unloaded them from
the
> > default provided emu_init. all that changes are different heavy distortions
> > 
> > (distortion = sounds like extreme clipping doe to over amilification)
> > 
> > is the 64bit address stuff causing this, or could as10k1 eventually produce
> > incorrect DSP machine code? (compiled DSP assembler code on x86_64 seems
> > to have differed from code previously assembled on x86, but Im not sure if
the
> > sources were 100% identical)
> 
> Which version of alsa-driver and alsa-tools are you trying. You will
> need at least version 1.0.10rc1, since it contains bug fixes to ld10k1
> that are related to 64bit systems.
> 
> /Mikael
> 

I think I had it running with 1.0.10rc1 on both driver and tools, but Im not
completely sure about alsa-driver anymore.

I have now tested again with both at 1.0.10rc2, everything compiled 64bit.

init_live still creates a setup with heavily distorted output, but when cleaning
the DSP setup with qlo10k1 and setting up a single master volume control slider
and routing from PCM to different speakers, I have been able to change their
volume successfully afterwards - so most of the backend seems to be working.

Maybe specific patches have problems, or the init_live scrip doesnt fit my card,
I'll give it some further tests, trying to find a working routing with adequate
mixer controls. Thanks for answer :-)

regards

Corvus


-------------------------------------------------------
SF.Net email is sponsored by:
Tame your development challenges with Apache's Geronimo App Server. Download
it for free - -and be entered to win a 42" plasma tv or your very own
Sony(tm)PSP.  Click here to play: http://sourceforge.net/geronimo.php

  reply	other threads:[~2005-11-09  1:04 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 [this message]
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

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=20051109020451.1cc1eb72@VikingPC.home \
    --to=corvus-ml@cybertrench.com \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=mikaelmagnusson@glocalnet.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 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.