Currently using Ubuntu 18.04, and my wireless driver is not being detected.

I've included a wireless diagnosis log.

$ dmesg | grep iwl
[    6.212724] Loading modules backported from iwlwifi
[    6.212724] iwlwifi-stack-public:master:6988:0d8892f2
[    6.224583] iwlwifi 0000:00:14.3: enabling device (0000 -> 0002)
[    6.229811] iwlwifi 0000:00:14.3: Direct firmware load for iwl-dbg-cfg.ini failed with error -2
[    6.230540] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-39.ucode failed with error -2
[    6.230547] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-38.ucode failed with error -2
[    6.230552] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-37.ucode failed with error -2
[    6.230557] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-36.ucode failed with error -2
[    6.230562] iwlwifi 0000:00:14.3: Direct firmware load for iwlwifi-9000-pu-b0-jf-b0-35.ucode failed with error -2
[    6.236670] iwlwifi 0000:00:14.3: loaded firmware version 34.0.0 op_mode iwlmvm
[    6.248314] iwlwifi 0000:00:14.3: Detected Intel(R) Dual Band Wireless AC 9560, REV=0x318
[    7.264081] iwlwifi 0000:00:14.3: SecBoot CPU1 Status: 0x3, CPU2 Status: 0x2477
[    7.264084] iwlwifi 0000:00:14.3: Failed to start INIT ucode: -110
[    7.276165] iwlwifi 0000:00:14.3: Failed to run INIT ucode: -110

sudo modprobe iwlwifi returns no output.

  • I expect that it wants but is missing firmware. Let's try to find out which. Please edit your question to add the result of two terminal commands: sudo modprobe iwlwifi and also: dmesg | grep iwl Welcome to Ask Ubuntu.
    – chili555
    Commented May 23, 2018 at 20:13
  • @chili555: OP added the requested info and it looks like the driver found a firmware and loaded it happily. Commented May 29, 2018 at 1:09

4 Answers 4


I noticed this morning that Update Manager installed a later version of the package linux-firmware. I suggest that you obtain a temporary internet connection by ethernet, tethered or whatever means possible and open a terminal and do:

sudo apt update
sudo apt upgrade

I suspect that linux-firmware will be upgraded. After the upgrade, my firmware files include:


Reboot so that -38 loads instead of -34 as before. Check the log:

dmesg | grep iwl

Is the alarming message gone?

iwlwifi 0000:00:14.3: Failed to start INIT ucode: -110

Your wireless should be working now.

  • gave that a go same error messages - Im suspecting it could be a hardware problem - tried using the wifi module on windows as well and seems like its failing as well
    – Hyun Kim
    Commented May 30, 2018 at 12:21
  • I'm having this issue in Ubuntu live environment, but for me, it works fine in Windows, I have a connection, but installer/live environment cannot connect to internet 9560. I'm hesitant to install if I can't get wi fi working, any ideas?
    – edencorbin
    Commented Jul 10, 2018 at 22:31
  • @edencorbin Please start your own new question. I'll be happy to help.
    – chili555
    Commented Jul 11, 2018 at 1:18
  • @chili555 askubuntu.com/questions/1054012/…
    – edencorbin
    Commented Jul 11, 2018 at 3:19

Someone I know had her Intel AC Wireless 9560 stop working randomly during the day (Ubuntu 18.04.2). After investigating the dmesg output, checking out the NetworkManager service, reinstalling linux-firmware, rebooting, etc., we tried loading up Windows 10 on the second partition. Even Windows 10 could not find the wireless.

I've seen a few forums mentioning this particular Intel wireless card model. While this may be unhelpful, it's possible your card is broken; you may want to invest in a usb wifi or use ethernet and see if the card can be replaced (or do it yourself) [with another model].

She updated the BIOS and it started working again.


I think found a possible fix for it by opening Asus laptop and removing and reinserting Wifi Card did the job for me. I found it under SSD. worth giving a try if you are facing issue with both Bluetooth and Wifi. Old problem but still a nightmare.

  1. You should be sure then your HW support this stuff. It requires the newest HW.
  2. Despite this stuff officially is supported since kernel 4.14+, by the fact you will avoid a lot of issues by using 4.16+ and the newest firmware.

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .