[alsa-devel] Via VT2020: issues with kernel 2.6.38.{2, 3} (alsa 1.0.23) - working with (alsa 1.0.21)

alex dot baldacchino dot alsasub at gmail dot com alex.baldacchino.alsasub at gmail.com
Mon May 9 01:16:01 CEST 2011


Thanks for your answer.

2011/5/8 Raymond Yau <superquad.vortex2 at gmail.com>:
> 2011/5/8 alex dot baldacchino dot alsasub at gmail dot com <
> alex.baldacchino.alsasub at gmail.com>
>> [...]
> Try the snapshot tarballs or git at
> http://www.kernel.org/pub/linux/kernel/people/tiwai/docs/HD-Audio.html

Sorry, I've never build modules out of 'regular' kernel build process
before, so I'd have a few questions. I'm using a tarball kernel source
for kernel taken from kernel.org, patched with some stuff
required by my distro (therein aufs) and incremented to version with the incremental patch taken, again, from kernel.org; I
have no git version of the kernel to pull the alsa git snapshot over,
and am not using a 'real' broadband connection at the moment, so I'd
prefer not to download a full git source. For accomplishing your
request, I've downloaded tarball alsa-driver-20110508.tar.bz2 from the
ftp pointed to within the document linked above

Now my questions. In file 'SUPPORTED_KERNELS' I can read the following:

"The alsa-drivers in this package are designed for the following kernels:

 - Vanilla 2.6.29 or earlier
 - Vanilla 2.4.31 or earlier
 - Vanilla 2.2.26 or earlier

It's not guaranteed that they work with any newer version than above
or modified kernels by distributors."

Is it a harmless warning, or should I upgrade my kernel to version or 38.5 and test the embedded alsa version (more recent than
current one I'm using) instead?

I've modified, through menuconfig ( CONFIG_LOCALVERSION ), my kernel
version string, so I can modify configuration at whim and keep
different flavors of the same kernel version (though I'm using just
one flavor for k; moreover, kernel source path doesn't match
the exact 'name' of the kernel (as named in /lib/modules/<version>)
and is located out of /usr/src, though actual source path is symlinked
from within kernel install dir as standard 'source' subdir (pointing
to <path/to/linux->). Hence, for what I've understood from
file 'INSTALL' in ALSA snapshot tarball, kernel version and source
tree should be easily identified by configure script, however, in case
there is a risk that ALSA snapshot gets misconfigured I prefer to ask
if I'd better to explicitly pass in --with-kernel and --with-build

But my main concern is about overall configuration. For better
comparison, I'd wish to use the very same sound configuration I've
used in kernel build process, but that's unclear to me if configure
script for ALSA snapshot will retrieve and use it, or if the script
can just use configuration options passed in/default values (as a
'regular' configure script).

Lastly, do I need to enable debug? (that is, is it required for better
alsa-info output?)

For now, below I'm posting alsa-info.sh output for current
configuration and for kernel (with working sound), hoping
this can help for comparison.

> Post the output of alsa-info.sh
> What is the model of your computer (desktop/notebook) ?

Sorry I didn't make it more clear in my previous post. Mine is a
home-build desktop with an Asrock motherboard (I don't know of any
notebook with asrock MoBo), model '890GX Extreme3', with integrated
graphics (Radeon HD4290) and audio (via vt2020 codec and ati hdmi), NB
AMD 890GX, SB850; CPU is a Phenom II X4 (kernel is configured
with amd specific optimizations while retaining x86 compatibility
code; kernel has no cpu-related optimization enabled; both
are 32 bit); 4 GB ddr3 memory; no expansion cards.

If more details are needed, I'll write full specs.

> How many audio jacks ?

Rear panel: 5 jacks for 7.1 channels audio + 1 Optical SPDIF OUT port
On board: front panel audio header for ac97/hd audio (connectors for
mic, left, right - I'm not sure if that's for supporting 2 independent
mono jacks, one stereo (headset) jack or both cases, I don't know
neither ac97, nor hd audio specifications) + header for 1 hdmi_spdif
out (to be connected to a discrete vga with hdmi capabilities)

> https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/729659
> It seem that vt2020 is 10 channels HDA with 5 [Audio Output] 0x8, 0x9, 0xa,
> 0xb and 0xc
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel at alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel



OUTPUT FOR ALSA-INFO.SH -- K2.6.33.2 - ALSA 1.0.21:


More information about the Alsa-devel mailing list