From: Peter <peter@cogweb.net>
To: <200301100250.h0A2olE20795@devserv.devel.redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19 -- ac97_codec failure ALi 5451 [rescued]
Date: Fri, 10 Jan 2003 19:37:03 +0100 [thread overview]
Message-ID: <200301101837.h0AIb3V05186@mail.intergenia.de> (raw)
> > Trident 4DWave/SiS 7018/ALi 5451,Tvia CyberPro 5050 PCI Audio,
> > version 0.14.9d, 00:57:19 Jan 9 2003
> > PCI: Enabling device 00:06.0 (0000 -> 0003)
> > PCI: Assigned IRQ 10 for device 00:06.0
> > trident: ALi Audio Accelerator found at IO 0x1000, IRQ 10
> > ac97_codec: AC97 Audio codec, id: 0x4144:0x5372 (Unknown)
>
> So far so good.
>
> > ali: AC97 CODEC read timed out.
> > last message repeated 127 times
> > ali: AC97 CODEC write timed out.
> > ac97_codec: AC97 codec, id: 0x0000:0x0000 (Unknown)
>
> Something lost the codec. Could be power management - was the laptop
> suspended before it went funny ?
No, this happens very reliably every time on a large number of occasions, whether
trident is compiled in or as a module, or with ALSA's snd-ali5451. Dozens of read
and write timeouts. In fact when the codec loads, it tends to freeze the whole
system for a short time (from a few seconds to a minute).
That said, it's close to working. There have been times when I've been able to get
sound -- typically by doing a manual insmod ac97_codec and trident. I had hoped the
ALSA module would work more reliably, but it seems the problem is with the ac97
codec.
Is the driver for the ac97 codec the same for OSS and ALSA? They appear to fail in
very similar ways.
Peter
-
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/
reply other threads:[~2003-01-10 18:51 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=200301101837.h0AIb3V05186@mail.intergenia.de \
--to=peter@cogweb.net \
--cc=200301100250.h0A2olE20795@devserv.devel.redhat.com \
--cc=linux-kernel@vger.kernel.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.