Arch Linux

1000teslas

Member

Registered: 2015-05-04

Posts: 12

r8712u network adapters stop working after a while

using arch, both my network adapters, the RTL8188SU and RTL8191SU, work initially, but stop working after a while. but they work fine in windows.

Last edited by 1000teslas (2015-05-21 07:19:06)

jasonwryan

Anarchist

From: .nz

Registered: 2009-05-09

Posts: 30,424

Website

Re: r8712u network adapters stop working after a while

Please edit your post and choose a meaningful title: https://wiki.archlinux.org/index.php/Fo … ow_to_post

Copy the journal to a USB drive: without logs, this isn't going to go far. Also, provide more detail about your cards, drivers, network manager, etc...

Moving to Newbie Corner.

---

Arch + dwm   •   Mercurial repos  •   Surfraw

Registered Linux User #482438

1000teslas

Member

Registered: 2015-05-04

Posts: 12

Re: r8712u network adapters stop working after a while

here are some logs

dmesg | grep r8712u

[    3.404367] r8712u: module is from the staging directory, the quality is unknown, you have been warned.
[    3.405323] r8712u: register rtl8712_netdev_ops to netdev_ops
[    3.405328] usb 1-1.6: r8712u: USB_SPEED_HIGH with 4 endpoints
[    3.405768] usb 1-1.6: r8712u: Boot from EFUSE: Autoload OK
[    3.899882] usb 1-1.6: r8712u: CustomerID = 0x0000
[    3.899889] usb 1-1.6: r8712u: MAC Address from efuse = 8c:92:36:00:17:15
[    3.899906] usb 1-1.6: r8712u: Loading firmware from "rtlwifi/rtl8712u.bin"
[    3.900061] usbcore: registered new interface driver r8712u
[    3.904004] r8712u 1-1.6:1.0 wlp0s26u1u6: renamed from wlan0

journalctl -xb | grep dhcpcd

May 21 17:45:34 arch dhcpcd[411]: wlp0s26u1u6: carrier acquired
May 21 17:45:34 arch dhcpcd[411]: DUID 00:01:00:01:1c:da:ea:c3:02:01:57:52:33:30
May 21 17:45:34 arch dhcpcd[411]: wlp0s26u1u6: IAID 36:00:17:15
May 21 17:45:34 arch dhcpcd[411]: wlp0s26u1u6: soliciting an IPv6 router
May 21 17:45:34 arch dhcpcd[411]: wlp0s26u1u6: rebinding lease of 192.168.0.17
May 21 17:45:35 arch dhcpcd[411]: wlp0s26u1u6: leased 192.168.0.17 for 3600 seconds
May 21 17:45:35 arch dhcpcd[411]: wlp0s26u1u6: adding route to 192.168.0.0/24
May 21 17:45:35 arch dhcpcd[411]: wlp0s26u1u6: adding default route via 192.168.0.1
May 21 17:45:36 arch dhcpcd[411]: forked to background, child pid 712
May 21 17:45:36 arch dhcpcd[411]: wlp0s26u1u6: adding address fe80::8e65:34e1:2a9f:2e36
May 21 17:45:36 arch dhcpcd[411]: wlp0s26u1u6: waiting for carrier
May 21 17:45:36 arch dhcpcd[411]: wlp0s26u1u6: carrier acquired
May 21 17:45:36 arch dhcpcd[411]: DUID 00:01:00:01:1c:da:ea:c3:02:01:57:52:33:30
May 21 17:45:36 arch dhcpcd[411]: wlp0s26u1u6: IAID 36:00:17:15
May 21 17:45:36 arch dhcpcd[411]: wlp0s26u1u6: soliciting an IPv6 router
May 21 17:45:36 arch dhcpcd[411]: wlp0s26u1u6: rebinding lease of 192.168.0.17
May 21 17:45:36 arch dhcpcd[411]: wlp0s26u1u6: leased 192.168.0.17 for 3600 seconds
May 21 17:45:36 arch dhcpcd[411]: wlp0s26u1u6: adding route to 192.168.0.0/24
May 21 17:45:36 arch dhcpcd[411]: wlp0s26u1u6: adding default route via 192.168.0.1
May 21 17:45:36 arch dhcpcd[411]: forked to background, child pid 712
May 21 17:45:47 arch dhcpcd[712]: wlp0s26u1u6: no IPv6 Routers available

/etc/systemd/system/network-wireless@wlp0s26u1u6.service

[Unit]
Description=wireless network connection for %i
Wants=network.target
Before=network.target
BindsTo=sys-subsystem-net-devices-%i.device
After=sys-subsystem-net-devices-%i.device

[Service]
Type=oneshot
RemainAfterExit=yes

ExecStart=/usr/bin/ip link set dev %i up
ExecStart=/usr/bin/wpa_supplicant -B -D wext -i %i -c /etc/wpa_supplicant/OPTUSVD3AE44B8.conf
ExecStart=/usr/bin/dhcpcd %i

ExecStop=/usr/bin/ip link set dev %i down

[Install]
WantedBy=multi-user.target

V1del

Forum Moderator

Registered: 2012-10-16

Posts: 21,768

Re: r8712u network adapters stop working after a while

I had such an adapter for a while but then replaced it because of this issue. The driver isn't stable yet (the topline of your dmesg tells you this, its from the staging tree) I don't think there's any magic switch you can flip other than hope that this is going to be fixed somewhere down the line (the driver has been in staging for a couple years already though, so I wouldn't hope for much in the forseeable future)