On 5/29/07, Jordan Bray <[EMAIL PROTECTED]> wrote: > On 5/28/07, Jordan Bray <[EMAIL PROTECTED]> wrote: > > I compiled gnome, got it working minus the sound. I compiled esound > > for that, it compiled fine. Here is how my day went: > > <code> > > #esd > > ALSA lib pcm_dmix.c:819:(snd_pcm_dmix_open) unable to open slave > > #esd -d "hw:0" > > - using device hw:0 > > #ps -A | grep esd > > #alsamixer > > </code> > > unmute everything and i do get to modify settings and such > > <code> > > #aplay > > ALSA lib pcm_dmix.c:819:(snd_pcm_dmix_open) unable to open slave > > aplay: main:542: audio open error: No such file or directory > > #speaker-test > > > > speaker-test 0.0.8 > > > > Playback device is plughw:0,0 > > Stream parameters are 48000Hz, S16_LE, 1 channels > > Using 16 octaves of pink noise > > Playback open error: -2,No such file or directory > > Playback open error: -2,No such file or directory > > ... > > ^C > > #lsmod | grep snd > > snd_cmipci 28416 0 > > snd_pcm 84872 1 snd_cmipci > > snd_page_alloc 8840 1 snd_pcm > > snd_opl3_lib 9216 1 snd_cmipci > > snd_timer 20868 2 snd_pcm,snd_opl3_lib > > snd_hwdep 7200 1 snd_opl3_lib > > snd_mpu401_uart 6016 1 snd_cmipci > > snd_rawmidi 20512 1 snd_mpu401_uart > > snd_seq_device 7180 2 snd_opl3_lib,snd_rawmidi > > snd 47588 8 > > snd_cmipci,snd_pcm,snd_opl3_lib,snd_timer,snd_hwdep,snd_mpu401_uart,snd_rawmidi,snd_seq_device > > </code> > > > > I've recompiled everything and still no luck and i am unfamiliar with alsa. > > > > any help would be greatly appreciated... > > > > -- > > /me > > > > The problem was /dev/snd/ devices weren't created. I don't know where > in the b?lfs process this is supposed to take place, but my > MAKEDEV-1.7 does not make these devices. there is a script included > with alsa-driver-1.0.13 called snddevices which i was able to use to > create the /dev/snd devices for alsa. > > -- > /me
Udev handles all devices that should be installed, and if udev doesn't create them at start, then you are probably missing the driver, and you end up recompiling the kernel. So, are you running a 2.4.x kernel like Simon said? If so, then you should really upgrade to 2.6 kernel, but that could cause problems, so you should really install the kernel next to the old one, and make them both available for boot, so that when your 2.6.x won't boot because of incompatible apps or such, then you can go back to 2.4.x without problems :) Tijnema -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
