[SandmanUT]

an easy way to test would be to use a GalliumOS or LibreELEC USB, and see their behavior on startup

Boot from Gallium..identical issues. No DP, HDMI doesn't want to recognize if change monitors without the triple reboot, etc. Reloaded the UEFI script again, just in case something was missing and reinstalled the firmware again. Same.

A reminder that this is a Panther box.

Should I just return to the stock firmware backup that was working previously? It appears that steamos (not that i'm loving that interface..but it's what's loaded) brewmaster has support for non uefi.

thoughts?

[Matt Devo]

I got very wierd HDMI Handshake Problems with my Chromebox after i switched my Beamer and HDMI Switch. After Refresh Rate switch sometimes Signal Errors with crazy Image distortion. I first thought that its a HDMI Cable Problem. I switched that but no luck, after that i thougt my HDMI Splitter is broken but atm i think its the Chromebox.

if it works without the splitter/switch inline, then I don't think the problem is with the Chromebox...

Boot from Gallium..identical issues. No DP, HDMI doesn't want to recognize if change monitors without the triple reboot, etc. Reloaded the UEFI script again, just in case something was missing and reinstalled the firmware again. Same.

A reminder that this is a Panther box.

Should I just return to the stock firmware backup that was working previously? It appears that steamos (not that i'm loving that interface..but it's what's loaded) brewmaster has support for non uefi.

thoughts?

you can revert to the previous legacy boot/SeaBIOS firmware using the Firmware Utility Script, just choose the unlock option (u) from the main menu first, then it will give you the choice between Legacy and UEFI when flashing. No reason to go back to stock. I'm not expecting it will fix the issue, but worth trying to rule it out at least

[john.cord]

I got very wierd HDMI Handshake Problems with my Chromebox after i switched my Beamer and HDMI Switch. After Refresh Rate switch sometimes Signal Errors with crazy Image distortion. I first thought that its a HDMI Cable Problem. I switched that but no luck, after that i thougt my HDMI Splitter is broken but atm i think its the Chromebox.

if it works without the splitter/switch inline, then I don't think the problem is with the Chromebox...

the fact that only the chromebox is affected and all other devices (PS4, PS3, Xbox One, Xbox 360,...) not brought me to the conclusion that its the chromebox. I switched the Splitter, die HMDI Cabels out and the problem is still present... i will try it with a fresh install with latest firmware for the chromebox and cross test it with a BeeBox J3160 tomorrow...

[john.cord]

I tried updating the firmware with a Ubuntu live Image over USB but now i have GRUB2 Bootmanger screen and cannot boot into Kodi Some idea how to fix this? I booted GalliumOS from USB but cannot change the boot options? Have i do a factory Reset?

[Matt Devo]

I tried updating the firmware with a Ubuntu live Image over USB but now i have GRUB2 Bootmanger screen and cannot boot into Kodi Some idea how to fix this? I booted GalliumOS from USB but cannot change the boot options? Have i do a factory Reset?

assuming you were running LibreELEC with the legacy boot firmware before, and you updated to the UEFI firmware, it's to be expected that the OS will no longer boot -- you simply can't change firmware types without reinstalling the OS or doing quite a bit of manual manipulation. That's not even a Chromebox thing, it's a PC thing.

If you don't care about your old setup, simply reinstall LibreELEC from USB. if you do, then revert to the older legacy boot firmware using the same instructions I posted above for SandmanUT

[john.cord]

ok thanks. i reverted back to stock and reinstalled the firmware and kodi.

[Matt Devo]

ok thanks. i reverted back to stock and reinstalled the firmware and kodi.

that was overkill, but ok I suppose

[john.cord]

maybe but it works now. Another thing. Why does the chromebox defaults to 1080i on Bootscreen and Kodi?

[Matt Devo]

maybe but it works now. Another thing. Why does the chromebox defaults to 1080i on Bootscreen and Kodi?

it defaults to whatever the display reports as the native resolution. it should always be progressive though

[SandmanUT]

I got very wierd HDMI Handshake Problems with my Chromebox after i switched my Beamer and HDMI Switch. After Refresh Rate switch sometimes Signal Errors with crazy Image distortion. I first thought that its a HDMI Cable Problem. I switched that but no luck, after that i thougt my HDMI Splitter is broken but atm i think its the Chromebox.

if it works without the splitter/switch inline, then I don't think the problem is with the Chromebox...

Boot from Gallium..identical issues. No DP, HDMI doesn't want to recognize if change monitors without the triple reboot, etc. Reloaded the UEFI script again, just in case something was missing and reinstalled the firmware again. Same.

A reminder that this is a Panther box.

Should I just return to the stock firmware backup that was working previously? It appears that steamos (not that i'm loving that interface..but it's what's loaded) brewmaster has support for non uefi.

thoughts?

you can revert to the previous legacy boot/SeaBIOS firmware using the Firmware Utility Script, just choose the unlock option (u) from the main menu first, then it will give you the choice between Legacy and UEFI when flashing. No reason to go back to stock. I'm not expecting it will fix the issue, but worth trying to rule it out at least

Instead of loading Legacy (1) I reloaded my full backup firmware and all display ports (DP & HDMI) and all cables play nice (enough) with all displays once again. I didn't go back to stock, the box had been running your script with openelec/chromeos dual boot for a long time already, just back to the legacy version that worked previously and now once again. I stuck with GalliomOS this time, since it was what I was live booting off of. But the revert back to the working version enabled dp and hdmi (mirroring) while Gallium was still on the stick, which it wouldn't do under the UEFI, so that you know.

[ardsavac]

Can you ssh in and see if there is anything in the log?

I have the same blank screen after update with only a mouse cursor.

http://pastebin.com/RnbV7YEV

[Matt Devo]

Hi everyone,
Recently I updated through the libreelec settings on my chromebox from 7.0.3 and after the libre boot screen its been blank (black screen with a cursor in the middle). Any ideas on what I should do from here? Never had this happen before after doing a update.

I use a single boot setup.

Thanks for your help.

I have the same blank screen after update with only a mouse cursor.

http://pastebin.com/RnbV7YEV

Apparently there is an issue with Kodi 17 updating the addons database -- sometimes it gets corrupted and fails to migrate to the new version:

Update: We have seen reports of boxes getting stuck on the Krypton splash screen after updating. Removing /storage/.kodi/Databases/Addons27.db manually allows Kodi to complete migration but add-ons will need to be re-enabled afterwards. The bug has been reported to Kodi. Auto-update will not be available until the issue is resolved. If you do not experience the issue when updating, do not delete the Addons27.db file!

Removing Addons27.db _should_ just re-migrate whatever database you have, hopefully succeeding second time around

[Matt Devo]

Instead of loading Legacy (1) I reloaded my full backup firmware and all display ports (DP & HDMI) and all cables play nice (enough) with all displays once again. I didn't go back to stock, the box had been running your script with openelec/chromeos dual boot for a long time already, just back to the legacy version that worked previously and now once again. I stuck with GalliomOS this time, since it was what I was live booting off of. But the revert back to the working version enabled dp and hdmi (mirroring) while Gallium was still on the stick, which it wouldn't do under the UEFI, so that you know.

your GalliumOS install on the USB stick was done with the legacy boot firmware, so it would not be expected to boot with the UEFI firmware. If you're moving from legacy to UEFI, you pretty much have to start fresh.

[ardsavac]

Removing Addons27.db _should_ just re-migrate whatever database you have, hopefully succeeding second time around

First,
I deleted /storage/.kodi/Userdata/Database/Addons27.db (Userdata was missing from your description)
This did not work for me. It now boots to a black screen only. No libreelec splash or mouse pointer.

Reading on the Libreelec forums it should copy Addons26.db to Addons27.db. I do not have an Addons26.db file in my directory. It did create an Addons27.db file after deleting my zero length file.

Extra info: I first updated to 7.95.2 using the built in gui updater. 8.0 was not in the list and I figured I would just do a two step update (first to 7.95.2, then to 8.0) When 7.95.2 failed to boot properly I loaded the *.tar for 8.0 into the update folder. Therefore I am running 8.0 now, but the update failed going to 7.95.2

Any ideas?

[Matt Devo]

Removing Addons27.db _should_ just re-migrate whatever database you have, hopefully succeeding second time around

First,
I deleted /storage/.kodi/Userdata/Database/Addons27.db (Userdata was missing from your description)
This did not work for me. It now boots to a black screen only. No libreelec splash or mouse pointer.

Reading on the Libreelec forums it should copy Addons26.db to Addons27.db. I do not have an Addons26.db file in my directory. It did create an Addons27.db file after deleting my zero length file.

Extra info: I first updated to 7.95.2 using the built in gui updater. 8.0 was not in the list and I figured I would just do a two step update (first to 7.95.2, then to 8.0) When 7.95.2 failed to boot properly I loaded the *.tar for 8.0 into the update folder. Therefore I am running 8.0 now, but the update failed going to 7.95.2

Any ideas?

as it's not in any way Chromebox related/specific, might be better served in one of the general Kodi support forums or the LE forums. I have not run into this issue myself and only copy/pasted the blurb from LE's site.