Hi,

On my Centos system, this is my nvme driver:

/lib/modules/3.16.0-38-generic/kernel/drivers/block/nvme.ko

When system boots this driver gets loaded automatically. Running lsmod shows that this driver is loaded and using modprobe -r or rmmod I can unload the driver.

I deleted this driver file and rebooted the system but the driver still loads! lsmod detects the driver and I can unload the driver. modinfo nvme says it cant find /lib/modules/3.16.0-38-generic/kernel/drivers/block/nvme.ko.

find / -name nvme.ko does not find any nvme driver on the system.

I know I can add the driver to the blacklist so it wont load, but what I want to know is where on earth is Linux loading the driver from?

TIA
Nisha

Is 3.16.0-38-generic the kernel version reported by "uname -r"?

You can (and often do) have multiple kernel versions installed as you update and it preserves earlier kernels in grub and in /lib/modules to allow you to boot from older kernel (especially after an upgrade). The /lib/modules subdirectory used is the one that matches the kernel release you're booting.

correct, that is the kernel version reported by uname -r.

The fact that I'm able to unload the driver (and also that lsmod reports it) confirms that the driver is not built into the kernel. Therefor it follows that modprobe looks for the driver in /lib/modules/`uname -r` but its not there!

BTW this thread was double posted by mistake.

Nisha

Is it built into ramfs?