[Matt Devo]

hi mat.help!!! im installing standalone openelec, and i have done stage 5, swapped usb drives, started stage 6 and it got to 75% and then the text dissapeared from my screan, and the screen is not getting a signal, as it telling me to connect a device. my usb stick is still flashing, and the power light is still on. is this normal, and i just have to wait?

can't say I've seen that, how long was it taking to download? can you press a key to wake it? I thought I had disabled ChromeOS's power management to prevent it from going to sleep, but maybe not

[milhouse34521]

Has anyone had issues with the network/wifi dropping with OpenElec on an Asus Chromebox? When it boots up its fine, but after a while of not being used (hours, not days), XBMC doesn't have a network address anymore. If I go into the network settings it will show the wireless network, but there is an error that flashes briefly (I believe something about other programs controlling XBMC) and to disable that. I have disabled that, but the problem persists (though sometimes that will get it working again for a while).

Thanks.

[movie78]

Correct

Here is the link you requested.

http://sprunge.us/OSQG

http://sprunge.us/RZBX

Thanks!

[pie eater]

oops. it had gone into sleep mode. when i tried to get it to install from usb after reboot, i would not read the usb stick, so i checked the stick, and it had partitioned and had 2 files, but it would not read it, so i deleted it and tried to install the generic version from openelec, and it still would not boot from the drive, so im now trying to get it to boot from an sd card, it says, booting from usb device, but doesnt seem to be doing much. any idears?

[Matt Devo]

Correct

Here is the link you requested.

http://sprunge.us/OSQG

http://sprunge.us/RZBX

Thanks!

as per the output of lsusb, your IR receiver is manufactured by Topseed, and their buggy firmware (or Linux's buggy USB3 implementation) is to blame for it not working. Grab one of the known working IR receivers (listed on the wiki) and you'll be all set.

oops. it had gone into sleep mode. when i tried to get it to install from usb after reboot, i would not read the usb stick, so i checked the stick, and it had partitioned and had 2 files, but it would not read it, so i deleted it and tried to install the generic version from openelec, and it still would not boot from the drive, so im now trying to get it to boot from an sd card, it says, booting from usb device, but doesnt seem to be doing much. any idears?

download the v4.2.1 Generic x86_64 disk image, write it to SD/UDB using the Win32DiskImager tool, then boot from it.

I'll take a look at the script and see why it's going to sleep, it shouldn't be doing that.

[aaatjs]

Hi Matt

trying to use option 5 stand alone install and write coreboot firmware

starts installing but then says:

an error occurred flashing the correct firmware. DO NOT REBOOT

HP CHROMEBOX USING E-Z SETUP V3.2

any suggestions?

[Matt Devo]

Hi Matt

trying to use option 5 stand alone install and write coreboot firmware

starts installing but then says:

an error occurred flashing the correct firmware. DO NOT REBOOT

HP CHROMEBOX USING E-Z SETUP V3.2

any suggestions?

yes, exit and re-run the script, and retry option 5.

[aaatjs]

have done it a few times now and keep getting the same thing... even reinstalled chromeos and started fresh... nothing.

---

is there and earlier version of the script i can use?

have done a few this way and always worked a treat, this one is being nasty

[Matt Devo]

have done it a few times now and keep getting the same thing... even reinstalled chromeos and started fresh... nothing.

wait, what? how did you reinstall ChromeOS without rebooting, which it told you not to do? And why would you need to, since flashing the firmware doesn't touch the OS?

I just tested/verified the script, so I'm going to guess that like another poster here, the write-protect isn't disabled, either because the wrong screw was removed, or because there's still something bridging the two connections on the board. You can verify this by running 'sudo crossystem' at the prompt, and checking the last two fields/values - they should both be 0 if the write-protect is correctly disabled.

[aaatjs]

ahhh ran the check - 1 on both

write protect screw removed.... hmmmm

thanks for your help, ill pull it apart and check the contacts

Tony

[nickr]

Correct

Here is the link you requested.

http://sprunge.us/OSQG

http://sprunge.us/RZBX

Thanks!

Well the remote is clearly recognised in dmesg,

[ 2.035374] input: Media Center Ed. eHome Infrared Remote Transceiver (1784:0008) as /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/rc/rc0/input9
[ 2.035525] rc0: Media Center Ed. eHome Infrared Remote Transceiver (1784:0008) as /devices/pci0000:00/0000:00:14.0/usb1/1-6/1-6:1.0/rc/rc0
[ 2.055823] IR NEC protocol handler initialized
[ 2.086273] IR RC5(x) protocol handler initialized

What problem exactly are you having? (Bearing in mind this probably isn't a question for this thread as the problem is unlikely to be peculiar to the Chromebox).

[Matt Devo]

Well the remote is clearly recognised in dmesg

you missed the important part, from the last line:

[ 1396.089499] mceusb 1-5:1.0: 2 tx ports (0x0 cabled) and 2 rx sensors (0x0 active)

What problem exactly are you having? (Bearing in mind this probably isn't a question for this thread as the problem is unlikely to be peculiar to the Chromebox).

These Topseed IR receivers fail to initialize properly in the MCE driver, leading to the 0 active rx sensor msg. Its a Linux/xHCI issue, as the same receiver will work fine when connected to a USB2 port. I have one here, and have tried to debug the driver init, I just haven't had the time/interest.

[nickr]

Also:

This is the best howto for remotes on openelec:

http://nucblog.net/2014/01/mapping-the-b...e-control/

This is also very helpful:

http://forum.kodi.tv/showthread.php?tid=101151

[Matt Devo]

most MCE remotes should work out of the box (with OpenELEC at least), so none of that should be necessary. And none of that will help anyway if the driver can't init properly and thinks there aren't any active IR sensors, which is the case here. Most users are probably best off just buying a Flirc to use with an existing remote or a harmony.

[nickr]

@matt Devo I bow to your superior observation and technical skills! (And I hadn't seen post 1932 when I posted 1933!)