I have just upgraded the system and among other things module-init-tools were upgraded from 3.0-r2 to 3.1. After that I later rebooted my system and noticed that ALSA drivers couldn't be loaded. I downgraded to module-init-tools 3.0-r2 and alsasound scrpt started to work again. So I guess there is something wrong with new m-i-t that breaks ALSA, or alsasound initscript is not compatible with new m-i-t. I'm using kernel gentoo-dev-sources 2.6.9-r3 and alsa-drivers 1.0.7-r1. Reproducible: Always Steps to Reproduce:
*** This bug has been marked as a duplicate of 72420 *** *** This bug has been marked as a duplicate of 72420 ***
I've been reading the other bug but it isn't about module-init-tools like this one is. The old ones work but 3.1 just doesn't work correctly.
This is what I did today: I emerged the new kernel (I had gentoo-dev-sources-2.6.9-r3 before and now 2.6.9-r6). Before compiling the kernel I made sure that all the ALSA and OSS options in the config are disabled (to make sure all the modules are not installed). After I compiled the kernel I reemerged alsa-drivers and nvidia-kernel. After reboot all was working fine (I still had module-init-tools-3.0-r2 installed). I then upgraded module-init-tools to 3.1 and rebooted again. During the booting I again started to get errors I mentioned above. I then downgraded module-init-tools to 3.0-r2 and rebooted again. This time all ALSA modules loaded up just fine. So the only difference between working and not working system is the version of module-init-tools.
This looks like a duplicate of bug #72099 And it happens to me as well.
Yeah it look like a duplicate of this bug. I'm marking it as szch. *** This bug has been marked as a duplicate of 72099 ***
