[Reb313]

yes, as per the wiki:

Is that different than updating the Coreboot ?

coreboot is the firmware (BIOS); the kernel is the "core" of the OS. So yes

k. I'm not seeing anything in the wiki on how to update that.

[Matt Devo]

coreboot is the firmware (BIOS); the kernel is the "core" of the OS. So yes

k. I'm not seeing anything in the wiki on how to update that.

because it's specific to the OS you are running (eg, Ubuntu), not to the ChromeBox. And since the latest kernel version changes regularly, providing explicit instructions with download links etc would be pointless. So I just put the min recommended kernel version (3.18.4), it's up to you to figure out how to install it (or something newer) on whatever OS you are running.

[Reb313]

coreboot is the firmware (BIOS); the kernel is the "core" of the OS. So yes

k. I'm not seeing anything in the wiki on how to update that.

because it's specific to the OS you are running (eg, Ubuntu), not to the ChromeBox. And since the latest kernel version changes regularly, providing explicit instructions with download links etc would be pointless. So I just put the min recommended kernel version (3.18.4), it's up to you to figure out how to install it (or something newer) on whatever OS you are running.

Kk. makes sense.

Thanks!

Edit:
followed this guide and now I'm on 18.3

http://www.linux.com/community/blogs/133...peppermint

[Matt Devo]

As I mentioned above and in the wiki, 3.18.4 is the min recommended since that's when the Intel GPU fix was merged in.

[DominicQc]

Dear Matt and all,

I tried to follow the instructions from this thread to install a dualboot set-up to my HP Chromebox (ChromeOS + OpenELEC). Unfortunately I am running into some trouble and I hope somebody can hep me..
I have to say that I am new to LINUX and to this forum so forgive me if anything is unclear in my explanation.

Basically, I followed all the instructions to prepare the chromebox, I login with user Chronos and did the installation which seemed successful. Then as recommended I changed the boot time to 1 sec and the default boot to OpenELEC. After re-booting for the first time I got to this screen and the booting is stuck there:

_________________________________________________
SeaBIOS (version -20140706_180417-build120-m2)

Press ESC for boot menu.

Booting from Hard Disk...
early console in decompress_kernel
KASLR using RDRAND...

Decompressing Linux... Parsing ELF... Performing relocations... done.
Booting the kernel.
_________________________________________________________

Then nothing happens and it stays stuck there.
I tried to hit ESC in many different ways during booting but canno't access the boot menu.
Then I re-booted (with the reset button pushed) and re-installed chrome (recovery mode) from an USB device.
(Not sure if that was a good idea or not..)
When rebooting I still get the the exact same screen.

Anybody has some advice on how to fix this?
How can I access the boot menu?

Thank you very much in advance,

Dominic

[Matt Devo]

Dear Matt and all,

I tried to follow the instructions from this thread to install a dualboot set-up to my HP Chromebox (ChromeOS + OpenELEC). Unfortunately I am running into some trouble and I hope somebody can hep me..
I have to say that I am new to LINUX and to this forum so forgive me if anything is unclear in my explanation.

Basically, I followed all the instructions to prepare the chromebox, I login with user Chronos and did the installation which seemed successful. Then as recommended I changed the boot time to 1 sec and the default boot to OpenELEC. After re-booting for the first time I got to this screen and the booting is stuck there:

yes, that's what happens when you change the boot options before completing the 2nd part of the dual boot setup, and why the instructions are explicit about not doing so

Then I re-booted (with the reset button pushed) and re-installed chrome (recovery mode) from an USB device.
(Not sure if that was a good idea or not..)
When rebooting I still get the the exact same screen.

Anybody has some advice on how to fix this?
How can I access the boot menu?

Thank you very much in advance,

Dominic

before the black SeaBIOS boot screen appears, press [CTRL-D] to boot ChromeOS (this may mean doing it before your screen initializes). Download/run the script, and set the boot options back to the default. Then, re-run both stages of the dual boot setup as per the instructions in the first post. Reboot and boot OpenELEC manually ([CTRL-L] on dev boot screen) to ensure everything works properly. Reboot and boot into ChromeOS, and re-run the script to set the boot options the way you want them.

[DominicQc]

Dear Matt and all,

I tried to follow the instructions from this thread to install a dualboot set-up to my HP Chromebox (ChromeOS + OpenELEC). Unfortunately I am running into some trouble and I hope somebody can hep me..
I have to say that I am new to LINUX and to this forum so forgive me if anything is unclear in my explanation.

