Re: [Openvortex-dev] Distorted sound with alsa drivers

[Jeff Muizelaar]

On 14 May 2003, Marc Heerdink wrote:

> Op wo 14-05-2003, om 00:58 schreef Jeff Muizelaar:
> [..]
> > Your mixer settings are sane right? Do things play at the proper speed?
> > Other than that I don't have any ideas as to what might be causing it.
>
> Things sometimes play faster than they should, let's say 150-200%.
> Usually after stopping playback and starting it again, the speed is
> normal again. Then after a while, it's getting fast again.

Yeah I see this here as well.

> The mixer settings are sane, they're always 100/100.

Having them set that high can cause problems. try lowering them to 70-80
and see if the problem persists.

> > Does anything other than this type of stuff show up in the logs?
> >
> > vortex: start 0
> > vortex: stop 0
> > vortex: start 0
> > vortex: stop 0
> > vortex: de alloc 0
> > Vortex: periods 16, period_bytes 4096, channels = 1
> > vortex: alloc 0
> > Vortex: periods 16, period_bytes 4096, channels = 1
> > vortex: de alloc 0
> > vortex: alloc 0
> > Vortex: periods 16, period_bytes 4096, channels = 2
> > vortex: de alloc 0
> > vortex: alloc 0
> > Vortex: periods 16, period_bytes 4096, channels = 2
> > vortex: de alloc 0
> > vortex: alloc 0
> > vortex: start 0
>
> That's all there is in the logs :/ Many of those periods lines, that's
> all. A total of 310 lines for 24 seconds of playback..

This seems high...

> > > I have a Diamond Monster Sound II with an Aureal Vortex2/au8830 chip. If
> > > you need other info, I'll be glad to provide it.
> >
> > how about a lspci -vvnd 12eb:0002 just for reference.
>
> 00:0a.0 Class 0401: 12eb:0002 (rev fe)
>         Subsystem: 1092:3003
>         Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop-
> ParErr- Stepping- SERR- FastB2B-
>         Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort-
> <TAbort- <MAbort- >SERR- <PERR-
>         Latency: 32 (1000ns min, 3000ns max), cache line size 08
>         Interrupt: pin A routed to IRQ 5
>         Region 0: Memory at e0000000 (32-bit, non-prefetchable)
> [size=256K]
>         Region 1: I/O ports at a400 [size=8]
>         Region 2: I/O ports at a000 [size=8]
>         Capabilities: [dc] Power Management version 1
>                 Flags: PMEClk- DSI+ D1- D2+ AuxCurrent=0mA
> PME(D0-,D1-,D2-,D3hot-,D3cold-)
>                 Status: D0 PME-Enable- DSel=0 DScale=0 PME-
>
>
>
> Completely different question: is the setpci fix still needed with the
> alsa driver on Via boards?

Who knows, this fix is very much a mystery...

-Jeff