Must force module regeneration? [solved]

[violagirl]

Ever since I did emerge --update world, I have been getting this same error every time I boot up (though I have compiled the kernel lately as well, so to way which is causing the problem, I'm not sure):

[NeddySeagoon]

violagirl,

Normally, this means that one of your files in /etc/modules.d/ has a syntax error or contains an invalid option.
Do you get a warning about that too?

update-modules processes all the files in /etc/modules.d/ regardless of name, so move 50% of them out and run update-modules.
If the error is gone, its in one of the files you moved out, if its still present, its in a file still in /etc/modules.d/.
You now know in which half of the content of /etc/modules.d/ the error is. Repeat the method on the faulty half until you locate the file.
That method is called a binary search, since half the possibilities are eliminated with every iteration.

Do not leave files missing from /etc/modules.d when you shut down or many things will break at the next boot.
_________________
Regards,

NeddySeagoon

Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.

[violagirl]

Well, after doing update-modules force, when I rebooted the computer again I no longer got that message but then ALSA didn't work. So it turned out to be ALSA after all! So I just did alsaconf and now it works again. I wonder often why random things like this happen, like ALSA suddenly not working or me not being able to install ndiswrapper unless I recompile the kernel because it can't find some file or another.... they just seem so random. Well, anyway, that's all right. Thanks for the suggestion. Luckily, I figured out the problem!

[PaulBredbury]