From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0002132]: No sound from speakers
Date: Fri, 2 Jun 2006 20:35:25 +0200 [thread overview]
Message-ID: <dbf84a6fc92e1f24ccf80bb44fc26285@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2132>
======================================================================
Reported By: bzbarsky
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 2132
Category: PCI - ens1371
Reproducibility: always
Severity: block
Priority: normal
Status: new
Distribution: Fedora Core 4
Kernel Version: 2.6.15
======================================================================
Date Submitted: 05-17-2006 19:54 CEST
Last Modified: 06-02-2006 20:35 CEST
======================================================================
Summary: No sound from speakers
Description:
Alsa seems to detect the sound card, but when I try to actually play
something there is no sound from the speakers.
======================================================================
----------------------------------------------------------------------
bzbarsky - 06-02-06 20:08
----------------------------------------------------------------------
I tried 1.0.11 and it didn't help. I'll upload the log files in case
they're useful.
----------------------------------------------------------------------
bzbarsky - 06-02-06 20:35
----------------------------------------------------------------------
I did verify that the module I compiled has the patch at
http://hg-mirror.alsa-project.org/alsa-kernel?cmd=changeset;node=47c1677e748c;style=gitweb
I've verified that I have a Tyan Trinity 400 with onboard audio (S1854A)
motherboard. All I can find in my motherboard manual is "AC97 codec rev
2.1". The board manual is at ftp://ftp.tyan.com/manuals/m_s1854_202.pdf
I don't see an obvious 48-pin square chip next to the es1373 chip...
I did try both speaker-test and aplay. Both produce no sound. :(
Issue History
Date Modified Username Field Change
======================================================================
05-17-06 19:54 bzbarsky New Issue
05-17-06 19:54 bzbarsky File Added: lspci.txt
05-17-06 19:54 bzbarsky Distribution => Fedora Core 4
05-17-06 19:54 bzbarsky Kernel Version => 2.6.15
05-17-06 19:55 bzbarsky File Added: lspci-n.txt
05-17-06 19:55 bzbarsky Issue Monitored: bzbarsky
05-17-06 19:56 bzbarsky File Added: scsound.log
05-17-06 19:57 bzbarsky Note Added: 0009857
05-20-06 05:31 Raymond Note Added: 0009882
05-20-06 21:43 bzbarsky Note Added: 0009893
05-21-06 03:41 Raymond Note Added: 0009894
05-21-06 03:48 Raymond Note Edited: 0009894
05-22-06 02:47 bzbarsky File Added: ac97#0-0
05-22-06 02:48 bzbarsky File Added: ac97#0-0+regs
05-22-06 02:53 bzbarsky Note Added: 0009901
05-22-06 04:14 Raymond Note Added: 0009902
05-23-06 09:00 Raymond Note Added: 0009929
05-23-06 09:03 Raymond Note Edited: 0009929
05-23-06 09:07 Raymond Note Edited: 0009929
06-02-06 20:08 bzbarsky Note Added: 0010053
06-02-06 20:09 bzbarsky File Added: scsound-1.0.11.log
06-02-06 20:09 bzbarsky File Added: ac97#0-0-1.0.11
06-02-06 20:10 bzbarsky File Added: ac97#0-0+regs-1.0.11
06-02-06 20:35 bzbarsky Note Added: 0010054
======================================================================
next reply other threads:[~2006-06-02 18:35 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-02 18:35 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-25 12:57 [ALSA - driver 0002132]: No sound from speakers bugtrack
2006-06-24 2:35 bugtrack
2006-06-24 0:36 bugtrack
2006-06-23 15:10 bugtrack
2006-06-23 14:11 bugtrack
2006-06-23 2:50 bugtrack
2006-06-23 2:00 bugtrack
2006-06-23 1:48 bugtrack
2006-06-23 1:28 bugtrack
2006-06-23 1:04 bugtrack
2006-06-23 1:01 bugtrack
2006-06-23 0:36 bugtrack
2006-06-23 0:28 bugtrack
2006-06-23 0:14 bugtrack
2006-06-23 0:02 bugtrack
2006-06-22 23:54 bugtrack
2006-06-22 1:18 bugtrack
2006-06-21 3:48 bugtrack
2006-06-21 3:05 bugtrack
2006-06-21 2:51 bugtrack
2006-06-21 1:54 bugtrack
2006-06-21 1:51 bugtrack
2006-06-20 6:45 bugtrack
2006-06-20 4:57 bugtrack
2006-06-20 4:35 bugtrack
2006-06-20 4:24 bugtrack
2006-06-20 4:20 bugtrack
2006-06-20 3:02 bugtrack
2006-06-16 2:31 bugtrack
2006-06-16 1:53 bugtrack
2006-06-15 15:07 bugtrack
2006-06-15 6:59 bugtrack
2006-06-15 6:06 bugtrack
2006-06-15 3:54 bugtrack
2006-06-15 2:19 bugtrack
2006-06-15 1:55 bugtrack
2006-06-15 1:53 bugtrack
2006-06-15 1:19 bugtrack
2006-06-15 0:59 bugtrack
2006-06-15 0:53 bugtrack
2006-06-15 0:36 bugtrack
2006-06-15 0:16 bugtrack
2006-06-14 3:00 bugtrack
2006-06-13 5:20 bugtrack
2006-06-13 3:39 bugtrack
2006-06-13 2:43 bugtrack
2006-06-12 16:12 bugtrack
2006-06-12 11:23 bugtrack
2006-06-12 3:26 bugtrack
2006-06-12 3:18 bugtrack
2006-06-12 2:36 bugtrack
2006-06-12 1:41 bugtrack
2006-06-12 1:31 bugtrack
2006-06-11 20:38 bugtrack
2006-06-11 3:24 bugtrack
2006-06-10 5:42 bugtrack
2006-06-06 4:35 bugtrack
2006-06-05 1:57 bugtrack
2006-06-05 1:31 bugtrack
2006-06-04 23:30 bugtrack
2006-06-03 0:44 bugtrack
2006-06-02 18:08 bugtrack
2006-05-23 7:00 bugtrack
2006-05-22 2:14 bugtrack
2006-05-22 0:53 bugtrack
2006-05-21 1:41 bugtrack
2006-05-20 19:43 bugtrack
2006-05-20 3:31 bugtrack
2006-05-17 17:57 bugtrack
2006-05-17 17:54 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=dbf84a6fc92e1f24ccf80bb44fc26285@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.