• Announcements

    • 1. Check power supply, check SD card and check other people experiences

      Power supply issues are one of the three biggest issues you'll face when starting with Single Board Computers (SBCs). SD card issues, whether fake or faulty, are another and issues resulting from poor board design is the other common issues you can encounter.   Power supply issues can be tricky. You might have a noisy power supply that works with one board because it has extra filtering, but won't work with another. Or you're using that cheap phone charger because your board has a microUSB connector, and it is either erratic, or doesn't start up, or even becomes the cause of some SD card issues.    Some tips to avoid the most common causes of problems reported:   Don't power via micro USB  - unless you have optimised your setup for low power requirements. Micro USB is great for mobile phones because they are simply charging a battery. It's bad for SBCs. Yes, it does work for a lot of people, but it also causes more problems and headaches over time than it is worth, unless you know exactly what you are doing. If you have a barrel jack power connector on your SBC, use it instead! If there is an option for powering via header connections, use that option!
        Don't use mobile phone chargers. They might be convenient and cheap, but this is because they are meant for charging phones, not powering your SBC which has particular power requirements.
        When you are evaluating a power supply, make sure you run some stress tests on your system to ensure that it will not cause issues down the path.   (Micro) SD card issues can be sneaky. They might appear right at the start causing strange boot and login errors, or they might cause problems over time. It is best to run a test on any new SD card you use, to ensure that it really is what it is, and to ensure that isn't faulty. Armbian provides you a simple way to do this   --   armbianmonitor -c /path/to/device/to/test  
    • 2. Make sure to collect and provide all necessary information

      We can only help if you provide quality information for us to work with. All stable images from the download section are tested, most stable upgrades are tested and we have tens of thousands of users. Even with regular and extensive testings, bugs sometimes do slip through. This is a voluntary support service and is unrelated to board makers, and is not obligated to provide you any answers. Repeated asking the same questions because you're not happy with the answers will result in you being ignored.

      Before you post a question, use the forum search as someone else might have already had the same problem and resolved it. And make sure you've read the Armbian documentation. If you still haven't found an answer, make sure you include the following in your post:   1. Logs when you can boot the board: armbianmonitor -u (paste URL to your forum post)   2. If your board does not boot, provide a log from serial console or at least make a picture, where it stops.   3. Describe the problem the best you can and provide all necessary info that we can reproduce the problem. We are not clairvoyant or mind readers. Please describe your setup as best as possible so we know what your operating environment is like.     We will not help in cases you are not using stable official Armbian builds, you have a problem with 3rd party hardware or reported problem would not be able to reproduced.

Realtek RTL8192EU WiFi driver?
0

21 posts in this topic

Recommended Posts

Hi,

 

I got one of those cheap 300Mbps wifi dongles with 8192EU chip with USB Vid/Pid  0bda:818b.

How can we enable this in Armbian?

lsmod does not show any detected h/w driver and wan0 is not showing up in ifconfig.

Only lsusb has the following

root@nanopineo:~# lsusb
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 006 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 002: ID 0bda:818b Realtek Semiconductor Corp.
Bus 004 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
root@nanopineo:~#

Any hint or pointer welcome.

 

Christos

 

Share this post


Link to post
Share on other sites

Ok,

The dongle came with a CD containing linux driver sources, a SDK for it, so if you have any pointer on how to add this myself, then I could give it a shot.

 

Also, which 300Mbps dongles do work with Armbian? do you happen to know? is the other you bought a 300Mbps one?

 

 

 

P.S.

I do have 8192cu 150Mbps dongles that are configured and work just fine, but do need now the extra bandwidth of the 300..

 

P.S. 2

Forgot to mention that I'm interested only in kernel 3.4.112

Share this post


Link to post
Share on other sites

This 300Mb/s vs. 150Mb/s is a marketing bullshit. All of these dongles are 802.11 b/g/n capable and actual efficiency depends only on chip used, in theory 802.11n data rates may go up to 600Mb/s. 8192eu may not be the worst one, but hey, it's 2016, no one should be forced to build kernel driver for a network card.

XTL likes this

Share this post


Link to post
Share on other sites

Ok,

 

The 8192cu based on specs go up to 150Mbps and 8192eu to 300Mbps, the protocol itself and its theoretical limit is another story.

What you forgot to mention is the actual current medium congestion where in rural areas and appartment buildings with lots of devices in the vicinity, achieving high speeds is dificult.

I kinda know all these things.. yet I do want to give a try and have a higher (capable) bandwidth wifi hardware.

So if anyone can propose such a device would be great. Or just to give me a pointer on how to integrate in Armbian a new driver.

 

Christos

Share this post


Link to post
Share on other sites

Hi,

 

I got one of those cheap 300Mbps wifi dongles with 8192EU chip with USB Vid/Pid  0bda:818b.

How can we enable this in Armbian?

lsmod does not show any detected h/w driver and wan0 is not showing up in ifconfig.

Only lsusb has the following

