Best to warn EC risks
Prerequisites
- [x] I am reporting a bug or feature request in YAMDCC's Readme.
- [x] I have searched the for duplicate issues
- [x] I have answered truthfully to the above questions.
Describe the bug
A EC risk warning may good as well
To Reproduce
Steps to reproduce the behavior:
- Go down the list
- Click on load a config
- Scroll down to config that has same name, but different product code.
- Find your system shutting down after a minute after start
Expected behavior
I hope the warnings can be improved a bit so they inform better, and prevent people from making a mistake
Additional context
(I hope I or others could contribute here as this sort of thing is a waste of devs time, and users if running into issues that could be avoided or resolved quickly)
(I'll try to look at later again within 48 hrs) Here is a 1st draft. Maybe good enough?)
**Warning the Embedded Controller (EC) manages the keyboard, charging, power, cooling, and ?temp reporting iirc? While sometimes it can be recovered by reseting the EC or reflashing
I have used other EC projects like msi-ec, mcontrolcenter, and others.
I suspect my hardware may be having a separate hardware board issue preventing communication from Ec to OS. EC reset were needed more often lately with ryzenadj, uxtu and ghelper. This happens to be first time a EC reset or reflashing the EC doesn't resolve all EC issues. Msi center and ryzenadj were not showing normal values and functioning normally.