modprobe

I have downloaded the latest 2.2 kernel source installed it on my openlinux1.3 system and configured and compiled the kernel. When i then boot the computer it will boot up to a point and the a modprobe error happens and this then is continual echoed to the screen so i can not tell what the problem is.
MarktalbotAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

guiyuCommented:
Did you also do

make modules

and

make modules_install

, to speak the obvious.
0
poggaCommented:
The problem is you've upgraded the kernel but not the modules.
You'll need to get the 2.2 modules for Openlinux.
0
MarktalbotAuthor Commented:
I have made the modules from the source code and so this has alredy updated the system. I have the auto kernel loader option on.
0
Big Business Goals? Which KPIs Will Help You

The most successful MSPs rely on metrics – known as key performance indicators (KPIs) – for making informed decisions that help their businesses thrive, rather than just survive. This eBook provides an overview of the most important KPIs used by top MSPs.

sackeriCommented:
I had this happen once too.  Strangely enough, I can't exactly remember what I did to fix it.  I looked through the man pages of modprobe, and there is an option that you can send to modprobe to stop it looking for certain modules.  I think it is "modprobe -r <module to remove>".  If you want to see what modules it is looking for, try a "modprobe -a".  Also check out the depmod command.

By the way, I hope you are able to boot into Linux from a floppy, otherwise, this probably won't help much.

Good luck,

-sackeri
0
MarktalbotAuthor Commented:
i kept the old 2.0.13 kernel active so i boot off that. I dont actualy now what modprobe is upto because the screen is scrolling to fast. I removed autokernel module loading support and it still did this
0
MarktalbotAuthor Commented:
i kept the old 2.0.13 kernel active so i boot off that. I dont actualy now what modprobe is upto because the screen is scrolling to fast. I removed autokernel module loading support and it still did this
0
SkAtAnCommented:
Probably it's yout eth0 device ,
does it sais

Modprobe: Can't locate module lo:1
Modprobe: Can't locate module lo:2
Modprobe: Can't locate module lo:3
....
Modprobe: Can't locate module eth0:1
Modprobe: Can't locate module eth0:2
Modprobe: Can't locate module eth0:3
....
Modprobe: Can't locate module eth0:49
 ?

Try /etc/rc.d/network restart and check
if you get the same error then the one
when booting.

Normally it should be no problem, except
that this message only should appear in
/var/log/messages and not the active tty

You can check /etc/conf.modules for
errors, and you can check /lib/modules/2.2.x
if these modules you used are present.
0
MarktalbotAuthor Commented:
I don`t have a ethernet device
0
crouchetCommented:
You need to check the logs. use the dmesg command. For more complete information you may want to view the message log directly with this command:

less /var/log/messages

You will be interested in the end of this file. A quick way to view only the end is this command:

tail /var/log/messages

You can only do these things if you are logged in as root.

Bonus answer ----> I had a similar situation. My problem was that the parallel port module had a different name than what was being called for by the kernel. I found this because my printer would not work. If your parallel port is working, you have a different problem.

Anyway, the fix was to add these lines to /etc/conf.modules

alias parport_lowlevel parport_pc
options parport_pc io=0x378 irq=7

substituting your io port address and irq, if they are different from these.

J Crouchet
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
guiyuCommented:
1 ultra remote possibility:

Did you

1) edit your /etc/lilo.conf file to refer to the new kernel?
2) run lilo once?

If you didn't, then it might be possible that all this time, your old kernel was been booted (no matter what you select at lilo), and since you overwrote the old modules with the new 2.2.13 modules (make modules_install), neither kernel could find the correct modules.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Linux

From novice to tech pro — start learning today.