[ET10x00] USB Wi-FI issues with the new Kernel upgrade on 4.2.027

[Joe_90]

No - he's referring to the 8192cu.ko module (no rtl prefix). I think that module has been used on some other machine builds.

 

[birdman]

@birdman - where are you seeing that it is using 8192cu.ko?

I'm looking at the files distributed with the image.
What gets build for 8192cu depends on whether linuxwifi is defined as a feature for the kernel. For 4.0.1 it wasn't, but for 4.8.3 it is.

So looking at the files in the 4.2.026 image for the e10k I can see:
image/lib/modules/4.0.1/kernel/drivers/net/wireless/8192cu.ko

but looking at the 4.2.027 image I see:
image/lib/modules/4.8.3/kernel/drivers/net/wireless/realtek/rtlwifi/rtl8192cu/rtl8192cu.ko

Which is why the dmesg outputs in #2 differ.

 

[Joe_90]

dmesg in both 026 and 028 is showing usage of the rtl8192cu.ko module. There's no reference to 8192cu.ko in either that I can see so I assume it's not using it although it may well be present.

Are you saying that there is no rtl8192cu.ko module in the 026 image? I'm not clear on whether both modules are there in 026. If not, then the 8192cu.ko module is announcing itself as rtl8192cu which is confusing at best.

 

[ccs]

modinfo 026 .....

root@et10000:~# modinfo 8192cu
filename:       /lib/modules/4.0.1/kernel/drivers/net/wireless/8192cu.ko
version:        v4.0.2_9000.20130911
author:         Realtek Semiconductor Corp.
description:    Realtek Wireless Lan Driver
license:        GPL
srcversion:     37A6B9EE78BDC75F69387A6
alias:          usb:v0BDAp8186d*dc*dsc*dp*ic*isc*ip*in*
.
.
.
alias:          usb:v0BDAp8191d*dc*dsc*dp*ic*isc*ip*in*
depends:
vermagic:       4.0.1 SMP mod_unload modversions BMIPS 32BIT
parm:           rtw_ips_mode:The default IPS mode (int)
parm:           ifname:The default name to allocate for first interface (charp)
parm:           if2name:The default name to allocate for second interface (charp)
parm:           rtw_initmac:charp
parm:           rtw_channel_plan:int
parm:           rtw_chip_version:int
parm:           rtw_rfintfs:int
parm:           rtw_lbkmode:int
parm:           rtw_network_mode:int
parm:           rtw_channel:int
parm:           rtw_mp_mode:int
parm:           rtw_wmm_enable:int
parm:           rtw_vrtl_carrier_sense:int
parm:           rtw_vcs_type:int
parm:           rtw_busy_thresh:int
parm:           rtw_ht_enable:int
parm:           rtw_cbw40_enable:int
parm:           rtw_ampdu_enable:int
parm:           rtw_rx_stbc:int
parm:           rtw_ampdu_amsdu:int
parm:           rtw_lowrate_two_xmit:int
parm:           rtw_rf_config:int
parm:           rtw_power_mgnt:int
parm:           rtw_low_power:int
parm:           rtw_wifi_spec:int
parm:           rtw_special_rf_path:int
parm:           rtw_antdiv_cfg:int
parm:           rtw_enusbss:int
parm:           rtw_hwpdn_mode:int
parm:           rtw_hwpwrp_detect:int
parm:           rtw_hw_wps_pbc:int
parm:           rtw_max_roaming_times:The max roaming times to try (uint)
parm:           rtw_force_iol:Force to enable IOL (bool)
parm:           rtw_mc2u_disable:int
parm:           rtw_mac_phy_mode:int
parm:           rtw_80211d:int
parm:           rtw_notch_filter:0:Disable, 1:Enable, 2:Enable only for P2P (uint)
root@et10000:~#

 

[birdman]

dmesg in both 026 and 028 is showing usage of the rtl8192cu.ko module.

No, it's not. It's showing the use of a module for rtl8192cu. It doesn't mention the file name. See the modinfo details in #24.

 

[ccs]

Added samba - very clunky - one telnet "cat" session is now stopping and starting every few seconds.

I don't really think samba is the cause, it just makes it appear worse, if that makes sense.

If anything, it seems to get progressively worse as time goes on.

'028+wireless+absolutely nothing else' was switched on for some time this morning. I then tried ping as another test, and it was very slow.

Traceroute is ok.

 

[Joe_90]

modinfo 026 .....

