OpenELEC / OpenELEC.tv

OpenELEC - The living room PC for everyone
http://openelec.tv
1.6k stars 887 forks source link

Suspend broken on Fusion since R9365 #112

Closed jimbo3 closed 12 years ago

jimbo3 commented 12 years ago

Since R9365 suspend/resume does not work on Fusion computers anymore. Seems to be a (linux) kernel/driver issue. See http://openelec.tv/forum/28-issue-reports/20916

When suspending, computer tries so suspend, but hangs with a black screen and does not switch-off. Only a hard reset or power supply switch off will reboot it. No info in logfiles.

So newer builds cannot be used when you rely on USB remote controls as we need suspend/resume to operate it with remote.

jimbo3 commented 12 years ago

With R9725 it seems to be better, but not solved. After a fresh reboot or startup, I can suspend always my foxconn nt-a3500 via usb remote control. But at resume, sometimes it normally starts, and sometimes it does not startup completely.

When it does not startup completely, the nt-a3500 is switching from standby (flashing red LED) to 'on' (green LED alway on), but no picture on HDMI. Also not possible to ssh or ping the htpc. Only a 'long' push on the power button to reboot the htpc works. After reboot no info in the logs (log starts from reboot).

With older versions (After R9365) it did not suspend, with newer versions it does suspend but does not always resume.

See above mentioned forum topic for more reports.

RogerSch commented 12 years ago

Suspend also doesn't work correctly on an ASUS E45M1-I DELUXE mainboard. (AMD E450 system). Tried multiple OPENELEC Fusion versions (both 32 bit and 64 bit). The incorrect Suspend behaviour various from version to version. Some detected Suspend behaviours:

Also latest Openelec fusion build (OpenELEC-Fusion.x86_64-devel-20120210133025-r9791) tested on a ASUS E45M1-I PRO mainboard. (AMD E450 system). This system has the same incorrect behaviour. Suspend on this system with Windows 7 installed works perfectly.

schumi2004 commented 12 years ago

My guess is is that you both having this problem after upgrading to newer builds? Not on clean installs?

Can you please try this and see if it solves the problem for now?

I used WinSCP for it.

  1. Go to the Storage paratition of OpenELEC
  2. Backup your settings folders .xbmc and .config folder and more if you like.
  3. Check the folder MOUNT. In my case it is a direct mapping to my NAS so don't delete that folder if you will see info in the folder or you will lose data.
  4. Delete all files and folders on the storage partition, except MOUNT folder if there is one.
  5. Restart OpenELEC XBMC. Just remove powerplug and start OpenELEC again.
  6. If everything whent well it is working again.
  7. Restore your folders you backuped to the storage partition again and start XBMC.
  8. I loss some setting for XBMC so maybe you will need to do some configuration again at the end.

Source: http://www.openelec.tv/forum/90-miscellaneous/23761-how-are-the-eden-builds-working-for-you?limit=20&start=20#25688

jimbo3 commented 12 years ago

I did a clean install a few times, and so did others in the mentioned topic without result.

compostbak commented 12 years ago

I did clean instal, also even did a format on the sd card

RogerSch commented 12 years ago

I did also a clean install on a USB HDD with the same results...

compostbak commented 12 years ago

tested

OpenELEC-Fusion.i386-devel-20120215170438-r9824.tar.bz2 OpenELEC-Fusion.x86_64-devel-20120215170728-r9824.tar.bz2

clean install

no improvement

jimbo3 commented 12 years ago

Have just installed the latest OpenELEC-Fusion.x86_64-devel-20120215170728-r9824.tar.bz2 with the same results as before.

After upgrade, startup normally. First time suspend is normally. First time resume also normally. Then suspend, the computer does not suspend, but hangs with a black screen and is not shutting down. SSH unreachable and no info in logs as only a hard reboot will restart it and then logs are cleared.

jimbo3 commented 12 years ago

