[Matt Devo]

The IR sensor and remote work OOTB on the OpenELEC on my Windows PC.

ok, do me a favor and download this app on your windows PC: http://rweverything.com/download/. I used the portable x64 version.

run it, click the USB button, then copy/paste the output from it. want to compare what Windows is reporting to what Linux is, particularly for the endpoint interval values.

this definitely looks like a linux/USB3 issue, but not one I've seen before, as the issue my patch fixed was for devices which used bulb type endpoints, vs interrupt endpoints like your device (which were previously working fine to my knowledge). If we can figure out the issue, I can (try to) fix it under Linux, and provide a fixed version of OpenELEC until the patch makes it in.

[Mark the Red]

PHP Code:

DriverKeyName: {36fc9e60-c465-11cf-8056-444553540000}\0044
DeviceName: 

Connection Information:
ConnectionIndex    0x00000001 - (Port number)
CurrentConfigurationValue    0x01
Speed    0x01 - Full speed
DeviceIsHub    0x00 - No
DeviceAddress    0x0001
NumberOfOpenPipes    0x00000002
ConnectionStatus    0x01 - DeviceConnected

Device Descriptor:
12 01 00 02 00 00 00 08 84 17 06 00 02 01 01 02    ................
03 01                                              ..              

bLength    0x12
bDescriptorType    0x01
bcdUSB    0x0200 - Spec# = 02.00
bDeviceClass    0x00 - (Defined at Interface level)
bDeviceSubClass    0x00 
bDeviceProtocol    0x00 
bMaxPacketSize0    0x08 - 8 bytes
idVendor    0x1784 - TopSeed Technology Corp.
idProduct    0x0006
bcdDevice    0x0102 - Device# = 01.02
iManufacturer    0x01 - TopSeed Technology Corp.
iProduct    0x02 - eHome Infrared Transceiver
iSerialNumber    0x03 - TS004RQf
bNumConfigurations    0x01

Configuration Descriptor:
09 02 20 00 01 01 00 A0 32                         .. .....2       

bLength    0x09
bDescriptorType    0x02
wTotalLength    0x0020
bNumInterfaces    0x01
bConfigurationValue    0x01
iConfiguration    0x00
bmAttributes    0xA0 - Self-powered=No, Remote Wakeup=Yes
MaxPower    0x32 - 100mA

Interface Descriptor:
09 04 00 00 02 FF FF FF 00                         .........       

bLength    0x09
bDescriptorType    0x04
bInterfaceNumber    0x00
bAlternateSetting    0x00
bNumEndpoints    0x02
bInterfaceClass    0xFF - Vendor specific
bInterfaceSubClass    0xFF - Vendor specific
bInterfaceProtocol    0xFF - Vendor specific
iInterface    0x00

Endpoint Descriptor:
07 05 01 03 20 00 00                               .... ..         

bLength    0x07
bDescriptorType    0x05
bEndpointAddress    0x01 - Endpoint# = 1, Direction = OUT
bmAttributes    0x03 - Transfer Type = Interrupt
wMaxPacketSize    0x0020 - 32 bytes
bInterval    0x00 - 0 milliseconds

Endpoint Descriptor:
07 05 81 03 20 00 00                               .... ..         

bLength    0x07
bDescriptorType    0x05
bEndpointAddress    0x81 - Endpoint# = 1, Direction = IN
bmAttributes    0x03 - Transfer Type = Interrupt
wMaxPacketSize    0x0020 - 32 bytes
bInterval    0x00 - 0 milliseconds

Configuration Descriptor:
05 02 02 00 04                                     .....           

bLength    0x05
bDescriptorType    0x02
wTotalLength    0x0002
bNumInterfaces    0x04
bConfigurationValue    0x00
iConfiguration    0x06 - 儐
bmAttributes    0x30 - Self-powered=No, Remote Wakeup=Yes
MaxPower    0x0F - 30mA

String LanguageID=0x0409 


Tell me if this is the right code. The window on the left referred to this eHome Infrared Receiver. Thanks.

[Matt Devo]

Tell me if this is the right code. The window on the left referred to this eHome Infrared Receiver. Thanks.

it's right, but unfortunately reporting the exact same info in Windows as in Linux, so no hint as to what the problem is. It's definitely a Linux/USB3/MCE driver issue, just not sure how to debug it at this point.

[Mark the Red]

Any other IR receiver I can buy you recommend? I got the one off the amazon link you recommended. Some say they are RC6 IR Protocol....will those work?

Could this also be (?) I did not install the firmware / BIOS correctly? Is there a way I can reinstall the bios via the ssh terminal. The sudo bash syntax gave me errors (post 1 instructions).

[Matt Devo]

Any other IR receiver I can buy you recommend? I got the one off the amazon link you recommended. Some say they are RC6 IR Protocol....will those work?

Could this also be (?) I did not install the firmware / BIOS correctly? Is there a way I can reinstall the bios via the ssh terminal. The sudo bash syntax gave me errors (post 1 instructions).

the HP receiver I have is model 5188-1667, and works out of the box. There's absolutely no way you didn't install the firmware correctly, or that the firmware is an issue here. I'd return the receiver you have and buy the one linked below - least hassle.

HP receiver on ebay: http://www.ebay.com/itm/like/191049086497?lpid=82

[Hannes The Hun]

Matt, seeing as the coreboot FW got updated I thought about updating my setup via the script... well... how would I get terminal access?

ssh won't work, connection refused. ctrl&alt&F2 with the keyboard brings up a non-working command prompt in full screen.

