[bolmsted]

I'm not sure what I'm running into but I've noticed that I sometimes reboot the chromebox and it hangs on the OpenELEC screen on reboot and I have to physically power it off and then back on. I've setup an OS side NFS mount and installed some addons - one of which needs an OS level share installed instead of having Kodi use one built in and I can see it mounted via ssh.

I'd bet it's hanging on trying to mount the NFS share before the network is up. Do you have the share setup properly to wait for the network before mounting?

Hi Matt

it seems to hang when rebooting the box. When I power on the box from cold it takes a bit of time to come up but it does mount the file system on boot... I'm using the new method for mounting NFS. This is from my Synology running DSM4.3

Code:

OpenELEC:~/.config/system.d # more storage-pulsar.mount
[Unit]
Description=Pulsar nfs mount script
Requires=network-online.service
After=network-online.service
Before=kodi.service

[Mount]
# The share we want mount
What=192.168.1.5:/volume1/pulsar
Where=/storage/pulsar
Options=
Type=nfs

[Install]
WantedBy=multi-user.target
OpenELEC:~/.config/system.d #

OpenELEC:~/.config/system.d # df -h
Filesystem                Size      Used Available Use% Mounted on
devtmpfs                934.5M    136.7M    797.7M  15% /dev
/dev/sda6               242.1M    146.2M     91.9M  61% /flash
/dev/sda7                 8.9G    336.0M      8.5G   4% /storage
/dev/loop0              136.8M    136.8M         0 100% /
tmpfs                   936.3M         0    936.3M   0% /dev/shm
tmpfs                   936.3M      5.7M    930.6M   1% /run
tmpfs                   936.3M         0    936.3M   0% /sys/fs/cgroup
tmpfs                   936.3M      8.0K    936.3M   0% /tmp
tmpfs                   936.3M    252.0K    936.0M   0% /var
/dev/sda12               16.0M      1.4M     14.5M   9% /var/media/EFI-SYSTEM
/dev/sda8                11.5M     24.0K     11.1M   0% /var/media/OEM
/dev/sda1                 1.5G     17.7M      1.4G   1% /var/media/sda1-ata-SanDisk_SSD_U110
192.168.1.5:/volume1/pulsar
                          7.2T      5.3T      1.9T  74% /storage/pulsar
OpenELEC:~/.config/system.d #

EDIT: sorry I put in the mount snippet twice and not the df -h to show it was mounting at boot.

[Matt Devo]

Sorry, that's definitely a question for the OE folks

[VanillaXtract]

I did a complete reinstall and now my HDMI out does not work. I can boot into openelec just fine. But if I plug in a HDMI cable and boot into openelec, it gives some squiggly lines on the TV and the laptop then both go blank. I have to hold the power button down to do a hard reset. I initially had the storage partition set to 1 GB, I then did another restore and changed it to 2 GB.Any suggestions on what is causing this issue?

no idea, but since you're using a ChromeBook (vs ChromeBox) there's no a whole lot I can do for you. Best thing I can suggest is to restore the factory legacy bios, which contains the video bios as well, and might be responsible for the issues you are having.

see: http://www.chromium.org/chromium-os/deve...esn-t-Work

I got a new Chromebook. I ran through your script, same issue. No HDMI out. Restored the original firmware. Ran your script but did ^c when it started checking for a new bios. Now I have HDMI out. My question is that is the original bios fine to stick with? Where does your script get the files from? Should I keep trying new ones and working backwords until I find one that works?

[bolmsted]

One of my coworkers has one of these Wireless Keyboards on his Android box and just wondering if I could use this on OpenELEC + Kodi?
http://www.dx.com/p/wireless-2-4ghz-usb-...LbMAivF_zh

I have an identical looking keyboard branded Rii I8. It works on my intel based hardware so should work on the Chromebox. It even works in the Bios of my Intel hardware, so may work for the chromebox ctrl- key options.

EDIT: the one I have http://www.dx.com/p/genuine-rii-mini-i8-...LbsGMl2M8s

