[matchesmalone]

I have been trying to get my Zbox HD-ID11 to wake from suspend using a MCE remote in XBMC Live (9.11 repack) installed to the HDD.

I believe I have ubuntu/XBMC configured properly (I have added the USBs to /proc/acpi/wakeup, and other things), and now I am thinking perhaps there is some kind of BIOS setting I am missing.

In the field where you can select have ACPI S1 or S3 I have it set to Auto, although I have tried the S3 setting as well with no luck.

My IR receiver flashes red when it receives an IR signal. However, when the box goes in to suspend mode the IR receiver appears to be unresponsive. No red flashes indicating that it has power. (Edit: I should also note that I am not using one of the USB ports next to the eSATA port for the IR receiver. The manual says they do not support the wakeup function.)

Has anybody gotten this to work? Does this hardware support this?

As much as I don't want to, I'm tempted to return this if I can't get it to work, there are so many other solutions that apparently have more functionality out of the box. I have been frustrated with the support from Zotac. The instructions for HDMI over audio provided by Zotac, for example, were almost immediately outdated. They even suggest using a patch for version 1.0.22 after instructing you to install 1.0.23, and the patch doesn't even support that version! It's painfully obvious that they didn't even test it themselves. Fortunately the patch isn't needed anyway.

And whatever happened to this statement?: "If you’re looking for an out-of-box compatibility with an XBMC LiveCD, stay tuned as we’re working with the XBMC team to incorporate support with future LiveCDs." It's been almost two months, and I've seen zero further communication in this regard.

This post has been edited by matchesmalone: 30 June 2010 - 12:06 PM

[supaahiro]

I'll contact the appropriate people and post back what I can find out.

[matchesmalone]

 supaahiro, on 30 June 2010 - 11:27 AM, said:

I'll contact the appropriate people and post back what I can find out.

Thanks for the reply!

That would be VERY appreciated. I'll be sure to help spread the word if you find anything else out.

[zivodevo]

I too am having the same problem. I have tried the XBMC 9.11 build and two versions from XBMCFreak without success. I have both a Logitech bluetooth keyboard and a standard USB wired keyboard and neither work. I'm running the latest ID11 bios (2K100526) which has reduced the fan noise considerably.

When the unit is in standby and I use the bluetooth keyboard, the bluetooth receiver flashes but nothing happens. Device can only be brought back with power button which is annoying. Tried bios with both Auto and S3.

I'm trying both an AIM MCE IR remote and a Wii remote tomorrow so I'll let you know if I can get any of those working but any assistance from someone who has this working would be appreciated. Not wife or child friendly yet so I can't put my beloved ID11 into production.

[supaahiro]

matchesmalone, can you give me a guide on what you did? I'll test it and see what I can find. I was told it could be the config under Linux.

[matchesmalone]

 supaahiro, on 06 July 2010 - 11:40 AM, said:

matchesmalone, can you give me a guide on what you did? I'll test it and see what I can find. I was told it could be the config under Linux.

I've tried the instructions from the XBMC wiki, here.

As far as installing/configuring XBMC, I wrote this guide detailing everything I did. Since then I have tried starting from scratch, and installing the XBMCFreak Live CD 10.08 svn 31495. Other than that, I didn't do much except upgrading to the 256.35 nvidia drivers and Alsa 1.0.23, per the instructions in the above link.

In all cases, the IR receiver is unresponsive during Suspend (no blinking red light during remote activity).

In searching various forums, I have found many other people with this same issue, but I have yet to find anyone who has gotten it working.

Thank you in advance for your help!

This post has been edited by matchesmalone: 06 July 2010 - 12:58 PM

[supaahiro]

Do other USB devices work while in suspend?

[matchesmalone]

 supaahiro, on 07 July 2010 - 03:51 PM, said:

Do other USB devices work while in suspend?

No. I have tried a USB keyboard with the same results.

[supaahiro]

Quote

Enable Wake on USB Activity

If your IR receiver is plugged into a USB port. You can have Linux recognize IR traffic on the USB bus as a signal to wake XBMC. This method can have the drawback of waking XBMC unnecessarily because you're using the remote for other devices.

First find which USB bus your IR receiver is connected to. The command lsusb can be somewhat useful for determining this, or you can just start at 0 and work your way up until you find it. The command to wake upon USB traffic is:

sudo sh -c 'echo "USB0" > /proc/acpi/wakeup'

