From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0001618]: No Sound on Acer with Intel ICH6 HDA and Realtek ALC260
Date: Mon, 16 Jan 2006 00:32:12 +0100 [thread overview]
Message-ID: <bcc4bde3e46fcaa3e426ce02e1928011@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1618>
======================================================================
Reported By: robertw
Assigned To: tiwai
======================================================================
Project: ALSA - driver
Issue ID: 1618
Category: PCI - hda-intel
Reproducibility: always
Severity: feature
Priority: normal
Status: assigned
Distribution: Ubuntu 5.10
Kernel Version: 2.6.12-10-686
======================================================================
Date Submitted: 12-04-2005 21:24 CET
Last Modified: 01-16-2006 00:32 CET
======================================================================
Summary: No Sound on Acer with Intel ICH6 HDA and Realtek
ALC260
Description:
I can load the snd-hda-intel module and play a file via aplay or xmms or
play a cd without any error, but I cannot hear anything neither via the
build-in speakers nor via headphones. All volume controllers are at 70%
and unmuted, except for PCM, because there is no mute/unmute-button.
======================================================================
Relationships ID Summary
----------------------------------------------------------------------
duplicate of 0001517 No sound on hda-intel on Acer TravelMat...
======================================================================
----------------------------------------------------------------------
eudoxos - 01-13-06 08:03
----------------------------------------------------------------------
ALSA-Configuration.txt mentions 'test' parameter to the snd-hda-intel
module (if debug-compiled) which whould enable almost all controls to be
set --- would this make it possible to test the real arrangement of
different i/o?
jwoithe: If it is not the case, could you post a bit more elaborate HOWTO
on how to experiment with pin assignment you mentioned in your first post
to this bug? I would consider it interesting for many of those having the
problem and some model descriptions (patches) could be obtained from users
themselves (like me) rather than waiting for the devs to fix it.
BTW #1517 is a dupe of this bug (although has not been marked as such
yet).
----------------------------------------------------------------------
jwoithe - 01-16-06 00:32
----------------------------------------------------------------------
In response to eudoxos' request, here's a *really brief* outline of how I
went about deducing the connection layout on the S7020. Note that there
may well be a better, more streamlined way of going about this. However,
this worked for me and was quick.
Firstly you really must get hold of the ALC260 datasheet from Realtek.
This is available for download on the realtek website. The datasheet
details the internal arrangement of the ALC260, the IDs of the various
widgets, and what command verbs each widget accepts. Of particular
interest are the widget IDs of the the I/O widgets which connect to
physical input/output pins on the chip. It is these which are in turn
connected to jacks, internal speakers etc.
It is also quite helpful to understand the basic details about the HDA
system structure and how it all fits together. This can be acquireed by
reading the source code or the HDA docs from Intel (downloadable from
their website).
Armed with the widget IDs of interest, I hacked the patch-realtek.c
module. In particular I concentrated on the mixer and initialisation verb
structures. Since I did my tests the structure of patch-realtek has
changed slightly, but for the purposes of this exercise changing
alc260_base_output_mixer and alc260_init_verbs in the most recent versions
of alsa-driver (1.0.11rc1 and later) should be fine.
To discover the output routings, add mixer controls for all the output
widgets of the ALC260 chip to the mixer definition -
alc260_base_output_mixer in this case. Then add initialisation verbs for
each of these widgets to the alc260_init_verbs list, making each of them
an output. Recompile and insert the new hda-* modules.
Use aplay (or anything really) to send output to the chip. Then play with
the controls in alsamixer until you discover which control sends output to
what.
The technique for input jacks is pretty much the same, but this time
you're configuring widgets for input and using a capture program instead
of a player. It's most convenient to use one which has input level meters
of some kind so you can monitor what the chip ADC is seeing as you change
the capture source in alsamixer.
At the end of all this you should end up with a list of widgets and which
jacks/devices each is connected to. This can then be used to construct a
new ALC260 model in patch-realtek.c in a similar way as for the existing
HP and Fujitsu models.
If you require more details, please contact me via the alsa-devel mailing
list and we'll pick this up off-list.
Issue History
Date Modified Username Field Change
======================================================================
12-04-05 21:24 robertw New Issue
12-04-05 21:24 robertw Distribution => Ubuntu 5.10
12-04-05 21:24 robertw Kernel Version => 2.6.12-10-686
12-05-05 07:12 jwoithe Note Added: 0006908
12-05-05 19:35 timmy Note Added: 0006914
12-06-05 15:52 tiwai Note Added: 0006925
12-06-05 18:10 robertw Note Added: 0006930
12-06-05 20:07 tiwai Note Added: 0006934
12-06-05 20:08 tiwai File Added: alc-cvs-fix.diff
12-06-05 20:09 tiwai Note Added: 0006935
12-06-05 22:51 robertw Note Added: 0006938
12-07-05 14:59 tiwai Note Added: 0006941
12-07-05 15:00 tiwai File Added: alc-cvs-fix2.diff
12-07-05 23:10 robertw Note Added: 0006952
12-08-05 17:19 tiwai Note Added: 0006957
12-08-05 22:01 robertw File Added: codec#0
12-08-05 22:02 robertw File Added: codec#1
12-08-05 22:03 robertw File Added: asound.state
12-08-05 22:05 robertw Note Added: 0006963
12-09-05 15:09 tiwai Note Added: 0006966
12-09-05 16:35 robertw Note Added: 0006967
12-09-05 17:03 tiwai Note Added: 0006969
12-09-05 17:17 robertw Note Added: 0006970
12-14-05 13:22 mytux Issue Monitored: mytux
12-19-05 02:11 rlrevell Note Added: 0007077
01-02-06 21:55 robertw Note Added: 0007391
01-04-06 17:29 tiwai Note Added: 0007441
01-04-06 22:00 robertw Note Added: 0007453
01-04-06 22:16 robertw Note Edited: 0007453
01-11-06 23:38 lobstaj Note Added: 0007572
01-11-06 23:48 rlrevell Note Added: 0007573
01-12-06 00:20 lobstaj Note Added: 0007575
01-12-06 00:26 rlrevell Note Added: 0007576
01-12-06 01:16 mytux Note Added: 0007577
01-12-06 01:20 mytux Note Edited: 0007577
01-12-06 14:13 robertw Note Added: 0007586
01-12-06 14:43 lobstaj Note Added: 0007587
01-12-06 16:45 eudoxos Issue Monitored: eudoxos
01-12-06 21:04 rlrevell Note Added: 0007591
01-13-06 01:11 rlrevell Relationship added duplicate of 0001517
01-13-06 08:03 eudoxos Note Added: 0007631
01-13-06 11:30 er-ku Issue Monitored: er-ku
01-16-06 00:32 jwoithe Note Added: 0007682
======================================================================
-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new AJAX search engine that makes
searching your log files as easy as surfing the web. DOWNLOAD SPLUNK!
http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click
next reply other threads:[~2006-01-15 23:32 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-15 23:32 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-02-28 23:45 [ALSA - driver 0001618]: No Sound on Acer with Intel ICH6 HDA and Realtek ALC260 bugtrack
2006-02-28 23:38 bugtrack
2006-02-28 23:34 bugtrack
2006-02-28 20:27 bugtrack
2006-02-28 20:21 bugtrack
2006-02-28 0:31 bugtrack
2006-02-27 21:26 bugtrack
2006-02-27 20:20 bugtrack
2006-02-26 23:27 bugtrack
2006-02-26 23:16 bugtrack
2006-02-26 22:53 bugtrack
2006-02-26 22:48 bugtrack
2006-02-26 14:00 bugtrack
2006-02-26 13:58 bugtrack
2006-02-26 5:03 bugtrack
2006-02-26 4:50 bugtrack
2006-02-25 11:31 bugtrack
2006-02-24 22:23 bugtrack
2006-02-24 21:32 bugtrack
2006-02-24 14:41 bugtrack
2006-02-24 13:58 bugtrack
2006-02-24 11:21 bugtrack
2006-02-23 0:12 bugtrack
2006-02-22 17:29 bugtrack
2006-02-19 15:49 bugtrack
2006-02-19 9:41 bugtrack
2006-02-18 22:48 bugtrack
2006-02-13 23:07 bugtrack
2006-02-13 5:42 bugtrack
2006-02-12 23:45 bugtrack
2006-02-12 22:05 bugtrack
2006-02-12 21:14 bugtrack
2006-02-12 21:11 bugtrack
2006-02-12 20:42 bugtrack
2006-02-10 10:02 bugtrack
2006-02-08 23:29 bugtrack
2006-02-08 13:46 bugtrack
2006-01-13 7:03 bugtrack
2006-01-13 0:11 bugtrack
2006-01-12 20:04 bugtrack
2006-01-12 13:43 bugtrack
2006-01-12 13:13 bugtrack
2006-01-12 0:16 bugtrack
2006-01-11 23:26 bugtrack
2006-01-11 23:20 bugtrack
2006-01-11 22:48 bugtrack
2006-01-11 22:38 bugtrack
2006-01-04 21:00 bugtrack
2006-01-04 16:29 bugtrack
2006-01-02 20:55 bugtrack
2005-12-19 1:11 bugtrack
2005-12-09 16:17 bugtrack
2005-12-09 16:03 bugtrack
2005-12-09 15:35 bugtrack
2005-12-09 14:09 bugtrack
2005-12-08 21:05 bugtrack
2005-12-08 16:19 bugtrack
2005-12-07 22:10 bugtrack
2005-12-07 13:59 bugtrack
2005-12-06 21:51 bugtrack
2005-12-06 19:09 bugtrack
2005-12-06 19:07 bugtrack
2005-12-06 17:10 bugtrack
2005-12-06 14:52 bugtrack
2005-12-05 18:35 bugtrack
2005-12-05 6:12 bugtrack
2005-12-04 20:24 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=bcc4bde3e46fcaa3e426ce02e1928011@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