rufik

Members
  • Content Count

    95
  • Joined

  • Last visited

 Content Type 

Forums

Member Map

Store

Crowdfunding

Raffles

Applications

Everything posted by rufik

  1. This directive is deprecated now. But I've set realtime=no and this error has gone.
  2. So it seems we (users) can buy this SBC now, thanks a lot [emoji12]
  3. Is anyone using watchdog on OrangePi H3 family? I've tried to set it up on OPI 2 (almost the same as OPI PC but with wifi) and I'm getting some trouble with watchdog service startup: cannot set scheduler (errno = 1 = 'Operation not permitted') May 10 09:29:23 opi2 systemd[1]: Starting watchdog daemon... May 10 09:29:23 opi2 watchdog[12308]: String 'watchdog-device' found as '/dev/watchdog' May 10 09:29:23 opi2 watchdog[12308]: String 'admin' found as 'root' May 10 09:29:23 opi2 watchdog[12310]: starting daemon (5.15): May 10 09:29:23 opi2 watchdog[12310]: int=7s realtime=yes sync=no load=0,0,0 soft=no [cut!] May 10 09:29:23 opi2 watchdog[12310]: watchdog now set to 16 seconds May 10 09:29:23 opi2 watchdog[12310]: hardware watchdog identity: sunxi-wdt May 10 09:29:23 opi2 watchdog[12310]: cannot set scheduler (errno = 1 = 'Operation not permitted') May 10 09:29:23 opi2 systemd[1]: Started watchdog daemon. I'm using latest armbian: Welcome to ARMBIAN 5.85 stable Ubuntu 18.04.2 LTS 4.19.38-sunxi It looks like problem with realtime schduling: https://www.freedesktop.org/wiki/Software/systemd/MyServiceCantGetRealtime and I've tried to add Delegate=cpu option to watchdog.service file but still no-go. Anyone was facing this issue?
  4. I own Chuwi Hi12 tablet based on Atom X5-Z8300 which was a bad guy due to keyboard/overall handling. I've successfully got rid of windows & android from eMMC and installed Ubuntu Server x64 So I decided get rid of some components as touchscreen, speakers, cameras, battery and use it as SBC headless server. Sadly ribbon cables were glued and I damaged one or two of them, so this is one-way trip now I think. But I can't power it on now :/ There is no reaction to power button at all. Does anyone have some experience with such boards? What components are required to be connected in order to boot it up? teardown pics 1 teardown pics 2
  5. Maybe nowayout param should be set to 1? I remember that nowayout=0 on H3 just disables watchdog hardware reset as described here: https://www.kernel.org/doc/Documentation/watchdog/watchdog-api.txt There is some discussion on forum here with H3 CPU, worth to be read.
  6. Anything below 480 MHz just trashes storage performance and almost saves no power. So leave minimal freq as is.
  7. Maybe blacklist touchscreen driver?
  8. https://www.kernel.org/doc/Documentation/watchdog/watchdog-api.txt When the device is closed, the watchdog is disabled, unless the "Magic Close" feature is supported (see below). This is not always such a good idea, since if there is a bug in the watchdog daemon and it crashes the system will not reboot. Because of this, some of the drivers support the configuration option "Disable watchdog shutdown on close", CONFIG_WATCHDOG_NOWAYOUT. If it is set to Y when compiling the kernel, there is no way of disabling the watchdog once it has been started. So, if the watchdog daemon crashes, the system will reboot after the timeout has passed. Watchdog devices also usually support the nowayout module parameter so that this option can be controlled at runtime. So it's required to set it up. Try some quoting. Maybe this should be the last line in armbianenv.txt file? I can't remember exactly but there was some issue about it...
  9. To make watchdog performing hard reset you need to add this param to /boot/armbianEnv.txt : extraarg=sunxi_wdt.nowayout=1 But I can't really recall if some quotation should be used (like extraarg="sunxi_wdt.nowayout=1") or not. Just try it yourself. This argument is required if you want your watchdog to perform hard reset SBC. And of course just install watchdog package using apt-get.
  10. You can easily fork my repo and customize srcipt to your needs I'm going to develop ready-made config files yet (like hass alredy configured with mariadb, mqtt, influx; to be deployed by script) and that's all.
  11. I've put some effort to make installation script for Home Assistant using docker: https://github.com/rufik/armbian-hass Script is self-explanatory, just installs some useful stuff, docker, images (portainer, hass, mqtt, mariadb, etc), prepares containers, etc. It's not finished yet, I'm still working on it, it has some problems (mosquito does not start properly yet), but I'm quite time limited right now. The idea is just to automate all these manuals steps required to bring up whole hass ecosystem...
  12. All you need is just to install watchdog service and set some parameter in armbianenv.txt file - I can't recall it right now, I'll try to search my notes later and post the solution.
  13. And check storage performance with all those settings now. You can run it using armbianmonitor with some switch (can't remember which one). My statement is based on some tkaiser's forum writing, and he's rather proven to not spread bs (he just did such tests AFAIK).
  14. Note that anything lower than 480 MHz will trash your storage performance probably. And power saving is also minimal. Consider using 480 as min freq.
  15. Anybody know a way to reset board (OPI PC) immediatly not going through shutdown process? I'm already logged in (ssh session). I've overwritten SD card by mistake, whole fs has gone, and I cant perform reboot or shutdown command (not found) :/
  16. Check your cpufreq config for bad entry 408 mhz instead of 480 mhz.
  17. Because everything lower than 480 trashes SD card performance, as@tkaiser wrote a few times.
  18. I'm just getting error starting watchdog service on OPI2 Ubuntu Bionic 4.14.70 like Cannot open /dev/watchdog (errno = 16 = 'Device or resource busy'). rufik@farmer:~$ sudo systemctl status watchdog ● watchdog.service - watchdog daemon Loaded: loaded (/lib/systemd/system/watchdog.service; enabled; vendor preset: enabled) Active: active (running) since Thu 2018-10-11 10:52:08 CEST; 15s ago Process: 17410 ExecStopPost=/bin/sh -c [ $run_wd_keepalive != 1 ] || false (code=exited, status=1/FAILURE) Process: 17436 ExecStart=/bin/sh -c [ $run_watchdog != 1 ] || exec /usr/sbin/watchdog $watchdog_options (code=exited, status=0/SUCCESS) Process: 17433 ExecStartPre=/bin/sh -c [ -z "${watchdog_module}" ] || [ "${watchdog_module}" = "none" ] || /sbin/modprobe $watchdog_module (code=exited, status= Main PID: 17438 (watchdog) CGroup: /system.slice/watchdog.service └─17438 /usr/sbin/watchdog Oct 11 10:52:08 farmer watchdog[17438]: starting daemon (5.14): Oct 11 10:52:08 farmer watchdog[17438]: int=3s realtime=yes sync=no soft=no mla=0 mem=0 Oct 11 10:52:08 farmer watchdog[17438]: ping: no machine to check Oct 11 10:52:08 farmer watchdog[17438]: file: no file to check Oct 11 10:52:08 farmer watchdog[17438]: pidfile: no server process to check Oct 11 10:52:08 farmer watchdog[17438]: interface: no interface to check Oct 11 10:52:08 farmer watchdog[17438]: temperature: no sensors to check Oct 11 10:52:08 farmer watchdog[17438]: test=none(0) repair=none(0) alive=/dev/watchdog heartbeat=none to=root no_act=no force=no Oct 11 10:52:08 farmer watchdog[17438]: cannot open /dev/watchdog (errno = 16 = 'Device or resource busy') Oct 11 10:52:08 farmer systemd[1]: Started watchdog daemon. But /dev/watchdog seems not to be opened: rufik@farmer:~$ sudo fuser -v /dev/watchdog rufik@farmer:~$ sudo lsof /dev/watchdog I have disabled wd_keepalive deamon - is it really required to run? Or just excludes with watchdog daemon?
  19. What commit interval do you advise for kernel 4.14.y using btrfs? Default (5 sec) or just armbian's default 600 sec? I've just migrated to Transcend TS32GMTS400S SSD + USB UASP adapter (ASM1351) via nand-sata-install option...
  20. Since I got rid of network manager (configured in old good way) my SBC connection is rock solid. Network Manager is not reliable somehow...
  21. I've already checked - firewall is disabled all the time, because OPI PC is inside my LAN. Nmap show open ports 22, 8123 (HomeAssistant), 3306 (MySQL) and so on. But every service accepts TCP connection and does not respond at all, terminating connection after some timeout. Sshd accepts connection, asks for password and hangs...until timeout. Ping works So it looks like some OS internal problem, maybe with memory and spawning processes/threads? That's why I'd like to try out watchdog.
  22. My OPI PC (mainline kernel) just freezes from time to time, it respond to ping but I cannot ssh into it (waiting forever for session then disconnects), services does not respond also. It looks like some OOM or similar problems, I cannot check it via serial console because it's remote location. So I thought that watchdog would be nice there, just to reset board in such cases.
  23. How is your watchdog doing? Does it work reliable over the time?
  24. I've just played with compilation a little bit and 4.18.y is selected when BRANCH="dev" is set. But script does not take KERNELTAG or KERNELBRANCH variables into account when set up in config-default.conf. Let's play with 4.18.7 kernel a little bit...:)
  25. I saw bionic image for download, so I thought I would build my customized image for OPI PC based on Ubuntu Bionic and 4.18.y kernel, so I have some questions: 1. Is Bionic fully stable/supported for OPI PC? 2. Is kernel 4.18.y supported? Is it sufficient to set KERNELTAG="v4.18.7" to build it? Or I just has to stick with 4.17.y?