[Matt Devo]

Yes, thanks, Matt. I was using quotes around "git" to imply a (sic). Bad joke... I wasn't able to get Kodi through that command. But, instead, I figured out the process for updating your Full Rom script and installing Libre Elec. All is well. Assuming you are pushing the UEFI automatically with the update, I should be done. Now working on adding Chromium, Emby, and some addons I always had. Then I will repeat for the other box. THANKS SOOOO MUCH FOR ALL YOUR HELP THOUGH THE YEARS!!!

ok good deal

[smyrosnik]

Hi, I have a question about booting.

I have setup my asus chromebox perfectly according to the guide (debian). My question is when the system boots up, it always shows the EFI shell , timeouts for 3 seconds and the proceeds to grub loader from debian to boot.
Is this normal? Or I can config it to load directly to grub?

In my /boot/efi directory I have a script called startup.nsh with contents
FS0:
\EFI\debian\grubx64.efi

(without this stays in EFI shell)

When executing efibootmgr I get the following:

BootCurrent: 0001
Timeout: 3 seconds
BootOrder: 0000,0001
Boot0000* EFI Hard Drive
Boot0001* EFI Internal Shell

Any thoughts to show directly grub instead of EFI shell?


Thank you.

[Matt Devo]

Hi, I have a question about booting.

I have setup my asus chromebox perfectly according to the guide (debian). My question is when the system boots up, it always shows the EFI shell , timeouts for 3 seconds and the proceeds to grub loader from debian to boot.
Is this normal? Or I can config it to load directly to grub?

Item #2 on my FAQ: https://mrchromebox.tech/#faq

TL;DR: copy /EFI/debian/grubx64.efi to /EFI/BOOT/BOOTX64.efi
(create BOOT dir if needed)

[smyrosnik]

I can't believe I missed the FAQ page! Bookmarked it. Thanks!

[Maximus1717]

Hello all,
My first post!
First off thanks to Matt and all developers providing such an awesome an easy software to get the most out of my chrome box.
I recently upgraded my TV to a Visio D50U-D1 and now I cannot get get my Asus m004u chromebox running dualboot latest libreelec build(LibreELEC-Generic.x86_64-8.0.0.tar) to connect. I am getting a no signal. When I use the same cable on another monitor it works flawlessly. Also when I plug in a different video source, that port works. I have alaso tried all other hdmi ports. I really don't know if I should take the TV back or if its libreelec.

I have tried the following:
-all known visio resets(holding power button for 30 seconds, ect)
- trying different power up options
I am not sure what to try next please help
Thanks!

[Matt Devo]

Hello all,
My first post!
First off thanks to Matt and all developers providing such an awesome an easy software to get the most out of my chrome box.
I recently upgraded my TV to a Visio D50U-D1 and now I cannot get get my Asus m004u chromebox running dualboot latest libreelec build(LibreELEC-Generic.x86_64-8.0.0.tar) to connect. I am getting a no signal. When I use the same cable on another monitor it works flawlessly. Also when I plug in a different video source, that port works. I have alaso tried all other hdmi ports. I really don't know if I should take the TV back or if its libreelec.

I have tried the following:
-all known visio resets(holding power button for 30 seconds, ect)
- trying different power up options
I am not sure what to try next please help
Thanks!

there's a known issue with many Vizio 4K sets where they report via EDID that they support 1080p at 120Hz (IIRC, but they don't) and so that's the mode the Chromebox is trying to use. I'm not sure how that works with a dual boot setup though, because in that case the video BIOS actually gets run twice, which may be problematic. In general, the firmware graphics driver in the UEFI standalone firmware is a bit better at handling newer/4K sets, but as I don't have one myself I haven't done any real testing.

If you're able to boot ChromeOS, then it's possible that using an autostart script to set the LibreELEC video mode to 1080p60 will suffice. If not, then I'd backup your LE userdata and give the UEFI firmware a try, see if it can boot the installer from USB at least.

[ArieS]

Hello, I'm thinking about replacing my ODroid C2 with a ChromeBox. The C2 is fine but I like to use a heavy skin and it's pretty sluggish at it...

If I go with a Intel Celeron 2955U, can I add more RAM to it if the skin needs it?
Tried to look on Amazon for what kind of RAM is needed but couldn't find the exact model.

Can I leave the ChromeBox always on or does it need to be turned off when not in use. I'm sure it draws more power than the C2 but how much compared to a regular Desktop?

I'm using iRule for remote control (via Network) so wondering also if the ChromeBox can be started with WOL from S3, S4 like my Intel NUC.

Thanks.

[Matt Devo]

Hello, I'm thinking about replacing my ODroid C2 with a ChromeBox. The C2 is fine but I like to use a heavy skin and it's pretty sluggish at it...

If I go with a Intel Celeron 2955U, can I add more RAM to it if the skin needs it?
Tried to look on Amazon for what kind of RAM is needed but couldn't find the exact model.

Can I leave the ChromeBox always on or does it need to be turned off when not in use. I'm sure it draws more power than the C2 but how much compared to a regular Desktop?

I'm using iRule for remote control (via Network) so wondering also if the ChromeBox can be started with WOL from S3, S4 like my Intel NUC.

Thanks.

see the Chromebox wiki, linked in my sig -- 16GB DDR3L max (2x2GB will be plenty)

I leave mine on 24x7, it uses something like 3W at idle and < .5W when suspended.

WoL is supported for S3/S4 for Ethernet, but not wifi.

[ArieS]

Thanks Matt!
Hopefully I'll be the winning bid on ebay
In the meantime, I've got some reading to do on the Wiki I guess

[mjunk]

