Login at Kodi Home

amcfarla · 2015-03-18, 01:15

I just tried setting up the dual boot setup with Chrome OS and Openelec on a Dell Chromebook 11. It seemed to install but when I reboot and I get to the Dell screen and hit ctrl-L to boot to Openelec and I just get a blank screen and Openelec never boots up. I tried reinstalling openelec a second time and same results. I can hit ctrl-d at the Dell boot screen and it will boot into Chrome OS without an issue, just not into Openelec. I Didn't remove the Firmware write protect screw, but I didn't think that was necessary. I am wondering what I am missing to be able get openelec to boot up on his device correctly as a second OS? Thank you.

Matt Devo · 2015-03-18, 04:01

(2015-03-18, 01:15)amcfarla Wrote: I just tried setting up the dual boot setup with Chrome OS and Openelec on a Dell Chromebook 11. It seemed to install but when I reboot and I get to the Dell screen and hit ctrl-L to boot to Openelec and I just get a blank screen and Openelec never boots up. I tried reinstalling openelec a second time and same results. I can hit ctrl-d at the Dell boot screen and it will boot into Chrome OS without an issue, just not into Openelec. I Didn't remove the Firmware write protect screw, but I didn't think that was necessary. I am wondering what I am missing to be able get openelec to boot up on his device correctly as a second OS? Thank you.

did you do a factory reset first as per the instructions? I'm guessing not

amcfarla · 2015-03-18, 05:32

(2015-03-18, 04:01)Matt Devo Wrote:
(2015-03-18, 01:15)amcfarla Wrote: I just tried setting up the dual boot setup with Chrome OS and Openelec on a Dell Chromebook 11. It seemed to install but when I reboot and I get to the Dell screen and hit ctrl-L to boot to Openelec and I just get a blank screen and Openelec never boots up. I tried reinstalling openelec a second time and same results. I can hit ctrl-d at the Dell boot screen and it will boot into Chrome OS without an issue, just not into Openelec. I Didn't remove the Firmware write protect screw, but I didn't think that was necessary. I am wondering what I am missing to be able get openelec to boot up on his device correctly as a second OS? Thank you.

did you do a factory reset first as per the instructions? I'm guessing not

Yep that fixed it, creating the recovery media though was a pita. Thanks for the assistance.

Matt Devo · 2015-03-18, 05:51

(2015-03-18, 05:32)amcfarla Wrote: Yep that fixed it, creating the recovery media though was a pita. Thanks for the assistance.

unfortunately not much I can do about that. Using the Chrome browser extension is probably the easiest way to do it.

Matt Devo · 2015-03-18, 05:54

script update 03/17/2015:

- update OpenELEC to 5.0.6 (stable, Kodi 14.2)
- added script function to create standalone Kodibuntu install media, using HugeGreenBug's updated Kodibuntu ISO (contains all required kernel/driver updates/fixes)

Note: no firmware-related changes; SeaBIOS datestamps remain 02/26/2015

amcfarla · 2015-03-18, 06:04

One more thing, I have noticed,not sure if this is an openelec thing or chromebook item, but the external speakers on the Dell Chromebook 11 do not function in Openelec. I have changed every setting and the only thing I can get sound out of is using headphones. Is there a fix for this? Thank you.

amcfarla · 2015-03-18, 06:14

(2015-03-18, 06:04)amcfarla Wrote: One more thing, I have noticed,not sure if this is an openelec thing or chromebook item, but the external speakers on the Dell Chromebook 11 do not function in Openelec. I have changed every setting and the only thing I can get sound out of is using headphones. Is there a fix for this? Thank you.

Well this is strange, booting into Chrome OS, the speakers now work in Openelec. Well that one is a little mind boggling, but I guess it works.

nickr · 2015-03-18, 07:04

Maybe loading chromeos loaded some firmware into the sound chip?

waverz · (This post was last modified: 2015-03-18, 08:19 by waverz.)

Just tried installing openelec via this script and am having issues.

I have a ASUS CHROMEBOX-M115U with a Intel Celeron 2955U 64-bit Dual Core Processor 1.4 GHz.

I get here:

4. Download and run the ChromeBox setup script with the commands:
curl -L -O http://goo.gl/3Tfu5W
sudo bash 3Tfu5W

But when I use the sudo bash 3Tfu5W command I get bash: 3tfu5w: no such file or directory

I've also tried:
curl -L -O https://db.tt/vUPL3OrH
sudo bash vUPL3OrH

but get the same error

Could this be because I have 64-bit architecture ?

Any help or advice would be great!

nickr · 2015-03-18, 09:27

When you type the curl commandline, do you see it download the file?

I see this:

