From: tony mancill <tony@mancill.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: alsa-devel <alsa-devel@alsa-project.org>
Subject: Re: HDA Intel sound driver fails on Acer notebook
Date: Thu, 07 Dec 2006 13:52:42 -0800 [thread overview]
Message-ID: <45788D2A.6070405@mancill.com> (raw)
In-Reply-To: <200612030233_MC3-1-D3BB-DE9@compuserve.com>
FWIW, I'm having problems with this same laptop as well (i386). Same
number of interrupts in /proc/interrupts. Interestingly, OSS output works
(mostly), but all of the ALSA commands fail:
tony@maus:~$ amixer -d scontrols
amixer: Mixer default load error: Invalid argument
tony@maus:~$ aplay ./test.wav
ALSA lib confmisc.c:1105:(snd_func_refer) Unable to find definition
'defaults.pcm.dmix_format'
ALSA lib conf.c:3500:(_snd_config_evaluate) function snd_func_refer
returned error: No such file or directory
ALSA lib conf.c:3957:(snd_config_expand) Args evaluate error: No such file
or directory
ALSA lib pcm.c:2143:(snd_pcm_open_noupdate) Unknown PCM dmix:0
aplay: main:550: audio open error: No such file or directory
However, this is running 1.0.13. I have yet to test with the 1.0.14rc1
pre-packages that were posted earlier today.
Chuck Ebbert wrote:
> The HDA Intel sound driver still fails to load on my Acer Aspire 5102
> notebook (Turion64 X2, ATI chipset):
>
> Here is the PCI info while running x86_64. I tried i386 and x86_64 and it fails
> on both:
>
> 00:14.2 Audio device: ATI Technologies Inc Unknown device 437b (rev 01)
> Subsystem: Acer Incorporated [ALI] Unknown device 009f
> Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- Stepping- SERR- FastB2B-
> Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=slow >TAbort- <TAbort- <MAbort- >SERR- <PERR-
> Latency: 64, Cache Line Size 08
> Interrupt: pin ? routed to IRQ 16
> Region 0: Memory at c0000000 (64-bit, non-prefetchable) [size=16K]
> Capabilities: [50] Power Management version 2
> Flags: PMEClk- DSI- D1- D2- AuxCurrent=55mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
> Status: D0 PME-Enable- DSel=0 DScale=0 PME-
> Capabilities: [60] Message Signalled Interrupts: 64bit+ Queue=0/0 Enable-
> Address: 0000000000000000 Data: 0000
> 00: 02 10 7b 43 06 00 10 04 01 00 03 04 08 40 00 00
> 10: 04 00 00 c0 00 00 00 00 00 00 00 00 00 00 00 00
> 20: 00 00 00 00 00 00 00 00 00 00 00 00 25 10 9f 00
> 30: 00 00 00 00 50 00 00 00 00 00 00 00 0a 00 00 00
> 40: 00 00 02 40 00 00 00 00 00 00 00 00 00 00 00 00
> 50: 01 60 42 c8 00 00 00 00 00 00 00 00 00 00 00 00
> 60: 05 00 80 00 00 00 00 00 00 00 00 00 00 00 00 00
> 70: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 80: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> 90: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> a0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> b0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> c0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> d0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> e0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
> f0: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
>
> On i386 I get this after doing
> insmod snd-hda-codec.ko ; insmod snd-hda-intel.ko
>
> Dec 1 17:38:29 ac kernel: ACPI: PCI Interrupt 0000:00:14.2[A] -> GSI 16 (level, low) -> IRQ 18
> Dec 1 17:38:29 ac kernel: codec_mask = 0xb
> Dec 1 17:38:30 ac kernel: hda_codec: PCI 1025:9f, codec config 5 is selected
> Dec 1 17:38:31 ac kernel: hda_intel: azx_get_response timeout, switching to polling mode...
> Dec 1 17:38:32 ac kernel: hda_intel: azx_get_response timeout, switching to single_cmd mode...
> Dec 1 17:38:32 ac kernel: hda-intel: get_response timeout: IRS=0x0
> Dec 1 17:38:36 ac last message repeated 24618 times
> Dec 1 17:38:36 ac kernel: hda_codec: invalid dep_range_val 0:7fff
> Dec 1 17:38:36 ac kernel: hda_codec: invalid dep_range_val 0:7fff
> Dec 1 17:38:36 ac kernel: hda-intel: get_response timeout: IRS=0x0
> Dec 1 17:38:36 ac kernel: hda_codec: invalid dep_range_val 0:7fff
> Dec 1 17:38:36 ac kernel: hda_codec: invalid dep_range_val 0:7fff
> Dec 1 17:38:36 ac kernel: hda-intel: get_response timeout: IRS=0x0
>
> The last three lines repeat many thousands of times, followed by:
>
> Dec 1 17:38:39 ac kernel: hda_generic: no proper input path found
> Dec 1 17:38:39 ac kernel: hda_generic: no proper output path found
> Dec 1 17:38:39 ac kernel: hda_generic: no PCM found
>
> Looking at /proc/interrupts, I see exactly 110 interrupts were processed
> by the driver while all this was happening:
>
> 18: 0 110 IO-APIC-fasteoi HDA Intel
>
> On x86_64 I forgot to enable verbose messages, so there's less information
> but it fails the same way.
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
next prev parent reply other threads:[~2006-12-07 21:53 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-03 7:30 HDA Intel sound driver fails on Acer notebook Chuck Ebbert
2006-12-07 21:52 ` tony mancill [this message]
2007-02-19 16:51 ` HDA Intel sound driver fails on Acer notebook - UPDATE, PROGRESS! tony mancill
2006-12-19 9:53 ` HDA Intel sound driver fails on Acer notebook Takashi Iwai
2006-12-20 1:48 ` tony mancill
2006-12-20 2:47 ` D. Hazelton
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=45788D2A.6070405@mancill.com \
--to=tony@mancill.com \
--cc=76306.1226@compuserve.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox