vlad59

if performance works then you can try conservative it should be better for Electricity cost (if that works of course)

Yes .... but something configurable is often more complex to maintain so while motd is kind of important for a guy that installed Armbian for the first time, it's rarely useful for someone that only use SSH with a purpose in mind (I only give a quick look to system load to check for unusual load that's all). It depends on the goal.

I agree br should be excluded (at least for my usecase which involve docker). I remember talking about Zador when he changed it a year ago : https://github.com/armbian/build/commit/2d37a1ec3e5aee5ed6d942a6eb93fdbf20a08413#diff-02317355268e7ae7265db2efbf843d7b I don't know why @Igor changed it. But as it's only a motd I don't care a lot about it.

I have a Banana Pi (The very first one, before the Banana Pro / m1 came out) running Armbian 5.38 with kernel 4.14.18 and it runs 24/7. Its uptime is 56 days (and I rebooted the board) so no problem at all. I have another Banana Pi running Armbian 5.31 with kernel 4.11.6 and its uptime is 143 days. I never had a single problem with both of them.

I have two Banana Pis running 24/7, one of them is running a rather old Jessie (4.14 IIRC) and the other one latest Armbian Stretch, both didn't have any hangs or reboots (the first one has almost one year uptime)

Sorry for the delay here my lsusb output : Bus 004 Device 002: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode) Device Descriptor: bLength 18 bDescriptorType 1 bcdUSB 2.00 bDeviceClass 224 Wireless bDeviceSubClass 1 Radio Frequency bDeviceProtocol 1 Bluetooth bMaxPacketSize0 64 idVendor 0x0a12 Cambridge Silicon Radio, Ltd idProduct 0x0001 Bluetooth Dongle (HCI mode) bcdDevice 88.91 iManufacturer 0 iProduct 2 CSR8510 A10 iSerial 0 bNumConfigurations 1 Configuration Descriptor: bLength 9 bDescriptorType 2 wTotalLength 177 bNumInterfaces 2 bConfigurationValue 1 iConfiguration 0 bmAttributes 0xe0 Self Powered Remote Wakeup MaxPower 100mA Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 0 bAlternateSetting 0 bNumEndpoints 3 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x81 EP 1 IN bmAttributes 3 Transfer Type Interrupt Synch Type None Usage Type Data wMaxPacketSize 0x0010 1x 16 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x02 EP 2 OUT bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x82 EP 2 IN bmAttributes 2 Transfer Type Bulk Synch Type None Usage Type Data wMaxPacketSize 0x0040 1x 64 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 0 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0000 1x 0 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0000 1x 0 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 1 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0009 1x 9 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0009 1x 9 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 2 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0011 1x 17 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0011 1x 17 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 3 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0019 1x 25 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0019 1x 25 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 4 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0021 1x 33 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0021 1x 33 bytes bInterval 1 Interface Descriptor: bLength 9 bDescriptorType 4 bInterfaceNumber 1 bAlternateSetting 5 bNumEndpoints 2 bInterfaceClass 224 Wireless bInterfaceSubClass 1 Radio Frequency bInterfaceProtocol 1 Bluetooth iInterface 0 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x03 EP 3 OUT bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0031 1x 49 bytes bInterval 1 Endpoint Descriptor: bLength 7 bDescriptorType 5 bEndpointAddress 0x83 EP 3 IN bmAttributes 1 Transfer Type Isochronous Synch Type None Usage Type Data wMaxPacketSize 0x0031 1x 49 bytes bInterval 1 Device Status: 0x0001 Self Powered

For now I only limited access to the Banana pi with BT 4.0 USB. As soon as I get a proper SSH, I'll send you the lsusb output.

Please note that removing those two modules mean that the kernel won't know if the SOC temp is too high (check dmesg afterwards) About your bluetooth dongle problem, I would guess it's a power supply problem. My two Banana Pis are powered with a 2A Power supply through the micro usb, they both have a SSD connected and one of them also has a bluetooth BLE (cheapest one on ebay) adapter and I have no problem (+100 days uptime). The BLE Usb device is used every 20s to check for specific BLE tracker to check for home presence and there was no glitch for a few months.

Please check https://groups.google.com/forum/#!searchin/linux-sunxi/lucas|sort:date/linux-sunxi/bVEsjQRNVSo/nTa3rpOyAQAJ for a workaround.

The banana pi only has 1 SPI Unless I'm mistaken. I used SPI some time ago and IIRC simply adding spi-spidev to the overlay did the trick. The Banana pi has no Nand. Hope this helps

Upgraded and it's working fine, I'll get back to you if there are problem

thanks, I'll upgrade tomorrow morning (too late here

I tried to update my Banana Pi but the no new kernel is found, I use apt.uk.armbian.com is it normal ?

I also noticed that a year ago when I switched to mainline on my Banana, IIRC I talked to tkaiser about it and it was a normal side effect. I did not try to change anything about as my banana pi stay mostly idle and only use their CPU when doing compression and that does not happen very often. The max freq is defined in the device tree so you can change it on userland

Still on a banana pi, updating a Stretch 5.35 installation on SATA worked perfectly.

So I was beat but I can also confirm that a new install is working fine. I'm updating another banana pi that was previously running 5.36 and report back. About the kworker, the problem was diagnosed on linux-sunxi mailing list : https://groups.google.com/forum/#!searchin/linux-sunxi/kworker|sort:date/linux-sunxi/bVEsjQRNVSo/nTa3rpOyAQAJ If you really want to remove this load you can unload the two modules but I don't know if you'll still have thermal protection on your A20. I'm tempted to try it as it does not run too hot.

@Igor If nobody beat me to it, I'll test the banana pi build. I won't be able to test SATA installation (I broke my sata connector on my third banana pi and did not resolder a new one) but I'll check the rest.

