I'm using Slackware 10.0 with the 2.6.7-kernel from /testing. In rc.modules I've uncommented both the sections on parallel port support and parallel printer support but whenever I boot my computer these modules (parport, parport_pc and lp) don't get loaded. By loading them manually and restarting cups, I could add my printer and that works fine -- till the next reboot. Then the modules aren't loaded, /dev/lp0-device isn't created and the printer doesn't work.

When I run /etc/rc.d/rc.modules from the command line, the output is:

cat: /proc/ksyms: No such file or directory
cat: /proc/ksyms: No such file or directory

Since the first lines in the parallel port- en parallel-printer section are:

if cat /proc/ksyms | grep ... (blablabla)

and /proc/ksyms doesn't exist I was wondering this is the problem? I don't understand why this doesn't work since I have a pretty standard install? Of course I can just add 'modprobe <module>' in rc.modules but I'm wondering why the standard-script doesn't work on my system, and why I don't have /proc/ksyms?

It's has to do with the way rc.modules checks if the modules are ready to load, just simply uncomment the lines that do the command modprobe. (at least that happened to me...)

/proc/ksyms is used with 2.4 series kernels

it is deprecated in 2.6 series, now /proc/kallsyms is used.

I think you could replace the lines in rc.modules accordingly

tobyl

tnx! I've changed it in the scripts to kallsyms but it still doesn't work. Now I've commented all but the /sbin/modprobe <modulename> and it works great. Guess I'll mail slackware about this though, since it's not like Slack not to work right out of the box!

Hi senorsnor,

You are quite right. As was gbonvehi.
Looks like Slackware's rc.modules script is slightly broken with 2.6 kernel.