So I have a
Jetway Mini-Top model number HBJC600C99-52W-BW and I am running Xbmcbuntu 11.0.
I've been struggling with the how it comes out of sleep. First off, the unit has a proprietary IR receiver and remote which I am not using except for the poweroff / standby signal. In short, I programmed my harmony remote to issue this command to wake it up cause it is not capable of waking with the HP mceusb receiver that I also have plugged to it.
Programmed suspend (5 min timer) works fine, it used to be (before upgrading to xbmcbuntu from xbmc live) that a single poweroff / standby signal would wake it up but now it automatically forces xbunbuntu to shut off.
It is to be noted that the way it used to work was that a single poweroff / standby signal would wake it and a second poweroff / standby signal would shut it down. That behavior I liked.
I hope this makes some sense.
At about 15:37:08 I attempted to wake it up (towards the end of log) and it shut down.
Perhaps someone has some insight, thanks.
xbmc.old.log
(2012-10-25, 23:13)john.cord Wrote: [ -> ]First you should check that the Shutdown Function in XBMC is set to suspend and not power down. Secon you should disable on of the two IR Recievers in your system and third you should use this guide (http://forum.xbmc.org/showthread.php?tid...pid1203339) to make the used IR Receiver able to wakeup your System.
Upgrade your System to Ubuntu 12.04 with this guide http://forum.xbmc.org/showthread.php?tid=116996
Thanks for the suggestions, it's much appreciated
1) The shutdown function in XBMC is set to suspend and not power down
2) Concerning disabling the IR receivers. I pulled out the HP mceusb receiver to see if the built-in receiver is picking up mce IR signals and it is not. Like I said, it's got it's own proprietary IR codes and I only use the poweroff/poweron IR command which is programmed in my harmony remote
oh and I tried hard to get the USB wake working with the HP mceusb instead, but it never worked. I also remember coming across another post in the forums saying that this box isn't capable of waking from USB
Quote:The built-in IR is from aureal
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 004 Device 002: ID 045e:006d Microsoft Corp. eHome Remote Control Keyboard keys
Bus 005 Device 002: ID 0d8c:013c C-Media Electronics, Inc.
Bus 001 Device 005: ID 0755:2626 Aureal Semiconductor
3) Quickly looking at the link you mentioned, it leads me to believe this is a Xvba guide for an amd chip, i am running an nvidia ION.
EDIT: Should I instead follow the guide and replace the xvba portion with nvidia and install ubuntu 12.04 and ditch xbmcbuntu 11.0?
Just a couple of things.
(2012-10-26, 01:16)joelones Wrote: [ -> ]3) Quickly looking at the link you mentioned, it leads me to believe this is a Xvba guide for an amd chip, i am running an nvidia ION.
It is for Nvidia too because it contains the VDPAU Optimizations from FernetMenta. As long as you use the xbcm-xvba branch from the PPA everything should be fine.
(2012-10-26, 01:16)joelones Wrote: [ -> ]EDIT: Should I instead follow the guide and replace the xvba portion with nvidia and install ubuntu 12.04 and ditch xbmcbuntu 11.0?
Just a couple of things.
Yes you should becaus it is much mor stable.
Are you shure that your box cannot be woken by usb
Try connect the HP MCEUSB and post a lsusb here please!!!
So, I installed 12.10 instead as I could not get sound working on 12.04 for the life of me despite having previous working configs (.asoundrc, which I know works on previous xbmc live setups)
Was pleasantly surprised to find that the xvba ppa is a frodo alpha build and audio was detected automatically with no problems.
So, here is the lsusb.
Quote:Bus 001 Device 002: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 004 Device 002: ID 045e:006d Microsoft Corp. eHome Remote Control Keyboard keys
Bus 005 Device 002: ID 0d8c:013c C-Media Electronics, Inc. CM108 Audio Controller
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 0755:2626 Aureal Semiconductor
I believe the device is 045e:006d
here is cat /proc/acpi/wakeup
Quote:P0P1 S4 *disabled pci:0000:00:1e.0
USB0 S4 *enabled pci:0000:00:1d.0
USB1 S4 *enabled pci:0000:00:1d.1
USB2 S4 *enabled pci:0000:00:1d.2
USB3 S4 *enabled pci:0000:00:1d.3
EUSB S4 *enabled pci:0000:00:1d.7
P0P4 S4 *disabled pci:0000:00:1c.0
P0P5 S4 *disabled pci:0000:00:1c.1
P0P6 S4 *disabled pci:0000:00:1c.2
P0P7 S4 *disabled
P0P8 S4 *disabled
P0P9 S4 *disabled
Judging by this thread, individuals with the same box never got usb wake working
http://forum.xbmc.org/showthread.php?tid...#pid782514
btw, the mceusb is on 4-1 and is enabled
Quote:[ 8540.499400] mceusb 4-1:1.0: >Registered Microsoft Microsoft IR Transceiver with mce emulator interface version 1
[ 8540.499412] mceusb 4-1:1.0: >2 tx ports (0x0 cabled) and 2 rx sensors (0x0 active)
Quote:$ cat /sys/bus/usb/devices/4-1:1.0/power/wakeup
enabled
I have another mini-top zotac box which i got usb wake working with the same IR HP mceusb device attached. And the difference between the two which I've noticed is that on the box that works, when it goes into suspend the LED on the IR device goes on and stills on during sleep, however on the Jetway (above, that doesn't work), the LED goes off. I'm assuming in the latter case, it's not listening for signals, the usb bus is off and hence no LED.
Unfortunately this is the only workaround I found (using the proprietary poweroff/poweron signal), just it's very flimsy, sometimes it comes out of wake properly other times justs shutdowns.
Do you tried the UDEV Rule ??
(2012-10-29, 04:44)john.cord Wrote: [ -> ]Do you tried the UDEV Rule ??
yep tried that too:
Code:
SUBSYSTEM=="usb", ATTRS{idVendor}=="045e", ATTRS{idProduct}=="006d" RUN+="/bin/sh -c 'echo enabled > /sys$env{DEVPATH}/../power/wakeup'"
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash usbcore.autosuspend=-1"
sudo update-grub
oh sending a wol packet does do the trick and resumes the box from supsend which is what i would like from the remote, after exhausting all possibilities its clear the usb wake is a hard limitation of this box, but still struggling with the initial issue