Every time my system boots, /etc/init.d/alsasound loads the sound modules after udev has already been started by /sbin/rc. This leads to missing sound device nodes (/dev/dsp, /dev/mixer, etc). I have added a call to udevstart at the end of load_modules() in /etc/init.d/alsasound and everything works now. I think a call to udevstart should be included in load_modules() if udev is installed and used.
(In reply to comment #0) > I think a call to udevstart should be included in load_modules() if udev is > installed and used. No, alsa definitely should't be starting udev. Is udevd running? Also, udev version missing, alsa version missing...
(In reply to comment #1) > (In reply to comment #0) > > I think a call to udevstart should be included in load_modules() if udev is > > installed and used. > > No, alsa definitely should't be starting udev. Is udevd running? Also, udev > version missing, alsa version missing... > media-sound/alsa-utils 1.0.10 sys-fs/udev 079-r1 # ps -ef|grep udevd root 2836 1 0 10:36 ? 00:00:00 /sbin/udevd --daemon
what kernel version are you using? udevstart is _not_ to be used by newer kernels.
I had kernel 2.6.11.11 and that had the problem. Upgrading to 2.6.15.1 fixed the issue.
(In reply to comment #3) > what kernel version are you using? > > udevstart is _not_ to be used by newer kernels. > 2.6.10, I'll try to upgrade it.
I have 2.6.11.6 and the same problem. Running udevstart manually worked for me too as a quick fix.. when I did /etc/init.d/alsasound restart the devices disappeared again.. Then I downgraded to udev-070-r1 and everything now works as expected again.. My friend told me that the kernel interface in udev changes a lot between versions, could it be that 079 just isn't meant to be used with 2.6.11 kernels? I can only hope you keep this udev-070-r1 ebuild around (or fix the newer ones if that is the correct solution) until I am able to upgrade the kernel.. Thanks, Jonas
the problem might be 2.6.11, and as that's not a kernel that we are supporting anymore, I really don't know. Please upgrade (for the security fixes alone.) Am marking this closed. If you still have this issue using 2.6.15, or 2.6.16, please reopen this.