dxs_support and via82xx (yet once more)

dxs_support and via82xx (yet once more)

[ico]

Hi all, 
 
Apologies for my persistence but is this feature 
broken in the 1.0.4.pre2 drivers or am I simply 
unable to put the right syntax into the 
modules.conf? 
 
alias char-major-116 snd 
alias char-major-14 soundcore 
alias snd-card-0 via82xx 
#I tried every possible option 
options via82xx dxs_support=1 
options snd-card-0 dxs_support=1 
options snd-via82xx dxs_support=1 
 
alias sound-slot-0 snd-card-0 
alias sound-service-0-0 snd-mixer-oss 
alias sound-service-0-1 snd-seq-oss 
alias sound-service-0-3 snd-pcm-oss 
alias sound-service-0-8 snd-seq-oss 
alias sound-service-0-12 snd-pcm-oss 
 
Even with all this the syslog still complains: 
via82xx: Assuming DXS channels with 48k fixed 
sample rate. 
         Please try dxs_support=1 or 
dxs_support=4 option 
         and report if it works on your machine. 
 
What am I doing wrong? 
 
Best wishes, 
 
Ico 
 



-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg\x12297

Re: dxs_support and via82xx (yet once more)

[Takashi Iwai]

At Fri, 23 Apr 2004 4:12:57 +0000,
<ico@fuse.net> wrote:
> 
> Hi all, 
>  
> Apologies for my persistence but is this feature 
> broken in the 1.0.4.pre2 drivers or am I simply 
> unable to put the right syntax into the 
> modules.conf? 
>  
> alias char-major-116 snd 
> alias char-major-14 soundcore 
> alias snd-card-0 via82xx 
                   ^^^^^^^
                   snd-via82xx
> #I tried every possible option 
> options via82xx dxs_support=1 

this line is useless.

> options snd-card-0 dxs_support=1 
> options snd-via82xx dxs_support=1 
>  
> alias sound-slot-0 snd-card-0 
> alias sound-service-0-0 snd-mixer-oss 
> alias sound-service-0-1 snd-seq-oss 
> alias sound-service-0-3 snd-pcm-oss 
> alias sound-service-0-8 snd-seq-oss 
> alias sound-service-0-12 snd-pcm-oss 
>  
> Even with all this the syslog still complains: 
> via82xx: Assuming DXS channels with 48k fixed 
> sample rate. 
>          Please try dxs_support=1 or 
> dxs_support=4 option 
>          and report if it works on your machine. 
>  
> What am I doing wrong? 

make sure that there is another defitions of snd-via82xx options in
/etc/modules.conf or its variants.


--
Takashi Iwai <tiwai@suse.de>		ALSA Developer - www.alsa-project.org


-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297

RE: dxs_support and via82xx (yet once more)

[Ivica Ico Bukvic]

> > alias char-major-116 snd
> > alias char-major-14 soundcore
> > alias snd-card-0 via82xx
>                    ^^^^^^^
>                    snd-via82xx

Hmmm, but somewhere along the road while troubleshooting this/installing
something told me (a script) that I should drop the snd- prefix. Are you
saying that I still need snd- prefix? The alsa init does succeed after all
even with only via82xx (modprobing) so that's why I am asking.

> > #I tried every possible option
> > options via82xx dxs_support=1
> 
> this line is useless.

Because it's missing snd- prefix? (I removed the hdsp stuff from the
modules.conf for the better legibility but using cards without snd- prefix
seemed to work just fine, so I am guessing that snd- is needed for the
options call only, or am I misunderstanding this?)

> 
> > options snd-card-0 dxs_support=1
> > options snd-via82xx dxs_support=1

Shouldn't this then work?

> >
> > alias sound-slot-0 snd-card-0
> > alias sound-service-0-0 snd-mixer-oss
> > alias sound-service-0-1 snd-seq-oss
> > alias sound-service-0-3 snd-pcm-oss
> > alias sound-service-0-8 snd-seq-oss
> > alias sound-service-0-12 snd-pcm-oss
> >
> > Even with all this the syslog still complains:
> > via82xx: Assuming DXS channels with 48k fixed
> > sample rate.
> >          Please try dxs_support=1 or
> > dxs_support=4 option
> >          and report if it works on your machine.
> >
> > What am I doing wrong?
> 
> make sure that there is another defitions of snd-via82xx options in
> /etc/modules.conf or its variants.

I am sorry, not sure that I understood you here. Do I need to create alias
between via82xx and snd-via82xx or simply rename the card to snd-via82xx? If
I need to rename it, how come that it works even without snd- prefix (except
for the dxs option)?

Thank you very much for your help!

Best wishes,

Ico





-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297

Re: dxs_support and via82xx (yet once more)

[Takashi Iwai]

At Fri, 23 Apr 2004 12:56:35 -0400,
Ivica Ico Bukvic wrote:
> 
> > > alias char-major-116 snd
> > > alias char-major-14 soundcore
> > > alias snd-card-0 via82xx
> >                    ^^^^^^^
> >                    snd-via82xx
> 
> Hmmm, but somewhere along the road while troubleshooting this/installing
> something told me (a script) that I should drop the snd- prefix. Are you
> saying that I still need snd- prefix? The alsa init does succeed after all
> even with only via82xx (modprobing) so that's why I am asking.

yes, the module name still consists of snd- prefix.
the snd_ prefix was dropped from the module OPTIONS.
(e.g. dxs_support would have been named as snd_dxs_support in the old
 versions.)

