LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (https://www.linuxquestions.org/questions/slackware-14/)
-   -   Kernel update problems (https://www.linuxquestions.org/questions/slackware-14/kernel-update-problems-90265/)

Sn1PeR 09-07-2003 03:54 PM

Kernel update problems
 
I installed some slackware upgrades(the kernel one too using updatepkg), but it seems to ahve renamed my /lib/modules/2.4.21 folder to /2.4.21-xfs

because of this it is failing to find my network card.... and use modprobe... any help would be great...

How can I fix this? I'm :cry: screwed

edit: Whenever I run modprobe it trys to find the old 2.4.21 folder and spits out an error because it cannot find it....

edit2: I think one of my main problems now is that I don't have my kernel source installed... how would I go about installing it for the 2.4.21-xfs kernel? I can burn it to a cd to get it on there... just point me in the right direction and tell me what to do... I think this might be solved soon. I think I will have to compile a new kernel to fix the problem, but to do this I need to have the kernel source and know how to install that.

marek 09-08-2003 06:52 AM

Hmm situation looks like that:
1) You have got a new modules insted old (i have never seen how package kernel-modules-2.4.21-xfs looks, but it should be very similar to kernel-modules-2.4.20-xfs :D, so you should have each of modules you need (to file system, devices, etc. ) in this package.

But you still have an old /etc/rc.d/rc.modules file. Of course you probably also have a new version of this file (/etc/rc.d/rc.modules.new) but changing this files won't resolve the problem, because both these scripts reference to kernel 2.4.21 (write command -> uname -a , you will see that this is just this version of kernel).

2) Solutions:

- you can rewrite the rc.modules script (instead uname -r write your wersion of kernel, it should works great (the only difference with -xfs version is only patched with xfs supply))
-you can install always source of kernel 2.4.21 (www.kernel.org :) ), compile and install 2.4.21 your own compiled modules

that's all

Ps. If you know everything i wrote, sorry, i don't know on which level you are :)

Sn1PeR 09-08-2003 08:57 PM

-delete-

Sn1PeR 09-08-2003 09:19 PM

When running it with $RELEASE='2.4.21-xfs' (which I beleive is correct) I get the following error: /etc/rc.d/rc.S line 25 =2.4.21-xfs : command not found.... when it says line 25 do I count comments and spaces? I don't see anything refering to $RELEASE...

edit: fixed that problem by removing the $ so it now reads RELEASE='2.4.21-xfs' ... no more errors about that during boot, however, it still says that modprobe cannot open dependancies file /lib/modules/2.4.21/modules.dep

so now I'm really stuck :scratch: :scratch: how do I update modprobe to point to the write place?

marek 09-09-2003 04:03 AM

Linux has a right, because command '2.4.21-xfs' doesn't exist. I'm guessing you have got modules.dep in directory /lib/modules/2.4.21-xfs (it should be there), so exchange every "$Release" (maybe not every, these not after "echo" :) ) in rc.modules on correct directory "2.4.21-xfs". that's all - it must works!!!
But i still suggest you to install kernel (with any version you want) and compile it - it will be great lesson for you. And after compiling of course you should come back to the old version of rc.modules (this before any changes). If you don't know how compile the kernel, it's traditionally
1) make config or make xconfig
2) make dep
3) make clean (is usually useful :) )
4) make bzImage
5) make modules
6) make modules_install

that's all

Ps. of course you have to copy your kernel (let me guess /usr/src/kernel_version/arch/i386/boot/bzImage to /boot
and add correct line to your bootloader


All times are GMT -5. The time now is 03:38 AM.