Hello,

there's an specific error I encounter while working on 2.4.20 kernel with "module-init-tools-0.9.15-pre4" which I installed, since this packet was on the "Changes" list in Kernel's 2.6.4 Documentation. The problem is that my modules won't load anymore when my system (RH9) starts up.

In the install guide of these tools they say that I have to backup my old modprobe file if I want module-init-tools required for kernel 2.6.4 to work fine with kernel 2.4.x.

And so I did, typing:

./configure --prefix=/
make moveold
make
make install

and then:

./generate-modprobe.conf /etc/modprobe.conf

Unfortunately I didn't know it had already been done by my brother once before and now, although these "tools" are installed correctly and work fine with Kernel 2.6.4 - modules won't load anymore with the system startup on Kernel 2.4.x. The system says that the file /sbin/modprobe.old is not an old version ("I am not an old version!") and modules won't load.

What can I do to fix this thing? Forcing installation of old module-init-tools-0.9.7 did't change the situation and even made it worse - none of my two kernels could load any modules.

I'll be grateful for any help, because I'm still a and can't fix this myself.


Thanx in advance, friends


rosol11

This solution will probably work if you are installing module-init-tools as rpm packages.

You can find out where each of the module-init-tools rpm packages install their files with:
rpm -qlp /pathname/packagename

Once you know what files are duplicate in the two packages then you can install the old module-init-tools rpm package, rename the duplicate files to file.old and then install the new module-init-tools rpm.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

Thanx for the reply, Steve


I tried to apply what You said and here's what I did:

1. I checked the locations where all contents of the module-init-tools are installed.

2. I switched to kernel 2.4.20-8

3. I enetered the directory where my module init tools were extracted from an gz archive and typed:

make clean
make uninstall

4. After that I typed:

depmod -V

to check the version of the tools and the system said that this command was uknknown which led me to believe there were no module-init-tools installed on my system.

5. Meanwhile I downloaded module-init-tools-0.9.15-pre4.tar.bz and unzipped them .

6. I tried to install old 0.9.9 module-init-tools by typing:

./configure --prefix=/
make
make install


7. I typed: depmod -V and the system correctly displayed the current version of the tools (0.9.9). The problem was that there were no *.old files while installing these module init tools, as there weren't any tools at all. So I changed the names of the files: insmod, modprobe, rmmod, lsmod, depmod to corresponding *.old and put them in /sbin, leaving the originals untouched. But the files and their *.old versions had of course the same content but different extensions.



8. What's the use of typing

depmod [kernel version]

which is stated in README file included in module-init-tools? And what does the command "./generate-modprobe.conf /etc/modules.conf" do?

9. The point is that when having installed module-init-tools-0.9.15-pre4 using:

./configure --prefix=/
make
make install

my kernel 2.6.4 works fine, but kernel 2.4.20-8 has still the same problems: it screams "I am not the old version!"


I am a newbie with linux but I learn fast because it inspires me somehow. However, I need Your help this time....


Thanx in advance


rosol11

"I tried to apply what You said "

You are using Red Hat so I assumed that you were installing the old 0.9.9 module-init-tools using the rpm program. Since you were installing the old 0.9.9 module-init-tools by compiling it from source then my instructions don't make any sense. Sorry, so I'll try again.

I think that the way to solve this problem is to install the old 0.9.9 module-init-tools. Then find out where the old 0.9.9 module-init-tools were installed. Rename the old 0.9.9 module-init-tools to such names as /bin/modprobe.old. Previously you tried changing insmod, modprobe, rmmod, lsmod, depmod to corresponding *.old and put them in /sbin. I suggest that you try it again. Then install the new module-init-tools-0.9.15-pre4.tar.bz

I have a way to know exactly what files the old 0.9.9 module-init-tools installs but it is complicated. If insmod, modprobe, rmmod, lsmod, depmod are not enough then I will explain the complicated way to find out exactly what is installed.

"8. What's the use of typing

depmod [kernel version]"

depmod creates a list of loadable modules to be loaded with the bootable kernel at boot time. The list will be different for different kernel versions.

"And what does the command "./generate-modprobe.conf /etc/modules.conf" do?"

I am not sure but I would guess that it generates a /etc/modules.conf file. The /etc/modules.conf file probably is the same for the two kernels. I have never had to change one when compiling a new kernel other than to comment out entries that I no longer needed but it is possible that the two kernels need two different /etc/modules.conf.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

Thanx fo the quick reply, Steve


You are right - i installed mod-init-tools from the source because it's damn hard to get old module-init-tools in rpm package. If You knew any link to obtain these RPMs I'd be grateful.

Anyway i switched to kernel 2.4.20-8 and again uninstalled all the tools. Then i installed old tools by typing:

./configure --prefix=/
make
make install

