From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000709]: Recording doesnt work
Date: Tue, 7 Dec 2004 18:28:54 +0100 [thread overview]
Message-ID: <a3d8df0928db571ae55c1de7900aeee2@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=709>
======================================================================
Reported By: tigermb
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 709
Category: PCI - via82xx
Reproducibility: always
Severity: minor
Priority: normal
Status: new
Distribution:
Kernel Version:
======================================================================
Date Submitted: 12-05-2004 16:33 CET
Last Modified: 12-07-2004 18:28 CET
======================================================================
Summary: Recording doesnt work
Description:
Soundcard: Multimedia audio controller: VIA Technologies, Inc.
VT8233/A/8235/8237 AC97 Audio Controller (rev 60)
The recording doesnt work.
When trying to record, nuthing happens. No errors. Although gnome-meeting
got an error and wonders if i have permission to device. But i tried it
under root and i get the same error. arecord give no error, but just
doesnt do anything.
======================================================================
----------------------------------------------------------------------
tigermb - 12-07-04 18:23
----------------------------------------------------------------------
Lots of notes, but the error somehow disappeared, played i little with the
mixer setting i think. Now it hangs again. I have the strace of arecord
----------------------------------------------------------------------
tiwai - 12-07-04 18:28
----------------------------------------------------------------------
The attached strace shows obviously that the device is blocked.
It's being used by other applications. It's not a bug at all.
If you get the I/O error (this appears after a certain wait time), it
means the DMA doesn't run properly. Tuning the "Input Source Select"
often helps in the case of via82xx.
Also, make sure that you have no strange /etc/asound.conf and ~/.asoundrc
for testing. Use the only default configuration.
Issue History
Date Modified Username Field Change
======================================================================
12-05-04 16:33 tigermb New Issue
12-05-04 16:34 tigermb Issue Monitored: tigermb
12-06-04 20:59 tiwai Note Added: 0002735
12-06-04 23:24 tigermb File Added: asound.state
12-06-04 23:25 tigermb Note Added: 0002738
12-07-04 14:32 tiwai Note Added: 0002747
12-07-04 17:59 tigermb Note Added: 0002750
12-07-04 18:01 tigermb Note Added: 0002751
12-07-04 18:22 tigermb File Added: strace.log
12-07-04 18:23 tigermb Note Added: 0002752
12-07-04 18:28 tiwai Note Added: 0002754
======================================================================
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next reply other threads:[~2004-12-07 17:28 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-07 17:28 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-01-11 15:53 [ALSA - driver 0000709]: Recording doesnt work bugtrack
2004-12-08 19:10 bugtrack
2004-12-08 16:01 bugtrack
2004-12-08 11:10 bugtrack
2004-12-07 21:21 bugtrack
2004-12-07 17:23 bugtrack
2004-12-07 17:01 bugtrack
2004-12-07 16:59 bugtrack
2004-12-07 13:32 bugtrack
2004-12-06 22:25 bugtrack
2004-12-06 19:59 bugtrack
2004-12-05 15:33 bugtrack
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=a3d8df0928db571ae55c1de7900aeee2@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--cc=alsa-devel@alsa-project.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox