| View previous topic :: View next topic |
| Author |
Message |
dongfangxunlei
n00b
Joined: 30 Jan 2013
Posts: 40
|
 Posted: Sun Jan 05, 2014 3:14 am Post subject: loop.ko cannot insmod automatically in kernel 3.13-rc |
 |
|
I am not sure from which kernel version this problem has occured.
Is this a new kernel feature?  |
|
| Back to top |
|
 |
Kompi
Apprentice
Joined: 05 Oct 2002
Posts: 252
Location: Germany
|
| Posted: Sun Jan 05, 2014 5:15 am Post subject: |
|
|
No, it is not very new. It is the module necessary for so called loop-devces. A loop device is a block device node called /dev/loopX that used a file as its storage backend. For example, if you mount a an .iso file, it will be first set up as a loop device and then mounted, as if it was a real device like a /dev/sdXX or /dev/srX node.
If the module cannot be loaded, check if you have compiled it in the kernel:
| Code: | cd /usr/src/linux
cat .config | grep CONFIG_BLK_DEV_LOOP
|
should output a line like this:
| Quote: | | CONFIG_BLK_DEV_LOOP=y |
If it is set to y, it is not compiled as a module but part of the kernel. In that case, you don't need to load it as a module. If it is set to "m" it should be possible to load it. If it is set to "n" you need to change it:
you find the option at: Device Drivers --> Block devices --> Loopback device support
If this option is already set as a module, the modules were somehow not installed correctly. Try running
| Code: | | make modules_install |
again. |
|
| Back to top |
|
|
krinn
Watchman
Joined: 02 May 2003
Posts: 7470
|
| Posted: Sun Jan 05, 2014 6:41 am Post subject: |
|
|
| Just use modprobe instead of insmod. |
|
| Back to top |
|
|
|
Kernel & Hardware