Basically, I followed all the instructions to prepare the chromebox, I login with user Chronos and did the installation which seemed successful. Then as recommended I changed the boot time to 1 sec and the default boot to OpenELEC. After re-booting for the first time I got to this screen and the booting is stuck there:

yes, that's what happens when you change the boot options before completing the 2nd part of the dual boot setup, and why the instructions are explicit about not doing so

Then I re-booted (with the reset button pushed) and re-installed chrome (recovery mode) from an USB device.
(Not sure if that was a good idea or not..)
When rebooting I still get the the exact same screen.

Anybody has some advice on how to fix this?
How can I access the boot menu?

Thank you very much in advance,

Dominic

before the black SeaBIOS boot screen appears, press [CTRL-D] to boot ChromeOS (this may mean doing it before your screen initializes). Download/run the script, and set the boot options back to the default. Then, re-run both stages of the dual boot setup as per the instructions in the first post. Reboot and boot OpenELEC manually ([CTRL-L] on dev boot screen) to ensure everything works properly. Reboot and boot into ChromeOS, and re-run the script to set the boot options the way you want them.

Just tried that and it worked like a charm!!
My dual boot set-up is up and running
If I may, I would advise to mention in the tutorial that you need to reboot once after the second part of the installation before changing the boot options.
I saw a warning message saying that you need to complete the second part of installation before changing that option but to be honest I thought it was completed already (without rebooting..)

Anyhow thank you very much Matt for your quick support!

[daan1]

Hi,

For some reason my chromebox lost its lan connection.
I already restarted everything and switched cables but no luck so far.
it is running openelec 5.0.2
I was wondering this is a known issue ?

I wanted to reinstall openelec to solve this problem but somehow i cannot get into the boot options either.
I need to hit esc at boot am i right ?
I have no idea what to do now, any help would be great!


Thanx

[movie78]

My ChromeBox crash and now all i get is a boot screen then black screen...

Any help..

[Matt Devo]

Hi,

For some reason my chromebox lost its lan connection.
I already restarted everything and switched cables but no luck so far.
it is running openelec 5.0.2
I was wondering this is a known issue ?

not a known issue with the ChromeBox firmware, hardware, or OpenELEC itself to my knowledge

I wanted to reinstall openelec to solve this problem but somehow i cannot get into the boot options either.
I need to hit esc at boot am i right ?
I have no idea what to do now, any help would be great!

With your USB install media plugged in, power on, then hit ESC. If you're not getting the 'Press ESC for boot menu prompt,' then there's an issue with the install media and/or the USB stick itself.

My ChromeBox crash and now all i get is a boot screen then black screen...

Any help..

sounds like an OpenELEC booting issue, not a ChromeBox one. Try the OpenELEC IRC chat support.

[Mark the Red]

"XBMC" was working great for a while, then I saw there was this new Kodi kid on the block.

Updated the Core Boot firmware (hadn't done it for a while), manually updated to Kodi and works great.

My reading on the bug fixes relevant to me was that:

(a) Hardware Accelleration now works for all video formats (no more software accelleration)
(b) h.265 codec now works
© fast forwarding / rewinding over wifi no longer takes forever.

Maybe this is pure anecdotal on my end.

Great work Matt! Appreciate the awesome HTPC! Don't know what they pay you at your day job, but whatever it is, it isn't enough!

[movie78]

Can anybody suggest a M SATA Hard drive for my ChromeBox

30 GB
32 GB
or 64 GB

Thanks!

[Matt Devo]

Can anybody suggest a M SATA Hard drive for my ChromeBox

30 GB
32 GB
or 64 GB

Thanks!

no, because the ChromeBox doesn't use a M.SATA drive; as the wiki says, you need a 42mm length M.2 SATA drive. I'd use one from Transcend rather than MyDigitalSSD, as the later seems to have a higher failure rate.

[sunflashx]

I had troubles with buffering on any high bit rate content over my local network. My previous popcorn hour A200 ran flawless for all content and the ChromeBox had the same issue with both SMB and NFS file shares, so I'm mostly sure it's not the network.

Option 4 below fixed it for me. I'm not entirely sure why it wouldn't be noted in the ChromeBox wiki, when we're talking about a specific piece of hardware, they should all behave the same, unless it really was some sort of network problem. At any rate, I don't see why you wouldn't always want in memory caching to be as aggressive as possible. I'm open to correction if there's a reason not to.

http://kodi.wiki/view/Video_cache

[nickr]

It is probably not in the chromebox page on the wiki because no one has seen the need. Frankly I think it is more likely to be your network, as most people don't have these problems.

Edit: of course anyone with an account can add to the wiki, so you could always add a link to the buffering howto page in case anyone else has a screwed up network.