New answers tagged kernel-modules
You can use the unbind interface in sysfs. Please refer to this article for details. You will find instructions for automating the unbind upon discovery of the device in this answer.
Kees Cook implemented a sysctl to fill this need in early 2009. As documented in Documentation/sysctl/kernel.txt: modules_disabled: A toggle value indicating if modules are allowed to be loaded in an otherwise modular kernel. This toggle defaults to off (0), but can be set true (1). Once true, modules can be neither loaded nor unloaded, and ...
You can also temporarily blacklist them on the grub command line (linux line) when you boot with the syntax module_to_blacklist.blacklist=yes OR modprobe.blacklist=module_to_blacklist You need to modify the grub,cfg to make the changes permanent. Mind you, this solution will not work for few modules
If you're repeatedly building the kernel on the same machine, ccache can help a lot, especially if you're using a VM. In my experience, successive clean builds of the same project on a VM will build in about half the time as a build that didn't use ccache. You will need some extra disk space, to store the object files saved from the first build. Also the ...
The following instructions apply to building a kernel from upstream. Personally I find that simplest. I don't know how to obtain a tree with the ubuntu patches applied, ready to build like this. (1) Theoretically the way you build kernels in more reasonable timespans for testing is supposed to be cp /boot/config-`uname -r` .config you don't need to ...
Any kernel older than 3.18 will not compile using gcc 5. Use an older compiler.
You do not have the kernel sources. The compiler is looking for that header file. This link will get you a version of the kernel source tree that should be mostly similar to what you are looking for. https://cdn.kernel.org/pub/linux/kernel/v2.6/longterm/v2.6.32/linux-188.8.131.52.tar.xz
No, it does not exist in Linux kernel 4.1. It seems that the patch in question had a v2 proposed, which was then abandoned. The patch author seems to have opted to use the "at24" driver instead.
Actually here two things are there to care about: Is the running kernel version is same are of the source we are using. As previously compiled kernel may not be having all the dependencies which may be used in latest version, while compilation of external module with latest kernel source may be dependent on any part of the code, which is only present in ...
Top 50 recent answers are included