Power off from the buttom


Recommended Posts

For me only power off command is working and i couldn't get syno_poweroff_feasible_check OR syno_poweroff_task commands to work. Am I doing something wrong? I replaced power off with either of those and rebooted and tried powering off by pressing the power button and it didn't work.

Link to post
Share on other sites
Now you could safely shutdown your box by pressing the power button. For a vSphere based XPenology system it should now be possible that the system will be shutdown when the ESXi is shutting down. But this I haven't tested.

Hope it helps you too! :smile:

Thanks for great solution and explanations :wink:

 

I'm definitively looking for such a feature with xpenology hosted in ESXi, I'll try it and report :mrgreen:

Link to post
Share on other sites
  • 3 weeks later...

So which is the command that has been setttled on that should be called?

 

I am unclear on the difference between "syno_poweroff_feasible_check" and "syno_poweroff_task", although I understand both are better than calling the standard "poweroff".

 

Thanks :smile:

Link to post
Share on other sites
This should work for any configuration?

It does not work on my GA-C1037UN EU.

 

How can I check for possible malfunctions in the code?

 

Start in the same way as darkest_star; press the power button and look for an event. If none the install the module and try again. Work your way through darkest_star's steps and see where it stops being the same.

Link to post
Share on other sites
  • 3 weeks later...
Sorry, I haven't realized that you are using 4.3.

 

If /proc/acpi/event is not present then the kernel has no acpi support enabled. I think the kernel needs to be recompiled with:

CONFIG_ACPI=y

 

:???:

Who has build your kernel respectively what package you are using?

 

I will include this on v1.1, but I need your busybox with enabled acpid for 4.3 :geek:

Link to post
Share on other sites
  • 4 weeks later...

I tried in Xpenology DS3612xs DSM 4.3 build 3810 pre V1.1 V4, and it seems build with ACPI enabled, but when i pressed the power button, nothing happened.

 

I checked whether button.ko is loaded by "lsmod | grep button", and it returns "button 4107 0" and it seems button.ko is loaded.

 

I checked by "cat /proc/acpi/event", it is empty and has no content even after i press power button, so acpid can not be triggered when power button is pressed.

 

So, what's the problem? Can anyone give some advise?

Link to post
Share on other sites

Maybe should compile kernel with ACPI_PROC_EVENT flag according to https://github.com/andy928/xpenology/bl ... pi/Kconfig

 

Or use acpid2 instead of acpid? According to website of acpid2 (http://sourceforge.net/projects/acpid2/), it use netlink and the input layer instead of deprecated /proc/acpi/event interface. But how can i build a binary package of acpid2?

Link to post
Share on other sites
Maybe should compile kernel with ACPI_PROC_EVENT flag according to https://github.com/andy928/xpenology/bl ... pi/Kconfig

 

Or use acpid2 instead of acpid? According to website of acpid2 (http://sourceforge.net/projects/acpid2/), it use netlink and the input layer instead of deprecated /proc/acpi/event interface. But how can i build a binary package of acpid2?

 

Download the acpi2 sources and cross compil them.

Use synology delevoper guide : http://ukdl.synology.com/download/ds/us ... _Guide.pdf

Use this tool chain : http://sourceforge.net/projects/dsgpl/f ... z/download

Link to post
Share on other sites

I download toolchain and source for acpid2, but it failed. Because acpid2 require glibc 2.5 and include some function in glibc 2.5, such as inotify_init in inotify.h.

 

Can anyone give some advisement? Can I install new version glibc to DSM without replace old glibc 2.3.6?

Link to post
Share on other sites

Maybe darkest_star is right.

 

I try to build a special version acpid2 to use specific libc.so.6 and ld-linux-x86-64.so.2 of the lastest version, and successfully run on my DSM 4.3 build 3810 pre V1.1 V4, and it can not get any ACPI events.

Link to post
Share on other sites
Maybe should compile kernel with ACPI_PROC_EVENT flag according to https://github.com/andy928/xpenology/bl ... pi/Kconfig

 

That is also my understanding: The kernel doesn't triggers the ACPI events. The busybox-acpid provided by me seems not to be the problem.

So, we need to recompile the kernel with ACPI_PROC_EVENT enabled.

 

I can confirm you that CONFIG_ACPI_PROC_EVENT=y is build in beta v3 et v4

Link to post
Share on other sites
Maybe should compile kernel with ACPI_PROC_EVENT flag according to https://github.com/andy928/xpenology/bl ... pi/Kconfig

 

That is also my understanding: The kernel doesn't triggers the ACPI events. The busybox-acpid provided by me seems not to be the problem.

So, we need to recompile the kernel with ACPI_PROC_EVENT enabled.

 

I can confirm you that CONFIG_ACPI_PROC_EVENT=y is build in beta v3 et v4

 

I seems wired. IS there any other method to test whether APCI is work properlu ?

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.