mirror of
https://github.com/007revad/Synology_HDD_db.git
synced 2026-04-25 13:45:59 +03:00
[GH-ISSUE #136] DVA memory warning #560
Labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/Synology_HDD_db#560
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @gitthangbaby on GitHub (Aug 21, 2023).
Original GitHub issue: https://github.com/007revad/Synology_HDD_db/issues/136
DVA3219 VM spam:
"Detected non-Synology recommended memory module configurations."
No matter what is set:
sed -i "s/support_memory_compatibility="no"/support_memory_compatibility="yes"/" /etc.defaults/synoinfo.conf
sed -i "s/support_memory_compatibility="yes"/support_memory_compatibility="no"/" /etc.defaults/synoinfo.conf
sed -i "s/support_memory_compatibility="no"/support_memory_compatibility="yes"/" /etc/synoinfo.conf
sed -i "s/support_memory_compatibility="yes"/support_memory_compatibility="no"/" /etc/synoinfo.conf
Here people believe opposite settings is good for DVA:
https://github.com/fbelavenuto/arpl/issues/307
Another annoyance is nonstop nvidia warning: "NVRM: No NVIDIA graphics adapter found!" in dmesg
Hope someone knows what's special about DVA.
@007revad commented on GitHub (Aug 21, 2023):
Your sed commands need to escape the " around the yes and no, otherwise sed fails to edit support_memory_compatibilty.
sed -i "s/support_memory_compatibility="\no\"/support_memory_compatibility="\yes\"/" /etc/synoinfo.confBut there is an easier way to disable support_memory_compatibility:
Or to enable support_memory_compatibility:
And to check the values:
@gitthangbaby commented on GitHub (Aug 21, 2023):
Sorry, the backslash was removed as I pasted it without code.
Still, in both ways the message stays there. By doing manually, by using -r switch, by using loader settings. No matter how it's set, after the boot the message is there.
post-boot
-> Detected non-Synology recommended memory module configurations. You may have
-> Detected non-Synology recommended memory module configurations. You may have
@gitthangbaby commented on GitHub (Aug 21, 2023):
Conclusion: -r sets 'no'. Reportedly, DVAs requires 'yes'. In my report, both don't work. Proposal that works:
/usr/lib/systemd/system/SynoMemCheck.service
ExecStart=/bin/true@007revad commented on GitHub (Aug 21, 2023):
So you edited /usr/lib/systemd/system/SynoMemCheck.service to replace ExecStart=/usr/syno/bin/syno_mem_check with ExecStart=/bin/true ?
@gitthangbaby commented on GitHub (Aug 21, 2023):
Correct, because i could not disable the service, it would come up like many other things in DSM. Looks like /bin/true is used in 10 other services already, quite popular.
@007revad commented on GitHub (Aug 22, 2023):
Fixed in Release v3.1.63