LinuxQuestions.org - [SOLVED] HELP - 14.1 upgrade from 14.0 with slackpkg kernel-module links to wrong kernel?

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - HELP - 14.1 upgrade from 14.0 with slackpkg kernel-module links to wrong kernel? (https://www.linuxquestions.org/questions/slackware-14/help-14-1-upgrade-from-14-0-with-slackpkg-kernel-module-links-to-wrong-kernel-4175486889/)

HELP - 14.1 upgrade from 14.0 with slackpkg kernel-module links to wrong kernel?

I used Alien Bob's slackpkg upgrade process to upgrade from Slackware 14.0 full install to Slackware 14.1. I'm having a wireless problem which might be related to this observation that I have. If I look at the rc.modules link it points to the 3.2.29 kernel-module rather than 3.10.17 kernel-module. Is that normal or is it a misstep when using slackpkg as the upgrade process rather than a full install? Do I simply issue a new ln statement to correct it, or is it something that LILO.conf is suppose to handle? If rc.modules isn't related to wireless issues then I post a separate issue to try and address that. If more information is needed, please feel free to ask. Happy Slacking, BAmunds

delete old /etc/rc.d/rc.modules-3.2.29 link and ln new one

Might be better to ask separate question regarding wireless as in posting result of lspci and looking into what wicd and networkmanager do.

Quote:

Originally Posted by glorsplitz (Post 5075583)

delete old /etc/rc.d/rc.modules-3.2.29 link and ln new one.

Thanks for the reply. I knew that a new link was necessary. What I didn't know is if LILO or something else makes this link automatically when you have multiple kernels installed. For example I have left the 3.2.29 kernel inplace as a fallback, along with vmlinuz. Is that a problem?

Quote:

Originally Posted by glarsplitz (Post 5075583)

Might be better to ask separate question regarding wireless as in posting result of lspci and looking into what wicd and networkmanager do.

I was planning to ask a separate question on the wireless, but wanted to get this kernel modules issue straightened out first, because if it isn't right then it could potentially cause a problem with wireless module loading.

Environment: HP Pavilion zv5000 with 512M and 60G HDD, Broadcom b43 driver added from slackpkgs. Slackware 14.1

We can see in /etc/rc.d/rc.S this:

Code:

# Priority is given first to a script named "rc.modules.local", then

# to "rc.modules-$FULL_KERNEL_VERSION", and finally to the plain "rc.modules".

# Note that if /etc/rc.d/rc.modules.local is found, then that will be the ONLY

# rc.modules script the machine will run, so make sure it has everything in

# it that you need.

if [ -x /etc/rc.d/rc.modules.local -a -r /proc/modules ]; then

  echo "Running /etc/rc.d/rc.modules.local:"

  /bin/sh /etc/rc.d/rc.modules.local

elif [ -x /etc/rc.d/rc.modules-$(uname -r) -a -r /proc/modules ]; then

  echo "Running /etc/rc.d/rc.modules-$(uname -r):"

  . /etc/rc.d/rc.modules-$(uname -r)

elif [ -x /etc/rc.d/rc.modules -a -r /proc/modules -a -L /etc/rc.d/rc.modules ]; then

  echo "Running /etc/rc.d/rc.modules -> $(readlink /etc/rc.d/rc.modules):"

  . /etc/rc.d/rc.modules

elif [ -x /etc/rc.d/rc.modules -a -r /proc/modules ]; then

  echo "Running /etc/rc.d/rc.modules:"

  . /etc/rc.d/rc.modules

fi

So target of rc.modules symlink doesn't matter until /etc/rc.d/rc.modules-$(uname -r) is in place.

Thanks Bormant. I suspected that there was more at play. So I guess I don't need to wonder if the right kernel modules are being loaded. I can now go ask another thread about why wlan0 is failing to gain it's IP address until I run /etc/rc.d/rc.inet1 manually. I did some poking around in the the log's and I don't see anyplace that the rc.S process is being logged. Is there a log that would show this without turning on debug?