From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000219]: Only pcm-2 (headphone) volume control works, others muted(?)
Date: Wed, 23 Mar 2005 16:06:12 +0100 [thread overview]
Message-ID: <1355c8d9daab0f287766f3f786db4a29@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=219>
======================================================================
Reported By: JonB
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 219
Category: PCI - intel8x0
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: Slackware 9.1
Kernel Version: 2.4.24
======================================================================
Date Submitted: 04-17-2004 12:23 CEST
Last Modified: 03-23-2005 16:06 CET
======================================================================
Summary: Only pcm-2 (headphone) volume control works, others
muted(?)
Description:
Tried various applications from CLI and Dropline GNOME 2.6.0 to get sound
output. Dell Inspiron 5150 laptop with 82801DBICH4.
Master volume control, PCM, CD, Video have no effect on sound volume - no
sound output from external speakers. Plugin headphones and can vary sound
through headphones using the headphone control (also known as pcm-2 in
aumix).
Playing any CD with the GNOME CD Player does not produce any sound through
headphones or speakers.
Playing through headphones - only the headphone control has any effect.
The master control has no effect.
Have included output from various parts of the system including lspci,
asound.state and some information in /proc/asound/card0.
Sound was working in 1.0.2 (except PCM control was intermittent) -
internal speakers worked, master volume control worked, etc.
======================================================================
----------------------------------------------------------------------
jdthood - 03-23-05 16:06
----------------------------------------------------------------------
Try switching on 'External Amplifier'.
Issue History
Date Modified Username Field Change
======================================================================
04-17-04 12:23 JonB New Issue
04-17-04 12:23 JonB File Added: intel8x0
04-17-04 12:23 JonB Distribution => Slackware 9.1
04-17-04 12:23 JonB Kernel Version => 2.4.24
03-23-05 16:06 jdthood Note Added: 0004171
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: 2005 Windows Mobile Application Contest
Submit applications for Windows Mobile(tm)-based Pocket PCs or Smartphones
for the chance to win $25,000 and application distribution. Enter today at
http://ads.osdn.com/?ad_id=6882&alloc_id=15148&op=click
next reply other threads:[~2005-03-23 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-23 15:06 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-29 10:13 [ALSA - driver 0000219]: Only pcm-2 (headphone) volume control works, others muted(?) bugtrack
2005-09-29 10:15 bugtrack
2005-12-31 2:18 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=1355c8d9daab0f287766f3f786db4a29@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