The forum is read-only currently.
DANGER: DO NOT do a manual Debian/Linux upgrade to your Kiwi! (update: but it's okay now)
We're not talking about the Kiwi auto-update process. That feature is perfectly fine and will continue as usual.
We're talking about people who manually update/upgrade the underlying Debian/Linux system on the Kiwi by logging into the Beagle as root and running, for example, the "apt" command. Please don't do this. We only validate specific Debian distributions. If you update manually you run the risk of "bricking" your Kiwi server. That is, downloading something causing an unexpected side-effect which prevents the Kiwi server from running. This will stop further auto-updates and will require a manual intervention to fix. Possibly by re-flashing your Beagle using the Seeed SD-card and losing your entire Kiwi configuration (unless you've backed up).
This is exactly what has happened since a change was made in late February by one of the Beagle developers that made its way into the Debian update stream. We've identified the problem and have asked them to make a change. But it is not clear when this might happen. If you have a Kiwi in this condition then please use the following workaround:
Symptom: The Kiwi server won't stay running. The log shows it just crashes and restarts over and over again with the error "SYS_PANIC: open spidev".
1) ssh/PuTTY into your Kiwi Beagle as user "root" (no password).
2) "cdp" Change to Kiwi build directory.
3) "up" Manually pulls the latest version from Github (v1.175 or later) and builds it.
4) When that's done do "cd unix_env/bb.org-overlays"
5) Type "./install.sh" (note the "dot" before the slash)
6) When that's done type "reboot"
Now the Kiwi server should run after the reboot.
If you upgrade from here things will break again until the Beagle developers can implement a permanent solution.