From: Takashi Iwai <tiwai@suse.de>
To: Erik Welander <erikwel@spray.se>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: ES18xx Bug report and help on ES1878 NoPnP
Date: Tue, 04 Feb 2003 13:27:05 +0100 [thread overview]
Message-ID: <s5hisw0grja.wl@alsa2.suse.de> (raw)
In-Reply-To: <1043956429015333@lycos-europe.com>
At Thu, 30 Jan 2003 20:53:49 +0100,
Erik Welander wrote:
>
> By modifying snd_es18xx_playback_trigger function I tested both dma
> playback functions and here are my findings:
>
> *dma1, i.e.snd_es18xx_playback2 function writeout kern.log:
> (Produces no sound at all. When stopped playing an mp3 with mpg321 gives playback drain error)
> **************************************************************************
> Jan 30 19:30:34 cyberbob kernel: isapnp: Scanning for PnP cards...
> Jan 30 19:30:34 cyberbob kernel: isapnp: No Plug & Play device found
> Jan 30 19:30:35 cyberbob kernel: ALSA ../alsa-kernel/isa/es18xx.c:1569: [0x220] ESS1878 chip found
> Jan 30 19:38:40 cyberbob kernel: ALSA ../alsa-kernel/core/pcm_native.c:1137: playback drain error (DMA or IRQ trouble?)
> ***************************************************************************
please try to play with the pcm "hw:0,0,1", namely,
% aplay -Dhw:0,0,1 foo.wav
if it's ok, then the problem is that the second DAC is not
functional. you can disable the second DAC by specifying the same DMA
value for dma1 and dma2 options. (this will disable the full-duplex,
though.)
Takashi
-------------------------------------------------------
This SF.NET email is sponsored by:
SourceForge Enterprise Edition + IBM + LinuxWorld = Something 2 See!
http://www.vasoftware.com
prev parent reply other threads:[~2003-02-04 12:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-30 19:53 ES18xx Bug report and help on ES1878 NoPnP Erik Welander
2003-02-04 12:27 ` Takashi Iwai [this message]
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=s5hisw0grja.wl@alsa2.suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@lists.sourceforge.net \
--cc=erikwel@spray.se \
/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.