From: Alex Romosan <romosan@sycorax.lbl.gov>
To: David Parker <david@neongoat.com>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Trident problems.
Date: Sat, 30 Aug 2003 10:47:37 -0700 [thread overview]
Message-ID: <873cfj82bq.fsf@sycorax.lbl.gov> (raw)
In-Reply-To: <20030828005741.162b0565.david@neongoat.com> (message from David Parker on Thu, 28 Aug 2003 00:57:41 -0700)
David Parker <david@neongoat.com> writes:
> A long time ago (many months... sorry I don't know exactly when), my
> Trident card stopped working with ALSA on a Debian unstable box. It
> still works with the kernel OSS module, but ALSA has problems with
> the AC'97 codec. Here's what I tried and the resulting log
> messages/output:
>
> hypnotic:/home/dap# modprobe snd-trident
> ALSA ../../alsa-kernel/pci/trident/trident_main.c:3394: AC'97 codec ready error
> Trident 4DWave PCI soundcard not found or device busy
> devfs_register(unknown): could not append to parent, err: -17
> ALSA ../../alsa-kernel/pci/ac97/ac97_codec.c:2096: AC'97 0:0 does not respond - RESET
> Trident 4DWave PCI soundcard not found or device busy
>
i have exactly the same problem. the weird thing is when it happened
(many months ago) i tried to go back to the previous working version
and it still didn't work. my theory is that the ac'97 codec got into a
funky state and it's not being reset. unfortunately i don't know what
to do either.
--alex--
--
| I believe the moment is at hand when, by a paranoiac and active |
| advance of the mind, it will be possible (simultaneously with |
| automatism and other passive states) to systematize confusion |
| and thus to help to discredit completely the world of reality. |
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2003-08-30 17:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-28 7:57 Trident problems David Parker
2003-08-30 17:47 ` Alex Romosan [this message]
2003-09-09 20:35 ` David Parker
2003-09-09 20:51 ` Alex Romosan
2003-09-09 21:32 ` David Parker
2003-09-09 21:47 ` Alex Romosan
2003-09-10 1:57 ` CS46xx, TB Santa Cruz, 4+ channel output? Joe
2003-09-10 12:34 ` Trident problems Takashi Iwai
2003-09-16 23:08 ` David Parker
2003-09-17 8:50 ` Takashi Iwai
-- strict thread matches above, loose matches on Subject: below --
2003-05-12 21:58 trident problems Alex Romosan
2003-02-13 21:00 Trident problems Peter Enderborg
2003-02-14 9:32 ` Takashi Iwai
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=873cfj82bq.fsf@sycorax.lbl.gov \
--to=romosan@sycorax.lbl.gov \
--cc=alsa-devel@lists.sourceforge.net \
--cc=david@neongoat.com \
/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