> > > #I tried every possible option
> > > options via82xx dxs_support=1
> > 
> > this line is useless.
> 
> Because it's missing snd- prefix? (I removed the hdsp stuff from the
> modules.conf for the better legibility but using cards without snd- prefix
> seemed to work just fine, so I am guessing that snd- is needed for the
> options call only, or am I misunderstanding this?)

snd- prefix is for the module NAMES, but not for module OPTIONS.
again, there is no via82xx module.  there is only snd-via82xx module.
defining the options for via82xx is useless because options for a
non-existing module will be never referred.


> > > options snd-card-0 dxs_support=1

this one is also useless.  remove it.
(snd-card-0 is just an alias, not the real module name.)


> > > options snd-via82xx dxs_support=1
> 
> Shouldn't this then work?

yes, in theory it should work.
that's why i asked you to make sure any other definitions exist.
there must be another error in the configuration.


BTW, i assume that are you using 2.4 kernel.  is it right?


Takashi


-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297

RE: [Alsa-devel] dxs_support and via82xx (yet once more) -- some new findings

[Ivica Ico Bukvic]

> yes, the module name still consists of snd- prefix.
> the snd_ prefix was dropped from the module OPTIONS.
> (e.g. dxs_support would have been named as snd_dxs_support in the old
>  versions.)

Oh, I see now. Thank you very much for explaining that.

Now, when I do put in an option into the modules.conf specifying a different
dxs mode, am I still supposed to get the same message in my syslog about
picking trying dxs=1 or 4 or does that message show up only when no options
have been successfully parsed?

I am asking this since even when I am 100% sure that my syntax is/was ok I
would still get the message no matter what option was specified in
modules.conf. I tried hacking via82xx.c file where I would hardwire my
vendor/card ID into the list of known cards and changing it that way and the
card worked the same no matter which options I chose, so I decided to leave
it at DXS_ENABLE (or 1 if I am not mistaken). This is the only way how I
would disable that message from appearing in syslog.

What kind of difference am I supposed to notice by changing dxs in order to
figure out the best option anyhow?

As it is right now I can play 4 simultaneous streams and they all sound ok
(no apparent glitches etc.). But this is the case no matter which option I
pick.

> BTW, i assume that are you using 2.4 kernel.  is it right?

No, I am working with 2.6.3 and 2.6.5 (both patched).

Finally, I've observed one extremely interesting phenomenon. I did notice
that when compiling preemptive versions of these kernels that I get tons of
xruns even when using aplay talking directly to hw:0. I literally need at
least buffer of 512 for aplay to play ok. I also noticed that certain
applications (i.e. frozen-bubble) would play stuff a bit faster than they
ought to be played (although I am not sure whether this is linked to a
particular alsa driver version or the preempt stuff).

With preemptive flag disabled, everything seems to be ok. 

Best wishes,

Ico




-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297

Re: dxs_support and via82xx (yet once more) -- some new findings

[Takashi Iwai]

At Sat, 24 Apr 2004 14:02:32 -0400,
Ivica Ico Bukvic wrote:
> 
> > yes, the module name still consists of snd- prefix.
> > the snd_ prefix was dropped from the module OPTIONS.
> > (e.g. dxs_support would have been named as snd_dxs_support in the old
> >  versions.)
> 
> Oh, I see now. Thank you very much for explaining that.
> 
> Now, when I do put in an option into the modules.conf specifying a different
> dxs mode, am I still supposed to get the same message in my syslog about
> picking trying dxs=1 or 4 or does that message show up only when no options
> have been successfully parsed?
> 
> I am asking this since even when I am 100% sure that my syntax is/was ok I
> would still get the message no matter what option was specified in
> modules.conf. I tried hacking via82xx.c file where I would hardwire my
> vendor/card ID into the list of known cards and changing it that way and the
> card worked the same no matter which options I chose, so I decided to leave
> it at DXS_ENABLE (or 1 if I am not mistaken). This is the only way how I
> would disable that message from appearing in syslog.

the problem is that you're modifying the obsolete config file (see
below).

anyway, try to load directly the module, not from the init script.
that is, run the following as root (suppose that snd-via82xx is not
loaded yet):

	# modprobe snd-via82xx dxs_support=1

so that the module parameter is passed directly.

> What kind of difference am I supposed to notice by changing dxs in order to
> figure out the best option anyhow?

when dxs_support=2, you'll have no DXS channel PCM (see
/proc/asound/pcm).
with dxs_support=3 and 4, you see always 48k DAC rate in
/proc/asound/card0/codec97#0/ac97#0-0 regardless of the playback
rate.  dxs_support=3 keeps 48k in the PCM hw_params
(/proc/asound/card0/pcm0p/sub0/hw_params) while dxs_support=4 accepts
other rates, too.
dxs_support=1, AC97 and hw_params rates will vary.


> As it is right now I can play 4 simultaneous streams and they all sound ok
> (no apparent glitches etc.). But this is the case no matter which option I
> pick.
> 
> > BTW, i assume that are you using 2.4 kernel.  is it right?
> 
> No, I am working with 2.6.3 and 2.6.5 (both patched).

bah, then it's now called /etc/modprobe.conf.
/etc/modules.conf is OBSOLETED!

add the options to /etc/modprobe.conf.


Takashi


-------------------------------------------------------
This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek
For a limited time only, get FREE Ground shipping on all orders of $35
or more. Hurry up and shop folks, this offer expires April 30th!
http://www.thinkgeek.com/freeshipping/?cpg=12297