From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0002200]: PCM channel doesn't exist!
Date: Thu, 29 Jun 2006 17:46:26 +0200 [thread overview]
Message-ID: <12304750153ab8db374aaef710064030@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2200>
======================================================================
Reported By: quetzyg
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 2200
Category: PCI - hda-intel
Reproducibility: always
Severity: minor
Priority: normal
Status: assigned
Distribution: Slackware
Kernel Version: 2.6.16.20 (but any version >= 2.6.16 should be
enough to reproduce this)
======================================================================
Date Submitted: 06-11-2006 17:50 CEST
Last Modified: 06-29-2006 17:46 CEST
======================================================================
Summary: PCM channel doesn't exist!
Description:
Since the early release candidates of ALSA 1.0.11, up to the final version,
I seem to have lost the PCM channel from alsamixer.
======================================================================
----------------------------------------------------------------------
quetzyg - 06-27-06 12:59
----------------------------------------------------------------------
No, all my apps are using ALSA (SoX, MPlayer, MOC, etc). I think that only
the flash plugin for firefox uses OSS.
----------------------------------------------------------------------
tiwai - 06-29-06 17:46
----------------------------------------------------------------------
Strange. Show the generated file via "alsactl -f file store". It's more
obvious than amixer output.
Also, provide more hardware information (the machine, the codec chip)
especially for HD-audio stuff. The behavior of that driver is sooooooooo
dependent upon the h/w and system you use.
Issue History
Date Modified Username Field Change
======================================================================
06-11-06 17:50 quetzyg New Issue
06-11-06 17:50 quetzyg Distribution => Slackware
06-11-06 17:50 quetzyg Kernel Version => 2.6.16.20 (but any
version >= 2.6.16 should be enough to reproduce this)
06-11-06 17:51 quetzyg Issue Monitored: quetzyg
06-27-06 12:47 quetzyg Note Added: 0010587
06-27-06 12:52 tiwai Note Added: 0010589
06-27-06 12:59 quetzyg Note Added: 0010590
06-29-06 17:46 tiwai Note Added: 0010675
======================================================================
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-06-29 15:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-29 15:46 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-07-06 13:52 [ALSA - driver 0002200]: PCM channel doesn't exist! bugtrack
2006-07-05 21:26 bugtrack
2006-06-29 16:51 bugtrack
2006-06-27 10:59 bugtrack
2006-06-27 10:52 bugtrack
2006-06-27 10:47 bugtrack
2006-06-11 15:50 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=12304750153ab8db374aaef710064030@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