Posts: 1,722
Joined: Sep 2009
Reputation:
20
I think you may have a command in your sleep script which resumes the computer. If you can, undo all of your changes to the sleep scripts and use the guide to construct a new one.
Also, try running IRW from a terminal when you shut down the computer to see if any random commands are being sent through lirc.
Posts: 1,722
Joined: Sep 2009
Reputation:
20
are you suspending from the remote?
Posts: 109
Joined: Jan 2007
Reputation:
0
2009-11-10, 03:53
(This post was last modified: 2009-11-10, 04:02 by brownstein.)
I think we are making progress. This time (after adding that code to the script), it appeared to go into sleep mode except it left a blinking cursor in the top left corner of the screen, it seemed to resume fine but if I try to suspend again xbmc just freezes for 10-15 seconds and the seems to restart (only say that because it updates the library again). I neglected to mention that it was doing the same thing before I added that extra bit to the script. It seems to only try to suspend the first time, after that I have to reboot.
edit: so it wasn't me that resumed it, I rebooted and suspended again but just left it at the blinking cursor and waited, sure enough, it just seemed come back to xbmc after about 10 seconds.
Posts: 1,722
Joined: Sep 2009
Reputation:
20
2009-11-10, 04:38
(This post was last modified: 2009-11-10, 04:42 by outleradam.)
put this line echo "sleep portion of the script completed" >>/tmp/script.log right after the lirc stop command. and remove the last echo command that says script complete.
restart the computer
suspend,
resume
check your log in /tmp/script.log and see if it says 'sleep portion of the script completed' Make sure it is executing that portion of the code.
Have you tried suspending by using the keyboard? I should have asked that first. that last script was to remove all extra commands from your remote.
Posts: 109
Joined: Jan 2007
Reputation:
0
yes, that portion of the script is logged as being executed and it is with that portion that my screen goes black with the blinking cursor, when I remove that part, the asrock appears to sleep but only for a second before the activity light blinks and it resumes.
I tried the sleep button on my keyboard but it didnt do anything, I also used my keyboard to navigate to shutdown > suspend but it reacted just as if I was using the remote, which I expected.
I really appreciate your help troubleshooting this and I feel some progress is being made. Not sure where the trouble lies as nobody else seems to be having the same issue with the asrock.
Is there anything else I can provide to be more helpful?
Posts: 1,722
Joined: Sep 2009
Reputation:
20
Ok, the resume script did nothing at all. It simply makes your computer take more time to shut down.
Here's what I'm going to need to take this any further.
Restore all bios settings to factory from inside the sytem bios
and one of the following:
What troubleshooting steps have you taken, which are not posted in this thread?
Post up any devices you have attatched to the computer
Post up any services you have installed on the computer
Can you post copies of the the files which you have modified?
or
do a clean re-install from a XBMC-Live cd.
Posts: 174
Joined: Jul 2008
Reputation:
0
Same behaviour here the ion330 just wakes up right away. and i have to unplug the receiver and plug it back in to get the remote working again.
it's driving me insane.
Posts: 23
Joined: Oct 2008
Reputation:
0
ingeo
Junior Member
Posts: 23
Just wondering if anyone experiencing the immediate wake on suspend issue with the ASRock 330 has found a working solution yet?
When I was running Alpha 1 my system would suspend and stay suspended and I had to enable the proper USB port to wake the system back up.
However since updating to Karmic and Alpha 2 my system will not stay suspended. It doesn't matter if I use the keyboard to navigate to the suspend command in XBMC or use the remote. The system powers down and no more then a second or two later fires right back up again.