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

I had something simliar, when I installed module-init-tools, it went and hid in /usr/local, wheras my modprobe command usually lives on the root partition.

Try using 'make moveold', or hunting our modprobe, backing it up, then passing '--prefix=/' or such like to configure.

Also make sure you have '/etc/modprobe.conf'

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 2.4.20.8 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

Well I had similar problems but I have not understood a single word you said
Can you explain how to install this progs as I need them to compile 2.6.6 kernel?
Big thanks! :-)

Where the program goes is a matter of choice, but if /usr is on a different partition you need to keep an eye out and pass --prefix to configure!

Download module-init-tools, [http://www.kernel.org/pub/linux/util...ls-3.0.tar.bz2],

%tar -jvzf ...
%cd ...
%./configure --prefix=/
%make
%su
$make move old
$make install

compile [use '--prefix=' to avoid the problem above], also use 'make moveold' to keep the old tools [so that you can dual boot]

When you boot to your 2.6 kernel, it should use the new tools [and you shouldn't get the QM_Modules problem].

--prefix followed by what? I'm a newbie

The prefix passed to the make file is the base of where the installation goes.

If a program installs to a 'bin' directory, prefix=/ would make it go in /bin
prefix=/usr/local, /usr/local/bin and so on.

If you want the program to bin in /sbin, but it defaults to /usr/local/sbin [as module-init-tools] does, than pass "--prefix=/" to "./configure".

There should be rpm's for major distributions for module-init-tools, which gets rid of this problem.

have you done the ./generate modprobe.conf /etc/modprobe.conf

Mustang...nope I didn't do that.
Why should I?

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 :-)

BIG THANKS to ya all!

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

So, to sum up all the steps:

%tar -jvzf ...
%cd ...
%./configure --prefix=/ <---installing modules in /sbin dir
%make
%su
$make move old
$make install
$ ./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
Thanks.

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....

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

Thanks mustang I'm gonna follow your steps which I suppose gotta be the standard.
To sum up for all the folks having our same troubles:

%tar -jvzf ...
%cd ...
%./configure --prefix=/
%make
%su
$make move old
$make install
$ ./generate modprobe.conf /etc/modprobe.conf

EDIT: I don't understand what - $make move old - do.

good luck. all I can say is that is what worked for me and I got all the info thru the net . marty

I can't compile for this fucking error I don't know where and why it comes from:

gcc -g -O2 -Wunused -Wall -o modinfo modinfo.o zlibsupport.o
gcc -g -O2 -Wunused -Wall -o insmod.static -static insmod.o
/usr//bin/ld: cannot find -lc
collect2: ld returned 1 exit status
make: *** [insmod.static] Error 1


I DO DEFINITIVELY HAVE THE LINKER!!!!!!!!

[giulio@localhost module-init-tools-3.0]$ whereis ld
ld: /usr/bin/ld /usr/share/man/man1/ld.1.bz2


HELP ME!!!!!