Upgraded to latest OpenELEC-Fusion.x86_64-devel-20120226092914-r9900.tar.bz2

(on the moment I am writing this, R9900 disappeared from the daily builds, so I think it was removed, it was available for a couple of hours today)

The suspend-bug was still in this version. When suspending, the box 'hangs' with a black screen.

I tried to log during suspend with SSH and a 'tail -f /var/log/messages' and '/var/log/pm-powersave.log'. During suspend nothing is written in pm-powersave.log.

The following is written in /var/log/messages during suspend. The htpc 'hangs' after the last line :

Feb 26 19:21:34 openelec user.notice Boot: ### running addon sleep script /storage/.xbmc/addons//sleep.d/.power (suspend)... ### Feb 26 19:21:34 openelec user.info kernel: [ 355.632880] EXT4-fs (sda1): re-mounted. Opts: barrier=1,data=ordered,commit=0 Feb 26 19:21:34 openelec user.info kernel: [ 355.703285] EXT4-fs (sda2): re-mounted. Opts: barrier=1,data=ordered,commit=0 Feb 26 19:21:35 openelec user.info kernel: [ 356.540029] xhci_hcd 0000:04:00.0: remove, state 4 Feb 26 19:21:35 openelec user.info kernel: [ 356.540053] usb usb9: USB disconnect, device number 1 Feb 26 19:21:35 openelec user.debug kernel: [ 356.540187] xHCI xhci_drop_endpoint called for root hub Feb 26 19:21:35 openelec user.debug kernel: [ 356.540190] xHCI xhci_check_bandwidth called for root hub Feb 26 19:21:35 openelec user.info kernel: [ 356.540336] xhci_hcd 0000:04:00.0: USB bus 9 deregistered Feb 26 19:21:35 openelec user.info kernel: [ 356.540347] xhci_hcd 0000:04:00.0: remove, state 4 Feb 26 19:21:35 openelec user.info kernel: [ 356.540353] usb usb8: USB disconnect, device number 1 Feb 26 19:21:35 openelec user.debug kernel: [ 356.540518] xHCI xhci_drop_endpoint called for root hub Feb 26 19:21:35 openelec user.debug kernel: [ 356.540522] xHCI xhci_check_bandwidth called for root hub Feb 26 19:21:35 openelec user.info kernel: [ 356.550714] xhci_hcd 0000:04:00.0: USB bus 8 deregistered Feb 26 19:21:35 openelec user.info kernel: [ 356.550798] xhci_hcd 0000:04:00.0: PCI INT A disabled Feb 26 19:21:36 openelec user.info kernel: [ 357.262352] HDMI hot plug event: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1 Feb 26 19:21:36 openelec user.info kernel: [ 357.262375] HDMI status: Codec=0 Pin=3 Presence_Detect=1 ELD_Valid=1

Update:

I tried a few times more and sometimes (one out of about every 6 times) suspend is normally setting the pc to standby, but the 'messages' are exactly the same as above.

Can someone tell me what other log file could be interesting to read during suspend ??

taleteller commented 12 years ago

Confirming this Issue for Fusion.i386-devel-20120228175451-r9924 on a Zbox AD10 (E350 device)

The Screen is going black, ssh and samba goes down, but the power keeps on. Only way to get it back alive is a power cycle.

compostbak commented 12 years ago

clean instal OpenELEC-Fusion.x86_64-devel-20120302011655-r9963.tar.bz2

suspend ok, resume just the power light goes on, nothing else.

To bad no improvement. foxconn A3500 ( fusion)

RogerSch commented 12 years ago

Not working Suspend functionality still exists on a ASUS E45M1-De Luxe mainboard. I presume the ATI closed source driver is causing this problem. So we need to wait until ATI fixes this problem. Does anybody know where to report this problem so ATI is aware of it?

taleteller commented 12 years ago

Well I am not too sure about ATI to be the problem. I just made a customized r9965 build using the ati driver 11.10. Tested on my ZBOX AD10: screen goes black, services offline, but power keeps on.