Replace USB0 with USB1 and so on until you find it. Once you do, add it to your startup by editing /etc/rc.local and putting the following line before exit 0.

echo "USB0" > /proc/acpi/wakeup

You can verify this is set after boot by running:

cat /proc/acpi/wakeup

It should show "enabled" in the 3rd column after the device you set.

I used this part of the guide and was able to Wake from Suspend with USB Keyboard and USB Mouse.
I editted the /etc/rc.local with nano
I enabled all USB devices.

[matchesmalone]

 supaahiro, on 07 July 2010 - 06:01 PM, said:

I used this part of the guide and was able to Wake from Suspend with USB Keyboard and USB Mouse.
I editted the /etc/rc.local with nano
I enabled all USB devices.

I haven't tried it lately, with the latest version of my install, so I'll give that a try again tomorrow (I'm on business travel and can't do it right now).

Have you tried it with a USB remote, or do you not have easy access to one? Also, which USB port did you use? I assume that they should all work, except for the two next to the eSATA port, correct? Were any BIOS changes necessary to accomplish this, and if so which BIOS version are you using?

Thank you very much for the help. I really appreciate getting some feedback on this. I'll post back if when I make progress.

This post has been edited by matchesmalone: 07 July 2010 - 07:13 PM

[supaahiro]

I don't have access to a remote, but I'm working on getting one. The USB ports I use are the one in the front and the one on top. I haven't tested the ones in back yet. I'll do it tomorrow and then edit my post accordingly.

The only changes I made in BIOS was setting it to S3 (STR) and enabling the video to repost on resume.

Update
I inserted the USB Mouse and Keyboard on the back USB Ports, they two, that are farthest from the eSata, also resume from S3. The other two, by the eSata, don't resume from S3.

[matchesmalone]

 supaahiro, on 07 July 2010 - 07:21 PM, said:

I don't have access to a remote, but I'm working on getting one. The USB ports I use are the one in the front and the one on top. I haven't tested the ones in back yet. I'll do it tomorrow and then edit my post accordingly.

The only changes I made in BIOS was setting it to S3 (STR) and enabling the video to repost on resume.

Interesting! Can you be more specific on the 2nd setting you mention "enabling the video to repost on resume?" Exactly where in the BIOS menu is that located? I hadn't tried anything like that. I had also been leaving the ACPI setting to "Auto" most of the time, so perhaps these will help fix my problems.

[supaahiro]

 matchesmalone, on 07 July 2010 - 08:44 PM, said:

Interesting! Can you be more specific on the 2nd setting you mention "enabling the video to repost on resume?" Exactly where in the BIOS menu is that located? I hadn't tried anything like that. I had also been leaving the ACPI setting to "Auto" most of the time, so perhaps these will help fix my problems.

It's called Repost Video on S3 Resume under ACPI Configuration > General ACPI configuration.

[matchesmalone]

Ok, I have been able to get it to wakeup with a keyboard plugged into USB, but the remote still will not work. I've even tried putting the IR receiver into the same port that the keyboard was in, but no luck. One time, I switched the USB ports while in Suspend mode, and just the act of removing the IR receiver USB plug was enough to wake it up. So it seems like it is in fact configured properly to wake from USB activity.

The problem is, no matter what I do the IR receiver doesn't respond when in suspend. In suspend mode, the receiver will not flash a red light when buttons on the remote are pressed. I'm not sure if that indicates that it doesn't have power, or if there is some other setting that needs to let the lirc module continue to run in suspend?

Anyway, I've posted a couple settings to make sure we're on the same page. Any further ideas would be appreciated.

xbmc@XBMCLive:~$ lsusb
Bus 005 Device 002: ID 046d:c517 Logitech, Inc. LX710 Cordless Desktop Laser
Bus 005 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 003 Device 002: ID 0471:0815 Philips eHome Infrared Receiver
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 005: ID 1bcf:0c31 Sunplus Innovation Technology Inc.
Bus 001 Device 003: ID 05e3:0608 Genesys Logic, Inc. USB-2.0 4-Port HUB
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

xbmc@XBMCLive:~$ cat /proc/acpi/wakeup
Device  S-state   Status   Sysfs node
P0P1      S4     disabled  pci:0000:00:1e.0
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
USB0      S3     enabled   pci:0000:00:1d.0
USB1      S3     enabled   pci:0000:00:1d.1
USB2      S3     enabled   pci:0000:00:1d.2
USB3      S3     enabled   pci:0000:00:1d.3
EUSB      S3     disabled  pci:0000:00:1d.7

