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

jmu · 2014-07-14 16:22:19

After recent (since 9.7.2014) updates, the WLAN link stopped working for me - and I don't seem to be find a way to restore it. Thus, your wisdom is appreciated:

Setup/Background
- Device: Zotac ZBox IQ (http://www.zotac.com/products/mini-pcs/ … nt/10.html)
- Network device (2xGLAN): Realtek RTL8111/8168/8411 (kernel module r8169 loads)
- Wifi (device missing, used to work as enp3s0 ??), should be intel chipset
- Wired connection works
- NetworkManager is in use
- Dmesg error: enp3s0 link is not ready

Tried so far

- Tested with older kernel 3.14.x -- no change
- Tested with kernel-lts -- no change
- Tested with older networkmanager -- no change
- Tested with fresh Arch media (latest.iso) -- device cannot be found
- Tested with older Arch media (1.4.2014.iso) -- device cannot be found
- Tried bringing up the link with command: ip link set dev enp3s0 up -- no change, no error
- Unloading r8169 removes the wired connection in networkmanager but not wireless, is that normal?
- Noticed also this link (https://wiki.archlinux.org/index.php/Ne … OL_problem), but setup has no Windows

Any pointers? Had a similar problem sometime in the past (https://bbs.archlinux.org/viewtopic.php?id=177793 -- different device), and then after some time and upgrades it just started working again.

Thanks in advance,
Juha

[EDIT 14.7]
Removed misleading reference: Noticed this post (https://bbs.archlinux.org/viewtopic.php?id=183601) and changed name in udev rules: enp03s0 -> wlp03s0 -- no change

[EDIT 16.7]
Added some details seen also later in thread

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

HungGarTiger · 2014-07-14 18:44:20

Same issue here, after some updates yesterday wlan0 won't load.

up link set wlan0 up

Gives: Operation not possible due to RF-kill

dmesg | grep wlan0

Gives: Link not ready

Trilby · 2014-07-14 19:11:16

jmu wrote:

... and changed name in udev rules: enp03s01 -> wlp03s02 -- no change
- Unloading r8169 removes the wired connection in networkmanager but not wireless, is that normal?

RE name change: that makes no sense. That does not come from the thread linked, and renaming a wired interface to something that looks like a wireless interface is a horrible idea. Please undo that first. (and/or help me understand why that step was taken).

For the module, that sounds reasonable if that is the ethernet driver module. What drivers do you use for the wireless card? What is the wireless card? Ethernet and wireless are separate devices and (at least almost always) will have separate drivers.

----

HungGarTiger wrote:

Same issue here ...
Gives: Operation not possible due to RF-kill

How is that the same issue? It sounds like a totally different issue. It is an issue with directions to a solution provided: check RF-Kill, then if that doesn't work and there isn't some more clear reason to link it to the OPs issue, start your own thread rather than trying to hijack someone else's.

(edit: oops - I quoted myself rather than editing - fixed that, I hope)

Last edited by Trilby (2014-07-14 19:21:29)

ewaller · 2014-07-14 19:16:47

Could you please post the output of ip link ?

jmu · 2014-07-14 20:44:18

First of all, thanks for the replies. Here's mine:

ip link (enp2s0 is wired connection, wlp3s0 is wlan):

23:29:46 juha@zbox ~ ip link                                                                                        1 ↵
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 00:01:2e:4f:71:a4 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,DYNAMIC,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:01:2e:4f:71:a5 brd ff:ff:ff:ff:ff:ff

dmesg | grep link

[  420.717745] r8169 0000:02:00.0 enp2s0: link down
[  420.717771] r8169 0000:02:00.0 enp2s0: link down
[  420.717808] IPv6: ADDRCONF(NETDEV_UP): enp2s0: link is not ready
[  420.847922] r8169 0000:03:00.0 wlp3s0: link down
[  420.847958] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[  422.338234] r8169 0000:02:00.0 enp2s0: link up
[  422.338246] IPv6: ADDRCONF(NETDEV_CHANGE): enp2s0: link becomes ready

I also just tried using Connman instead of NetworkManager, just to verify the problem is not in NM. Outcome: The wired connection works, but wireless does not exist:

23:27:23 juha@zbox ~ connmanctl technologies
/net/connman/technology/ethernet
  Name = Wired
  Type = ethernet
  Powered = True
  Connected = True
  Tethering = False
/net/connman/technology/bluetooth
  Name = Bluetooth
  Type = bluetooth
  Powered = False
  Connected = False
  Tethering = False

@Trilby: No real reason for the name change - just picked up it from the referenced post (you know how desperate one can get just to fix the issue ). I'll remove the renaming.

ewaller · 2014-07-14 20:51:00

I don't know about the history of your machine, but right now your wireless interface is called wlp3s0.
Try the command sudo iw wlp3s0 scan
You should see a site survey that includes your access point. If that works, then we can move forward.

Edit: If things have changed names from what they have been in the past, is it possible you have added or rearranged hardware in your system?

Last edited by ewaller (2014-07-14 20:51:57)

jmu · 2014-07-14 21:05:32

I had interface renamed with rule - but now it is disabled and interface name is again enp3s0:

23:56:52 root@zbox juha cat /etc/udev/rules.d/10-network.rules 
#SUBSYSTEM=="net", ACTION=="add", ATTR{address}=="00:01:2e:4f:71:a5", NAME="wlp3s0"

23:56:24 root@zbox juha ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:01:2e:4f:71:a4 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.99/24 brd 192.168.1.255 scope global enp2s0
       valid_lft forever preferred_lft forever
    inet6 fe80::201:2eff:fe4f:71a4/64 scope link 
       valid_lft forever preferred_lft forever
3: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 00:01:2e:4f:71:a5 brd ff:ff:ff:ff:ff:ff

I tried iw scanning but it does not find the device:

23:57:31 root@zbox juha iw enp3s0 scan
command failed: No such device (-19)

0:00:19 root@zbox juha iw list
(empty output)

And as for the issue background - the usual story: No changes in HW or BIOS, just SW updates as they flow (I tend to run them daily bases). It was 9th or 10th of July when I rebooted my computer just to find out the wireless no longer works.

ewaller · 2014-07-14 21:13:46

Well, I guess I can't help if you won't try the command I provided.

But ask yourself, why is there a conflict between the ip link command output versus the ip addr output in terms of device names?

jmu · 2014-07-14 21:19:13

Uh, sorry if I missed something but I did run the command and pasted the output of iw scan - here it is again:

iw enp3s0 scan
command failed: No such device (-19)

jmu · 2014-07-14 21:21:53

And I don't see the difference in device names - what do you mean exactly?

ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 00:01:2e:4f:71:a4 brd ff:ff:ff:ff:ff:ff
3: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:01:2e:4f:71:a5 brd ff:ff:ff:ff:ff:ff

ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:01:2e:4f:71:a4 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.99/24 brd 192.168.1.255 scope global enp2s0
       valid_lft forever preferred_lft forever
    inet6 fe80::201:2eff:fe4f:71a4/64 scope link 
       valid_lft forever preferred_lft forever
3: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 00:01:2e:4f:71:a5 brd ff:ff:ff:ff:ff:ff

Trilby · 2014-07-14 21:30:34

Jmu, I think you are assuming we know all about your machine and it's history. We don't. You're using two naming schemes interchangeably, and they're both odd. Again, the thread you linked to says absolutely nothing about manually renaming that interface. It does indicate that with *that* driver, the wireless interface used to show up as if it were ethernet (e.g. en* naming), but with an up to date system it will not show up properly as a w*. This does not say you should rename it - it says if your system is up-to-date, the driver will properly name it.

So either you are not actually using that driver (which still isn't clear) or your system is not up to date ... or perhaps you are up to date, and you are using that driver, and that post is just wrong. But I can't tell.

Don't make us guess and assume. Tell us what wireless hardware you have (you've told us about your ethernet hardware, but that isn't relevant - what's the wireless card). Tell us what driver it is using, tell us what names it used to have and when it last worked ... tell us anything that can help us understand your process.

Last edited by Trilby (2014-07-14 21:32:05)

jmu · 2014-07-14 21:33:42

Yes, sorry about the misleading reference there. I'll remove it from the first post just to avoid more confusion.

Trilby · 2014-07-14 21:36:48

Eh ... removing information - even if it lead you down the wrong path - isn't the solution. The solution is providing information. But if you don't want to do that, no one will be able to help you. Good luck.

jmu · 2014-07-14 21:41:11

Look, I'm trying to provide the info as much as getting the issue fixed (and hopefully also someone else having the issue). Are there any questions that I have not answered (that I'm capable of answering to)?

As for the removing, I put the link in [edited] section so that I would not cause any misleading references.

ewaller · 2014-07-14 21:42:18

jmu wrote:

Uh, sorry if I missed something but I did run the command and pasted the output of iw scan - here it is again:
iw enp3s0 scan
command failed: No such device (-19)

And, again, that is not the command I provided.

jmu · 2014-07-14 21:43:31

Now about that driver thing - how can I check which driver I'm using / should be using with wireless connection?

jmu · 2014-07-14 21:52:54

Sorry for missing your guidance ewaller, but you mean this?

ewaller wrote:

I don't know about the history of your machine, but right now your wireless interface is called wlp3s0.
Try the command sudo iw wlp3s0 scan
You should see a site survey that includes your access point. If that works, then we can move forward.
Edit: If things have changed names from what they have been in the past, is it possible you have added or rearranged hardware in your system?

Let's try again:

sudo iw wlp3s0 scan
(iw help output)

Apparently it requires dev parameter?

sudo iw dev wlp3s0 scan
command failed: No such device (-19)

I'd also point out that at this point the interface renaming is removed as suggested, but still the outcome is the same:

sudo iw dev enp3s0 scan
command failed: No such device (-19)

jmu · 2014-07-14 21:56:31

And here's the output of lspci -k (taken from: https://wiki.archlinux.org/index.php/Wi … er_status)

lspci -k
02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)
        Subsystem: ZOTAC International (MCO) Ltd. Device 8168
        Kernel driver in use: r8169
        Kernel modules: r8169
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 07)
        Subsystem: ZOTAC International (MCO) Ltd. Device 8168
        Kernel driver in use: r8169
        Kernel modules: r8169

Trilby · 2014-07-14 22:18:21

The information that is needed is primarily about your hardware and the drivers you have been (trying) to use and whether your system is up to date. This last post is part of what is needed. Arch users are expected to be able to look through the wiki and figure out how to gather some of their own information - this is also addressed in the link in ewaller's signature which is worth a read. But to be fair I might be a little short tempered tonight. I got a urgent call to help a dog-sitter who was taking care of a friends dog ... They've been doing a horrible job, the dog and it's living area where smeared in poop, and I had to restrain the dog to remove a tick ... then she crapped all over me. I ended up having to drive home covered in crap, clean myself, clean my clothes, and clean my truck. So suffice it to say it was a 'shitty' day.

Anyhow - That lspci output indicates you have two ethernet cards, but suggests there is no wireless hardware. The command itself would provided *a lot* more output than that, so I assume you have filtered what you thought would be relevant. But are you sure you filtered correctly. The following version will help - post all the output from this one:

lspci -vnn | grep -i net

ewaller · 2014-07-14 22:37:13

jmu wrote:

Sorry for missing your guidance ewaller, but you mean this?
...
Let's try again:
sudo iw wlp3s0 scan
(iw help output)
Apparently it requires dev parameter?
sudo iw dev wlp3s0 scan
command failed: No such device (-19)
...

ewaller$@$odin ~ 1012 %sudo iw wlan0 scan
[sudo] password for ewaller:
BSS c4:3d:c7:5d:eb:8f(on wlan0) -- associated
        TSF: 142129421052 usec (1d, 15:28:49)
        freq: 2412
        beacon interval: 100 TUs
        capability: ESS Privacy ShortSlotTime (0x0411)
        signal: -42.00 dBm
        last seen: 260 ms ago
        Information elements from Probe Response frame:
        SSID: Woodlyn
        Supported rates: 1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0
        DS Parameter set: channel 1
        ERP: <no flags>
        ERP D4.0: <no flags>
        RSN:     * Version: 1
                 * Group cipher: CCMP
                 * Pairwise ciphers: CCMP
                 * Authentication suites: PSK
                 * Capabilities: 16-PTKSA-RC 1-GTKSA-RC (0x000c)
        Extended supported rates: 6.0 9.0 12.0 48.0
        HT capabilities:
                Capabilities: 0x187c
                        HT20
                        SM Power Save disabled
                        RX Greenfield
                        RX HT20 SGI
                        RX HT40 SGI
                        No RX STBC
                        Max AMSDU length: 7935 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT RX MCS rate indexes supported: 0-15
                HT TX MCS rate indexes are undefined
        HT operation:
                 * primary channel: 1
                 * secondary channel offset: no secondary
                 * STA channel width: 20 MHz
                 * RIFS: 0
                 * HT protection: non-HT mixed
                 * non-GF present: 1
                 * OBSS non-GF present: 1
                 * dual beacon: 0
                 * dual CTS protection: 0
                 * STBC beacon: 0
                 * L-SIG TXOP Prot: 0
                 * PCO active: 0
                 * PCO phase: 0
        WMM:     * Parameter version 1
                 * u-APSD
                 * BE: CW 15-1023, AIFSN 3
                 * BK: CW 15-1023, AIFSN 7
                 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
                 * VO: CW 3-7, AIFSN 2, TXOP 1504 usec
BSS 78:54:2e:17:d3:ee(on wlan0)
        TSF: 18945414335000 usec (219d, 06:36:54)
        freq: 2412
        beacon interval: 100 TUs
        capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
        signal: -84.00 dBm
        last seen: 193 ms ago
        Information elements from Probe Response frame:
        SSID: mcfab
        Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
        DS Parameter set: channel 1
        Country: US     Environment: Indoor/Outdoor
                Channels [1 - 11] @ 30 dBm
        ERP: Use_Protection Barker_Preamble_Mode
        Extended supported rates: 24.0 36.0 48.0 54.0
        HT capabilities:
                Capabilities: 0x1ad
                        RX LDPC
                        HT20
                        SM Power Save disabled
                        RX HT20 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        No DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: No restriction (0x00)
                HT RX MCS rate indexes supported: 0-15
                HT TX MCS rate indexes are undefined
        HT operation:
                 * primary channel: 1
                 * secondary channel offset: no secondary
                 * STA channel width: 20 MHz
                 * RIFS: 0
                 * HT protection: non-HT mixed
                 * non-GF present: 0
                 * OBSS non-GF present: 1
                 * dual beacon: 0
                 * dual CTS protection: 0
                 * STBC beacon: 0
                 * L-SIG TXOP Prot: 0
                 * PCO active: 0
                 * PCO phase: 0
        Overlapping BSS scan params:
                 * passive dwell: 20 TUs
                 * active dwell: 10 TUs
                 * channel width trigger scan interval: 300 s
                 * scan passive total per channel: 200 TUs
                 * scan active total per channel: 20 TUs
                 * BSS width channel transition delay factor: 5
                 * OBSS Scan Activity Threshold: 0.25 %
        Extended capabilities: HT Information Exchange Supported
        WMM:     * Parameter version 1
                 * u-APSD
                 * BE: CW 15-1023, AIFSN 3
                 * BK: CW 15-1023, AIFSN 7
                 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
                 * VO: CW 3-7, AIFSN 2, TXOP 1504 usec
        RSN:     * Version: 1
                 * Group cipher: TKIP
                 * Pairwise ciphers: CCMP TKIP
                 * Authentication suites: PSK
                 * Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
        WPA:     * Version: 1
                 * Group cipher: TKIP
                 * Pairwise ciphers: CCMP TKIP
                 * Authentication suites: PSK
        WPS:     * Version: 1.0
                 * Wi-Fi Protected Setup State: 2 (Configured)
                 * Response Type: 3 (AP)
                 * UUID: 13c0b07c-1dd2-11b2-8c69-91034a198fdd
                 * Manufacturer: D-Link
                 * Model: D-Link Repeater
                 * Model Number: DAP-1320
                 * Serial Number: none
                 * Primary Device Type: 6-0050f204-1
                 * Device name: DAP-1320
                 * Config methods: PBC
                 * RF Bands: 0x1
                 * Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
BSS 58:6d:8f:1c:7f:f5(on wlan0)
        TSF: 369471980976 usec (4d, 06:37:51)
        freq: 2422
        beacon interval: 100 TUs
        capability: ESS Privacy ShortSlotTime (0x0411)
        signal: -82.00 dBm
        last seen: 3106 ms ago
        Information elements from Probe Response frame:
        SSID: Merlin
        Supported rates: 1.0* 2.0* 5.5* 11.0* 18.0 24.0 36.0 54.0
        DS Parameter set: channel 3
        ERP: <no flags>
        ERP D4.0: <no flags>
        RSN:     * Version: 1
                 * Group cipher: TKIP
                 * Pairwise ciphers: CCMP TKIP
                 * Authentication suites: PSK
                 * Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
        Extended supported rates: 6.0 9.0 12.0 48.0
        HT capabilities:
                Capabilities: 0x18fc
                        HT20
                        SM Power Save disabled
                        RX Greenfield
                        RX HT20 SGI
                        RX HT40 SGI
                        TX STBC
                        No RX STBC
                        Max AMSDU length: 7935 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT RX MCS rate indexes supported: 0-15
                HT TX MCS rate indexes are undefined
        HT operation:
                 * primary channel: 3
                 * secondary channel offset: no secondary
                 * STA channel width: 20 MHz
                 * RIFS: 0
                 * HT protection: non-HT mixed
                 * non-GF present: 1
                 * OBSS non-GF present: 1
                 * dual beacon: 0
                 * dual CTS protection: 0
                 * STBC beacon: 0
                 * L-SIG TXOP Prot: 0
                 * PCO active: 0
                 * PCO phase: 0
        WPS:     * Version: 1.0
                 * Wi-Fi Protected Setup State: 2 (Configured)
                 * Response Type: 3 (AP)
                 * UUID: c18a4b3e-6832-34c7-2859-7ccb974a11a7
                 * Manufacturer: Cisco
                 * Model: Linksys E3200
                 * Model Number: v1.0.04
                 * Serial Number: 42
                 * Primary Device Type: 6-0050f204-1
                 * Device name: Linksys E3200
                 * Config methods: Display, PBC
                 * RF Bands: 0x3
                 * Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
        WPA:     * Version: 1
                 * Group cipher: TKIP
                 * Pairwise ciphers: CCMP TKIP
                 * Authentication suites: PSK
                 * Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
BSS b8:e6:25:f7:1d:29(on wlan0)
        TSF: 1088585492128 usec (12d, 14:23:05)
        freq: 2462
        beacon interval: 100 TUs
        capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
        signal: -79.00 dBm
        last seen: 30 ms ago
        Information elements from Probe Response frame:
        SSID: 2WIRE883
        Supported rates: 1.0* 2.0* 5.5* 6.0 9.0 11.0* 12.0 18.0
        DS Parameter set: channel 11
        Country: US     Environment: Indoor/Outdoor
                Channels [1 - 11] @ 27 dBm
        RSN:     * Version: 1
                 * Group cipher: TKIP
                 * Pairwise ciphers: CCMP TKIP
                 * Authentication suites: PSK
                 * Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
        WPA:     * Version: 1
                 * Group cipher: TKIP
                 * Pairwise ciphers: CCMP TKIP
                 * Authentication suites: PSK
        ERP: <no flags>
        Extended supported rates: 24.0 36.0 48.0 54.0
BSS c4:04:15:8f:29:a0(on wlan0)
        TSF: 1092012544384 usec (12d, 15:20:12)
        freq: 2447
        beacon interval: 100 TUs
        capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
        signal: -84.00 dBm
        last seen: 1170 ms ago
        Information elements from Probe Response frame:
        SSID: MyCharterWiFia0-2G
        Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
        DS Parameter set: channel 8
        TIM: DTIM Count 0 DTIM Period 2 Bitmap Control 0x0 Bitmap[0] 0x4
        ERP: <no flags>
        RSN:     * Version: 1
                 * Group cipher: CCMP
                 * Pairwise ciphers: CCMP
                 * Authentication suites: PSK
                 * Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
        Extended supported rates: 24.0 36.0 48.0 54.0
        WMM:     * Parameter version 1
                 * u-APSD
                 * BE: CW 15-1023, AIFSN 3
                 * BK: CW 15-1023, AIFSN 7
                 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
                 * VO: CW 3-7, AIFSN 2, TXOP 1504 usec
        HT capabilities:
                Capabilities: 0x11cc
                        HT20
                        SM Power Save disabled
                        RX HT40 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 3839 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 8 usec (0x06)
                HT RX MCS rate indexes supported: 0-15
                HT TX MCS rate indexes are undefined
        HT operation:
                 * primary channel: 8
                 * secondary channel offset: no secondary
                 * STA channel width: 20 MHz
                 * RIFS: 1
                 * HT protection: no
                 * non-GF present: 0
                 * OBSS non-GF present: 0
                 * dual beacon: 0
                 * dual CTS protection: 0
                 * STBC beacon: 0
                 * L-SIG TXOP Prot: 0
                 * PCO active: 0
                 * PCO phase: 0
        Overlapping BSS scan params:
                 * passive dwell: 20 TUs
                 * active dwell: 10 TUs
                 * channel width trigger scan interval: 300 s
                 * scan passive total per channel: 200 TUs
                 * scan active total per channel: 20 TUs
                 * BSS width channel transition delay factor: 5
                 * OBSS Scan Activity Threshold: 0.25 %
        Extended capabilities: HT Information Exchange Supported
BSS 00:1a:ef:0a:1f:1c(on wlan0)
        TSF: 1456596480215 usec (16d, 20:36:36)
        freq: 2412
        beacon interval: 100 TUs
        capability: ESS Privacy ShortSlotTime (0x0411)
        signal: -90.00 dBm
        last seen: 1503 ms ago
        Information elements from Probe Response frame:
        SSID: MEJ
        Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
        DS Parameter set: channel 1
        TIM: DTIM Count 0 DTIM Period 1 Bitmap Control 0x0 Bitmap[0] 0x20
        ERP: Barker_Preamble_Mode
        Extended supported rates: 24.0 36.0 48.0 54.0
        HT capabilities:
                Capabilities: 0x186e
                        HT20/HT40
                        SM Power Save disabled
                        RX HT20 SGI
                        RX HT40 SGI
                        No RX STBC
                        Max AMSDU length: 7935 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 32767 bytes (exponent: 0x002)
                Minimum RX AMPDU time spacing: 16 usec (0x07)
                HT RX MCS rate indexes supported: 0-15
                HT TX MCS rate indexes are undefined
        HT operation:
                 * primary channel: 1
                 * secondary channel offset: above
                 * STA channel width: any
                 * RIFS: 0
                 * HT protection: non-HT mixed
                 * non-GF present: 0
                 * OBSS non-GF present: 0
                 * dual beacon: 0
                 * dual CTS protection: 0
                 * STBC beacon: 0
                 * L-SIG TXOP Prot: 0
                 * PCO active: 0
                 * PCO phase: 0
        WMM:     * Parameter version 1
                 * BE: CW 15-1023, AIFSN 3
                 * BK: CW 15-1023, AIFSN 7
                 * VI: CW 7-15, AIFSN 2, TXOP 3008 usec
                 * VO: CW 3-7, AIFSN 2, TXOP 1504 usec
        WPS:     * Version: 1.0
                 * Wi-Fi Protected Setup State: 2 (Configured)
BSS e4:f4:c6:0a:52:e0(on wlan0)
        TSF: 105656013203 usec (1d, 05:20:56)
        freq: 2412
        beacon interval: 100 TUs
        capability: ESS Privacy ShortSlotTime RadioMeasure (0x1411)
        signal: -85.00 dBm
        last seen: 236 ms ago
        Information elements from Probe Response frame:
        SSID: NETGEAR98
        Supported rates: 1.0* 2.0* 5.5 11.0 18.0 24.0 36.0 54.0
        DS Parameter set: channel 1
        TIM: DTIM Count 1 DTIM Period 2 Bitmap Control 0x0 Bitmap[0] 0x0
        ERP: <no flags>
        ERP D4.0: <no flags>
        RSN:     * Version: 1
                 * Group cipher: CCMP
                 * Pairwise ciphers: CCMP
                 * Authentication suites: PSK
                 * Capabilities: 16-PTKSA-RC 1-GTKSA-RC (0x000c)
        Extended supported rates: 6.0 9.0 12.0 48.0
        BSS Load:
                 * station count: 6
                 * channel utilisation: 27/255
                 * available admission capacity: 0 [*32us]
        HT capabilities:
                Capabilities: 0x19ad
                        RX LDPC
                        HT20
                        SM Power Save disabled
                        RX HT20 SGI
                        TX STBC
                        RX STBC 1-stream
                        Max AMSDU length: 7935 bytes
                        DSSS/CCK HT40
                Maximum RX AMPDU length 65535 bytes (exponent: 0x003)
                Minimum RX AMPDU time spacing: 4 usec (0x05)
                HT RX MCS rate indexes supported: 0-23
                HT TX MCS rate indexes are undefined
        HT operation:
                 * primary channel: 1
                 * secondary channel offset: no secondary
                 * STA channel width: 20 MHz
                 * RIFS: 1
                 * HT protection: nonmember
                 * non-GF present: 1
                 * OBSS non-GF present: 1
                 * dual beacon: 0
                 * dual CTS protection: 0
                 * STBC beacon: 0
                 * L-SIG TXOP Prot: 0
                 * PCO active: 0
                 * PCO phase: 0
        Overlapping BSS scan params:
                 * passive dwell: 20 TUs
                 * active dwell: 10 TUs
                 * channel width trigger scan interval: 300 s
                 * scan passive total per channel: 200 TUs
                 * scan active total per channel: 20 TUs
                 * BSS width channel transition delay factor: 5
                 * OBSS Scan Activity Threshold: 0.25 %
        Extended capabilities: HT Information Exchange Supported, Extended Channel Switching, BSS Transition, 6
        WPS:     * Version: 1.0
                 * Wi-Fi Protected Setup State: 2 (Configured)
                 * UUID: 14ac5004-9685-bde7-cca3-7f46f9cc6964
                 * RF Bands: 0x3
                 * Unknown TLV (0x1049, 6 bytes): 00 37 2a 00 01 20
        WMM:     * Parameter version 1
                 * u-APSD
                 * BE: CW 15-1023, AIFSN 3
                 * BK: CW 15-1023, AIFSN 7
                 * VI: CW 7-15, AIFSN 2, TXOP 6016 usec
                 * VO: CW 3-7, AIFSN 2, TXOP 3264 usec
BSS ac:5d:10:66:64:e9(on wlan0)
        TSF: 568059494785 usec (6d, 13:47:39)
        freq: 2432
        beacon interval: 100 TUs
        capability: ESS Privacy ShortPreamble ShortSlotTime (0x0431)
        signal: -84.00 dBm
        last seen: 2350 ms ago
        Information elements from Probe Response frame:
        SSID: 2WIRE929
        Supported rates: 1.0* 2.0* 5.5* 11.0* 6.0 9.0 12.0 18.0
        DS Parameter set: channel 5
        TIM: DTIM Count 0 DTIM Period 1 Bitmap Control 0x0 Bitmap[0] 0x0
        Country: US     Environment: Indoor/Outdoor
                Channels [1 - 11] @ 27 dBm
        ERP: <no flags>
        RSN:     * Version: 1
                 * Group cipher: TKIP
                 * Pairwise ciphers: CCMP TKIP
                 * Authentication suites: PSK
                 * Capabilities: 1-PTKSA-RC 1-GTKSA-RC (0x0000)
        WPA:     * Version: 1
                 * Group cipher: TKIP
                 * Pairwise ciphers: CCMP TKIP
                 * Authentication suites: PSK
        Extended supported rates: 24.0 36.0 48.0 54.0
ewaller$@$odin ~ 1013 %

Nope.

ewaller · 2014-07-14 22:53:00

jmu wrote:

And I don't see the difference in device names - what do you mean exactly?

ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 00:01:2e:4f:71:a4 brd ff:ff:ff:ff:ff:ff
3: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:01:2e:4f:71:a5 brd ff:ff:ff:ff:ff:ff

ip addr
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
    inet 127.0.0.1/8 scope host lo
       valid_lft forever preferred_lft forever
    inet6 ::1/128 scope host 
       valid_lft forever preferred_lft forever
2: enp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP group default qlen 1000
    link/ether 00:01:2e:4f:71:a4 brd ff:ff:ff:ff:ff:ff
    inet 192.168.1.99/24 brd 192.168.1.255 scope global enp2s0
       valid_lft forever preferred_lft forever
    inet6 fe80::201:2eff:fe4f:71a4/64 scope link 
       valid_lft forever preferred_lft forever
3: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 00:01:2e:4f:71:a5 brd ff:ff:ff:ff:ff:ff

Do you think it is odd that when you ran it before it gave you a different answer?

jmu wrote:

23:29:46 juha@zbox ~ ip link                                                                                        1 ↵
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default 
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp2s0: <BROADCAST,MULTICAST,DYNAMIC,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DEFAULT group default qlen 1000
    link/ether 00:01:2e:4f:71:a4 brd ff:ff:ff:ff:ff:ff
3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,DYNAMIC,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:01:2e:4f:71:a5 brd ff:ff:ff:ff:ff:ff

What changed?

jmu · 2014-07-16 10:58:00

I'm puzzled - seems that wireless device has disappeared altogether (after trying various approaches unsuccessfully, I'm considering buying USB-WLAN dongle )

