Hi, I tried to upgrade my 2.2.17 kernel to 2.4.2. Unfortunately now the system couldn't find any module. I did a 'depmod -a', but for some reason it didn't work... Can it be that the 2.4.* kernel is not working with old (2.2.*) depmod? I noticed that the 2.4.* has a different directory structure in the /lib/modules and when I copied those modules by hand in directories like in 2.2.* I got depmod working properly. I would like to run a 2.4.* kernel because of security issues and also because I would be able to use the PROMISE IDE controller in UltraDMA mode. But it looks like compiling the kernel is not enough this time... Did anyone get into such a problem? Marko P.S.: I am sorry if this is not 100% security related! -- O _ O 0 0 ------------------m-\o/-m------------------------------------------ Dr. Marko K"aning Tel/Fax: +49-3834 554 442 / -3834 554 301 INP Greifswald email : kaening@inp-greifswald.de
On Sun, 20 May 2001, Marko Kaening wrote:
I tried to upgrade my 2.2.17 kernel to 2.4.2. Unfortunately now the system couldn't find any module. I did a 'depmod -a', but for some reason it didn't work... You missed the modutils update, I think (see http://sdb.suse.de/de/sdb/html/new_kernel_71.html, too).
HTH best regards, Rainer Link -- Rainer Link | SuSE - The Linux Experts link@suse.de | Developer of A Mail Virus Scanner (amavis.org) www.suse.de | Founder OpenAntiVirus Project (www.openantivirus.org)
You missed the modutils update, I think (see http://sdb.suse.de/de/sdb/html/new_kernel_71.html, too). Thanks for the hint! The package installs in test mode even on my 6.3 without errors in dependencies... So I'll give it a try at my home comp. I suppose it will work with older kernels too!?!?
Marko
Hi, On Mon, May 21, Marko Kaening wrote:
You missed the modutils update, I think (see http://sdb.suse.de/de/sdb/html/new_kernel_71.html, too). Thanks for the hint! The package installs in test mode even on my 6.3 without errors in dependencies... So I'll give it a try at my home comp. I suppose it will work with older kernels too!?!?
Yes.
Marko -o) Hubert Mantel Goodbye, dots... /\\ _\_v
I had similar problems, and as of now, still try every couple of weekends to figure out the problem to no avail. michael On Sun, 20 May 2001, Marko Kaening wrote:
Hi,
I tried to upgrade my 2.2.17 kernel to 2.4.2. Unfortunately now the system couldn't find any module. I did a 'depmod -a', but for some reason it didn't work...
Can it be that the 2.4.* kernel is not working with old (2.2.*) depmod? I noticed that the 2.4.* has a different directory structure in the /lib/modules and when I copied those modules by hand in directories like in 2.2.* I got depmod working properly.
I would like to run a 2.4.* kernel because of security issues and also because I would be able to use the PROMISE IDE controller in UltraDMA mode. But it looks like compiling the kernel is not enough this time...
Did anyone get into such a problem?
Marko
P.S.: I am sorry if this is not 100% security related!
-- O _ O 0 0 ------------------m-\o/-m------------------------------------------ Dr. Marko K"aning Tel/Fax: +49-3834 554 442 / -3834 554 301 INP Greifswald email : kaening@inp-greifswald.de
--------------------------------------------------------------------- To unsubscribe, e-mail: suse-security-unsubscribe@suse.com For additional commands, e-mail: suse-security-help@suse.com
It's a good idea to to back up the modules.conf and I beleive the rc.config files before making and installing the kernel. And remember to run the "mk_initd" command before running lilo (these are SuSE specific things). Look for the "SuSE" howto on kernel installs. Double check this. The general idea is correct - just make sure the commands and the proper files are backed up in case. On Sunday 20 May 2001 10:34, Marko Kaening wrote:
Hi,
I tried to upgrade my 2.2.17 kernel to 2.4.2. Unfortunately now the system couldn't find any module. I did a 'depmod -a', but for some reason it didn't work...
Can it be that the 2.4.* kernel is not working with old (2.2.*) depmod? I noticed that the 2.4.* has a different directory structure in the /lib/modules and when I copied those modules by hand in directories like in 2.2.* I got depmod working properly.
I would like to run a 2.4.* kernel because of security issues and also because I would be able to use the PROMISE IDE controller in UltraDMA mode. But it looks like compiling the kernel is not enough this time...
Did anyone get into such a problem?
Marko
P.S.: I am sorry if this is not 100% security related!
participants (5)
-
Curtis Rey -
Hubert Mantel -
Marko Kaening -
Michael Chletsos -
Rainer Link