From: "Lee Revell" <rlrevell@joe-job.com>
To: Marek Zelem <marek@terminus.sk>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: No sound card found for ATI SB600 Azalia
Date: Mon, 23 Jul 2007 22:42:07 -0400 [thread overview]
Message-ID: <75b66ecd0707231942k15fa92c3mc67211764375bee8@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0707232239190.25733@shell.terminus.sk>
On 7/23/07, Marek Zelem <marek@terminus.sk> wrote:
> ACPI: PCI Interrupt 0000:00:14.2[A] -> GSI 16 (level, low) -> IRQ 16
> ALSA
> /usr/src/modules/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:558:
> hda_intel: azx_get_response timeout, switching to polling mode...
> ALSA
> /usr/src/modules/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:564:
> hda_intel: azx_get_response timeout, switching to single_cmd mode...
> hda_codec: No auto-config is available, default to model=ref
> ALSA
> /usr/src/modules/alsa-driver/pci/hda/../../alsa-kernel/pci/hda/hda_intel.c:1020:
> hda-intel: no codecs initialized
Takashi-san,
Maybe you should add another printk() to HDA intel driver that
instructs the user to post relevant debug info
(/proc/asound/card0/codecblah...) to alsa-devel in these cases where
we encounter some problem that is likely to result in no sound? Other
subsystems do it in similar cases (essentially, too many hardware
variants for the maintainers to have any chance of testing them all)
and it seems to produce good results. It would make a lot of users
happy to not have to google for what to do next...
Lee
next prev parent reply other threads:[~2007-07-24 2:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-23 21:00 No sound card found for ATI SB600 Azalia Marek Zelem
2007-07-24 2:42 ` Lee Revell [this message]
2007-07-24 10:01 ` Takashi Iwai
2007-07-24 19:53 ` Marek Zelem
2007-07-31 13:09 ` Takashi Iwai
2007-07-31 18:09 ` Marek Zelem
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=75b66ecd0707231942k15fa92c3mc67211764375bee8@mail.gmail.com \
--to=rlrevell@joe-job.com \
--cc=alsa-devel@alsa-project.org \
--cc=marek@terminus.sk \
--cc=tiwai@suse.de \
/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;
as well as URLs for NNTP newsgroup(s).