Rmmod kernel driver

Improve this answer. Although you answered your own question, I'm upvoting to help you recover lost bounty points. Thank you for the response.

But I don't want to connect to like that. I just need to unload it from the kernel. Maybe that will work for you. This is accomplished by blacklisting the module: How to blacklist kernel modules? The offending module will no longer be loaded at startup. Sign up or log in Sign up using Google. Sign up using Facebook. Sign up using Email and Password. Post as a guest Name. Email Required, but never shown. Active 5 years, 3 months ago. Viewed times. Improve this question.

GAD3R Walter Walter 1, 2 2 gold badges 11 11 silver badges 30 30 bronze badges. Disable the power management — GAD3R. I checked the wiki and it is disabled by default. Back to the drawing board. Add a comment. Active Oldest Votes. Improve this answer. Kaz Kaz 6, 1 1 gold badge 21 21 silver badges 39 39 bronze badges. Ubuntu Community Ask! Sign up to join this community. The best answers are voted up and rise to the top.

Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 1 year, 11 months ago. Active 2 months ago. Viewed 10k times. Improve this question. Just a stupid idea Add a comment. Active Oldest Votes. Check whether all the interfaces related to your module is not 'up'.

Also read man rmmod. One more thing -- the main problem here is that the number of references to the module, i. Before running the daemon, the reference counter is 0, after the daemon has been launched, the counter goes up to 6, although I'd expect just 3 given that it opens three sockets. So, after killing the damon, the counter goes down to 3, and thus the module can't be unloaded. Are there any ways to catch what other descriptors etc.

Mark - this is a separate question. See this and this.