root@et10000:~# modinfo 8192cu
filename:       /lib/modules/4.0.1/kernel/drivers/net/wireless/8192cu.ko
version:        v4.0.2_9000.20130911
author:         Realtek Semiconductor Corp.
description:    Realtek Wireless Lan Driver
license:        GPL
srcversion:     37A6B9EE78BDC75F69387A6
alias:          usb:v0BDAp8186d*dc*dsc*dp*ic*isc*ip*in*
.
.
.
alias:          usb:v0BDAp8191d*dc*dsc*dp*ic*isc*ip*in*
depends:
vermagic:       4.0.1 SMP mod_unload modversions BMIPS 32BIT
parm:           rtw_ips_mode:The default IPS mode (int)
parm:           ifname:The default name to allocate for first interface (charp)
parm:           if2name:The default name to allocate for second interface (charp)
parm:           rtw_initmac:charp
parm:           rtw_channel_plan:int
parm:           rtw_chip_version:int
parm:           rtw_rfintfs:int
parm:           rtw_lbkmode:int
parm:           rtw_network_mode:int
parm:           rtw_channel:int
parm:           rtw_mp_mode:int
parm:           rtw_wmm_enable:int
parm:           rtw_vrtl_carrier_sense:int
parm:           rtw_vcs_type:int
parm:           rtw_busy_thresh:int
parm:           rtw_ht_enable:int
parm:           rtw_cbw40_enable:int
parm:           rtw_ampdu_enable:int
parm:           rtw_rx_stbc:int
parm:           rtw_ampdu_amsdu:int
parm:           rtw_lowrate_two_xmit:int
parm:           rtw_rf_config:int
parm:           rtw_power_mgnt:int
parm:           rtw_low_power:int
parm:           rtw_wifi_spec:int
parm:           rtw_special_rf_path:int
parm:           rtw_antdiv_cfg:int
parm:           rtw_enusbss:int
parm:           rtw_hwpdn_mode:int
parm:           rtw_hwpwrp_detect:int
parm:           rtw_hw_wps_pbc:int
parm:           rtw_max_roaming_times:The max roaming times to try (uint)
parm:           rtw_force_iol:Force to enable IOL (bool)
parm:           rtw_mc2u_disable:int
parm:           rtw_mac_phy_mode:int
parm:           rtw_80211d:int
parm:           rtw_notch_filter:0:Disable, 1:Enable, 2:Enable only for P2P (uint)
root@et10000:~#

Thanks ccs - that's new information and @birdman has commented on it. The modinfo in post #4 doesn't reference the 8192cu.ko file at all (presumably because it was run on 028?). It would seem that the two files actually contain different driver code. The fact that dmesg is showing the use of the rtl8192cu driver in both 026 and 028 is masking the fact that different files have been used. I would have thought that it would be good practice to match the filename to the module, but there you are...
Those rtl8192cu wifi dongles don't all seem to behave in the manner expected. Mine will work with the generic rtl8xxxcu driver up to the point of establishing a crypto handshake with the router and then immediately lock up. So I had to go back to the actual rtl8192cu driver. In your case you may have to install the 8192cu.ko driver.

 

[ccs]

In your case you may have to install the 8192cu.ko driver.

This is where I start to struggle.
I can see how to uninstall the driver on 4.8.3, but were is the 4.0.1 driver to put back?.
I'm assuming it needs to be uninstalled/installed, not me just overwriting rtl8192cu.ko with 8192cu.ko ?

 

[ccs]

Would this be a start (on 026)....

root@et10000:/media/hdd/tmp# [COLOR="#0000FF"]opkg list|grep 8192cu[/COLOR]
enigma2-plugin-drivers-network-usb-rtl8192cu - 1.0-r5 - new universal rt18xxx kernel driver  new universal rt18xxx kernel driver.
enigma2-plugin-drivers-network-usb-rtl8192cu-dbg - 1.0-r5 - new universal rt18xxx kernel driver - Debugging files  new universal
enigma2-plugin-drivers-network-usb-rtl8192cu-dev - 1.0-r5 - new universal rt18xxx kernel driver - Development files  new universal
enigma2-plugin-drivers-network-usb-rtl8192cu-rev2 - 1.0-r5 - rt8192cu Proprietary alternative kernel driver  rt8192cu Proprietary
enigma2-plugin-drivers-network-usb-rtl8192cu-rev2-dbg - 1.0-r5 - rt8192cu Proprietary alternative kernel driver - Debugging files
 rt8192cu Proprietary alternative kernel driver.  This package contains
enigma2-plugin-drivers-network-usb-rtl8192cu-rev2-dev - 1.0-r5 - rt8192cu Proprietary alternative kernel driver - Development files
 rt8192cu Proprietary alternative kernel driver.  This package contains
firmware-rtl8192cu - 1.0-r0 - Firmware for RTL8192CU  Firmware for RTL8192CU.
firmware-rtl8192cufw - 1.0-r0 - Firmware for rtl8192cufw_TMSC  Firmware for rtl8192cufw_TMSC.
kernel-module-8192cu - 4.0.2-r4 - 8192cu kernel module  8192cu kernel module; Realtek Wireless Lan Driver
kernel-module-rtl8192cu - 4.0.1-r0.4 - rtl8192cu kernel module  rtl8192cu kernel module; Realtek 8192C/8188C
rtl8192cu - 4.0.2-r4 - Driver for Realtek USB wireless devices  Driver for Realtek USB wireless
rtl8192cu-dbg - 4.0.2-r4 - Driver for Realtek USB wireless devices - Debugging files  Driver for
rtl8192cu-dev - 4.0.2-r4 - Driver for Realtek USB wireless devices - Development files  Driver for

