Hi, My LinkStar-H68K arrived and flashed tfcard with openwrt with docker support OpenWrt R22.11.13
When I click on Status > Overview I get the following errors:
/usr/lib/lua/luci/dispatcher.lua:474: Failed to execute template dispatcher target for entry ‘/admin/status/overview’.
The called action terminated with an exception:
/usr/lib/lua/luci/template.lua:74: Failed to load template ‘admin_status/index’.
Error while parsing template ‘/usr/lib/lua/luci/view/admin_status/index.htm’:
I/O error
stack traceback:
[C]: in function ‘assert’
/usr/lib/lua/luci/dispatcher.lua:474: in function ‘dispatch’
/usr/lib/lua/luci/dispatcher.lua:126: in function </usr/lib/lua/luci/dispatcher.lua:125>
I had the exact same problem. I also have the exact same version as you. I wasn’t able to get the TF card to work but I was able to put it directly on the eMMc and although it didn’t resolve the TF card issue it did make it to where I was able to use the device. Hope this helps somewhat.
Think must have been a network issue as when I used it today it was perfect.
Any way to get Google services installed on the Android version? Trying to install plex but on Google play store the device is not available to select.
So if you have a smart home there is one wiki I found that was pretty cool and easy to follow. You can install Home Assistant in a docker container. Access it from a web UI and control all the smart devices. One thing that is different in the wiki is it says to drag the amount of space you are going to require. On this version what you will do is put the specific amount as number in the two digit columns on the bottom. If you don’t specify it’s going to use the rest of the space specifically for this docker container. I did get a response from Tech support and they said they are going to have a different git up soon and we can pull that firmware. Next week is the ETA.
OpenWrt allows you to boot into a failsafe mode that overrides its current configuration. If your device becomes inaccessible, e.g. after a configuration error, then failsafe mode is there to help you out. When you reboot in failsafe mode, the device starts up in a basic operating state, with a few hard coded defaults, and you can begin to fix the problem manually.
Failsafe mode cannot, however, fix more deeply rooted problems like faulty hardware or a broken kernel. It is similar to a reset, however with failsafe, you can access your device and restore settings if desired, whereas a reset would just wipe everything.
Caveat: Failsafe mode is only available if you have installed firmware from a SquashFS image, that includes the required read-only root partition. To verify whether your device has the SquashFS root partition, check for “squashfs” either in the OpenWrt image name or perform the following check on your device:
grep squash /proc/mounts
The terminal should return something similar to this:
Side note with TF card issues. I flashed the OpenWRT image to the TF card, but apparently it wasn’t enough. I had to repartition/format my TF card to MBR ExFat before flashing the OpenWRT image on a macOS. H68K is only able to boot from MBR structure disk.
On different OS you may have to use other commands to set partition structure. On macOS I was able to set structure only when reformatting/erase.