vlad59

Members
  • Content count

    78
  • Joined

  • Last visited

About vlad59

  • Rank
    Advanced Member

Recent Profile Visitors

277 profile views
  1. 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)
  2. 5.35/5.36 bug / questions collection

    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) ?
  3. 5.35/5.36 bug / questions collection

    Changing fstab to this may solve the problem : root@minus:~# cat /etc/fstab # <file system> <mount point> <type> <options> <dump> <pass> tmpfs /tmp tmpfs defaults,nosuid 0 0 /var/swap none swap sw 0 0 UUID=f33f7df6-250e-499d-80fc-a8fd4441081e /media/mmcboot ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 /media/mmcboot/boot /boot none bind 0 0 UUID=4240532a-38e9-4e3f-8a3d-3d3e814a38de / ext4 defaults,noatime,nodiratime,commit=600,errors=remount-ro 0 1 notice the /media/mmcboot/boot
  4. 5.35/5.36 bug / questions collection

    Yes, especially as armbianEnv.txt is expected to be found in /boot/armbianEnv.txt not /boot/boot/armbianEnv.txt https://github.com/armbian/build/blob/master/packages/bsp/common/usr/sbin/armbian-add-overlay#L31 Reading @tkaiser answer, I can umount /boot but it still feel strange as if I want to use DT Overlays, they still have to be read from SD card (loaded from uboot directly) so the /boot from my SATA drive won't be used.
  5. 5.35/5.36 bug / questions collection

    Me again, Please tell me if you prefer that I open a topic for each issue. I found another strange thing : I used armbian-config to use my SSD and after the full copy and the reboot it seems that my SD card still contain a full armbian filesystem : root@minus:~/src/dtc# mount | grep "/boot" /dev/mmcblk0p1 on /boot type ext4 (rw,noatime,nodiratime,errors=remount-ro,commit=600) root@minus:~/src/dtc# ls /boot/ bin boot dev etc home lib lost+found media mnt opt proc root run sbin selinux srv sys tmp usr var on my other devices /boot only contain the real /boot file. It also causes problem with armbian-add-overlay for example because /boot/armbianEnv.txt is not found (it's under /boot/boot/armbianEnv.txt).
  6. 5.35/5.36 bug / questions collection

    I just installed again from scratch one of my banana pi with Armbian_5.35_Bananapi_Debian_stretch_next_4.13.16.img, I've done an apt update && upgrade (initrd was updated) a few minutes ago, rebooted and I also see kworker using ~8% CPU. Is there something more to do with a Banana Pi ? I'm copying to SATA for now but I'll be happy to test after it's finished. SATA copy is finished : http://sprunge.us/dbSd
  7. fix for 24/32bit H3 audio capture

    Great ! Please try to propose it to linux-sunxi or did you take it from there ?
  8. Patch for busy hang in aufs (docker)

    Sorry I have missed you were using a pinebook. I'm use mainline on a Pine64 and it's working fine but I'm not using any desktop / gui About aufs vs Overlay2 : when I was still using my SDCard as storage for my docker containers (one year ago), I had a lot of performance problem with aufs -> using overlay2 solved most of it. Back I was reading this site and it convinced me https://github.com/chriskuehl/docker-storage-benchmark But I'm not selling anything, if it works good enought don't touch it
  9. Patch for busy hang in aufs (docker)

    You're using mainline kernel or legacy ? If you're using mainline Overlay2 is a better choice, isn't it ? I'm using it for months (more than a year even) without any problem with A20 board.
  10. Bananapi pro bricked

    The banana pi has absolutely no protection between the PMIC and the USB port -> if you plug a peripheral that use more current that the PMIC can provide you get magic smoke I don't know if the pro is the same
  11. Another make of H3 board

    Nanopi M1 is made by FriendlyArm / FriendlyElec (see here http://www.friendlyarm.com/index.php?route=product/product&path=69&product_id=109 ) It's quite old (I got two a year ago). They're quite good but as the PCB is small they tend to overheat. They're already supported by Armbian, see https://www.armbian.com/nanopi-m1
  12. As you stated most of the time, this problem come from Bad power supply / Bad SD card. It's hard to have a better guess :(.
  13. i2s in mainline?

    IIRC I2S is not available for Banana PI (not wired to GPIO), I think it's available for lime2
  14. What does your workbench look like?

    This will proove I'm older than you .... but I still use my HP48sx from when I was in the University (as a side note I still works perfectly fine after more than 20 years) ..... I'll post a photo of my workbench soon
  15. Maybe try to change the mount option : sudo mount.cifs //192.168.0.200/y /media/200_y -o user=armuser,iocharset=utf8