From alsa-user-owner@alsa.jcu.cz  Tue Sep 22 17:40:13 1998
Received: from ursa.cus.cam.ac.uk (cusexim@ursa.cus.cam.ac.uk [131.111.8.6])
	by marvin.jcu.cz (8.9.1a/8.9.1) with ESMTP id RAA26466
	for <alsa-user@alsa.jcu.cz>; Tue, 22 Sep 1998 17:40:04 +0200
Received: from mibm1.jims.cam.ac.uk ([131.111.178.181])
	by ursa.cus.cam.ac.uk with esmtp (Exim 2.03 #2)
	id 0zLUXq-0006eT-00
	for alsa-user@alsa.jcu.cz; Tue, 22 Sep 1998 16:40:02 +0100
Date: Tue, 22 Sep 1998 16:37:50 +0100 (BST)
From: James Scott <jes23@cam.ac.uk>
To: alsa-user@alsa.jcu.cz
Subject: Re: Ensoniq ES1371 problems
In-Reply-To: <Pine.A41.4.03.9809221548500.36028-100000@mibm1.jims.cam.ac.uk>
Message-ID: <Pine.A41.4.03.9809221635340.36028-100000@mibm1.jims.cam.ac.uk>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Reply-To: alsa-user@alsa.jcu.cz
Sender: alsa-user-owner@alsa.jcu.cz
Precedence: list


p.s. I thought my machine's going too fast so I tried increasing the
number of iterations in the busy waits in lowlevel/pci/es1370.c but this
had no effect (apart from taking a long time to timeout).


On Tue, 22 Sep 1998, James Scott wrote:

> 
> Hi, 
> 
> I've installed the ALSA driver for my ES1371, and all the modules seem to
> load properly, and interesting things appear in /proc/asound, but whenever
> I try to use it (e.g. cat /dev/mixer or cat a_sound.au > /dev/dsp) I get
> kernel messages like the following:
> 
> Sep 22 14:58:40 rouble kernel: snd: es1371: codec write timeout at 0x1014
> [0x0] 
> Sep 22 14:58:40 rouble kernel: snd: es1371: codec read timeout at 0x1014
> [0x0] 
> 
> any ideas anyone?! 
> 
> James
> 
> 