I also noticed the current ATI driver is 11.11 since a few weeks because 12.1 raised other problems.

taleteller commented 12 years ago

Is this about to get addressed? Missing suspend is a real bummer on systems like ZBOX, since they got no remote power on.

jimbo3 commented 12 years ago

Nobody seems to know what is causing the problems. All we know is that it worked until about R9365....

We have asked the developers many times if they are maybe waiting for a linux fix for this, but nobody replied, so we do not know if the have even seen this issue or working on it.

I know that this is beta-software and I do not expect bugfree versions in the daily builds, but some information would be nice. And if developers are working on a fix and need debugging or logfiles, please tell us what to post ...

compostbak commented 12 years ago

clean instal r10027 no improvement

hopely pointing in de right direction we are not alone with this isue https://bugs.launchpad.net/ubuntu/+source/linux/+bug/767975 reed from the botom of the page rumours say new ati (AMD) at the end of the month

taleteller commented 12 years ago

I dug a little deeper into the issue today. First attempt was modifying a actual build redirecting all logs into the storage partition. However, there was no single sign of anything going wrong at all. I discovered that killing Xorg and unloading the fglrx module by hand resulted in a successful power-down when issuing suspend. Therefore its related to fglrx.

Since I got no build from the time it worked, I started to build one myself. Which is far lesser easy than I taught, because most of the code is fetched externally, and some of it is unavailable already. Therefore i had to backport the packages zlib, dbus and the whole mediacenter stuff. At the present moment I got a R9301 'likish version able to suspend flawless.

The present step is to move toward the commit when suspend stopped working. Theoretically we can exclude any XBMC, VDR or DVB related commits to be the problem. Since I have to run a clean build for each step, it will take quite a while to identify the cause.

Personally I mostly suspect the kernel commits. The R9301 build runs under fglrx 11.12, where the actual build has 11.11 and the most recent is 12.1. Therefore suspend already had worked using the presently used driver.

compostbak commented 12 years ago

@Taleteller

older builds http://www.mediafire.com/openelec

build server: http://modelxposure.com:555/ mabey it speeds up your investigations

wish i could help but i am just a niewbie

taleteller commented 12 years ago

@compostbak thanks, that cloud link is useful.

It seems to have work around R9300, about December 19th and stopped before R9317 on December 22th. The most obvious change here is the Upgrade from Kernel 3.1.5 to 3.2.rc6. I will run a build at commit 7f3843929131c0350568f7774bef8b514b30b022 overnight, and I wont be surprised if the bug hides somewhere in the kernel flags from 3.2 onwards.

compostbak commented 12 years ago

@taleteller

If you need somone to test maybe i can help
I have a foxconn A3500 i use for testing Imho ist also bios related if i change something in the bios the behavior is changed Also changing instalation on different media (hardisk, sdcard) has a different behavior

qeustion: is it possible to instal on a sd card, log the resume proces an remove the sd card to read the log files

Ps dutch is my native langeuse, sorry

taleteller commented 12 years ago

@compostbak Sure if i am able to identify the problem, I will publish a link to a patched binary.

On the ZBOX there is not much to be changed in BIOS. I am not part of the OpenELEC team myself, I am just bothered by the bug and pretty familiar with linux.

compostbak commented 12 years ago

I wil hope that you wil find problem because OE is useles fore me at the moment and i don,t want to go to a windows system Please report your progress. if can help, dont hasitate to ask.

compostbak commented 12 years ago

@Taleteller

mayby nothing, mayby intresting.

http://forum.xbmc.org/showthread.php?t=121158&highlight=kernel+3.2

taleteller commented 12 years ago

Looks like it is an issue between kernel 3.2+ and the fglrx proprietary driver. It cannot be fixed by compiling the kernel with different flags. I also found a bug on ubuntu pointing toward the kernel.

https://bugs.launchpad.net/ubuntu/+source/linux/+bug/908268

