[SOLVED]Upgrade last night then wifi does not work

csfreebird · 2016-05-01 02:58:33

Hi,
My laptop is dell xps 13 9350. Arch works on my laptop for one months already. But last night after I upgrade system, I find the wifi status is down.

# ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp5s0u1u4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1280 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 00:24:9b:18:01:91 brd ff:ff:ff:ff:ff:ff
3: wlp58s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN mode DEFAULT group default qlen 1000
    link/ether c8:ff:28:78:44:fb brd ff:ff:ff:ff:ff:ff

Execute

ip link set wlp58s0 up

get nothing, no error message, state still is DOWN.

Below is my pac log.

[2016-04-30 22:01] [PACMAN] Running 'pacman -Syu'
[2016-04-30 22:01] [PACMAN] synchronizing package lists
[2016-04-30 22:02] [PACMAN] starting full system upgrade
[2016-04-30 22:34] [ALPM] running '70-dkms-remove.hook'...
[2016-04-30 22:34] [ALPM-SCRIPTLET] ==> No kernel 4.5.1-1-ARCH headers. You must install them to use DKMS!
[2016-04-30 22:34] [ALPM] transaction started
[2016-04-30 22:34] [ALPM] upgraded glib2 (2.48.0-1 -> 2.48.0-2)
[2016-04-30 22:34] [ALPM] upgraded texinfo (6.1-1 -> 6.1-3)
[2016-04-30 22:34] [ALPM] upgraded libcups (2.1.3-1 -> 2.1.3-2)
[2016-04-30 22:34] [ALPM] upgraded cups (2.1.3-1 -> 2.1.3-2)
[2016-04-30 22:34] [ALPM] upgraded qt5-base (5.6.0-3 -> 5.6.0-4)
[2016-04-30 22:34] [ALPM] upgraded desktop-file-utils (0.22-1 -> 0.22-2)
[2016-04-30 22:34] [ALPM] upgraded gdk-pixbuf2 (2.34.0-1 -> 2.34.0-2)
[2016-04-30 22:34] [ALPM] upgraded gtk-update-icon-cache (3.20.3-1 -> 3.20.3-4)
[2016-04-30 22:34] [ALPM] upgraded shared-mime-info (1.6-1 -> 1.6-2)
[2016-04-30 22:34] [ALPM] upgraded librsvg (2:2.40.15-1 -> 2:2.40.15-2)
[2016-04-30 22:34] [ALPM] upgraded gtk2 (2.24.30-1 -> 2.24.30-2)
[2016-04-30 22:34] [ALPM] upgraded deepin-screenshot (3.1.7-1 -> 3.1.7-2)
[2016-04-30 22:34] [ALPM] upgraded dhclient (4.3.4-1 -> 4.3.4-2)
[2016-04-30 22:34] [ALPM] upgraded fcitx (4.2.9.1-1 -> 4.2.9.1-2)
[2016-04-30 22:34] [ALPM] upgraded fcitx-googlepinyin (0.1.6-4 -> 0.1.6-5)
[2016-04-30 22:34] [ALPM] upgraded fcitx-gtk2 (4.2.9.1-1 -> 4.2.9.1-2)
[2016-04-30 22:34] [ALPM] upgraded libsoup (2.54.0.1-1 -> 2.54.1-1)
[2016-04-30 22:34] [ALPM] upgraded gtk3 (3.20.3-1 -> 3.20.3-4)
[2016-04-30 22:34] [ALPM] upgraded fcitx-gtk3 (4.2.9.1-1 -> 4.2.9.1-2)
[2016-04-30 22:34] [ALPM] upgraded qt4 (4.8.7-8 -> 4.8.7-9)
[2016-04-30 22:34] [ALPM] upgraded fcitx-qt4 (4.2.9.1-1 -> 4.2.9.1-2)
[2016-04-30 22:34] [ALPM] upgraded ffmpeg (1:3.0.1-1 -> 1:3.0.2-1)
[2016-04-30 22:34] [ALPM] upgraded firefox (45.0.2-1 -> 46.0-2)
[2016-04-30 22:34] [ALPM] upgraded jre8-openjdk-headless (8.u77-1 -> 8.u92-1)
[2016-04-30 22:34] [ALPM] upgraded jre8-openjdk (8.u77-1 -> 8.u92-1)
[2016-04-30 22:34] [ALPM] upgraded freemind (1.0.1-1 -> 1.0.1-2)
[2016-04-30 22:34] [ALPM] upgraded gconf (3.2.6-3 -> 3.2.6-4)
[2016-04-30 22:34] [ALPM] upgraded grep (2.24-1 -> 2.25-1)
[2016-04-30 22:34] [ALPM] upgraded jdk8-openjdk (8.u77-1 -> 8.u92-1)
[2016-04-30 22:34] [ALPM] upgraded kcoreaddons (5.21.0-1 -> 5.21.0-3)
[2016-04-30 22:34] [ALPM] upgraded kio (5.21.0-1 -> 5.21.0-2)
[2016-04-30 22:34] [ALPM] upgraded lib32-elfutils (0.165-1 -> 0.166-1)
[2016-04-30 22:34] [ALPM] upgraded libbsd (0.8.2-2 -> 0.8.3-1)
[2016-04-30 22:34] [ALPM] upgraded libnm-glib (1.0.12-1 -> 1.2.0-3)
[2016-04-30 22:34] [ALPM] upgraded libwmf (0.2.8.4-12 -> 0.2.8.4-13)
[2016-04-30 22:34] [ALPM] upgraded nm-connection-editor (1.0.10-1 -> 1.2.0-1)
[2016-04-30 22:34] [ALPM] upgraded network-manager-applet (1.0.10-1 -> 1.2.0-1)
[2016-04-30 22:34] [ALPM] upgraded networkmanager (1.0.12-1 -> 1.2.0-3)
[2016-04-30 22:34] [ALPM] upgraded networkmanager-pptp (1.0.8-1 -> 1.2.0-1)
[2016-04-30 22:34] [ALPM] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
[2016-04-30 22:34] [ALPM] upgraded pacman-mirrorlist (20160422-1 -> 20160424-1)
[2016-04-30 22:34] [ALPM] upgraded perl-dbi (1.634-1 -> 1.636-1)
[2016-04-30 22:34] [ALPM] upgraded smplayer (16.4.0-1 -> 16.4.0-2)
[2016-04-30 22:34] [ALPM] upgraded virtualbox-guest-dkms (5.0.16-4 -> 5.0.18-1)
[2016-04-30 22:34] [ALPM] upgraded virtualbox-guest-utils (5.0.16-4 -> 5.0.18-1)
[2016-04-30 22:34] [ALPM] upgraded wine (1.9.8-1 -> 1.9.9-2)
[2016-04-30 22:34] [ALPM] upgraded xapian-core (1:1.2.22-1 -> 1:1.2.23-1)
[2016-04-30 22:34] [ALPM] transaction completed
[2016-04-30 22:34] [ALPM] running '70-dkms-install.hook'...
[2016-04-30 22:34] [ALPM-SCRIPTLET] ==> No kernel 4.5.1-1-ARCH headers. You must install them to use DKMS!
[2016-04-30 22:34] [ALPM] running 'gdk-pixbuf-query-loaders.hook'...
[2016-04-30 22:34] [ALPM] running 'gio-querymodules.hook'...
[2016-04-30 22:34] [ALPM] running 'glib-compile-schemes.hook'...
[2016-04-30 22:34] [ALPM] running 'gtk-query-immodules-2.0.hook'...
[2016-04-30 22:34] [ALPM] running 'gtk-query-immodules-3.0.hook'...
[2016-04-30 22:34] [ALPM] running 'gtk-update-icon-cache.hook'...
[2016-04-30 22:34] [ALPM] running 'texinfo-install.hook'...
[2016-04-30 22:34] [ALPM] running 'update-desktop-database.hook'...
[2016-04-30 22:34] [ALPM] running 'update-mime-database.hook'...
[2016-04-30 22:39] [PACMAN] Running 'pacman -Sy boost-libs'
[2016-04-30 22:39] [PACMAN] synchronizing package lists
[2016-04-30 22:40] [ALPM] transaction started
[2016-04-30 22:40] [ALPM] reinstalled boost-libs (1.60.0-4)
[2016-04-30 22:40] [ALPM] transaction completed

