2015-06-23, 17:34
Quote:normally that error only occurs when you are pressing CTRL-<something> after SeaBIOS starts, which you shouldn't do. Are you getting this error without any keyboard interaction?
I am not sure if i get you here. I start the device by powering on. Then i press Ctrl + L to tell it to boot my Kodi. Then i wait and do nothing and get the described message about 639K RAM.
Quote:what seems most likely is that the bootloader got messed up, not the OS itself (which is a read-only image), or anything Kodi-related. You basically have two options: 1) re-install OpenELEC using the EZ Setup Script (this won't affect ChromeOS at all, but will erase your Kodi user data), or 2) boot ChromeOS, mount the OE partitions, and try to fix things manually (which would require you to msg me on IRC or google hangouts to walk you thru it)
Thanks for leting me know the options. I am totally ok with only reinstalling Kodi. The configuration in Kodi is done quite quick. I will then do a backup of it so i have it handy for any future upcoming similar events