[wizziwig]

I'm a new Asus 2955u Chromebox user and just installed the latest standalone OE Helix nightly beta (10/30/14). I primarily watch recordings made by my TV tuner. Most of them are ATSC 1080i @29.97 interlaced video. When I select the most advanced hardware accelerated de-interlacing mode available: "VAAPI Motion Compensated", the Chromebox will hang after a few minutes of playback. This also happens with 1080i @29.97 Blu-Ray rips such as music concerts.

Is this a known issue? To verify that it was not an openelec bug, I ran the same build on my desktop haswell (4770k) and did not get any hangs with the exact same settings and video files. I know about the work-around of using software de-interlacing but I was hoping to use the higher quality and lower CPU usage HW modes.

[Matt Devo]

this thread is geared towards support for running the setup script / getting things installed, not 'I'm having issues running bleeding edge/nightly alpha builds' . Your best bet is either on the OpenELEC forums where they have discussion threads for these builds, or the deinterlacing thread pinned in the Linux section here.

[fritsch]

It's nothing we can do about, the real bug is somewhere in the linux kernel. It also happens with vanilla 13.2 version and new kernel in "progressive" only mode ... see the thread you linked.

[bobbyhawks]

Hi there,
Great forum,
Just purchased the HP chrome box and followed the instructions for installing dual boot with openelec.
I Removed the write-protect screw but still I am getting a message that write protect is enabled.
Any ideas?
Thanks a lot

I had the exact same thing happen to me last night. I ran through the script twice (successfully), and when I tried to select the boot options, nothing happened. I selected the boot options (#3) again, and I got the write protect language. I ran the shell command suggested earlier, and it was clear that the system thought the screw was still in there. I re-opened the box to make sure I didn't remove the wrong screw and closed it again without removing anything new. I re-booted, re-ran the script, and everything worked fine. The only possible difference is that I stuck the screwdriver in the empty screw slot (gently) to make sure there wasn't anything crazy like a metal schard I couldn't see, even though I know that shouldn't make a difference. I'm guessing it was more the reboot that cleared things up than me re-opening the box, but it is possible that there was something else loose in the box I never noticed.

[TychoCaine]

Hi everyone,

Awesome script Matt, thanks a bunch for all the hard work, especially the additions to the chromebox section of wiki that I assume were all culled from this thread.
I have read through the thread in detail and after following all the instructions have a perfectly working standalone openelec asus chromebox.
I am however troubleshooting a couple of minor issues and I wondered if anyone could shed any light or point me in the right direction for further troubleshooting.

1. I have an xbox 360 wired gamepad controller plugged in but openelec does not seem to recognise it. I have confirmed I have gamepads enabled in the XBMC options and everything I've read seems to suggest the driver is a default in the current build of OE but my install doesn't seem to load it and the controller isn't listed when I run any diagnostic utilities. Stupid question but does the build of openelec installed by the script include the driver for the 360 controlpad? If no, how would I install it? If yes, any ideas where I can look for further troubleshooting on this?

2. WOL doesn't seem to work for me at all. I know that unreliable WOL is a known issue with the chromebox but I am running a standalone and I used matt's script so I assume the coreboot firmware was installed. I am also making sure I use suspend instead of shutdown/hibernate but the WOL packet still doesn't seem to work. I have tried sending it via Yatse on android (2 different phones) and XBMC remote (joethefox) on iphone. no dice.. the chromebox stays suspended until I hit the power switch or press a key on the keyboard. Any ideas where I can look or how I can troubleshoot this further?

Again thanks to everyone in the thread but matt in particular for all the hard work.

TC

[Matt Devo]

Hi everyone,

Awesome script Matt, thanks a bunch for all the hard work, especially the additions to the chromebox section of wiki that I assume were all culled from this thread.
I have read through the thread in detail and after following all the instructions have a perfectly working standalone openelec asus chromebox.
I am however troubleshooting a couple of minor issues and I wondered if anyone could shed any light or point me in the right direction for further troubleshooting.

1. I have an xbox 360 wired gamepad controller plugged in but openelec does not seem to recognise it. I have confirmed I have gamepads enabled in the XBMC options and everything I've read seems to suggest the driver is a default in the current build of OE but my install doesn't seem to load it and the controller isn't listed when I run any diagnostic utilities. Stupid question but does the build of openelec installed by the script include the driver for the 360 controlpad? If no, how would I install it? If yes, any ideas where I can look for further troubleshooting on this?

2. WOL doesn't seem to work for me at all. I know that unreliable WOL is a known issue with the chromebox but I am running a standalone and I used matt's script so I assume the coreboot firmware was installed. I am also making sure I use suspend instead of shutdown/hibernate but the WOL packet still doesn't seem to work. I have tried sending it via Yatse on android (2 different phones) and XBMC remote (joethefox) on iphone. no dice.. the chromebox stays suspended until I hit the power switch or press a key on the keyboard. Any ideas where I can look or how I can troubleshoot this further?

Again thanks to everyone in the thread but matt in particular for all the hard work.

TC

1) you'll need to boot up, connect the controller, then post the kernel log from an ssh session: dmesg | pastebinit

