darkest_star

Hello all, Since 2013 I've used 4.2.3211++ (repack v1.2) for my NAS without any problem. Today I have done a new installation of 5.2 with new disks for the volume. Now I have the same problem again: My power button is not working. I've read all the posts in the meantime from 2013 until now to see whats the current state. Because on my system /proc/acpi/events is not present. I have loaded button.ko and evdev.ko. Without the /proc/acpi/event acpid will not work. Is this a known problem?

Until this is not working we don't need to take care about the usermode program acpid (or busybox-acpid). In DSM 4.3 v1.0 I've seen, that CONFIG_ACPI_PROCFS is not configured. So, could please enable the follwing parameters: CONFIG_ACPI_PROCFS=y CONFIG_ACPI_PROC_EVENT=y CONFIG_ACPI_PROCFS_POWER=y Respectively please set the CONFIG_ACPI_* parameters to the same values as in the working DSM 4.2 Kernel. Thank you very much.

And with that Kernel you really get no events in /proc/acpi/event by pressing the power button on bare metal installation?

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.

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?

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?

This means, the button.ko is aleady loaded.

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).

Would be also my suggestion. If you have such problems try to connect via ssh and shut down the system via the known poweroff commands.

Depends on what you mean with freeze. If only the webservices freezes maybe that the powerbutton shutdown may work. What do you exactly mean with "freezes'?

After some tests and after reading on the internet "syno_poweroff_feasible_check" seems to be a more save way to shutdown the system. As far as I understand it would prevent shutting down, if e.g. backup operations are still running. So, I would also vote for replacing "poweroff" with "syno_poweroff_feasible_check" in the acpid-configure script /etc/acpi/PWRF/00000080. But nevertheless, I had not observed any problems with the simple "poweroff".

From my point of view the 'poweroff' command really does a graceful shutdown of the system. If I press the button I see, that my HDD LEDs are flickering and after a while one after another is powered off. The shutdown (from pressing power button until power-off) takes around 20-30 seconds. Btw, I have a hybrid RAID with 3 disks and after a poweroff with the button I never had a problem with my RAID. There was never a complain caused by a "hard" power off. But I didn't knew the special shutdown commands (syno_poweroff_feasible_check and/or syno_poweroff_task) and would test it with them today evening.

Habs jetzt bei mir soweit hinbekommen und hier im englischen Forum beschrieben: viewtopic.php?f=2&t=889#p7305 Ich hoffe, es ist kein Fehler in meiner Beschreibung ...

Here is my solution for this issue: powering off the DiskStation by shortly pressing the power button. I'm using 4.2.3211++ (repack v1.2) natively installed. If you want to follow these steps, do it as user root! I have packed all my file to a tar-file, which can be downloaded here: https://www.dropbox.com/s/tzg9n0336zqez79/acpid-files.tar 1. Make button.ko loaded automatically - open /etc/rc for editing - search for the first occurence of the environment variable KERNEL_MODULES and put 'button' at the end of the string. 2. Install a acpid daemon - For this I have rebuilt the busybox with enabled acpid. Since I'm not sure, if the other busybox features are correctly working with my own built busybox, I'm using it only as acpid. The acpid in the download package is simply a renamed busybox. - copy acpid to /bin as user root and check that it's executable. Should look like this: DiskStation> ll /bin/acpid -rwxr-xr-x 1 root root 536592 Oct 27 18:08 /bin/acpid 3. Install a acpid start/stop script - create an startup script /usr/syno/etc/rc.d/S30acpid.sh #!/bin/sh # # This goes in /usr/syno/etc/rc.d and gets run at boot-time. PATH_ACPID=/bin/acpid case "$1" in start) if [ -x "$PATH_ACPID" ] ; then echo "start acpid" $PATH_ACPID fi ;; stop) echo "stop acpid" killall acpid > /dev/null 2>&1 logger -p daemon.error "$0 stopped acpid" ;; *) echo "usage: $0 { start | stop }" >&2 exit 1 ;; esac - check that it's executable. Should look like this: DiskStation> ll /usr/syno/etc/rc.d/S30acpid.sh -rwxr-xr-x 1 root root 359 Oct 29 20:45 /usr/syno/etc/rc.d/S30acpid.sh 4. Add a acpid event config - Finally add a acpid config file for the power button event /etc/acpi/PWRF/00000080 #!/bin/sh poweroff - also here: check it's owned by root and executable: DiskStation> ll /etc/acpi/PWRF/00000080 -rwxrwxrwx 1 root root 20 Oct 17 22:28 /etc/acpi/PWRF/00000080 Finally reboot your box. 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!

@Rand__: Thank you! I know acpid from every Linux distribution I've used. But I was wondering that it's not already included to the XPEnology releases. I'm currently setting up a build machine and will build the missing binary.