New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disk hibernation not working #489
Comments
Please do a test, return to loader, go to advanced menu, change the LKM from DEV to PROD, rebuild the loader and test again. |
I use https://github.com/wjz304/Redpill_CustomBuild Built. The default lkm used is redpill |
The LKM from DEV to PROD has been compiled and modified sed -i 's//var/log/scemd.log//tmp/scemd.log/g' /etc.defaults/syslog-ng/patterndb.d/scemd.conf Observe whether to hibernate after setting hibernation and restarting |
Changed LKM from Dev to PROD. In "/var/log/scemd.log", "/var/log/kern.log" and "in/var/log/messages" spam the following errors: scemd.log:
messages:
kern.log:
I think they are not critical and they can be hidden using filters in /etc.defaults/syslog-ng/patterndb.d/ |
I tested it and still can't |
mother asrock j4125 installed arpl v1.0-beta10, DSM 7.1.1 buil 42962
along the way /var/log/messages spams errors every minute, because of this it does not go into hibernation... Any ideas what the problem is and how to win?
root@HomeNasSynology:~# tail -f /var/log/messages 2023-01-11T00:49:26+03:00 HomeNasSynology kernel: [ 7652.126309] <redpill/pmu_shim.c:234> Unknown 1 byte PMU command with signature hex="44" ascii="D" 2023-01-11T00:49:27+03:00 HomeNasSynology kernel: [ 7652.367854] synobios get empty ttyS current 2023-01-11T00:50:27+03:00 HomeNasSynology kernel: [ 7712.858896] <redpill/pmu_shim.c:234> Unknown 1 byte PMU command with signature hex="44" ascii="D" 2023-01-11T00:50:27+03:00 HomeNasSynology kernel: [ 7713.100187] synobios get empty ttyS current 2023-01-11T00:51:28+03:00 HomeNasSynology kernel: [ 7773.588841] <redpill/pmu_shim.c:234> Unknown 1 byte PMU command with signature hex="44" ascii="D"
The text was updated successfully, but these errors were encountered: