Removing a kernel module Aggressively
by LongtimeListener from LinuxQuestions.org on (#525M1)
my aim: to find peace
my question, when there's a module, let's call it "nouveau", that is shipped with a distro and is installed by the installer, what are the steps one might take to remove all trace of nouveau as if it had never been present? Assume that the module is "in use" already when booting in level 3.
background:
I have tried google, I've tried modprobe. tried configuring modprobe, tried edit to loader invocation line. tried removing the package through the package browser. mind, this was only to stop the module, not to destroy it. now it seems that I have no choice but to destroy it. don't take this as a sign of arrogance, but I'm not interested in all the other linux questions. as of now, I want to destroy nouveau - I mean, my unspecified module - leaving everything around it intact and working (hopefully) good. that's why I come before you. maybe this will enlighten me about the workings of a linux system in general. almost certainly it will arm me for the next time a module stands between me and computing bliss. so help me brothers and sisters. if I have to go to where this module lives and dd it, byte by byte, let me have that one win.
my question, when there's a module, let's call it "nouveau", that is shipped with a distro and is installed by the installer, what are the steps one might take to remove all trace of nouveau as if it had never been present? Assume that the module is "in use" already when booting in level 3.
background:
I have tried google, I've tried modprobe. tried configuring modprobe, tried edit to loader invocation line. tried removing the package through the package browser. mind, this was only to stop the module, not to destroy it. now it seems that I have no choice but to destroy it. don't take this as a sign of arrogance, but I'm not interested in all the other linux questions. as of now, I want to destroy nouveau - I mean, my unspecified module - leaving everything around it intact and working (hopefully) good. that's why I come before you. maybe this will enlighten me about the workings of a linux system in general. almost certainly it will arm me for the next time a module stands between me and computing bliss. so help me brothers and sisters. if I have to go to where this module lives and dd it, byte by byte, let me have that one win.