openvortex-dev
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Openvortex-dev] Aureal Advantage (8810) problem


From: Kovacs Krisztian
Subject: Re: [Openvortex-dev] Aureal Advantage (8810) problem
Date: Tue, 13 Jan 2004 11:24:11 +0100
User-agent: Mutt/1.4i

  Hi,

On Mon, Jan 12, 2004 at 10:07:36PM -0400, Manuel Jander wrote:
> Thanks for reporting this. It would be very interested in knowing more
> about your computer (CPU, mainboard), specific Aureal Vortex sound card,
> any other hardware you have installed (output of "lspci -vvv" would be
> very useful).

  I have an Asus A7V-E, with VIA KT133 chipset, and a Duron 750 CPU. I've
changed PCI register 40 to 0xff, so that it works at all. (This fix is
needed on Windows, of course.) I'll send lspci info later, since I'm not
home at the moment...

> >   When loading the driver, I get the following messages:
> > kecske kernel: PCI: Found IRQ 9 for device 0000:00:0f.0
> > kecske kernel: Vortex: hardware init.... <6>done.
> > kecske kernel: SDAC detected <3>vortex: unknown irq source 4
> 
> This warnings are OK, except "vortex: unknown irq source 4". Since we
> reverse engineered the driver from the windows binary driver, we don't
> have any documentation about the chip. That means we have still no idea
> what the IRQ source flag "4" stands for, hence the warning.

  Actually I tried modifying the driver to acknowledge the IRQ, and I
think it helps a bit. However, sometimes these changes still occur. Do you
have any idea about where the interrupt handler of the disassembled
windows driver can be found? (I've found that on your homepage, but had no
luck finding the IRQ handler.)

> >   I had a look at the source, it seems that vortex_interrupt() handler is
> > getting interrupts from an unknown source. When the handler gets the
> > source from the VORTEX_IRQ_SOURCE register, it gets 4... I've added a few
> > debug messages, and it looks that sometimes it even gets 1004. (1000 would
> > be IRQ_SOURCE_TIMER, but what is 4?)
> > 
> >   Even worse, sometimes I get a lot of ALSA warning messages:
> > 
> > kecske kernel: ALSA sound/core/pcm_lib.c:186: Unexpected hw_pointer value
> > [1] (stream = 0, delta: -597, max jitter = 8192): wrong interrupt 
> > acknowledge?
> > kecske kernel: ALSA sound/core/pcm_lib.c:186: Unexpected hw_pointer value
> > [1] (stream = 0, delta: -84, max jitter = 8192): wrong interrupt 
> > acknowledge?
> > kecske kernel: ALSA sound/core/pcm_lib.c:186: Unexpected hw_pointer value
> > [1] (stream = 0, delta: -850, max jitter = 8192): wrong interrupt 
> > acknowledge?
> 
> How often do you get them ? Every then and when or at a higher rate
> (more than one per second) ?

  There is not too much correspondence between the pitches and these
messages (at least it is not obvious), I get them only about five times
per minute. I'll provide more info when I'll have access to the logs.

> There is are changes to come in the routing setup of the driver, once we
> integrate 3D positional audio into the stable driver branch.
> But if you want, you could try this driver snapshot:
> http://galadriel.mat.utfsm.cl/~mjander/aureal/alsa/alsa-new-23-10-2003.tgz

  Thanks, I'll try it.

-- 
 Kovács Krisztián (Hidden)





reply via email to

[Prev in Thread] Current Thread [Next in Thread]