-   Slackware (
-   -   slackware boot up question (

Murkhadh 02-16-2007 09:53 PM

slackware boot up question
I just noticed when my slackware 11.0 is booting up

there is a line that reads:
running /etc/rc.d/rc.modules -> rc.modules-

I'm curious why it points to the modules

I installed kernel 2.6.18 from the CD and then later upgraded to 2.6.20 was never installed, Why does it say that?

H_TeXMeX_H 02-16-2007 10:57 PM

Well fix it. It's in '/etc/rc.d', symlink 'rc.modules' to 'rc.modules-`uname -r`'.

allend 02-17-2007 02:18 AM

Are you sure that you have installed the 2.6 kernel correctly?
After installing the 2.6 kernel, there is a symlink /etc/rc.d/rc.modules that points to /etc/rc.d/rc.modules-, which I suggest you change to point to your new rc.modules-2.6. This is because when you installed Slack, you must have chosen a kernel image on the install CD that was based on

However, when booting Slack, the boot scripts check the kernel version and use the appropriate rc.modules.
If you are seeing this message at boot, it may indicate a problem.
Did you also install 2.6 kernel modules when you installed the kernel?

Murkhadh 02-17-2007 09:32 AM

Well I can't honestly say that I'm sure I installed it right. This is my first run at intalling a kernel.

I did do the make modules_install so I thought I installed the modules right but its starting to sound like i didn't

Murkhadh 02-17-2007 10:32 AM

More info

When I look in the /etc/rc.d folder for that symlink

the symlink points to a script titeld rc.modules-

there is also a script for rc.modules-2.6.18

but there isn't a script for the kernel I actually use (2.6.20)

H_TeXMeX_H 02-17-2007 11:40 AM

Link it to 'rc.modules-2.6.18'.

ryanoa 02-17-2007 01:59 PM

I had the same situation after I compiled I just made a copy of rc.modules-2.6.18 and renamed it to rc.modules- I haven't had any problems yet :) On boot it always looks for rc.modules-uname -r first.

All times are GMT -5. The time now is 04:07 PM.