All Activity

This stream auto-updates     

  1. Past hour
  2. gounthar

    Sunvell H3 2GB RAM + 16GB ROM TV Box

    Started up this small machine tonight, and I am impressed. It's the best version of Android I have seen on AllWinner Hx (ok, I only tried OrangePi's Android versions on the Zero and the One Plus). Pretty responsive, adb does work: $ adb connect 192.168.0.21 already connected to 192.168.0.21:5555 $ adb devices List of devices attached 192.168.0.21:5555 device dolphin-fvd-p1:/ # cat /proc/cpuinfo cat /proc/cpuinfo processor : 0 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 48.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 processor : 1 model name : ARMv7 Processor rev 5 (v7l) BogoMIPS : 48.00 Features : half thumb fastmult vfp edsp neon vfpv3 tls vfpv4 idiva idivt vfpd32 lpae CPU implementer : 0x41 CPU architecture: 7 CPU variant : 0x0 CPU part : 0xc07 CPU revision : 5 Hardware : sun8iw7 Revision : 0000 Serial : 740078864424142508d1 I don't know Kodi well enough to test the functionalities, but it launched and gave me a few info. I will take some bad pics and post them. I don't know either what we could do with that, but there is this directory: dolphin-fvd-p1:/proc/device-tree # ls ls #address-cells dvfs_table prcm #size-cells firmware psci aliases gpu@0x01c40000 s_brom bt interrupt-controller@1c81000 soc@01c00000 btlpm interrupt-parent sunxi-chipid@01c14200 chosen ion sunxi-sid@01c14000 clocks memory@40000000 timer compatible model uboot cpus n_brom watchdog@01c20ca0 cpuscfg name wlan dram opp_dvfs_table dramfreq pmu The kernel is not that old: dolphin-fvd-p1:/proc # uname -a uname -a Linux localhost 4.4.55 #1 SMP PREEMPT Tue Aug 14 11:27:43 CST 2018 armv7l
  3. Today
  4. ... and I have build it and pushed to Armbian stable repository (Stretch, Xenial and Bionic; armhf+arm64). First boot scripts also creates CPUfreq config based on CPU count. More can be added if there is an interest ... Package can be installed via apt update and upgrade while auto config feature will work only on self made images.
  5. constantius

    Le Potato general topics

    Hi I have build Armbian Bionic 5.64 and 5.46 with XFCE desktop and system works only to the first reboot. After reboot i see only black screen. Kernels 4.18 and 4.16
  6. moved to p2p cause hardware but not really armbian related. not really, never had to deal with thermal zones for h3. go through the armbianmonitor related parts of the buidscript to get a clue.. if everything in kernel is there.. dt too then you've to nail down user-space... e.g. https://github.com/armbian/build/blob/624132790f0514cec0316538b752c733591a2f6f/packages/bsp/common/usr/lib/armbian/armbian-hardware-monitor#L39-L49 maybe we patched something as well.. I've really no idea. H3 was quite mature when I started to deal with such stuff...
  7. Hi, had the same problem here with bananapi. The LAN interface got no IPV4 Address, only IPV6 (over DHCP). I have removed networkmanager and assigned a static IPv4 Address in my router for the BPi board. That solved my problem. This is only a workaround, not a solution. I think the problem should be reproducible with the current Armbian distro. Steve
  8. I'll split it.. cause IMO we go a way of topic here... (last post from) which 'bpi kernel'? the 4.9 bsp, @frank-ws 4.14? If 4.9, well my interest is minor if nobody has a proper patchset for mainline.. I decided shortly after starting that I won't deal with the 4.9 kernel, the whole network part differs from their mainline implementation I had a lot of build errors and a kernel with no git history.. The only thing which looks sane to me is 4.19 (since LTS and support of MT7623 matured a lot.. there were changes in the network related stuff between 4.14 and 4.15 if I've it right in mind and I never want to deal with backports there.. Frank did or tried it and spend a lot of time to provide a kernel based on 4.14 - appreciated but to much efforts needed IMO, honestly the interest here was too low to put much efforts in it. Upstream U-boot needs some adjustments, basically it works/can work (it boots up, but I would need to write a proper bootscript and configure it properly ), a default network config is there (all RJ45 bridged) MTKs crypto kernelmodules are there. As long as this is a 'one man show' development is slow cause I don't use the R2 productive and I don't have projects which rely on it. It would be nice to separate IoT nodes from the rest of my network (e.g. keep insecure thingies separated). As long as nobody wants to contribute and test this will be AS IS. I may fix u-boot so that it properly boots into Linux and stick everything to 4.19. Hardware drivers for USB, SATA and network are there.. Wifi won't be there until its manilined (which likely never happens - and my interest in wifi is minor to port it). mPCI 'should' work (e.g. nothing suspicious in dmesg) HDMI is untested.
  9. Yes, this was my first attempt a lot of time ago. However, as you describe, things in R2 were very unstable those days. Also, cryptodev it is not an official part of the Kernel, so I prefer to use AF_ALG. (the only problem with these things is that the documentation it is horrible, inaccurate and incomplete ... you need to catch details from everywhere to understand what to do). And you are right, it is necessary to recompile openssl for cryptodev ... but also to obtain the AF_ALG openssl driver (in openssl) and the module (for the kernel). In general, openssl it is not prepared from factory to work with this type of extensions that are very important for some types of hardware as the R2. In fact, AF_ALG works well, just that the corresponding modules are not included by default (I really don't know why). My current efforts are related with why crytposetup can't use AF_ALG without the BPI kernel (there is something with the drivers). But, although not so fast, LUKS works well on the R2 even without the hardware support.
  10. Captain Chaos, I don't have the time to read each time 10 posts and make notes to find out where we are standing form on post and topic to the next. Fazit: I never considered to take part in this discussion here - too inefficient. On the Excel you can write: @chwe to each topic and leave your comment to each topic and so can others. Where all agree we can solve it, where not we can discuss in the forum in a dedicated Thread, for example a series that starts with: AB improvements: xyz . Why you would drop: Bananapi PRO is a miracle to me.
  11. Just In case anyone is interested I have pushed HTOP 2.2.1 to github, so it is possible to monitor big.LITTLE cores in real-time. You can view the big.LITTLE in action, Vcore, Cpu thermal throttling and Cpu frequency for each big or LITTLE core. HTOP is a nice console graphical tool for system-monitor, process-viewer and process-manager. DEB package and source code in case you want to extend or fix things. Be aware the process list and task can be very intrusive if you want to monitor many things at once. It has been tested on NanoPi M4 (thanks to FriendlyElec for the samples) but should work on any SBC just adjust the Vcore path for different kernel version. https://github.com/avafinger/htop-2.1.1_enhanced-version
  12. for the part which is now green.. It's around 2 weeks there and nobody insisted.. Should we announce in their subforums that those boards/kernels seek either a new maintainer or they get dropped? Or just for the bords? E.g. 'maintainership' includes proper testing of boards before each 'major' release (e.g. subversion kernel change for next, or u-boot change) testing and adjusting patches in dev after every sublevel jump.
  13. I have tested the OV5640 driver on K1+ (H5) only. According to @Igor comment, OV5640 is enabled on NeoAir (H3). Please see the patch: https://github.com/armbian/build/commit/10e206519089b8ff81b0dd6a6f3caa6c1adba04d - # Linux/arm 4.17.0-rc3 Kernel Configuration + # Linux/arm 4.17.2 Kernel Configuration I think you should apply this patch to your board and see if it works.
  14. I think this would help too, I don't want to wash my eyes with a soap after reading some threads. Something like this will do: Not sure if it needs rules or just explanation. After a 'soap moment' I wrote once such a explanation but never published it: Maybe sufficient? maybe it needs to be more strict? Something like this pinned on every subforum once again mighthelp.
  15. DS Justice

    Bcache-tools not building module on 4.18.6

    Yes, well past that. Reinstalled, reconfigured, the works. I have: $ lsinitramfs /boot/initrd.img-4.18.6-mvebu64 | grep bcache lib/udev/probe-bcache lib/udev/bcache-register lib/udev/rules.d/69-bcache.rules A working system would have an element under lib/modules as well.
  16. Seasalt

    NanoPi NEO4

    This is a good review of the Nano Pi M4.
  17. System Information: - Cubietruck with Ubuntu 16.04 - armbian-config 5.62 - armbian-firmware 5.60 - armbian-tools-xenial 5.60 Hallo since last few updated I've noticed that I have no logs... With some update armbian ram logging was enabled and all logs moved to log.hdd folder, but not all of them are filled up after this operation. I did disabled armbian-ram-loggin wia editing /etc/default/armbian-ramlog: ENABLED=false After this services was disabled, but no logs filled in a log folder... Also no log rotation happens. # /var/log/ls -lah total 116K drwxrwxr-x 13 root syslog 4.0K Oct 15 06:30 . drwxr-xr-x 16 root root 4.0K May 4 13:42 .. -rw-r--r-- 1 root root 0 Oct 15 14:45 alternatives.log drwxr-x--- 2 root adm 4.0K Oct 15 06:30 apache2 drwxr-xr-x 2 root root 4.0K Sep 21 20:00 apt -rw-rw-r-- 1 vpn sambashare 0 Oct 15 14:45 aria2.log -rw-r--r-- 1 root root 0 Oct 15 14:45 armbian-hardware-monitor.log -rw-r--r-- 1 root root 0 Oct 15 14:45 armbian-ramlog.log -rw-r--r-- 1 root root 0 Oct 15 14:45 armhwinfo.log -rw-r----- 1 syslog adm 1.3K Oct 15 14:55 auth.log -rw-r--r-- 1 root root 0 Oct 15 14:45 backup_2f695.log -rw-r--r-- 1 root root 0 Oct 15 14:45 battery_checker.log -rw-r--r-- 1 root root 0 Oct 15 14:45 bootstrap.log -rw------- 1 root utmp 0 Oct 15 14:45 btmp drwxr-xr-x 2 www-data www-data 4.0K Oct 14 06:30 cacti drwxr-xr-x 2 root root 4.0K Sep 21 20:00 dbconfig-common -rw-r----- 1 root adm 31 Feb 5 2017 dmesg -rw-r--r-- 1 root root 0 Oct 15 14:45 dpkg.log -rw-r----- 1 root adm 237 Oct 15 14:48 fail2ban.log -rw-r--r-- 1 root root 0 Oct 15 14:45 faillog -rw-r--r-- 1 root root 0 Oct 15 14:45 fontconfig.log drwxr-xr-x 2 root root 4.0K Feb 5 2017 fsck -rw-r----- 1 syslog adm 0 Oct 15 14:45 kern.log -rw-r--r-- 1 root root 13 Oct 15 00:01 last_ip -rw-rw-r-- 1 root utmp 0 Oct 15 14:45 lastlog drwx------ 2 root root 4.0K Oct 15 03:18 letsencrypt -rw-r--r-- 1 root root 0 Oct 15 14:45 log2ram.log -rw-r----- 1 syslog adm 18K Oct 15 14:45 mail.err -rw-r----- 1 syslog adm 1.4K Oct 15 14:45 mail.log -rw-r--r-- 1 root root 24 Feb 27 2018 md5sum -rw-r--r-- 1 minidlna minidlna 0 Oct 15 14:45 minidlna.log drwxr-s--- 2 mysql adm 4.0K Oct 6 06:30 mysql -rw-r--r-- 1 root root 0 Oct 15 14:45 nand-sata-install.log -rw-r--r-- 1 www-data www-data 0 Oct 15 14:45 next-cron.log lrwxrwxrwx 1 root root 35 Mar 5 2018 nextcloud.log -> ../www/nextcloud/data/nextcloud.log -rw-r--r-- 1 root root 0 Oct 15 14:45 noip.log drwxr-xr-x 2 ntp ntp 4.0K Oct 5 2016 ntpstats -rw------- 1 root root 749 Oct 15 14:55 php7.0-fpm.log -rw-r--r-- 1 syslog syslog 3.7K Oct 15 14:55 remote.log drwxr-x--- 3 root adm 4.0K Oct 7 06:30 samba -rw-rw-rw- 1 root root 3.8K Oct 15 14:58 socks.log -rw-r----- 1 syslog adm 2.5K Oct 15 14:55 syslog drwxr-xr-x 2 root root 4.0K May 12 2016 sysstat -rw-r--r-- 1 root root 0 Oct 15 14:45 systembackup.log drwxr-x--- 2 root adm 4.0K Sep 21 20:00 unattended-upgrades -rw-rw-r-- 1 root utmp 0 Oct 15 14:45 wtmp # ls -lah ../log.hdd total 5.0M drwxrwxr-x 13 root root 4.0K Oct 5 06:30 . drwxr-xr-x 16 root root 4.0K May 4 13:42 .. -rw-r--r-- 1 root root 0 Oct 5 09:45 alternatives.log -rw-r--r-- 1 root root 1.3K Aug 31 06:31 alternatives.log.1 -rw-r--r-- 1 root root 198 Jul 31 06:22 alternatives.log.2.gz -rw-r--r-- 1 root root 177 Jun 15 09:13 alternatives.log.3.gz -rw-r--r-- 1 root root 206 May 24 06:42 alternatives.log.4.gz -rw-r--r-- 1 root root 252 Apr 27 08:30 alternatives.log.5.gz -rw-r--r-- 1 root root 533 Mar 20 2018 alternatives.log.6.gz -rw-r--r-- 1 root root 377 Feb 16 2018 alternatives.log.7.gz -rw-r--r-- 1 root root 2.8K Jan 23 2018 alternatives.log.8.gz drwxr-x--- 2 root root 4.0K Oct 5 06:30 apache2 drwxr-xr-x 2 root root 4.0K Sep 21 20:00 apt -rw-rw-r-- 1 root root 0 Oct 5 09:45 aria2.log -rw-rw-r-- 1 root root 283 Oct 1 06:25 aria2.log.1.gz -rw-rw-r-- 1 root root 5.2K Aug 1 06:25 aria2.log.2.gz -rw-rw-r-- 1 root root 28K Jul 1 06:25 aria2.log.3.gz -rw-r--r-- 1 root root 0 Oct 5 09:45 armbian-hardware-monitor.log -rw-r--r-- 1 root root 516K Oct 5 10:00 armbian-ramlog.log -rw-r--r-- 1 root root 0 Oct 5 09:45 armhwinfo.log -rw-r--r-- 1 root root 82K Jul 6 01:23 armhwinfo.log.1.gz -rw-r--r-- 1 root root 73K Jan 27 2018 armhwinfo.log.10.gz -rw-r--r-- 1 root root 28K Jun 12 08:40 armhwinfo.log.2.gz -rw-r--r-- 1 root root 14K May 14 02:17 armhwinfo.log.3.gz -rw-r--r-- 1 root root 44K Apr 27 21:37 armhwinfo.log.4.gz -rw-r--r-- 1 root root 16K Apr 15 2018 armhwinfo.log.5.gz -rw-r--r-- 1 root root 16K Mar 18 2018 armhwinfo.log.6.gz -rw-r--r-- 1 root root 31K Mar 1 2018 armhwinfo.log.7.gz -rw-r--r-- 1 root root 16K Feb 26 2018 armhwinfo.log.8.gz -rw-r--r-- 1 root root 16K Jan 30 2018 armhwinfo.log.9.gz -rw-r----- 1 root root 2.0K Oct 5 10:00 auth.log -rw-r----- 1 root root 19K Oct 1 06:25 auth.log.1 -rw-r----- 1 root root 0 Feb 25 2018 auth.log.1.gz -rw-r----- 1 root root 77K Sep 9 06:25 auth.log.2.gz -rw-r----- 1 root root 66K Sep 2 06:25 auth.log.3.gz -rw-r----- 1 root root 90K Aug 27 06:25 auth.log.4.gz -rw-r--r-- 1 root root 0 Oct 5 09:45 backup_2f695.log -rw-r--r-- 1 root root 0 Oct 5 09:45 battery_checker.log -rw-r--r-- 1 root root 126 Oct 5 06:17 battery_checker.log.1.gz -rw-r--r-- 1 root root 4.3K Aug 1 06:17 battery_checker.log.2.gz -rw-r--r-- 1 root root 1.8K Jul 1 06:17 battery_checker.log.3.gz -rw-r--r-- 1 root root 0 Oct 5 09:45 bootstrap.log -rw------- 1 root root 0 Oct 5 09:45 btmp -rw------- 1 root root 60 Apr 10 2018 btmp.1.gz drwxr-xr-x 2 root root 4.0K Oct 5 06:30 cacti drwxr-xr-x 2 root root 4.0K Sep 21 20:00 dbconfig-common -rw-r----- 1 root root 31 Feb 5 2017 dmesg -rw-r--r-- 1 root root 0 Oct 5 09:45 dpkg.log -rw-r--r-- 1 root root 42K Aug 31 06:31 dpkg.log.1 -rw-r--r-- 1 root root 6.9K Jul 31 06:22 dpkg.log.2.gz -rw-r--r-- 1 root root 4.1K Jun 28 06:36 dpkg.log.3.gz -rw-r--r-- 1 root root 4.2K May 29 08:55 dpkg.log.4.gz -rw-r--r-- 1 root root 5.7K Apr 27 11:24 dpkg.log.5.gz -rw-r--r-- 1 root root 8.4K Mar 29 2018 dpkg.log.6.gz -rw-r--r-- 1 root root 13K Feb 27 2018 dpkg.log.7.gz -rw-r--r-- 1 root root 57K Jan 30 2018 dpkg.log.8.gz -rw-r----- 1 root root 0 Oct 5 09:45 fail2ban.log -rw-r----- 1 root root 110 Oct 5 06:25 fail2ban.log.1 -rw-r----- 1 root root 2.6K Sep 9 00:32 fail2ban.log.2.gz -rw-r----- 1 root root 2.3K Sep 2 00:48 fail2ban.log.3.gz -rw-r----- 1 root root 2.9K Aug 27 00:58 fail2ban.log.4.gz -rw-r--r-- 1 root root 0 Oct 5 09:45 faillog -rw-r--r-- 1 root root 0 Oct 5 09:45 fontconfig.log drwxr-xr-x 2 root root 4.0K Feb 5 2017 fsck -rw-r----- 1 root root 0 Oct 5 09:45 kern.log -rw-r----- 1 root root 5.7K Sep 30 00:06 kern.log.1 -rw-r----- 1 root root 2.6K Sep 9 02:22 kern.log.2.gz -rw-r----- 1 root root 1.8K Sep 2 00:48 kern.log.3.gz -rw-r----- 1 root root 2.4K Aug 27 00:58 kern.log.4.gz -rw-r--r-- 1 root root 13 Oct 5 00:33 last_ip -rw-rw-r-- 1 root root 0 Oct 5 09:45 lastlog drwx------ 2 root root 4.0K Oct 4 20:15 letsencrypt -rw-r--r-- 1 root root 0 Oct 5 09:45 log2ram.log -rw-r----- 1 root root 10K Oct 5 09:45 mail.err -rw-r----- 1 root root 51K Oct 1 04:15 mail.err.1 -rw-r----- 1 root root 0 Feb 25 2018 mail.err.1.gz -rw-r----- 1 root root 607 Sep 9 02:55 mail.err.2.gz -rw-r----- 1 root root 603 Sep 2 02:44 mail.err.3.gz -rw-r----- 1 root root 576 Aug 27 02:56 mail.err.4.gz -rw-r----- 1 root root 1.4K Oct 5 09:45 mail.log -rw-r----- 1 root root 1.4K Oct 1 04:15 mail.log.1 -rw-r----- 1 root root 0 Feb 25 2018 mail.log.1.gz -rw-r----- 1 root root 5.1K Sep 9 02:55 mail.log.2.gz -rw-r----- 1 root root 5.5K Sep 2 02:44 mail.log.3.gz -rw-r----- 1 root root 5.2K Aug 27 02:56 mail.log.4.gz -rw-r--r-- 1 root root 24 Feb 27 2018 md5sum -rw-r--r-- 1 root root 0 Oct 5 09:45 minidlna.log -rw-r--r-- 1 root root 1013 Sep 29 06:27 minidlna.log.1 -rw-r--r-- 1 root root 926 Sep 9 06:25 minidlna.log.2.gz -rw-r--r-- 1 root root 1.1K Sep 2 06:25 minidlna.log.3.gz -rw-r--r-- 1 root root 17K Aug 27 06:25 minidlna.log.4.gz drwxr-s--- 2 root root 4.0K Oct 5 06:30 mysql -rw-r--r-- 1 root root 0 Oct 5 09:45 nand-sata-install.log -rw-r--r-- 1 root root 0 Oct 5 09:45 next-cron.log -rw-r--r-- 1 root root 2.7K Aug 22 12:13 next-cron.log.1.gz -rw-r--r-- 1 root root 3.4K Aug 1 03:56 next-cron.log.2.gz -rw-r--r-- 1 root root 9.0K Jul 1 04:05 next-cron.log.3.gz lrwxrwxrwx 1 root root 35 Mar 5 2018 nextcloud.log -> ../www/nextcloud/data/nextcloud.log -rw-r----- 1 root root 234K Aug 24 06:19 nextcloud.log.1.gz -rw-r----- 1 root root 264K Aug 16 06:15 nextcloud.log.2.gz -rw-r----- 1 root root 186K Aug 8 06:20 nextcloud.log.3.gz -rw-r----- 1 root root 263K Aug 4 06:19 nextcloud.log.4.gz -rw-r----- 1 root root 279K Jul 27 06:22 nextcloud.log.5.gz -rw-r----- 1 root root 270K Jul 18 06:21 nextcloud.log.6.gz -rw-r----- 1 root root 265K Jul 8 05:48 nextcloud.log.7.gz -rw-r----- 1 root root 253K Jun 28 06:20 nextcloud.log.8.gz -rw-r--r-- 1 root root 0 Oct 5 09:45 noip.log -rw-r--r-- 1 root root 105 Oct 2 00:46 noip.log.1.gz -rw-r--r-- 1 root root 303 Aug 1 00:58 noip.log.2.gz -rw-r--r-- 1 root root 1.2K Jul 1 00:32 noip.log.3.gz drwxr-xr-x 2 root root 4.0K Oct 5 2016 ntpstats -rw------- 1 root root 0 Oct 5 09:45 php7.0-fpm.log -rw------- 1 root root 321 Sep 29 20:56 php7.0-fpm.log.1 -rw------- 1 root root 0 Feb 25 2018 php7.0-fpm.log.1.gz -rw------- 1 root root 277 Jul 14 23:35 php7.0-fpm.log.10.gz -rw------- 1 root root 619 Jul 6 20:55 php7.0-fpm.log.11.gz -rw------- 1 root root 364 Jul 1 21:58 php7.0-fpm.log.12.gz -rw------- 1 root root 440 Sep 8 20:47 php7.0-fpm.log.2.gz -rw------- 1 root root 531 Sep 1 10:53 php7.0-fpm.log.3.gz -rw------- 1 root root 912 Aug 26 21:14 php7.0-fpm.log.4.gz -rw------- 1 root root 560 Aug 18 22:12 php7.0-fpm.log.5.gz -rw------- 1 root root 1.1K Aug 12 18:45 php7.0-fpm.log.6.gz -rw------- 1 root root 663 Aug 5 04:02 php7.0-fpm.log.7.gz -rw------- 1 root root 920 Jul 28 21:41 php7.0-fpm.log.8.gz -rw------- 1 root root 653 Jul 22 14:08 php7.0-fpm.log.9.gz -rw-r--r-- 1 root root 6.4K Oct 5 10:00 remote.log -rw-r--r-- 1 root root 48K Oct 1 06:25 remote.log.1 -rw-r--r-- 1 root root 192K Sep 9 06:25 remote.log.2.gz -rw-r--r-- 1 root root 186K Sep 2 06:25 remote.log.3.gz -rw-r--r-- 1 root root 325K Aug 27 06:25 remote.log.4.gz drwxr-x--- 3 root root 4.0K Oct 5 06:30 samba -rw-rw-rw- 1 root root 0 Oct 5 09:45 socks.log -rw-rw-rw- 1 root root 3.0K Oct 5 06:30 socks.log.1 -rw-rw-rw- 1 root root 76K Sep 10 16:40 socks.log.2.gz -rw-rw-rw- 1 root root 53K Sep 3 06:25 socks.log.3.gz -rw-rw-rw- 1 root root 47K Aug 28 06:29 socks.log.4.gz -rw-rw-rw- 1 root root 42K Aug 20 06:25 socks.log.5.gz -rw-r----- 1 root root 4.5K Oct 5 10:00 syslog -rw-r----- 1 root root 4.5K Oct 5 06:25 syslog.1 -rw-r----- 1 root root 0 Feb 26 2018 syslog.1.gz -rw-r----- 1 root root 0 Feb 24 2018 syslog.1.gz-2018022506.backup -rw-r----- 1 root root 0 Feb 25 2018 syslog.1.gz-2018022606.backup -rw-r----- 1 root root 0 Feb 26 2018 syslog.1.gz-2018022706.backup -rw-r----- 1 root root 18K Oct 3 06:25 syslog.2.gz -rw-r----- 1 root root 29K Oct 2 06:25 syslog.3.gz -rw-r----- 1 root root 3.3K Oct 1 06:25 syslog.4.gz -rw-r----- 1 root root 42K Sep 30 06:25 syslog.5.gz -rw-r----- 1 root root 17K Sep 29 06:25 syslog.6.gz -rw-r----- 1 root root 67K Sep 28 06:25 syslog.7.gz drwxr-xr-x 2 root root 4.0K May 12 2016 sysstat -rw-r--r-- 1 root root 0 Oct 5 09:45 systembackup.log -rw-r--r-- 1 root root 67K Sep 1 00:58 systembackup.log.1.gz -rw-r--r-- 1 root root 126 Aug 1 00:00 systembackup.log.2.gz -rw-r--r-- 1 root root 71K Jul 1 00:58 systembackup.log.3.gz drwxr-x--- 2 root root 4.0K Sep 21 20:00 unattended-upgrades -rw-rw-r-- 1 root root 0 Oct 5 09:45 wtmp -rw-rw-r-- 1 root root 538 Aug 26 13:10 wtmp.1.gz
  18. hanguofu

    Armbian for Amlogic S9xxx kernel 4.1x (>= ver 5.55)

    I put the img. Armbian_5.59_Aml-s9xxx_Ubuntu_xenial_default_4.18.0_20180823.img into a usb disc. and boot it successfully with my TV box. I havenot flashed the emmc yet . Another word , I played with Armbian installed at the U-disc. However , when I tried to upload/download files to/from the box with tool "Xftp 5" ( from NetSarang ) , the tool failed to connected to the box. The box and my pc are in the same local network ( 192.168.0.xxx ) Of course , the ssh service is good and I can log into the box with tool "Xshell 5". Is the ftp service not avail. at the img. ?
  19. martinayotte

    Bcache-tools not building module on 4.18.6

    apt-get install bcache-tools
  20. It's open source, released under GPLv3 also the app!
  21. Is this Open Source Software or a binary ?
  22. Hey, we made a tool that allows us to configure the wireless connection of a headless systems using just a smartphone. The reason was that we often ended up in situations where we prepared a headless system with our full stack (see https://nymea.io) and handed it over to someone else to just it in their WLAN. The target group are end users which are not able to use a console. In an attempt to return something to the community we've created a standalone tool for this to share it with others, BerryLan. At the moment it requires to add the nymeas debian repository and install nymea-networkmanager. You can find all the details about it on https://berrylan.app. It was originally designed for the Raspberry Pi, but it works with any other debian based system too. The device must have a wireless adapter and a Bluetooth LE adapter. The daemon works with network-manager and bluez. The source code of the daemon can be found here: https://github.com/guh/nymea-networkmanager By default, this will open up a Bluetooth LE server on the device which allows to connect with the BerryLan app whenever there is no other network connection. As soon as the device is connected to a network (either LAN or WLAN), the Bluetooth server will shut down. This behavior can also be configured to e.g. only allow configuring a network once and then never open up again. We'd be happy for any feedback, please let us know about issues you find. Also we'd love to know if you find this tool useful and if it'd be worth going through the efforts of trying to get it included in the Debian archive. Enjoy, and please do let us know what you think about it! Cheers, Simon
  23. NicoD

    NanoPI M4

    That doesn't seem normal to me. I see no reason why there should be power on that output. I think @TonyMac32 knows more about these things. Is it normal the voltage is passed thru the i/o output of an hd enclosure? I can imagine that you could power the enclosure with that usb-c connector. So maybe the 5V there is open both ways? I'm just guessing. I think it doesn't start the sbc because there's nothing trying to read the hard drive. So it doesn't see it's connected. Once turned on, the sbc communicates with the hd, so it's turned on. And so the 5V is shared too. I can be completely wrong. The more knowledgeable people will know more.
  24. balbes150

    ARMBIAN for Amlogic S905 and S905X (ver 5.44 =<)

    Do and all say thank you. Desktop versions are optimized to work in this mode.
  25. Igor_K

    Recommended SBC below 20USD range.

    @tommy the best sbc for what? What is your use case?
  26. Learnincurve

    Pine A64 MIPI DSI mainline

    I see that Jagan's tree is based on 4.19 and is related to a64-relic but don't know how to incorporate it into the Armbian build process or even if I should try.
  27. Hi. I'm using Cubietruck, and installed Ubuntu server(mainline) on it. Suddenly, I can't write to disk(SD card). Actually, yes I can. I could create, edit, or even delete files, but all the changes are gone after the Cubietruck is rebooted. The deleted files are back, and created files are gone. What should I check? My SD card is Samsung Evo 16GB, and I'm running Cubietruck for more than 2 years. I have never encountered this weird situation. Thank, Cristiano
  1. Load more activity