From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000384]: Crackly PCM output.
Date: Wed, 10 Nov 2004 12:48:33 +0100 [thread overview]
Message-ID: <ea1b42c7c0b9d0ed93921e4c2b63b37d@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=384>
======================================================================
Reported By: bryanb
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 384
Category: PCI - ymfpci
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: Gentoo dev sources
Kernel Version: 2.6
======================================================================
Date Submitted: 07-13-2004 19:28 CEST
Last Modified: 11-10-2004 12:48 CET
======================================================================
Summary: Crackly PCM output.
Description:
When playing a sound through the speakers on Toshiba Tecra 8100 the only
sound produced is noise.
======================================================================
----------------------------------------------------------------------
c0ldevil - 10-23-04 23:56
----------------------------------------------------------------------
Why is this bug still unassigned? This worked in the 0.5 series and it's an
old bug. I'm not bitchin', if you need any help with this i'll be glad to
lend you a hand in what I can.
OSS sucks...sound quality is soooo bad!
----------------------------------------------------------------------
tiwai - 11-10-04 12:48
----------------------------------------------------------------------
Yeah I know it's a known long-standing bug. Just no time to look at this
yet.
It's likely a missing or wrong initialization of registers.
To compare the registers, please check /proc/asound/card0/ymfpci before
and after loading the OSS ymfpci module. Also, check the output of "lspci
-xxxvv" before and after the OSS, too.
Issue History
Date Modified Username Field Change
======================================================================
07-13-04 19:28 bryanb New Issue
07-13-04 19:28 bryanb Distribution => Gentoo dev sources
07-13-04 19:28 bryanb Kernel Version => 2.6
07-29-04 22:43 codefathers Note Added: 0001485
07-29-04 22:45 codefathers Issue Monitored: codefathers
09-03-04 03:37 Derek_Burdick Issue Monitored: Derek_Burdick
09-03-04 03:40 Derek_Burdick Note Added: 0001684
10-23-04 23:24 c0ldevil Note Added: 0002257
10-23-04 23:27 c0ldevil Note Edited: 0002257
10-23-04 23:55 c0ldevil Note Added: 0002259
10-23-04 23:56 c0ldevil Note Added: 0002260
11-10-04 12:48 tiwai Note Added: 0002369
======================================================================
-------------------------------------------------------
This SF.Net email is sponsored by:
Sybase ASE Linux Express Edition - download now for FREE
LinuxWorld Reader's Choice Award Winner for best database on Linux.
http://ads.osdn.com/?ad_id=5588&alloc_id=12065&op=click
next reply other threads:[~2004-11-10 11:48 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-10 11:48 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-05-31 16:02 [ALSA - driver 0000384]: Crackly PCM output bugtrack
2005-01-18 18:07 bugtrack
2005-01-18 17:44 bugtrack
2005-01-03 13:27 bugtrack
2005-01-03 12:48 bugtrack
2004-12-20 16:42 bugtrack
2004-12-20 16:37 bugtrack
2004-12-20 16:25 bugtrack
2004-12-20 15:59 bugtrack
2004-12-20 15:08 bugtrack
2004-12-16 21:44 bugtrack
2004-11-23 15:15 bugtrack
2004-11-22 13:37 bugtrack
2004-11-22 13:24 bugtrack
2004-11-18 20:05 bugtrack
2004-11-18 18:44 bugtrack
2004-11-18 15:00 bugtrack
2004-11-18 14:56 bugtrack
2004-11-18 14:46 bugtrack
2004-11-18 13:30 bugtrack
2004-11-17 19:39 bugtrack
2004-11-17 19:33 bugtrack
2004-11-17 17:14 bugtrack
2004-10-23 21:56 bugtrack
2004-10-23 21:55 bugtrack
2004-10-23 21:24 bugtrack
2004-09-03 1:40 bugtrack
2004-07-13 17:28 noreply
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=ea1b42c7c0b9d0ed93921e4c2b63b37d@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