mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Michael F. Robbins" <compumike@compumike.com>
To: Tachino Nobuhiro <tachino@open.nm.fujitsu.co.jp>
Cc: linux-kernel@vger.kernel.org,
	"Michael F. Robbins" <compumike@compumike.com>,
	Robert Love <rml@tech9.net>,
	Tachino Nobuhiro <tachino@open.nm.fujitsu.co.jp>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: SiS/Trident 4DWave sound driver oops
Date: 26 Oct 2001 19:43:02 -0400	[thread overview]
Message-ID: <1004139782.1176.10.camel@tbird.robbins> (raw)
In-Reply-To: <7ktjw58u.wl@nisaaru.dvs.cs.fujitsu.co.jp>
In-Reply-To: <1004016263.1384.15.camel@tbird.robbins>  <7ktjw58u.wl@nisaaru.dvs.cs.fujitsu.co.jp>

Quick summary: sound now works on the ALi 5451 chip, 
but has some non-fatal error messages.

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.)





  parent reply	other threads:[~2001-10-26 23:43 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-25 13:24 Michael F. Robbins
2001-10-26  1:37 ` Tachino Nobuhiro
2001-10-26  1:56   ` Tachino Nobuhiro
2001-10-26  2:36     ` Tachino Nobuhiro
2001-10-26  1:45 ` Robert Love
2001-10-26  2:02   ` Robert Love
2001-10-26  2:42     ` Robert Love
2001-10-26  3:13       ` David Weinehall
2001-10-26  3:28       ` Robert Love
2001-10-26  3:24     ` Stuart Young
2001-10-26 14:36       ` Alan Cox
2001-10-26 14:47         ` Trever L. Adams
2001-10-28 23:06       ` SiS/Trident 4DWave sound driver Stuart Young
2001-10-29  1:19       ` SiS/Trident 4DWave sound driver (Update) Stuart Young
2001-10-29  4:04       ` SiS drivers (more) Stuart Young
2001-10-26 23:43 ` Michael F. Robbins [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-10-25  1:07 SiS/Trident 4DWave sound driver oops Michael F. Robbins
2001-10-25  5:55 ` Stuart Young
2001-10-25  7:02 ` Stuart Young
2001-10-23  6:15 Stuart Young
2001-10-23 16:19 ` Alan Cox
2001-10-24 23:55 ` Stuart Young

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=1004139782.1176.10.camel@tbird.robbins \
    --to=compumike@compumike.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rml@tech9.net \
    --cc=tachino@open.nm.fujitsu.co.jp \
    /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

all inboxes | Powered by JetHome®