• Content Count

  • Joined

  • Last visited

About gas_85

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Hey I try 2 images - stable and nightly (LibreELEC-A20.arm-9.80-devel-20191230203035-9d103bd-cubietruck.img.gz and LibreELEC-A20.arm-9.80-nightly-20200201-a869d6c-cubietruck.img.gz), but after SD card resizing it is coming nothing on the display, seems I have the same error as you described on other forum. Currently I have no cable to connect to the SSH and try to solve it. Sad, but it does not really work out of the box with Cubietruck.
  2. As I see has also nothing related to USB host. Or?
  3. Hello, Just find out that my USB ports are not working. Quick dig shows that the are disabled: # lsusb # dmesg |grep usb [ 0.000000] Kernel command line: root=UUID=e8491c09-2260-4706-a9a4-1f9f96af1232 rootwait rootfstype=ext4 console=ttyS0,115200 console=tty1 disp.screen0_output_mode=1920x1080p60 panic=10 consoleblank=0 loglevel=1 ubootpart=5b507211-01 ubootsource=mmc usb-storage.quirks=0x2537:0x1066:u,0x2537:0x1068:u sunxi_ve_mem_reserve=0 sunxi_g2d_mem_reserve=0 sunxi_fb_mem_reserve=16 cgroup_enable=memory swapaccount=1 [ 1.308752] usbcore: registered new i
  4. I did as you told: install Armbian on a new SD, bootup, create user and set passwords. After I adjust /boot/armbianEnv.txt to set UUID to my drive and then rebooted successfully. One point, because older SD was going into RO mode, I have badly installed package: initramfs-tools, and future apt upgrade were finished with an error. So I have to reinstall it by command: sudo apt install --reinstall initramfs-tools:armhf After this everything works good, thanks! UPDATE: I was a bit wrong, Kernel has some problems, this is an error when I try to run iptables: $ sudo
  5. Thanks! I will try do this. Last year I did the same as you told and it did not work for me... Lets see now. Is there is a way to automate this prcess? E.g. added User (copy /etc/passwd and /etc/shadows)?
  6. Hello, I have trouble with my SD Card - it goes in Read Only mode. What I have: I have Running System from the HDD (installed by nand-sata-install command) My Cubietruck is online for now, but I'm afraid do switch it off. I try to run dd command to make a backup of RO SD card and reuse image on a new SD card, but it does not succeed: # dd if=/dev/mmcblk0 bs=10M | gzip -c > /media/dataPartition/sdcard.img.gz dd: error reading '/dev/mmcblk0': Input/output error 0+0 records in 0+0 records out 0 bytes copied, 0.00503184 s, 0.0 kB/s I read the forum regarding bac
  7. And after update to latest Armbian I noticed that it is not there. Update was done from Ubuntu 16.04... And before I can get AC Power supply status via: cat /sys/class/power_supply/ac/present Now I could not find anything AC Power supply related... Where is all this gone? ls -la /sys/class/power_supply total 0 drwxr-xr-x 2 root root 0 Aug 20 10:26 . drwxr-xr-x 61 root root 0 Aug 20 10:26 .. lrwxrwxrwx 1 root root 0 Aug 20 10:26 axp20x-battery -> ../../devices/platform/soc@1c00000/1c2ac00.i2c/i2c-1/1-0034/axp20x-battery-power-supply/power_supply/axp20x-battery lrwxrwxrwx 1 root
  8. How to disable it correctly: Only config edit will not give you correct effect.
  9. I read zram and log2ram config and source and recognized that zram will evaluate config of log2ram, so if I disable it in config - everything works. Only issue - truncate operation is still in cron and script does not look into config by executing... This bring must be disabled in cron. Yes, I forgot to say about this... daily script was commented # cat /etc/cron.daily/armbian-ram-logging #!/bin/sh #/usr/lib/armbian/armbian-ramlog write >/dev/null 2>&1 Thanks a lot!
  10. Long story short, to disable arbain-ramlog: 1. Change in /etc/default/armbian-ramlog ENABLED=false 2. Disable in cron root user truncate-logs by editing /etc/cron.d/armbian-truncate-logs (just comment the line) like this: # 0,15,30,45 * * * * root /usr/lib/armbian/armbian-truncate-logs 3. Delete /etc/cron.daily/armbian-ram-logging or comment it like: #!/bin/sh #/usr/lib/armbian/armbian-ramlog write >/dev/null 2>&1 4. Restart Server. Because armbian-zram is connected to ramlog service and will read config of it. It will not create compressed in-memory folder
  11. Also try to solve this problem. I create a script that will try to send Warning Email and and shutdown the system as soon as it goes below 10%. I put it in cron hourly and script should automatically check and do loop if battery discharging and below e.g. 80%. E-Mail is needed because last time I did not know that my power supply died and I did not know why sever stopped. This version is also producing logs that could be checked after cubietruck fails. That helps for trouble shooting, e.g. to find out that power supply could not produce enough current to charge battery. Log outp
  12. 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.
  13. Try to wait:D I have the same "issue" shutdown or reboot takes time (around 2 minutes) before it goes down, I did not check, but seems some trim operation with SD card, or something. In time between shutdown/reboot command when LED blinks cubietruck is not reachable via network.
  14. I find out what was wrong. It was my mistake with mysql and iptables. Basically I setup wrong settings for iptables and localhost (like from to, but this will cause situation when MySQL port 3306 will not accept some of inbound connections from e.g. 10.0.x.x that is also "local". This will cause issue when CPU load is extremely high, but you could not recognize app/service that cause it, only "TIME+" can give a hint on root mysql process. It is hardly to catch, because issue will not accrue till reboot, and you do not need to reboot the system for iptables. This