Posts: 4,512
Joined: Nov 2008
Reputation:
224
2015-10-10 script update:
- add PXE network boot support as option for standalone firmware
- default to installing latest OE beta/RC (vs latest stable)
- synchronized coreboot and SeaBIOS to latest upstream codebases
Posts: 55
Joined: May 2015
Reputation:
1
Tried to update my firmware but got the following:
3Tfu5W: ./functions.sh: line 49: syntax error: unexpected "("
Any idea?
Posts: 37
Joined: Feb 2015
Reputation:
0
Hi, I have the pulse-eight USB-CEC adapter with an Asus Chromebox. Unfortunately it requires USB power right at boot (before the Chromebox provides it) or it doesn't work right. I have had to add a powered usb hub just to get it to work right. Sometimes the power to the hub doesn't work and I lose CEC functionality. The whole thing would be much more elegant if one of the usb ports could be set up to provide power-while-off. Is there any chance of adding this feature?
Posts: 362
Joined: Jan 2008
Reputation:
2
I just read about usb3 causing interference on wireless devices. Could it be causing problems my friend is having with Openelec, Asus Chromebox and PS4 game controller? Controller connection is a bit unreliable, button presses repeat now and then and so on. There's no bluetooth-devices connected on that chromebox, so is there anything that could fix this?
Odroid C2 running CoreElec
Posts: 10
Joined: Apr 2014
Reputation:
0
Milky1
Junior Member
Posts: 10
Thanks Matt for the excellent script and your relentless work answering queries on this forum!
I just wanted to put an FYI for anyone who has a similar problem to me.
I have an ASUS CHROMEBOX-M004U Desktop hooked up to a new Samsung 4k JU6400
It will ONLY work if device type on input is set to PC and UHD Color is set to ON
On my model that can only be HDMI 1, on better models UHD color is available on all inputs
So basically no handshake issue etc, just correct set up, just wanted to share.
Posts: 1
Joined: Oct 2015
Reputation:
1
2015-10-22, 05:03
(This post was last modified: 2015-10-22, 06:36 by red_z.)
Atmos 7.1.4 passthrough working on Dell Chromebox!
I've been searching for several days for a Kodibuntu/OpenElec solution that will allow Atmos, TrueHD, HD Audio 7.1 passthrough to an AVR for decoding. After much searching and trials on various boxes, I was finally able to get this to work using OpenElec on a Dell Chromebox. I used the method outlined here (which is very easy to follow) and used the OpenElec dual-boot method. I am now able to playback all of my high bit-rate mkv movies and the AVR receives the audio as bitstream Atmos and even displays Atmos on the receiver indicating the stream is coming through properly.
Many thanks to all who have pointed me in the right direction. For anyone else trying to do this (and I know there are many that I've seen in various forums), I hope this helps. For what its worth, I tried several other solutions before landing here and this was the only one that came through correctly. This includes trying the Dual-Boot Ubuntu method on the same Chromebox and running Kodi 15.2 RC. This last solution appeared to not recognize the HDMI correctly as it would only output PCM and not the raw passthrough audio. In fact it only gave me a single option to select Passthrough (which didn't seem to work) and did not expose the other options you usually get on passthrough - like TrueHD capable receiver, DTS-HD capable receiver, etc. So the same box with Kodibuntu wouldn't work, but with OpenElec worked flawlessly right out of the box.
I also tried other Kodio 15.2 solutions on other PCs with Windows & Ubuntu and none of those seemed to work correctly for me. Those may have been due to the hardware that I was using that might have been dated.
This appears to be an amazing solution for a low-cost, simple, fast-booting HTPC. High bit-rate mkvs are playing smoothly and with full Atmos audio with no stuttering, hiccups, etc. Been looking for something like this for a very long time... :-)
Posts: 967
Joined: Nov 2006
Reputation:
27
Be careful upgrading to or installing Ubuntu 15.10 on the chromebox. It immediately kernel panics upon boot. After some investigation, this seems to be a known issue with 4.2 and chromebooks (and now, chromeboxes also). To fix it, go into the boot menu and boot your old kernel, 3.19.
Posts: 4
Joined: Oct 2015
Reputation:
0
2015-10-25, 23:46
(This post was last modified: 2015-11-03, 03:44 by toyopl.)
-Microsoft all-in-one media keyboard (wireless)
-IRainy 6 axis (wireless)
-Corsair Vengeance K70 (wired)