Hot answers tagged

2

Skylake support isn't currently all that good in Linux in general. Furthermore, the default kernel in Debian 8.4 (and the associated firmware) is too old... You should try the updates available in the backports: echo deb http://http.debian.net/debian jessie-backports main contrib non-free > /etc/apt/sources.list.d/jessie-backports.list (as root), then ...


2

I had another, closer look at modules_install. In the Linux Makefile: # Target to install modules PHONY += modules_install modules_install: _modinst_ _modinst_post PHONY += _modinst_ _modinst_: @rm -rf $(MODLIB)/kernel @rm -f $(MODLIB)/source @mkdir -p $(MODLIB)/kernel @ln -s `cd $(srctree) && /bin/pwd` $(MODLIB)/...


1

The kernel doesn't log module operations in a centralised manner, each module can log whatever it wants (using printk()). The USB module logs "Initializing USB Mass Storage Driver..." etc.; but the FCoE drivers only log messages when errors occur — if everything loads correctly they're silent. Many modules work this way; the tendency is to minimize the ...


1

Those options work by passing options to the compiler, so the most straightforward way is to recompile the kernel. However for a reproducible and module-specific way kbuild allows you to set custom CFLAGs on a per-module basis. https://www.kernel.org/doc/Documentation/kbuild/makefiles.txt You particularly want to set -fno-stack-protector for the modules ...


1

You need to build a new kernel. The Brodcom BCM43142 is working under the 3.2.81 kernel version. To get some idea about the problem we can refer to the Bug report posted by @stephen-kitt 1) Remove the bcmwl driver 2) Compile the 3.2.81 Kernel 3) Re-install the broadcom-sta-dkms



Only top voted, non community-wiki answers of a minimum length are eligible