Linux From ScratchThis Forum is for the discussion of LFS.
LFS is a project that provides you with the steps necessary to build your own custom Linux system.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
I've got the same problem as logicalfuzz in his/her thread.
I am in the mid-way of having ALSA in place on my (B)LFS 6.1. I installed ALSA-lib, ALSA-plugins, ALSA-utils. When I tried to configure the utils with alsaconf it says something like
modinfo : could not find module snd
which : dialog not found
which : whiptail not found
Error, dialog or whiptail not found.
"which" seems to be in place, but I can't understand what dialog and whiptail are (neither LFS nor BLFS indexes contain anything alike). BTW, lspci lists my AC97 on-board sound "card"
... Multimedia audio controller: VIA VT82C686A (rev 10)...
no unknown things listed, so LFS found my soundcard.
I tried to recompile the kernel without any modules - no changes.
Last edited by Vitalie Ciubotaru; 03-11-2006 at 05:03 AM.
In Fedora, and, I suspect, any system using ALSA, you need to define the sound driver in /etc/modprobe.conf
# ALSA portion
alias char-major-116 snd
alias snd-card-0 snd-<your driver name>
# OSS/Free portion
alias char-major-14 soundcore
# card #1
alias sound-service-0-0 snd-mixer-oss
alias sound-service-0-1 snd-seq-oss
alias sound-service-0-3 snd-pcm-oss
alias sound-service-0-8 snd-seq-oss
alias sound-service-0-12 snd-pcm-oss
Also (again, on Fedora, but I suspect others) ALSA initially defaults to all sound muted. Check /etc/asound.state for the ALSA device states and levels. (Those are usually set by amixer, but, without the dialog tools, I think amixer won't work very well.)
PTrenholme, thank you for the information above (and below - I edited this after you posted the quote on whiptail).
I consulted the modprobe.conf on my Fedora Core 3, which produces sound with no problem, and think that the problem is not in this file. My FC3 finds the soundcard and creates devices (pcmC0D0c, PCMC0D0p, timer and smth else) in /dev/snd directory, while LFS creates similar devices in /dev directory.
Can this be the reason why my ALSA doesn't find them?
Last edited by Vitalie Ciubotaru; 03-11-2006 at 05:14 AM.
Dialog compliant utility that allows you to build user interfaces in a TTY (text mode only). You can call dialog from within a shell script to ask the user questions or present with choices in a more user friendly manner.
Dialog (and gdialog) are similar "window on terminal" display programs.
Thank you once again.
I found dialog on my Fedora Core 3 and read the manual to it (now I see that whiptail is the same thing). I simply copied the executable (don't know how wise it is) from /usr/bin of FC3 to /usr/bin of LFS. Now alsaconf doesn't complain about dialog/whiptail, but still produces error (it can't find my card/device). The same is true, for example, for alsamixer - it says it can't find the default card/device, but I do not know their names. Are they different from other distros?
Assumption here -- I may be wrong -- but if you're doing LFS, don't you have to build your own sound driver? If so, it's wherever you put it, and called whatever you called it. I also suspect that you need to compile sound support into your kernel, and the source code -- or the LFS documentation -- should go into some detail about where the drivers are located and how to build them. (I also suspect that it tells you how to change those locations to suit yourself.)
I am completely confused.
PTrenholme said I presumably "have to build [my] own sound driver". Stupid question, but still: what does the word "own" mean/imply?
I followed BLFS instructions and built ALSA Libraries, ALSA Plugins and ALSA Utilities (alsaconf, alsamixer and the like). I know that there is an ALSA Drivers package, but there's nothing about it in the BLFS documentation, so I did not build it.
PTrenholme suspects I "need to compile sound support into [my] kernel".
I still need additional comments on that.
I enabled sound support in my kernel, tried to enable/disable/modularize support for my sound card (which is specified above), I even tried to build it all as modules - no changes. I definitely didn't (re)assign any names and didn't move anything for the mere reason that the instructions do not say that.
Thank you for your participation. However, I am stuck with this problem.
In order to get any further, I need structured answers to the following questions (if I'm mixing up things, please correct me):
1. The kernel. In order to get my soundcard (on-board, VIA686A chip based, AC97) working, shall I (re)build the kernel:
a) with sound support enabled or modularized?
b) with my type of soundcard enabled or modularized (or maybe disabled as the ALSA website suggests)?
c) other things enabled or modularized (and which namely)?
2. The ALSA package.
a) How can I find out that my operating system recognized (found) the soundcard, and its just ALSA that can't interact with it? In this case, it just has to be configured properly, right?
b) How is it configured?
If anyone encountered the same or similar problems, and solved them successfully, or just knows the answer to a particular question I posed please let me know.