Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hi there i'm having a problem with package module-init-tools both pre and .9 ..seems like it isn't fully installing from source code.. nope not a dependency problem..looks like it's installed and acts like its installed
but whgen i do make modules_install kernel 2.6.5 complains ..codemonkey halloween..blah blah.. so every time i boot into kernel 2.6.5 Qm_Modules_funtion not implemented.. and i have to load ALL my modules by hand after boot ...also theres nothing pointing to lib/modules/2.6.5 so in order to even load my modules i have to load them from lib/modules/2.6.5
not a simple insmod..whats going on here..oh yeas i'm using rh9
well looks like i found a way to fix it..however it my old kernel got botched in the process.. but you're right it will install itself in /usr/local like a lost puppy dog ..my only solution was to copy all its install files into /sbin/..whoever wrote this program (i think the guys name is rusty) needs to work on it a lil more ..it's even worse in debian woody (libranet)
looks like i ended up in reinstall land ..well now i know..worse part is if recompiled the kernel 2.6.5 in 18.104.22.168 the poor thing thinks its 2.6.5 and won't make an initrd thinking its 2.6.5 and the loop back is up..sighz..hope this is a help for anyone else who encounter problems from this shafty always pre beta module-init-tools proggy..cheers
Anyway, I'm gonna compile and build new module-init-tools.
I'll move old modules and pass --preix= / to the ./configure alright?
So ti will install modules in /sbin and 2.6.6 kernel will look there for'em isn't it?
Correct me if I'm wrong I'm olny a newbie folks :-)
Yes you do need to do that. The generate script is in the mod-init tools directory when you make the command in terminal while in the tools directory it creates the file /etc/modprobe.conf when you finish compiling use command modprobe and see the result or modinfo . I could not get my modules loaded properly without that script. good luck. Marty
%tar -jvzf ...
%./configure --prefix=/ <---installing modules in /sbin dir
$make move old
$ ./generate modprobe.conf /etc/modprobe.conf <---must be done at the very end?
now new module-init-tools should be correctly installed.
Correct me if I'm wrong
EDIT: I'have just read man modprobe. It says that make modules_install create another directory but does not change de default one. So to change the default to the current you should use depmode - (parameters) is that correct?
Or it's only necessary $make move old? Or only ./generate modprobe.conf /etc/modprobe.conf.
I'm a little confused....
Last edited by fenice1976; 05-17-2004 at 01:38 PM.
with my experience which is not a lot I found after configuring modinittools I had to create the file modprobe.conf. That is what worked for me otherwise Qmodules not found, do modprobe when finished to see if its installed. practice is the key as far as the other stuff I didn't seem to need it. Once you configure module init tools you have to "make install" to install it to kernal. That is how I remember. "./configure" or "make" is first config step,"make install" is second step " ./generate modprobe.conf "is the third and final part. at least for rh9 marty