I guess it might take some time before a fix gets available.

RogerSch commented 12 years ago

Hi Taleteller, thank you for the effort. I think in the end AMD need to fix this in FGLRX. So we need somehow to address to ATI. This is also one to the drawbacks of proprietary software;, the open source community can't solve the problems.

Isn't there a work around possible that all services and drivers are shutdown but not the power to the USB port? So you could still remotly power up the Fusion system. (I've no problem in a cold boot as OpenElec is then still faster in powering up than my LCD tv...)

taleteller commented 12 years ago

While experimenting, I killed Xorg from the console, removed fglrx by hand, and issued the suspend by command. Doing so, results in powering down the box. Sadly its not possible to wake it up correctly, network wont come up.

My "Workaround" will be to use, the R9301 build with a few tweaks. For example, the TARGET_CPU, and PROJECT_CFLAGS settings were ineffective and produced high load these days.

USB wakeup should be possible with most boards, but USB IR receivers typically dont issue a powerup.

jimbo3 commented 12 years ago

Do we need kernel > 3.2 ?? Would it be possible to build the latest versions with the last working kernel ?

jimbo3 commented 12 years ago

@taleteller: In comment # 14 on the ubuntu link you quoted "Rich" writes "Not had time to report an upstream bug yet, but suffice to say that I installed the latest proprietary fglrx driver packages direct from AMD's site using the --buildpkg switch (file downloaded was called "amd-driver-installer-12-1-x86.x86_64.run") and I got a successful suspend/resume using this driver/module."

Is it possible to use this driver also in OpenElec ?

taleteller commented 12 years ago

@jimbo3 Driver 12.1 was pretty bugged, Its not even linked on the ATI site anymore.

Its not necessary to have Kernel 3.2, but getting 3.1.x working with the present git might turn into a lot of manual patching. Even more when needing the PVR builds.

compostbak commented 12 years ago

is this the new driver for 12.2 ??

http://support.amd.com/us/gpudownload/linux/Pages/radeon_linux.aspx

look at the release date maybe worht a shot

cannot find any release log

taleteller commented 12 years ago

Indeed! I will try a shot.

taleteller commented 12 years ago

The first quick attempt, looked pretty good. I built the 12.2 driver into the already compiled "R9307" checkout. I successfully put the system three times into S3 and back with it!

For tonight i will patch it against a clean head checkout, and test it tomorrow.

Funny enough, I checked for the 12.2 this morning, and it wasnt released yet. Doh!

compostbak commented 12 years ago

Lets hope you can make us all happy

I think a lot of people waiting fore working system

Please report your progres minut by minut

RogerSch commented 12 years ago

Greate progress!

taleteller commented 12 years ago

Funny enough sraue was as fast as me with the fglrx driver. However I had to patch it to get it compiled with x86: http://www.mediafire.com/?ua89soxp5u62har

And this is the binary I got: http://www.mediafire.com/?xhtj23it205f4cp

Suspend now works fine for me.

compostbak commented 12 years ago

clean instal OpenELEC-Fusion.x86_64-devel-20120308070355-r10034.tar.bz2

NOT working

foxconn a3500

compostbak commented 12 years ago

OpenELEC-Fusion.x86_64-devel-20120308161437-r10049.tar.bz2

suspend ok resume: give black screen

with hd activetie and can acces ssh doesnt react on remote after resumeing Foxcon A3500 HD 2,5 0.5 Tb 4 GiG mem

taleteller commented 12 years ago

Have you tried to disable C6-Mode in BIOS? I have heard it might help.

compostbak commented 12 years ago

tested some more on 10049

sometimes suspend/resume works 4-5 times in a row then fails to resume
after faling to resume with remote pressing button on a attached keyboard the system resume again, sometimes to xbmc gui other times only to black screen without ssh usb is awake always, i have a led indication in usb reciever which flicker when i push a button on the remote even when the system is not reacting on the resume function i see the led flickering

