AC97 codec odd behaviour (STAC9708/11) / Aureal Card IS SUPPORTED!

AC97 codec odd behaviour (STAC9708/11) / Aureal Card IS SUPPORTED!

[Manuel Jander]

Hi everyone,

I'm facing some odd things with a Aureal MX300 with a
AC97 codec. For some reason the AC97 interface doesnt
set the EAPD (external amp enable) bit correctly, and i have 
to set it explicitly after calling the ac97  mixer initializer.

Maybe, that the AC97 codec write function actually implemented
for the Aureal cards "misses" some writes, but i just want to be sure
if this bit works for other cards with a STAC9708/11 or similar
codec that need this bit by default, or if i really need to set it
myself ??

I would like to ask once again please to update the ALSA Soundcard
matrix that there is a ALSA driver for all the Aureal cards.
The driver very soon to be posted here can be found at:
http://savannah.nongnu.org/projects/openvortex
If you don't want to be anoyed with this again, please update that
compatibility matrix ;)

Thank you very much

Manuel Jander




-------------------------------------------------------
This SF.NET email is sponsored by: eBay
Great deals on office technology -- on eBay now! Click here:
http://adfarm.mediaplex.com/ad/ck/711-11697-6916-5

./snddevices

[Patrick Shirkey]

I have a report that the manually running snddevices script is needed to 
get 0.9.4 working.

Last time I asked I got the impression that it was being automatically 
handled and even saw the output messages after running make install.

However I and others using the quattro have a bizarre problem where we 
cannot access the alsa layer as a normal user.

This is the message I get before/after running ./snddevices manually:
-----
snd_pcm_open: Permission denied (quattro1)
Failed to initialize plugin!
Failed to register plugin: /usr/local/lib/alsaplayer/output/libalsa_out.so
Failed to load output plugin "alsa". Trying defaults.
snd_pcm_open: Permission denied (quattro1)
Failed to initialize plugin!
-----

Can someone let me know what is wrong or has support for the old dev 
system been dropped now?


-- 
Patrick Shirkey - Boost Hardware Ltd.
Http://www.boosthardware.com
Http://www.djcj.org - The Linux Audio Users guide
========================================

Being on stage with the band in front of crowds shouting, "Get off! No! 
We want normal music!", I think that was more like acting than anything 
I've ever done.

Goldie, 8 Nov, 2002
The Scotsman



-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php

Re: ./snddevices

[Takashi Iwai]

At Wed, 18 Jun 2003 14:20:37 +0900,
Patrick Shirkey wrote:
> 
> However I and others using the quattro have a bizarre problem where we 
> cannot access the alsa layer as a normal user.
> 
> This is the message I get before/after running ./snddevices manually:
> -----
> snd_pcm_open: Permission denied (quattro1)
> Failed to initialize plugin!
> Failed to register plugin: /usr/local/lib/alsaplayer/output/libalsa_out.so
> Failed to load output plugin "alsa". Trying defaults.
> snd_pcm_open: Permission denied (quattro1)
> Failed to initialize plugin!
> -----

please check the permission of device files under /dev/snd directory.
the snddevices script creates the devices with the owner root.audio
(if such a group exists - if not, root.root is used).
this might be different on your system.

i hope this problem won't happen in future once after the major
distributions create such device files as default, and takes the
permission controls via pam.


> Can someone let me know what is wrong or has support for the old dev 
> system been dropped now?

because it is an ugly style and devfs can do the same thing even
better...


Takashi


-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php

Re: AC97 codec odd behaviour (STAC9708/11) / Aureal Card IS SUPPORTED!

[Takashi Iwai]

At 12 Jun 2003 17:51:50 -0400,
Manuel Jander wrote:
> 
> Hi everyone,
> 
> I'm facing some odd things with a Aureal MX300 with a
> AC97 codec. For some reason the AC97 interface doesnt
> set the EAPD (external amp enable) bit correctly, and i have 
> to set it explicitly after calling the ac97  mixer initializer.
> 
> Maybe, that the AC97 codec write function actually implemented
> for the Aureal cards "misses" some writes, but i just want to be sure
> if this bit works for other cards with a STAC9708/11 or similar
> codec that need this bit by default, or if i really need to set it
> myself ??

i recommend you to do this in the card driver level.

the use of EAPD is dependent upon the devices.  also, some uses EAPD
pin for different purposes...


> I would like to ask once again please to update the ALSA Soundcard
> matrix that there is a ALSA driver for all the Aureal cards.
> The driver very soon to be posted here can be found at:
> http://savannah.nongnu.org/projects/openvortex
> If you don't want to be anoyed with this again, please update that
> compatibility matrix ;)

Patrick, could you take care of this?


thanks,

Takashi


-------------------------------------------------------
This SF.Net email is sponsored by: INetU
Attention Web Developers & Consultants: Become An INetU Hosting Partner.
Refer Dedicated Servers. We Manage Them. You Get 10% Monthly Commission!
INetU Dedicated Managed Hosting http://www.inetu.net/partner/index.php

Re: AC97 codec odd behaviour (STAC9708/11) / Aureal Card IS SUPPORTED!

[Raymond]

Takashi Iwai wrote:
> At 12 Jun 2003 17:51:50 -0400,
> Manuel Jander wrote:
> 
>>Hi everyone,
>>
>>I'm facing some odd things with a Aureal MX300 with a
>>AC97 codec. For some reason the AC97 interface doesnt
>>set the EAPD (external amp enable) bit correctly, and i have 
>>to set it explicitly after calling the ac97  mixer initializer.
>>
>>Maybe, that the AC97 codec write function actually implemented
>>for the Aureal cards "misses" some writes, but i just want to be sure
>>if this bit works for other cards with a STAC9708/11 or similar
>>codec that need this bit by default, or if i really need to set it
>>myself ??
> 
> 
> i recommend you to do this in the card driver level.
> 
> the use of EAPD is dependent upon the devices.  also, some uses EAPD
> pin for different purposes...
> 
> 
> 
According to datasheet of STAC9708, the general purpose register (0x20)
has 3D, MIX, MS, LPBK bits.

Is "POP" a undocumented feature of STAC9708 ?

Simple mixer control 'PCM Out Path & Mute',0
   Capabilities: enum
   Items: 'pre 3D' 'post 3D'
   Item0: 'post 3D'

0-0/0: SigmaTel STAC9708,11

Capabilities     : -headphone out-
DAC resolution   : 18-bit
ADC resolution   : 18-bit
3D enhancement   : SigmaTel 3D Enhancement

Current setup
Mic gain         : +0dB [+0dB]
POP path         : post 3D        <-------------------------
Sim. stereo      : off
3D enhancement   : off
Loudness         : off
Mono output      : MIX
Mic select       : Mic1
ADC/DAC loopback : off
Extended ID      : codec=0 rev=0 SDAC DSA=0
Extended status  : SDAC

numid=43,iface=MIXER,name='PCM Out Path & Mute'
   ; type=ENUMERATED,access=rw---,values=1,items=2
   ; Item #0 'pre 3D'
   ; Item #1 'post 3D'
   : values=0


STAC9708 on other sound cards such as Soundblaster 4.1

http://thread.gmane.org/gmane.linux.alsa.devel/4818




-------------------------------------------------------
SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
from IBM. Find simple to follow Roadmaps, straightforward articles,
informative Webcasts and more! Get everything you need to get up to
speed, fast. http://ads.osdn.com/?ad_id=7477&alloc_id=16492&op=click