From: bugtrack@alsa-project.org
To: alsa-devel@alsa-project.org
Subject: [ALSA - driver 0002217]: Problems with ASUS A6Km
Date: Tue, 20 Jun 2006 20:16:27 +0200 [thread overview]
Message-ID: <93d87c8815a2c1927554264fc4b1bc4e@bugtrack.alsa-project.org> (raw)
A NOTE has been added to this issue.
======================================================================
<https://bugtrack.alsa-project.org/alsa-bug/view.php?id=2217>
======================================================================
Reported By: mafm
Assigned To:
======================================================================
Project: ALSA - driver
Issue ID: 2217
Category: PCI - intel8x0
Reproducibility: always
Severity: major
Priority: normal
Status: new
Distribution:
Kernel Version:
======================================================================
Date Submitted: 06-18-2006 05:06 CEST
Last Modified: 06-20-2006 20:16 CEST
======================================================================
Summary: Problems with ASUS A6Km
Description:
I have the same problems described here:
https://bugtrack.alsa-project.org/alsa-bug/view.php?id=1898 , but I'm
opening a new report because I can't find a way to add a comment there.
I tried that asus-a6km-fix.diff but it doesn't work, in fact it doesn't
appear to have any effect at all.
======================================================================
----------------------------------------------------------------------
tiwai - 06-20-06 19:46
----------------------------------------------------------------------
You should check the PCI SSID whether it really matches with the one added
in the patch.
----------------------------------------------------------------------
mafm - 06-20-06 20:16
----------------------------------------------------------------------
Do you mean subsystem_vendor and subsystem_device? Despite the hexadecimal
0x before the numbers in the patch, it looks like the same -- I assume
that lspci uses hexadecimals too but doesn't print the 0x in front of the
numbers.
My model is A6KM Q0012H, with amd64 and DDR instead of DDRII of the Intel
models; and currently I use "acpi=ht" because it has some problems with
the BIOS (it won't boot with the USB attached otherwise). Doing 'echo "7a
57c1" > /proc/asound/card0/codec97#0/ac97#0-0+regs' doesn't work saying
that the device doesn't exists, but I can't think of any other difference
with the other bug reports talking about the same problem: symptoms are
the same, the models of the hardware seem to be the same too, etc.
The patch:
------------------------------------------------------------------------------
diff -r 10a2ea6ebebc pci/ac97/ac97_patch.c
--- a/pci/ac97/ac97_patch.c Thu Apr 20 12:37:00 2006 +0200
+++ b/pci/ac97/ac97_patch.c Thu Apr 20 14:55:55 2006 +0200
@@ -2048,7 +2048,10 @@ int patch_alc650(struct snd_ac97 * ac97)
/* Enable SPDIF-IN only on Rev.E and above */
val = snd_ac97_read(ac97, AC97_ALC650_CLOCK);
/* SPDIF IN with pin 47 */
- if (ac97->spec.dev_flags)
+ if (ac97->spec.dev_flags &&
+ /* ASUS A6KM requires EAPD */
+ ! (ac97->subsystem_vendor == 0x1043 &&
+ ac97->subsystem_device == 0x1103))
val |= 0x03; /* enable */
else
val &= ~0x03; /* disable */
------------------------------------------------------------------------------
lspci -v
------------------------------------------------------------------------------
00:02.7 Multimedia audio controller: Silicon Integrated Systems [SiS]
AC'97 Sound Controller (rev a0)
Subsystem: ASUSTeK Computer Inc. Unknown device 1103
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at e400 [size=256]
I/O ports at e000 [size=128]
Capabilities: [48] Power Management version 2
------------------------------------------------------------------------------
lspci -v -n
------------------------------------------------------------------------------
00:02.7 0401: 1039:7012 (rev a0)
Subsystem: 1043:1103
Flags: bus master, medium devsel, latency 64, IRQ 11
I/O ports at e400 [size=256]
I/O ports at e000 [size=128]
Capabilities: [48] Power Management version 2
------------------------------------------------------------------------------
Issue History
Date Modified Username Field Change
======================================================================
06-18-06 05:06 mafm New Issue
06-18-06 16:51 ryswic Issue Monitored: ryswic
06-19-06 15:49 mafm Issue Monitored: mafm
06-19-06 15:50 mafm Note Added: 0010315
06-20-06 19:46 tiwai Note Added: 0010345
06-20-06 20:16 mafm Note Added: 0010354
======================================================================
next reply other threads:[~2006-06-20 18:16 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 18:16 bugtrack [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-06-26 14:11 [ALSA - driver 0002217]: Problems with ASUS A6Km bugtrack
2006-06-25 9:32 bugtrack
2006-06-24 12:32 bugtrack
2006-06-24 8:26 bugtrack
2006-06-24 7:12 bugtrack
2006-06-23 14:23 bugtrack
2006-06-23 13:27 bugtrack
2006-06-21 22:10 bugtrack
2006-06-21 20:48 bugtrack
2006-06-21 20:33 bugtrack
2006-06-21 20:24 bugtrack
2006-06-21 19:37 bugtrack
2006-06-20 17:46 bugtrack
2006-06-19 13:50 bugtrack
2006-06-18 3:06 bugtrack
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=93d87c8815a2c1927554264fc4b1bc4e@bugtrack.alsa-project.org \
--to=bugtrack@alsa-project.org \
--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.