All Activity

This stream auto-updates     

  1. Past hour
  2. Is disabled by default: [Time] #NTP= #RootDistanceMaxSec=5 #PollIntervalMinSec=32 #PollIntervalMaxSec=2048
  3. Welcome to help implementing this feature to armbian-config.
  4. Today
  5. Absolutely. What shell we do with this implementation ?
  6. Hi all, I got my hotspot working via armbian-config but I can't seem to edit the rules using ufw. Trying to block port xyz, any ideas how?
  7. as said by Lima maintainer: Qiang Yu, xfce4 runs OK on lima now we could start to integrate lima to Armbian. @Igor do you agree?
  8. Yesterday
  9. yep - this board does seem to be similar to the Sunvell board - straight NAND there, so need to build a flash filesystem on it... One might hope -- On the board - one would want to sort out the UART headers - seems there is a socket, so one should use a scope to sort them - then console output there would be quite helpful...
  10. See above - yes, you can... Be mindful of systemd-timesyncd - you might want to disable that one if one is running chrony, ntpd, or ntpsec.
  11. Might consider looking at SecureBoot That would be the first place to look - lock your board down there... And then start moving up the stack... sfx
  12. hi to all, I made my own board using the V3s and Im new to the embedded world. Is my intention to enable the ethernet port on V3s and following this links: 1)贡献/article 6.html 2) I cant cross-compile the dtbs. Im using licheepi-zero dts and sunxi8i-V3s.dtsi to enable ethernet. Did someone enable ethernet on V3s?
  13. Weekend job: - default kernel -> stock 4.9.y - next -> mainline 5.2.y
  14. - default kernel -> stock 4.9.y - next kernel -> 5.2.y (except Udoo)
  15. Its possible that this patch will not work on older v1 and v2 boards ... shell we rather create a new DTB for this one?
  16. Please provide: armbianmonitor -u It can help diagnosing this issue.
  17. root@aml:~# free -m total used free shared buff/cache available Mem: 3353 796 1947 67 609 2414 Swap: 1023 0 1023 IMHO for the maximum size of available memory can be used u-boot-2019 (it can be installed in eMMC) and specially optimized DTB (with minimal memory reserves for video and other things). But while u-boot-2019 for VIM3 is not in the public domain (it is, but not for General use ).
  18. The only reason I burned Ubuntu and not Android was because the Ubuntu build was newer and I was hoping that the latest u-boot patches was present. For me it doesn't really matter as I'm regardless going to install Armbian to eMMC and never use either Ubuntu or Android. Thanks for the tip btw I'll burn the next Android build when it arrive to see if RAM is increased. How much available RAM do you have with the build you are testing on your VIM3?
  19. When using Khadas Ubuntu in eMMC (using Ubuntu's option to write to eMMC via USB Burn Tool) is a bad option for General use with external systems (which run from SD card and USB flash drive). All versions of Khadas Ubuntu to write to eMMC, have an error in u-boot, which does not properly run external systems. If you want to run Armbian with external media, the eMMC should be strictly firmware with regular Android. I have explained this problem many times on the Khadas forum.
  20. What driver/chip do you want to build? Your better off getting the correct kernel source from (or armbian build) if its a popular driver not enabled in the current /boot/config. Search these forum threads for build instructions.
  21. I've attached a picture so you can see the issue I faced when I tested Armbian_5.94_Aml-g12_Debian_buster_default_5.2.1_20190821.img. I did a full erase of eMMC and burned latest Ubuntu (VIM3_Ubuntu-server-bionic_Linux-4.9_arm64_EMMC_V20190813) with USB Upgrade Tool before installing Armbian to eMMC the last time. How much RAM do you have with VIM3 with the build you are using?
  22. I checked the image on my VIM3, everything works correctly, there is no problem with the color or clarity of the text. If you run coreelec, for proper operation of other systems after it, you need to full erase the eMMC and restore the standard firmware.
  23. Hi @lifeform, Im trying do the same for Tp-link usb WiFi dongle drivers, but without succes becouse the @balbes150 armbian image I used does not have headers. I see you are trying with another aproach, could you please let me know which repo are you using and Wich are the main steps you are doing? Thanks a lot
  24. So the new kernel reserves almost 350 MB of RAM for video? Which means the latest patches for Khadas VIM3 u-boot (which is not present in theirs latest Android og Ubuntu builds) won't increase the amount available RAM if I start over by burning Android/Ubuntu to eMMC with latest u-boot and then install latest version of Armbian (Armbian_5.94_Aml-g12_Debian_buster_dev_5.3.0-rc5_20190825) to eMMC again?
  25. Coreelec uses an outdated system startup and kernel ( with serious problems in security), it is not compatible with Armbian and Libreelec. The new kernel reserves memory for video. According to the log, the kernel panic is caused by the absence of eMMC. You can try to change the DTB and remove the partition from eMMC (infu how to do this look in this and neighboring topics).
  26. Pay attention. The multi-boot scripts have been updated, I recommend to re-activate the multi-boot using the new scripts. In the scripts added ability to run Android without removing the external media Armbian. To do this in the first section of the external media (/boot) to create an empty file boot_android. If you have this file, each time you restart, either the external system or Android from eMMC will start in turn. To disable this mode, you need to delete the file boot_android external media.
  27. Hi Members, I've installed the latest avaiable image for my lamobo Ri (Debian GNU/Linux 8, Release 4.9.7-sunxi) from: I need to set the overscan parameters for my display, but can't find the formal used file: script.bin Please by what files/procedures are the values found in script.bin during boot are now replaced? Or does someone knows a newer armbian image for my BPI-R1 ? Regards Wolli
  28. Updated several HC1 to Buster. Reapplied the optimized board config, as done under stretch before. Main issue: No matter what CPU governor I set, max. frequency jumps around automagically between 1.8 GHz and 2.0 GHz. I can set performance governor to the range from 1.9 to 2.0 GHz, armbian-config confirms, and when I back out of the menu it says "soc runs between 1800 and 1800 MHz using performance governor". Even at > 90% CPU boards stay below 2.0 GHz. Minor glitches only for boards, I already upgraded from jessie to stretch: - boot.ini misses the hc1.dtb check - must manually edit - systemd misses armbian* entries, as well as the utilities referenced in /usr/lib/
  1. Load more activity