On Fri, Feb 20, 2009 at 02:39:52PM -0500, Ken Schneider wrote:
Josef Wolf pecked at the keyboard and wrote:
Hello,
I'd like to debug a kernel module. For that, I want to unload the module that was loaded at boot. I remember in the old days, you could simply "modprobe -r modname" to get rid of it. But nowadays, with all this udev/hal/debus/whatever, I am somewhat lost. Here is what I would like to get rid of:
raven:/ # lsmod | egrep '(299|dvb|budget)' stv0299 11280 1 budget_ci 18956 0 budget_core 12332 1 budget_ci dvb_core 87948 3 stv0299,budget_ci,budget_core saa7146 18080 2 budget_ci,budget_core ttpci_eeprom 2520 1 budget_core ir_common 43340 1 budget_ci i2c_core 35280 5 stv0299,budget_ci,budget_core,ttpci_eeprom,i2c_piix4 raven:/ #
See the use-count of stv0299? How do I find out which component uses it and how do I get rid of it?
First you need to rmmod the modules used in other modules i.e.
rmmod budget_ci before you rmmod budget_core
OK, that helps. Thanks Ken! But I still don't understand why the dependency is not listed for the stv0299 module? And how would I find out (without asking the net) that budget_ci is the module that keeps stv0299 from being released? -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org