My coworker lent me the keyboard and it is working for me so I ordered it tonite so hopefully DX sends it quickly so for now I have to use xbmc on my phone and I don't want to have to drag my phone downstairs to watch TV all the time. I also ordered an Ortek remote (or at least that is what shows up on Amazon in the comments) that is compatible with the Asus Chromebox according to the wiki as an MCE remote and program it in the Harmony remote and toss the original remote (just the IR sensor needed) to keep the wife happy as she doesn't want to use the keyboard to use the TV. Just good to have keyboard for searching for stuff, etc.

---

Sorry, that's definitely a question for the OE folks

Well I asked there in the openelec.tv forums so see what they say (no bites yet though). Wonder if an addon can crash Kodi/OpenELEC as one of the addons was updated so may try it. I'm gong to try rebooting the Chromebox from Kodi once the wife is done using the TV before I run the addon to see if it is causing the issue as a bit of a process of elimination.

[bolmsted]

If a new version of OpenELEC or XBMC comes out do we need to flash the box again using this script or will it update automatically in place like other Linux distros and patching? Can we backup our setup and restore afterwards if we have to reflash?

[Matt Devo]

I got a new Chromebook. I ran through your script, same issue. No HDMI out. Restored the original firmware. Ran your script but did ^c when it started checking for a new bios. Now I have HDMI out. My question is that is the original bios fine to stick with? Where does your script get the files from? Should I keep trying new ones and working backwords until I find one that works?

ok, then stick with that - I make no promises that any of this will work with the Haswell ChromeBooks, especially not the firmware (which I guarantee 100% will brick them). If the stock legacy BIOS on your ChromeBook is functional (unlike with the Asus/HP ChromeBoxes) then there's no reason to update it.

the firmware files use by my script (both the full coreboot firmware and SeaBIOS payload for the stock firmware) are built by me, and optimized/tested only on the Haswell ChromeBoxes; the Haswell ChromeBooks are different because they have an onboard display and sensors for lid open/shut etc. I have built custom firmware for ChromeBook users who have requested it, though I don't make those available publicly, only upon request, since I can't test them beforehand.

Well I asked there in the openelec.tv forums so see what they say (no bites yet though). Wonder if an addon can crash Kodi/OpenELEC as one of the addons was updated so may try it. I'm gong to try rebooting the Chromebox from Kodi once the wife is done using the TV before I run the addon to see if it is causing the issue as a bit of a process of elimination.

you'll have much better luck asking in the IRC support channel than on the forums.

If a new version of OpenELEC or XBMC comes out do we need to flash the box again using this script or will it update automatically in place like other Linux distros and patching? Can we backup our setup and restore afterwards if we have to reflash?

for a standalone setup, you'll never have to run the script again, unless there is a firmware update that specifically fixes an issue you are having. If it's not broke, don't fix it. OpenELEC will update automatically if you have that option enabled, otherwise you update it like you would on any other PC (which is covered in the wiki)

[bolmsted]

Hi Matt

I switched from WiFi over to wired Ethernet and it seems to boot fairly quickly now and rebooting it doesn't seem to hang. Perhaps the wifi driver takes a while to come up but seems to be better now. Will monitor. Was hoping to free up an Ethernet port on the router but oh well.

[Matt Devo]

that's definitely possible, all my boxes are wired gigE here so I only switch to wifi when someone asks me to test something (eg, throughput)

[-DDD-]

it's a marketing thing, the Celerons have typically used 'Intel HD Graphics' whereas the Core CPUs get a number. From a hardware standpoint, HD4000 (Haswell) is accurate; the only difference between the Celeron and Haswell Core i3/i7 GPUs with the HD4400 GPU is the number of execution units (EUs) and the clock speed.

Marketing or not, there was never an HD4000 for HSW.
HD 4000 is IVB with 16 EUs - HD Graphics (HSW) is 10 EUs
http://en.wikipedia.org/wiki/Intel_HD_and_Iris_Graphics
Where is the Hardware Standpoint where HSW HD is similar to IVB HD4000?
If you say Celeron 2955U have an HD4000, people think this is an IVB GPU and have this Bug for example
https://bugs.freedesktop.org/show_bug.cgi?id=79765
But that's not true, cause Celeron 2955U is an Haswell and have an HD Graphics HSW GPU.

So why don't call it like everyone call it, HD Graphics?
I don't call my i3 3225 an i5 2500 also, although they might be similar.

