So, I upgraded my ASUS Chrome box to 12.2 (from 12.02) via the LibreElec settings page.
After successfully unpacking the .TAR file and updating the kernel and system, after the first reboot and splash page, I get no GUI, but rather a pointer, that flickers and reappears every few seconds... as if the graphics subsystem is in a restart loop... apparently the network isn't up either as I can't ping it SSH into it. Subsequent reboots do no good.. same behavior.
Any thoughts or suggestions?
What did you installed exactly? LE x86-64 legacy? What are your hardware specs?
I installed 12.2 non-legacy via the LibreElec setting app as outlined on THIS page:
Users with 12.0 installs, or 11.0 installs on x86_64 hardware, can manually update as normal using the LibreELEC settings add-on or by placing an update file in the /storage/.update folder.
In the settings app I selected the 12.2 channel, and it showed as available. This is the same process I've used to upgrade a number of times on this box. I believe if it HAD been legacy (as I had to do on another box) the channel name in the settings app would have specified that?
It's an ASUS Chromebox CN 60 as described HERE. It uses an Intel 2955U CPU with integrated Intel (not NVIDIA) graphics.
Thanks for responding and any help.
Following up on this...
I dug out another identical Chromebox CN60 I had x86 generic_legacy 12.0 on. For it, there is no 12.2 Update Channel listed in the settings app, but did have an 12.0.2 available version. I updated to that, and after reboot, still had no 12.2 listed as a Channel or available as a version.
It does turn out that "legacy" is only called out in the "About" pane of the settings app not the Update Channel name as I had thought. However, the fact that 12.2 was not available on the generic_legacy installation but had been on the one stuck in the loop tends to reinforce the borked one was indeed not a legacy install.
I can get into the BIOS boot menu, so could ostensibly boot from alternate media (USB or file?). But if that doesn't buy me anything, then I may have to just re-install...
Reinstall the spare box with the latest LE13 nightly 'Generic' image. If there is no Kodi GUI after, the Samba server is on/enabled by default and when you access the 'Logfiles' share over the network Samba generates a zip archive containing a bunch of logs. Share the zip so we can see what's happening (or not).
To be clear, by "spare box" are you referring to the 2nd one I referred to that is currently running legacy 12.0.2 or the initial one that's borked?
I'm a tad hesitant to crater the second one as it's now been pressed into service in light of the initial one having failed...
