From: Manuel Naranjo <manuel@aircable.net>
To: alsa-devel@alsa-project.org
Subject: Via vt8237 sometimes fails to load
Date: Mon, 13 Apr 2009 10:43:25 -0300 [thread overview]
Message-ID: <49E3417D.30709@aircable.net> (raw)
Hello guys,
I have a KT880 based mobo made by MSI, I haven't used this computer for
a while (a year or so) I remember that before the audio was working,
even though sometimes it was initializated with noise and required me
restarting alsa. Now it doesn't even load, and I get some weird errors
in dmesg.
I've checked the wiki and the bug tracker but still couldn't find a
solution.
This is lspci -vv -nn
00:11.5 Multimedia audio controller [0401]: VIA Technologies, Inc.
VT8233/A/8235/8237 AC97 Audio Controller [1106:3059] (rev 60)
Subsystem: Micro-Star International Co., Ltd. Device [1462:0470]
Control: I/O+ Mem- BusMaster- SpecCycle- MemWINV- VGASnoop-
ParErr- Stepping- SERR- FastB2B- DisINTx-
Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort-
<TAbort- <MAbort- >SERR- <PERR- INTx-
Interrupt: pin C routed to IRQ 22
Region 0: I/O ports at a800 [size=256]
Capabilities: <access denied>
Kernel modules: snd-via82xx
And dmesg
ALSA /tmp/alsa/alsa-driver-1.0.19/pci/via82xx.c:581: codec_read: codec 0
is not valid [0x1fc0000]
ALSA /tmp/alsa/alsa-driver-1.0.19/pci/via82xx.c:581: codec_read: codec 0
is not valid [0x1fe0000]
ALSA /tmp/alsa/alsa-driver-1.0.19/pci/via82xx.c:523: codec_ready: codec
0 is not ready [0x1000000]
ALSA /tmp/alsa/alsa-driver-1.0.19/pci/via82xx.c:523: codec_ready: codec
0 is not ready [0x1000000]
ALSA /tmp/alsa/alsa-driver-1.0.19/pci/via82xx.c:581: codec_read: codec 0
is not valid [0x1fc0000]
ALSA /tmp/alsa/alsa-driver-1.0.19/pci/via82xx.c:581: codec_read: codec 0
is not valid [0x1fe0000]
ALSA /tmp/alsa/alsa-driver-1.0.19/pci/ac97/ac97_codec.c:2077: AC'97 0
access is not valid [0xffffffff], removing mixer.
VIA 82xx Audio 0000:00:11.5: PCI INT C disabled
VIA 82xx Audio: probe of 0000:00:11.5 failed with error -5
Thanks,
Manuel
reply other threads:[~2009-04-13 13:43 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=49E3417D.30709@aircable.net \
--to=manuel@aircable.net \
--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