From: "Miroslav Šulc" <fordfrog@gmail.com>
To: alsa-devel@alsa-project.org
Subject: Re: acer aspire 8943g with alc670
Date: Thu, 29 Jul 2010 18:35:23 +0200 [thread overview]
Message-ID: <4C51ADCB.4010607@gmail.com> (raw)
In-Reply-To: <AANLkTindqKL769hKUk9z18RkABL4SwEubWzn_D0DuAb5@mail.gmail.com>
Dne 29.7.2010 15:20, Raymond Yau napsal(a):
> 2010/7/29 Miroslav Šulc <fordfrog@gmail.com>
>> hello,
>>
>> i'd like to help with making the above soundcard to fully work, but have
>> no clue what to do exactly. currently the soundcard works pretty weird,
>> though at least sound goes out :-)
>>
>> i tried hda analyzer but did not find any documentation for it so have
>> no idea what to do exactly. also, when clicking AUD_IN nodes, i get this
>> error:
>>
>> ** (hda_analyzer.py:10063): WARNING **: column number is a boolean, but
>> will be interpreted as an integer; this is likely not what you intended
>> Traceback (most recent call last):
>> File "/dev/shm/hda-analyzer/hda_analyzer.py", line 308, in
>> selection_changed_cb
>> self.__refresh()
>> File "/dev/shm/hda-analyzer/hda_analyzer.py", line 276, in __refresh
>> self.load()
>> File "/dev/shm/hda-analyzer/hda_analyzer.py", line 336, in load
>> self.node_window.add(NodeGui(node=n))
>> File "/dev/shm/hda-analyzer/hda_guilib.py", line 86, in __init__
>> self.__build_node(node, doframe)
>> File "/dev/shm/hda-analyzer/hda_guilib.py", line 682, in __build_node
>> vbox.pack_start(self.__build_amps(node), False, False)
>> File "/dev/shm/hda-analyzer/hda_guilib.py", line 365, in __build_amps
>> node.in_amp and node.amp_vals_in or None)
>> File "/dev/shm/hda-analyzer/hda_guilib.py", line 328, in build_caps
>> if ctl.hdactl.amp_index_match(idx):
>> File "/dev/shm/hda-analyzer/hda_proc.py", line 170, in amp_index_match
>> count = (self.amp_chs & 1) + ((self.amp_chs >> 1) & 1)
>> TypeError: unsupported operand type(s) for &: 'NoneType' and 'int'
>>
>>
>> can anybody pls direct me to some documentation that could help me to
>> master hda analyzer and find the way to make the card work correctly?
>>
>> miroslav
> By using alc670 alsa-info.txt in the alsa bugtracker
here is the bug and alsa-info.txt:
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=5083
> the latest version
> hda_analyzer don't has any error message when clicking AUD_IN node
>
> Not sure your error is due to using /proc instead of text file since I
> don't have your codec
>
> There are error messages when click the "graph" button to generate the
> graph.
>
> About the graph
> the blue line - connected audio path
> the grey line - unconncted audio path
> the line turn red when you put the mouse cursor near any line ,
>
>
> TypeError: 'int' object is not iterable
> Traceback (most recent call last):
> File "/hda-analyzer/hda_graph.py", line 579, in expose
> route.expose(cr, event)
> File "/hda-analyzer/hda_graph.py", line 190, in expose
> inactive = self.src.node.is_conn_active(self.dst.node)
> File "/hda-analyzer/hda_codec.py", line 809, in is_conn_active
> vals = dst_node.amp_vals_in.get_val_db(idx)
> File "/hda-analyzer/hda_codec.py", line 377, in get_val_db
> for val in vals:
> TypeError: 'int' object is not iterable
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2010-07-29 16:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-29 2:09 acer aspire 8943g with alc670 Miroslav Šulc
2010-07-29 13:20 ` Raymond Yau
2010-07-29 13:40 ` Miroslav Šulc
2010-07-29 13:54 ` Raymond Yau
2010-07-29 14:28 ` Miroslav Šulc
2010-07-29 15:10 ` Jaroslav Kysela
2010-07-29 16:24 ` Miroslav Šulc
2010-07-29 16:35 ` Miroslav Šulc [this message]
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=4C51ADCB.4010607@gmail.com \
--to=fordfrog@gmail.com \
--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.