heyredy141 Posted November 1, 2013 Share #26 Posted November 1, 2013 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. Quote Link to comment Share on other sites More sharing options...
Rand__ Posted November 1, 2013 Share #27 Posted November 1, 2013 Do they work if you call them manually? I.e. ssh in (eg via putty), login with root user (with admin user pw), then run command. It shuts down ok for me after a minute or two Quote Link to comment Share on other sites More sharing options...
heyredy141 Posted November 2, 2013 Share #28 Posted November 2, 2013 Thanks that worked when I did it through ssh and it also worked this time when I did through power button. Last time there must have been some operation that was holding it from shutting down. Quote Link to comment Share on other sites More sharing options...
Djey Posted November 4, 2013 Share #29 Posted November 4, 2013 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! Thanks for great solution and explanations I'm definitively looking for such a feature with xpenology hosted in ESXi, I'll try it and report Quote Link to comment Share on other sites More sharing options...
Schmill Posted November 20, 2013 Share #30 Posted November 20, 2013 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 Quote Link to comment Share on other sites More sharing options...
Mentat Posted November 22, 2013 Share #31 Posted November 22, 2013 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? Quote Link to comment Share on other sites More sharing options...
Schmill Posted November 23, 2013 Share #32 Posted November 23, 2013 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. Quote Link to comment Share on other sites More sharing options...
Mentat Posted November 23, 2013 Share #33 Posted November 23, 2013 What I do not know is IF button.ko is allready installed or not. There is no instruction about this... Quote Link to comment Share on other sites More sharing options...
Mentat Posted November 23, 2013 Share #34 Posted November 23, 2013 button.co is in /lib/modules, but i get acpid: /proc/acpi/event: No such file or directory in /var/log/acpid.log btw, I'm using 4.3 viewtopic.php?f=14&t=1700 I think the acpid file (renamed busybox) is not correct. I even use my busybox, but no luck here. Quote Link to comment Share on other sites More sharing options...
darkest_star Posted November 25, 2013 Share #35 Posted November 25, 2013 What I do not know is IF button.ko is allready installed or not. There is no instruction about this... Simply check with: lsmod | grep button If this command gives you a line containing "button" the module is loaded (if no line appears button.ko isn't loaded). Quote Link to comment Share on other sites More sharing options...
Mentat Posted November 25, 2013 Share #36 Posted November 25, 2013 lsmod | grep button button 4107 0 Quote Link to comment Share on other sites More sharing options...
darkest_star Posted November 25, 2013 Share #37 Posted November 25, 2013 lsmod | grep button button 4107 0 This means, the button.ko is aleady loaded. Quote Link to comment Share on other sites More sharing options...
darkest_star Posted November 25, 2013 Share #38 Posted November 25, 2013 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? Quote Link to comment Share on other sites More sharing options...
Mentat Posted November 25, 2013 Share #39 Posted November 25, 2013 Trantor - the only 4.3 DSM build now viewtopic.php?f=14&t=1700 Quote Link to comment Share on other sites More sharing options...
Trantor Posted December 15, 2013 Share #40 Posted December 15, 2013 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 Quote Link to comment Share on other sites More sharing options...
darkest_star Posted December 19, 2013 Share #41 Posted December 19, 2013 AFAIK the acpid-enabled busybox seems not to be the problem. The kernel needs to be compiled with acpid enabled. Is it possible to start the acpid on a 4.3 system? Quote Link to comment Share on other sites More sharing options...
gebing Posted January 13, 2014 Share #42 Posted January 13, 2014 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? Quote Link to comment Share on other sites More sharing options...
gebing Posted January 13, 2014 Share #43 Posted January 13, 2014 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? Quote Link to comment Share on other sites More sharing options...
Trantor Posted January 14, 2014 Share #44 Posted January 14, 2014 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 Quote Link to comment Share on other sites More sharing options...
gebing Posted January 15, 2014 Share #45 Posted January 15, 2014 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? Quote Link to comment Share on other sites More sharing options...
darkest_star Posted January 16, 2014 Share #46 Posted January 16, 2014 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. Quote Link to comment Share on other sites More sharing options...
gebing Posted January 16, 2014 Share #47 Posted January 16, 2014 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. Quote Link to comment Share on other sites More sharing options...
Trantor Posted January 16, 2014 Share #48 Posted January 16, 2014 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 Quote Link to comment Share on other sites More sharing options...
darkest_star Posted January 17, 2014 Share #49 Posted January 17, 2014 I can confirm you that CONFIG_ACPI_PROC_EVENT=y is build in beta v3 et v4 And with that Kernel you really get no events in /proc/acpi/event by pressing the power button on bare metal installation? Quote Link to comment Share on other sites More sharing options...
gebing Posted January 19, 2014 Share #50 Posted January 19, 2014 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 ? Quote Link to comment Share on other sites More sharing options...
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.