R8188eu drivers

Hello all,
i wonna ask what driver is available in osmc RC3 for the chipset in object.

When kernel 3.18.x arrived on raspberry, a driver for r8188eu was inserted in it (missing only the firmware file), but it was RUBBISH and we all with this chipset use drivers compiled elsewhere (link to raspberry forum topic: (UPDATE) Drivers for TL-WN725N V2 - 3.6.11+ -> 4.xx.xx+ - Raspberry Pi Forums )

Now, i suspect in osmc there is the first option.
Why?
Look at this:

wlan0 IEEE 802.11bgn ESSID:“SpringfieldG” Nickname:“WIFI@REALTEK
Mode:Managed Frequency:2.437 GHz Access Point: A0:21:B7:AC:DA:2F
Bit Rate:150 Mb/s Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=0/100 Signal level=7/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

in the meantime, 10 cm further, my raspi 2b with the SAME chipset (and compiled drivers) says this:

wlan0 IEEE 802.11bgn ESSID:“SpringfieldG” Nickname:“WIFI@REALTEK
Mode:Managed Frequency:2.437 GHz Access Point: A0:21:B7:AC:DA:2F
Bit Rate:150 Mb/s Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Power Management:off
Link Quality=100/100 Signal level=98/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

and this is EXACTLY the same behaviour seen on raspbian…

can we do something about this? :slight_smile:

Will fix. Already took measures (out of tree builds) to deal with 8192cu issues, will do it for the other Realtek dongles too.

Sam

But, does one actually perform any better than the other in terms of actual performance (measured throughput) and reliability ?

You realise that a driver can’t affect received signal strength, right ? It can only report it differently (or completely incorrectly as above) but that doesn’t necessarily mean it will cause you issues actually using it. There are a few linux wifi drivers that do not report signal strength correctly to the OS but still work fine anyway.

(Obviously we still want the best drivers we can in OSMC of course, but I just had to point out that reported signal strength is not the be all and end all because its equally easy to falsify or give inaccurate readings in the “suspiciously strong” direction too…)

a simple ssh session with the first driver fall down every minute or so.
with the second driver it’s rock solid for hours
they can tell me all the numbers they want, but in this case performance is MUCH different.

Fair enough, if the performance is much better that is definitely worth doing.

1 Like

Just to save my Raspberry from being kicked out of the window, i’m now using a RT5370 wifi dongle and this is MUCH more reliable.
I really hope realtek drivers will get fixed soon :frowning:

Realtek RTL-8188eu OSMC driver works fine here.
I can confirm that the Link Quality and Signal level indication are broken, but the driver works as expected and the wifi link speed (file transfer via samba share) is about 2.2-2.5 MB/s and there aren’t connennection drop-outs anymore. I have had serious connection dropout problems in the past, but now the wifi dongle works well (thank you DBMandrake :smile:).

My setup: OSMC RC3 and Raspberry pi 2, wifi dongle TP-LINK TP-725N v2 (chipset 8188eu).

Cheers

Ouch 2.5 MB/s isn’t that good. I use the same Wi-Fi dongle and get about 6-7 MB/s one time even 11.3 MB/s (But my router wasn’t hit as hard by multiple devices at the time)

If I remember correctly I got your speeds before setting max_usb_current so you may want to do that.

As for the drivers I would like them updated. Just because my Wi-FI works most of the time for raw Bluray doesn’t mean it couldn’t be better with a updated driver. It wouldn;t be the first time that due to lack of knowledge I assumed I was using a device to its full extent just to find out that it could of been better.

@shadow: how do you measured 6-7 MB/s?
I did my test with a 2 GB file transfer from laptop (wifi connected) to Raspberry pi 2 (wifi connected also). Files on the Rpi are stored on a local attached hdd NTFS formatted, so considering that NTFS file system is not the best choice for Rpi (cpu overhead) and the USB bus is shared between hdd and wifi dongle, I think that 2.5 MB/s is acceptable (setting max_usb_current=1 obviously).

I measured a couple ways

  1. scp 'ing a file to the Pi
  2. ssh’d into it (use a little bit of bandwidth for the connection) then pv (cp with progress info) a file from my NAS via NFS
  3. also ssh’d into it running iftop when watching a full Bluray video from either NFS or UPNP

But maybe it is stuff like it being NTFS or Samba which I heard is one of the worst for bad speed (but they say the same about scp which I still get good speed from)