root@nanopineo:~# lsusb
Bus 004 Device 002: ID 0bda:818b Realtek Semiconductor Corp.
root@nanopineo:~#

Any hint or pointer welcome.

 

Christos

 

Hi Christos,
 
Please follow the below steps to compile and deploy the kernel module for 8192EU:
 
git clone https://github.com/shahidali55/rtl8192eu_3
cd rtl8192eu_3
make ARCH=arm
sudo make install

If all the above steps complete without errors, reboot the board. ifconfig should now show wlan0

Christos likes this

Share this post


Link to post
Share on other sites

I also have one of those cheap 8192EU dongles. Driver is a little pain in the back for all platforms. In Windows, official driver installs but no signs of work, i had to deeply dig internet for correct driver and then it works fine, with real 300Mbit speed and descend range. In Linux (official x64), it kind of worked with this driver - dkms_rtl8192eu_4.3.1.1.11320.20140505-2_all.deb , but show no connection speed, and real download speed was about 100/200Kb. I have no idea if it can be installed on Armbian. I have also this drivers on my harddrive - dkms_rtl8192eu_4.3.1.1.11320.20140505_all.deb, Realtek-TL8192EU-driver.tar.gz .But doesn't have a chance to test it, because the cheap thing, mechanically break, losing it's front metal cover and i lost enthusiasm to deal with it.

Share this post


Link to post
Share on other sites

 

Hi Christos,
 
Please follow the below steps to compile and deploy the kernel module for 8192EU:
 
git clone https://github.com/shahidali55/rtl8192eu_3
cd rtl8192eu_3
make ARCH=arm
sudo make install

If all the above steps complete without errors, reboot the board. ifconfig should now show wlan0

 

 

@shaidali55

 

Thanks!!

 

Tested and t works just fine.

 

 

Thank you

Christos

Share this post


Link to post
Share on other sites

Ok,

 

After succesfully using the 8192eu as client, its time to set ip up with hostapd use.

 

I got two of those dongles, each is plugged to a NanoPi NEO v1.1 running Armbian 5.21 jessie 3.4.112.

 

Both got the 8192eu .ko driver installed and are able to operate as clients succesfully.

 

Now one of them I like to make it as AP with hostapd.

Followed the tutorial here for AP

-> http://forum.armbian.com/index.php/topic/1237-tutorial-opi-one-wireless-success/

but did report errors

root@nanopineo:~# hostapd /etc/hostapd.conf
Configuration file: /etc/hostapd.conf
nl80211: deinit ifname=wlan1 disabled_11b_rates=0
nl80211 driver initialization failed.
wlan1: interface state UNINITIALIZED->DISABLED
wlan1: AP-DISABLED
hostapd_free_hapd_data: Interface wlan1 wasn't started
root@nanopineo:~#

the /etc/hostapd.conf contents

root@nanopineo:~# cat /etc/hostapd.conf
ssid=NanoPiNEO
interface=wlan1
hw_mode=g
channel=5
driver=nl80211
logger_syslog=0
logger_syslog_level=0
wmm_enabled=1
ieee80211n=1
wpa=3
preamble=1
#wpa_psk=66eb31d2b48d19ba216f2e50c6831ee11be98e2fa3a8075e30b866f4a5ccda27
wpa_passphrase='123456789'
wpa_key_mgmt=WPA-PSK
wpa_pairwise=TKIP
rsn_pairwise=CCMP
auth_algs=1
macaddr_acl=0
noscan=1
#ht_capab=[HT40-][SHORT-GI-40][SHORT-GI-40][DSSS_CCK-40]
country_code=GR
#ieee80211d=1

root@nanopineo:~#

thats the ifconfig -a report

root@nanopineo:~# ifconfig -a
eth0      Link encap:Ethernet  HWaddr ee:1e:a4:bb:94:e9
          inet addr:192.168.1.7  Bcast:192.168.1.255  Mask:255.255.255.0
          inet6 addr: 2a02:582:d2e:1100:ec1e:a4ff:febb:94e9/64 Scope:Global
          inet6 addr: fe80::ec1e:a4ff:febb:94e9/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:818 errors:0 dropped:0 overruns:0 frame:0
          TX packets:702 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:74303 (72.5 KiB)  TX bytes:87621 (85.5 KiB)
          Interrupt:114

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:43 errors:0 dropped:0 overruns:0 frame:0
          TX packets:43 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:4436 (4.3 KiB)  TX bytes:4436 (4.3 KiB)