But here are my latest findings (and some answers):

Zotac IQ01 indeed has two network adapters, which explains the enp2s0 and enp3s0 links (both of them are working when the cable is plugged in)
Seems that WiFi is actually provided by Intel chip instead of Realtek. iwlwifi is not loaded by default, but loading it manually does not make any difference, either
A reference (http://superuser.com/questions/50735/zo … ux-support) suggested that WiFi module connects the board via USB header. While there are some Intel devices listed, non of them seem Wireless devices.
Since WLAN used to work, I've tried with alternative media (loading from USB stick): Arch 1.4.2014 (kernel 3.13), Arch latest (3.15), Ubuntu 14.4 LTS (kernel 3.13) as well as couple of different kernel versions. None of them shows the wireless device
There is no way to disable wireless in BIOS, only GLAN cards. I also reset the BIOS settings just to make sure

However, as mentioned, WLAN used to work and it's device name matched with enp3s0 (I don't there there ever has been 4 links (including loopback)). But I can't seem to be able to reproduce the success Still there are resources claiming that it works out-of-the-box: https://wiki.debian.org/InstallingDebia … ox/squeeze

----

Now for the responses (thanks for them!):

@evaller:

lspci -vnn | grep -i net                                                                                                                                                                                                  
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 07)
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 07)

