reopen 709106
thanks
Hi Elimar,
On 2013-05-26 04:16, Elimar Riesebieter wrote:
* Filipus Klutiero<[email protected]> [2013-05-25 22:40 -0400]:
On 2013-05-25 05:36, Elimar Riesebieter wrote:
[...]
So if you solved your configuration problem I can't figure out a bug
anywere?
As things are currently, *I* have no problem. The bug is that I
had to use a workaround to get speaker-test and others to work. It
isn't a "configuration problem", it happens in the *default*
configuration. In other words, if I was to reinstall today, I
would go back to a broken install with the cryptic errors
mentioned.
Of course, getting rid of the problem in the default configuration
would already be a good improvement. But speaker-test should never
fail in this way, regardless of what device is configured as the
default.
OK, configure a soundchicp which isn't supported by ALSA yet as the
default one is more or less an ALSA thing. What we can to is to
blacklist snd_hda_codec_hdmi but Iam sure there are soundchips
(soundcards) out there which are working well with that codec,
though. The Debian documantaion in
/usr/share/doc/alsa-base/README.Debian helps users to configure
their soundcrads. So I close this bug herewith.
A bug report should only be closed when the bug has been resolved. If you don't
know how to fix a bug, simply leave the report open. If you believe a bug
cannot be fixed, the report can be tagged wontfix (which is very rarely
appropriate).
In this case, there are apparently 2 ways to make progress:
1. If, as your reply implies, the chip is not supported, support can be
introduced.
2. In my case, where the problematic chip is not the only one and another chip
works fine, another chip can be made the default.
--
Filipus Klutiero
http://www.philippecloutier.com
