All Activity

This stream auto-updates     

  1. Past hour
  2. Thank you very much, vfrolov! I've suffered from the error messages on boot for long time and occasionally found your solution that worked for me.
  3. Today
  4. These days i did install on some devices debian buster (via armbian-build-system generated). On the Orange Pi One this did work also fine with the cpu-temperature (showing via armbianmonitor -m) On a Orange Pi PC2 and a NanoPi K1 Plus this doesnt work. First I did think this is a problem of the dev-image with debian buster where /sys/devices/virtual/thermal/thermal_zone0/temp doesnt show an output via cat or more - but its filesize does show a 4096 bytes size (also on a working device - and also rights 444 = rrr for the file): -r--r--r-- 1 root root 4096 May 20 10:47 temp BUT NOW after a apt update & apt upgrade I also got this "problem" on a NanoPi Neo2 LTS with a stable debian stretch image: Welcome to ARMBIAN 5.85 stable Debian GNU/Linux 9 (stretch) 5.1.0-sunxi64 package bsp-kernel[5.86] u-boot[5.85] dtb[5.86] firmware[5.83] config[5.86] with armbianmonitor -m the stretch and buster devices does show the following error: Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU 11:14:59: 1008MHz 0.22 7% 4% 2% 0% 0% 0%/usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected and the devices with this error got these - for me - new error messages about thermal in the dmesg: [ 6.727971] OF: /thermal-zones/cpu-thermal: arguments longer than property [ 6.728007] OF: /thermal-zones/cpu-thermal: arguments longer than property armbianmonitor -u for the NanoPi Neo2 LTS: root@npi-neo2-24( armbianmonitor -u System diagnosis information will now be uploaded to /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 385: read: read error: 0: Invalid argument /usr/bin/armbianmonitor: line 386: [: -ge: unary operator expected Please post the URL in the forum where you've been asked for.
  5. The same as always. OMV only works on Debian based Armbian.
  6. Dear Igor, This, "you need to have an active internet connection to setup AP" confused me a bit... I don't want to "share" the internet from another channel (another wifi or GPRS/3G) from my device... Basically my Orange Pi device will sit on a long pole and will create a WiFi access point at a definite time (between 23:00 and 24:00 for example) and my sensors will join the WiFi network Orange Pi created and send their data to Orange Pi. And at another certain time (for example every Sunday between 13:00 and 16:00) a mobile device with WiFi will come to collect data from Orange Pi. This time Orange Pi will join the mobile device's WiFi. For all this, only one WiFi adaptor should suffice without any internet connection.
  7. Dear Igor, I will try to establish an access point using hostapd directly instead of nmcli. I will also look at the armbian-config code. I will post the progress and maybe ask more. Thanx your prompt responses.
  8. Troubles means it can works under certain conditions, but sometimes or mostly not. Aha. I see now what is the problem. You need to have active internet connection to setup AP. If your only adaptor is already connected, you can not add AP to id. That is not supported in this driver/chip version. And if it would, performance would sucks.
  9. Dear Igor, I tried to use armbian-config (as your link suggested) to create a Hotspot but it fails... I will try to capture the failures... But even it works, it doesn't solve my problem. What I want is to be able to create and destroy wireless access point programmatically and only on certain conditions.
  10. Each kernel has its own version of the driver. Some needs special handling for AP mode and on some its (temporally?) broken. RPi is different hardware, has different kernel but by coincidence similar chip. One can not conclude anything from this mess. That's why I provide you safest option. In general, be (very) skeptical what you read around on the internet. Do some testings, read, test more, ...
  11. I am trying the first releases of armbian on my new odroid n2 and would like also to test openmediavault which should be available with 3rd party option on armbian-config. But at the moment this software option is not available. Is there a reason for this, maybe the device is very new and not tested for the moment?
  12. Thanx Igor... I will try your suggestion today... By the way, I researched more... Just for general knowledge for interested; wireless chip on Orange Pi Zero Plus 2 is AP6212 and it's kernel module on the mainline kernel is brcmfmac. The other module, dhd, is used on the sunxi-3.4 legacy kernel. For anybody interested: Another thing (to my surprise) nmcli worked on Raspberry Pi without needing any change...
  13. Try removing the u-boot loader from the eMMC and remove the startup scripts (boot.ini).
  14. Igor

    zd1211 driver

    How you did? root@nanopifire3:~# apt install firmware-zd1211 Reading package lists... Done Building dependency tree Reading state information... Done The following NEW packages will be installed: firmware-zd1211 0 upgraded, 1 newly installed, 0 to remove and 1 not upgraded. Need to get 14.3 kB of archives. After this operation, 66.6 kB of additional disk space will be used. Get:1 stretch/non-free arm64 firmware-zd1211 all 1:1.5-4 [14.3 kB] Fetched 14.3 kB in 0s (43.5 kB/s) Selecting previously unselected package firmware-zd1211. (Reading database ... 32249 files and directories currently installed.) Preparing to unpack .../firmware-zd1211_1%3a1.5-4_all.deb ... Unpacking firmware-zd1211 (1:1.5-4) ... Setting up firmware-zd1211 (1:1.5-4) ... root@nanopifire3:~#
  15. Runs like a Porsche Can you provide logs: armbianmonitor -u and a picture of PCB ... check if memory chip numbers perhaps begins with SEC710 K4B4G16 So far this problem was related to boards that have more than 1GB (NanoPC+)
  16. Try some older kernel versions (armbian-config -> system -> alternative kernels) or older images if that solves the problem. We are using different kernel and u-boot than FriendlyARM image or FriendlyARM image + bloatware (Dietpi). It is really strange what is happening to you. Never heart or seen such on this board ... it could only be slow this way if SD card is a broken one. I will check last version on my board later on ... Yes, Docker works OOB. Of course.
  17. Trying is the main purpose. Good! Usually none without R&D. Things in development are changing daily. If board is not declared stable, you are wasting your time, unless you are going to fix things.
  18. Hi there! I recently installed Armbian (Stretch: Armbian_5.83_Nanopifire3_Debian_stretch_next_4.14.115) on my new NanoPi Fire3. I was able to boot, but it responds so slow, that it is unusable! For example, when I SSH into it, it takes a log time to show me the login prompt. When I enter the username and press enter, it takes about 5 seconds to ask me for password. When I enter password, it takes about 10 seconds to show me the Armbian banner. I wasn't even able to go past the changing of unix password on first login, because it just "froze". I have installed the image twice on my SD card, just to make sure it isn't a corrupted install. I'm using a good PSU, and a good quality Samsung EVO 32GB sd card. I have tried installing DietPi, and FriendlyElec's 64 bit xenial image, without problems! This behavior happens only with Armbian. I want to use Armbian because I understood that it supports Docker on the Fire3 (is this true?) I haven't tried the Ubuntu version of Armbian, since it has Desktop, and I'm looking for a headless OS. BTW, is the Armbian Stretch image for the NanoPi 64 bit? Thank you guys for the excellent work!
  19. Support on most recent boards is not the same as on 10 years old technology. Here such things have to be developed, not just enabled, which is related with (huge) costs. There is no sign of CAN bus support and I am not sure this will be working anytime soon. If you need this feature on this hardware, you will need to invest into R&D ... Or just use a board that supports CAN the way you expect. Allwinner A20 based boards are known to work (but not much of an upgrade from RPi), most likely H3 & H5 as well. For others I can't tell without advanced research.
  20. nmcli has troubles in our world. I recommend setting up AP this way:
  21. You could ask for a replacement V7 board AND for a V5 board as some kind of compensation for all the trouble you had so far. My V5_0_1 boards are running 24/7 ...
  22. I am currently trying to set up the PICAN GPS+ACC Rev B on my NanoPi M4 in order to receive CAN connections. I have previously set this up on a Raspberry Pi with no issues, but because the NanoPi does not have /boot/config.txt and /boot/cmdline.txt I am at a loss at how to set up the module. Any information as to how I can go about using the module on the NanoPi would be much appreciated. The guide I used to set up the module on the Raspberry Pi is here Thanks
  23. Yesterday
  24. locally on rockpro64 i have done this but no dtb generated.. $ make INSTALL_DTBS_PATH=$PWD/../output/dtb dtbs CHK include/config/kernel.release CHK include/generated/uapi/linux/version.h CHK include/generated/utsrelease.h CHK include/generated/bounds.h CHK include/generated/timeconst.h CHK include/generated/asm-offsets.h CALL scripts/ make[1]: 'include/generated/vdso-offsets.h' is up to date. CHK scripts/mod/devicetable-offsets.h $ ls -la ../output total 8 drwxr-xr-x 2 labros labros 4096 May 23 08:10 . drwxr-xr-x 6 labros labros 4096 May 23 08:10 .. but is found this in custom kernel. Can i copy this dir manually in /boot and make symlink ? $ ls arch/arm64/boot/dts/rockchip Makefile rk3308-evb-amic-v11.dtb rk3328-box-liantong-avb.dts rk3368-px5-evb.dtb rk3399-evb-rev1-cros.dtb rk3399-opp.dtsi modules.order rk3308-evb-amic-v11.dts rk3328-box-liantong.dtb rk3368-px5-evb.dts rk3399-evb-rev1-cros.dts rk3399pro.dtsi px30-ad-d6-anx6345.dtb rk3308-evb-dmic-i2s-v10.dtb rk3328-box-liantong.dts rk3368-r88-dcdc.dtb rk3399-evb-rev1.dtsi rk3399pro-evb-v10.dtb px30-ad-d6-anx6345.dts rk3308-evb-dmic-i2s-v10.dts rk3328-box-liantong.dtsi rk3368-r88-dcdc.dts rk3399-evb-rev2-android-6.0.dtb rk3399pro-evb-v10.dts px30-ad-r35-mb-rk618-dual-lvds.dtb rk3308-evb-dmic-i2s-v11.dtb rk3328-box-plus-dram-timing.dtsi rk3368-r88.dtb rk3399-evb-rev2-android-6.0.dts rk3399pro-evb-v11.dtb px30-ad-r35-mb-rk618-dual-lvds.dts rk3308-evb-dmic-i2s-v11.dts rk3328-dram-2layer-timing.dtsi rk3368-r88.dts rk3399-evb-rev2-android.dtb rk3399pro-evb-v11.dts px30-ad-r35-mb-rk618-hdmi.dtb rk3308-evb-dmic-pdm-v10.dtb rk3328-dram-default-timing.dtsi rk3368-sheep.dtb rk3399-evb-rev2-android.dts rk3399pro-npu.dtsi px30-ad-r35-mb-rk618-hdmi.dts rk3308-evb-dmic-pdm-v10.dts rk3328.dtsi rk3368-sheep.dts rk3399-evb-rev2-cros.dtb rk3399pro-npu-evb-v10.dtb px30-ad-r35-mb-rk618-hdmi-lvds.dtb rk3308-evb-dmic-pdm-v11.dtb rk3328-evb-android-avb.dtb rk3368-sheep-lvds.dtb rk3399-evb-rev2-cros.dts rk3399pro-npu-evb-v10.dts px30-ad-r35-mb-rk618-hdmi-lvds.dts rk3308-evb-dmic-pdm-v11.dts rk3328-evb-android-avb.dts rk3368-sheep-lvds.dts rk3399-evb-rev2.dtsi rk3399-rock960-ab.dtb px30-ad-r35-mb-rk618-lvds.dtb rk3308-evb-ext-v10.dtsi rk3328-evb-android.dtb rk3368-sziauto-rk618.dtb rk3399-evb-rev3-android-6.0.dtb rk3399-rock960-ab.dts px30-ad-r35-mb-rk618-lvds.dts rk3308-evb-v10.dtsi rk3328-evb-android.dts rk3368-sziauto-rk618.dts rk3399-evb-rev3-android-6.0.dts rk3399-rockpro64.dtb px30-android.dtsi rk3308-evb-v11.dtsi rk3328-evb-android.dtsi rk3368-xikp-avb.dts rk3399-evb-rev3-android-6.0-edp.dtb rk3399-rockpro64.dts px30-dram-default-timing.dtsi rk3308-fpga.dtb rk3328-evb.dtb rk3368-xikp.dtb rk3399-evb-rev3-android-6.0-edp.dts rk3399-rv1-android.dtb px30.dtsi rk3308-fpga.dts rk3328-evb.dts rk3368-xikp.dts rk3399-evb-rev3-android.dtb rk3399-rv1-android.dts px30-evb-ddr3-lvds-v10.dtb rk3308k.dtsi rk3328-rock64-android-avb.dtb rk3368-xikp.dtsi rk3399-evb-rev3-android.dts rk3399-sapphire.dtsi px30-evb-ddr3-lvds-v10.dts rk3308-voice-module-board-v10.dtb rk3328-rock64-android-avb.dts rk3399-android-6.0.dtsi rk3399-evb-rev3-android-edp.dtb rk3399-sapphire-excavator-box-android-6.0.dtb px30-evb-ddr3-v10.dtb rk3308-voice-module-board-v10.dts rk3328-rock64-android.dtb rk3399-android.dtsi rk3399-evb-rev3-android-edp.dts rk3399-sapphire-excavator-box-android-6.0.dts px30-evb-ddr3-v10.dts rk3326-863-cif-sensor.dtsi rk3328-rock64-android.dts rk3399-box-808-android-6.0.dtb rk3399-evb-rev3-android-lp4.dtb rk3399-sapphire-excavator-box.dtb px30-evb-ddr3-v10-linux.dtb rk3326-863-lp3-v10-avb.dtb rk3328-rock64-android.dtsi rk3399-box-808-android-6.0.dts rk3399-evb-rev3-android-lp4.dts rk3399-sapphire-excavator-box.dts px30-evb-ddr3-v10-linux.dts rk3326-863-lp3-v10-avb.dts rk3328-rock64.dtb rk3399-box-android-6.0.dtsi rk3399-evb-rev3-android-mipi-edp.dtb rk3399-sapphire-excavator-disvr.dtb px30-evb-ddr4-v10.dtb rk3326-863-lp3-v10.dtb rk3328-rock64.dts rk3399-box.dtsi rk3399-evb-rev3-android-mipi-edp.dts rk3399-sapphire-excavator-disvr.dts px30-evb-ddr4-v10.dts rk3326-863-lp3-v10.dts rk3366-android-6.0.dtsi rk3399-box-rev1-android-6.0.dtb rk3399-evb-rev3-cros.dtb rk3399-sapphire-excavator-edp-android-6.0.dtb px30-evb-ext-rk618.dtb rk3326-863-lp3-v10.dtsi rk3366-android.dtsi rk3399-box-rev1-android-6.0.dts rk3399-evb-rev3-cros.dts rk3399-sapphire-excavator-edp-android-6.0.dts px30-evb-ext-rk618.dts rk3326-86v-v10.dtb rk3366.dtsi rk3399-box-rev1-disvr.dtb rk3399-evb-rev3.dtsi rk3399-sapphire-excavator-edp-avb.dtb px30-z7-a0-rk618-dsi.dtb rk3326-86v-v10.dts rk3366-fpga.dtb rk3399-box-rev1-disvr.dts rk3399-excavator-sapphire.dtsi rk3399-sapphire-excavator-edp-avb.dts px30-z7-a0-rk618-dsi.dts rk3326.dtsi rk3366-fpga.dts rk3399-box-rev1.dtb rk3399-firefly-android.dtb rk3399-sapphire-excavator-edp.dtb rk1808-dram-default-timing.dtsi rk3326-evb-ai-va-v10.dtb rk3366-sheep.dtb rk3399-box-rev1.dts rk3399-firefly-android.dts rk3399-sapphire-excavator-edp.dts rk1808.dtsi rk3326-evb-ai-va-v10.dts rk3366-sheep.dts rk3399-box-rev2-android-6.0.dtb rk3399-firefly-linux.dtb rk3399-sapphire-excavator-edp.dtsi rk1808-evb.dtsi rk3326-evb-ai-va-v11.dtb rk3366-tb.dts rk3399-box-rev2-android-6.0.dts rk3399-firefly-linux.dts rk3399-sapphire-excavator-linux.dtb rk1808-evb-v10.dtb rk3326-evb-ai-va-v11.dts rk3368-android.dtsi rk3399-box-rev2-disvr.dtb rk3399-fpga.dtb rk3399-sapphire-excavator-linux.dts rk1808-evb-v10.dts rk3326-evb-ai-va-v11-i2s-dmic.dtb rk3368-cif-sensor.dtsi rk3399-box-rev2-disvr.dts rk3399-fpga.dts rk3399-sched-energy.dtsi rk1808-evb-x4.dtb rk3326-evb-ai-va-v11-i2s-dmic.dts rk3368-dram-default-timing.dtsi rk3399-box-rev2.dtb rk3399-gru.dtsi rk3399-tve1030g-avb.dtb rk1808-evb-x4.dts rk3326-evb-lp3-v10-avb.dtb rk3368.dtsi rk3399-box-rev2.dts rk3399-gru-gru.dtb rk3399-tve1030g-avb.dts rk1808-fpga.dtb rk3326-evb-lp3-v10-avb.dts rk3368-evb-act8846.dtb rk3399-disvr-android.dtb rk3399-gru-gru.dts rk3399-tve1030g.dtb rk1808-fpga.dts rk3326-evb-lp3-v10.dtb rk3368-evb-act8846.dts rk3399-disvr-android.dts rk3399-gru-kevin-r0.dtb rk3399-tve1030g.dts rk3308-ai-va-v10.dtb rk3326-evb-lp3-v10.dts rk3368-evb.dtsi rk3399-dram-default-timing.dtsi rk3399-gru-kevin-r0.dts rk3399-tve1030g.dtsi rk3308-ai-va-v10.dts rk3326-evb-lp3-v10.dtsi rk3368-geekbox.dtb rk3399.dtsi rk3399-gru-kevin-r1.dtb rk3399-tve1205g.dtb rk3308b-evb-amic-v10.dtb rk3326-evb-lp3-v10-linux.dtb rk3368-geekbox.dts rk3399-early-opp.dtsi rk3399-gru-kevin-r1.dts rk3399-tve1205g.dts rk3308b-evb-amic-v10.dts rk3326-evb-lp3-v10-linux.dts rk3368-p9-avb.dts rk3399-evb-cros.dtsi rk3399k-opp.dtsi rk3399-videostrong-linux.dtb rk3308b-evb-ext-v10.dtsi rk3326-evb-lp3-v10-robot-linux.dtb rk3368-p9.dtb rk3399-evb.dtsi rk3399-linux.dtsi rk3399-videostrong-linux.dts rk3308b-evb-v10.dtsi rk3326-evb-lp3-v10-robot-linux.dts rk3368-p9.dts rk3399-evb-rev1-android-6.0.dtb rk3399-mid-818-android-6.0.dtb rk3399-vop-clk-set.dtsi rk3308.dtsi rk3326-linux.dtsi rk3368-p9.dtsi rk3399-evb-rev1-android-6.0.dts rk3399-mid-818-android-6.0.dts rk3399-vr-android.dtb rk3308-evb-amic-v10.dtb rk3328-android.dtsi rk3368-px5-evb-android.dtb rk3399-evb-rev1-android.dtb rk3399-mid-818-android.dtb rk3399-vr-android.dts rk3308-evb-amic-v10.dts rk3328-box-liantong-avb.dtb rk3368-px5-evb-android.dts rk3399-evb-rev1-android.dts rk3399-mid-818-android.dts
  25. If I'm not too late, I too have this issue with OPi R1, but I'm using Armbian Stretch 5.83. I found a (very bad) workaround: rmmod 8189es; modprobe 8189es I think there is something wrong with this driver, but I did not investigate further. Hope this can help.
  26. Hi, sorry for the confusion. I was assuming, that you are going to build a DTS for the ADS7846 and maybe a second one for the ili9x Display to support the WaveShare Display. I do have a WaveShare display and a second one, driver-wise compatible, but using different pins. For the ili-Display I used options in the module-loading to adapt from WaveShare to the other Display with the ili-driver-module. For the ADS I know, that there can't be options in the module, so they need to be used at the DTS. For DTS / DT Overlays I have read half a day how it works, and found with google, that they can be decomplied forth and back. But this doesn't work for me somehow. Still a beginner there. Sorry again, and I do appreciate your help. If you can point me to a guide, how to rebuild the kernel with DTS and so on, that I can follow, I'm willing to learn and try. Thanks in advance, kind regards, Olaf
  27. Is inconsistent with And I'll disregard your caps yelling over a 20 minute first try using the information you provided and we'll move forward.lockquote widget. I'll give it another try and post the source later, but you need to do some different stuff to compile it.
  1. Load more activity