and then renamed these 5 files You mentioned into the corresponding *.old versions. I didn't type "depmod 2.4.20-8 - should I have?

This was all I did about the old tools. Is this correct? "Depmod -V" shows 0.9.9 version so it's correctly installed.

But when I install module-init-tools-0.9.15-pre4 in THE SAME way:

./configure --prefix=/
make
make install

and then type "lsmod" it still says: "I am not the old version!". And still after rebooting the system on kernel 2.4 it doesn't mount either vfat file system or my network card correctly.


This whole problem is slowly driving me mad, but I'am counting on You. If You could please write a simple "step by step" instruction how to fix the problem - i mean mainly the commands which I should type - I'd be really grateful. I should add that You've helped me a lot so far - just only by replying my post

"and then type "lsmod" it still says: "I am not the old version!"."

I think that you need to run lsmod.old. When you want to use the old commands use the .old extension now that you have the old versions named *.old.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

Typing "lsmod.old" won't do a lot, neither does any other *.old command. Any *.old command i type gives the warning: "I am not the old version!"


I thing there's smthn wrong with my System.map file, therefore I tried to do the following:

I switched to kernel 2.4 and uninstalled all module-init-tools. There's something wrong with "locate" command - even if I remove some files it still shows that they are present - maybe typing "locate <filename>" in not enough....


Anyway I installed "module-init-tools-3.0-pre4" - there's besides a problem i can't understand: if I type :

./configure --prefix=/
make
make install

everything is all right - typing "depmod -V" shows the current version of the tools. But when instead I type:

./configure
make
make install

then BASH says it doesn't know any of the commands "modprobe, lsmod etc..." I think I should add them somehow.... but don't know how.

I think that maybe I install these tools in wrong directory - maybe new files collide with the old ones somehow, I don't know...

After installing typing "depmod" (or depmod.old) should update System.old, but I don't know whethet it does or not. But the fact is that having do so, typing any of "insmod, lsmod, modprobe, rmmod" or their *.old versions still gives the same warnings, still doesn't the system recognize either my ethernet controller or vfat filesystem.

I'm sick of it all. I'll probably reinstall the system and get rid of this tiring error. Thank You for all the advice You have given me, friend. CU online anyway



PS. How can I re-configurate my mouse as I have changed it to 2-button without scroll and I can't handle the cursor in KDE anymore?

"How can I re-configurate my mouse as I have changed it to 2-button without scroll and I can't handle the cursor in KDE anymore?"

I think that you do it by logging in as root and running redhat-config-mouse.

___________________________________
Be prepared. Create a LifeBoat CD.
http://users.rcn.com/srstites/LifeBo...home.page.html

Steve Stites

Thanx for Your advice - my mouse runs smoothly now


As about the damn module init tools: I fixed the problem Kernel 2.4 and 2.6 runs without ANY errors now, this is what I did:

I uninstalled an rpm "modutils 2.4.22" from the system - this was very important! Then I installed newer "modutils 2.4.27" from an rpm, of course previously uninstalling any module-init-tools that ever existed. Having done so, I installed "module-init-tools-0.9.15 pre4" in the following way:

./configure --prefix=/
make moveold
make
make install
./generate_modprobe.conf /etc/modprobe.conf
depmod
depmod 2.6.4

And since than kernel 2.4 has been running perfectly. I partially got know how this module thing works - kernels 2.6.x use modprobe.conf instead of modules.conf file. "./generate_modprobe.conf /etc/modprobe.conf" converts options from modules.conf into modprobe.conf.

There's was however a problem with kernel 2.6 - when the init script starts, it shows errors (a few FAILED labels) referring to USB saying that it can't find any modules which handle e.g. usb-uhci, which is incorrect because I installed these modules when recompiling the 2.6.4 kernel. I got know that usb-uhci module has had their name changed in kernel 2.6 – I easily changed that in aliases in modprobe.conf.

There were also problems with keybdev and mousdev modules which wouldn’t like to load properly. Reading the Forum I encountered the following solution which happened to work:

/etc/rc.d/rc.sysinit @ line 207:
needusbstorage= <-- line 203
if [ $usb = "1" ]; then
needusbstorage=`LC_ALL=C grep -e "^I.*Cls=08" /proc/bus/usb/devices 2>/dev/null`
LC_ALL=C fgrep 'hid' /proc/bus/usb/drivers || action $"Initializing USB HID interface: " modprobe hid 2> /dev/null
if [ `uname -r | awk 'BEGIN {FS = "."};{print $2}'` -lt 6 ]; then
action $"Initializing USB keyboard: " modprobe keybdev 2> /dev/null
action $"Initializing USB mouse: " modprobe mousedev 2> /dev/null
fi
fi


Now everything goes well – the end of “module-init-tools” nightmare Thanx again, Steve. CU online.