On Thu, 2001-10-25 at 21:37, Tachino Nobuhiro wrote:
> diff -u -r linux-2.4.12-ac5.org/drivers/sound/ac97_codec.c linux-2.4.12-ac5/drivers/sound/ac97_codec.c
> --- linux-2.4.12-ac5.org/drivers/sound/ac97_codec.c Mon Oct 22 09:34:21 2001
> +++ linux-2.4.12-ac5/drivers/sound/ac97_codec.c Fri Oct 26 10:26:41 2001
> @@ -143,7 +143,6 @@
> {0x83847656, "SigmaTel STAC9756/57", &sigmatel_9744_ops},
> {0x83847684, "SigmaTel STAC9783/84?", &null_ops},
> {0x57454301, "Winbond 83971D", &null_ops},
> - {0,}
> };
>
> static const char *ac97_stereo_enhancements[] =
I just removed that final data set and the preceeding comma and
recompiled 2.4.12-ac6. I'm pleased to report that the sound now works
just fine! The module loads, and I do get some (non-fatal) error
messages, but once its loaded it runs like a champ.
BTW, I was also getting these error messages on my old 2.4.7 install.
This is my 2.4.12-ac6 log after `modprobe trident`. Take a look:
----------
Trident 4DWave/SiS 7018/ALi 5451,Tvia CyberPro 5050 PCI Audio, version
0.14.9d, 19:15:41 Oct 26 2001
PCI: Assigned IRQ 10 for device 00:03.0
trident: ALi Audio Accelerator found at IO 0xc400, IRQ 10
ac97_codec: AC97 Audio codec, id: 0x414c:0x4326 (Unknown)
ali: AC97 CODEC read timed out.
ali: AC97 CODEC write timed out.
ali: AC97 CODEC read timed out.
last message repeated 2 times
ac97_codec: AC97 codec, id: 0x0000:0x0000 (Unknown)
ali: AC97 CODEC write timed out.
ali: AC97 CODEC read timed out.
ali: AC97 CODEC write timed out.
last message repeated 10 times
ali: AC97 CODEC read timed out.
last message repeated 127 times
----------
This hangs the system totally for about 5 seconds. After this, it's all
fine and the sound works great. One strange thing I notice from the
above log is the different codec IDs showing up...
Thanks,
Mike Robbins
compumike@compumike.com
(Please also cc your reply to me.)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/