BPI-R2 new image: BPI-R2 OpenWrt(LEDE) Souce code : 2018-05-09

Hi Frank,

So I burned the image of ubuntu 16 from your images, than I copied the contents of BPI-BOOT the bananapi folder to the boot directory on disk and BPI-ROOT contents, the lib folder to the root directory overwriting the lib folder. But the bananapi will not boot, I get a blue screen and after a few seconds it turns black, saying no signal.

I guess you use hdmi? This is one of things only working on 4.4…but you can change network-settings like described on my wiki to login via ssh or use debug-uart (usb2serial).

I’ll give that a try. Where is your wiki on setting up ssh?

Hello, i get a “Bad Gateway” error for luci ???

Hi Roman

Yes, the HDMI is not supported in openwrt yet. We can use the below three ways to login to R2 board if you use latest openwrt image:

  1. Serial port,
  2. ssh [email protected] (from one of four lan ports), the 192.168.1.1 is the default gateway.
  3. web: http://192.168.1.1 (from one of four lan ports)

The Switch does works if you use ubuntu image, but HNAT doesn’t work, and we have no plan to support it.

I also faced this problem one week ago, the reason is latest source code of luci doen’t stable yet, also I report issue to here: https://github.com/jow-/lucihttp/issues/1, but have no time to find the root cause yet.

The workaround is to use stable luci code, so please change the source of luci package in feeds.conf.default to below:

src-git luci https://github.com/openwrt/luci.git;lede-17.01

1 Like

Thank nicoo. I found some other interfaces. Do you know they can be used?

/proc/sys/net/ipv6/conf/all/temp_prefered_lft
/proc/sys/net/ipv6/conf/all/temp_valid_lft
/proc/sys/net/ipv6/conf/all/use_tempaddr
/proc/sys/net/ipv6/conf/br-lan/temp_prefered_lft
/proc/sys/net/ipv6/conf/br-lan/temp_valid_lft
/proc/sys/net/ipv6/conf/br-lan/use_tempaddr
/proc/sys/net/ipv6/conf/default/temp_prefered_lft
/proc/sys/net/ipv6/conf/default/temp_valid_lft
/proc/sys/net/ipv6/conf/default/use_tempaddr
/proc/sys/net/ipv6/conf/eth0/temp_prefered_lft
/proc/sys/net/ipv6/conf/eth0/temp_valid_lft
/proc/sys/net/ipv6/conf/eth0/use_tempaddr
/proc/sys/net/ipv6/conf/eth1/temp_prefered_lft
/proc/sys/net/ipv6/conf/eth1/temp_valid_lft
/proc/sys/net/ipv6/conf/eth1/use_tempaddr
/proc/sys/net/ipv6/conf/gre0/temp_prefered_lft
/proc/sys/net/ipv6/conf/gre0/temp_valid_lft
/proc/sys/net/ipv6/conf/gre0/use_tempaddr
/proc/sys/net/ipv6/conf/gretap0/temp_prefered_lft
/proc/sys/net/ipv6/conf/gretap0/temp_valid_lft
/proc/sys/net/ipv6/conf/gretap0/use_tempaddr
/proc/sys/net/ipv6/conf/lan0/temp_prefered_lft
/proc/sys/net/ipv6/conf/lan0/temp_valid_lft
/proc/sys/net/ipv6/conf/lan0/use_tempaddr
/proc/sys/net/ipv6/conf/lan1/temp_prefered_lft
/proc/sys/net/ipv6/conf/lan1/temp_valid_lft
/proc/sys/net/ipv6/conf/lan1/use_tempaddr
/proc/sys/net/ipv6/conf/lan2/temp_prefered_lft
/proc/sys/net/ipv6/conf/lan2/temp_valid_lft
/proc/sys/net/ipv6/conf/lan2/use_tempaddr
/proc/sys/net/ipv6/conf/lan3/temp_prefered_lft
/proc/sys/net/ipv6/conf/lan3/temp_valid_lft
/proc/sys/net/ipv6/conf/lan3/use_tempaddr
/proc/sys/net/ipv6/conf/lo/temp_prefered_lft
/proc/sys/net/ipv6/conf/lo/temp_valid_lft
/proc/sys/net/ipv6/conf/lo/use_tempaddr
/proc/sys/net/ipv6/conf/wan/temp_prefered_lft
/proc/sys/net/ipv6/conf/wan/temp_valid_lft
/proc/sys/net/ipv6/conf/wan/use_tempaddr
/sys/devices/virtual/thermal/thermal_zone0/trip_point_3_temp
/sys/devices/virtual/thermal/thermal_zone0/trip_point_2_temp
/sys/devices/virtual/thermal/thermal_zone0/trip_point_1_temp
/sys/devices/virtual/thermal/thermal_zone0/trip_point_0_temp
/sys/devices/virtual/thermal/thermal_zone0/temp
/sys/firmware/devicetree/base/thermal-zones/cpu_thermal/trips/cpu_passive/temperature
/sys/firmware/devicetree/base/thermal-zones/cpu_thermal/trips/cpu_active/temperature
/sys/firmware/devicetree/base/thermal-zones/cpu_thermal/trips/cpu_hot/temperature
/sys/firmware/devicetree/base/thermal-zones/cpu_thermal/trips/cpu_crit/temperature

