Tag Info

Hot answers tagged

2

Not unless you're willing to replace the BIOS. IBMs are usually considered "corporate" machines and this restriction is a "feature" so that you as a user can not install an unsecured or untested Wi-Fi card and bring down your corporate network. Even in the "home" space, it is still considered a "security feature". This is a design decision by IBM and ...


2

Okay after searching some more, and focusing on the driver problem i came up with this: echo "options ath9k nohwcrypt=1" | sudo tee /etc/modprobe.d/ath9k.conf sudo modprobe -rfv ath9k sudo modprobe -v ath9k I have no idea what it does, but it worked!


1

I fixed it by upgrading the kernel to 3.16, it is in wheezy-backports, it is also in jessie, expected to be released on 25 Apr 2015 (latter this month). Thanks to @Nasha 's comment, I followed your support link to intel's site, and found the driver (7260 ac), it says there, that I need a newer kernel, at least 3.10, so I found that there is a 3.16 in ...


1

mac here doesn't have any relation to Macs: MAC stands for Media Access Control. The module described in details here and it just provides a framework for Wi-Fi drivers to build upon. Also, cfg80211 provides the configuration layer. As I understand it, iwldvm just provides lower-level functionality for iwlwifi (thus the dependency) and other Intel WLAN ...


1

AFAIK, /sys/class/net/interface name holds the key. If there is a wireless directory contained in one of the interface name directories, then that is a wireless interface.


1

So, the core problem there is that it's looking for the kernel header files needed to compile new kernel modules. You can install those with sudo yum install kernel-devel But the further trick is that the compile process is looking for kernel devel files which match your running kernel. You can run uname -r to find the currently-running kernel, and rpm -q ...


1

The basic problem was you do not have kernel headers installed. If you do sudo yum install kernel-devel kernel-headers and boot into the new installed kernel. Then your driver make will be able to find your kernel headers in /lib/modules/{uname -r}/build


1

The following worked for me on Linux Mint "Rebecca" 64bit, running Cinnamon: Open the DVD / USB with the Linux install. Go to /pool/main/e/eglibc. Install both packages. (libc6-dev & libc-dev-bin) Go to /pool/main/b/bcmwl. Install package. (bcmwl-kernel-source). Note: If you don't find the packages there, search them elsewhere in /pool. (updates ...



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