Remove a manually installed driver (wireless usb) But probably you'll need to unload the module before. You can use lsmod command to see currently loaded modules and rmmod to unload a module for the current session (it would be loaded again on next boot), names from lsmod doesn't always correspond to filenames.
I am developing a Windows C++ application that drives a motor controller that is plugged on USB.This controller relies on Ftdibus drivers and it works fine on my PC.However, on a test computer it used to work but since I messed up with the Ftdi drivers as soon as I plug the controller, I get a BSoD (mentioning Ftdibus).I would like to cleanup the drivers, but:
- they do not appear in Windows 'uninstall programs'
- I can't right click on the controller in the device manager and chose 'uninstall' because I can't plug the controller (BSoD)
- I tried nirsoft tool that has an option to uninstall devices but it won't work
I'm clueless, how could I clean up that mess?
Select Control panel. Click on network and sharing center. At the left top corner click on Change adapter settings. There you will be able to see the Driver name of the network Adapter next to the Icon. Then you can go to device manager and check for that network adapter and you can uninstall the driver. Nov 20, 2013 Where can I find my network drivers so that I can uninstall then reinstall them? 0 smorizio Titan. Jan 22, 2010 30,968 0 137,460 5,699. Is it the adapter or ethernet controller? Refmon Honorable. Dec 27, 2012 264 0 10,780 0. Nov 20, 2013 #4 I don't know which one it is. 0 Tradesman1 Titan. There will be a box that says 'Remove driver software' - check this box and Uninstall the driver. This should remove it from the driver store and uninstall the device from the registry. If all drivers for the device has been removed you should be able to plug it in and see that no driver loads for the device.
PS: if anyone has documentation regarding how drivers are bound to an USB port number, I would enjoy reading on the subject
Julien M
Julien MJulien M
2 Answers
If this is Vista and later, the supported method for deleting a driver package is with pnputil:
Just deleting the service is sort of a bad idea, that's not the only thing that installing a driver puts in the registry.
I missed the second part of your post about how Windows binds drivers to USB devices. There's a nice description of it here:
If you need more details feel free to contact me (I specialize in Windows drivers for a living :))
snoonesnoone
How I do it is one of three ways:
- Go into Device Manager, select 'view' menu and select the 'Show hidden devices'. Find your device description and select the 'uninstall' menu option. [easy]
- You can use the Service Control Manager command line 'SC' to delete the device driver from the registry. You will need to know the installed driver name. [medium]
- Manually delete the driver setup in the registry. Using regedit, you can delete the registry entries for the driver. Drivers registry setup lives under 'HKEY_LOCAL_MACHINESYSTEMCurrentControlSetservices'. Find the driver name key and delete it. [hard]
Shane PowellShane Powell
Not the answer you're looking for? Browse other questions tagged windowshardwareuninstalldrivers or ask your own question.
I downloaded and installed a driver for my wireless usb dongle as it wasn't detected by linux (KDE). I wasn't very sure which model it was but apparently it is a Ralink RT2870 (Brand name IPTime N150UA).I downloaded the driver, patched a file to make it compatible with my new kernel version (3 and above) following this page and finally installed it like shown in the page.Then My wifi dongle was detected and I could connect to the network. The problem is, as soon as I do ssh or open the router's webpage my whole computer freezes and I have to shut it down.Now I want to delete this driver, I searched on internet but couldn't find anything helpful. When I run lshw I get for my wireless driver:
description: Wireless interface
physical id: 1
logical name: ra0
serial: 64:e5:99:f6:33:60
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=RALINK WLAN ip=192.168.1.8 multicast=yes wireless=Ralink STA
physical id: 1
logical name: ra0
serial: 64:e5:99:f6:33:60
capabilities: ethernet physical wireless
configuration: broadcast=yes driver=RALINK WLAN ip=192.168.1.8 multicast=yes wireless=Ralink STA
That is a very weird driver name with a space in the middle. I can't even follow some tutorials about how to get more information about a driver because when I input RALINK WLAN it thinks it is two different driver names.What should I do?
MehdiMehdi
2 Answers
According to your link the filename of the driver should be
mt7601Usta.ko
(.ko
is the extension for kernel modules).Kernel modules are usually installed in
/lib/modules/$(uname -r)
, so use find /lib/modules/$(uname -r) -name mt7601Usta.ko
then sudo rm
to delete it if you're sure it is the right module (or mv
to move it out from the modules tree so it won't be loaded on next boot).But probably you'll need to unload the module before.
You can use
lsmod
command to see currently loaded modules and rmmod
to unload a module for the current session (it would be loaded again on next boot), names from lsmod
doesn't always correspond to filenames.With
lsmod
results you can use modinfo
command to get informations about the module (ie: modinfo <modulename>
)Depending on the distro you're using you may be able to blacklist adding a line in
/etc/modprobe.d/blacklist.conf
so it won't be loaded on bootAdd a new file if
blacklist.conf
doesn't existYou can also blacklist it from the kernel command line (ie: grub bootloader)
AlexAlex
Look in the 'Makefile' of the driver source you downloaded. It will have a block named 'install', which will look something like this:
If you typed
make some_keyword
to install the driver, look for the block starting with 'some_keyword' instead of 'install'The commands in this block were executed when you typed
make install
and then entered your password. This block will have some commands which moved the driver files from the compilation directory to some other directories, most probably to somewhere in '/usr/lib' find those commands and delete all the mentioned files.You can execute
grep 'mv ' Makefile'
to easily find those commands. This although assumes that the makefile is named 'Makefile', not 'makefile' or something else.The point is that the commands which actually modified your system were in the install block of the makefile, the one for which you had to give root permission. All the rest are compilation instructions.
Network Controller Driver Linksys
sagasaga