Is ssh enqbled in ubuntu by default with permitrootlogin? Have it also fixed on lan-ports?

Are you workin on integrating hdmi in 4.14?

@roman i hve no page for ssh yet…i mean configure network to get access to exing ssh-server. Network-config in 4.14 is different to 4.4 because of changed interface-names. But please make a new thread…this is for lede

Vendor has submited patch of HDMI to kernel 4.16, but we don’t have time to port it to 4.14 and 4.9(openwrt).

How can i compile as “hard-float” ? What i have to change during compile process ? Thanks a lot for all your help Guys

Please make sure you’re using latest source code from https://github.com/garywangcn/bpi-r2_lede/tree/bpi-r2-on-lede-v1, and then ensure the option Advanced configuration options ->Target Options ->Use software floating point by default is NOT selected. And then compile whole project.

1 Like

Great Thanks @garywang So in this case i think, is a good choice to check the checkbox for all the userspace packages, right ?

status (boolean) temporary IPv6 address. I didn’t check all your entries, I may know some of them but I mostly don’t know them… anyway you can forget all /proc/sys/net/ipv6/ entries. they are nothing related to temperature.

those inside /sy/device/virtual are parentless devices… I personally never have to deal with them, I don’t know much about them, excpet that they are used somehow for RAID… fyi, virtual devices can be elsewhere too…

/sys/firmware/devicetree/base/thermal-zones/cpu_thermal/ I don’t much about it, but seems interesting. I can’t turn on my BPI for now…

I need myself to monitor the temperature, I don’t know yet where are temperature sensors on the BPI, but I keep in mind to connect my own senor directly to the gpio. I don’t know if the gpio can be used with lede though…

hope this answer somehow

didn’t work ,again Bad Gateway…

It will take a huge time to validate all userspace packages, actually we’d like you are using the packages from the stable release, also please maintain yourself repository if you want to make a product based on R2 and Openwrt.

can you please share us the list of installed packages? If you are still use latest luci code, maybe the workaround in https://github.com/jow-/lucihttp/issues/1 is required, please note that the workaround isn’t agreed by author yet.