Does newest networkmanger cause this problem? Can I downgrade this to solve this? And how to downgrade it?

Last edited by csfreebird (2016-05-02 02:44:52)

Trilby · 2016-05-01 03:23:54

The interface is up - that is what is indicated inside the brackets. The "DOWN" after that just means you don't have an active connection. You could downgrade, but you should just fix whatever went wrong with your networkmanager configuration. Did you check for pacnew files? (I've never used NM, so I can't point to specifics of what may have changed).

Did you see those warnings about installing kernel-headers for your dkms packages? Did you install kernel-headers?

cox · 2016-05-01 07:39:28

I got the exact same problem
My laptop

[    0.000000] DMI: SAMSUNG ELECTRONICS CO., LTD. 870Z5G/880Z5F/NP870Z5G-X01SE, BIOS P09RCL.066.150521.CC 05/21/2015

By running

systemctl restart NetworkManager

my wifi was up and connected

I do not yet know if this is needed on every boot, will test. EDIT back to failing after reboot :-(

Before

[kjetil@Arch log]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 18:67:b0:cc:f0:2f brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DEFAULT group default qlen 1000
    link/ether 6c:29:95:02:4b:7b brd ff:ff:ff:ff:ff:ff

After

[kjetil@Arch ~]$ ip link
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether 18:67:b0:cc:f0:2f brd ff:ff:ff:ff:ff:ff
3: wlp2s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP mode DORMANT group default qlen 1000
    link/ether 6c:29:95:02:4b:7b brd ff:ff:ff:ff:ff:ff

Last edited by cox (2016-05-01 07:45:03)

cox · 2016-05-01 09:49:15

Update:

Running KDE Plasma.

Made a new test user, logged in and found the wireless networks.
Connected to the network, and it connects fine.
Rebooted and logged in as original user and all i well with the world.

What could be the reason for such strange behaviour?

Last edited by cox (2016-05-01 09:50:02)

burebista · 2016-05-01 19:55:19

My WIFI stopped working as well because of the updates that I received in the last 24 hours. Here is what I see in dmesg, if this matter:

...
[ 2.576266] iwlwifi 0000:03:00.0: enabling device (0000 -> 0002)
[ 2.577193] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-8000C-20.ucode failed with error -2
[ 2.577202] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-8000C-19.ucode failed with error -2
[ 2.577220] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-8000C-18.ucode failed with error -2
[ 2.577242] iwlwifi 0000:03:00.0: Direct firmware load for iwlwifi-8000C-17.ucode failed with error -2
[ 2.579445] AVX2 version of gcm_enc/dec engaged.
[ 2.579445] AES CTR mode by8 optimization enabled
[ 2.582986] iwlwifi 0000:03:00.0: loaded firmware version 16.242414.0 op_mode iwlmvm
[ 2.586939] r8169 0000:02:00.1 enp2s0f1: renamed from eth0
[ 2.614311] media: Linux media interface: v0.10
[ 2.620181] Linux video capture interface: v2.00
[ 2.620618] iwlwifi 0000:03:00.0: Detected Intel(R) Dual Band Wireless AC 8260, REV=0x208
[ 2.620687] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
[ 2.620968] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
[ 2.622129] iwlwifi 0000:03:00.0: can't access the RSA semaphore it is write protected
...
[ 2.768215] ieee80211 phy0: Selected rate control algorithm 'iwl-mvm-rs'
[ 2.770006] iwlwifi 0000:03:00.0 wlp3s0: renamed from wlan0
...
[ 2.973423] IPv6: ADDRCONF(NETDEV_UP): enp2s0f1: link is not ready
[ 2.993691] r8169 0000:02:00.1 enp2s0f1: link down
[ 2.993793] IPv6: ADDRCONF(NETDEV_UP): enp2s0f1: link is not ready
[ 2.999590] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[ 2.999695] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
[ 2.999999] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
[ 3.001091] iwlwifi 0000:03:00.0: can't access the RSA semaphore it is write protected
[ 3.201492] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
[ 3.202226] iwlwifi 0000:03:00.0: L1 Enabled - LTR Disabled
[ 3.202836] iwlwifi 0000:03:00.0: can't access the RSA semaphore it is write protected
...

The problem persisted across each restart. I never had WIFI problems on my laptop before today and I do update my system almost every day.
Then I issued once, as listed before, the command

systemctl restart NetworkManager

and the WIFI started working again AND now it works across restarts. So I only needed to issue once the above restart command.

BTW, I am using cinnamon as desktop.

Last edited by burebista (2016-05-01 20:03:05)

tazee · 2016-05-01 21:05:02

I too have this issue. The command

sudo systemctl restart NetworkManager

did not work for me. I saw the nm-applet icon in the system tray would cycle between connecting and disconnected. I then ran the

ip link

command every few seconds and found that my computers wireless interface to cycle between up and down.

Luckily I was able to plug my laptop into my router using a wire and hence I am able to get online.

So now my computer has the handicap of WiFi not working.

Last edited by tazee (2016-05-01 21:17:45)

Trilby · 2016-05-01 22:16:44

tazee wrote:

So now my computer has the handicap of WiFi not working.

No - it is NetworkManager that is not working (and likely your own configuration). It appears your WIFI is fine. You could use another tool to connect wirelessly until you identify what is wrong with your NM configuration.

nourathar · 2016-05-01 23:44:18

I updated today and I am running into the same / similar wifi problems on my Microsoft Surface Pro.
Restarting Networkmanager did not help.
I downloaded the dkms package and the linux-headers, reinstalled the kernel, but that did not seem to have caused any rebuilding of modules. Not sure what to add and how (and if I should really be doing that with my level of understanding).
When inspecting my dmesg output, it seems to be related to the mwifiex driver not behaving properly. Does this mean this is a kernel thing ?
it mentions dumping something to /sys/class/devcoredump, but in that directory there is only a file called 'disables' which contains the value '0'.

$ dmesg | grep wifi
[    2.443837] mwifiex_pcie 0000:01:00.0: enabling device (0000 -> 0002)
[    2.444060] mwifiex_pcie: try set_consistent_dma_mask(32)
[    2.444086] mwifiex_pcie: PCI memory map Virt0: ffffc90000e00000 PCI memory map Virt2: ffffc90003400000
[    2.444115] mwifiex: rx work enabled, cpus 4
[    3.485102] mwifiex_pcie 0000:01:00.0: info: FW download over, size 803884 bytes
[    4.518479] mwifiex_pcie 0000:01:00.0: WLAN FW is active
[    4.608821] mwifiex_pcie 0000:01:00.0: info: MWIFIEX VERSION: mwifiex 1.0 (15.68.7.p53) 
[    4.608824] mwifiex_pcie 0000:01:00.0: driver_version = mwifiex 1.0 (15.68.7.p53) 
[    4.610690] mwifiex_pcie 0000:01:00.0 wlp1s0: renamed from mlan0
[   10.906122] mwifiex_pcie 0000:01:00.0: CMD_RESP: invalid cmd resp
[   11.369311] mwifiex_pcie 0000:01:00.0: There is no command but got cmdrsp
[   11.369333] mwifiex_pcie 0000:01:00.0: CMD_RESP: invalid cmd resp
[   11.832524] mwifiex_pcie 0000:01:00.0: There is no command but got cmdrsp
[   11.832649] mwifiex_pcie 0000:01:00.0: CMD_RESP: invalid cmd resp
[   35.044113] mwifiex_pcie 0000:01:00.0: mwifiex_cmd_timeout_func: Timeout cmd id = 0x10, act = 0x1
[   35.044126] mwifiex_pcie 0000:01:00.0: num_data_h2c_failure = 0
[   35.044130] mwifiex_pcie 0000:01:00.0: num_cmd_h2c_failure = 0
[   35.044132] mwifiex_pcie 0000:01:00.0: is_cmd_timedout = 1
[   35.044135] mwifiex_pcie 0000:01:00.0: num_tx_timeout = 0
[   35.044137] mwifiex_pcie 0000:01:00.0: last_cmd_index = 0
[   35.044140] mwifiex_pcie 0000:01:00.0: last_cmd_id: 10 00 07 01 07 01 07 01 07 01
[   35.044142] mwifiex_pcie 0000:01:00.0: last_cmd_act: 01 00 00 00 00 00 00 00 00 00
[   35.044145] mwifiex_pcie 0000:01:00.0: last_cmd_resp_index = 4
[   35.044147] mwifiex_pcie 0000:01:00.0: last_cmd_resp_id: 07 81 00 00 00 00 00 00 07 81
[   35.044150] mwifiex_pcie 0000:01:00.0: last_event_index = 3
[   35.044152] mwifiex_pcie 0000:01:00.0: last_event: 58 00 58 00 58 00 58 00 58 00
[   35.044155] mwifiex_pcie 0000:01:00.0: data_sent=0 cmd_sent=1
[   35.044157] mwifiex_pcie 0000:01:00.0: ps_mode=1 ps_state=0
[   35.045360] mwifiex_pcie 0000:01:00.0: ===mwifiex driverinfo dump start===
[   35.045394] mwifiex_pcie 0000:01:00.0: info: MWIFIEX VERSION: mwifiex 1.0 (15.68.7.p53) 
[   35.045407] mwifiex_pcie 0000:01:00.0: ===mwifiex driverinfo dump end===
[   40.871076] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[   58.105826] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[   87.170916] mwifiex_pcie 0000:01:00.0: Firmware dump Finished!
[   87.171075] mwifiex_pcie 0000:01:00.0: == mwifiex dump information to /sys/class/devcoredump start
[   87.171299] mwifiex_pcie 0000:01:00.0: == mwifiex dump information to /sys/class/devcoredump end
[  106.034410] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[  306.107587] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[  306.112543] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[  306.115499] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[  306.115516] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[  306.115521] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[  316.224620] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state
[  634.386032] mwifiex_pcie 0000:01:00.0: PREP_CMD: FW is in bad state

Last edited by nourathar (2016-05-01 23:48:41)

nourathar · 2016-05-02 00:08:58

ok, I have no idea what is going on here, but the following happened:

I noticed that my Surface Pro 2 did not shut down cleanly; I had to shut it down using the power button for every reboot.
During one of these reboots I did not attempt to use wifi.
It shut down cleanly, and on restart wifi works and the mwifiex errors are gone.
Tried this several times now and it seems completely stable.

So I suppose some kind of updating process had some trouble finishing.

butler360 · 2016-05-02 00:24:42

Sounds like a duplicate of this: https://bbs.archlinux.org/viewtopic.php?pid=1624355

tazee · 2016-05-02 02:11:32

I tried several things unsuccessfully. In the end I reverted back to the old version of NetworkManager, which fixed the issue.

csfreebird · 2016-05-02 02:43:58

I downgrade the networkmanager, it works now.

strawberryfields · 2016-05-07 13:14:03

Thanks folks!
This was driving me nuts.

fahrgast · 2016-05-07 17:45:59

Same problem here after upgrading to libnm-glib-1.2.0-3 and networkmanager-1.2.0-3.

Downgrading to 1.0.12-1 fixed the issue, but this is only a workaround so I wouldn't tag the thread as SOLVED. I've seen that a bug has been reported here.

Scimmia · 2016-05-07 17:59:35

fahrgast wrote:

I've seen that a bug has been reported here.

If that's the issue, how about just fixing your config instead of downgrading?

fahrgast · 2016-05-07 18:10:28

Scimmia wrote:

If that's the issue, how about just fixing your config instead of downgrading?

With version 1.2.0-3 I tried to change from dhcp=internal to dhcp=dhclient in NetworkManager.conf, as described in the bug report, but it didn't work for me.

Scimmia · 2016-05-07 23:38:18

And dhclient is installed? If so, it's not the same issue.

fahrgast · 2016-05-10 19:43:41

Scimmia wrote:

And dhclient is installed? If so, it's not the same issue.

Yes, dhclient is installed. I don't know if the issue is the same or just similar, but the symptoms are just the same.

I've seen this sticky, related post.

fahrgast · 2016-05-19 08:43:37

NetworkManager-1.2.2-1 solved the issue for me.

Arch Linux

#1 2016-05-01 02:58:33

[SOLVED]Upgrade last night then wifi does not work

#2 2016-05-01 03:23:54

Re: [SOLVED]Upgrade last night then wifi does not work

#3 2016-05-01 07:39:28

Re: [SOLVED]Upgrade last night then wifi does not work

#4 2016-05-01 09:49:15

Re: [SOLVED]Upgrade last night then wifi does not work

#5 2016-05-01 19:55:19

Re: [SOLVED]Upgrade last night then wifi does not work

#6 2016-05-01 21:05:02

Re: [SOLVED]Upgrade last night then wifi does not work

#7 2016-05-01 22:16:44

Re: [SOLVED]Upgrade last night then wifi does not work

#8 2016-05-01 23:44:18

Re: [SOLVED]Upgrade last night then wifi does not work

#9 2016-05-02 00:08:58

Re: [SOLVED]Upgrade last night then wifi does not work

#10 2016-05-02 00:24:42

Re: [SOLVED]Upgrade last night then wifi does not work

#11 2016-05-02 02:11:32

Re: [SOLVED]Upgrade last night then wifi does not work

#12 2016-05-02 02:43:58

Re: [SOLVED]Upgrade last night then wifi does not work

#13 2016-05-07 13:14:03

Re: [SOLVED]Upgrade last night then wifi does not work

#14 2016-05-07 17:45:59

Re: [SOLVED]Upgrade last night then wifi does not work

#15 2016-05-07 17:59:35

Re: [SOLVED]Upgrade last night then wifi does not work

#16 2016-05-07 18:10:28

Re: [SOLVED]Upgrade last night then wifi does not work

#17 2016-05-07 23:38:18

Re: [SOLVED]Upgrade last night then wifi does not work

#18 2016-05-10 19:43:41

Re: [SOLVED]Upgrade last night then wifi does not work

#19 2016-05-19 08:43:37

Re: [SOLVED]Upgrade last night then wifi does not work

Board footer