ALSA Upgrade Script

[zim2dive]

If you updated the kernel, you need to run the script with -i again. Also, it might help to make a log of it like suggested in the OP.

I ran thru the process twice.. but still show 1.0.22.1 ... alsamixer shows nvidia sound when I hit F6, but aplay -l does not list my GT240.

Where does one get version info for alsamixer?

Logs are attached.

EDIT: oh duh.. it does say 1.0.23 in the alsamixer top line (I was trying to find a command line -version switch)... but aplay -l does not list my GT240, and "cat /proc/asound/version" shows 1.0.22.1, not .23.

[Objekt]

You appear to have a local version of libavcodec which is taking precedence over the repo version.

How can I fix that? Just uninstall my local version through Synaptic, then try again?

[Yellow Pasque]

How can I fix that? Just uninstall my local version through Synaptic, then try again?

It would be nice if you could remember how it got there. To find out if it's part of a .deb package:

dpkg-query -S /usr/local/lib/libavcodec.a

More likely, you compiled source somewhere along the line and installed it. If you still have the source directory, you would run 'make uninstall' from it.

[Vladimir Hidalgo]

https://bugs.launchpad.net/ubuntu/+s...48/comments/97

I think we're doing it wrong, there's an alsa ppa that we can use to avoid compiling. Silly me, this could made me avoid downloading about 500MB in order to compile ALSA.

[Objekt]

Guess I'll try that next, since the download-and-compile thing didn't work for me.

I'm happy I didn't break my sound (yet!).

[juiceguden]

Still no sound, either something is wrong with apt-get or the script messed up my system.
I have since tried AlsaUpgrade-1.0.22.1-2.sh -r , but it didnt help.

Any suggestions what I can try?

I have included my original post below.

(In response to Temujins suggestion to run apt-get install libasound2-dev): Thanks, but your suggestion does not work, apt-get complaints about dependencies. Unfortunately the messages are in Swedish, so a copy and paste won't probably help you help me, but roughly translated it says:

Some packages could not be installed. The cause of this could be that you have requested an impossible situation or, if you are using the unstable edition, that some nescessary packages have not yet been created or moved out from "incoming". The following information could be of help for resolving the situation: 

The following packages have dependencies that are not satisfied:
  libasound2-dev: Dependent of: libasound2 (= 1.0.20-3ubuntu6) but 1.0.20-3ubuntu6.1 will be installed
E: Broken package

Any further tips?

[Vladimir Hidalgo]

If you still have the change to re-install ubuntu Lucid, update it to the lastest packages and then use the alsa ppa repo, then you should go this way.
At this point with custom kernels and other things you'd modified it's almost a game for anybody to try to give you a proper solution.

[zim2dive]

https://bugs.launchpad.net/ubuntu/+s...48/comments/97

I think we're doing it wrong, there's an alsa ppa that we can use to avoid compiling. Silly me, this could made me avoid downloading about 500MB in order to compile ALSA.

>sudo apt-get install linux-alsa-driver-modules-2.6.31
Reading package lists... Done
Building dependency tree       
Reading state information... Done
E: Couldn't find package linux-alsa-driver-modules-2.6.31

I added the PPA and did an update.. what am I missing here?

[paoleary]

I added the PPA and did an update.. what am I missing here?

That's not the complete package name; it will be linux-alsa-driver-modules-`uname -r` (including the -nn-{generic,server}). I'm actually trying the PPA now; we'll see how it goes.

UPDATE: There was a bit of finagling, as I believe the original alsa-modules package created an undetected conflict. Also, the tools are all back to 1.0.20 versions (so no F6 action in alsamixer, for instance). But the audio does work as it did before, and should be easier to upgrade.

[yonkiman]

That's not the complete package name; it will be linux-alsa-driver-modules-`uname -r` (including the -nn-{generic,server}).

I'm still a bit confused - I thought this would show up in Synaptic after I added the PPA ("sudo add-apt-repository ppa:ubuntu-audio-dev"), but I didn't see anything. Would you mind spelling out exactly what to type to get the repository and the alsa package? I'm not sure what to do with "linux-alsa-driver-modules-`uname -r` (including the -nn-{generic,server}".

UPDATE: There was a bit of finagling, as I believe the original alsa-modules package created an undetected conflict. Also, the tools are all back to 1.0.20 versions (so no F6 action in alsamixer, for instance). But the audio does work as it did before, and should be easier to upgrade.

I'm even more confused: This will upgrade alsa to the latest 1.0.23, but the tools stay 1.0.20?

I thought the ppa was supposed to be simpler than the script!