From: "Valdis Klētnieks" <valdis.kletnieks@vt.edu>
To: Muni Sekhar <munisekharrms@gmail.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>,
linux-usb@vger.kernel.org, linux-sound@vger.kernel.org,
kernelnewbies <kernelnewbies@kernelnewbies.org>
Subject: Re: USB sound card issues
Date: Fri, 11 Jun 2021 19:46:34 -0400 [thread overview]
Message-ID: <26698.1623455194@turing-police> (raw)
In-Reply-To: <CAHhAz+haTa8FJep+mokae4O7Gy9zzq2dbPk28fuEH5FO24uTzw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 643 bytes --]
On Tue, 08 Jun 2021 16:20:07 +0530, Muni Sekhar said:
> $ arecord --device hw:1,0 --channels 1 --format S16_LE --rate 32000_Hz x.wav
> Recording WAVE 'x.wav' : Signed 16 bit Little Endian, Rate 32000 Hz, Mono
> arecord: pcm_read:2032: read error: Input/output error
Always check the obvious stuff first does the card support S16_LE 32Khz data?
And if it's configurable for multiple formats, was it set for the correct one?
Does wireshark or other USB snoop program show any traffic at all?
Does the record die immediately, or hang for a few seconds and timeout?
Does 'arecord -v' or arecord -vv' tell us anything more about the situation?
[-- Attachment #1.2: Type: application/pgp-signature, Size: 832 bytes --]
[-- Attachment #2: Type: text/plain, Size: 170 bytes --]
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2021-06-11 23:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-08 10:50 USB sound card issues Muni Sekhar
2021-06-08 11:14 ` Greg KH
2021-06-08 12:14 ` Muni Sekhar
2021-06-08 12:31 ` Greg KH
2021-06-08 12:45 ` Muni Sekhar
2021-06-08 13:03 ` Greg KH
2021-06-11 23:46 ` Valdis Klētnieks [this message]
2021-06-12 11:15 ` Muni Sekhar
2021-06-15 6:14 ` Valdis Klētnieks
2021-06-15 7:00 ` Muni Sekhar
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=26698.1623455194@turing-police \
--to=valdis.kletnieks@vt.edu \
--cc=alsa-devel@alsa-project.org \
--cc=kernelnewbies@kernelnewbies.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=munisekharrms@gmail.com \
/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;
as well as URLs for NNTP newsgroup(s).