DXS autodetection in snd_via82xx module is unreliable?

[Łukasz Nowak]

I'm using card:
atari:~ # lspci -s 0000:00:11.5
0000:00:11.5 Multimedia audio controller: VIA Technologies, Inc. VT8233/A/8235
AC97 Audio Controller (rev 50)

And this card is properly detected. But the parametr dxs_support (Support for
DXS channels) if set to auto (0) enables
DXS, but I have only two channels. I have to put line:

snd_via82xx option dxs_support=2

in modules configuration file.

First boot, and next, are fine, but after 5 boot autodetection fails.

[Matt Zimmerman (mdz)]

When you say that autodetection fails, what do you mean? Please attach the
following:

dmesg output when it is working
dmesg output when it is not working

[Łukasz Nowak (ionowaklukasz)]

(In reply to comment #1)
> When you say that autodetection fails, what do you mean? Please attach the
> following:
> dmesg output when it is working
> dmesg output when it is not working

When I meant that autodetection fails:
Automatic detection in module, param dxs_support (set to 0), activates DXS
channel support, which is
not good. I have to manually use dxs_support = 2 to gain hearable sound. DXS
support activated uses all
minijacks as output for sound - it's 5.1 channel soundcard.

Card is working good in any of that state, but with DXS support activated sound
level is very low.

Sorry,
That's my flacky english :(

[Łukasz Nowak (ionowaklukasz)]

Created an attachment (id=828)
dmesg without working sound

Right now I have:
#options snd_via82xx dxs_support=2 # <- commented out
in
/etc/modprobe.d/aliases
DXS channels are muted in mixer. Two speakers connected.

[Łukasz Nowak (ionowaklukasz)]

Created an attachment (id=829)
dmesg with working sound

Now:
options snd_via82xx dxs_support=2 # <- not commented
in
/etc/modprobe.d/aliases
DXS channels are NOT avaiable in mixer. Two speakers connected.

[Ben Collins (ben-collins)]

Odd, both the dmesg's are identical, and so sign of the sound driver being
loaded. Loading the module doesn't provide any sort of kernel output?

[Ben Collins (ben-collins)]

This bug has been flagged because it is old and possibly inactive. It may or may
not be fixed in the latest release (Breezy Badger 5.10). It is being marked as
"NEEDSINFO". In two weeks time, if the bug is not updated back to "NEW" and
validated against Breezy, it will be closed.

This is needed in order to help manage the current bug list for the kernel. We
would like to fix all bugs, but need users to test and help with debugging.

If this change was in error for this bug, please respond and make the
appropriate change (or email <email address hidden> if you cannot make the
change).

Thanks for your help.

[Łukasz Nowak (ionowaklukasz)]

Hello,

(In reply to comment #6)
> This bug has been flagged because it is old and possibly inactive. It may or may
> not be fixed in the latest release (Breezy Badger 5.10). It is being marked as
> "NEEDSINFO". In two weeks time, if the bug is not updated back to "NEW" and
> validated against Breezy, it will be closed.

That bug IS FIXED in Breezy - at least on my machine. Right now all is working fine.
Updated Hoary kernels had fixed that bug. As for me that bug could be set as FIXED.

Thanks,
Luke Nowak

[Dennis Kaarsemaker (dennis)]

Fixed according to user