From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000387]: No soundcard detected on Chaintech ZNF3-250
Date: Mon, 22 Nov 2004 14:50:23 +0100 [thread overview]
Message-ID: <68cd6fd87af8e9b29d82fbc0410be688@bugtrack.alsa-project.org> (raw)
The following issue has been CLOSED
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=387>
======================================================================
Reported By: silent_runner
Assigned To: perex
======================================================================
Project: ALSA - driver
Issue ID: 387
Category: PCI - ice1724
Reproducibility: always
Severity: block
Priority: normal
Status: closed
Distribution: Gentoo
Kernel Version: 2.6.7 kernel.org stock
Resolution: suspended
Fixed in Version:
======================================================================
Date Submitted: 07-13-2004 21:48 CEST
Last Modified: 11-22-2004 14:50 CET
======================================================================
Summary: No soundcard detected on Chaintech ZNF3-250
Description:
cat /proc/asound/cards gives --no souncards--
======================================================================
----------------------------------------------------------------------
perex - 10-22-04 17:02
----------------------------------------------------------------------
No response from user.
----------------------------------------------------------------------
tiwai - 11-22-04 14:50
----------------------------------------------------------------------
Now closed. Please reopen if you can try the patch.
Issue History
Date Modified Username Field Change
======================================================================
07-13-04 21:48 silent_runner New Issue
07-13-04 21:48 silent_runner File Added: command-outputs.tar.bz2
07-13-04 21:48 silent_runner Distribution => Gentoo
07-13-04 21:48 silent_runner Kernel Version => 2.6.7 kernel.org
stock
07-13-04 22:18 silent_runner Issue Monitored: silent_runner
07-27-04 13:50 silent_runner Issue Monitored: perex
07-27-04 13:50 silent_runner Note Added: 0001476
07-30-04 17:03 tiwai Note Added: 0001494
07-30-04 17:03 tiwai File Added: chaintech.dif
10-22-04 17:02 perex Status new => resolved
10-22-04 17:02 perex Resolution open => suspended
10-22-04 17:02 perex Assigned To => perex
10-22-04 17:02 perex Note Added: 0002251
11-22-04 14:50 tiwai Status resolved => closed
11-22-04 14:50 tiwai Note Added: 0002505
======================================================================
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
next reply other threads:[~2004-11-22 13:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-22 13:50 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-10-22 15:02 [ALSA - driver 0000387]: No soundcard detected on Chaintech ZNF3-250 bugtrack
2004-07-13 19:48 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=68cd6fd87af8e9b29d82fbc0410be688@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