[matchesmalone]

Oh, and one other thing that might be helpful for other people out there trying to get Suspend to work.

Whenever I resume, I have had the annoying issue of the being disconnected from the network (I'm using wireless). Upon resume, I have no ip address, but restarting the network always brings it back without a problem. To fix this, I created a script to automatically restart the network.

First, create the script and bring up a text editor:

nano 74network-resume.sh

Then copy and paste the code below:

#!bin/bash

. /usr/lib/pm-utils/functions

case "$1" in
        thaw|resume)
                /etc/init.d/networking restart
                ;;
        *)
                ;;

esac

exit $?

Now just make it executable and then copy it to the folder where it will be executed on Resume:

chmod +x 74network-resume.sh
cp 74network-resume.sh /etc/pm/sleep.d

[supaahiro]

In XBMC, System > System > Input Devices, try enabling Remote control sends keyboard presses.

[matchesmalone]

Success! I actually didn't even need to enable that.

I found that it will wake from the remote, only if you press the power button on the remote. I feel a little silly, as I was thinking that it should wake when there is any remote activity, similar to how a keyboard can wake it up by pressing any button.

This is obviously preferable though, since it won't wake up every time I use any other remote in the room. I'm guessing it's supposed to work that way, which is why I feel silly...

Anyway, thank you again for the help!

[supaahiro]

Glad to have helped
It was a learning experience for me too

[gpborges]

Guys, I have a Zocat IONITX-L-E and it's all fine but the resume from the MCE remote. I'm struggling for DAYS and I've read all about this... I have a Microsoft Wireless Mouse/Keyboard set (USB) and I can wake the HTPC up using the keyboard or remote on ALL the back USB ports. However, the MCE remote can't do it. Follow some output of my setup:

All USB hubs enabled to wake up

gpborges@htpc-backend:~$ cat /proc/acpi/wakeup 
Device	S-state	  Status   Sysfs node
SMB0	  S4	 disabled  pci:0000:00:03.2
USB0	  S4	 enabled   pci:0000:00:04.0
USB2	  S4	 enabled   pci:0000:00:04.1
US15	  S4	 enabled   pci:0000:00:06.0
US12	  S4	 enabled   pci:0000:00:06.1
NMAC	  S5	 disabled  pci:0000:00:0a.0
PBB0	  S4	 disabled  pci:0000:00:09.0
HDAC	  S4	 disabled  pci:0000:00:08.0
XVR0	  S4	 disabled  pci:0000:00:0c.0
XVR1	  S4	 disabled  
P0P5	  S4	 disabled  
P0P6	  S4	 disabled  pci:0000:00:15.0
P0P7	  S4	 disabled  pci:0000:00:16.0
P0P8	  S4	 disabled  pci:0000:00:17.0
P0P9	  S4	 disabled  pci:0000:00:18.0
PWRB	  S4	*enabled   
gpborges@htpc-backend:~$ 

Confirming numbers of Sysfs node with lspci command

gpborges@htpc-backend:~$ lspci | grep USB
00:04.0 USB Controller: nVidia Corporation MCP79 OHCI USB 1.1 Controller (rev b1)
00:04.1 USB Controller: nVidia Corporation MCP79 EHCI USB 2.0 Controller (rev b1)
00:06.0 USB Controller: nVidia Corporation MCP79 OHCI USB 1.1 Controller (rev b1)
00:06.1 USB Controller: nVidia Corporation MCP79 EHCI USB 2.0 Controller (rev b1)
gpborges@htpc-backend:~$

And my BIOS is set to Susped to RAM (S3). The suspend from MCE remote works fine, and resume using power button on my case also. I don't have any issue from various cycles of suspend/resume and the only thing I need to fix is the resume using the MCE remote.

PLEASE, I need help on this...

Looking forward a feedback!

Cheers...

[nut]

We do not officially support linux, gpborges, however I have done some research on this subject matter for you and have found information here to help you: http://wiki.xbmc.org..._Wake-On-Device

As stated at the bottom of that webpage, a particular bug can occur depending on the kernel that you run in your XBMC.

Also, have you committed your configuration to rc.local?

Regards,
Nut