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
Tried to update my firmware but got the following:
3Tfu5W: ./functions.sh: line 49: syntax error: unexpected "("
Any idea?
(2015-10-15, 02:09)Matt Devo Wrote: [ -> ] (2015-10-14, 23:00)Karnis Wrote: [ -> ]Steve Miller_Fly Like An Eagle_DTS 5.1
I'm able to reproduce that here, and unfortunately it's no better in OE 5.95.5/Kodi 15.2 RC, where it's simply marked as unplayable and skipped. Even encoding as FLAC as suggested elsewhere doesn't help. Seems like the DTS header isn't being recognized/respected.
Thanks for checking it out, Matt.
I have tried for quite a while to solve this by myself using this thread and the wiki, but have got stuck in the process. I have a Asus chromebox CN60-M1097, which is supposedly the same as the M004U. I am trying to do a single boot to openelec.
The text is on left side of my tv screen is hidden, but the thread provide enough information to choose the options as I progressed. I successfully got to the point where the openelec media was applied to the USB stick. I get this far:
on of OpenElec install media is complete.
eboot. press [ESC] at the boot menu prompt. Then slect your USB/SD device from the list
But not sure how to get to the boot prompt again as seem to go back to chrome? Or does this indicate that the USB device is not adequate because I cannot get to the prompt? Either way I am now stuck and not sure what to do next. Any guidance is welcomed.
(2015-10-15, 10:54)wwessel Wrote: [ -> ]Tried to update my firmware but got the following:
3Tfu5W: ./functions.sh: line 49: syntax error: unexpected "("
Any idea?
runs fine here, which makes me think you're trying to run it from OpenELEC, which doesn't work, and why there's a special firmware update script just for OE. Read the OP.
(2015-10-15, 14:40)RMP888 Wrote: [ -> ]I have tried for quite a while to solve this by myself using this thread and the wiki, but have got stuck in the process. I have a Asus chromebox CN60-M1097, which is supposedly the same as the M004U. I am trying to do a single boot to openelec.
The text is on left side of my tv screen is hidden, but the thread provide enough information to choose the options as I progressed. I successfully got to the point where the openelec media was applied to the USB stick. I get this far:
on of OpenElec install media is complete.
eboot. press [ESC] at the boot menu prompt. Then slect your USB/SD device from the list
But not sure how to get to the boot prompt again as seem to go back to chrome? Or does this indicate that the USB device is not adequate because I cannot get to the prompt? Either way I am now stuck and not sure what to do next. Any guidance is welcomed.
the easiest and correct solution is to disable overscan on your TV so that you can see WTF you are doing. Googling your TV model/series should tell you how to do that. Barring that, hook the thing up to a computer monitor which doesn't overscan. I highly recommend you fix this before continuing and not try to navigate blindly.
btw, the text reads:
Quote:Creation of OpenELEC install media is complete.
Upon reboot, press [ESC] at the boot menu prompt, then select your USB/SD device from the list
If you have not already done so, run the 'Install/update: Custom coreboot Firmware' option before reboot.
Press [Enter] to return to the main menu
(2015-10-15, 16:48)Matt Devo Wrote: [ -> ] (2015-10-15, 10:54)wwessel Wrote: [ -> ]Tried to update my firmware but got the following:
3Tfu5W: ./functions.sh: line 49: syntax error: unexpected "("
Any idea?
runs fine here, which makes me think you're trying to run it from OpenELEC, which doesn't work, and why there's a special firmware update script just for OE. Read the OP.
Ah, thanks. Yes, I didn't catch the right one...
(2015-10-15, 05:19)Matt Devo Wrote: [ -> ] (2015-10-15, 04:27)RichAggie Wrote: [ -> ]It seems to be an issue with the TV. The chromebox boots fine on other TV's. I have have a Vizio P70 (same as someone earlier in this thread who also had an issue). Funny thing is it has worked great for months on this TV. I've tried all the HDMI inputs. I don't know what to try next.
so wait, the box works fine on other displays, just not your 4K Vizio? In that case, the problem and solution are the same as I posted earlier as well - just set the output resolution and refresh rate via an autostart script.
Are you talking about the code below? Forgive my ignorance, but I am still learning all this. Where do I actually put that?
#!/bin/sh
xrandr --output HDMI1 --mode 1920x1080 -r 60
(2015-10-16, 03:52)RichAggie Wrote: [ -> ]Are you talking about the code below? Forgive my ignorance, but I am still learning all this. Where do I actually put that?
#!/bin/sh
xrandr --output HDMI1 --mode 1920x1080 -r 60
correct. In an autostart script:
http://wiki.openelec.tv/index.php?title=Autostart.sh
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?
(2015-10-20, 01:03)liebezeit Wrote: [ -> ]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?
I've looked into it but not been able to figure it out. Your best bet is to use the setup described in the wiki
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?
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.
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... :-)
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.
-Microsoft all-in-one media keyboard (wireless)
-IRainy 6 axis (wireless)
-Corsair Vengeance K70 (wired)