On Tue, Feb 27, 2007 at 03:12:57PM +0000, Nikhil Nair wrote: > Hi, > > I'm working on a debootstrap installed etch amd64 system; 2.6 kernel, udev > etc. Audio (snd_emu10k1 module, SBLive! card) hasn't been working > consistently - some applications are fine, one gave a warning message, and > one crashed out altogether. > > I've worked out that this is all about ALSA vs. OSS: mplayer warned that > /dev/dsp was missing before reverting to ALSA, and flite (text to speech) > failed for that reason. I then found the linux-sound-base package, which > is configured to ALSA, but as that's the recommended setting, I thought > I'd better leave it there.
[...] > > I found a suggestion on the web that I should add a few lines to > /etc/modprobe.conf; as Debian uses modprobe.d instead, I put them in the > new file /etc/modprobe.d/oss-emulation, as follows: > > 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 > > I then rebooted, but still got the same issues. When I 'modprobe > snd-pcm-oss' manually, things work OK. > so, when you reboot, what is the state of snd-pcm-oss? is it already loaded so that your modprobe is reloading it? or it is not loaded? > I think what is happening is this: the kernel is waiting for an attempted > access to /dev/dsp etc. in order to load the snd-pcm-oss module; however, > udev is waiting for the module to be created before allowing /dev/dsp etc. > to appear. Because there is no file /dev/dsp, there can be no attempted > access to the appropriate kernel device. > > Presumably I need to do something in the udev setup to fix this - either > that, or have the snd-*-oss modules loaded automatically at boot-time. > Where do I put the names to have them loaded automatically? have you run alsaconf? all of this should be taken care of by running that. it sets up all the aliases so that the devices are created at boot. A
signature.asc
Description: Digital signature
