rufik

Members
  • Content Count

    101
  • Joined

  • Last visited

About rufik

  • Rank
    Elite member

Profile Information

  • Gender
    Male
  • Location
    Poland

Recent Profile Visitors

1001 profile views
  1. So effectively wlan0 down is the same as commenting it out in DT, right?
  2. I do not use wifi at all, so I'd like to disable it completely. It's not configured right now, but I wonder if I could power down whole chip, ex. commenting it out in DT file? Does it save some power or not?
  3. Opi3 here with slow chip (bin=1) (raw=1).
  4. As far as comments are somehow meaningful it's perfectly fine. Consider this example: $ sudo apt list --upgradable Listing... Done armbian-config/bionic,bionic 5.98.191022 all [upgradable from: 5.98.191016] It would be nice to know what has changed in armbian-config package version 5.98.191022 compared to 5.98.191016, if it's worth to upgrade or just dangerous to me (like kernel/uboot). Commit comments are sufficient, I can just go to github repo to investigate it further. I really know that any hands are welcome, I've been tracking project for more than year and still have no time to participate (kids, kids, kids, work, building a house) :/ But maybe...some day...:P
  5. Diff would be really nice and 100% sufficient for me [emoji108]
  6. How to track changes in armbian packages, especially for dev boards like OPI 3? I know there is Changelog in docs site but it's not really up to date... For example apt reports me now that there are new packages to be updated: linux-dtb-dev-sunxi64 linux-image-dev-sunxi64 linux-u-boot-orangepi3-dev. How can I tracka/see changes made in them?
  7. This directive is deprecated now. But I've set realtime=no and this error has gone.
  8. So it seems we (users) can buy this SBC now, thanks a lot [emoji12]
  9. 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?
  10. 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
  11. 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.
  12. Anything below 480 MHz just trashes storage performance and almost saves no power. So leave minimal freq as is.
  13. Maybe blacklist touchscreen driver?
  14. 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...
  15. 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.