[SOLVED: HW ISSUE] WLAN no longer works (Zotac IQ01 / r8169 / iwlwifi)

ewaller · 2014-07-16 16:20:21

I am starting to think you have a hardware fault. There are no PCI devices attached to your system that provide a Wireless interface..
You indicated that someone had suggested it was a usb device. The output of lsusb does not show the device either. You have a bunch of HID (Human Interface Device), some audio, and a wireless board that is being driven by the Bluetooth driver. Maybe the device became unplugged? It could either be PCI-E or USB.

On the other hand, the spec sheet on you machine says

Networking
Ethernet 	2 x 10/100/1000Mbps
WiFi 	802.11ac + Bluetooth 4.0

That confirms the two wired interfaces. But, perhaps the wireless is a Bluetooth/802.11 combo. By extension, maybe the btusb driver is not answering the mail when it comes to WiFi.

So, you might try blacklisting the btusb module and see if the system finds an alternate driver. It is a quick a nasty test that might work.
Also, lets have a close look at the device. Please post the output of lsusb -v -s 3:7

jmu · 2014-07-16 16:36:10

@trilby:
I think that is the bluetooth (btusb = bluetooth usb?).
I don't understand why lsusb tree numbers does not match with normal listing, but I believe that is the same device:

sudo lsusb
Bus 004 Device 002: ID 8087:8000 Intel Corp. 
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 8087:8008 Intel Corp. 
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 006: ID 045e:00db Microsoft Corp. Natural Ergonomic Keyboard 4000 V1.0
Bus 001 Device 005: ID 8087:07dc Intel Corp. 
Bus 001 Device 004: ID 0bda:0129 Realtek Semiconductor Corp. RTS5129 Card Reader Controller
Bus 001 Device 007: ID 045e:0040 Microsoft Corp. Wheel Mouse Optical
Bus 001 Device 002: ID 1852:db96 GYROCOM C&C Co., LTD 
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

sudo lsusb -vs 001:005 |grep Protocol
  bDeviceProtocol         1 Bluetooth
      bInterfaceProtocol      1 Bluetooth
      bInterfaceProtocol      1 Bluetooth
      bInterfaceProtocol      1 Bluetooth
      bInterfaceProtocol      1 Bluetooth
      bInterfaceProtocol      1 Bluetooth
      bInterfaceProtocol      1 Bluetooth
      bInterfaceProtocol      1 Bluetooth

Last edited by jmu (2014-07-16 16:38:43)

ewaller · 2014-07-16 16:45:49

Arrg..... This is starting to feel like we are trying to nail Jell-O to a tree
I get the impression you must have rebooted and the buses re-enumerated. Anyway, yes that is what I was trying to explore.
It is your Bluetooth device, but, as it is the only wireless thing I see on your system, want to see if it has other capabilities. Could you post the output of that command without the filter? I want to look at all the interfaces and endpoints of that device. If that device does not have WiFi capability, then I would say you have a hardware failure.

jmu · 2014-07-16 18:45:09

Ah, they change on every reboot? That explains.

Output of lsusb -v command: http://pastebin.com/ACVFBsqt

When btusb is blacklisted, it shows "Driver=," for those Wireless USB entries

lsusb -t
/:  Bus 04.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 5000M
/:  Bus 03.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/14p, 480M
    |__ Port 1: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M
    |__ Port 1: Dev 2, If 1, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 1: Dev 2, If 3, Class=Audio, Driver=snd-usb-audio, 12M
    |__ Port 6: Dev 3, If 0, Class=Vendor Specific Class, Driver=rts5139, 480M
    |__ Port 7: Dev 4, If 0, Class=Wireless, Driver=, 12M
    |__ Port 7: Dev 4, If 1, Class=Wireless, Driver=, 12M
    |__ Port 9: Dev 5, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 9: Dev 5, If 1, Class=Human Interface Device, Driver=usbhid, 1.5M
    |__ Port 10: Dev 6, If 0, Class=Human Interface Device, Driver=usbhid, 1.5M
/:  Bus 02.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/8p, 480M
/:  Bus 01.Port 1: Dev 1, Class=root_hub, Driver=ehci-pci/2p, 480M
    |__ Port 1: Dev 2, If 0, Class=Hub, Driver=hub/6p, 480M

And as a reminder, iwlwifi is still not loaded automatically (it is being added in /etc/modules-load.d/iwlwifi.conf atm)

Yes, HW failure is an option - in case it would be very unfortunate as the PC itself is only few months old
And I'm not sure if it could be detached, being tightly packaged mini pc with more/less integrated ... well, everything?

eewallace · 2014-07-16 21:13:20

Just as a sanity check, since I don't see it answered in the thread so far, are you sure that the iwlwifi module is actually being loaded? What's the output of

