[knives of ice]

ok i have everything up and running awesome.

one thing with my nuc that i'm missing - it had two hdmi out ports so i connected to two displays, one upstairs and one down.

can i use a displayport to hdmi adaptor to send a 2nd hdmi signal downstairs? anyone else doing a similar setup successfully?

also, is there ANY benefit at all to adding the max 4 gb of ram to the Hp chromebox at all? i fogot to cancel my ram order but i can easily send it back to Amazon

man, this thing is so much faster than the entry level Nuc i had just wish i would have set it up earlier!

[Matt Devo]

Yes, both video outputs can be used simultaneously, but some passive DisplayPort to HDMI adapters are problematic (but usually when used alone, not in a dual output situation).

Also, I told you so ;-)

[Arse4life]

Installing dual boot as I type this. I was wondering when I'd get to the point of choosing between beta and stable build during installation process. N!

Brilliant Matt!

[Matt Devo]

Start of 2nd stage, when it actually installs OpenELEC (as opposed to the 1st stage, where it's just resizing partitions)

[knives of ice]

Matt, can you see any benefit at all to put this ram i have into the HP chromebox? if no, i'll just return it. thanks

[Matt Devo]

Matt, can you see any benefit at all to put this ram i have into the HP chromebox? if no, i'll just return it. thanks

on the HP, no. On the others an additional stick of ram would net you the benefits of dual channel memory, but you don't get that on the HP, and OpenELEC/Kodi won't use more than 1GB even

[liebezeit]

A warning to all--if you update to Linux 3.19.0-18, audio over HDMI will stop working.
I used Grub Customizer to go back to loading 3.19.0-16 for now.
(This is on ubuntu, the bug is here: https://bugs.launchpad.net/ubuntu/+sourc...ug/1457369)

[FreakinSyco]

It's likely booting but you're not seeing any output. Check your router for an IP assignment and then try to ssh in

I played around with xrandr settings in my autostart.sh last night. Still no booting. ChromeBox doesn't get to the point of initiating the network either. I did notice the fan on the unit will run up very high when stuck in the not booting freeze.

Xrandr settings in autostart.sh are working because now once I do my HDMI unplug, reboot, connect HDMI, I get 1080p60 when before it would renegotiate at 2160p30 on HDMI5.

Also I managed to get some display on ports 1-4 by SSHing in after booting and manually xrandr to 1080p60. It appears to auto negotiate 1080p120 or 1024x768 on ports 1-4. I saw both happen, but didn't nail down why I got one or other other after a reboot and HDMI connection. But I still couldn't get video playback on HDMI 1-4. I have Kodi set to framerate match to video and once video playback starts (was watching 60hz news) it went black again.

On HDMI1-4 it appears if I reboot with HDMI disconnected then connect HDMI after enough time that my autostart.sh xrandr settings have no effect. I'm guessing the reconnection of the HDMI cables causes a renegotiation of resolution and refresh rate redoing the settings I had set in the autostart.sh.

For some reason I enjoy troubleshooting stuff like this, but it sure drove my wife up the wall. She just wanted to watch the news lol.

[Matt Devo]

This is what I used on my friend's box:

Code:

#!/bin/sh
xrandr --output HDMI1 --mode 1920x1080 -r 60

[thecolin]

A big thank you to everyone who set this up. Just about everything is working perfectly on my Asus chromebox. I'm only mildly tech-savy and I've had almost no problems.

One issue that I'm having after a week with my setup is that the wireless seems to turn off by itself and I need to go in and turn it back on. It doesn't seem to happen consistently, just after the system has been shut off for a while. If I just reboot, the wireless appears to stay connected. Looking around at similar problems on other systems it looks like this might be a power management issue? Looking in the power management menu though, I can't see anything that might be relevant.

The only settings I've changed so far are the recommended settings from the tutorial and setting up access for yatse. As well as reserving an ip address on my router.

This problem is a bit annoying since I'm using a wireless remote, I have to connect a mouse to turn the wireless back on every time I turn the system back on. (not the end of the world I know, but annoying! )

Has anyone with an Asus chromebox or any other system had a similar problem?

[Matt Devo]

Can't say I've seen that (but I use a wired connection) - assume you are running OpenELEC? Stable or beta?

[thecolin]

Yes I'm running OpenELEC 5.95.1.

Though when I booted up now to check the version, I had the mouse already plugged in but it didn't work until I rebooted... in my limited experience usb ports turning off might also be a power management issue?

[Matt Devo]

Yes I'm running OpenELEC 5.95.1.

Though when I booted up now to check the version, I had the mouse already plugged in but it didn't work until I rebooted... in my limited experience usb ports turning off might also be a power management issue?

haven't seen that either, but haven't done much testing with a mouse on OE 5.95.1. Could be due to changes in the kernel?

[FreeMan xbmc]

I've been happily running standalone Kodibuntu 14.0 on my ASUS Chromebox since around Nov '14, so thank you very much, Matt!

I decided that it was time to update to 14.2, and that's when things went haywire. In the process of doing so, it seems that I ran out of space on my 16GB drive part way through the upgrade:

Code:

xbmc@xbmc:~$ df -h
df: â/run/user/107/gvfsâ: Permission denied
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda1        13G   13G     0 100% /
none            4.0K     0  4.0K   0% /sys/fs/cgroup
udev            924M  4.0K  924M   1% /dev
tmpfs           188M  804K  187M   1% /run
none            5.0M     0  5.0M   0% /run/lock
none            938M  4.0K  938M   1% /run/shm
none            100M  4.0K  100M   1% /run/user
overflow        1.0M  1.0M     0 100% /tmp

I'm now stuck with a box that boots to a Ubuntu desktop login screen, but won't start Kodi. I cannot login to the desktop at all, but I can still SSH in from another machine.

I posted in this thread about it, and that's where the out of disk space issue was discovered, however, that thread seems to have run out of steam. You can read the short saga there to see all the steps I've taken in an attempt to get things working again.

At this point, I have a non-funcitonal Kodi box and a very unhappy family. I'd be happy to just return to 14.0 and stay there for a while, if necessary, but, as noted in my other thread, uninstall procedures don't seem to be working.

• Should I return to the OP here to reinstall from scratch?
  • if so, I presume I should use one of the curl commands to download the menu, then use option 8 for a fresh install
• Is there a directory that I can purge to free up some space so I can get a working machine?
  
• Since I have over 1500 movies and 5000+ TV episodes, is the database chewing up all that disk space?
  • Would I be better off moving to a remove SQL database on my file server (where all the actual shows reside)
    
  • Would I be better off buying a larger m.sata drive and reinstalling the whole thing on that?
    
  • If I buy a new drive, what size would be recommended? I don't want to run out of space again, but I'm not up for massive overkill, either.

Thanks again for a great tool, and thanks for helping me through this issue!

[Matt Devo]

• Should I return to the OP here to reinstall from scratch?
  • if so, what step should I start from
• Is there a directory that I can purge to free up some space so I can get a working machine?
  
• Since I have over 1500 movies and 5000+ TV episodes, is the database chewing up all that disk space?
  • Would I be better off moving to a remove SQL database on my file server (where all the actual shows reside)
    
  • Would I be better off buying a larger m.sata drive and reinstalling the whole thing on that?
    
  • If I buy a new drive, what size would be recommended? I don't want to run out of space again, but I'm not up for massive overkill, either.

Thanks again for a great tool, and thanks for helping me through this issue!

I'd login locally and copy the kodi userdata folder to USB, then reinstall Ubuntu from USB (or upgrade the SSD - they are cheap - and reinstall Ubuntu) the restore your Kodi userdata.

I doubt it's your database that's the issue, but even if it were, moving it to the NAS would still require local thumbnails (unless you remapped those as well) which are likely the bigger space hog. I'd probably just get a 64/128GB drive and not worry about it, or if you don't need a full Linux OS, run something with a much smaller footprint like OpenELEC.

remember, now that you've installed the custom firmware, your ChromeBox is just a regular PC (albeit one with a ultra-fast booting firmware) - so (re)installing an OS is as simple as booting a USB