Users want to run alsaconf

[xkernel@…]

For running alsaconf You need to compile whiptail or dialog before. That's not in the book.

[bdubbs@…]

I found dialog at ​http://packages.debian.org/unstable/misc/dialog

The build is fairly vanilla, but the install needs to be done by copying the executable and man page to the proper locations.

alsaconf runs, but I cannot test it becuse the alsaconf script assumes that the user is using modules. I have my sound driver compiled into the kerenel. The script's purpose is to load the appropriate module and test it.

The script also sets the volumes for alsamixer using amixer, but only after finding and installing a kernel sound module. That would be useful for non-module based kernels too, but would require modification of the script.

Probably the best thing for the book is to add this as an optional dependency and update the short description for alsaconf.

Lowering priority/severity.

[alexander@…]

Alsaconf creates setup that doesn't play nice with udev. Therefore, there's no point in being able to run that program. If you just want "dialog" from ​http://invisible-island.net/dialog/dialog.html to be in the book, please open a separate bug.

[Matteo]

I had the same problem with alsaconf, and i'm using modules for audio. Installing dialog fix the bug and alsaconf works, we can insert dialog as a dependency of ALSA-utilities?

[alexander@…]

mat_jack1: what is your sound card? Running alsaconf is always a bad idea with udev, especially with more than one sound card. Alsaconf only does the following things:

• Creates aliases in /etc/modprobe.conf, but, as explained in LFS, aliases never work with udev due to a chicken-and-egg problem, and udev should be able to load sound modules even without aliases in modprobe.conf.

• Unmutes audio, but you should know how to do this yourself.

In addition, it teaches you nothing in terms of creating a working setup.

[bdubbs@…]

Milestone old deleted