Code:
nick@envy ~/Downloads $ curl -L -O http://goo.gl/3Tfu5W

  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current

                                 Dload  Upload   Total   Spent    Left  Speed

100   260    0   260    0     0    437      0 --:--:-- --:--:-- --:--:--  1319

100   383    0   383    0     0    183      0 --:--:--  0:00:02 --:--:--  9000

100 38605  100 38605    0     0  10844      0  0:00:03  0:00:03 --:--:-- 39363

UdoG · 2015-03-18, 10:30

Hello!

I would like to reset my Asus chromebox but unfortunately I'm not able to disable the OS confirmation after the power-on.

At first I got the OS warning and the following message (top left):

gbb.flags is nonzero: 0x00000039
read-only firmware id: Google_Panther.4920.24.21
Active firmware id: Google_Panther.4920.24.21

If I press enter I got a beep and the following message:

WARNING: TONORM prohibited by GBB FORCE_DEV_SWITCH_ON.
read-only firmware id: Google_Panther.4920.24.21
read-only firmware id: Google_Panther.4920.24.21
Active firmware id: Google_Panther.4920.24.21

... but after the next reboot the OS warning still exists.

Disable Firmware Write Protect is still active (screw is removed).

What's wrong?

Thanks

Udo

amcfarla · 2015-03-18, 12:05

(2015-03-18, 07:04)nickr Wrote: Maybe loading chromeos loaded some firmware into the sound chip?

I have no clue, but I selected the Intel analog sound card and wasn't getting any audio unless I was using headphones. I rebooted Openelec twice and still no sound. I booted into Chrome OS made sure the speakers were working over there, and they worked without an issue. I came back to Openelec and heard the menu navigation sounds when it booted up through the laptop speakers, and videos had sound also. I am not sure, but a little bit of a mystery.

yammydodger · (This post was last modified: 2015-03-18, 16:31 by Matt Devo.)

(2015-03-17, 18:18)Matt Devo Wrote: 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

Matt,

Thanks for the prompt reply, don't know how I've lost the MAC from the firmware, had followed EZ setup script. No problems though as your advice set me on the right track, had been looking in the wrong place for Wifi settings, all sorted now and going well.

Thanks for your help it was much appreciated Smile

Matt Devo · 2015-03-18, 16:30

(2015-03-18, 08:12)waverz Wrote: Just tried installing openelec via this script and am having issues.

I have a ASUS CHROMEBOX-M115U with a Intel Celeron 2955U 64-bit Dual Core Processor 1.4 GHz.

I get here:

4. Download and run the ChromeBox setup script with the commands:
curl -L -O http://goo.gl/3Tfu5W
sudo bash 3Tfu5W

But when I use the sudo bash 3Tfu5W command I get bash: 3tfu5w: no such file or directory

I've also tried:
curl -L -O https://db.tt/vUPL3OrH
sudo bash vUPL3OrH

but get the same error

Could this be because I have 64-bit architecture ?

Any help or advice would be great!

as per the instructions, you need to have setup a network connection (wired or wireless) in order to download the script

(2015-03-18, 10:30)UdoG Wrote: Hello!

I would like to reset my Asus chromebox but unfortunately I'm not able to disable the OS confirmation after the power-on.

At first I got the OS warning and the following message (top left):

gbb.flags is nonzero: 0x00000039
read-only firmware id: Google_Panther.4920.24.21
Active firmware id: Google_Panther.4920.24.21

If I press enter I got a beep and the following message:

WARNING: TONORM prohibited by GBB FORCE_DEV_SWITCH_ON.
read-only firmware id: Google_Panther.4920.24.21
read-only firmware id: Google_Panther.4920.24.21
Active firmware id: Google_Panther.4920.24.21

... but after the next reboot the OS warning still exists.

Disable Firmware Write Protect is still active (screw is removed).

What's wrong?

Thanks

Udo

this has nothing to do with the script, but I'm in a generous mode today.
It's telling you exactly what the issue is - gbb.flags is nonzero, and one of the flags that is set is preventing you from disabling developer mode. Use the script to reset the boot options to the default (which sets gbb.flags to zero), reboot, and you should be able to return to normal/verified boot mode.

danfloss · 2015-03-18, 16:38

(2015-03-18, 05:54)Matt Devo Wrote: script update 03/17/2015:

- update OpenELEC to 5.0.6 (stable, Kodi 14.2)
- added script function to create standalone Kodibuntu install media, using HugeGreenBug's updated Kodibuntu ISO (contains all required kernel/driver updates/fixes)

Note: no firmware-related changes; SeaBIOS datestamps remain 02/26/2015

wonder will this fix the high CPU usage i was having previously with Kodibuntu