From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - utils 0002134]: arecord doesn't work in amd x86_64 X2 dual core.
Date: Mon, 22 May 2006 17:47:45 +0200 [thread overview]
Message-ID: <e429923978124e88f93fc57d72a11a9a@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2134>
======================================================================
Reported By: bolsog
Assigned To:
======================================================================
Project: ALSA - utils
Issue ID: 2134
Category: aplay/arecord
Reproducibility: always
Severity: major
Priority: normal
Status: new
======================================================================
Date Submitted: 05-18-2006 13:25 CEST
Last Modified: 05-22-2006 17:47 CEST
======================================================================
Summary: arecord doesn't work in amd x86_64 X2 dual core.
Description:
arecord doen't work on a amd x86_64 X2 dual core.
examples:
arecord -d 10 -c 2 -f S16_LE -r 32000 foo.wav
arecord -d 10 -f S16_LE -r 48000 foo.wav
arecord -d 10 -f S16_LE -r 32000 foo.wav
arecord -d 10 -f S16_LE -r 16000 foo.wav
all examples must be terminated using Ctrl-c and only the 44 byte header
is saved.
The soundcard is a
Multimedia audio controller: nVidia Corporation CK804 AC'97 Audio
Controller
(rev a2)
We tested this problem on a similar pc with amd x86_64 single core with
the same
soundcard and all works fine.
aplay works on both pcs without problems!
We tested on Fedora Core 4 (1.0.10) and Fedora Core 5 (1.0.11rc2)
We need recording on this pc, so we appreciate every help. Thanks.
======================================================================
----------------------------------------------------------------------
bolsog - 05-22-06 11:57
----------------------------------------------------------------------
| arecord -v -D hw:0,0 -d 10 -f S16_LE -r 48000 foo.wav
Recording WAVE 'foo.wav' : Signed 16 bit Little Endian, Rate 48000 Hz,
Stereo
Hardware PCM card 0 'NVidia CK804' device 0 subdevice 0
Its setup is:
stream : CAPTURE
access : RW_INTERLEAVED
format : S16_LE
subformat : STD
channels : 2
rate : 48000
exact rate : 48000 (48000/1)
msbits : 16
buffer_size : 16384
period_size : 4096
period_time : 85333
tick_time : 4000
tstamp_mode : NONE
period_step : 1
sleep_min : 0
avail_min : 4096
xfer_align : 4096
start_threshold : 1
stop_threshold : 16384
silence_threshold: 0
silence_size : 0
boundary : 4611686018427387904
arecord: pcm_read:1338: read error: Eingabe-/Ausgabefehler
--
And foo.wav wasn't created.
Eingabe-/Ausgabefehler means Input/Output-error.
Our FC5 is installed with German root-account.
---
| arecord -v -D plughw:0,0 -d 10 -f S16_LE -r 48000 foo.wav
Recording WAVE 'foo.wav' : Signed 16 bit Little Endian, Rate 48000 Hz,
Mono
Plug PCM: Route conversion PCM (sformat=S16_LE)
Transformation table:
0 <- 0*0,5 + 1*0,5
Its setup is:
stream : CAPTURE
access : RW_INTERLEAVED
format : S16_LE
subformat : STD
channels : 1
rate : 48000
exact rate : 48000 (48000/1)
msbits : 16
buffer_size : 16384
period_size : 4096
period_time : 85333
tick_time : 4000
tstamp_mode : NONE
period_step : 1
sleep_min : 0
avail_min : 4096
xfer_align : 4096
start_threshold : 1
stop_threshold : 16384
silence_threshold: 0
silence_size : 0
boundary : 4611686018427387904
Slave: Hardware PCM card 0 'NVidia CK804' device 0 subdevice 0
Its setup is:
stream : CAPTURE
access : MMAP_INTERLEAVED
format : S16_LE
subformat : STD
channels : 2
rate : 48000
exact rate : 48000 (48000/1)
msbits : 16
buffer_size : 16384
period_size : 4096
period_time : 85333
tick_time : 4000
tstamp_mode : NONE
period_step : 1
sleep_min : 0
avail_min : 4096
xfer_align : 4096
start_threshold : 1
stop_threshold : 16384
silence_threshold: 0
silence_size : 0
boundary : 4611686018427387904
--
This command never stops. I pressed Ctrl-C and a 44byte foo.wav was
created.
--
I've used the root-account for both commands.
----------------------------------------------------------------------
Raymond - 05-22-06 17:47
----------------------------------------------------------------------
Please post output of
arecord -L
Issue History
Date Modified Username Field Change
======================================================================
05-18-06 13:25 bolsog New Issue
05-21-06 14:12 Raymond Note Added: 0009899
05-21-06 14:13 Raymond Note Edited: 0009899
05-21-06 14:15 Raymond Note Edited: 0009899
05-22-06 11:57 bolsog Note Added: 0009907
05-22-06 17:47 Raymond Note Added: 0009917
======================================================================
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
next reply other threads:[~2006-05-22 15:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-22 15:47 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-05-23 16:37 [ALSA - utils 0002134]: arecord doesn't work in amd x86_64 X2 dual core bugtrack
2006-05-23 12:39 bugtrack
2006-05-22 16:52 bugtrack
2006-05-22 9:57 bugtrack
2006-05-21 12:12 bugtrack
2006-05-18 11:25 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=e429923978124e88f93fc57d72a11a9a@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