and yes, dev -parameter can be omitted with iw command when there are devices available (it seems).

The difference between link names can be explained with udev rule I added and then removed (albeit I don't know if it explains the DYNAMIC keyword?

3: enp3s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast state DOWN group default qlen 1000
    link/ether 00:01:2e:4f:71:a5 brd ff:ff:ff:ff:ff:ff

3: wlp3s0: <NO-CARRIER,BROADCAST,MULTICAST,DYNAMIC,UP> mtu 1500 qdisc pfifo_fast state DOWN mode DEFAULT group default qlen 1000
    link/ether 00:01:2e:4f:71:a5 brd ff:ff:ff:ff:ff:ff

And finally, here are my USB devices:

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=btusb, 12M
    |__ Port 7: Dev 4, If 1, Class=Wireless, Driver=btusb, 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

@Trilby:
Yeah, dogs can give headache at times (I also have one).

Last edited by jmu (2014-07-16 10:59:19)

ewaller · 2014-07-16 15:33:35

Okay, things are starting to make a little sense.
Lets see the output of lspci -nn (The version you provided had been filtered for lines containing 'net', I would like the unfiltered list)
Also, if you could post the output of pacman -Qs firmware

jmu · 2014-07-16 15:56:17

As it happens, I was also looking at the firmware versions. So here it goes:

lspci -nn 
00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM Controller [8086:0c00] (rev 06)
00:02.0 VGA compatible controller [0300]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller [8086:0412] (rev 06)
00:03.0 Audio device [0403]: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor HD Audio Controller [8086:0c0c] (rev 06)
00:14.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB xHCI [8086:8c31] (rev 05)
00:16.0 Communication controller [0780]: Intel Corporation 8 Series/C220 Series Chipset Family MEI Controller #1 [8086:8c3a] (rev 04)
00:1a.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #2 [8086:8c2d] (rev 05)
00:1b.0 Audio device [0403]: Intel Corporation 8 Series/C220 Series Chipset High Definition Audio Controller [8086:8c20] (rev 05)
00:1c.0 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #1 [8086:8c10] (rev d5)
00:1c.3 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #4 [8086:8c16] (rev d5)
00:1c.4 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #5 [8086:8c18] (rev d5)
00:1c.5 PCI bridge [0604]: Intel Corporation 8 Series/C220 Series Chipset Family PCI Express Root Port #6 [8086:8c1a] (rev d5)
00:1d.0 USB controller [0c03]: Intel Corporation 8 Series/C220 Series Chipset Family USB EHCI #1 [8086:8c26] (rev 05)
00:1f.0 ISA bridge [0601]: Intel Corporation H87 Express LPC Controller [8086:8c4a] (rev 05)
00:1f.2 SATA controller [0106]: Intel Corporation 8 Series/C220 Series Chipset Family 6-port SATA Controller 1 [AHCI mode] [8086:8c02] (rev 05)
00:1f.3 SMBus [0c05]: Intel Corporation 8 Series/C220 Series Chipset Family SMBus Controller [8086:8c22] (rev 05)
02:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 07)
03:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 07)