2) WOL should work 100% with an ethernet connection; it doesn't work at all with wifi. be sure to set up a new profile with Yatse since it stores the MAC address, not just the IP address

[TychoCaine]

Thanks for the advice Matt,

Re the Xbox 360 Controller:
I rebooted, plugged in the controller and generated a log, reviewed it, then unplugged the controller and tried a different one, then ran the log again -> http://sprunge.us/PUaY

[38276.594764] usb 1-2: new full-speed USB device number 4 using xhci_hcd
[38744.745115] usb 1-2: USB disconnect, device number 4
[38746.926368] usb 1-2: new full-speed USB device number 5 using xhci_hcd

I assume from the above that it's clearly detecting my controllers without error... they just aren't working for some reason. Would appreciate any advice or guidance you can offer but I assume I need to head over to the OE forums to resolve this one?

WOL issue:
As you can see from the junk in my log, I got the WOL working and tested it a bunch of times. For anyone else wrestling with this Matt was 100% spot on... Yatse keeps old MAC addresses and the iphone remote does not store the MAC address... so I created a new profile for yatse and manually typed in the MAC on the iphone and now all good.

TC

[Matt Devo]

Thanks for the advice Matt,

Re the Xbox 360 Controller:
I rebooted, plugged in the controller and generated a log, reviewed it, then unplugged the controller and tried a different one, then ran the log again -> http://sprunge.us/PUaY

[38276.594764] usb 1-2: new full-speed USB device number 4 using xhci_hcd
[38744.745115] usb 1-2: USB disconnect, device number 4
[38746.926368] usb 1-2: new full-speed USB device number 5 using xhci_hcd

I assume from the above that it's clearly detecting my controllers without error... they just aren't working for some reason. Would appreciate any advice or guidance you can offer but I assume I need to head over to the OE forums to resolve this one?

WOL issue:
As you can see from the junk in my log, I got the WOL working and tested it a bunch of times. For anyone else wrestling with this Matt was 100% spot on... Yatse keeps old MAC addresses and the iphone remote does not store the MAC address... so I created a new profile for yatse and manually typed in the MAC on the iphone and now all good.

TC

with the controller plugged in, give me the log from: lsusb -vv | pastebinit

for WOL, you can have YATSE autodetect your ChromeBox, no need to type out the MAC manually

[TychoCaine]

Thanks Matt... I worked through my controller issues last night w/ some OE guys in thier irc channel.
Turns out the wireless microsoft 360 controller I have does not act as a usb device when plugged in... it's a charge cable only so I just switched to a PS3 bluetooth controller and it worked fine.
Again thanks for all the assistance... loving the chromebox

[ATV1-canada]

Hi Matt - awesome work - thanks .

just upgraded from my vintage but very well used ATV1 with crystalbuntu to the ASUS -CB - (M004U), the only mod I added was an extra 2gig memory card in the open slot. I set it up stand alone as its a replacement for the family's main XBMC box.

set up was very easy and took about 30 minutes