It’s not a matter of indicators.
When those drivers came out on raspbian, i had my raspi1 working quite good (slow, but stable), and the raspi2 loosing connection every 10 seconds and unable even to do a apt-get call.
Now it’s the same on the raspi1 with osmc.

I don’t think mr engman is keeping updated the driver for a matter of indicators, do you?

@Massi
I used the rtl8188eu chipset since Raspbmc (Rapsberry pi model B) and compiled myself the driver from source.
Honestly I don’t remember if the source was provided by Mr. engman or not, but after some problems, it worked fine (slow speed in file transert but that was related to my configs, see my previous post).

Now I’ve a Raspberry pi 2 with OSMC and the same USB Wifi dongle, a TP-LINK TP-725N v2 (chipset 8188eu) and after some connection problems (the same you are suffering now with OSMC) it works fine with OSMC RC3 driver (I suspect even with RC2 driver but I’m unsure).
My problem was in the Router TCP/IP configs.
I did a router factory reset and a full reconfiguration and my rtl8188eu worked fine since then.
I use aMule in background and I can assure you I have no disconnections/dropouts anymore with OSMC driver, and p2p programs will stress network connection a lot.
This is my experience and I’ve not tested OSMC with Raspberry pi 1 at all.
I don’t know if the Mr. Engman develops the driver or simply provides src for Raspbian but if his driver is useful for your problem and you are unable to compile yourself then maybe the OSMC developers (DBMandrake?) could have a look at the Mr. Engman work and eventually include it in OSMC.

There seems to be some confusion here. Raspbian is a userland. Mr Engman (the user on the Pi forum) has provided some instructions to compile the out-of-tree modules for the kernel and include them in Raspbian. The drivers aren’t ‘part’ of Raspbian and they should actually be considered kernel space.

BTW: OSMC is not always based on Raspbian: Pi 2 is actually based on Debian Jessie upstream and does not include any Raspbian components.

The issue is that Realtek hit a merge window once every few months for the mainline, and if it somewhat works no one cares or has the energy to test the drivers. The solution is simple: build out of tree (which is effectively what Engman does, with the latest RTL driver). I’m now starting to ship our own, customised Realtek drivers for OSMC (patched to actually compile on 3.18x+ kernels, additional vid/pid combos). I’ll do this for 8188EU soon, but I do not have a dongle to test.

Sam

I’m confused… would this help with my issues with the Edimax EW-7811UTC?

What ssh command gives that detail about the wifi connection that massi posted in the first post in this topic??

I’ve provided info in this thread of my problems…

Please help…
Thanks

what’s the chipset it’s using?

it’s iwconfig.
You need a sudo apt-get install wireless-tools, if i remember right the name…

1 Like

Thanks for the install wireless tools command!

I think it uses Realtek RTL8811AU chipset. Is there a way to confirm this with another ssh command?

Bus 001 Device 005: ID 7392:a812 Edimax Technology Co., Ltd

Bizarrely, it seems to think my connection is good, but still unreliable… sometimes! I don’t get it!

wlan0 IEEE 802.11AC ESSID:“5” Nickname:“WIFI@REALTEK”
Mode:Managed Frequency:5.18 GHz Access Point: 10:BF:48:D8:A4:C4
Bit Rate:434 Mb/s Sensitivity:0/0
Retry:off RTS thr:off Fragment thr:off
Encryption key:------- Security mode:open
Power Management:off
Link Quality=100/100 Signal level=98/100 Noise level=0/100
Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0
Tx excessive retries:0 Invalid misc:0 Missed beacon:0

Different chipset, please start a new thread

What’s the status of 8188eu driver?
osmc@osmc:~$ iwconfig wlan0 IEEE 802.11bgn ESSID:"thaks98" Nickname:"<WIFI@REALTEK>" Mode:Managed Frequency:2.412 GHz Access Point: FC:DD:55:05:EC:70 Bit Rate:65 Mb/s Sensitivity:0/0 Retry:off RTS thr:off Fragment thr:off Power Management:off Link Quality=8/100 Signal level=30/100 Noise level=0/100 Rx invalid nwid:0 Rx invalid crypt:0 Rx invalid frag:0 Tx excessive retries:0 Invalid misc:0 Missed beacon:0

The link quality and signal level is still low.
and I am using:
osmc@osmc:~$ uname -a Linux osmc 4.3.0-10-osmc #1 SMP PREEMPT Sun Nov 29 14:06:50 UTC 2015 armv7l GNU/Linux

We use the in-tree module which should be reasonably mature. I can see if anything can be done to improve the state of this driver.

Sam