How to disable unused device without blacklisting a module
Hello,
Does anyone know a general way of disabling a device without blacklisting a module/driver? The reason I am asking this is that I have two webcams (one built-in, one external) and I want to permanently disable the built-in one. Blacklisting a module is not an option cause both webcams use the same driver (uvcvideo, if that makes a difference)... I was trying to find a way to do that using udev rule(s) but no luck so far. Crossposted a week ago on askubuntu: http://askubuntu.com/questions/18970...n-external-one Thanks, Alikasundara |
Have you looked in the BIOS to see if you can disable it there? If you can, then the OS won't see the device at all.
|
Quote:
Thanks, Alikasundara |
This blogger wrote a udev rule to switch which one was primary...
http://windywindycitytech.wordpress....-linux-ubuntu/ You could do something similar, just not enable the one at all... However, what about the BIOS? Many built in cameras can be disabled in the BIOS settings... |
Quote:
Quote:
Thanks, Alikasundara |
You might look into unplugging the web cam. Most manufacturers have doc on how to remove and replace parts. If you are handy, and have some physical kill, you may be able to simply unplug the device.
|
Quote:
If a device is not properly defined by the system's udev rules,... and cannot be found, it doesn't exist as far as the system is concerned. Unuseable. It's just an unknown device... Only someone with root access would be able to fix it... Short of physically removing it, only cutting power to it will "completely" disable it,... and that's a (missing) BIOS function. |
Quote:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="5986", ATTRS{idProduct}=="0361" Thank you! |
Start by commenting it out... the # in the beginning of it's line...
|
Quote:
|
Quote:
It just seems unbelivable to me that there is no easy way to disable a particular device on OS level. |
Are you sure that there is no udev rule regarding this camera? Did you check within the /etc/udev/rules.d/ directory? They might just ID the camera by vendor...
I'm not sure how uvcvideo works, but I would assume that udev has to ID the device first, before it just starts using it... uvcvideo is part of the v4l2 subsystem, ... and one would assume that this device is getting assigned to something like /dev/video0 or something ... |
Quote:
Quote:
Thanks, Alikasundara |
That just doesn't sound right...
What about in... /usr/lib/udev/rules.d ??? My understanding was that udevadm handled all the /dev namings... ?!?! But then again, I don't know whether the udev developers even fully understand udev... |
Alright,... Following up my own post...
See here,... http://content.hccfl.edu/pollock/AUnix1/udev-info.htm Third paragraph,... I suppose it is possible for the driver to produce its own dev namings... So, there's either a rule in one of the rules.d directories, or there's a listing in the driver's data file for the major and minor device node numbers, or the UVC driver is doing it directly. If it's the two former scenarios, you need to edit those files. If it's the latter, you either patch UVC to NOT pick up that device, or you're S-O-L, unfortunately. |
All times are GMT -5. The time now is 04:37 AM. |