> base-files - 174-r4773-2cb61a83f4
> blkid - 2.30.1-2
> block-mount - 2017-07-31-8ab4fda6-1
> blockd - 2017-07-31-8ab4fda6-1
> busybox - 1.26.2-7
> chattr - 1.43.5-1
> curl - 7.54.1-1
> dnsmasq - 2.77-8
> dropbear - 2017.75-3
> e2fsprogs - 1.43.5-1
> fdisk - 2.30.1-2
> firewall - 2017-05-27-a4d98aea-1
> fstools - 2017-07-31-8ab4fda6-1
> fwtool - 1
> hostapd-common - 2016-12-19-ad02e79d-4
> ip-tiny - 4.11.0-1
> ip6tables - 1.6.1-1
> iptables - 1.6.1-1
> iptables-mod-ipsec - 1.6.1-1
> iwinfo - 2017-08-23-c1a03e82-1
> jshn - 2017-06-17-fd57eea9-1
> jsonfilter - 2016-07-02-dea067ad-1
> kernel - 4.9.44-1-06049d59456e793334a35db08d676f50
> kmod-crypto-aead - 4.9.44-1
> kmod-crypto-authenc - 4.9.44-1
> kmod-crypto-cbc - 4.9.44-1
> kmod-crypto-deflate - 4.9.44-1
> kmod-crypto-des - 4.9.44-1
> kmod-crypto-echainiv - 4.9.44-1
> kmod-crypto-hash - 4.9.44-1
> kmod-crypto-hmac - 4.9.44-1
> kmod-crypto-iv - 4.9.44-1
> kmod-crypto-manager - 4.9.44-1
> kmod-crypto-md5 - 4.9.44-1
> kmod-crypto-null - 4.9.44-1
> kmod-crypto-pcompress - 4.9.44-1
> kmod-crypto-rng - 4.9.44-1
> kmod-crypto-sha1 - 4.9.44-1
> kmod-crypto-sha256 - 4.9.44-1
> kmod-crypto-wq - 4.9.44-1
> kmod-fs-autofs4 - 4.9.44-1
> kmod-gpio-button-hotplug - 4.9.44-2
> kmod-ip6tables - 4.9.44-1
> kmod-ipsec - 4.9.44-1
> kmod-ipsec4 - 4.9.44-1
> kmod-ipsec6 - 4.9.44-1
> kmod-ipt-conntrack - 4.9.44-1
> kmod-ipt-core - 4.9.44-1
> kmod-ipt-ipsec - 4.9.44-1
> kmod-ipt-nat - 4.9.44-1
> kmod-iptunnel4 - 4.9.44-1
> kmod-iptunnel6 - 4.9.44-1
> kmod-leds-gpio - 4.9.44-1
> kmod-lib-crc-ccitt - 4.9.44-1
> kmod-lib-zlib-deflate - 4.9.44-1
> kmod-lib-zlib-inflate - 4.9.44-1
> kmod-nf-conntrack - 4.9.44-1
> kmod-nf-conntrack6 - 4.9.44-1
> kmod-nf-ipt - 4.9.44-1
> kmod-nf-ipt6 - 4.9.44-1
> kmod-nf-nat - 4.9.44-1
> kmod-ppp - 4.9.44-1
> kmod-pppoe - 4.9.44-1
> kmod-pppox - 4.9.44-1
> kmod-slhc - 4.9.44-1
> lede-keyring - 2017-01-20-a50b7529-1
> libblkid - 2.30.1-2
> libblobmsg-json - 2017-06-17-fd57eea9-1
> libbz2 - 1.0.6-3
> libc - 1.1.16-1
> libcurl - 7.54.1-1
> libext2fs - 1.43.5-1
> libfdisk - 2.30.1-2
> libgcc - 5.4.0-1
> libgmp - 6.1.2-1
> libip4tc - 1.6.1-1
> libip6tc - 1.6.1-1
> libiwinfo - 2017-08-23-c1a03e82-1
> libiwinfo-lua - 2017-08-23-c1a03e82-1
> libjson-c - 0.12.1-1
> libjson-script - 2017-06-17-fd57eea9-1
> liblua - 5.1.5-1
> liblucihttp - 2018-04-22-ccc685e5-1
> liblucihttp-lua - 2018-04-22-ccc685e5-1
> libmbedtls - 2.5.1-1
> libncurses - 6.0-1
> libnl-tiny - 0.1-5
> libopenssl - 1.0.2l-1
> libpthread - 1.1.16-1
> librt - 1.1.16-1
> libsmartcols - 2.30.1-2
> libubox - 2017-06-17-fd57eea9-1
> libubus - 2017-02-18-34c6e818-1
> libubus-lua - 2017-02-18-34c6e818-1
> libuci - 2017-04-12-c4df32b3-1
> libuci-lua - 2017-04-12-c4df32b3-1
> libuclient - 2016-12-09-52d955fd-1
> libustream-openssl - 2016-07-02-ec80adaa-2
> libuuid - 2.30.1-2
> libxtables - 1.6.1-1
> logd - 2017-03-03-21a4bd04-1
> lua - 5.1.5-1
> luci - git-18.138.35484-521554f-1
> luci-app-firewall - git-18.138.35484-521554f-1
> luci-base - git-18.138.35484-521554f-1
> luci-lib-ip - git-18.138.35484-521554f-1
> luci-lib-jsonc - git-18.138.35484-521554f-1
> luci-lib-nixio - git-18.138.35484-521554f-1
> luci-mod-admin-full - git-18.138.35484-521554f-1
> luci-proto-ipv6 - git-18.138.35484-521554f-1
> luci-proto-ppp - git-18.138.35484-521554f-1
> luci-theme-bootstrap - git-18.138.35484-521554f-1
> mtd - 21
> netifd - 2017-08-22-b5731bfb-1
> nstat - 4.11.0-1
> odhcp6c - 2017-03-22-0463b057-2
> odhcpd - 2017-08-16-94e65ee0-1
> openssl-util - 1.0.2l-1
> opkg - 2017-07-28-4bd8601e-1
> ppp - 2.4.7-12
> ppp-mod-pppoe - 2.4.7-12
> procd - 2017-08-22-54b46a35-1
> rpcd - 2016-12-03-0577cfc1-1
> rpcd-mod-rrdns - 20170710
> terminfo - 6.0-1
> trace-cmd - v2.6.1-1
> ubi-utils - 1.5.2-1
> ubox - 2017-03-03-21a4bd04-1
> ubus - 2017-02-18-34c6e818-1
> ubusd - 2017-02-18-34c6e818-1
> uci - 2017-04-12-c4df32b3-1
> uclient-fetch - 2016-12-09-52d955fd-1
> uhttpd - 2016-10-25-1628fa4b-2
> uhttpd-mod-ubus - 2016-10-25-1628fa4b-2
> usign - 2015-07-04-ef641914-1
> wmt - 4.9.44
> wpad-mini - 2016-12-19-ad02e79d-4

You are still using latest luci code, you have two ways to let luci to work:

  1. Apply below patch to file build/target…/lucihttp-2018-04-22-ccc685e5/lib/lua.c, and then rebuild project. image
  2. Use the code from https://github.com/openwrt/luci.git;lede-17.01, the commands are: 1). change feeds.conf.default 2). scripts/feeds update -a 3). scripts/feeds install -a 4). make -j1 V=s

so maybe my fault was not to enter the commands from step 2 to 3. I changed the feeds.conf.default but nothing was changed (without step 2,3) Thanks a lot @garywang I will give them a try

also i cannot find “build/target…/lucihttp-2018-04-22-ccc685e5/lib…”

bpi-r2_lede/build_dir/target-arm_cortex-a7+neon-vfpv4_musl_eabi/linux-mediatek_32/siit-1.2/siit.o’ failed

resolved with patch