@ taleteller
disable ever thing except fore : usb2 port s3 wakeup usb2 port s4 wakeup

also thright only : usb2 port s3 wakeup everything else disabeld

what can i test more to give more information

taleteller commented 12 years ago

@compostbak

I really cant say. I once had similar wakeup issues with a ZBOX AD02, the "big" brother of the AD10. In my case the (original Microsoft) USB IR-Receiver was problematic. It also helped to disable the light-effect,which the A3500 afaik dont have.

compostbak commented 12 years ago

Tested OpenELEC-Fusion.x86_64-devel-20120309124526-r10068.tar.bz2 bios, al settings disabeled except usb2 port s3 wakeup

clean instal on harddisk 500 gig suspend/resume 3 times before failing to black screen kingston SD 4 gig class 6 sd card suspend/resume 3 times before failing to black screen cheap sd card from old tomtom device suspend/resume 4 times before failing to black screen

RogerSch commented 12 years ago

Tested OpenELEC-Fusion.x86_64-devel-20120309124526-r10068 on an Asus E45M1-M DELUXE, 4GB Ram, 1TB HD.

Configured XBMC to go into suspend mode when the powering down. Using the power button on an USB MCE remote I can switch on and off the system 4 times. There after it stays in suspend mode. Although I can get the system out of suspend mode by pressing the space bar on a remote Logitech Keyboard. When I thereafter issue a reboot command in XBMC, the system hangs immediately after power up. I need to remove the power cord briefly before the system boots up again.

So bottom line: It's getting better but it is still not usable in a normal "family condition"...

Isn't it possible to create a kind of work around where the system, after it powers up out of suspend mode does a complete restart. Just like when the system identifies a new version in the Update directory? In that case it copies the kernel and system file and does a complete restart... Of course there is a clear drawback that the boot time is much longer (but in my case it should be still quicker than my LCD is powered up...).

taleteller commented 12 years ago

Those issues sound like more related to linux power management itself than openelec, but I am not sure. Have you ever tried to test it on a distribution like ubuntu?

What I noticed is, the openelec image lacks of vbetool, and I am also not sure how pm-utils is handling the video-quirks without it.

compostbak commented 12 years ago

tested OpenELEC-Fusion.x86_64-devel-20120318025803-r10162.tar.bz2 clean instal on harddisk: after 3 times cycle suspend resume fails (black screen) on 4 gig sd card : aprx. 10 times cycle before fail (black screen)

1 time i had a faling screen but hd activitie and putty acces made a log file

sorry couldnt not reproduce

log file:

login as: root ##############################################

OpenELEC - The living room PC for everyone

...... visit http://www.openelec.tv ......

##############################################

OpenELEC Version: devel-20120318025803-r10162 OpenELEC git: 2e66a869ada2aaad69635bacdec3f9e15d22dabb root@192.168.1.50's password: root ~ # cat /var/log/pm-suspend.log Initial commandline parameters: Sun Mar 18 09:30:01 UTC 2012: Running hooks for suspend. Running hook /etc/pm/sleep.d/00addon-sleep suspend suspend: sh: /storage/.xbmc/addons//sleep.d/_.power: No such file or directory

/etc/pm/sleep.d/00_addon-sleep suspend suspend: success. Running hook /usr/lib/pm-utils/sleep.d/00logging suspend suspend: Linux openelec 3.2.11 #1 SMP Sat Mar 17 04:16:16 CET 2012 x86_64 GNU/Linux Module Size Used by xhci_hcd 75514 0 fglrx 3147740 59 ath9k 85237 0 snd_hda_codec_realtek 189470 1 ath9k_common 1778 1 ath9k ath9k_hw 338578 2 ath9k_common,ath9k snd_hda_codec_hdmi 22825 1 snd_hda_intel 22027 0 snd_hda_codec 73075 3 snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_realtek ath 14203 3 ath9k_hw,ath9k_common,ath9k snd_hwdep 5477 1 snd_hda_codec snd_pcm 64260 3 snd_hda_codec,snd_hda_intel,snd_hda_codec_hdmi snd_timer 18026 1 snd_pcm snd 47796 7 snd_timer,snd_pcm,snd_hwdep,snd_hda_codec,snd_hda_intel,snd_hda_codec_hdmi,snd_hda_codec_realtek snd_page_alloc 6689 2 snd_pcm,snd_hda_intel uvesafb 20780 3 total used free shared buffers Mem: 3656252 437596 3218656 0 51180 -/+ buffers: 386416 3269836 Swap: 0 0 0

