modprobe: Can't locate module...
i just reinstalled gentoo on this box (after having a pretty good build for around 6 months until i filled the hard drive up so tight with junk i could'nt install anymore) so i go to reinstall and it all works fine and dandy, except that on my first virtual terminal there are modprobe error messages scrolling by every now and then that say "modprobe: Can't localte module" and then it will specifiy a name, except the things it is specifying are not even modules, it just picks stuff out of my /dev dirrectory and tries to load htem then pipes the output to that terminal and clutters them, i want to know why it's trying to load these things as modules (there are many differant devices in dev it will try, most of the time /dev/apm_bios (which does not even exist...) , but often other things too), how to stop it, and why it is piping it all out to that term, anyone know? i dont remember having the problem the last time that i installed gentoo.
|
You could check /etc/modules.conf to see if that is where the commands are being issued to load all these things. If so you can comment out the superfluous commands.
|
i looked there, and looked through /etc/modules.autoload to see if anything looked funky but none of the things i was seeing were specifically mentioned in either of those files, when i start X is when a LOT of them come up like 50 or so /dev devices fly by being tried to load as modules and half of them dont even exist, i assume all of this is also slowing things down somewhat as well.
|
Me too.
Ihave this issue as well...any resolution?
|
same issue
I too have a fresh build of Gentoo and have the same problem.
Has anyone found a fix. I have kernel 2.4.20-r6 I did a Stage 1 install yesterday. All I have installed is gnome. |
Bug
Look at the Gentoo bug list. It's in there, as well as some fixes.
|
I have the exact same problem after reinstalling Gentoo. I looked on the bug list to try to find the solution. I couldn't find a bug reporting this problem. Could you give the bug number?
Thnx, ~michael |
fix
I had the exact same problem, modprobe messages, about 50 or so, when I log in as a normal user, (not root)
You need to add a system logger like sysklogd, metalog, msyslog, etc... emerge -k app-admin/sysklogd then make it start at boot with: rc-update add sysklogd default Problem fixed, at least for me, hope this helps :) |
That was it...when I did a reinstall of gentoo I forgot the rc-update part...thanks for the help!
|
All times are GMT -5. The time now is 06:10 AM. |