Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0000674]: sound modules loaded, unmuted channels, progressbar moving STILL no output
Date: Wed, 8 Dec 2004 12:00:11 +0100	[thread overview]
Message-ID: <ec017522dd43dd0fbd10e97dd8137f25@bugtrack.alsa-project.org> (raw)


A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=674> 
======================================================================
Reported By:                IceRAM
Assigned To:                
======================================================================
Project:                    ALSA - driver
Issue ID:                   674
Category:                   PCI - intel8x0
Reproducibility:            always
Severity:                   major
Priority:                   normal
Status:                     new
Distribution:               ArchLinux
Kernel Version:             2.6.9
======================================================================
Date Submitted:             11-24-2004 13:12 CET
Last Modified:              12-08-2004 12:00 CET
======================================================================
Summary:                    sound modules loaded, unmuted channels, progressbar
moving STILL no output
Description: 
I can't get any sound out of the integrated sound card, even though I've
tried everything possible (I think - oh, I haven't tried Windows, yet)
======================================================================

----------------------------------------------------------------------
 IceRAM - 11-28-04 23:10 
----------------------------------------------------------------------
pzad (11-24-04 16:07) guided me to:
http://sourceforge.net/mailarchive/message.php?msg_id=10061173

 > Greetings -
 > 
 > I have an ABIT AN7 motherboard with an nForce2 audio controller.  The
AC97
 > chip is an ALC658, and the patch from ac97_patch.c from 1.30 to 1.31
in
 > CVS seems to have broken standard stereo output.  I can get some sound
 > output from my speakers if I enable Line-In As Surround and Duplicate
 > Front, but it is very faint.  Without these features enabled, I don"t
get
 > any audio output from any of the analog output jacks.
 > 
 > I"ve looked at the code, for patch_alc655() as compared to
patch_alc650()
 > but I"m not proficient enough to figure out what to change to make it
 > work, so I"ve simply modified ac97_codec.c to use patch_alc650() for
my
 > ALC658.  There seem to be other people on the alsa-users list with a
 > similar problem, and I"d be happy to help try and diagnose the problem
 > further, but I"m not sure what other information will be helpful.
 > 

I have installed today Windows. To my surprise, the Line Out jack doesn't
work, no matter what output I would choose in Windows (2ch,4ch,6ch).
Surprisingly, the Line in works (in 4ch), but I can only hear sound in the
right speaker & the sound in the left speaker is very faint.

I took is as a hardware problem of the MB and left it as is (I left the
speakers in the Line in jack).

Sometime later I booted into Linux. Playing through the filesystem, I
don't know what made me choose Play from the context menu over a file.
Surprisingly, amarok started and I got sound in the right speaker.
Amaizing improvement.

I've continued my reasearch in the configs and discovered, after my recent
playing in them, that "Duplicate front" and "Line in as surround" were
checked. Unchecking turned off the sound. It was kind of obvious that I
would get sound through the Line in jack with these 2 selected.

I must also add that the Line In (Line is as surround) is badly balanced
(as in Windows) - I suspect this to be a hardware problem, I'll research.

edited on: 11-28-04 23:10

----------------------------------------------------------------------
 IceRAM - 12-08-04 12:00 
----------------------------------------------------------------------
It turned out to be a hardware problem (Front panel was incorrectly wired
to the motherboard).

This bug can be closed. Sorry for all the fuss, but I couldn't have
thought about an incorrect wiring (this has been done by a 'pro').

Issue History
Date Modified  Username       Field                    Change              
======================================================================
11-24-04 13:12 IceRAM         New Issue                                    
11-24-04 13:12 IceRAM         File Added: asound.state                     
11-24-04 13:12 IceRAM         Distribution              => ArchLinux       
11-24-04 13:12 IceRAM         Kernel Version            => 2.6.9           
11-24-04 13:13 IceRAM         File Added: .asoundrc                        
11-24-04 13:17 IceRAM         File Added: modprobe.conf                    
11-24-04 13:19 IceRAM         Note Added: 0002560                          
11-24-04 13:19 IceRAM         File Added: lsmod.txt                        
11-24-04 13:20 IceRAM         Issue Monitored: IceRAM                      
11-24-04 15:36 IceRAM         File Added: lspci_v.txt                      
11-24-04 15:39 IceRAM         Note Added: 0002568                          
11-24-04 16:07 pzad           Note Added: 0002569                          
11-24-04 16:31 IceRAM         Note Added: 0002570                          
11-24-04 18:02 tiwai          Note Added: 0002576                          
11-24-04 18:37 IceRAM         File Added: ac97#0-0                         
11-24-04 18:37 IceRAM         File Added: ac97#0-0+regs                    
11-24-04 18:39 IceRAM         Note Added: 0002578                          
11-24-04 18:43 IceRAM         Note Added: 0002579                          
11-28-04 21:11 IceRAM         Note Added: 0002629                          
11-28-04 23:10 IceRAM         Note Edited: 0002629                         
12-08-04 12:00 IceRAM         Note Added: 0002775                          
======================================================================




-------------------------------------------------------
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-12-08 11:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-08 11:00 bugtrack [this message]
  -- strict thread matches above, loose matches on Subject: below --
2005-01-11 15:52 [ALSA - driver 0000674]: sound modules loaded, unmuted channels, progressbar moving STILL no output bugtrack
2004-12-08 11:50 bugtrack
2004-11-28 20:11 bugtrack
2004-11-24 17:43 bugtrack
2004-11-24 17:39 bugtrack
2004-11-24 17:02 bugtrack
2004-11-24 15:31 bugtrack
2004-11-24 15:07 bugtrack
2004-11-24 14:39 bugtrack
2004-11-24 12:19 bugtrack
2004-11-24 12:12 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=ec017522dd43dd0fbd10e97dd8137f25@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