Nothing wants to download eg

root@et10000:~# opkg download enigma2-plugin-drivers-network-usb-rtl8192cu-rev2
Downloading http://www.openvix.co.uk/feeds/open...ers-network-usb-rtl8192cu-rev2_1.0-r5_all.ipk.
Removing corrupt package file /var/cache/opkg/bc4e010ee86896c4f5f873000a0ea68e_enigma2-plugin-drivers-network-usb-rtl8192cu-rev2_1.0-r5_all.ipk.
Collected errors:
* opkg_download_cmd: Failed to download enigma2-plugin-drivers-network-usb-rtl8192cu-rev2.

 

[birdman]

The fact that dmesg is showing the use of the rtl8192cu driver in both 026 and 028 is masking the fact that different files have been used. I would have thought that it would be good practice to match the filename to the module, but there you are...

It's saying that it has added a driver for the rtl8192cu chipset. It doesn't mention filenames at all (you could name the file anything you wish and still load it).

Those rtl8192cu wifi dongles don't all seem to behave in the manner expected. Mine will work with the generic rtl8xxxcu driver up to the point of establishing a crypto handshake with the router and then immediately lock up. So I had to go back to the actual rtl8192cu driver. In your case you may have to install the 8192cu.ko driver.

Remember that it's not just USB Wifi dongles which have an issue with the 4.8.3 kernel on Xtrend boxes - it's USB tuners (Sundtek and PC-TV) as well. There are a number of options:

• Stay on 4.8.3, but switch off the linuxwifi option - unlikely to help the USB tuners
• Switch back to the 4.0.1 kernel for all Xtrend boxes - but presumably any new Xtrend box/fix will use 4.8.3, so the problem may recur there if the root cause isn't investigated here.

 

[ccs]

Nothing wants to download.

Good old opkg update does the trick.


root@et10000:/media/hdd/tmp# opkg download enigma2-plugin-drivers-network-usb-rtl8192cu-rev2
Downloaded enigma2-plugin-drivers-network-usb-rtl8192cu-rev2 as enigma2-plugin-drivers-network-usb-rtl8192cu-rev2_1.0-r5_all.ipk.
root@et10000:/media/hdd/tmp#

Anyway, I can't image installing that on 028 will work/is advisable?

There's firmware-rtl8192cu - 1.0-r0, firmware-rtl8192cufw - 1.0-r0 and kernel-module-8192cu - 4.0.2-r4 to worry about as well?

 

[birdman]

Good old opkg update does the trick.


root@et10000:/media/hdd/tmp# opkg download enigma2-plugin-drivers-network-usb-rtl8192cu-rev2
Downloaded enigma2-plugin-drivers-network-usb-rtl8192cu-rev2 as enigma2-plugin-drivers-network-usb-rtl8192cu-rev2_1.0-r5_all.ipk.
root@et10000:/media/hdd/tmp#

Anyway, I can't image installing that on 028 will work/is advisable?

rtl8192cu-rev2 is (or should be) the one installed on the image by default.
The other one is an rtl8xxxu driver.

 

[ccs]

rtl8192cu-rev2 is (or should be) the one installed on the image by default.
The other one is an rtl8xxxu driver.

Yes, that's about the only thing I have worked out.
I wondered if I downloaded from 026 I could reinstall it on 028, but something tells me no chance.

If there's anything I can try out, please let me know.

 

[ccs]

I don't think anything has changed, image-wise, so usb wireless rtl8192cu on 4.2.029 is still very slow, confirmed by ping.

 

[ccs]

Looking at ping a bit more...

Most of the time 029 (2ms to 3ms) is about 3 times faster that 026 (6ms to 7ms), but has occasional bad spells, and some Destination host unreachable's.

026 has the odd poorish spell as well and averages 11ms.

029 averages 62ms.

 

[birdman]

I don't think anything has changed, image-wise

There was one driver used with kernel 4.0.1, and a different one with kernel 4.8.3.
There are also USB tuner issues with the 4.8.3 kernel (they don't work at all).

 

[ccs]

There was one driver used with kernel 4.0.1, and a different one with kernel 4.8.3.
There are also USB tuner issues with the 4.8.3 kernel (they don't work at all).

I know, I was referring to moving from 028 to 029.

 

[ccs]

Ping is now 10 times faster on 4.2.030 than it was on 4.2.029.

Has anything changed?

 

[ccs]

Playback of a recording on a Fire TV with Kodi appears to be ok as well, apart from one thing.

A (Kodi) information message is permanently onscreen, VU+/Enigma2 client - connection lost.

It stays on for about 10 seconds, momentarily goes off, and then is back again. But playback is not affected (as far I can see/hear).

 

[ccs]

Krypton 17 seems to have got rid of the connection lost message. (It is configurable, and can be permanently switched off, although I haven't(yet))