/usr/lib/pm-utils/sleep.d/00logging suspend suspend: success. Running hook /usr/lib/pm-utils/sleep.d/00powersave suspend suspend:

/usr/lib/pm-utils/sleep.d/00powersave suspend suspend: success. Running hook /usr/lib/pm-utils/sleep.d/01grub suspend suspend:

/usr/lib/pm-utils/sleep.d/01grub suspend suspend: success. Running hook /usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend:

/usr/lib/pm-utils/sleep.d/49bluetooth suspend suspend: success. Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend: Having NetworkManager put all interaces to sleep...Done.

/usr/lib/pm-utils/sleep.d/55NetworkManager suspend suspend: success. Running hook /etc/pm/sleep.d/61_xbmc_lirc suspend suspend: Sending action: LIRC.Stop

/etc/pm/sleep.d/61_xbmc_lirc suspend suspend: success. Running hook /etc/pm/sleep.d/62_xbmc_lcd suspend suspend: Sending action: LCD.Suspend

/etc/pm/sleep.d/62_xbmc_lcd suspend suspend: success. Running hook /usr/lib/pm-utils/sleep.d/75modules suspend suspend: Unloading kernel module xhci-hcd...Done. Unloading kernel module jme...Done. Unloading kernel module anysee...Done. Unloading kernel module rtl8192se...Done. Unloading kernel module imon...Done.

/usr/lib/pm-utils/sleep.d/75modules suspend suspend: success. Running hook /etc/pm/sleep.d/90_autoupdate suspend suspend:

/etc/pm/sleep.d/90_autoupdate suspend suspend: success. Running hook /usr/lib/pm-utils/sleep.d/90clock suspend suspend:

/usr/lib/pm-utils/sleep.d/90clock suspend suspend: success. Running hook /usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend:

/usr/lib/pm-utils/sleep.d/94cpufreq suspend suspend: success. Running hook /usr/lib/pm-utils/sleep.d/95led suspend suspend:

/usr/lib/pm-utils/sleep.d/95led suspend suspend: success. Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: ATI Catalyst driver detected, not using quirks.

/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler suspend suspend: success. Running hook /etc/pm/sleep.d/99_reload_skin suspend suspend:

/etc/pm/sleep.d/99_reload_skin suspend suspend: success. Running hook /usr/lib/pm-utils/sleep.d/99video suspend suspend: kernel.acpi_video_flags = 0

/usr/lib/pm-utils/sleep.d/99video suspend suspend: success. Sun Mar 18 09:30:04 UTC 2012: performing suspend Sun Mar 18 09:30:11 UTC 2012: Awake. Sun Mar 18 09:30:11 UTC 2012: Running hooks for resume Running hook /usr/lib/pm-utils/sleep.d/99video resume suspend:

/usr/lib/pm-utils/sleep.d/99video resume suspend: success. Running hook /etc/pm/sleep.d/99_reload_skin resume suspend:

/etc/pm/sleep.d/99_reload_skin resume suspend: success. Running hook /usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend:

/usr/lib/pm-utils/sleep.d/98video-quirk-db-handler resume suspend: success. Running hook /usr/lib/pm-utils/sleep.d/95led resume suspend:

/usr/lib/pm-utils/sleep.d/95led resume suspend: success. Running hook /usr/lib/pm-utils/sleep.d/94cpufreq resume suspend:

