From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000660]: No sound output despite unmuting and maximizing all volume settings
Date: Mon, 7 Mar 2005 02:22:19 +0100 [thread overview]
Message-ID: <c4021d1c751bc8f3f63d27bb9ce1c179@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=660>
======================================================================
Reported By: bji
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 660
Category: PCI - intel8x0
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution: Fedora Core 3
Kernel Version: 2.6.9
======================================================================
Date Submitted: 11-21-2004 02:53 CET
Last Modified: 03-07-2005 02:22 CET
======================================================================
Summary: No sound output despite unmuting and maximizing all
volume settings
Description:
I get no sound output from any program I have tried (xmms, play, aplay, cat
> /dev/audio) with no error messages or any other indication that there is
a problem which would cause sound to not occur.
I have already run alsamixer many times and tried every combination of
muted and unmuted settings with all volumes maximized. With no volume
settings muted, and all volume settings at maximum level, I still get no
sound.
Everything *looks* like it's working - output in the kernel log, xmms's
display, everything. But I get no sound out of the built-in speaker or
the headphone jack.
I have tried the following:
* Default install of Fedora Core 3; it recognized the sound card and
installed module settings in /etc/modprobe.conf to load snd-intel8x0. But
I never got any sound out of this default install no matter what I tried.
* Custom compiled the 2.6.9 kernel with no patches except the software
suspend 2 patch. This built the version of the ALSA drivers that come
with 2.6.9. Still no sound.
* Downloaded and compiled version 1.0.7 of the ALSA drivers and installed
them. Still no sound.
======================================================================
----------------------------------------------------------------------
bji - 12-09-04 07:06
----------------------------------------------------------------------
Thank you for the suggestion, unfortunately muting "external amplifier" via
alsamixer does not fix the problem.
I apologize but I still don't know how to run the record test that you
(tiwai) are suggesting. I don't know what program to run to do the audio
recording. Can you please suggest a program. Thank you!
----------------------------------------------------------------------
bji - 03-07-05 02:22
----------------------------------------------------------------------
OK, here's another data point.
I recently got a Panasonic Y2 in addition to the Panasonic T2 that I was
using when reporting this bug. As far as I know, the hardware related to
sound in these two laptops is essentially the same.
I discovered that I could get sound to work with the Panasonic Y2 if I did
the following:
* Booted to Windows XP
* Turned the Windows XP volume control to its highest setting
* Muted sound in Windows XP (which is how I usually keep sound in Windows
XP)
Now if I boot Linux with ALSA 1.0.6 (the stock alsa with Fedora Core 3), I
can adjust the sound volumes using alsamixer, and everything works. I can
play musing using xmms with either the ALSA or OSS plugins, and this also
works (although the volume slider in xmms does not work, not sure why, I
have to use alsamixer or aumix to adjust sound volume). Also, the
speakers work.
Thus I am convinced that the problem is that the ALSA driver for this
hardware is for some reason not able to adjust the volume beyond some
maximum value which was set by the BIOS, as remembered by the most recent
Windows XP setting.
Does this help at all?
Thanks!
Issue History
Date Modified Username Field Change
======================================================================
11-21-04 02:53 bji New Issue
11-21-04 02:53 bji Distribution => Fedora Core 3
11-21-04 02:53 bji Kernel Version => 2.6.9
11-21-04 02:55 bji Note Added: 0002481
11-21-04 02:56 bji File Added: proc_asound.txt
11-21-04 03:16 bji Note Added: 0002483
11-21-04 03:19 bji Note Added: 0002484
11-23-04 16:20 tiwai Note Added: 0002522
11-23-04 23:23 IceRAM Note Added: 0002537
11-23-04 23:24 IceRAM File Added: asound.state
11-23-04 23:25 IceRAM File Added: modprobe.conf
11-23-04 23:26 IceRAM File Added: iceram_lsmod.txt
11-23-04 23:27 IceRAM Note Added: 0002538
11-23-04 23:28 IceRAM Note Edited: 0002537
11-23-04 23:29 IceRAM Note Edited: 0002537
11-23-04 23:29 IceRAM Issue Monitored: IceRAM
11-23-04 23:45 IceRAM Note Added: 0002539
11-23-04 23:45 IceRAM File Added: .asoundrc
11-23-04 23:46 IceRAM Note Edited: 0002538
11-24-04 12:32 bji File Added: asound.state
11-24-04 12:33 bji Note Added: 0002550
11-24-04 12:40 tiwai Note Added: 0002552
11-24-04 13:15 IceRAM Note Deleted: 0002537
11-24-04 13:16 IceRAM Note Deleted: 0002539
11-24-04 13:19 IceRAM Note Deleted: 0002538
11-24-04 13:26 IceRAM Note Added: 0002561
11-24-04 14:57 tiwai Note Added: 0002565
11-25-04 07:07 bji Note Added: 0002587
11-28-04 04:24 bji Note Added: 0002619
11-28-04 06:04 bji Note Added: 0002620
11-29-04 17:19 tiwai Note Added: 0002654
11-29-04 17:19 tiwai File Added: stac9752a.diff
11-30-04 08:56 bji Note Added: 0002661
11-30-04 21:02 tiwai Note Added: 0002662
12-02-04 06:37 bji Note Added: 0002674
12-02-04 19:20 tiwai Note Added: 0002689
12-06-04 19:47 jnm11 Note Added: 0002730
12-06-04 19:47 jnm11 Issue Monitored: jnm11
12-09-04 07:06 bji Note Added: 0002797
03-07-05 02:22 bji Note Added: 0003806
======================================================================
-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next reply other threads:[~2005-03-07 1:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 1:22 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-22 2:08 [ALSA - driver 0000660]: No sound output despite unmuting and maximizing all volume settings bugtrack
2005-09-19 8:12 bugtrack
2004-12-09 6:06 bugtrack
2004-12-06 18:47 bugtrack
2004-12-02 18:20 bugtrack
2004-12-02 5:37 bugtrack
2004-11-30 20:02 bugtrack
2004-11-30 7:56 bugtrack
2004-11-29 16:19 bugtrack
2004-11-28 5:04 bugtrack
2004-11-28 3:24 bugtrack
2004-11-25 6:07 bugtrack
2004-11-24 13:57 bugtrack
2004-11-24 12:26 bugtrack
2004-11-24 11:40 bugtrack
2004-11-24 11:33 bugtrack
2004-11-23 22:45 bugtrack
2004-11-23 22:27 bugtrack
2004-11-23 22:23 bugtrack
2004-11-23 15:20 bugtrack
2004-11-21 2:19 bugtrack
2004-11-21 2:16 bugtrack
2004-11-21 1:55 bugtrack
2004-11-21 1:53 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=c4021d1c751bc8f3f63d27bb9ce1c179@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