Jump to content

rufik

Members
  • Posts

    106
  • Joined

  • Last visited

Everything posted by rufik

  1. 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) :/
  2. Check your cpufreq config for bad entry 408 mhz instead of 480 mhz.
  3. Because everything lower than 480 trashes SD card performance, as@tkaiser wrote a few times.
  4. 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?
  5. 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...
  6. Since I got rid of network manager (configured in old good way) my SBC connection is rock solid. Network Manager is not reliable somehow...
  7. 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.
  8. 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.
  9. How is your watchdog doing? Does it work reliable over the time?
  10. 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...:)
  11. 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?
  12. So SSD with SMART + JMS578 adapter is going to be the best choice. I could use it with OPI PC right now and easily migrate to USB 3.0 when needed. What about splitting rootfs into read-only SD card and all data & logs into SSD? It should give me long life of SD card and fast storage capabilites...does it make sense? Is anyone already using such setup or?
  13. Anyone made random IO benchmarks comparing USB 2.0 and 3.0 adapter? Maybe these 100-200 SQL queries per minute does not require supa-speed? I don't think I need native M.2 slot that costs me $110. I'd like to stick with $50 tag price...
  14. I'd like to migrate from SD card Samsung Evo+ to something more durable (I'm running home assistant automation on OPI PC now, mariadb, influx, etc, many writes per minute). I think that I have only two options: go with SBC with EMMC or just buy cheap 32/64 GB SSD with USB adapter. What do you think, which option gives me better durability? Can I assume that EMMC is really durable comparing to SD card? Is USB 2.0 adapter as fast as EMMC?
  15. I just realized that best option would be big cheap old smartphone with small full qwerty keyboard (BT or USB) - all together fitted into 3D printed case. Something like BB Key/Passport [emoji16] but under $100 possible.
  16. I didn't test directly your value (1.20), I set it to 2.0 because of my customization I'm preparing - it works fine. I suppose it should be OK.
  17. I was thinking about buying small handheld with keyboard that could be used for small linux terminal, for some quick administrative & diagnostic work (login here, login there, put some commands, see webpage for help, etc). Something inexpensive with small qwerty keyboard. Something like PocketCHIP or this DYI on RPI http://www.3ders.org/articles/20170409-zero-terminal-raspberry-pi-device-is-a-diy-handheld-linux-pc-in-a-3d-printed-case.html Has anyone found or did such a thing? I wonder if I could use OPI/NanoPi/similar with 5-7 inch LCD (3:2 screen would be best IMHO), keyboard and LiPo battery from mobile, put it into 3-D printed case and run Armbian Desktop
  18. Yup, midnight commander via apt-get Thanks, I just found this place to be adjusted.
  19. I've just tried to build my custom image for OPI 2 but got into some trouble with space: I'm not really short of root fs space. It looks like /dev/loop12p1 lacks of free space. Why? Should I adjust this loop device size somehow? I'm building on Ubuntu 18.04.
  20. I have OPI 2 running latest armbian mainline with MQTT broker and home assistant only. And I've started to experience hard freezes that only power re-plug helps :/ At first I thought that only networking was gone, but I've triggered hearbeat on red onboard led and this led is just stopping blinking on freezes. I've even got rid of Network Manager and setup iface in old good way via /etc/networking/interfaces. Then I've connected to serial console, run minicom in screen with logging to file. Just to see if serial console would show some kernel panic or so...but nothing, no output on serial console. Anyone experienced such behaviour? How to debug it? My second sbc - OPI PC - just started doing the same...irregular freezes. Output from armianmonitor: http://ix.io/1hIf
  21. Anyone experienced problem with logging in via Tapatalk? Neither "tapatalk linked account" nor standard login+pwd option works for me, see error on screenshot. I'm using Tapatalk app v7.4.2 right now. Maybe tapatalk forum plugin needs to be upgraded?
  22. Thanks a lot. Just did it and network manager have took control. Now I can just perform nmcli d disconnect/connect easily By the way, I wonder why I'm getting disconnected...it didn't happened for weeks until I've install mosquitto and home assistant...
  23. I've experienced some issue on my OPI PC running 4.14 kernel - it disconnects eth after some hours of running. It's very annoying for me because I'm running Home Assistant automations on it and it's located in remote location (not in my home), so I have to drive 50 km to reset/reconnect it manually First I thought OPI just froze somehow (kernel panic or so). But later I've set up heartbeat trigger on red led and it's blinking, so OPI just disconnects from eth. When I unplugged cable for a minute and plugged it in back, networking was restored and I could reach via ssh. I'd like to make some workaround for now and the simplest thing seems to be write a script and put into crontab every minute - check/ping network and make a networking restart if failed. But the question is - how is managed eth0 for OPI PC in mainline ubuntu server? Just ifdown/ifup eth0 or via nmcli? I ask because I can see that mncli shows eth0 unmanaged...what is the proper way? rufik@opi:~$ uname -a Linux opi 4.14.18-sunxi #24 SMP Fri Feb 9 16:24:32 CET 2018 armv7l armv7l armv7l GNU/Linux rufik@opi:~$ ifconfig eth0 Link encap:Ethernet HWaddr 02:81:fd:fc:ae:65 inet addr:192.168.9.2 Bcast:192.168.9.255 Mask:255.255.255.0 inet6 addr: fe80::81:fdff:fefc:ae65/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:5809 errors:0 dropped:0 overruns:0 frame:0 TX packets:5305 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:1000 RX bytes:552340 (552.3 KB) TX bytes:980090 (980.0 KB) Interrupt:38 rufik@opi:~$ cat /etc/network/interfaces source /etc/network/interfaces.d/* # Wired adapter #1 allow-hotplug eth0 no-auto-down eth0 iface eth0 inet dhcp # Local loopback auto lo iface lo inet loopback rufik@opi:~$ sudo nmcli g STATE CONNECTIVITY WIFI-HW WIFI WWAN-HW WWAN connected none enabled enabled enabled enabled rufik@opi:~$ sudo nmcli c NAME UUID TYPE DEVICE rufik@opi:~$ sudo nmcli n enabled rufik@opi:~$ sudo nmcli d DEVICE TYPE STATE CONNECTION eth0 ethernet unmanaged -- lo loopback unmanaged --
×
×
  • Create New...

Important Information

Terms of Use - Privacy Policy - Guidelines