[naloj]

There's an issue open about the network droppages:

https://github.com/OpenELEC/OpenELEC.tv/issues/3873

Pretty sure it is DHCP related. I just noticed that I have a 10 minute lease time and that coincided with the timing of some of the network drops.

What about not being able to get a wired connection to work that must be hardware no? I will try a static ip today see if that helps. Lease time is 2 hours which seems about the time till it dies.

Sorry, my post wasn't a direct response to you, more for other people a couple pages back that were also having network dropouts similar to my own.

If you're not getting the connection to work in ChromeOS either then it's most likely not related to the OpenELEC issue. That is unless your DHCP server has some sort of issue providing a lease to your machine.

[nickr]

There isn't much need to have a short lease time. My router defaulted to 12 hours, but there is no reason not to make it longer - unless there are frequent changes to your infrastructure that you want to propagate quickly.

[jskala]

There's an issue open about the network droppages:

https://github.com/OpenELEC/OpenELEC.tv/issues/3873

Pretty sure it is DHCP related. I just noticed that I have a 10 minute lease time and that coincided with the timing of some of the network drops.

What about not being able to get a wired connection to work that must be hardware no? I will try a static ip today see if that helps. Lease time is 2 hours which seems about the time till it dies.

Sorry, my post wasn't a direct response to you, more for other people a couple pages back that were also having network dropouts similar to my own.

If you're not getting the connection to work in ChromeOS either then it's most likely not related to the OpenELEC issue. That is unless your DHCP server has some sort of issue providing a lease to your machine.

No problem but you gave me at least a direction to my wireless issue. Which I believe is the DHCP timing seems right. Now to figure out my wired issue.

[A2K81]

I haven't updated anything on my my Asus Chromebox (standalone) in a while. I tried to update from Gotham 13.2 to Kodi. I followed the instructions on the main page (SSH, enter "curl -L -O http://goo.gl/HSZer4" and then "bash HSZer4") and although I think it worked, the last message in Putty said "Please power cycle your ChromeBox to complete the update."

I don't know what this means...I tried rebooting and turning off the power, but I still have Gotham 13.2 and OpenELEC 4.2.1. I tried doing the SSH steps over again, but now it says I already have the latest firmware...

I've looked through the forum and the wiki, but I can't figure out what I'm doing wrong (or not doing). I obviously have no idea what the hell I'm doing lol. Can you help me out?

Thanks!

[desperado77]

@A2K81

You need to Manually Update OpenELEC 4.x to 5.0 i think what you did is the chromebox firmware update.

From the wiki: http://wiki.openelec.tv/index.php/Updating_OpenELEC
The automatic update function will not make a major update from 4.0/4.2 software towards 5.0. Major updates are not done because major steps in versions can lead to unstable setups as too many settings have changed between the versions. You can update manually though.

Please be sure to backup all your settings before the update and follow the manual update instructions given above.

If you do want to go ahead with the upgrade, doing a -full- backup of your OpenELEC setup first is recommended at all times. Use the Backup/Restore tool in the OpenELEC Setting addon, and place the backup file in a secure location. That means NOT on the same OpenELEC htpc you are making the backup of.

[A2K81]

@A2K81

You need to Manually Update OpenELEC 4.x to 5.0 i think what you did is the chromebox firmware update.

From the wiki: http://wiki.openelec.tv/index.php/Updating_OpenELEC
The automatic update function will not make a major update from 4.0/4.2 software towards 5.0. Major updates are not done because major steps in versions can lead to unstable setups as too many settings have changed between the versions. You can update manually though.

Please be sure to backup all your settings before the update and follow the manual update instructions given above.

If you do want to go ahead with the upgrade, doing a -full- backup of your OpenELEC setup first is recommended at all times. Use the Backup/Restore tool in the OpenELEC Setting addon, and place the backup file in a secure location. That means NOT on the same OpenELEC htpc you are making the backup of.

Thanks for the response. Yes, I did the firmware update using the EZ Setup Script instructions I referred to originally. I thought that updating the coreboot Firmware (standalone) would automatically update OpenELEC and upgrade to Kodi. If I update OpenELEC manually as per the wiki instructions, will I then have the latest version of Kodi on my Chromebox?

[ozkhan1]

Quick question.. what brand chromebox is best for openelec? I heard some brands are better than others

[Matt Devo]

Thanks for the response. Yes, I did the firmware update using the EZ Setup Script instructions I referred to originally. I thought that updating the coreboot Firmware (standalone) would automatically update OpenELEC and upgrade to Kodi. If I update OpenELEC manually as per the wiki instructions, will I then have the latest version of Kodi on my Chromebox?

I'm not sure how I can make it more clear in the wiki/OP that the firmware and OS are completely separate and unrelated. There are separate wiki sections for updating the firmware and updating OE. what else do I need?

Quick question.. what brand chromebox is best for openelec? I heard some brands are better than others

Asus. The wiki lists all the differences between the 4.

[A2K81]

