mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Peter <peter@cogweb.net>
To: Alan Cox <alan@redhat.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.4.19 -- ac97_codec failure ALi 5451
Date: Thu,  9 Jan 2003 20:30:25 -0800	[thread overview]
Message-ID: <1042173025.3e1e4c61af615@webmail.cogweb.net> (raw)
In-Reply-To: <200301100250.h0A2olE20795@devserv.devel.redhat.com>

Quoting Alan Cox <alan@redhat.com>:

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

  reply	other threads:[~2003-01-10  4:21 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-04  5:50 2.4.19-ac4 build problem Peter
2002-09-04 16:21 ` Greg KH
2002-09-05  3:59 ` Peter
2002-09-05  6:58   ` Greg KH
2002-09-12  2:41   ` 2.4.19-ac4 Out of Memory cogwepeter
2003-01-10  2:35     ` 2.4.19 -- ac97_codec failure ALi 5451 Peter
2003-01-10  2:50       ` Alan Cox
2003-01-10  4:30         ` Peter [this message]
2003-01-10 13:15         ` Peter
2003-01-10 13:36           ` Alan Cox
2003-01-21  0:41             ` 2.4.20 USB storage (SCSI emulation) Peter Nome
2003-01-21  1:18               ` Matthew Dharm
2003-01-21  2:01                 ` Peter Nome
2002-09-05  8:00 ` 2.4.19-ac4 build problem Peter
2002-09-05 16:26   ` Greg KH
2003-01-13  4:40 2.4.19 -- ac97_codec failure ALi 5451 peter

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=1042173025.3e1e4c61af615@webmail.cogweb.net \
    --to=peter@cogweb.net \
    --cc=alan@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome