From: noreply@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000384]: Crackly PCM output.
Date: Tue, 13 Jul 2004 19:28:55 +0200 [thread overview]
Message-ID: <4e818a5d73900b3aae04752ef5471bd6@bugtrack.alsa-project.org> (raw)
The following bug has been SUBMITTED.
======================================================================
https://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=0000384
======================================================================
Reported By: bryanb
Assigned To:
======================================================================
Project: ALSA - driver
Bug 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: 07-13-2004 19:28 CEST
======================================================================
Summary: Crackly PCM output.
Description:
When playing a sound through the speakers on Toshiba Tecra 8100 the only
sound produced is noise.
======================================================================
Bug History
Date Modified Username Field Change
======================================================================
07-13-04 19:28 bryanb New Bug
07-13-04 19:28 bryanb Distribution => Gentoo dev sources
07-13-04 19:28 bryanb Kernel Version => 2.6
======================================================================
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
next reply other threads:[~2004-07-13 17:28 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-13 17:28 noreply [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-09-03 1:40 [ALSA - driver 0000384]: Crackly PCM output bugtrack
2004-10-23 21:24 bugtrack
2004-10-23 21:55 bugtrack
2004-10-23 21:56 bugtrack
2004-11-10 11:48 bugtrack
2004-11-17 17:14 bugtrack
2004-11-17 19:33 bugtrack
2004-11-17 19:39 bugtrack
2004-11-18 13:30 bugtrack
2004-11-18 14:46 bugtrack
2004-11-18 14:56 bugtrack
2004-11-18 15:00 bugtrack
2004-11-18 18:44 bugtrack
2004-11-18 20:05 bugtrack
2004-11-22 13:24 bugtrack
2004-11-22 13:37 bugtrack
2004-11-23 15:15 bugtrack
2004-12-16 21:44 bugtrack
2004-12-20 15:08 bugtrack
2004-12-20 15:59 bugtrack
2004-12-20 16:25 bugtrack
2004-12-20 16:37 bugtrack
2004-12-20 16:42 bugtrack
2005-01-03 12:48 bugtrack
2005-01-03 13:27 bugtrack
2005-01-18 17:44 bugtrack
2005-01-18 18:07 bugtrack
2005-05-31 16:02 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=4e818a5d73900b3aae04752ef5471bd6@bugtrack.alsa-project.org \
--to=noreply@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