All of lore.kernel.org
 help / color / mirror / Atom feed
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: Tue, 23 Nov 2004 16:20:10 +0100	[thread overview]
Message-ID: <71ec90341f32854f3b4f0bbb443d2281@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:              11-23-2004 16:20 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 - 11-21-04 03:19 
----------------------------------------------------------------------
Here are the modules that are installed after my system boots:

Module                  Size  Used by
snd_pcm_oss            55208  0 
snd_mixer_oss          19712  1 snd_pcm_oss
snd_intel8x0           36924  1 
snd_ac97_codec         76896  1 snd_intel8x0
snd_pcm               111240  3 snd_pcm_oss,snd_intel8x0,snd_ac97_codec
snd_timer              34948  1 snd_pcm
snd                    61156  8
snd_pcm_oss,snd_mixer_oss,snd_intel8x0,snd_ac97_codec,snd_pcm,snd_timer
soundcore              11360  1 snd
snd_page_alloc         10504  2 snd_intel8x0,snd_pcm
uhci_hcd               34960  0 
ehci_hcd               37380  0 
ipw2100               146372  0 
ieee80211              35908  1 ipw2100
i915                   86788  3 
md5                     4608  1 
ipv6                  272320  8 
ds                     19204  2 
ipt_REJECT              7296  1 
ipt_state               2176  1 
ip_conntrack           45876  1 ipt_state
iptable_filter          3200  1 
ip_tables              18048  3 ipt_REJECT,ipt_state,iptable_filter
dm_mod                 62740  0 
button                  6928  0 
battery                 9220  0 
ac                      5124  0 
yenta_socket           20864  0 
pcmcia_core            67396  2 ds,yenta_socket
arc4                    2176  1 
ieee80211_crypt_wep     5376  1 
ieee80211_crypt         7684  2 ieee80211,ieee80211_crypt_wep
8139too                30336  0 
mii                     5504  1 8139too
ext3                  121576  1 
jbd                    90392  1 ext3

----------------------------------------------------------------------
 tiwai - 11-23-04 16:20 
----------------------------------------------------------------------
It's likely a mixer issue.  Could you attach /etc/asound.state?

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                          
======================================================================




-------------------------------------------------------
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/

             reply	other threads:[~2004-11-23 15:20 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-11-23 15:20 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
2005-03-07  1:22 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-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=71ec90341f32854f3b4f0bbb443d2281@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.