(2016-12-13, 19:14)Matt Devo Wrote: [ -> ] (2016-12-13, 18:56)HDClown Wrote: [ -> ]I don't have a way to not set it to shutdown or suspend, unless I'm just totally missing something. Here's what I have available: in Kodi to set: http://i.imgur.com/NfSAeIEl.jpg
the shutdown/suspend function is only relevant when the timer setting above is active; otherwise it just sets the function of the remote 'powertoggle' command
Interesting. I didn't make any changes with my Harmony remote configuration, and when I was using OpenELEC with a dualboot config (done back in the early days of the script), the Chromebox never shut down. Guess I'll need to modify the settings on the remote and make sure it's set for the device to be always on.
(2016-12-13, 21:53)HDClown Wrote: [ -> ]Interesting. I didn't make any changes with my Harmony remote configuration, and when I was using OpenELEC with a dualboot config (done back in the early days of the script), the Chromebox never shut down. Guess I'll need to modify the settings on the remote and make sure it's set for the device to be always on.
I suspect that's your issue
What did I do wrong while resetting, because my box is now still in developer mode, and screen that tells me about that just flashes for 2s? It's not big deal because ChromeOS loads and works just fine apart from that.
I tried to follow instructions in Wiki, but this part was bit odd to me:
"Note that this will re-partition the internal hard drive and restore the original copy of ChromeOS, erasing anything else on the drive. The ChromeBox will still be left in developer mode, and if you changed the Boot Options they will still be set - so be sure to reset them back to the 'ChromeOS + 30s default' option before performing a factory reset. If you forget to do that, you'll need to press [CTRL-D] on the developer boot screen (or before the legacy boot/SeaBIOS boot screen) in order to boot ChromeOS after performing the recovery. "
So I did restore the stock firmware via Ubuntu, and then performed reset with Google's restore media. While in Ubuntu and running that restoring script, it said something about running script again after restoring for setting boot options, but I can't boot to usb-stick anymore with stock firmware?
(2016-12-17, 20:45)BoxFreak Wrote: [ -> ]What did I do wrong while resetting, because my box is now still in developer mode, and screen that tells me about that just flashes for 2s? It's not big deal because ChromeOS loads and works just fine apart from that.
I tried to follow instructions in Wiki, but this part was bit odd to me:
"Note that this will re-partition the internal hard drive and restore the original copy of ChromeOS, erasing anything else on the drive. The ChromeBox will still be left in developer mode, and if you changed the Boot Options they will still be set - so be sure to reset them back to the 'ChromeOS + 30s default' option before performing a factory reset. If you forget to do that, you'll need to press [CTRL-D] on the developer boot screen (or before the legacy boot/SeaBIOS boot screen) in order to boot ChromeOS after performing the recovery. "
So I did restore the stock firmware via Ubuntu, and then performed reset with Google's restore media. While in Ubuntu and running that restoring script, it said something about running script again after restoring for setting boot options, but I can't boot to usb-stick anymore with stock firmware?
I'm not understanding what your issue is, but to clarify the restoration instructions, you need to boot ChromeOS and re-run the Firmware Utility Script to reset the boot flags/boot options in order to be able to exit Developer Mode
Of course, I didn't realise that it's possible to use terminal in ChromeOS.
Thank you, I'm sure that will help!
Hi Matt,
I was wondering if you'd be able to help. I bought a new Samsung TV during Black Friday and it finally arrived today. When I went to go plug-in my Chromebox (i3 with LibreElec connected via HDMI) the screen was blank and it told me that there wasn't any source.
Is there an option in Kodi/LibreElec to get the box and TV to play nice? I tried connecting the Chromebox to my older LG TV and it fired up right away.
Have you encountered something similar? Any thoughts or tips are greatly appreciated.
Cheers,
(2016-12-17, 23:32)eros28 Wrote: [ -> ]Hi Matt,
I was wondering if you'd be able to help. I bought a new Samsung TV during Black Friday and it finally arrived today. When I went to go plug-in my Chromebox (i3 with LibreElec connected via HDMI) the screen was blank and it told me that there wasn't any source.
Is there an option in Kodi/LibreElec to get the box and TV to play nice? I tried connecting the Chromebox to my older LG TV and it fired up right away.
Have you encountered something similar? Any thoughts or tips are greatly appreciated.
Cheers,
There appears to be some sort of issue with the video BIOS (vbios) used in the stock firmware (as well as my custom Legacy boot firmware) and 4K sets. One potential solution is to use my new UEFI boot firmware, which doesn't use a video BIOS, and should be more compatible with 4K sets, but will require you to backup/reinstall OE/restore your backup
@
matt,
Thanks for the quick reply, I'll give it a shot and report back.
Cheers,
(2016-12-18, 00:15)Matt Devo Wrote: [ -> ] (2016-12-17, 23:32)eros28 Wrote: [ -> ]Hi Matt,
I was wondering if you'd be able to help. I bought a new Samsung TV during Black Friday and it finally arrived today. When I went to go plug-in my Chromebox (i3 with LibreElec connected via HDMI) the screen was blank and it told me that there wasn't any source.
Is there an option in Kodi/LibreElec to get the box and TV to play nice? I tried connecting the Chromebox to my older LG TV and it fired up right away.
Have you encountered something similar? Any thoughts or tips are greatly appreciated.
Cheers,
There appears to be some sort of issue with the video BIOS (vbios) used in the stock firmware (as well as my custom Legacy boot firmware) and 4K sets. One potential solution is to use my new UEFI boot firmware, which doesn't use a video BIOS, and should be more compatible with 4K sets, but will require you to backup/reinstall OE/restore your backup
Hi Matt,
A quick question for you. I installed the UEFI firmware and then installed LibreElec, and it loaded everything well. How would I update the firmware going forward? I'm well versed using your script by going into the ChromeOS but now that it isn't there how would I go about it?
Also, I hear the fan pretty high since going to UEFI, is there a utility to minimize the fan speed/noise?
Cheers,
(2016-12-18, 06:33)eros28 Wrote: [ -> ]Hi Matt,
A quick question for you. I installed the UEFI firmware and then installed LibreElec, and it loaded everything well. How would I update the firmware going forward? I'm well versed using your script by going into the ChromeOS but now that it isn't there how would I go about it?
Also, I hear the fan pretty high since going to UEFI, is there a utility to minimize the fan speed/noise?
Cheers,
same as you flashed it now - from a shell terminal in a Linux distro that has a real bash shell
the fan speed / thermal threshold defaults shouldn't have changed going from one firmware to the other, but you can control the fan speed thru whatever mechanism the OS supports/provides
did the UEFI firmware at least resolve the issue with your 4K set?
(2016-12-18, 06:39)Matt Devo Wrote: [ -> ] (2016-12-18, 06:33)eros28 Wrote: [ -> ]Hi Matt,
A quick question for you. I installed the UEFI firmware and then installed LibreElec, and it loaded everything well. How would I update the firmware going forward? I'm well versed using your script by going into the ChromeOS but now that it isn't there how would I go about it?
Also, I hear the fan pretty high since going to UEFI, is there a utility to minimize the fan speed/noise?
Cheers,
same as you flashed it now - from a shell terminal in a Linux distro that has a real bash shell
the fan speed / thermal threshold defaults shouldn't have changed going from one firmware to the other, but you can control the fan speed thru whatever mechanism the OS supports/provides
did the UEFI firmware at least resolve the issue with your 4K set?
I won't be able to try tonight as the gf is watching her shows.
As for the fan issue, I may have to re-run everything as I can't find an option to control fan speed in LibreElec.
(2016-12-18, 06:53)eros28 Wrote: [ -> ]I won't be able to try tonight as the gf is watching her shows.
As for the fan issue, I may have to re-run everything as I can't find an option to control fan speed in LibreElec.
reinstalling the OS won't do anything there. Which box is this? If not the Asus (panther), is it running the Asus firmware, or the proper firmware for the device?
I think I fixed the problem. I have an Asus Chromebox (CN60 i believe)
Once flashing the new UEFI firmware and installing LibreElec from a USB stick. The fan speed was at max.
I went to the wiki and followed the "High/Full fan speed on Wakeup from Suspend:" procedure. I SSH from my Macbook. I put the box in Suspend and then woke it up and the fan noise was gone. I restarted the box and the fan noise was not present.
ok cool well LMK how the 4K goes, I'll be testing here too soon hopefully
Hi Matt, I am going to upgrade to the UEFI firmware so I can use my ASUS Chromebox on my 4K TV.
My LibreELEC install (Millhouse builds) is all backed up so not bothered if things get wiped, is there a best way to go about this please?
I am thinking I create a Linux USB stick and run the firmware updater from that then install LibreELEC using their install creator and update to Millhouse build as normal, does that sound about right?