problem: it does not connect to any wifi network you can see the time out on
dmesg
>lsusb
Bus 002 Device 007: ID 0bda:817f Realtek Semiconductor Corp. RTL8188RU
802.11n WLAN Adapter
>iwconfig
wlp0s20u1 IEEE 802.11bgn ESSID:off/any
Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
Retry short limit:7 RTS thr=2347 B Fragment thr:off
Power Management:off
>dmesg
[16421.696441] usb 2-1: new high-speed USB device number 6 using xhci_hcd
[16423.550427] usb 2-1: Vendor: 11n U
[16423.550433] usb 2-1: Product: US036NHR
[16423.550437] usb 2-1: RTL8188RU rev A (TSMC) 1T1R, TX queues 2, WiFi=1,
BT=0, GPS=0, HI PA=1
[16423.550439] usb 2-1: RTL8188RU MAC: 00:c0:ca:7e:c7:d3
[16423.550441] usb 2-1: rtl8xxxu: Loading firmware
rtlwifi/rtl8192cufw_TMSC.bin
[16423.566357] usb 2-1: Firmware revision 80.0 (signature 0x88c1)
[16423.851643] usb 2-1: rtl8xxxu_iqk_path_a: Path A RX IQK failed!
[16423.958287] usbcore: registered new interface driver rtl8xxxu
[16424.016545] rtl8xxxu 2-1:1.0 wlp0s20u1: renamed from wlan0
[16424.032244] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[16424.038160] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[16424.080456] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[16673.335433] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16673.343329] [drm] Module unloaded
[16673.358464] bbswitch: disabling discrete graphics
[16673.358476] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16673.370088] pci 0000:04:00.0: Refused to change power state, currently in
D0
[16693.345669] bbswitch: enabling discrete graphics
[16693.851919] [drm] Initialized nvidia-drm 0.0.0 20150116 for 0000:04:00.0
on minor 1
[16693.851926] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 352.63 Sat
Nov 7 21:25:42 PST 2015
[16693.874719] vgaarb: this pci device is not a vga device
[16693.877519] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16693.877610] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16693.877645] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16693.877680] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16693.877711] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16693.877741] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16693.877796] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16693.877823] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16693.896287] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16694.332278] vgaarb: this pci device is not a vga device
[16754.752107] wlp3s0: deauthenticating from 9c:97:26:0f:0e:8e by local
choice (Reason: 3=DEAUTH_LEAVING)
[16754.773908] cfg80211: World regulatory domain updated:
[16754.773911] cfg80211: DFS Master region: unset
[16754.773912] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp), (dfs_cac_time)
[16754.773913] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A,
2000 mBm), (N/A)
[16754.773915] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A,
2000 mBm), (N/A)
[16754.773916] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A,
2000 mBm), (N/A)
[16754.773917] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000
KHz AUTO), (N/A, 2000 mBm), (N/A)
[16754.773919] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000
KHz AUTO), (N/A, 2000 mBm), (0 s)
[16754.773920] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A,
2000 mBm), (0 s)
[16754.773921] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A,
2000 mBm), (N/A)
[16754.773922] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz),
(N/A, 0 mBm), (N/A)
[16763.402727] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[16763.417485] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[16855.122476] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[16886.169494] wlp0s20u1: authenticate with 9c:97:26:0f:0e:8e
[16886.178492] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 1/3)
[16886.378815] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 2/3)
[16886.582153] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 3/3)
[16886.785485] wlp0s20u1: authentication with 9c:97:26:0f:0e:8e timed out
[16887.892687] wlp0s20u1: authenticate with 9c:97:26:0f:0e:8e
[16887.900447] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 1/3)
[16888.102209] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 2/3)
[16888.305548] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 3/3)
[16888.508920] wlp0s20u1: authentication with 9c:97:26:0f:0e:8e timed out
[16890.019757] wlp0s20u1: authenticate with 9c:97:26:0f:0e:8e
[16890.026490] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 1/3)
[16890.228972] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 2/3)
[16890.432302] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 3/3)
[16890.635649] wlp0s20u1: authentication with 9c:97:26:0f:0e:8e timed out
[16892.649660] wlp0s20u1: authenticate with 9c:97:26:0f:0e:8e
[16892.656123] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 1/3)
[16892.859066] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 2/3)
[16893.062410] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 3/3)
[16893.265769] wlp0s20u1: authentication with 9c:97:26:0f:0e:8e timed out
[16904.280196] wlp0s20u1: authenticate with 9c:97:26:0f:0e:8e
[16904.291265] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 1/3)
[16904.492903] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 2/3)
[16904.696222] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 3/3)
[16904.859783] wlp0s20u1: aborting authentication with 9c:97:26:0f:0e:8e by
local choice (Reason: 3=DEAUTH_LEAVING)
[16904.884734] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[17480.739921] vgaarb: this pci device is not a vga device
[17594.761942] vgaarb: this pci device is not a vga device
[17614.149381] wlp0s20u1: authenticate with 9c:97:26:0f:0e:8e
[17614.154382] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 1/3)
[17614.355248] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 2/3)
[17614.558591] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 3/3)
[17614.761922] wlp0s20u1: authentication with 9c:97:26:0f:0e:8e timed out
[17625.726388] wlp0s20u1: authenticate with 9c:97:26:0f:0e:8e
[17625.732085] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 1/3)
[17625.932382] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 2/3)
[17626.135736] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 3/3)
[17626.339089] wlp0s20u1: authentication with 9c:97:26:0f:0e:8e timed out
[16421.696441] usb 2-1: new high-speed USB device number 6 using xhci_hcd
[16423.550427] usb 2-1: Vendor: 11n U
[16423.550433] usb 2-1: Product: US036NHR
[16423.550437] usb 2-1: RTL8188RU rev A (TSMC) 1T1R, TX queues 2, WiFi=1,
BT=0, GPS=0, HI PA=1
[16423.550439] usb 2-1: RTL8188RU MAC: 00:c0:ca:7e:c7:d3
[16423.550441] usb 2-1: rtl8xxxu: Loading firmware
rtlwifi/rtl8192cufw_TMSC.bin
[16423.566357] usb 2-1: Firmware revision 80.0 (signature 0x88c1)
[16423.851643] usb 2-1: rtl8xxxu_iqk_path_a: Path A RX IQK failed!
[16423.958287] usbcore: registered new interface driver rtl8xxxu
[16424.016545] rtl8xxxu 2-1:1.0 wlp0s20u1: renamed from wlan0
[16424.032244] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[16424.038160] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[16424.080456] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[16673.335433] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16673.343329] [drm] Module unloaded
[16673.358464] bbswitch: disabling discrete graphics
[16673.358476] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16673.370088] pci 0000:04:00.0: Refused to change power state, currently in
D0
[16693.345669] bbswitch: enabling discrete graphics
[16693.851919] [drm] Initialized nvidia-drm 0.0.0 20150116 for 0000:04:00.0
on minor 1
[16693.851926] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 352.63 Sat
Nov 7 21:25:42 PST 2015
[16693.874719] vgaarb: this pci device is not a vga device
[16693.877519] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16693.877610] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16693.877645] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16693.877680] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16693.877711] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16693.877741] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16693.877796] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16693.877823] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16693.896287] ACPI Warning: \_SB_.PCI0.RP05.PEGP._DSM: Argument #4 type
mismatch - Found [Buffer], ACPI requires [Package] (20150930/nsarguments-95)
[16694.332278] vgaarb: this pci device is not a vga device
[16754.752107] wlp3s0: deauthenticating from 9c:97:26:0f:0e:8e by local
choice (Reason: 3=DEAUTH_LEAVING)
[16754.773908] cfg80211: World regulatory domain updated:
[16754.773911] cfg80211: DFS Master region: unset
[16754.773912] cfg80211: (start_freq - end_freq @ bandwidth),
(max_antenna_gain, max_eirp), (dfs_cac_time)
[16754.773913] cfg80211: (2402000 KHz - 2472000 KHz @ 40000 KHz), (N/A,
2000 mBm), (N/A)
[16754.773915] cfg80211: (2457000 KHz - 2482000 KHz @ 40000 KHz), (N/A,
2000 mBm), (N/A)
[16754.773916] cfg80211: (2474000 KHz - 2494000 KHz @ 20000 KHz), (N/A,
2000 mBm), (N/A)
[16754.773917] cfg80211: (5170000 KHz - 5250000 KHz @ 80000 KHz, 160000
KHz AUTO), (N/A, 2000 mBm), (N/A)
[16754.773919] cfg80211: (5250000 KHz - 5330000 KHz @ 80000 KHz, 160000
KHz AUTO), (N/A, 2000 mBm), (0 s)
[16754.773920] cfg80211: (5490000 KHz - 5730000 KHz @ 160000 KHz), (N/A,
2000 mBm), (0 s)
[16754.773921] cfg80211: (5735000 KHz - 5835000 KHz @ 80000 KHz), (N/A,
2000 mBm), (N/A)
[16754.773922] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz),
(N/A, 0 mBm), (N/A)
[16763.402727] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[16763.417485] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[16855.122476] IPv6: ADDRCONF(NETDEV_UP): wlp3s0: link is not ready
[16886.169494] wlp0s20u1: authenticate with 9c:97:26:0f:0e:8e
[16886.178492] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 1/3)
[16886.378815] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 2/3)
[16886.582153] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 3/3)
[16886.785485] wlp0s20u1: authentication with 9c:97:26:0f:0e:8e timed out
[16887.892687] wlp0s20u1: authenticate with 9c:97:26:0f:0e:8e
[16887.900447] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 1/3)
[16888.102209] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 2/3)
[16888.305548] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 3/3)
[16888.508920] wlp0s20u1: authentication with 9c:97:26:0f:0e:8e timed out
[16890.019757] wlp0s20u1: authenticate with 9c:97:26:0f:0e:8e
[16890.026490] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 1/3)
[16890.228972] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 2/3)
[16890.432302] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 3/3)
[16890.635649] wlp0s20u1: authentication with 9c:97:26:0f:0e:8e timed out
[16892.649660] wlp0s20u1: authenticate with 9c:97:26:0f:0e:8e
[16892.656123] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 1/3)
[16892.859066] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 2/3)
[16893.062410] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 3/3)
[16893.265769] wlp0s20u1: authentication with 9c:97:26:0f:0e:8e timed out
[16904.280196] wlp0s20u1: authenticate with 9c:97:26:0f:0e:8e
[16904.291265] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 1/3)
[16904.492903] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 2/3)
[16904.696222] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 3/3)
[16904.859783] wlp0s20u1: aborting authentication with 9c:97:26:0f:0e:8e by
local choice (Reason: 3=DEAUTH_LEAVING)
[16904.884734] IPv6: ADDRCONF(NETDEV_UP): wlp0s20u1: link is not ready
[17480.739921] vgaarb: this pci device is not a vga device
[17594.761942] vgaarb: this pci device is not a vga device
[17614.149381] wlp0s20u1: authenticate with 9c:97:26:0f:0e:8e
[17614.154382] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 1/3)
[17614.355248] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 2/3)
[17614.558591] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 3/3)
[17614.761922] wlp0s20u1: authentication with 9c:97:26:0f:0e:8e timed out
[17625.726388] wlp0s20u1: authenticate with 9c:97:26:0f:0e:8e
[17625.732085] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 1/3)
[17625.932382] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 2/3)
[17626.135736] wlp0s20u1: send auth to 9c:97:26:0f:0e:8e (try 3/3)
[17626.339089] wlp0s20u1: authentication with 9c:97:26:0f:0e:8e timed out
On 02/29/2016 06:28 AM, Jes Sorensen wrote:
> That one I have never seen before - could you try and insert some debug
> prints to see where the RF initialization fails?
The call to usb_control_msg() is returning -EPROTO (-71), but sometimes the
system works. I added the following patch:
diff --git a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c
b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c
index 38aa3c2..8ab77a0 100644
--- a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c
+++ b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c
@@ -1979,9 +1979,12 @@ static int rtl8xxxu_write_rfreg(struct rtl8xxxu_priv *priv,
/* Use XB for path B */
ret = rtl8xxxu_write32(priv, rtl8xxxu_rfregs[path].lssiparm, dataaddr);
- if (ret != sizeof(dataaddr))
+ if (ret != sizeof(dataaddr)) {
+ pr_info("**** rtl8xxxu_write32() error %d: path %d, reg: 0x%x,
data 0x%x, dataaddr 0x%x, lssiparm 0x%x\n",
+ ret, path, reg, data, dataaddr,
rtl8xxxu_rfregs[path].lssiparm);
+ dump_stack();
retval = -EIO;
- else
+ } else
retval = 0;
udelay(1);
When the error happens, my log contains
[52347.751420] **** rtl8xxxu_write32() error -71: path 0, reg: 0x2a, data 0x5,
dataaddr 0x2a00005, lssiparm 0x840
[52347.751427] CPU: 0 PID: 5743 Comm: systemd-udevd Not tainted 4.5.0-rc2-jes+ #2
[52347.751429] Hardware name: TOSHIBA TECRA A50-A/TECRA A50-A, BIOS Version 4.20
04/17/2014
[52347.751430] 00000000fffffffb ffff880117e139b8 ffffffff813d7722 ffff880101fb2860
[52347.751433] ffff880117e13a00 ffffffffa066ed56 ffffffff00000840 0000000500000010
[52347.751435] ffffffffa06803c0 ffff880101fb2860 0000000000000000 0000000000000031
[52347.751437] Call Trace:
[52347.751442] [<ffffffff813d7722>] dump_stack+0x4b/0x79
[52347.751446] [<ffffffffa066ed56>] rtl8xxxu_write_rfreg+0x146/0x150 [rtl8xxxu]
[52347.751448] [<ffffffffa0672c32>] rtl8xxxu_init_phy_rf+0x152/0x240 [rtl8xxxu]
[52347.751451] [<ffffffffa0676c89>] rtl8192cu_init_phy_rf+0x69/0x70 [rtl8xxxu]
[52347.751453] [<ffffffffa06783ac>] rtl8xxxu_init_device.isra.36+0x57c/0x14d0
[rtl8xxxu]
[52347.751456] [<ffffffff815146a8>] ? release_firmware+0x58/0x70
[52347.751458] [<ffffffffa067a0d5>] rtl8xxxu_probe+0xdd5/0x1130 [rtl8xxxu]
[52347.751461] [<ffffffff815829a8>] usb_probe_interface+0x1c8/0x310
[52347.751463] [<ffffffff814ff507>] driver_probe_device+0x247/0x460
--snip--
[52347.751487] [<ffffffff811899ea>] do_init_module+0x60/0x1ee
[52347.751489] [<ffffffff81108e51>] load_module+0x1ee1/0x2830
[52347.751491] [<ffffffff81105230>] ? __symbol_put+0x50/0x50
[52347.751493] [<ffffffff811098d9>] SyS_init_module+0x139/0x180
[52347.751495] [<ffffffff81776c17>] entry_SYSCALL_64_fastpath+0x12/0x6f
[52347.751498] usb 3-6: Failed to initialize RF
Perhaps you can recognize what is wrong.
Larry
Jes Sorensen <[email protected]> writes:
> Larry Finger <[email protected]> writes:
>> On 02/04/2016 10:45 AM, Jes Sorensen wrote:
>>> Drunk Cat <[email protected]> writes:
>>>> problem: it does not connect to any wifi network you can see the time out on
>>>> dmesg
>>>>
>>>>
>>>>> lsusb
>>>>
>>>> Bus 002 Device 007: ID 0bda:817f Realtek Semiconductor Corp. RTL8188RU
>>>> 802.11n WLAN Adapter
>>>>
>>>>> iwconfig
>>>> wlp0s20u1 IEEE 802.11bgn ESSID:off/any
>>>> Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
>>>> Retry short limit:7 RTS thr=2347 B Fragment thr:off
>>>> Power Management:off
>>>>> dmesg
>>>
>>> Not sure what distribution you are running, but I am seeing problems
>>> with NetworkManager in recent Fedora.
>>>
>>> Could you try the following:
>>> 1) Unplug the WiFi dongle
>>> 2) (Re)load the driver (rmmod rtl8xxxu ; insmod rtl8xxxu)
>>> 3) Restart NetworkManager 'systemctl restart NetworkManager'
>>> 4) Plug in the WiFi dongle
>>
>> Jes,
>>
>> I can confirm what Drunk Cat sees. There is something different about
>> the RTL8192RU as using the iwconfig utility shows no APs in the
>> scan. I hope to get to debugging the problem soon.
>
> OK - thats unfortunate. Most likely the wrong antenna path is being
> enabled for it, or something like that.
>
> Once I finish up the 8723bu/8192eu patchset, I'll try to find some time
> to look at it, if you don't nail it before.
One more time with the actual patch ...
Jes
On 02/09/2016 03:00 PM, Jes Sorensen wrote:
> Jes Sorensen <[email protected]> writes:
>> Larry Finger <[email protected]> writes:
>>> On 02/04/2016 10:45 AM, Jes Sorensen wrote:
>>>> Drunk Cat <[email protected]> writes:
>>>>> problem: it does not connect to any wifi network you can see the time out on
>>>>> dmesg
>>>>>
>>>>>
>>>>>> lsusb
>>>>>
>>>>> Bus 002 Device 007: ID 0bda:817f Realtek Semiconductor Corp. RTL8188RU
>>>>> 802.11n WLAN Adapter
>>>>>
>>>>>> iwconfig
>>>>> wlp0s20u1 IEEE 802.11bgn ESSID:off/any
>>>>> Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
>>>>> Retry short limit:7 RTS thr=2347 B Fragment thr:off
>>>>> Power Management:off
>>>>>> dmesg
>>>>
>>>> Not sure what distribution you are running, but I am seeing problems
>>>> with NetworkManager in recent Fedora.
>>>>
>>>> Could you try the following:
>>>> 1) Unplug the WiFi dongle
>>>> 2) (Re)load the driver (rmmod rtl8xxxu ; insmod rtl8xxxu)
>>>> 3) Restart NetworkManager 'systemctl restart NetworkManager'
>>>> 4) Plug in the WiFi dongle
>>>
>>> Jes,
>>>
>>> I can confirm what Drunk Cat sees. There is something different about
>>> the RTL8192RU as using the iwconfig utility shows no APs in the
>>> scan. I hope to get to debugging the problem soon.
>>
>> OK - thats unfortunate. Most likely the wrong antenna path is being
>> enabled for it, or something like that.
>>
>> Once I finish up the 8723bu/8192eu patchset, I'll try to find some time
>> to look at it, if you don't nail it before.
>
> One more time with the actual patch ...
No help. The name of the patch makes it sound as if it is for a 1T2R device. The
RTL8188RU is 1x1.
Larry
Larry Finger <[email protected]> writes:
> On 02/09/2016 03:00 PM, Jes Sorensen wrote:
>> Jes Sorensen <[email protected]> writes:
>>> Larry Finger <[email protected]> writes:
>>>> I can confirm what Drunk Cat sees. There is something different about
>>>> the RTL8192RU as using the iwconfig utility shows no APs in the
>>>> scan. I hope to get to debugging the problem soon.
>>>
>>> OK - thats unfortunate. Most likely the wrong antenna path is being
>>> enabled for it, or something like that.
>>>
>>> Once I finish up the 8723bu/8192eu patchset, I'll try to find some time
>>> to look at it, if you don't nail it before.
>>
>> One more time with the actual patch ...
>
> No help. The name of the patch makes it sound as if it is for a 1T2R
> device. The RTL8188RU is 1x1.
Darn, I didn't have an 8188RU near me when I discovered that bug and so
I wasn't sure if it was 1T2R or 1T1R. All my other 1T1R parts work
fine with the current code.
Cheers,
Jes
Larry Finger <[email protected]> writes:
> On 02/10/2016 06:01 AM, dsadsa sadsad wrote:
>> So do i have to patch and recompile or not?
>
> It will not change a thing for the AWUS036NHR. It will fix a bug in
> 1T2R devices.
After pulling my hairs out over this one for days (if not weeks), I
think I finally figured it out.
I just pushed a patch into the rtl8xxxu-nextgen repository which makes
the AWUS036NHR v2 work for me.
Jes
Drunk Cat <[email protected]> writes:
> problem: it does not connect to any wifi network you can see the time out on
> dmesg
>
>
>>lsusb
>
> Bus 002 Device 007: ID 0bda:817f Realtek Semiconductor Corp. RTL8188RU
> 802.11n WLAN Adapter
>
>>iwconfig
> wlp0s20u1 IEEE 802.11bgn ESSID:off/any
> Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
> Retry short limit:7 RTS thr=2347 B Fragment thr:off
> Power Management:off
>>dmesg
Not sure what distribution you are running, but I am seeing problems
with NetworkManager in recent Fedora.
Could you try the following:
1) Unplug the WiFi dongle
2) (Re)load the driver (rmmod rtl8xxxu ; insmod rtl8xxxu)
3) Restart NetworkManager 'systemctl restart NetworkManager'
4) Plug in the WiFi dongle
Thanks,
Jes
On 02/04/2016 11:41 AM, Jes Sorensen wrote:
> Larry Finger <[email protected]> writes:
>> On 02/04/2016 10:45 AM, Jes Sorensen wrote:
>>> Drunk Cat <[email protected]> writes:
>>>> problem: it does not connect to any wifi network you can see the time out on
>>>> dmesg
>>>>
>>>>
>>>>> lsusb
>>>>
>>>> Bus 002 Device 007: ID 0bda:817f Realtek Semiconductor Corp. RTL8188RU
>>>> 802.11n WLAN Adapter
>>>>
>>>>> iwconfig
>>>> wlp0s20u1 IEEE 802.11bgn ESSID:off/any
>>>> Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
>>>> Retry short limit:7 RTS thr=2347 B Fragment thr:off
>>>> Power Management:off
>>>>> dmesg
>>>
>>> Not sure what distribution you are running, but I am seeing problems
>>> with NetworkManager in recent Fedora.
>>>
>>> Could you try the following:
>>> 1) Unplug the WiFi dongle
>>> 2) (Re)load the driver (rmmod rtl8xxxu ; insmod rtl8xxxu)
>>> 3) Restart NetworkManager 'systemctl restart NetworkManager'
>>> 4) Plug in the WiFi dongle
>>
>> Jes,
>>
>> I can confirm what Drunk Cat sees. There is something different about
>> the RTL8192RU as using the iwconfig utility shows no APs in the
>> scan. I hope to get to debugging the problem soon.
>
> OK - thats unfortunate. Most likely the wrong antenna path is being
> enabled for it, or something like that.
>
> Once I finish up the 8723bu/8192eu patchset, I'll try to find some time
> to look at it, if you don't nail it before.
It definitely is an antenna path problem. I finally got a few scans with signal
levels in the -100 dBm range.
Larry
On 02/28/2016 05:01 PM, Jes Sorensen wrote:
> Larry Finger <[email protected]> writes:
>> On 02/10/2016 06:01 AM, dsadsa sadsad wrote:
>>> So do i have to patch and recompile or not?
>>
>> It will not change a thing for the AWUS036NHR. It will fix a bug in
>> 1T2R devices.
>
> After pulling my hairs out over this one for days (if not weeks), I
> think I finally figured it out.
>
> I just pushed a patch into the rtl8xxxu-nextgen repository which makes
> the AWUS036NHR v2 work for me.
Jes,
On my unit, which seems to be V1, things are worse. The logged output is
[ 31.833290] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 31.833292] usb 3-6: Product: ALFA AWUS036NHR
[ 31.833294] usb 3-6: SerialNumber: 00e04c000001
[ 32.066835] fuse init (API version 7.24)
[ 33.201094] usb 3-6: Vendor: ^R^CALFA
[ 33.201097] usb 3-6: Product: US036NHR
[ 33.201099] usb 3-6: rtl8192cu_parse_efuse: dumping efuse (0x80 bytes):
[ 33.201101] usb 3-6: 00: 29 81 00 74 cd 00 00 00
[ 33.201102] usb 3-6: 08: ff 00 da 0b 7f 81 03 41
[ 33.201103] usb 3-6: 10: 32 00 85 62 9e ad 00 c0
[ 33.201105] usb 3-6: 18: ca 52 c3 c9 02 03 12 03
[ 33.201106] usb 3-6: 20: 41 4c 46 41 20 20 41 57
[ 33.201107] usb 3-6: 28: 55 53 30 33 36 4e 48 52
[ 33.201108] usb 3-6: 30: 00 00 00 00 00 00 00 00
[ 33.201110] usb 3-6: 38: 00 00 00 00 00 00 00 00
[ 33.201111] usb 3-6: 40: 00 00 00 00 00 00 00 00
[ 33.201112] usb 3-6: 48: 00 00 00 00 00 00 00 00
[ 33.201113] usb 3-6: 50: 00 00 00 00 00 00 00 00
[ 33.201114] usb 3-6: 58: 06 00 19 19 19 00 00 00
[ 33.201116] usb 3-6: 60: 27 26 25 00 00 00 00 00
[ 33.201117] usb 3-6: 68: 00 00 00 00 00 00 00 00
[ 33.201118] usb 3-6: 70: 00 00 00 00 00 0a 40 00
[ 33.201119] usb 3-6: 78: 0e 20 00 00 36 00 04 00
[ 33.201121] usb 3-6: RTL8188RU rev A (TSMC) 1T1R, TX queues 2, WiFi=1, BT=0,
GPS=0, HI PA=1
[ 33.201122] usb 3-6: RTL8188RU MAC: 00:c0:ca:52:c3:c9
[ 33.201124] usb 3-6: rtl8xxxu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
[ 33.203491] usb 3-6: Firmware revision 80.0 (signature 0x88c1)
[ 33.348885] usb 3-6: Failed to initialize RF
[ 33.661460] usbcore: registered new interface driver rtl8xxxu
[ 33.675077] rtl8xxxu 3-6:1.0 wlp0s20u6: renamed from wlan0
[ 33.749780] usb 3-6: rtl8xxxu_int_complete: Error -71
Larry
On 02/10/2016 06:01 AM, dsadsa sadsad wrote:
> So do i have to patch and recompile or not?
It will not change a thing for the AWUS036NHR. It will fix a bug in 1T2R devices.
Larry
Larry Finger <[email protected]> writes:
> On 02/28/2016 05:01 PM, Jes Sorensen wrote:
>> Larry Finger <[email protected]> writes:
>>> On 02/10/2016 06:01 AM, dsadsa sadsad wrote:
>>>> So do i have to patch and recompile or not?
>>>
>>> It will not change a thing for the AWUS036NHR. It will fix a bug in
>>> 1T2R devices.
>>
>> After pulling my hairs out over this one for days (if not weeks), I
>> think I finally figured it out.
>>
>> I just pushed a patch into the rtl8xxxu-nextgen repository which makes
>> the AWUS036NHR v2 work for me.
>
> Jes,
>
> On my unit, which seems to be V1, things are worse. The logged output is
>
> [ 31.833290] usb 3-6: New USB device strings: Mfr=1, Product=2, SerialNumber=3
> [ 31.833292] usb 3-6: Product: ALFA AWUS036NHR
> [ 31.833294] usb 3-6: SerialNumber: 00e04c000001
> [ 32.066835] fuse init (API version 7.24)
> [ 33.201094] usb 3-6: Vendor: ^R^CALFA
> [ 33.201097] usb 3-6: Product: US036NHR
> [ 33.201099] usb 3-6: rtl8192cu_parse_efuse: dumping efuse (0x80 bytes):
> [ 33.201101] usb 3-6: 00: 29 81 00 74 cd 00 00 00
> [ 33.201102] usb 3-6: 08: ff 00 da 0b 7f 81 03 41
> [ 33.201103] usb 3-6: 10: 32 00 85 62 9e ad 00 c0
> [ 33.201105] usb 3-6: 18: ca 52 c3 c9 02 03 12 03
> [ 33.201106] usb 3-6: 20: 41 4c 46 41 20 20 41 57
> [ 33.201107] usb 3-6: 28: 55 53 30 33 36 4e 48 52
> [ 33.201108] usb 3-6: 30: 00 00 00 00 00 00 00 00
> [ 33.201110] usb 3-6: 38: 00 00 00 00 00 00 00 00
> [ 33.201111] usb 3-6: 40: 00 00 00 00 00 00 00 00
> [ 33.201112] usb 3-6: 48: 00 00 00 00 00 00 00 00
> [ 33.201113] usb 3-6: 50: 00 00 00 00 00 00 00 00
> [ 33.201114] usb 3-6: 58: 06 00 19 19 19 00 00 00
> [ 33.201116] usb 3-6: 60: 27 26 25 00 00 00 00 00
> [ 33.201117] usb 3-6: 68: 00 00 00 00 00 00 00 00
> [ 33.201118] usb 3-6: 70: 00 00 00 00 00 0a 40 00
> [ 33.201119] usb 3-6: 78: 0e 20 00 00 36 00 04 00
> [ 33.201121] usb 3-6: RTL8188RU rev A (TSMC) 1T1R, TX queues 2,
> WiFi=1, BT=0, GPS=0, HI PA=1
> [ 33.201122] usb 3-6: RTL8188RU MAC: 00:c0:ca:52:c3:c9
> [ 33.201124] usb 3-6: rtl8xxxu: Loading firmware rtlwifi/rtl8192cufw_TMSC.bin
> [ 33.203491] usb 3-6: Firmware revision 80.0 (signature 0x88c1)
> [ 33.348885] usb 3-6: Failed to initialize RF
> [ 33.661460] usbcore: registered new interface driver rtl8xxxu
> [ 33.675077] rtl8xxxu 3-6:1.0 wlp0s20u6: renamed from wlan0
> [ 33.749780] usb 3-6: rtl8xxxu_int_complete: Error -71
That one I have never seen before - could you try and insert some debug
prints to see where the RF initialization fails?
Cheers,
Jes
On 02/04/2016 10:45 AM, Jes Sorensen wrote:
> Drunk Cat <[email protected]> writes:
>> problem: it does not connect to any wifi network you can see the time out on
>> dmesg
>>
>>
>>> lsusb
>>
>> Bus 002 Device 007: ID 0bda:817f Realtek Semiconductor Corp. RTL8188RU
>> 802.11n WLAN Adapter
>>
>>> iwconfig
>> wlp0s20u1 IEEE 802.11bgn ESSID:off/any
>> Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
>> Retry short limit:7 RTS thr=2347 B Fragment thr:off
>> Power Management:off
>>> dmesg
>
> Not sure what distribution you are running, but I am seeing problems
> with NetworkManager in recent Fedora.
>
> Could you try the following:
> 1) Unplug the WiFi dongle
> 2) (Re)load the driver (rmmod rtl8xxxu ; insmod rtl8xxxu)
> 3) Restart NetworkManager 'systemctl restart NetworkManager'
> 4) Plug in the WiFi dongle
Jes,
I can confirm what Drunk Cat sees. There is something different about the
RTL8192RU as using the iwconfig utility shows no APs in the scan. I hope to get
to debugging the problem soon.
Larry
Larry Finger <[email protected]> writes:
> On 02/04/2016 10:45 AM, Jes Sorensen wrote:
>> Drunk Cat <[email protected]> writes:
>>> problem: it does not connect to any wifi network you can see the time out on
>>> dmesg
>>>
>>>
>>>> lsusb
>>>
>>> Bus 002 Device 007: ID 0bda:817f Realtek Semiconductor Corp. RTL8188RU
>>> 802.11n WLAN Adapter
>>>
>>>> iwconfig
>>> wlp0s20u1 IEEE 802.11bgn ESSID:off/any
>>> Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
>>> Retry short limit:7 RTS thr=2347 B Fragment thr:off
>>> Power Management:off
>>>> dmesg
>>
>> Not sure what distribution you are running, but I am seeing problems
>> with NetworkManager in recent Fedora.
>>
>> Could you try the following:
>> 1) Unplug the WiFi dongle
>> 2) (Re)load the driver (rmmod rtl8xxxu ; insmod rtl8xxxu)
>> 3) Restart NetworkManager 'systemctl restart NetworkManager'
>> 4) Plug in the WiFi dongle
>
> Jes,
>
> I can confirm what Drunk Cat sees. There is something different about
> the RTL8192RU as using the iwconfig utility shows no APs in the
> scan. I hope to get to debugging the problem soon.
OK - thats unfortunate. Most likely the wrong antenna path is being
enabled for it, or something like that.
Once I finish up the 8723bu/8192eu patchset, I'll try to find some time
to look at it, if you don't nail it before.
Cheers,
Jes
Jes Sorensen <[email protected]> writes:
> Larry Finger <[email protected]> writes:
>> On 02/04/2016 10:45 AM, Jes Sorensen wrote:
>>> Drunk Cat <[email protected]> writes:
>>>> problem: it does not connect to any wifi network you can see the time out on
>>>> dmesg
>>>>
>>>>
>>>>> lsusb
>>>>
>>>> Bus 002 Device 007: ID 0bda:817f Realtek Semiconductor Corp. RTL8188RU
>>>> 802.11n WLAN Adapter
>>>>
>>>>> iwconfig
>>>> wlp0s20u1 IEEE 802.11bgn ESSID:off/any
>>>> Mode:Managed Access Point: Not-Associated Tx-Power=20 dBm
>>>> Retry short limit:7 RTS thr=2347 B Fragment thr:off
>>>> Power Management:off
>>>>> dmesg
>>>
>>> Not sure what distribution you are running, but I am seeing problems
>>> with NetworkManager in recent Fedora.
>>>
>>> Could you try the following:
>>> 1) Unplug the WiFi dongle
>>> 2) (Re)load the driver (rmmod rtl8xxxu ; insmod rtl8xxxu)
>>> 3) Restart NetworkManager 'systemctl restart NetworkManager'
>>> 4) Plug in the WiFi dongle
>>
>> Jes,
>>
>> I can confirm what Drunk Cat sees. There is something different about
>> the RTL8192RU as using the iwconfig utility shows no APs in the
>> scan. I hope to get to debugging the problem soon.
>
> OK - thats unfortunate. Most likely the wrong antenna path is being
> enabled for it, or something like that.
>
> Once I finish up the 8723bu/8192eu patchset, I'll try to find some time
> to look at it, if you don't nail it before.
Larry,
Does this patch make any difference?
Cheers,
Jes
Larry Finger <[email protected]> writes:
> On 02/29/2016 06:28 AM, Jes Sorensen wrote:
>> That one I have never seen before - could you try and insert some debug
>> prints to see where the RF initialization fails?
>
> The call to usb_control_msg() is returning -EPROTO (-71), but
> sometimes the system works. I added the following patch:
>
> diff --git a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c
> b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c
> index 38aa3c2..8ab77a0 100644
> --- a/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c
> +++ b/drivers/net/wireless/realtek/rtl8xxxu/rtl8xxxu.c
> @@ -1979,9 +1979,12 @@ static int rtl8xxxu_write_rfreg(struct rtl8xxxu_priv *priv,
>
> /* Use XB for path B */
> ret = rtl8xxxu_write32(priv, rtl8xxxu_rfregs[path].lssiparm, dataaddr);
> - if (ret != sizeof(dataaddr))
> + if (ret != sizeof(dataaddr)) {
> + pr_info("**** rtl8xxxu_write32() error %d: path %d,
> reg: 0x%x, data 0x%x, dataaddr 0x%x, lssiparm 0x%x\n",
> + ret, path, reg, data, dataaddr,
> rtl8xxxu_rfregs[path].lssiparm);
> + dump_stack();
> retval = -EIO;
> - else
> + } else
> retval = 0;
>
> udelay(1);
>
> When the error happens, my log contains
Odd, I wonder if my code writes the reigsters out to the device too
fast. You could try adding a call to read back the RF register before
exiting the function - preferably after the udelay().
Cheers,
Jes