I just went through the process myself and couldn't find a simple guide... Had to piece several posts together to figure it all out... Surely it could be simplified..
What has retroarch got to do with Matt Devo's script? Absolutely nothing! Please start another thread.
(2015-03-15, 00:22)ardsavac Wrote: [ -> ]Matt,
I know this isn't specifically a thread for install on Chromebooks. I was having trouble with the install today since I was unable to boot from legacy device (CTRL-L) once everything was complete. I finally saw that by default on the ACER C720 chromebook that booting from the legacy bios is disabled by default. The following had to be run from command
Code:
sudo crossystem dev_boot_legacy=1
Do you think it is proper to add warning to the first post? I finally found it on the following page: http://www.chromium.org/chromium-os/deve...chromebook
I had the same issue. It seems to randomly change to 0. I set up my C720P to dual boot OpenELEC. My wife uses ChromeOS then after a few months, I attempted to use OpenELEC. This was set to 0, but it had worked before. I'm not sure what changes it, just something you need to watch out for.
Thank You for your wonderful script
Only one issue that was caused by my fault cause i didn't changed the keyboard layout before entering the shell
I have two problem after resuming from s3 but i will open a new thread
Question about Power Management ... sort of.
I have an Uninterruptible Power Supply with a USB connector that can signal devices when the power is lost.
Normally you have that USB run to a computer and that computer then sends commands to shut down servers and such.
I've read about how to do this with linux here...http://www.engadget.com/2006/07/25/how-to-network-your-ups/
Think it's possible to do this with my Chromebox?... Have the Chromebox intercept the power lost signal and send shutdown signals to 2 NAS units?...
Maybe there is actually a pre-coded add on for this already.
EDIT - never mind this.... it may be easy but it's surely off topic.
-Brian
Speaking of power - I just ordered one of these, but because I'm Vesa mounting these to the backs of TV's that are a little high for the wife to reach, is there some way to have these turn back on automatically after a power loss, like how some how some bioses have that option? Just trying to get a handle before it's delivered.
(2015-03-16, 22:52)rafisher79 Wrote: [ -> ]Speaking of power - I just ordered one of these, but because I'm Vesa mounting these to the backs of TV's that are a little high for the wife to reach, is there some way to have these turn back on automatically after a power loss, like how some how some bioses have that option? Just trying to get a handle before it's delivered.
The ASUS Chromebox will power on after a power failure, but with Ubuntu it will stay at the Grub screen waiting for a selection unless you edit /etc/default/grub and add:
GRUB_RECORDFAIL_TIMEOUT=0
Not sure about openelec.
Ben
Thanks Ben, that's good info for someone who hasn't purchased it yet!
the firmware is setup to power back on after loss of AC power; how the OS/bootloader handles that is dependent on those components. OE will boot right back up and you'll never know anything happened
Question about firmware
I have a slight problem, managed to create standalone Openelec on my HP chromebox, boots no problem but I don't have a MAC address, so no wifi. Somehow my firmware backup was corrupted when I originally went through the operation which failed, I in the meantime tried the dual boot option which went well until final boot into Openelec, kept getting the message about only having 639k ram and requiring 9k.
Result is, I started over again with standalone Openelec install but when it came to coreboot install, it stated there was no MAC address in loaded firmware and to load from backup, this is when I discovered my backup was corrupt. Is there any way to recover from this, whether with a method of inputting the MAC address into firmware or with a coreboot file with a MAC address included.
Thanks for reading
Joe
(2015-03-17, 13:31)yammydodger Wrote: [ -> ]Question about firmware
I have a slight problem, managed to create standalone Openelec on my HP chromebox, boots no problem but I don't have a MAC address, so no wifi. Somehow my firmware backup was corrupted when I originally went through the operation which failed, I in the meantime tried the dual boot option which went well until final boot into Openelec, kept getting the message about only having 639k ram and requiring 9k.
Result is, I started over again with standalone Openelec install but when it came to coreboot install, it stated there was no MAC address in loaded firmware and to load from backup, this is when I discovered my backup was corrupt. Is there any way to recover from this, whether with a method of inputting the MAC address into firmware or with a coreboot file with a MAC address included.
Thanks for reading
Joe
Joe,
1) how did you manage to get a standalone setup that didn't maintain the MAC from the stock firmware? The script pulls it from the running (stock) firmware, so the only way you wouldn't have it is if you flashed it manually.
2) the unique
ethernet MAC address is the one which is stored in the device firmware, and will work fine without, just using a default value. The wifi MAC address is stored on the card itself and has no relation to the device firmware. You do however have to turn on wifi under OpenELEC, as it's off by default
Not related to script but i plugged an external usb ntfs powered disk, open elec mounted it ( i see a pop up) but i can't see anywhere to add as a source
No unlucky it's a compatibility issue
Wd my book studio 4Tb usb3 Ntfs not mounted (i don't understand why when i unplug it open elec reports hardware disconnected but doesn't say nothing when it's connected)
Wd passport 500gb usb3 ntfs mounted correctly and i added video source
I checked and the 4tb hd is not listes also in system menĂº
Please start a new thread Roby77 as this is long enough and your question isn't related to Matt's script.
when you start the new thread include a link given by the command
after plugging and unplugging the device.