hi, thankyou for reply.... > 'm' to unmute each muted control, then change the volumes. If you > really cannot alter the volume sliders, you possibly have the wrong > driver in the kernel.
with "m" I control some switch OK; MASTER is ON but fix to zero and aplay run OK but no sounds I try command: mknod -m 666 /dev/dsp c 14 3 and command: mpg123 xxxxx.mp3 play somethings in silent > On a few chips, there are more controls than will fit in the console > window, and you have to cursor right to access them - start by unmuting > everything, increase the volume of everything except master, play a .wav > file with aplay in another term, and use the master volume to increase > the volume until you can hear it. After that, experiment to find which > controls actually matter on your installation, and set your preferred > volume. > You may also need to add yourself to the audio group. I add UID 0 to group audio > > - when I installed ALSA, in alsa-tool package I installed nothing..... > > is this wrong ? > > I don't think I bother building that, so only wrong if there is > something there that you want. > > > - when I run alsaconf I look at an error: > > modinfo: could not find module snd > > Because you have now built it in. I believe alsaconf assumes > everything will be modules. > > > what can I do ? > > *grin* Stop top-posting and trim your replies ? > > Seriously, the LFS book's configuration I pointed you to yesterday > works for me when I build sound as modules, and when I build it into the > kernel it also works. > > I did once have unsolved problems with alsaconf when it wanted to use > the (not connected) sound chip on the mobo, and I wanted to use an > add-in card, but for most people it works. If it doesn't work, limit > your testing to aplay and alsamixer until you have basic sound > functioning, then you can try other applications that might use oss > devices. I have soundcard on motherboard, but with archie (using udev and ALSA and same kernel) it work OK > I've just taken a look at my main desktop box - no alsa files other > than the mixer state, but sound works. I guess this means alsaconf is > not normally required, at least if the sound driver is built in to the > kernel. > > Ken thankyou for patience [EMAIL PROTECTED] -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