pacman -Qs firmware
local/linux-firmware 20140603.a4f3bc0-1
    Firmware files for Linux

Now, I've come to a conclusion the required firmware is intel 3160 (name was listed in provided windows -only driver resource). Based on that, I end up looking at these:

Unable to load firmware: https://bbs.archlinux.org/viewtopic.php?id=178458
I've tried with different combinations/versions of linux-3.1x and with linux-firmware (including linux-firmware-git), but no success so far

Here's the list of 3160 firmwares:

ls -l /lib/firmware/iwlwifi-3160-*
-rw-r--r-- 1 root root 670484 Jun 12 20:31 /lib/firmware/iwlwifi-3160-7.ucode
-rw-r--r-- 1 root root 667284 Jun 12 20:31 /lib/firmware/iwlwifi-3160-8.ucode
-rw-r--r-- 1 root root 666792 Jun 12 20:31 /lib/firmware/iwlwifi-3160-9.ucode

And then:

sudo modinfo iwlwifi | grep firmware
[sudo] password for juha: 
firmware:       iwlwifi-100-5.ucode
firmware:       iwlwifi-1000-5.ucode
firmware:       iwlwifi-135-6.ucode
firmware:       iwlwifi-105-6.ucode
firmware:       iwlwifi-2030-6.ucode
firmware:       iwlwifi-2000-6.ucode
firmware:       iwlwifi-5150-2.ucode
firmware:       iwlwifi-5000-5.ucode
firmware:       iwlwifi-6000g2b-6.ucode
firmware:       iwlwifi-6000g2a-5.ucode
firmware:       iwlwifi-6050-5.ucode
firmware:       iwlwifi-6000-4.ucode
firmware:       iwlwifi-3160-7.ucode
firmware:       iwlwifi-7260-7.ucode
parm:           fw_restart:restart firmware in case of error (default true) (bool)