lsmod | grep iwlwifi

?

And if it is there, you might want to see if

dmesg | grep iwl

shows any unusual messages.

jmu · 2014-07-16 22:10:04

@eewallace:

iwldvm is loaded by setting it in /etc/modules-load.d/wlan.conf (i've come to learn that iwldvm also loads iwlwifi)

lsmod|grep iw                                                                                                                                                                                                              1 ↵
iwldvm                170799  0 
iwlwifi               148746  1 iwldvm
led_class               3611  1 iwldvm
mac80211              495361  1 iwldvm
cfg80211              437959  3 iwlwifi,mac80211,iwldvm

dmesg shows nothing with:
```
dmesg |grep iwl
(empty)
```
however, it shows the module being loaded with (the message shown when modprobe iwlwifi is called manually):
```
dmesg |grep -i wifi 
[    1.632973] Intel(R) Wireless WiFi driver for Linux, in-tree:
```
but then again iwlwifi is not listed being used in lspci or lsusb
I wonder if device could have been shutdown programmatically? i've also tried settings some options for iwlwifi:
```
# /etc/modprobe.d/wlan.conf
options iwlwifi 11n_disable=1 bt_coex_active=0 power_save=0  swcrypto=1
```

eewallace · 2014-07-16 23:22:31

jmu wrote:

@eewallace:

iwldvm is loaded by setting it in /etc/modules-load.d/wlan.conf (i've come to learn that iwldvm also loads iwlwifi)

lsmod|grep iw                                                                                                                                                                                                              1 ↵
iwldvm                170799  0 
iwlwifi               148746  1 iwldvm
led_class               3611  1 iwldvm
mac80211              495361  1 iwldvm
cfg80211              437959  3 iwlwifi,mac80211,iwldvm

Well, that does at least show iwlwifi as loaded, so that rules out the naïve guess.

dmesg shows nothing with:
dmesg |grep iwl
(empty)

This seems odd. Both iwlwifi and iwldvm start with iwl, so that should catch messages from either one of them. From what I've seen, there should be at least a few messages from iwlwifi on load, whatever the configuration, so this makes it look to me as though it's not being loaded. Maybe I'm missing something here, though.

however, it shows the module being loaded with (the message shown when modprobe iwlwifi is called manually):
dmesg |grep -i wifi 
[    1.632973] Intel(R) Wireless WiFi driver for Linux, in-tree:
but then again iwlwifi is not listed being used in lspci or lsusb

I'm not sure I understand what you mean about calling modprobe iwlwifi manually here. In any case, that single line doesn't say anything about which module specifically is being loaded. Can you do

dmesg | grep -i -A 10 wifi

to get the next few lines?

I wonder if device could have been shutdown programmatically? i've also tried settings some options for iwlwifi:
# /etc/modprobe.d/wlan.conf
options iwlwifi 11n_disable=1 bt_coex_active=0 power_save=0  swcrypto=1

Did you add these options recently? I don't know much about the details of the wifi/bluetooth coexistence capabilities, but it seems odd to disable them on a card hosting both, unless you are not planning to use the bluetooth at all and having the coexistence mode enabled causes wifi problems somehow.

eewallace · 2014-07-16 23:32:08

Actually, from a bit more looking, it looks as though the two modules libdvm and libmvm are loaded automatically by iwlwifi, depending on the detected firmware versions. From the iwlwifi source:

config IWLDVM
	tristate "Intel Wireless WiFi DVM Firmware support"
	depends on IWLWIFI
	default IWLWIFI
	help
	  This is the driver that supports the DVM firmware which is
	  used by most existing devices (with the exception of 7260
	  and 3160).

config IWLMVM
	tristate "Intel Wireless WiFi MVM Firmware support"
	depends on IWLWIFI
	help
	  This is the driver that supports the MVM firmware which is
	  currently only available for 7260 and 3160 devices.

it looks like iwldvm is the wrong one for your card (intel 7260). I would suggest you try

rmmod iwldvm
rmmod iwlwifi
modprobe iwlwifi
lsmod | grep iwl

and see if it loads iwlmvm automatically.

jmu · 2014-07-17 10:11:52

Thanks for thorough research. Here are my clarifications:

Dmesg does not seem to contain 'iwl' at all. When iwlwifi is loaded (from command line or based on etc settings) it only shows following:

[  277.613720] Intel(R) Wireless WiFi driver for Linux, in-tree:           <- iwlwifi
[  277.613723] Copyright(c) 2003- 2014 Intel Corporation                   <- iwlwifi

Loading iwlwifi does not load iwlmvm nor iwldvm - maybe it's not detecting the right firmware version, then?

modprobe -v iwlwifi
insmod /lib/modules/3.15.5-1-ARCH/kernel/drivers/net/wireless/iwlwifi/iwlwifi.ko.gz 

lsmod|grep iwl
iwlwifi               148746  0 
cfg80211              437959  1 iwlwifi

modprobe -r iwlwifi

modprobe -v iwlmvm
insmod /lib/modules/3.15.5-1-ARCH/kernel/net/wireless/cfg80211.ko.gz 
insmod /lib/modules/3.15.5-1-ARCH/kernel/net/mac80211/mac80211.ko.gz 
insmod /lib/modules/3.15.5-1-ARCH/kernel/drivers/leds/led-class.ko.gz 
insmod /lib/modules/3.15.5-1-ARCH/kernel/drivers/net/wireless/iwlwifi/iwlwifi.ko.gz 
insmod /lib/modules/3.15.5-1-ARCH/kernel/drivers/net/wireless/iwlwifi/mvm/iwlmvm.ko.gz

lsmod|grep iwl
iwlmvm                155868  0 
iwlwifi               148746  1 iwlmvm
led_class               3611  1 iwlmvm
mac80211              495361  1 iwlmvm
cfg80211              437959  3 iwlwifi,mac80211,iwlmvm

As for the module parameters, I was just trying them out yesterday - now they have been commented out (no change whatsoever).

According to my understanding 3160 is the right one

----

I just realized I have a spare 2,5" disk. As a next step, I could install Windows to it, just to ensure if it's a hardware failure or does Windows still find it correctly - using provided drivers etc. And mayby I'll check for loose components while at it.

eewallace · 2014-07-17 16:32:04

Well, I'm running out of ideas. From what I can find about the device, it seems that it should show up as both a pci device (the 802.11ac part) and a usb device (the bluetooth). Since you're seeing one but not the other, it suggests that either there's a mechanical failure with just the wifi, or that somehow the pci device is failing to be registered. I have no real idea of how the pci info returned by lspci is populated to begin with, so I don't know whether that's a plausible explanation or not. The only other thing I can think of to check is whether there are any messages in dmesg about the pci device you would expect to see. It looks like it should be either 8086:08b1 or 8086:08b2, maybe but probably not 8086:08b4. So maybe a quick

dmesg | grep -A 10 | 8086:08

just to see whether there's anything about problems with the detection.

jmu · 2014-07-18 16:07:07

Ok, now it really seems like hardware issue (or at least Linux is not here to blaim): I installed Windows on spare disk just to find out that it does not list Wireless device either. I've contacted Zotac support to see if they have still something to check.

I'll update the topic with [SOLVED: HW ISSUE] for now.

Thank you very much for your help and time while digging into issue!

Last edited by jmu (2014-07-18 16:08:17)

eewallace · 2014-07-18 16:28:19

Sorry to hear it. Good luck.

Arch Linux

#26 2014-07-16 16:20:21

Re: [SOLVED: HW ISSUE] WLAN no longer works (Zotac IQ01 / r8169 / iwlwifi)

#27 2014-07-16 16:36:10

Re: [SOLVED: HW ISSUE] WLAN no longer works (Zotac IQ01 / r8169 / iwlwifi)

#28 2014-07-16 16:45:49

Re: [SOLVED: HW ISSUE] WLAN no longer works (Zotac IQ01 / r8169 / iwlwifi)

#29 2014-07-16 18:45:09

Re: [SOLVED: HW ISSUE] WLAN no longer works (Zotac IQ01 / r8169 / iwlwifi)

#30 2014-07-16 21:13:20

Re: [SOLVED: HW ISSUE] WLAN no longer works (Zotac IQ01 / r8169 / iwlwifi)

#31 2014-07-16 22:10:04

Re: [SOLVED: HW ISSUE] WLAN no longer works (Zotac IQ01 / r8169 / iwlwifi)

#32 2014-07-16 23:22:31

Re: [SOLVED: HW ISSUE] WLAN no longer works (Zotac IQ01 / r8169 / iwlwifi)

#33 2014-07-16 23:32:08

Re: [SOLVED: HW ISSUE] WLAN no longer works (Zotac IQ01 / r8169 / iwlwifi)

#34 2014-07-17 10:11:52

Re: [SOLVED: HW ISSUE] WLAN no longer works (Zotac IQ01 / r8169 / iwlwifi)

#35 2014-07-17 16:32:04

Re: [SOLVED: HW ISSUE] WLAN no longer works (Zotac IQ01 / r8169 / iwlwifi)

#36 2014-07-18 16:07:07

Re: [SOLVED: HW ISSUE] WLAN no longer works (Zotac IQ01 / r8169 / iwlwifi)

#37 2014-07-18 16:28:19

Re: [SOLVED: HW ISSUE] WLAN no longer works (Zotac IQ01 / r8169 / iwlwifi)

Board footer