[karmic] Please update alsa to 1.0.20 version

Alsa in jaunty will not be updated to 1.0.19 at this late stage. Any important fixes in newer versions of alsa will be included in jaunty's alsa packages where necessar.

 affects ubuntu/alsa-driver
 status wontfix

Is it possible that update alsa to 1.0.19 version into karmic?

karmic will have at least 1.0.19 userspace and kernelspace.

Sound does not work at all in a number of common chipsets with the version that is shipped with Jaunty... Neither my Thinkpad T61 or my HP Mini 700 have sound, and the word is that 1.0.19 fixes the problems with the Intel sound chipset... I'm not really sure what we're supposed to do, I've hunted for a PPA with 1.0.19 but no luck yet, and I am really reluctant to try to build from source, as the reason I switched to Ubuntu was to ensure that everything is done from packages to avoid dependency issues.

Well my sound chipset (a RealTek ALC 889A) is completely unbearable without using 1.0.19 - it stutters frequently.

The same is true for almost all the cards using the snd-hda-intel driver. I really cannot believe that this package is not included in Jaunty. It is literally a joke that recent(ish) chipsets that are properly supported in a stable release of ALSA are not working in the newest release of Ubuntu.

I'm tired of compiling ALSA from source every time the kernel package is upgraded slightly. Sorry for ranting a bit, but this really does just make Linux seem like a joke to new users who will not be able to compile these packages from source.

The further add to my rant. There isn't even a PPA for people to use who actually care about having working sound in Linux.

On Wed, 29 Apr 2009, Pete Woods wrote:

> Well my sound chipset (a RealTek ALC 889A) is completely unbearable
> without using 1.0.19 - it stutters frequently.

You're confusing two separate causes (though I admit it's fairly easy to
confuse the symptoms for people who aren't intimately familiar with the
source code).

Firstly, there're mid-layer changes in sound-2.6.git that help immensely
with the stuttering. You can find the most important of those changes
already applied in my test kernel (http://kernel.ubuntu.com/~dtchen/). I
have also proposed those changes (see the kernel-team@ archive) for
jaunty-proposed.

Secondly, there're controller-level changes in sound-2.6.git that address
polling and detection. Those changes have not been proposed for
jaunty-proposed yet (but feel free to do so!).

Thirdly, it's important to note that not all audio anomalies are resolved
even with daily (un)stable snapshots of git HEAD for sound-2.6. The audio
stack is evolving, and as various components shift around jaunty's frozen
userspace (since people tend to want sound working and tend to compile
random stuff), it's very much a moving target.

Lastly, providing [frequently] updated alsa-kernel bits is difficult in a
PPA, because several recent changes have bumped the symbol exports, which
results in an ABI bump in the linux image. One essentially ends up needing
to rebuild the linux image, provide new headers, and provide a new
restricted-modules image. We went through a lot of pain during hardy when
we shipped ALSA in linux-ubuntu-modules.

I will, however, look into providing snapshots compiled against
jaunty-updates/jaunty-security and jaunty-proposed.

So what you're saying is that by compiling all of ALSA it's actually the kernel side of things that is causing the improvements? And that in the sound-2.6 patchset(?) these changes are already being included?

Assuming what I said is correct there, would this mean that once the sound-2.6 changes have been included that my compiling of ALSA would become redundant?

"+ [karmic] Please update alsa to 1.0.20 version"

I guess that this means that audio support for modern chipsets is staying broken in Jaunty then. Oh well, I'll just keep on compiling those packages...

alsa-base.preinst has a leading backslash before the shebang (\#!/bin/sh), as well as some merge conflict markers (<<<<<<) in the middle of the file, leading to bug 380426. The backslash was just fixed in bzr, but not the conflict markers.

This bug was fixed in the package alsa-driver - 1.0.20+dfsg-1ubuntu3

---------------
alsa-driver (1.0.20+dfsg-1ubuntu3) karmic; urgency=low

  * alsa-base.preinst: Remove leading \\ that prevented installs
    and upgrades from completing (LP: #380426)
  * alsa-base.{modprobe,postinst,preinst}: Remove diff(3) conflict
    markers (LP: #380426)
  * New version packaged (LP: #324646)

 -- Daniel T Chen <email address hidden> Tue, 26 May 2009 02:15:32 +0200

i just found this ppa with alsa 1.0.19 in it: https://launchpad.net/~themuso/+archive/ppa