Rodrigo Matias

Hi Peter, Did you find an increase in SD card reliability after moving to BTRFS in your (/) root partition instead of EXT4 default that comes with ARMBIAN? Currently I'm having equipments with filsystem corruption in LIME2 boards average 2-3 months using KINGSTON microSD cards. The cards are not damaged. I write a new image and everything gets back on track working fine. I recently moved to INDUSTRIAL grade versions of the KINSTON microSD cards and deasctivated almost every filesystem writes like logs, etc....one of the tricks was to move some folders to temporary RAM drives. Waiting for time to pass and see if it improves reliability. Now I'm thinking in creating a new SD image exactly like you did to test if it improves. Regards, Rodrigo Matias

Hi everyone, Is this problem already solved? I keep trying to use hwaddress xx:xx:xx:yy:yy:yy or hwaddress ether xx:xx:xx:yy:yy:yy option on /etc/network/interfaces configuration file with no success. I also tried the pre-up ifconfig hw ether xx:xx:xx:yy:yy:yy, but with no success either. I keep having to manually put interface down with ifdown, then reconfigure its HW address and after that, restart NetworkManager and then renew the DHCP process. The main problem is that sometimes this process is not 100% realiable and home router gets 2 DHCP negotiations, one for the RANDOM MAC address and the other for the manually configured MAC address. Any clues? Thanks. Rodrigo Matias

Hi, I exceuted your commands. Result was: :~# ls -la /etc/armbianmonitor/datasources/soctemp lrwxrwxrwx 1 root root 47 Sep 22 2017 /etc/armbianmonitor/datasources/soctemp -> /sys/devices/virtual/thermal/thermal_zone0/temp :~# cat /etc/armbianmonitor/datasources/soctemp cat: /etc/armbianmonitor/datasources/soctemp: Connection timed out :~# armbianmonitor -u System diagnosis information will now be uploaded to /usr/bin/armbianmonitor: line 351: read: read error: 0: Connection timed out /usr/bin/armbianmonitor: line 352: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 351: read: read error: 0: Connection timed out /usr/bin/armbianmonitor: line 352: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 351: read: read error: 0: Connection timed out /usr/bin/armbianmonitor: line 352: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 351: read: read error: 0: Connection timed out /usr/bin/armbianmonitor: line 352: [: 57.6: integer expression expected /usr/bin/armbianmonitor: line 351: read: read error: 0: Connection timed out /usr/bin/armbianmonitor: line 352: [: -ge: unary operator expected /usr/bin/armbianmonitor: line 1: echo: write error: Broken pipe Thanks, Rodrigo Matias

Hi, I have some armbian 5.38 (kernel 4.11.5) installations and recently updated them. With this update I got kernel 4.14.18. When I executed command "armbianmonitor -m" I used to get something like this: :~# armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU PMIC 10:52:13: 528MHz 0.35 21% 2% 18% 0% 0% 0% 40.8°C 41.0°C 10:52:18: 528MHz 0.52 21% 2% 18% 0% 0% 0% 40.7°C 41.0°C 10:52:24: 528MHz 0.47 21% 2% 18% 0% 0% 0% 40.7°C 41.0°C Now after update, and kernel 4.14.18 among other new packets, I got this: :~# armbianmonitor -m Stop monitoring using [ctrl]-[c] Time CPU load %cpu %sys %usr %nice %io %irq CPU PMIC DC-IN C.St. 08:53:25: 720MHz 0.88 46% 12% 33% 0% 0% 0% 57.5°C 59.3°C 4.76V 0/6 08:53:31: 720MHz 1.19 21% 6% 14% 0% 0% 0%/usr/bin/armbianmonitor: line 351: read: read error: 0: Connection timed out /usr/bin/armbianmonitor: line 352: [: 57.5: integer expression expected 57.5°C 59.0°C 4.76V 0/6 08:53:39: 720MHz 1.09 21% 6% 14% 0% 0% 0%/usr/bin/armbianmonitor: line 351: read: read error: 0: Connection timed out /usr/bin/armbianmonitor: line 352: [: 57.5: integer expression expected 57.5°C 59.3°C 4.77V 0/6 08:53:45: 720MHz 1.30 21% 6% 14% 0% 0% 0%^C/usr/bin/armbianmonitor: line 351: read: read error: 0: Connection timed out Are there any broken links among the files that this command looks for or other bugs? I also realised that now CPU frequency is higher and cpu temperature. Nothing as changed and behaviour is completely different. Any help is appreciated! Thanks. Regards, Rodrigo Matias