Re: Trident problems.

Re: Trident problems.

[David Parker]

Hi,

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

hypnotic:/home/dap# modprobe trident
Trident 4DWave/SiS 7018/ALi 5451,Tvia CyberPro 5050 PCI Audio, version 0.14.10h, 18:35:01 Jul 19 2003
trident: Trident 4DWave DX found at IO 0x1400, IRQ 19
ac97_codec: AC97  codec, id: ""D68 (Unknown)

hypnotic:/home/dap# uname -a
Linux hypnotic 2.4.22-pre7 #1 SMP Sat Jul 19 18:29:55 PDT 2003 i686 GNU/Linux

hypnotic:/proc/asound# cat version 
Advanced Linux Sound Architecture Driver Version 0.9.4.
Compiled on Jul 19 2003 for kernel 2.4.22-pre7 (SMP) with versioned symbols.

hypnotic:/home/dap# lspci -n -v -s 00:0b.0
00:0b.0 Class 0401: 1023:2000 (rev 02)
        Subsystem: 1023:2000
        Flags: bus master, medium devsel, latency 64, IRQ 19
        I/O ports at 1400 [size=256]
        Memory at e8002000 (32-bit, non-prefetchable) [size=4K]
        Capabilities: [48] Power Management version 1

I saw someone else had this same problem on the alsa-devel list a while ago
(http://www.mail-archive.com/alsa-devel@lists.sourceforge.net/msg06500.html)
but it doesn't look like it was ever resolved. Is there something I need to
tweak, or is this a valid bug? If it would help to test specific old versions
of ALSA I could do that too.

Thanks,
David

-------
David Parker <david@neongoat.com>
Neon Goat Productions
http://www.neongoat.com
0xF90FFFE5 / F362 51F7 6D51 85EB AF68 75B9 D29B 1AFC F90F FFE5
-------



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: Trident problems.

[Alex Romosan]

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

Re: Trident problems.

[David Parker]

On Sat, 30 Aug 2003 10:47:37 -0700, Alex Romosan wrote:

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

Things have been quiet on this thread... does anyone have any ideas, or any
knowledge of whether or not the ac'97 codec can even get into such a weird
persistent state? Is it something that can be ignored, since somehow the 2.4
kernel OSS module still works? Any help or ideas for me to google on would be
great.

(more debugging details at
http://www.mail-archive.com/alsa-devel@lists.sourceforge.net/msg08889.html)

David

-------
David Parker <david@neongoat.com>
Neon Goat Productions
http://www.neongoat.com
0xF90FFFE5 / F362 51F7 6D51 85EB AF68 75B9 D29B 1AFC F90F FFE5
-------



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: Trident problems.

[Alex Romosan]

David Parker <david@neongoat.com> writes:

> Things have been quiet on this thread... does anyone have any ideas,
> or any knowledge of whether or not the ac'97 codec can even get into
> such a weird persistent state? Is it something that can be ignored,
> since somehow the 2.4 kernel OSS module still works? Any help or
> ideas for me to google on would be great.

well, i had the card working yesterday but it got noisier over time
and then today after i tried to remove the modules and then reinsert
them i couldn't do it anymore. i wasn;t able to get the oss modules
working (it's been many years since i used oss) so maybe the card is
at fault.

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

Re: Trident problems.

[David Parker]

On Tue, 09 Sep 2003 13:51:22 -0700, Alex Romosan wrote:

> well, i had the card working yesterday but it got noisier over time
> and then today after i tried to remove the modules and then reinsert
> them i couldn't do it anymore. i wasn;t able to get the oss modules
> working (it's been many years since i used oss) so maybe the card is
> at fault.

Strange, did you do anything special to get ALSA working with the trident
again or did it just happen to work on the first try?

David

-------
David Parker <david@neongoat.com>
Neon Goat Productions
http://www.neongoat.com
0xF90FFFE5 / F362 51F7 6D51 85EB AF68 75B9 D29B 1AFC F90F FFE5
-------



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: Trident problems.

[Alex Romosan]

David Parker <david@neongoat.com> writes:

> Strange, did you do anything special to get ALSA working with the trident
> again or did it just happen to work on the first try?

just the usual: did a cvs update, tried to insert the modules and by
some miracle it worked. same modules don't work today...

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

CS46xx, TB Santa Cruz, 4+ channel output?

[Joe]

Hi, I've posted on the Alsa-User list, and get absolutely no reply, so I
thought I'd try my luck here.

I've given the same spiel to several forums and lists, so rather than go
over it again, I'm going to post a link to a few of my forum topics, to
see if I can get any help with this.  The problem is I am trying to find
a way to mirror the output on one device (CS46xx) to one or two other
devices ("CS46xx - Rear", and "CS46xx - Center LFE"), and I'm getting no
where.  The alsa-project "Wiki" says that surround output has been
"verified working" with the latest version of alsa, so my question is,
what is required to get that sound mirrored?  Using "surround40" and
"surround51", I get an error, so I don't think that works, yet each
individual output device works, and I get sound on the correct speakers
when I change the output device.

http://forums.gentoo.org/viewtopic.php?p=512760#512760
http://forums.gentoo.org/viewtopic.php?t=76654

Can anyone tell me what I need to do in order to get simultaneous output
on all channels for this particular sound card?

Pertinent info:

$ cat /proc/asound/version
Advanced Linux Sound Architecture Driver Version 0.9.6.
Compiled on Aug 18 2003 for kernel 2.4.20-gentoo-r6 with versioned
symbols.

$ cat /proc/asound/pcm
00-00: CS46xx : CS46xx : playback 31 : capture 1
00-01: CS46xx - Rear : CS46xx - Rear : playback 31
00-02: CS46xx - IEC958 : CS46xx - IEC958 : playback 1
00-03: CS46xx - Center LFE : CS46xx - Center LFE : playback 31

Any other information you need, just ask.

Thanks a lot,
-- 
madCoder <madCoder@GamesNET.net>
GamesNET Support Operator
http://www.gamesnet.net/



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: Trident problems.

[Takashi Iwai]

[-- Attachment #1: Type: text/plain, Size: 2491 bytes --]

At Thu, 28 Aug 2003 00:57:41 -0700,
David Parker wrote:
> 
> Hi,
> 
> 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
> 
> hypnotic:/home/dap# modprobe trident
> Trident 4DWave/SiS 7018/ALi 5451,Tvia CyberPro 5050 PCI Audio, version 0.14.10h, 18:35:01 Jul 19 2003
> trident: Trident 4DWave DX found at IO 0x1400, IRQ 19
> ac97_codec: AC97  codec, id: ""D68 (Unknown)
> 
> hypnotic:/home/dap# uname -a
> Linux hypnotic 2.4.22-pre7 #1 SMP Sat Jul 19 18:29:55 PDT 2003 i686 GNU/Linux
> 
> hypnotic:/proc/asound# cat version 
> Advanced Linux Sound Architecture Driver Version 0.9.4.
> Compiled on Jul 19 2003 for kernel 2.4.22-pre7 (SMP) with versioned symbols.
> 
> hypnotic:/home/dap# lspci -n -v -s 00:0b.0
> 00:0b.0 Class 0401: 1023:2000 (rev 02)
>         Subsystem: 1023:2000
>         Flags: bus master, medium devsel, latency 64, IRQ 19
>         I/O ports at 1400 [size=256]
>         Memory at e8002000 (32-bit, non-prefetchable) [size=4K]
>         Capabilities: [48] Power Management version 1
> 
> I saw someone else had this same problem on the alsa-devel list a while ago
> (http://www.mail-archive.com/alsa-devel@lists.sourceforge.net/msg06500.html)
> but it doesn't look like it was ever resolved. Is there something I need to
> tweak, or is this a valid bug? If it would help to test specific old versions
> of ALSA I could do that too.

could you please try the attached patch?
if it still doesn't solve the problem, try to increase the length of
timeout in snd_trident_4d_dx_init(), e.g. 

	end_time = jiffies + HZ * 2;

it will wait for 2 seconds.
try this with and without the patch.

if the same problem happens, try to commend out the line
"return -EIO;" in the same function, so that the probing proceeds even
if the check fails.  let's see whether the further ac97 probing
works.

if still fails...  remove the warm reset part.


Takashi

[-- Attachment #2: trident-4d-fix.dif --]
[-- Type: application/octet-stream, Size: 1082 bytes --]

Index: alsa-kernel/pci/trident/trident_main.c
===================================================================
RCS file: /suse/tiwai/cvs/alsa/alsa-kernel/pci/trident/trident_main.c,v
retrieving revision 1.39
diff -u -r1.39 trident_main.c
--- alsa-kernel/pci/trident/trident_main.c	2 Sep 2003 18:04:54 -0000	1.39
+++ alsa-kernel/pci/trident/trident_main.c	10 Sep 2003 12:24:46 -0000
@@ -3387,9 +3387,6 @@
 	outl(0x00000001, TRID_REG(trident, DX_ACR2_AC97_COM_STAT));
 	udelay(100);
 	outl(0x00000000, TRID_REG(trident, DX_ACR2_AC97_COM_STAT));
-	/* DAC on, disable SB IRQ and try to force ADC valid signal */
-	trident->ac97_ctrl = 0x0000004a;
-	outl(trident->ac97_ctrl, TRID_REG(trident, DX_ACR2_AC97_COM_STAT));
 	/* wait, until the codec is ready */
 	end_time = (jiffies + (HZ * 3) / 4) + 1;
 	do {
@@ -3401,6 +3398,10 @@
 	return -EIO;
 
  __dx_ok:
+	/* DAC on, disable SB IRQ and try to force ADC valid signal */
+	trident->ac97_ctrl = 0x0000004a;
+	outl(trident->ac97_ctrl, TRID_REG(trident, DX_ACR2_AC97_COM_STAT));
+
 	snd_trident_stop_all_voices(trident);
 
 	return 0;

Re: Trident problems.

[David Parker]

Takashi Iwai <tiwai@suse.de> said:

> could you please try the attached patch?
> if it still doesn't solve the problem, try to increase the length of
> timeout in snd_trident_4d_dx_init(), e.g. 
> 
> 	end_time = jiffies + HZ * 2;
> 
> it will wait for 2 seconds.
> try this with and without the patch.
> 
> if the same problem happens, try to commend out the line
> "return -EIO;" in the same function, so that the probing proceeds even
> if the check fails.  let's see whether the further ac97 probing
> works.
> 
> if still fails...  remove the warm reset part.

Sorry for the slow reply... I tried the patch and it didn't work so I also
tried combining the above fixes with and without the patch. Still no luck :(
Would it be helpful to put debug messages on each line and pasting that, or
should I try something else?

Thanks,
David

-------
David Parker <david@neongoat.com>
Neon Goat Productions
http://www.neongoat.com
0xF90FFFE5 / F362 51F7 6D51 85EB AF68 75B9 D29B 1AFC F90F FFE5
-------







-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

Re: Trident problems.

[Takashi Iwai]

At Tue, 16 Sep 2003 23:08:16 -0000,
David Parker wrote:
> 
> Takashi Iwai <tiwai@suse.de> said:
> 
> > could you please try the attached patch?
> > if it still doesn't solve the problem, try to increase the length of
> > timeout in snd_trident_4d_dx_init(), e.g. 
> > 
> > 	end_time = jiffies + HZ * 2;
> > 
> > it will wait for 2 seconds.
> > try this with and without the patch.
> > 
> > if the same problem happens, try to commend out the line
> > "return -EIO;" in the same function, so that the probing proceeds even
> > if the check fails.  let's see whether the further ac97 probing
> > works.
> > 
> > if still fails...  remove the warm reset part.
> 
> Sorry for the slow reply... I tried the patch and it didn't work so I also
> tried combining the above fixes with and without the patch. Still no luck :(

didn't it work even if you ignore the error as mentioned above?
then it means that ac97 is really not ready for use.
i'm afraid something is broken.


Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

trident problems

[Alex Romosan]

i am running kernel 2.4.21-rc2 and i think since friday after i did a
cvs update i can't get the trident module to load anymore. this is the
output from syslog:

kernel: PCI: Found IRQ 10 for device 00:0b.0
kernel: PCI: Sharing IRQ 10 with 00:05.0
kernel: ALSA ../../alsa-kernel/pci/ac97/ac97_codec.c:2048: AC'97 0:0 does not respond - RESET
kernel: Trident 4DWave PCI soundcard not found or device busy
insmod: /lib/modules/2.4.21-rc2/kernel/sound/pci/trident/snd-trident.o: init_module: No such device
insmod: Hint: insmod errors can be caused by incorrect module parameters, including invalid IO or IRQ parameters.       You may find more information in syslog or the output from dmesg
insmod: /lib/modules/2.4.21-rc2/kernel/sound/pci/trident/snd-trident.o: insmod snd-card-0 failed

any ideas?

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


-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com

Trident problems.

[Peter Enderborg]

(cvs version 2003-02-13)
 /sbin/modprobe snd-trident
Note: /etc/modules.conf is more recent than
/lib/modules/2.4.19/modules.dep
/lib/modules/2.4.19/kernel/sound/pci/trident/snd-trident.o: init_module:
No such device
Hint: insmod errors can be caused by incorrect module parameters,
including invalid IO or IRQ parameters.
      You may find more information in syslog or the output from dmesg
/lib/modules/2.4.19/kernel/sound/pci/trident/snd-trident.o: insmod
/lib/modules/2.4.19/kernel/sound/pci/trident/snd-trident.o failed
/lib/modules/2.4.19/kernel/sound/pci/trident/snd-trident.o: insmod
snd-trident failed
[root@pescadero Documentation]#


And dmsg:

ALSA ../../alsa-kernel/pci/trident/trident_main.c:3382: AC'97 codec
ready error [0x0]
Trident 4DWave PCI soundcard not found or device busy

What can make it busy?

>From /proc/pci

 Bus  0, device  11, function  0:
    Multimedia audio controller: Trident Microsystems 4DWave NX (rev 2).

      IRQ 17.
      Master Capable.  Latency=32.  Min Gnt=2.Max Lat=5.
      I/O at 0x9400 [0x94ff].
      Non-prefetchable 32 bit memory at 0xd3000000 [0xd3000fff].

I have not had this card running for a year or so. The machine runs on a
dual PII with SMP kernel.
The other soundcard a SB-PCI128 works fine.





-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en

Re: Trident problems.

[Takashi Iwai]

At Thu, 13 Feb 2003 22:00:45 +0100,
Peter Enderborg wrote:
> 
> (cvs version 2003-02-13)
>  /sbin/modprobe snd-trident
> Note: /etc/modules.conf is more recent than
> /lib/modules/2.4.19/modules.dep
> /lib/modules/2.4.19/kernel/sound/pci/trident/snd-trident.o: init_module:
> No such device
> Hint: insmod errors can be caused by incorrect module parameters,
> including invalid IO or IRQ parameters.
>       You may find more information in syslog or the output from dmesg
> /lib/modules/2.4.19/kernel/sound/pci/trident/snd-trident.o: insmod
> /lib/modules/2.4.19/kernel/sound/pci/trident/snd-trident.o failed
> /lib/modules/2.4.19/kernel/sound/pci/trident/snd-trident.o: insmod
> snd-trident failed
> [root@pescadero Documentation]#
> 
> 
> And dmsg:
> 
> ALSA ../../alsa-kernel/pci/trident/trident_main.c:3382: AC'97 codec
> ready error [0x0]
> Trident 4DWave PCI soundcard not found or device busy
> 
> What can make it busy?

no idea yet.  it means the ac97 codec connection was not initialized
properly.  could you try the kernel oss trident driver and check
whether it works?


thanks,

Takashi


-------------------------------------------------------
This SF.NET email is sponsored by: FREE  SSL Guide from Thawte
are you planning your Web Server Security? Click here to get a FREE
Thawte SSL guide and find the answers to all your  SSL security issues.
http://ads.sourceforge.net/cgi-bin/redirect.pl?thaw0026en