1. Home
  2. Featured Articles
  3. Killer AX1650 in Debian/Ubuntu 16.04+
  1. Home
  2. Installing and Updating
  3. Killer AX1650 in Debian/Ubuntu 16.04+
  1. Home
  2. Wi-Fi and Bluetooth Troubleshooting
  3. Killer AX1650 in Debian/Ubuntu 16.04+
  1. Home
  2. Frequently Asked Questions
  3. Killer AX1650 in Debian/Ubuntu 16.04+
  1. Home
  2. Linux
  3. Killer AX1650 in Debian/Ubuntu 16.04+

Killer AX1650 in Debian/Ubuntu 16.04+

If your version of Linux does not support the Killer Wireless AX1650 at install, and you are using Ubuntu 16.04 or later, or another version of Debian Linux, you can use this guide to backport the drivers from the latest version of Ubuntu/Debian, enabling the Killer AX1650 in 16.04 or later. We have confirmed that this will result in wireless connectivity in Ubuntu 16.04 with the Killer Wireless AX1650.

If the device you are attempting to install WI-FI drivers on has NO Internet access at all, please refer to the following article

Please note that Secure Boot must be disabled in your BIOS before following these steps. If you are unsure how to disable Secure Boot, please refer to your machine or motherboard’s support materials or website.

Type or copy and paste the following commands in a Terminal, one line at a time, pressing Enter after each command.

$ sudo apt update
$ sudo apt-get install git
$ sudo apt-get install build-essential
$ git clone https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git
$ cd backport-iwlwifi
$ sudo make defconfig-iwlwifi-public
$ sudo make -j4
$ sudo make install

Additionally, you will need to ensure you have the latest iwlwifi firmware:

$ git clone git://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git
$ cd linux-firmware
$ sudo cp iwlwifi-* /lib/firmware/

Then restart.

If the WiFi Adapter still doesn’t appear, try entering the following in your Terminal:

$ sudo apt-get update --fix-missing
$ sudo apt-get upgrade
$ reboot

Once you have done this, you should be able to connect to your wireless access point!

If the issue hasn’t been resolved, please try getting in contact with our Support team by performing the following:

Create a file containing your Boot and Dmesg logs:
$ echo "Journalctl Boot Log" > logs.txt
$ journalctl -b >> logs.txt
$ echo "Dmesg" >> logs.txt
$ dmesg >> logs.txt
$ uname -a >> logs.txt
$ rfkill list >> logs.txt
$ sudo lshw -C network >> logs.txt
$ lspci -nn | grep -i net >> logs.txt

Submit a Ticket describing your issue and the steps you've taken.
Please attach the 'logs.txt' file also.
Submit A Ticket
Updated on September 12, 2019

Was this article helpful?

Related Articles

Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!