tunl0     Link encap:IPIP Tunnel  HWaddr
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0   TX bytes:0 (0.0 

wlan1     Link encap:Ethernet  HWaddr 24:05:0f:00:00:75
          inet addr:192.168.10.1  Bcast:192.168.10.255  Mask:255.255.255.0
          inet6 addr: 2a02:582:d2e:1100:2605:fff:fe00:75/64 Scope:Global
          inet6 addr: fe80::2605:fff:fe00:75/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:31 errors:0 dropped:2 overruns:0 frame:0
          TX packets:124 errors:0 dropped:1 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:5427 (5.2 KiB)  TX bytes:9680 (9.4 KiB)

root@nanopineo:~#

Any hints?

 

Christos

Share this post


Link to post
Share on other sites

Any hints?

 

Wasting another few hours of your life googling for '8192eu -8192cu ap mode' and stuff like that? Most probably to realize that the only place on earth where this works are seller pages on Aliexpress?

zgoda_j likes this

Share this post


Link to post
Share on other sites

Managed so far to have hostapd with 8192cu and client with 8192eu.

 

But still hostapd with 8192eu is elusive for me..  (keep trying and using hostapd-realtek).

Share this post


Link to post
Share on other sites

Managed so far to have hostapd with 8192cu and client with 8192eu.

 

But still hostapd with 8192eu is elusive for me..  (keep trying and using hostapd-realtek).

 

Googling for 'problem or issue 8192' results in 3,000,000 hits. Given a single hour spent on solving problems with these crap dongles is worth just $1 maybe these RealTek devices are the most expensive peripherals around?

 

Anyway: I would never buy this stuff but have one 8192CU based TL-WN823N here by accident (came with an UP Board). The dongle is rated '300 Mbps' and compared to the el cheapo onboard SDIO Wi-Fi of an Orange Pi Lite it's just... slow crap: see #238 here: http://forum.armbian.com/index.php/topic/1580-nanopi-neo-air/?p=17619 (I tested also speed with iperf3, over 3 times less than OPi Lite Wi-Fi).

 

BTW: No offense at all, I just want to produce stuff for search engines so that people realize that crappy Wi-Fi dongles are crappy Wi-Fi dongles prior to purchase and not after. :)

Share this post


Link to post
Share on other sites

Ok,

 

After succesfully using the 8192eu as client, its time to set ip up with hostapd use.

 

I got two of those dongles, each is plugged to a NanoPi NEO v1.1 running Armbian 5.21 jessie 3.4.112.

 

Both got the 8192eu .ko driver installed and are able to operate as clients succesfully.

 

Now one of them I like to make it as AP with hostapd.

Followed the tutorial here for AP

-> http://forum.armbian.com/index.php/topic/1237-tutorial-opi-one-wireless-success/

but did report errors

 

 

Any hints?

 

Christos

 

Hi Christos,

 

You will need hostapd version specific for 8192eu module. I've just tested compiling it and it does compile. Not sure if it will work. Please try and let me know.

git clone https://github.com/shahidali55/rtl8192eu-driver
cd rtl8192eu-driver
cd wpa_supplicant_hostapd
tar -zxvf wpa_supplicant_hostapd-0.8_rtw_r7048.20130424.tar.gz
cd wpa_supplicant_hostapd-0.8_rtw_r7048.20130424
cd hostapd
make arch=ARM
cp ../../rtl_hostapd_2G.conf ./

Then follow this guide to setup and launch hostapd

Share this post


Link to post
Share on other sites

Hi Christos,

 

You will need hostapd version specific for 8192eu module. I've just tested compiling it and it does compile. Not sure if it will work. Please try and let me know.

git clone https://github.com/shahidali55/rtl8192eu-driver
cd rtl8192eu-driver
cd wpa_supplicant_hostapd
tar -zxvf wpa_supplicant_hostapd-0.8_rtw_r7048.20130424.tar.gz
cd wpa_supplicant_hostapd-0.8_rtw_r7048.20130424
cd hostapd
make arch=ARM
cp ../../rtl_hostapd_2G.conf ./

Then follow this guide to setup and launch hostapd

 

Thank you very much shahidali55 for the help, its really appreciated.

Tried the compile and got it through, yet I could not start the produced hostapd even though tried quite a few config variations.

I come to believe that it might not worth the trouble after all..

 

 

 

@tkaiser  ..Thomas, just got a new OPiPC+ and indeed, working wifi out of the box and by listing twice as many nearby APs is definitively impressive..

Share this post


Link to post
Share on other sites

Downloaded the driver and compiled it with many errors like

rtw_security.c:(.text+0x20f4): multiple definition of `is_multicast_mac_addr'
/home/gandalf/rtl8192eu_3/core/rtw_cmd.o:rtw_cmd.c:(.text+0x4c): first defined here

 

after removing in the file ieee80211.h ' extern _' in line 1317, 1322 and 1328,  it compiled fine and after 'sudo make install' the wifi was up and running

thanks for the driver

git clone https://github.com/shahidali55/rtl8192eu_3
cd rtl8192eu_3
make ARCH=arm
sudo make install

Share this post


Link to post
Share on other sites

For current OS installs, to get this to compile edit the file include/ieee80211.h, search for 'extern __inline' and replace with 'static __inline' for the three offending declarations!  This allows it to compile cleanly.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

0

  • Support the project

    We need your help to stay focused on the project.

    Choose the amount and currency you would like to donate in below.