SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm having trouble loading a module at startup. it's the lp module. parport and parport_pc load. When
I modprobe lp it loads and I can then print.
Now, back in the olden days, all I'd do is edit rc.modules and all would be fine. However rc.modules appears to be deprecated (indeed, I don't have one) and I'm under the impression that one is to use udev.
udev seems hellish complicated for getting a parallel printer to run. ISTR tackling it before to get my scsi scanner to work and it wasn't a nice experience.
So, should I just create an rc.modules script or put it in rc.local or could some kind soul let me know what the udev rule should look like please?
If you installed a kernel-modules package in Slackware 12.2, you should have a file /etc/rc.d/rc.modules. It is a symbolic link to another file in the same directory called rc.modules-<something>.
So all you have to do is uncomment the relevant lines. Of course you need to chmod +x /etc/rc.d/rc.modules*
Hmm. Perhaps I missed that day in school, but my 12.2 setup has an rc.modules file. Actually, rc.modules is soft link to rc.modules-2.6.27.7-smp. I also have an rc.modules-2.6.27.7 file.
The rc.modules files are installed from the a/kernel-modules-smp-2.6.27.7_smp-i686-1 and a/kernel-modules-2.6.27.7-i486-1 packages. Perhaps try reinstalling those packages.
From within those rc.modules files, I still enable the lp kernel module. Just like previously, delete the comment hash mark and ensure the rc.modules file is executable.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.