wlan card not detected [SOLVED]

[Pifagor]

All of a sudden, my wlan card is not working or showing up: ifconfig gives

eth0 Link encap:Ethernet HWaddr c0:3f:d5:62:b0:a6
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
Interrupt:20 Memory:f7d00000-f7d20000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:201896 errors:0 dropped:0 overruns:0 frame:0
TX packets:201896 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1
RX bytes:17321679 (17.3 MB) TX bytes:17321679 (17.3 MB)

usb0 Link encap:Ethernet HWaddr 92:656a:d4:f2
inet addr:192.168.42.66 Bcast:192.168.42.255 Mask:255.255.255.0
inet6 addr: fe80::9065:abff:fe6a:d4f2/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:139088 errors:0 dropped:0 overruns:0 frame:0
TX packets:114977 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:123104823 (123.1 MB) TX bytes:30041232 (30.0 MB)

What is strange is that bluetooth is still working when I send a file from my mobile; don't they use the same card? Is this a hardware problem or what? I am totally lost.

[JeremyB]

Post results for

Code: Select all

lspci -nnk | grep -iA3 net; lsusb; lshw -c net

[Pifagor]

lspci -nnk | grep -iA3 net; lsusb; lshw -c net
00:19.0 Ethernet controller [0200]: Intel Corporation Ethernet Connection I218-V [8086:1559] (rev 04)
Subsystem: Intel Corporation Device [8086:2054]
Kernel driver in use: e1000e
00:1b.0 Audio device [0403]: Intel Corporation 8 Series HD Audio Controller [8086:9c20] (rev 04)
--
02:00.0 Network controller [0280]: Intel Corporation Wireless 3160 [8086:08b3] (rev 83)
Subsystem: Intel Corporation Dual Band Wireless-AC 3160 [8086:0070]
Bus 001 Device 002: ID 8087:8000 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 002 Device 005: ID 8087:07dc Intel Corp.
Bus 002 Device 013: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 002 Device 032: ID 22b8:2e24 Motorola PCS
Bus 002 Device 006: ID 1686:0120 ZOOM Corporation
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
WARNING: you should run this program as super-user.
*-network
description: Ethernet interface
product: Ethernet Connection I218-V
vendor: Intel Corporation
physical id: 19
bus info: pci@0000:00:19.0
logical name: eth0
version: 04
serial: c0:3f:d5:62:b0:a6
capacity: 1Gbit/s
width: 32 bits
clock: 33MHz
capabilities: bus_master cap_list ethernet physical tp 10bt 10bt-fd 100bt 100bt-fd 1000bt-fd autonegotiation
configuration: autonegotiation=on broadcast=yes driver=e1000e driverversion=3.2.6-k firmware=0.6-4 latency=0 link=no multicast=yes port=twisted pair
resources: irq:44 memory:f7d00000-f7d1ffff memory:f7d3c000-f7d3cfff ioport:f080(size=32)
*-network UNCLAIMED
description: Network controller
product: Wireless 3160
vendor: Intel Corporation
physical id: 0
bus info: pci@0000:02:00.0
version: 83
width: 64 bits
clock: 33MHz
capabilities: cap_list
configuration: latency=0
resources: memory:f7c00000-f7c01fff
*-network
description: Ethernet interface
physical id: 2
logical name: usb0
serial: 92:656a:d4:f2
capabilities: ethernet physical
configuration: broadcast=yes driver=rndis_host driverversion=22-Aug-2005 firmware=RNDIS device ip=192.168.42.66 link=yes multicast=yes
WARNING: output may be incomplete or inaccurate, you should run this program as super-user.

[JeremyB]

What happens if you

Code: Select all

sudo modprobe -v iwlwifi

[Pifagor]

absolutely nothing.

[JeremyB]

Post results for

Code: Select all

dmesg | grep iwl

[Pifagor]

dmesg | grep iwl
[ 5.435580] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
[ 5.732381] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-3160-17.ucode failed with error -2
[ 5.752862] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-3160-16.ucode failed with error -2
[ 5.752889] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-3160-15.ucode failed with error -2
[ 5.768189] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-3160-14.ucode failed with error -2
[ 5.768209] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-3160-13.ucode failed with error -2
[ 5.768212] iwlwifi 0000:02:00.0: request for firmware file 'iwlwifi-3160-13.ucode' failed.
[ 5.768215] iwlwifi 0000:02:00.0: no suitable firmware found!

[kc1di]

this thread may be of help https://askubuntu.com/questions/864866/ ... 997#864997

[JeremyB]

They just need to update linux-firmware and reboot

Code: Select all

sudo apt-get install linux-firmware

[Pifagor]

I did update the firmware and rebooted, a couple of times until no more error messages came out. Still no luck finding the wlan.

[Pifagor]

Also, still
dmesg | grep iwl
[ 5.968409] iwlwifi 0000:02:00.0: enabling device (0000 -> 0002)
[ 6.011699] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-3160-17.ucode failed with error -2
[ 6.023161] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-3160-16.ucode failed with error -2
[ 6.023192] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-3160-15.ucode failed with error -2
[ 6.026905] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-3160-14.ucode failed with error -2
[ 6.026938] iwlwifi 0000:02:00.0: Direct firmware load for iwlwifi-3160-13.ucode failed with error -2
[ 6.026942] iwlwifi 0000:02:00.0: request for firmware file 'iwlwifi-3160-13.ucode' failed.
[ 6.026946] iwlwifi 0000:02:00.0: no suitable firmware found!

[JeremyB]

Ok,

Code: Select all

cd /lib/firmware
sudo wget https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/plain/iwlwifi-3160-17.ucode
sudo modprobe -r iwlwifi && sleep 10 && sudo modprobe iwlwifi

[Pifagor]

Unbelievable! My wireless is back! Thank you, thank you, thank you!

One note: the directory was lib, not llib, don't know if it is relevant.

I haven't got much of an idea what happened, anyone who wants to explain it in simple terms is welcome to do so!

[JeremyB]

The driver couldn't find the firmware, so we downloaded it and put it where the driver was looking