[Matt Devo]

Marketing or not, there was never an HD4000 for HSW.
HD 4000 is IVB with 16 EUs - HD Graphics (HSW) is 10 EUs
http://en.wikipedia.org/wiki/Intel_HD_and_Iris_Graphics
Where is the Hardware Standpoint where HSW HD is similar to IVB HD4000?
If you say Celeron 2955U have an HD4000, people think this is an IVB GPU and have this Bug for example
https://bugs.freedesktop.org/show_bug.cgi?id=79765
But that's not true, cause Celeron 2955U is an Haswell and have an HD Graphics HSW GPU.

So why don't call it like everyone call it, HD Graphics?
I don't call my i3 3225 an i5 2500 also, although they might be similar.

your arguments here are bizarre, no one is saying that the 2955U has the same GPU as a SB/IVB CPU, nor is there likely to be any confusion to that effect. If that was the case, then Intel saying all Celerons have HD Graphics, regardless of platform/architecture, would be even more confusing - would it not? Regardless, I have clarified the wiki in the hope we can put this issue to rest.

[Matt Devo]

I got a new Chromebook. I ran through your script, same issue. No HDMI out. Restored the original firmware. Ran your script but did ^c when it started checking for a new bios. Now I have HDMI out. My question is that is the original bios fine to stick with? Where does your script get the files from? Should I keep trying new ones and working backwords until I find one that works?

ok, then stick with that - I make no promises that any of this will work with the Haswell ChromeBooks, especially not the firmware (which I guarantee 100% will brick them). If the stock legacy BIOS on your ChromeBook is functional (unlike with the Asus/HP ChromeBoxes) then there's no reason to update it.

the firmware files use by my script (both the full coreboot firmware and SeaBIOS payload for the stock firmware) are built by me, and optimized/tested only on the Haswell ChromeBoxes; the Haswell ChromeBooks are different because they have an onboard display and sensors for lid open/shut etc. I have built custom firmware for ChromeBook users who have requested it, though I don't make those available publicly, only upon request, since I can't test them beforehand.

FYI, I added a proper legacy BIOS (SeaBIOS) for Haswell ChromeBook users, who can now safely use the dual boot features of the script. It's completely transparent, and I'd appreciate it if you could give it a test for me. Just run the script and choose the legacy BIOS update option (#4)

[CaTz]

Hi Matt,

I just got my Asus ChromeBox, does it have the WOL option with your bios?
If so, how can i turn it ON?

[Matt Devo]

Hi Matt,

I just got my Asus ChromeBox, does it have the WOL option with your bios?
If so, how can i turn it ON?

yes, for Ethernet only; you don't need to do anything to turn it on

[Freakshow999]

I just wanted to say a big thank you!

Got my HP ChromeBox a few days ago and just got a chance to mod it last night!
I've put it through it's paces with some of the toughest files I have (VC1 & 7.1 DTS-HD MA about 39Mbps). I am super happy with the results so far.
Only hiccup I have had was not getting audio back up after coming out of suspend which I believe is mentioned somewhere anyway.
I've been back and forth with XBMC for a very long time and was very active in the original ATV1 Moding etc.
I've got my old school hp ir receiver hooked up and working on my universal remote along with my K400 working no problems.
I do home automation, A/V, IT design and installs for a living so I've got a crazy test bed of devices.
I was actually pretty impressed with the FireTV sideloaded with KODI until I ran into the VC1 bug.
I've got a Plex server, Sony Smart Blu-ray, Sony 4k Smart TV, ATV1, ATV 3, Roku 3, FireTV, WDTV Streaming, HTPC, Netgear GTV100 (Google TV Appliance), and now a modded ChromeBox.
All in my test system because I need to know how everything works etc.
I am super happy to have a bootable KODI appliance that will finally play every file I've thrown at it. Now if I can figure out how to marry it to a Roku for the streaming services I would definitely be down to one device to kill them all! lol

[Matt Devo]

I just wanted to say a big thank you!

you're welcome

Only hiccup I have had was not getting audio back up after coming out of suspend which I believe is mentioned somewhere anyway.

check the wiki, there's some notes and a script you can try to force a reset on the audio device upon resume from suspend