rusefi

Sorry no debug logs yet but just FYI - running "sudo apt-get update" seems to have changed the behavior of this subsystem in a very positive way. the file has appeared, the image was compiled etc while same was not happening on a brand new installation prior to "sudo apt-get update" to be even more specific it was "sudo apt-get install openjdk-11-jdk-headless" which has triggered image to be compiled, all the update/install magic has kicked it while installing java of all things please do not get mad at me for no logs this time

Is there a good URL elaborating on what kind of logs make a good defect report/question? While i am aware of the concept in my field, I am not qualified enough in linux to know which logs are helpful and which are not.

I have a brand new install of Armbian 20.05.4 trying sudo armbian-config to enable overlayroot and getting sed: can't read /etc/overlayroot.conf: No such file or directory is that a feature of a bug? would touch /etc/overlayroot.conf be a proper work around or is something more expected of me to enable overlayroot?

Tide, you are mistaken in your assumption that I had broken SD cards in my RPI. I have not yet rebooted it 1000 times since I guess it's about startup logs tourtering the card. I also believe that this is pretty standard RPI with very mild changes. can you please explain your arguments a bit better? I have a feeling that I can learn a lot from you. what would be a better comparison methodology? I guess I should wire up grio LED to both boards and see at which point user startup script would turn them on.

I need wifi to work I just do not need wifi to be ready to boot. Thank you Heisath that "systemctl disable NetworkManager-wait-online.service" has made things better! But RPI is still starting a bit faster. If needed I can setup both systems with exactly same SD cards, those play a role but probably but software configuration does matter as well I assume. orange@orangepizero:~$ systemd-analyze Startup finished in 6.549s (kernel) + 16.664s (userspace) = 23.214s pi@raspberrypi:~ $ systemd-analyze Startup finished in 1.642s (kernel) + 7.302s (userspace) = 8.944s orange@orangepizero:~$ systemd-analyze Startup finished in 6.549s (kernel) + 16.664s (userspace) = 23.214s graphical.target reached after 16.444s in userspace orange@orangepizero:~$ systemd-analyze blame 4.758s armbian-zram-config.service 4.697s armbian-ramlog.service 2.786s dev-mmcblk0p1.device 2.589s networkd-dispatcher.service 1.447s networking.service 1.280s NetworkManager.service 1.141s loadcpufreq.service 1.070s systemd-udev-trigger.service 1.027s keyboard-setup.service pi@raspberrypi:~ $ systemd-analyze blame 4.637s apt-daily.service 3.335s apt-daily-upgrade.service 1.833s dev-mmcblk0p2.device 1.700s udisks2.service 1.684s raspi-config.service 826ms systemd-fsck@dev-disk-by\x2dpartuuid-738a4d67\x2d01.service 709ms keyboard-setup.service 648ms ssh.service 622ms systemd-timesyncd.service 578ms user@1000.service 563ms lightdm.service 520ms wpa_supplicant.service 505ms plymouth-read-write.service 485ms plymouth-quit-wait.service 482ms networking.service

Any specific test I can run to help?

OrangePiZero, Armbian_20.05.1_Orangepizero_buster_current_5.4.43 in RPI they have an option "Boot without waiting for network connection" which to be honest I do not know does what under the hood. What can I use with armbian to get faster boot time? I do not use Ethernet at all, I use wifi but do not want to wait for it to start using my device. Here is my boot statistics: root@orangepizero:~# systemd-analyze Startup finished in 7.295s (kernel) + 29.971s (userspace) = 37.266s graphical.target reached after 29.810s in userspace root@orangepizero:~# systemd-analyze blame 8.967s networkd-dispatcher.service 7.813s loadcpufreq.service 7.677s NetworkManager.service 7.379s wpa_supplicant.service 7.360s NetworkManager-wait-online.service 7.265s rng-tools.service 7.236s systemd-logind.service 7.174s sysstat.service 7.154s rsyslog.service

Happy 2020! The world is so different from 2019 I have just installed Armbian_20.05.1_Orangepizero_buster_current_5.4.43.img.xz.torrent on my OPi Zero and WiFi just works right away. What kind of "wireless connection issues are expected"? is the warning like the one on https://www.armbian.com/orange-pi-zero/ outdated now?

I guess my application is IOT - I am getting data via USB and SPI, report status via GPIO LEDs and upload data to the internet. I am enjoying raspberrypi 3B but it's huge and relatively expensive. I am trying to return Orange Pi 2G IOT since it's a disaster. Looks like Orange Pi Zero for a bit under $20 would not be a disaster? Are there other boards to consider if I care about physical size and price?