Question

1

How do I prevent the lp module from loading on boot?

rated 0 times [ 1] [ 0] / answers: 1 / hits: 10478 / 2 Years ago, mon, february 28, 2022, 3:00:06

I use some software under a VMWare VM that needs to access the parallel port. If the lp kernel module is loaded, VMWare's Player can't access the port. I need to unload the module every time I want to use it under my virtual machine, and since I never use it under Ubuntu itself, it'd be nice if it was just not loaded by default.

I've tried adding blacklist lp to /etc/modprobe.d/blacklist.conf and running sudo update-initramfs -k all -u, but lsmod shows that it's still loaded after I boot. How can I keep the module from being loaded? I'm using Ubuntu 11.10 with the 3.0.0-x kernels from the kernel team PPA.

Answers

Only authorized users can answer the question. Please sign in first, or register a free account.

enincroscope

Add To Favorites

Follow

Total Points: 252

Total Questions: 124

Total Answers: 104

Location: Tajikistan

Member since Thu, Apr 14, 2022

2 Years ago

enincroscope questions

1 Ubuntu 22.04 how to install Nvidia drivers and Cuda for GeForce GTX 1650 Mobile

Tue, Dec 21, 21, 22:46, 2 Years ago

1 firefox window in always on top mode

Thu, Jan 20, 22, 08:33, 2 Years ago

1 How to disable on-screen keyboard when using touchscreen

Thu, Apr 7, 22, 01:09, 2 Years ago

1 What is the size of Gnome's top bar?

Mon, May 16, 22, 09:08, 2 Years ago

1 Nvidia-driver not working on ubuntu 20.04 with 5.15.0-051500rc6 kernel

Sat, Apr 2, 22, 05:35, 2 Years ago

View All

answered 2 Years ago farnic · Accepted Answer

How can I keep the module from being loaded?

lp is built into the kernel, so blacklisting it won't work. The simple solution is to do rmmod lp to unload it once logged in. You can automate this by making an init script, or just putting this in your .bashrc -- use rmmod lp 2>nul so that if the module is already unloaded, it won't clutter your screen with an error.

I'm using Ubuntu 11.10 with the 3.0.0-x kernels from the kernel team PPA.

The long-term solution is to simply remove the module from the kernel, which of course requires building a custom kernel. Please see this community help page for more information on how to do this, if you choose to go this way.