Orange Pi Plus 2E - no Wifi


#1

Hi all,

I’ve managed to get my Orange Pi Plus 2E up and running here with the help of the Balena team.

However there’s no WiFI support present for the onboard RTL8189FTV.

Hunting around I see this commit which seems to confirm the lack of support.

Can anybody give me an idea what the current state of play is? Are we anywhere near having WiFi supported? What is the issue with it?

Thanks!

Alex


OrangePi Plus 2E Not Booting?
#5

Hi @ajlennon,

The commit you linked here is deprecated and WiFi is definitely working on Orange Pi Plus 2.

I can’t really say about Orange Pi Plus 2E because we don’t have this board.

Let’s try and see if we can make WiFi work on your Orange Pi Plus 2E board.

Please give me the output of ifconfig command.

Regards!


#7

ok great!

Here is the ifconfig output

root@d05658d:/usr/src/app# ifconfig
balena0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 10.114.101.1  netmask 255.255.255.0  broadcast 0.0.0.0
        ether 02:42:49:14:64:ab  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

br-eb3426989bdb: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.18.0.1  netmask 255.255.0.0  broadcast 0.0.0.0
        ether 02:42:a6:9a:53:9c  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 192.168.10.244  netmask 255.255.255.0  broadcast 192.168.10.255
        ether 02:81:3b:44:18:2b  txqueuelen 1000  (Ethernet)
        RX packets 356  bytes 163185 (159.3 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 404  bytes 58017 (56.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 32

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 292  bytes 29849 (29.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 292  bytes 29849 (29.1 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

resin-dns: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet 10.114.102.1  netmask 255.255.255.0  broadcast 0.0.0.0
        inet6 fe80::bc9e:dcff:feeb:caaf  prefixlen 64  scopeid 0x20<link>
        ether be:9e:dc:eb:ca:af  txqueuelen 1000  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 29  bytes 4726 (4.6 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

resin-vpn: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST>  mtu 1500
        inet 10.240.2.12  netmask 255.255.255.255  destination 52.4.252.97
        inet6 fe80::c293:5118:4143:8783  prefixlen 64  scopeid 0x20<link>
        unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 100  (UNSPEC)
        RX packets 42  bytes 5357 (5.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 47  bytes 5102 (4.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

supervisor0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.17.0.1  netmask 255.255.0.0  broadcast 0.0.0.0
        ether 02:42:ba:0f:85:fb  txqueuelen 0  (Ethernet)
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Also I have just granted you support access to d05658d98906bcec90a9eb7000e84f69 which is the Orange Pi Plus 2E connected over wired Ethernet…


#8

Hi @ajlennon,

I can see on your device that you are using the device tree for the Orange Pi Plus 2.

Could you please try and replace it with the device tree that I sent you for the Orange Pi Plus 2e?

And then try again to see if WiFi works.

Regards!


#10

Will do!


#11

OK should be running the new DTB now.

Bit of finger trouble on my part and it reflashed the eMMC from the SD so has a new UID.

Have granted support access to 7df5dc908785cf371e5f8132710f947d again.

Thanks!


#12

Still no WiFi from what I can see (I did have it running the new DTB before)

iw dev and iw phy give nothing etc.


#13

Hey @ajlennon,

Indeed, WiFi it’s not working on your board.

It’s curious that it doesn’t work since the WiFi chip is advertised as being the same.

Unfortunately I can’t help you make it work because I don’t have the board at hand.

If you need WiFi you could:

  • use an USB WiFi dongle
  • try to make it yourself work
  • use the Orange Pi Plus2 board instead of Orange Pi Plus 2e

#15

Yeah. It’s a shame. I can use an external dongle with the Raspberry Pi but I really want to use the internal WiFi part. The problem is the Raspberry Pi internal dongle doesn’t properly support monitor mode, which the OrangePi part should do.

I am thinking I might have a look at rebuilding the BelanaOS image and see if that gets me anywhere…

Thanks!


#16

Looking through the DTS files in the linux tree. They seem pretty much the same.

I am wondering if there is a difference between the u-boot setups?


#17

In u-boot the difference between the two boards seems to be related to SATA and USB power:

Here’s a diff between the two configs:

diff -Naur orangepi_plus2e_defconfig orangepi_plus_defconfig
--- orangepi_plus2e_defconfig	2019-02-22 13:03:07.123170185 +0100
+++ orangepi_plus_defconfig	2019-02-22 13:03:07.123170185 +0100
@@ -6,7 +6,9 @@
 CONFIG_DRAM_ODT_EN=y
 CONFIG_MACPWR="PD6"
 CONFIG_MMC_SUNXI_SLOT_EXTRA=2
-CONFIG_DEFAULT_DEVICE_TREE="sun8i-h3-orangepi-plus2e"
+CONFIG_USB1_VBUS_PIN="PG13"
+CONFIG_SATAPWR="PG11"
+CONFIG_DEFAULT_DEVICE_TREE="sun8i-h3-orangepi-plus"
 # CONFIG_SYS_MALLOC_CLEAR_ON_INIT is not set
 CONFIG_SPL=y
 CONFIG_SPL_I2C_SUPPORT=y

#19

Yeah thanks @spanceac. That’s what I saw. I came to the conclusion I couldn’t see anything in there that leaps out at me as a problem.

Trying to rebuild from the GitHub repo now to (a) replicate what I see with current binaries then (b) try to modify to build for 2E

Cheers!


#22

Getting there slowly. I have a build targetting the Plus2E now and am nearly there.

It’s failing as it’s building the rootfs with something about kernel-abiversion

Can you point me in the right direction at all?

NOTE: resin-image-flasher-1.0-r0 do_rootfs: Executing write_image_manifest ...
NOTE: resin-image-1.0-r0 do_rootfs: Executing: ldconfig -r/data_drive/devel/spriteguard/balena-allwinner/build/tmp/work/orangepi_plus2e-poky-linux-gnueabi/resin-image/1.0-r0/rootfs-c new -v
ERROR: resin-image-1.0-r0 do_rootfs: No kernel-abiversion file found (/data_drive/devel/spriteguard/balena-allwinner/build/tmp/pkgdata/orangepi-plus2e/kernel-depmod/kernel-abiversion), cannot run depmod, aborting
ERROR: resin-image-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /data_drive/devel/spriteguard/balena-allwinner/build/tmp/work/orangepi_plus2e-poky-linux-gnueabi/resin-image/1.0-r0/temp/log.do_rootfs.27992
ERROR: Task (/data_drive/devel/spriteguard/balena-allwinner/build/../layers/meta-resin/meta-resin-common/recipes-core/images/resin-image.bb:do_rootfs) failed with exit code '1'
NOTE: resin-image-flasher-1.0-r0 do_rootfs: Executing: ldconfig -r/data_drive/devel/spriteguard/balena-allwinner/build/tmp/work/orangepi_plus2e-poky-linux-gnueabi/resin-image-flasher/1.0-r0/rootfs-c new -v
ERROR: resin-image-flasher-1.0-r0 do_rootfs: No kernel-abiversion file found (/data_drive/devel/spriteguard/balena-allwinner/build/tmp/pkgdata/orangepi-plus2e/kernel-depmod/kernel-abiversion), cannot run depmod, aborting
ERROR: resin-image-flasher-1.0-r0 do_rootfs: Function failed: do_rootfs
ERROR: Logfile of failure stored in: /data_drive/devel/spriteguard/balena-allwinner/build/tmp/work/orangepi_plus2e-poky-linux-gnueabi/resin-image-flasher/1.0-r0/temp/log.do_rootfs.27995
ERROR: Task (/data_drive/devel/spriteguard/balena-allwinner/build/../layers/meta-resin/meta-resin-common/recipes-core/images/resin-image-flasher.bb:do_rootfs) failed with exit code '1'

Thanks!


#23

Made some good progress @spanceac

I’ve now got a new machine supported, the orangepi-plus-2e which builds with the needed driver for WiFi.

There are a few different external repos involved here.

Can somebody at Balena take me under their wing and help me get some PRs into you guys in the right way so this work doesn’t go to waste?

Thanks Alex


#24

For those who just want a working WiFI for the Plus2E you need the rtl8189fs-mod driver from this repo


#25

Wow that’s great news @ajlennon :clap:
I will pass this internally to have someone assist you on this.


#33

Hi @ajlennon,

Thank you for your orangepi-plus2e PR in github.

We will review it and let you know if any changes are needed and then to have it merged.

Regards!


#34

Hi @ajlennon,
Thank you for your orangepi-plus2e PR in github.
We will review it and let you know if any changes are needed and then to have it merged.
Regards!


#35

Thanks guys. I’ve just realised that the Plus2E is 2.4GHz only.

I see there’s a 2.4/5GHz variant, the Orange Pi 3.

I might have a look at this. Have you got a board at Balena Towers? Do you have any support for this?

Thanks!


#37

To my knowledge we don’t have the Plus2E or the Pi 3 in our offices