/usr/lib/pm-utils/sleep.d/94cpufreq resume suspend: success. Running hook /usr/lib/pm-utils/sleep.d/90clock resume suspend:

/usr/lib/pm-utils/sleep.d/90clock resume suspend: success. Running hook /etc/pm/sleep.d/90_autoupdate resume suspend:

/etc/pm/sleep.d/90_autoupdate resume suspend: success. Running hook /usr/lib/pm-utils/sleep.d/75modules resume suspend: Reloaded unloaded modules.

/usr/lib/pm-utils/sleep.d/75modules resume suspend: success. Running hook /etc/pm/sleep.d/62_xbmc_lcd resume suspend: Sending action: ReloadSkin() Sending action: LCD.Resume

/etc/pm/sleep.d/62_xbmc_lcd resume suspend: success. Running hook /etc/pm/sleep.d/61_xbmc_lirc resume suspend: Sending action: LIRC.Start

/etc/pm/sleep.d/61_xbmc_lirc resume suspend: success. Running hook /usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend: Having NetworkManager wake interfaces back up...Done.

/usr/lib/pm-utils/sleep.d/55NetworkManager resume suspend: success. Running hook /usr/lib/pm-utils/sleep.d/49bluetooth resume suspend:

/usr/lib/pm-utils/sleep.d/49bluetooth resume suspend: success. Running hook /usr/lib/pm-utils/sleep.d/01grub resume suspend:

/usr/lib/pm-utils/sleep.d/01grub resume suspend: success. Running hook /usr/lib/pm-utils/sleep.d/00powersave resume suspend:

/usr/lib/pm-utils/sleep.d/00powersave resume suspend: success. Running hook /usr/lib/pm-utils/sleep.d/00logging resume suspend:

/usr/lib/pm-utils/sleep.d/00logging resume suspend: success. Running hook /etc/pm/sleep.d/00addon-sleep resume suspend: sh: /storage/.xbmc/addons//sleep.d/_.power: No such file or directory

/etc/pm/sleep.d/00_addon-sleep resume suspend: success. Sun Mar 18 09:30:13 UTC 2012: Finished.

compostbak commented 12 years ago

clean install

r 10254 r 10247 no improvement bummer

RogerSch commented 12 years ago

Installed OpenELEC-Fusion.x86_64-devel-20120402145419-r10416 version and it seems that suspend (tested about ten times after each other) now works correctly on my ASUS E45M1-I DELUXE mainboard. (AMD E450 system)

compostbak commented 12 years ago

clean install on harddisk OpenELEC-Fusion.x86_64-devel-20120402145419-r10416

no improvement here still hanging on resume after 2-3 cycle

foxconn a-3500

taleteller commented 12 years ago

@compostbak

as i mentioned before, have you tried suspend in a mainstream distro like ubuntu? I am not sure if openelec is the cause of your problems, since its working pretty fine for most systems.

jimbo3 commented 12 years ago

I did not have a 'hang' since versions of march 2012 (around 10049 I think) and I tried many times to suspend and resume.

And I am using also a foxconn A-3500 like compostbak. The only difference is the TV and harddisk. I am using only a SD card for the program and all my data is on a samba network disk. My TV is JVC HD-Ready 1080i (or 720P).

I only had a problem with upgrading to the latest version. After that the screen was black and a segmentation fault in the Xorg log. Also using the older versions which worked before did not solve this. After deleting the /Configfiles/fglrx.conf and /Userdata/guisettings.xml userfile all was normal again.

compostbak commented 12 years ago

@jimbo3, just tried clean install on sd card (hardisk removed) stil having the problems what kind of system memory ( size, brand) do you have in your system??

hopefuly in the new kernel there are alot of fixes fore resume iseu,s http://www.kernel.org/pub/linux/kernel/v3.0/ChangeLog-3.3.1

@taleteller, tried ubuntu same problem.

bummer bummer bummer