I have a maestro3 in a laptop which is behaving funnily. It works OK
through oss emulation (eg. xmms), but if I try to use aplay, ecasound or
jack I get big overruns. lspci shows:
02:03.0 Multimedia audio controller: ESS Technology ES1983S Maestro-3i PCI Audio
Accelerator (rev 10)
Subsystem: Dell Computer Corporation: Unknown device 00e6
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Step
ping- SERR- FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B+ ParErr- DEVSEL=medium >TAbort- <TAbort-
<MAbort- >SERR- <PERR-
Latency: 32 (500ns min, 6000ns max)
Interrupt: pin A routed to IRQ 5
Region 0: I/O ports at dc00 [size=256]
Region 1: Memory at f6ffe000 (32-bit, non-prefetchable) [size=8K]
Capabilities: [c0] Power Management version 2
Flags: PMEClk- DSI+ D1+ D2+ AuxCurrent=0mA
PME(D0-,D1+,D2+,D3hot+,D3cold-)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
If I run jackd -p 1024 I see:
alsa_pcm: xrun of 2664 frames, (55.500 msecs)
alsa_pcm: xrun of 4776 frames, (99.500 msecs)
alsa_pcm: xrun of 2816 frames, (58.667 msecs)
alsa_pcm: xrun of 4776 frames, (99.500 msecs)
alsa_pcm: xrun of 2792 frames, (58.167 msecs)
alsa_pcm: xrun of 4832 frames, (100.667 msecs)
...
And if I run at 2048 I see:
alsa_pcm: xrun of 4648 frames, (96.833 msecs)
alsa_pcm: xrun of 8616 frames, (179.500 msecs)
alsa_pcm: xrun of 4648 frames, (96.833 msecs)
alsa_pcm: xrun of 8672 frames, (180.667 msecs)
alsa_pcm: xrun of 4656 frames, (97.000 msecs)
alsa_pcm: xrun of 8672 frames, (180.667 msecs)
alsa_pcm: xrun of 4656 frames, (97.000 msecs)
...
aplay quits after a fraction of a second with a xrun error.
It works fine with the native oss driver in 2.4.7.
Cheers,
Steve
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
