Tag Info

New answers tagged

0

On a current CentOS 7 minimal install you need: sudo yum install gcc kernel-devel-$(uname -r)


2

Make can read a makefile from stdin, so you can give it a here document that is a makefile. The following is a makefile that includes your kernel makefile and adds a new wildcard target, %.var, whose recipe will output the value of the given make variable. (This assumes you don't have any files or other targets that end in .var, of course). showvar() { make ...


4

If you need just simple things like your example, just grep them out of the Makefile. For more complicated things, GNU Make has a -p option which prints the database after running Make, which includes all the variable definitions (and a lot more). You can use it together with -n, which causes the actions to not actually run (so nothing gets built). You can ...


2

You may try to extract the values with grep and sed. For example: filename="$HOME/kernelbuild/linux-3.14.37/Makefile" version=$(grep -m 1 VERSION $filename | sed 's/^.*= //g') This greps for first occurrence of "VERSION" in Makefile


0

You can find it in /usr/src or you can download from here (src.txz). In FreeBSD the base system is outside of package manager. You can't install kernel package, system utils (cp, ls, etc.) package, etc.. They are part of base system - you can update with freebsd-update (it's part of base system, of course). Check documentation too!


0

This may be a duplicate of this just asked differently. Anyways, have you tried to find out if another process is using the camera(such as one of your previous attempts to use the camera not exiting properly...) Try this - (notice you have to take the output of the first line and edit the third line to match your output... sudo fuser /dev/video0 ...


0

I ran into the same problem! After googling around for a good while, it finally turned out (in my case) that the kernel build toolchain is very picky about some env options, as pointed out here. Here, in my ~/.bashrc I had export GREP_OPTIONS='--color=always' and that seems to be causing problem with the module script generation. So changing it to export ...


1

I solved the problem by analyzing & modifying kernel module. Analyzing kernel module source code indicates that compatible kernel options should be concerned to load kernel modules as Gilles commented. Loading gre kernel module caused the problem because existing pptp module uses protocol ID IPGRE_PROTO that is equal to gre protocol ID. Kernel without ...


0

Having looked into this further it seems that this is due to the driver only being partially implemented, critical ioctls seem to be stubbed out.


0

There's so little detail here at the moment so we're just taking a stab in the dark at the moment. Reason why there could be only one kernel module present is that it's the only one needed, most driver requirements have been compiled as into the kernel not as loadable kernel modules, loading of many kernel modules have been blacklisted (for various ...


1

Distributions which use SysV init scripts where systemd is not available used to load modules on init listed in /etc/modules or /etc/modules.conf (from the kmod job). In distributions where systemd is available systemd-modules-load.service reads files from: /etc/modules-load.d/*.conf /run/modules-load.d/*.conf /usr/lib/modules-load.d/*.conf to load ...



Top 50 recent answers are included