the Turtle beach USB digital audio adapter as per the WIKI works great and does pass DD and DTS to my 5.1 receiver via SPDIF

I "borrowed" my sons PS3 - bluetooth DVD remote and it works - good - plug and play.

UPDATE

the ASUS-CB has been working perfectly :-) thanks Matt !

having used the ATV1 previously for years ... the PS3 BD remote works functionally on the ASUS CB - however it is a little clunky in comparison to the apple remote.

I do however really like the blue tooth as it is built into the ASUS CB

with this in mind - I was able to acquire a fire tv remote and created a keyboard.xml file in notepad which I placed in the /storage/.xbmc/userdata/keymaps : folder

the new fire tv remote passed the WAF factor and essentially emulates the ATV1 remote with the plus of a blue-tooth.

my key map is below for anyone wishing to try:

<?xml version="1.0" encoding="UTF-8"?>
<keymap>
<Global>
<keyboard>
<key id="0xf200">ContextMenu</key>
<browser_back>Back</browser_back>
</keyboard>
</Global>
<FullscreenVideo>
<keyboard>
<key id="0xf200">CodecInfo</key>
<browser_back>Stop</browser_back>
<up>VolumeUp</up>
<down>VolumeDown</down>
</keyboard>
</FullscreenVideo>
<VideoMenu>
<keyboard>
<key id="0xf200">ContextMenu</key>
<browser_back>Back</browser_back>
</keyboard>
</VideoMenu>
</keymap>

[denrock]

Been using the standalone openelec for months on the asus Celeron 2955U and it's been working great. Thanks again for all your work Matt.

I also have the asus i5 chromebox and I decided to try out the dual boot ubuntu and chrome os. Everything went fine with the script and it is all set up and working except bluetooth doesn't work in ubuntu. It works under chrome os but under ubuntu it says there's no bluetooth adaptor found. Has anyone else done the dual boot with the asus i5 and had this no bluetooth adaptor found problem?

[Matt Devo]

Been using the standalone openelec for months on the asus Celeron 2955U and it's been working great. Thanks again for all your work Matt.

I also have the asus i5 chromebox and I decided to try out the dual boot ubuntu and chrome os. Everything went fine with the script and it is all set up and working except bluetooth doesn't work in ubuntu. It works under chrome os but under ubuntu it says there's no bluetooth adaptor found. Has anyone else done the dual boot with the asus i5 and had this no bluetooth adaptor found problem?

there is no Asus i5 ChromeBox to my knowledge, do you mean i3? The celeron and i3 are identical hardware wise outside of the CPU/GPU. Perhaps the bluetooth adapter is disabled by default in Ubuntu? There's no reason it shouldn't work properly.

[Newbie2015]

Thank you for all of your excellent work Matt!

I can't seem to get rid of the partition that I created for a dual-boot setup. I tried the dual-boot but found I didn't really need it, so did a factory reset followed by a stand alone setup but Kodi only shows an 8GB drive...

How do I get the full 16GB back?

Thanks!

[denrock]

Been using the standalone openelec for months on the asus Celeron 2955U and it's been working great. Thanks again for all your work Matt.

I also have the asus i5 chromebox and I decided to try out the dual boot ubuntu and chrome os. Everything went fine with the script and it is all set up and working except bluetooth doesn't work in ubuntu. It works under chrome os but under ubuntu it says there's no bluetooth adaptor found. Has anyone else done the dual boot with the asus i5 and had this no bluetooth adaptor found problem?

there is no Asus i5 ChromeBox to my knowledge, do you mean i3? The celeron and i3 are identical hardware wise outside of the CPU/GPU. Perhaps the bluetooth adapter is disabled by default in Ubuntu? There's no reason it shouldn't work properly.

yeah, I meant the i3 chromebox. When you go to the settings bluetooth it just says no bluetooth adapters found. There's no option to turn it on or off or enable or disable...everything is grayed out since it says no adapters found. I was just wondering if anyone else had encountered this on this model. I tried reinstalling it a couple of times just to make sure and the problem was there each time.

[nickr]

The following commands help with hardware detection:

lspci
lsusb
lshw

See what they say about Bluetooth.