Disabling the Hardware
Once you have figured out the correct module, you will edit the /etc/modprobe.d/blacklist.conf file. This file may also be called /etc/modprobe.d/blacklist depending on your distribution. The blacklist.conf file is owned by root, so either su to root, or use "sudo gedit" to make any changes. The format for blacklisting a module is "blacklist <module>". For example if I wanted to blacklist the "berry_charge" module, I would add the following two lines to my blacklist.conf file:
#No longer own my blackberry
Once you add an entry to the blacklist.conf file, you must reboot your system for the changes to take effect.
You can also permanently remove the module by using the "rmmod" command. Using the berry_charge example, if I wanted to permanently remove the module I would use the command:
sudo rmmod berry_charge
Some modules depend on other modules, so you may have to follow a dependency trail to actually get the results that you want.
Finally, if the driver is actually compiled into the kernel, you may have some difficulty actually disabling it. Sometimes you can use the /proc and /sys filesystems to disable the hardware. For example, if you want to disable a cpu you would use the following command:
echo 0 >> /sys/devices/system/cpu/cpu1/online
Other times, you will have to use kernel command line arguments.
As you can see, disabling hardware is not a simple "point and click" process in Linux. There may be a time, possibly in the near future, when there will be graphical system. Until then your best bet is to hope your hardware uses a kernel module, and blacklist it.