vlad59

Check first 3 seconds of the first video : you can choose to generate a full image

AFAIK there's no way to do that, Instead use the same instruction and choose to create a full image instead of Kernel / U-boot packages.

In case that's useful, I reinstalled my Orange Pi +2E with latest DEV image. Everything seems to work (I can send a report if needed but the current one is quite recent). This morning I checked `dmesg` output for something else and I saw these three red lines (full armbianmonitor output is http://ix.io/1uAk) [ 6.087868] sun4i-codec 1c22c00.codec: ASoC: codec-analog@1f015c0 not registered [ 6.087882] sun4i-codec 1c22c00.codec: Failed to register our card [ 6.140691] sun8i_ths 1c25000.thermal-sensor: no memory resources defined I have no way to check if audio is working for now (I'm at work). But I checked DVFS / Thermal protection and it's works perfectly fine.

Fixed with a reboot ..... still don't know why but at least it works.

That's strange indeed. I did a git pull. I'll try to remove all the cache.

Hi, After building a DEV Pine64 image successfully, I wanted to build a Dev BananaPI image to update 2 banana pis. Unfortunately I have this error (using this commit id : e7aeffb1) : Setting up nplan (0.36.3) ... Setting up networkd-dispatcher (1.7-0ubuntu3.3) ... Installing new version of config file /etc/default/networkd-dispatcher ... Setting up gnupg (2.2.4-1ubuntu1.1) ... Processing triggers for libc-bin (2.27-3ubuntu1) ... Processing triggers for initramfs-tools (0.130ubuntu3.5) ... [ o.k. ] Installing packages for [ Armbian ] Reading package lists... Building dependency tree... Reading state information... E: Unable to locate package armbian-firmware [ error ] ERROR in function create_rootfs_cache [ debootstrap-ng.sh:216 ] [ error ] Installation of Armbian packages failed [ o.k. ] Process terminated [ error ] ERROR in function unmount_on_exit [ image-helpers.sh:60 ] [ error ] debootstrap-ng was interrupted [ o.k. ] Process terminated I'm trying to generate a new image. It's only the second image I'm trying to build, so maybe I forgot some cleanup somewhere. Thanks in advance.

@belfastraven It's great you also got it working. I bought 3 pine64 + 3 SDIO Wifi / BT addons and I got a faulty one, fortunately I tested all 3 three and I got another one for free ;). About bluetooth I also saw Anarsoul kernel, In case you didn't saw you may have to tweak the firmware blobs : * https://forum.manjaro.org/t/bluetooth-not-working-with-rtl8723bs-bt/51906/10 * https://github.com/lwfinger/rtl8723bs_bt/issues/28#issuecomment-432806835 If nobody beats me to it, I'll probably try to fix bluetooth next week.

Latest build from Armbian dev 4.19.2

Strange wifi is working on my Pine64 but I have an old SDIO adaptor : root@pine64:~# dmesg | grep 8723 [ 5.240274] r8723bs: module is from the staging directory, the quality is unknown, you have been warned. [ 5.287430] RTL8723BS: module init start [ 5.287439] RTL8723BS: rtl8723bs v4.3.5.5_12290.20140916_BTCOEX20140507-4E40 [ 5.287441] RTL8723BS: rtl8723bs BT-Coex version = BTCOEX20140507-4E40 [ 5.397757] RTL8723BS: rtw_ndev_init(wlan0) [ 5.406514] RTL8723BS: module init ret =0 [ 16.270611] rtl8723bs: acquire FW from file:rtlwifi/rtl8723bs_nic.bin

Report sent : https://github.com/armbian/testings/pull/122 As a side note, I have 2 Nanopi M1 (512Mo) collecting dust, I saw they are not supported anymore but will it help if I add a report for them ?

@belfastraven What problem do you have with wifi on your Pine64 ?

So I can confirm, a DEV image boots fine on my Pine64 (1G if that's important). I'll send a complete report later today. For now I can confirm that wired network is fine (Gigabit), Wifi network seems to work (scan is working but not tried to join one for now), Bluetooth don't work (nothing detected). I'll test HDMI before sending the report. To confirm I tested the right image : root@pine64:~# uname -a Linux pine64 4.19.2-sunxi64 #1 SMP Thu Nov 22 17:00:08 CET 2018 aarch64 aarch64 aarch64 GNU/Linux

I'm building an image for pine64 tonight and will test tomorrow. Will report back ASAP.

Else you can use plowdown (I'll let you google that), it a command line tool though.

it is faster (guaranted if you have more than one core because OpenVPN only use one core)

2 mounting holes on the same side will make any heatsink design "mechanically interesting"

Yes all the download went fine the second time, Next Pine64 build is on the way thanks ;).

Hi, I just made a brand new VM to build armbian this morning so after installing Bionic / checking out the sources, I started `compile.sh` for the first time and I got theses warning / errors (15 minutes ago) : E: Version '1.2.0' for 'aptly' was not found [ o.k. ] Syncing clock [ host ] [ .... ] Downloading [ gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux ] -=O=- # # # # curl: (7) Failed to connect to dl.armbian.com port 443: Connection refused curl: (7) Failed to connect to dl.armbian.com port 443: Connection refused [ .... ] Verifying grep: gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux.tar.xz.asc: No such file or directory md5sum: gcc-linaro-arm-linux-gnueabihf-4.8-2014.04_linux.tar.xz.asc: No such file or directory I just restarted it and it seems to work better (the downloading seems to be working). So no real problem there, just wanted to notify in case it may be important.

Once you see it with `i2cdetect` you can use any program on github : https://github.com/ControlEverythingCommunity/PCF8574 (being the first one) no need for WiringPi for i2c access

That's why the use case is very important and you have to be specific : if I/O (disk or network) is the most important for you, then RPi3 can be worse than an old Banana Pi. If your main problem is CPU then Rpi3 will be better. i.e. : * you run static website (hugo for example) -> disk I/O is not that important as most of your files will be cached * you run many Wordpress / MySQL databases -> Disk I/O is important * You serve very big files -> More than 1Go of RAM can be great and Gigabit ethernet is mandatory .....

You can use a normal kitchen oven ..... if your wife agree (at your own risk) and if you don't care about the smell afterwards.

I'm using the workaround for the last month but my Banana pi has not a lot of work to do (load average: 0,21, 0,15, 0,11) so I really don't know if there is a risk or not.

This is due the a kernel change so the distribution shoud not change that at all. You can use the search to find a palliative.

I got 2 banana pis running 24/7 for 4 years with SSD -> not any problem. I've got a spare one that I boot every year. I got 2 Pine64 used at work also running 24/7 for 1,5 year -> not any problem with the boards but I had to renew the SD on both Pine64. I also have Pine64 and various Nanopi that are not running 24/7 but still work fine. My 3 Rpis (only old ones : first 256Mb RpiB, another 512Mb and a RPI2) are also fine (used with Libreelec in various room at home) -> the SDcard never had a fail. So for SBC not a single fail. If I add others microcontrollers, never had a problem with my arduinos (mainly moteinos) but some Flash fails with ESP8266.

Thanks I'll test it at home and report back