Thanks for the response. Yes, I did the firmware update using the EZ Setup Script instructions I referred to originally. I thought that updating the coreboot Firmware (standalone) would automatically update OpenELEC and upgrade to Kodi. If I update OpenELEC manually as per the wiki instructions, will I then have the latest version of Kodi on my Chromebox?

I'm not sure how I can make it more clear in the wiki/OP that the firmware and OS are completely separate and unrelated. There are separate wiki sections for updating the firmware and updating OE. what else do I need?

Honestly man, you probably can't. The problem (for me at least) is that there is a lot of info out there and, frankly, even reading that the firmware and OS are different doesn't really compute to a basic user (i.e. noob) like me.

In any event, sorry for asking a dumb question and thanks for all your contributions

[bhampton]

There needs to be a way to send coffee wirelessly to anyone who reads the wiki for the first time. That may be the solution. Sounds like a possible future tech.

I think if there's a problem,... it's to direct... most people need more pictures and hand holding these days. (Not kidding really... not kidding.) I used the wiki a few times and everyone has hard time giving anything the right amount of attention these days.

[wackid]

I think the Wiki is great and read it several times.
It's the only way to learn about your device and get the most out of it.

[Soli]

I wanted to chime in with my experiences, but accidentally posted in the wrong thread, so I'm gonna repost it:
Got a hp chromebox, that I first tried Linux Mint on, then I got fed up with all the bloat and tried out Kodibuntu instead.
Running with a PS3 BD Remote and it works more or less perfectly. I didn't want to go the OE route because I don't want to depend on OE, and besides I wanted a normal desktop just in case, plus I wanted to use Netflixbmc.
I haven't read the whole thread, but it seems noone has really posted a step by step using Kodibuntu on a Chromebox.
Here are the steps I took. If someone are interested I could be more specific.

1. Installed Kodibuntu from a USB stick.
2. Apt-get update && apt-get upgrade.
3. Installed Google Chrome and uninstalled Chromium.
4. Added the tear free option in /etc/X11/xorg.conf.d/20-intel.conf so that playing videos in a normal browser wouldnt tear.
5. Installed gnome-terminal to since the xterm and uxterm are horrible. (and is only dependent on an extra library, so no bloat) Made a shortcut in the startmenu for gnome-terminal since installing gnome-terminal didnt populate the start menu automatically.
6. Added the RGB FIX to the startup of lightdm at /etc/lightdm/lightdm.conf. made a script in my home folder (and chmod +x) named rgbfix.sh with

Code:

#!/bin/sh
xrandr --output HDMI1 --set "Broadcast RGB" "Full"

added the line

Code:

display-setup-script=/home/xxx/rgbfix.sh

to lightdm.conf

7. Installed blueman and paired my PS3 BD Remote. (use the "trust" option or else blueman will ask for a pin, which will fail because the BD Remote does not use a pin code). Blueman show up in the start menu and is a nice gui to pair bluetooth devices.
8. We need a patched bluez to use all the buttons on the ps3 remote so i installed a patched version (only a patched main bluez package is needed).
9. Added the PS3 BD REMOTE specific config file to /etc/bluetooth/input.conf (remember the timeout setting is in seconds instead of minutes when using the patched version) I use timeout of 25 seconds. No need to fickle anymore with bluetooth after this, it reconnects automatically at boot.

10. To get sound in the normal desktop environment, I used alsamixer to set the default audio device to my USB soundcard and unmute it. You can also use /etc/asound.conf. Or you might not even need to do anything if you're using HDMI audio. (unless analog output is default).

11. Installed Intel Graphics Installer 1.07 package (google it), and then you have to run the actual program which then installs some Intel drivers. You also have to manually install apt-transport-https or the package will fail. This speeds up html5 in google chrome (doesn't seem to do much for flash though). Now I can watch Netflix in 1080p in Google chrome without stuttering, which is not bad considering its software decoding on a 1.4ghz dual core Celeron.

12. Installed the Linux 3.18.5 kernel image and kernel headers.

Reboot.
I think that was it. It works perfectly!

[bhampton]

Soli,

Does this result in Vaapi hardware acceleration or something else like DVXA or ...??... Could you check if you don't mind? Just look under the acceleration tab in video playback expert settings.

I have Kodi running on 3 very different computers... A PC, a Mac, and a Chromebox... but the OpenElec using Vaapi hardware acceleration is giving me problems I would rather not have.

edit - Never heard of RGB FIX option.... I do rely on the the Broadcast RGB Full flag.

-Brian

[fritsch]

You have issues with exactly one kind of file - VC1. All the rest is perfectly fine. So keep the chapel in the village, please.

[bhampton]

You have issues with exactly one kind of file - VC1. All the rest is perfectly fine. So keep the chapel in the village, please.

[trying to explain my silly lack of patience]

You're right, I'm being silly and sound ungrateful. Thank you again specifically for your help. I run Kodi on multiple machines so I'm open to maybe a different config just working better for me.

For example, I was very interested in the fork someone made with 3D LUT support (which is likely left behind as it was not part of current code) as that could really help with my projector calibration but to run that I would NEED to likely swap out my current Chromebox for a hefty PC. So,... I'm just open to maybe changing things up if it helps.

[/trying to explain my silly lack of patience]