Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
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: Thu, 18 May 2006 13:25:51 +0200	[thread overview]
Message-ID: <90bef740b4fbecafa0cf9cfb68e6826e@bugtrack.alsa-project.org> (raw)


The following issue has been SUBMITTED.
======================================================================
<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-18-2006 13:25 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.
======================================================================

Issue History
Date Modified  Username       Field                    Change              
======================================================================
05-18-06 13:25 bolsog         New Issue                                    
======================================================================




-------------------------------------------------------
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

             reply	other threads:[~2006-05-18 11:25 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18 11:25 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-05-21 12:12 [ALSA - utils 0002134]: arecord doesn't work in amd x86_64 X2 dual core bugtrack
2006-05-22  9:57 bugtrack
2006-05-22 15:47 bugtrack
2006-05-22 16:52 bugtrack
2006-05-23 12:39 bugtrack
2006-05-23 16:37 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=90bef740b4fbecafa0cf9cfb68e6826e@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