LinuxQuestions.org
Visit the LQ Articles and Editorials section
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Software
User Name
Password
Linux - Software This 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.

Notices

Reply
 
Search this Thread
Old 05-16-2004, 05:22 AM   #1
positiveinflux
LQ Newbie
 
Registered: Apr 2004
Location: philadelphia
Distribution: redhat 9
Posts: 9

Rep: Reputation: 0
module-init-tools refuses to install properly


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
 
Old 05-16-2004, 12:05 PM   #2
jmorse
Member
 
Registered: Mar 2004
Location: United Kingdom
Distribution: LFS
Posts: 74

Rep: Reputation: 15
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'
 
Old 05-17-2004, 06:27 AM   #3
positiveinflux
LQ Newbie
 
Registered: Apr 2004
Location: philadelphia
Distribution: redhat 9
Posts: 9

Original Poster
Rep: Reputation: 0
ehhhh

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
 
Old 05-17-2004, 08:51 AM   #4
fenice1976
Member
 
Registered: May 2004
Distribution: MDK 9.2 - Kernel 2.4.22mdk
Posts: 108

Rep: Reputation: 15
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! :-)
 
Old 05-17-2004, 09:06 AM   #5
jmorse
Member
 
Registered: Mar 2004
Location: United Kingdom
Distribution: LFS
Posts: 74

Rep: Reputation: 15
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].

Last edited by jmorse; 05-17-2004 at 09:09 AM.
 
Old 05-17-2004, 09:12 AM   #6
fenice1976
Member
 
Registered: May 2004
Distribution: MDK 9.2 - Kernel 2.4.22mdk
Posts: 108

Rep: Reputation: 15
--prefix followed by what? I'm a newbie
 
Old 05-17-2004, 09:17 AM   #7
jmorse
Member
 
Registered: Mar 2004
Location: United Kingdom
Distribution: LFS
Posts: 74

Rep: Reputation: 15
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.
 
Old 05-17-2004, 10:35 AM   #8
mustang335
LQ Newbie
 
Registered: Mar 2004
Location: coventry, connecticut, usa
Distribution: Puppy 5.6.1
Posts: 27

Rep: Reputation: 15
have you done the ./generate modprobe.conf /etc/modprobe.conf
 
Old 05-17-2004, 12:33 PM   #9
fenice1976
Member
 
Registered: May 2004
Distribution: MDK 9.2 - Kernel 2.4.22mdk
Posts: 108

Rep: Reputation: 15
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!
 
Old 05-17-2004, 01:00 PM   #10
mustang335
LQ Newbie
 
Registered: Mar 2004
Location: coventry, connecticut, usa
Distribution: Puppy 5.6.1
Posts: 27

Rep: Reputation: 15
module-init-tools

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
 
Old 05-17-2004, 01:48 PM   #11
fenice1976
Member
 
Registered: May 2004
Distribution: MDK 9.2 - Kernel 2.4.22mdk
Posts: 108

Rep: Reputation: 15
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....

Last edited by fenice1976; 05-17-2004 at 02:38 PM.
 
Old 05-17-2004, 04:15 PM   #12
mustang335
LQ Newbie
 
Registered: Mar 2004
Location: coventry, connecticut, usa
Distribution: Puppy 5.6.1
Posts: 27

Rep: Reputation: 15
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
 
Old 05-17-2004, 04:27 PM   #13
fenice1976
Member
 
Registered: May 2004
Distribution: MDK 9.2 - Kernel 2.4.22mdk
Posts: 108

Rep: Reputation: 15
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.

Last edited by fenice1976; 05-17-2004 at 04:29 PM.
 
Old 05-17-2004, 04:30 PM   #14
mustang335
LQ Newbie
 
Registered: Mar 2004
Location: coventry, connecticut, usa
Distribution: Puppy 5.6.1
Posts: 27

Rep: Reputation: 15
good luck. all I can say is that is what worked for me and I got all the info thru the net . marty
 
Old 05-17-2004, 04:51 PM   #15
fenice1976
Member
 
Registered: May 2004
Distribution: MDK 9.2 - Kernel 2.4.22mdk
Posts: 108

Rep: Reputation: 15
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!!!!!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
module-init-tools install failed taoweijia Linux - General 4 02-01-2005 09:33 PM
module-init-tools fenice1976 Linux - Software 29 06-09-2004 11:45 AM
module-init-tools ? kam_kenneth Linux - Newbie 1 05-07-2004 09:40 AM
Question about when to install module-init-tools beejayzed Linux - Newbie 11 02-03-2004 05:11 PM
problem with modules install after installing module-init-tools fobius Linux - Software 4 02-01-2004 04:40 PM


All times are GMT -5. The time now is 11:05 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration