On 12/17/05, Ernie Schroder <[EMAIL PROTECTED]> wrote: > > Is /dev/dsp actually missing on startup, or just created with the > > wrong permissions? > > Apparently it has the wrong permissions, or so says the message when I start > KDE,but if I reset them, next boot they are changed. Either resetting > permissions, or doing # udevstart allows me to use /dev/dsp as user but > changes don't survive a reboot.
Hmm, /dev/dsp is only necessary for legacy OSS support...it should not be necessary with KDE, which _should_ be able to use the ALSA interface. Do you have the alsa USE flag set? What are the permissions that it is being created with? (Do "ls -l /dev/dsp" from a console after startup without logging into KDE). > > Are you using a device tarball (RC_DEVICE_TARBALL in /etc/conf.d/rc)? > > Yes. I would suggest turning TARBALL off. It is almost certainly not needed today. One possibility is that the device is comfing from the tarball, but not being recreated by udev for some reason. You can check this with: tar -tjvf /lib/udev-state/devices.tar.bz2 Also, what messages do you get on bootup between "Starting udevd" and "Mounting /dev/pts..." Do you CONFIG_SND_PCM_OSS=y or =m in your kernel configuration? -Richard -- [email protected] mailing list