I guess it was to the bad mount of the sdcard just after the release of 5.35 : I guess @Flavio just need to change his fstab reboot and the update should go fine.

I had no time to do more debugging with this, I read some commits but did not find anything new. You can try to ask linux-sunxi mailing list / or maybe their irc channel. I have not tried any H3 build with mainline , I'll check with Pine64 soon.

+1 never had a single problem with this sensor when used inside my house. On you other post I've also proposed another python library.

there are many breadboard compatible boards made with BME280 : Most of mine are more complex than yours : https://fr.aliexpress.com/item/GY-BME280-BME280-I2C-SPI-Num-rique-Capteur-Module-Breakout-Temp-rature-Humidit-Pression-Barom-trique/32840435761.html?spm=a2g0w.search0104.3.112.5bANYG&ws_ab_test=searchweb0_0%2Csearchweb201602_5_10152_10065_10151_10344_10068_10345_10342_10343_51102_10340_10341_10609_10541_5130013_5000013_10084_10083_10305_10304_10307_10306_5080013_10302_10610_5870020_10312_10059_10313_10314_10184_10534_100031_10604_10603_10103_10605_5060013_10594_10142_10107%2Csearchweb201603_25%2CppcSwitch_2&algo_expid=4383f9c8-b5ae-48a5-8fd1-e32deb3d9fb9-16&algo_pvid=4383f9c8-b5ae-48a5-8fd1-e32deb3d9fb9&rmStoreLevelAB=5 either way, the first after connecting is checking if the BME280 is detected on the bus : root@minus:~# i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- 23 -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 70: -- -- -- -- -- -- 76 -- See the 76 here, that means BME280 is detected. Here I checked i2c-1 (you may have to change that depending of how many i2c bus your board have. I don't like most Adafruit libraries (find them hard to read), for BME280 I use this library : https://bitbucket.org/MattHawkinsUK/rpispy-misc/raw/master/python/bme280.py

I guess the question is : Is apt.armbian.com available with ipv6 only ? For now dig says no.

I also have the problem. I tried some quick debugging and watched some kernel logs about network / a20 but found nothing so far.

I completely agree with you. When I first started home automation, I was using an all-in-one solution but as it grew on the only thing that's became really important for me is that everything goes by a MQTT server (every sensor, every action, every result of automation). In the end I use Home Assistant for some stuff, hand made python script for thermostat / smart valve automation, ESP8266 for most of my home sensor, Arduino with HF, some Xiaomi Aqara sensors, ... The only common point is that everything goes into a MQTT server. Anyway thanks for the information I'll read the project documentation (marketting is always frustating)

I'm not sure , I debugged a little and I got this (worker 4425 is the one using 10% CPU) : kworker/0:1-4425 [000] dns. 15926.716039: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d.s. 15927.836116: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d.s. 15928.956207: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d.s. 15930.076285: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d.s. 15931.196364: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d.s. 15931.256369: workqueue_queue_work: work struct=c0d1bc84 function=vmstat_shepherd workqueue=ef004500 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d.s. 15932.316456: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d.s. 15933.436530: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d.s. 15934.556614: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d.H. 15935.666723: workqueue_queue_work: work struct=ee4abe38 function=dbs_work_handler workqueue=ef004500 req_cpu=0 cpu=0 kworker/0:1-4425 [000] d.s. 15935.676705: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d.s. 15936.796780: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d.s. 15937.916862: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d... 15938.257014: workqueue_queue_work: work struct=ef6bcd24 function=vmstat_update workqueue=ef0cfd00 req_cpu=0 cpu=0 kworker/0:1-4425 [000] d.s. 15939.036960: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d.s. 15940.157029: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d.s. 15940.217039: workqueue_queue_work: work struct=c0d1bc84 function=vmstat_shepherd workqueue=ef004500 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d... 15940.237242: workqueue_queue_work: work struct=ef6cdd24 function=vmstat_update workqueue=ef0cfd00 req_cpu=1 cpu=1 kworker/0:1-4425 [000] d.s. 15941.277113: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d... 15941.357319: workqueue_queue_work: work struct=ef6bcd24 function=vmstat_update workqueue=ef0cfd00 req_cpu=0 cpu=0 kworker/0:1-4425 [000] d.s. 15942.397206: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 kworker/0:1-4425 [000] dns. 15943.517309: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d... 15944.247437: workqueue_queue_work: work struct=ef6cdd24 function=vmstat_update workqueue=ef0cfd00 req_cpu=1 cpu=1 kworker/0:1-4425 [000] d.s. 15944.637363: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d... 15945.367559: workqueue_queue_work: work struct=ef6cdd24 function=vmstat_update workqueue=ef0cfd00 req_cpu=1 cpu=1 kworker/0:1-4425 [000] d.H. 15945.747474: workqueue_queue_work: work struct=ee4abe38 function=dbs_work_handler workqueue=ef004500 req_cpu=0 cpu=0 kworker/0:1-4425 [000] d.s. 15945.757456: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d... 15946.227594: workqueue_queue_work: work struct=ef6bcd24 function=vmstat_update workqueue=ef0cfd00 req_cpu=0 cpu=0 kworker/0:1-4425 [000] d.s. 15946.877526: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 kworker/0:1-4425 [000] d... 15947.257684: workqueue_queue_work: work struct=ef6cdd24 function=vmstat_update workqueue=ef0cfd00 req_cpu=1 cpu=1 kworker/0:1-4425 [000] d.s. 15947.997610: workqueue_queue_work: work struct=bfa71244 function=gc_worker [nf_conntrack] workqueue=ef004900 req_cpu=4 cpu=0 Can it be network related (conntrack) ?