New answers tagged

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


0

Besides what derobert wrote, I find myself using lsusb -t Which will print a tree with various info about connected devices including an helpful « Driver » part. and dmesg | grep driver which will list you the drivers of the latest plugged-in devices. The pros is that these two commands come installed with all distributions.


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 ...


0

Instead of a service to do the insmod you could provide a /lib/modprobe.d/mymodule.conf with the line install mymodule insmod /path/to/mymodule.ko I tried this and it worked ok on a fedora 22 using as an example the existing slip module. $ cd /lib/modules/4.2.8-200.fc22.x86_64/extra/drivers/net/slip/ $ lsmod|grep slip $ sudo modprobe slip $ lsmod|grep ...


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

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 ...


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 ...


0

So the solution to making the Canusb work in udev was found by Kurt Van Dijck: Sometimes one can have race conditions with udev rules since not all attributes are present on the launch of the uevent This updated /usr/local/bin/slcan_add.sh makes the CanUsb work correctly with udev when plugged in: #!/bin/sh # Bind the USBCAN device sleep 1 /usr/local/...


0

I had the same questions as you. In my case, the wireless controler is a Broadcom Corporation BCM4313 and the manufacturer and model numbers are 14e4 and 4727 : $ lspci -nn -s 03:00 |grep -i net 03:00.0 Network controller [0280]: Broadcom Corporation BCM4313 802.11bgn Wireless Network Adapter [14e4:4727] (rev 01) 1 - The module alias of the controler is ...



Top 50 recent answers are included