am I doing something obviously wrong here? already googled the hell out of the openelec ssh problem but to no avail.
outdated guides say to create an ssh_enable file in the configfiles samba folder of the chromebox, current guides say
to just enable SSH in the openelec settings but there's only the option to disable ssh password.

[Matt Devo]

Matt, seeing as the coreboot FW got updated I thought about updating my setup via the script... well... how would I get terminal access?

ssh won't work, connection refused. ctrl&alt&F2 with the keyboard brings up a non-working command prompt in full screen.

am I doing something obviously wrong here? already googled the hell out of the openelec ssh problem but to no avail.
outdated guides say to create an ssh_enable file in the configfiles samba folder of the chromebox, current guides say
to just enable SSH in the openelec settings but there's only the option to disable ssh password.

The script has to be run from either ChromeOS or ChromiumOS. Since you can no longer boot the former, you need to make a USB stick with the latter and download/run the script from there

[Hannes The Hun]

ah okay, got it. thanks!

[jsp1]

Matt, I did backup my stock bios, however...I am getting nothing when trying to restore the mac and such from the new script. It seems that my usb got corrupted somehow? Anyway, I can pull some files under recovery, could you tell me what the filename/size should be for the backup?

[Matt Devo]

Matt, I did backup my stock bios, however...I am getting nothing when trying to restore the mac and such from the new script. It seems that my usb got corrupted somehow? Anyway, I can pull some files under recovery, could you tell me what the filename/size should be for the backup?

stock-firmware.rom, 8.4 MB

[jsp1]

Matt, I did backup my stock bios, however...I am getting nothing when trying to restore the mac and such from the new script. It seems that my usb got corrupted somehow? Anyway, I can pull some files under recovery, could you tell me what the filename/size should be for the backup?

stock-firmware.rom, 8.4 MB

Thanks. Nothing of the sort shows up, lost cause?

Edit: It looks like I can recover my original chromeOS update...perhaps that would contain the info?

[tret]

Has there been any progress (resolution or workaround) for the VAAPI hardware accelerated playback freezing issue?

Symptom - During playback, the video freezes while the audio continues to play. Key presses are non-responsive and the chromebox needs to be powered off/rebooted to regain normal function.

Obviously disabling hardware accelerated playback prevents the symptoms however higher bitrate content playback is choppy, particularly when syncing to a 24p display. I haven't seen much chatting about this issue and haven't been able to find any solutions in the thread. If there isn't one, is this on the XBMC Dev team's radar?

Note: Running standalone openelec v4.0.6. The content is being pulled (over SMB) from a NAS on a 1Gb link. Same config/content works fine on an older Zotac zbox w/ celeron CPU and nvidia GPU.

[jerndl]

Has there been any progress (resolution or workaround) for the VAAPI hardware accelerated playback freezing issue?

Symptom - During playback, the video freezes while the audio continues to play. Key presses are non-responsive and the chromebox needs to be powered off/rebooted to regain normal function.

Obviously disabling hardware accelerated playback prevents the symptoms however higher bitrate content playback is choppy, particularly when syncing to a 24p display. I haven't seen much chatting about this issue and haven't been able to find any solutions in the thread. If there isn't one, is this on the XBMC Dev team's radar?

Note: Running standalone openelec v4.0.6. The content is being pulled (over SMB) from a NAS on a 1Gb link. Same config/content works fine on an older Zotac zbox w/ celeron CPU and nvidia GPU.

I'm having the exact same problem "Symptom - During playback, the video freezes while the audio continues to play. Key presses are non-responsive and the chromebox needs to be powered off/rebooted to regain normal function." It doesn't happen all the time, although it "seems like" it is happening more frequently. I am also running standalone OE 4.0.6 but my content is coming from a 4TB WD MyBook external USB 3.0 drive. I set this up awhile ago during the early stages of the EZ setup script, before the Coreboot firmware update. Any Ideas? I can provide a log if needed. BTW during the "freeze" the Chromebox continues to work as a SMB server for other XBMC "clients". Thanks.

Jay

[tret]

Has there been any progress (resolution or workaround) for the VAAPI hardware accelerated playback freezing issue?

Symptom - During playback, the video freezes while the audio continues to play. Key presses are non-responsive and the chromebox needs to be powered off/rebooted to regain normal function.

Obviously disabling hardware accelerated playback prevents the symptoms however higher bitrate content playback is choppy, particularly when syncing to a 24p display. I haven't seen much chatting about this issue and haven't been able to find any solutions in the thread. If there isn't one, is this on the XBMC Dev team's radar?

Note: Running standalone openelec v4.0.6. The content is being pulled (over SMB) from a NAS on a 1Gb link. Same config/content works fine on an older Zotac zbox w/ celeron CPU and nvidia GPU.

I'm having the exact same problem "Symptom - During playback, the video freezes while the audio continues to play. Key presses are non-responsive and the chromebox needs to be powered off/rebooted to regain normal function." It doesn't happen all the time, although it "seems like" it is happening more frequently. I am also running standalone OE 4.0.6 but my content is coming from a 4TB WD MyBook external USB 3.0 drive. I set this up awhile ago during the early stages of the EZ setup script, before the Coreboot firmware update. Any Ideas? I can provide a log if needed. BTW during the "freeze" the Chromebox continues to work as a SMB server for other XBMC "clients". Thanks.

Jay

I also set mine up some time ago, approx 6 weeks ago, and haven't updated the firmware since. Matt, is this perhaps something that has been fixed in later firmware/bios updates?

[YellowDog]

I see 12 separate partitions on the firmware backup.

Can anyone suggest how to backup the flash drive. Can I use

Code:

dd if=/dev/sdb of=chrome-backup.img