Home / ubuntu / Questions / 92619
Accepted
dr Hannibal Lecter
Asked: 2012-01-04 13:48:55 +0800 CST

How do I compile ALSA 1.0.24?

  • 772

I'm using Ubuntu Maverick on my main PC, and I got the system configured just the way I like it (yay!) a long time ago. Everything was well until the recent Wine releases which are apparently made to use ALSA 1.0.24 which is sadly not available for Maverick. This means I lost all sound in Wine, which is not nearly as funny as it should be!

I found this tutorial on how to build ALSA 1.0.24, but I'm not sure if the procedure is "safe enough" to use. By "safe enough" I mean "will it mess up my system beyond repair". Is the big red-lettered disclaimer in the beginning of the article justified? How dangerous is the procedure described? Should I risk it and give it a shot or just bite the bullet and install Mint from scratch, like I did on my laptop (successfully, it seems)?

UPDATE:

After following Gilles' advice below about trying to install ALSA binaries for Lucid, I had a bit of a problem with sound being blocked for other apps when playing something in Flash. To fix this, I did the following:

Create /etc/asound.conf with the following content:

pcm.pulse { type pulse }
ctl.pulse { type pulse }
pcm.!default { type pulse }
ctl.!default { type pulse }

Then simply restart ALSA with the following command:

sudo alsa reload

I found all this on this forum thread but chose to restart ALSA instead of the whole system, and it worked!

compiling

1 Answers

  1. Best Answer

    This warning is grossly exaggerated. The main problem with it is that it will install files under /lib and/usr, overwriting some files provided by the Ubuntu distribution. This means that it won't be easy to uninstall or upgrade your manually installed drivers. I recommend specifying ./configure --prefix=/usr/local when compiling the library and the utilities, so that everything you install that isn't part of the distribution is under /usr/local. For the drivers, you don't have this luxury: they must be under /lib/modules, but fortunately these aren't so critical.

    Nonetheless, I suggest carefully reviewing and keeping note of what files are being installed. Run make -n install to see this, before running sudo make install. Alternatively, install the stow package, create a directory /usr/local/stow/alsa-1.0.24, give yourself write permission on it (e.g. sudo chown hannibal /usr/local/stow/alsa-1.0.24), specify ./configure --prefix=/usr/local/stow/alsa-1.0.24, and run make install without sudo. Then run sudo stow alsa-1.0.24 from the /usr/local/stow directory. Finally, symlink the modules under /usr/local/stow/alsa-1.0.24/lib/modules to the corresponding directory under /lib/modules and run sudo depmod -a.

    Compiling the packages from the upstream source is not the easiest solution. There's a PPA with Alsa 1.0.24 packages for lucid; those binary packages might work on maverick. Or you could try recompiling the 1.0.24 packages from natty.

    • 2