So I finally pulled the trigger on the ASUS Chromebox today and followed the instructions on the front page but found that some of the menu items are not the same.

I want to install the standalone LibreELEC and of course the first thing I did was to remove the screw to disable the firmware protection. From there I was successful in entering developer mode and download the E-Z script. When the menu options come up I assume I start at step 6 under standalone however I get different options: the instructions show "6. Install/update: Custom coreboot firmware" however I get "6. Install/update: Custom UEFI firmware". So I select 6 only to get an error message saying hardware write-protect enabled and it cannot flash full ROM firmware. Odd since I'm staring at the screw I took out.

So I proceed to step 7 and download/installation of LibreELEC on USB was fine. However, I never got the boot options screen. When powering off and restarting it just goes to ChromeOS at the screen that says verification is off. My only option is to return to developer mode to download and run the script and I did that twice with the same results.

So what am I doing wrong? The screw is off and I don't understand that write-protect error. Am I following the right sequence for standalone? Should I try dual?

Thanks for any help.

[Matt Devo]

I want to install the standalone LibreELEC and of course the first thing I did was to remove the screw to disable the firmware protection. From there I was successful in entering developer mode and download the E-Z script. When the menu options come up I assume I start at step 6 under standalone however I get different options: the instructions show "6. Install/update: Custom coreboot firmware" however I get "6. Install/update: Custom UEFI firmware". So I select 6 only to get an error message saying hardware write-protect enabled and it cannot flash full ROM firmware. Odd since I'm staring at the screw I took out.

I'll update the instructions/screenshot at some point, but the functionality is the same.

If the script is telling you that write protect is still enabled, then it's still enabled. As per the wiki instructions:

On some boxes (this is rare, but seems to be most common on the Dells), even after removing the write-protect screw, there is still connectivity between the two semi-circles, in which case you may need to use a small flathead screwdriver (eg) to lightly scrape away the excess material which is causing continuity. You can verify with a DMM.

sometimes the connectivity is on the inner part of the screw hole, so check that too. And double check you removed the correct screw.

So I proceed to step 7 and download/installation of LibreELEC on USB was fine. However, I never got the boot options screen. When powering off and restarting it just goes to ChromeOS at the screen that says verification is off. My only option is to return to developer mode to download and run the script and I did that twice with the same results.

So what am I doing wrong? The screw is off and I don't understand that write-protect error. Am I following the right sequence for standalone? Should

of course it's still rebooting to ChromeOS -- you never installed the custom firmware, due to the write protect still being enabled. Fix the WP, then flash the firmware, then boot from USB and install LibreELEC

[mjunk]

On some boxes (this is rare, but seems to be most common on the Dells), even after removing the write-protect screw, there is still connectivity between the two semi-circles, in which case you may need to use a small flathead screwdriver (eg) to lightly scrape away the excess material which is causing continuity. You can verify with a DMM.

sometimes the connectivity is on the inner part of the screw hole, so check that too. And double check you removed the correct screw.


of course it's still rebooting to ChromeOS -- you never installed the custom firmware, due to the write protect still being enabled. Fix the WP, then flash the firmware, then boot from USB and install LibreELEC

Thank you so much Matt.

I knew about that wiki quote but I thought that applied only to Dell's. I'll check it again and make sure the right screw was removed. (I thought I saw only one.)

Just to confirm I do start at step 6 right?

[Matt Devo]

Thank you so much Matt.

I knew about that wiki quote but I thought that applied only to Dell's. I'll check it again and make sure the right screw was removed. (I thought I saw only one.)

Just to confirm I do start at step 6 right?

yes, start with the firmware flash (menu option 6), then boot/install LibreELEC and you should be set

[mjunk]

Thank you so much Matt.

I knew about that wiki quote but I thought that applied only to Dell's. I'll check it again and make sure the right screw was removed. (I thought I saw only one.)

Just to confirm I do start at step 6 right?

yes, start with the firmware flash (menu option 6), then boot/install LibreELEC and you should be set

Thanks. I decided to install dual boot Chrome OS/LibreELEC and followed all the steps including creating a recovery USB. Long story short, I now get "Press ESC for boot menu" and when I do nothing happens. Nest message that comes up is Booting from Hard Disk and Missing OS. This happens even when I insert the recovery USB. I hope I didn't brick it.

Any suggestions how I can back to do a fresh start?

Edit: here's what I get starting in various modes:
- Turn on normally with no USB: goes to recovery mode for a second then straight to the boot from hard drive screen with "press to escape for boot menu" (which does nothing) then to a blank dark screen

- Turn on using recovery button: goes to the recovery screen. Text at top left-hand corner says I have Google_Panther firmware id. Insert my recovery USB and system recovery performs successfully. Remove USB when done to restart, end up at the same result as above-booting from hard drive and blank screen.

- As a final resort, downloaded LibreELEC USB creator, inserted and restarted normally with the USB in: same as above.

It seems that the only option is to boot from the hard drive. I cannot run the E-Z setup script so I'm at a dead-end now.

Thanks

Edit 2: I managed to get into developer mode by pressing Ctrl-D earlier. This is in the wiki and it worked. I have now got it working booting straight to LibreELEC. Will continue to test it out tonight to see if I can boot into ChromeOS. Thanks for your guidance Matt!

[Wasse]

I'm running Ubuntu Server 16.04.... Everything works perfectly (after setting up the correct EFI Boot from the FAQ)

BUT, the Server doesn't won't boot, UNLESS I have some kind of Video Output connected. If I have HDMI/DP connected, it will boot fine. But if I don't... It won't boot.

If I try to connect an HDMI cable to it after it's already tried it's booting, it will flicker a "Graphics Console Started" on the screen off and on, but still won't boot the server.

Any ideas?