According to this ticket comment the .9 should be in use though? https://bugzilla.kernel.org/show_bug.cgi?id=73441#c1

Trilby · 2014-07-16 16:10:40

...
    |__ Port 7: Dev 4, If 0, Class=Wireless, Driver=btusb, 12M
    |__ Port 7: Dev 4, If 1, Class=Wireless, Driver=btusb, 12M

Isn't that it? So this wouldn't be expected to show up in lspci. I don't know as much about getting usb interface data, but `lsusb -v` will provide more detail on those two entries.

EDIT: btusb ... yeah, sorry I missed that. I don't have any bt devices.

Last edited by Trilby (2014-07-16 16:37:47)

Arch Linux

#1 2014-07-14 16:22:19

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

#2 2014-07-14 18:44:20

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

#3 2014-07-14 19:11:16

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

#4 2014-07-14 19:16:47

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

#5 2014-07-14 20:44:18

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

#6 2014-07-14 20:51:00

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

#7 2014-07-14 21:05:32

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

#8 2014-07-14 21:13:46

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

#9 2014-07-14 21:19:13

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

#10 2014-07-14 21:21:53

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

#11 2014-07-14 21:30:34

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

#12 2014-07-14 21:33:42

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

#13 2014-07-14 21:36:48

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

#14 2014-07-14 21:41:11

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

#15 2014-07-14 21:42:18

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

#16 2014-07-14 21:43:31

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

#17 2014-07-14 21:52:54

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

#18 2014-07-14 21:56:31

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

#19 2014-07-14 22:18:21

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

#20 2014-07-14 22:37:13

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

#21 2014-07-14 22:53:00

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

#22 2014-07-16 10:58:00

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

#23 2014-07-16 15:33:35

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

#24 2014-07-16 15:56:17

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

#25 2014-07-16 16:10:40

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

Board footer