You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
DTS print scary errors in red without providing any guideance for users what to do next.
How reproducible
Always when doing initial deployment.
How to reproduce
Boot DTS with USB
Enter DES keys/password, choose to Install Dasharo / option 'd' for DESchoose
Expected behavior
If DTS encounters an error path, it should provide guidance on what to do in such a situation. We should provide protection and detection mechanisms and a recovery path for the problems we face during deployment.
In case of not disabled ME, the point is that we should not proceed with an update of ME while it is running since it can lead to unexpected behavior (even bricking if I hang the platform during BIOS region flashing). We should not just print, The firmware binary contains Management Engine (ME), but ME is not disabled! We should say what to do next.
According to the discussion on Matrix, one way to proceed is M-Flash, which disables ME and deploys the binary, but it is just for Z690. Currently, DTS is not capable of deploying DES binaries, which is a critical issue.
Actual behavior
Currently, DTS prints scary messages like the one in the title, with which users have no idea what to do with.
Screenshots
No response
Additional context
Such bugs lead to a rise in support tickets and a loss of focus by the Dasharo Team.
Solutions you've tried
No response
The text was updated successfully, but these errors were encountered:
Component
Dasharo Tools Suite
Device
MSI Pro Z690-A
Dasharo version
No response
Dasharo Tools Suite version
v1.2.21
Brief summary
DTS print scary errors in red without providing any guideance for users what to do next.
How reproducible
Always when doing initial deployment.
How to reproduce
Expected behavior
If DTS encounters an error path, it should provide guidance on what to do in such a situation. We should provide protection and detection mechanisms and a recovery path for the problems we face during deployment.
In case of not disabled ME, the point is that we should not proceed with an update of ME while it is running since it can lead to unexpected behavior (even bricking if I hang the platform during BIOS region flashing). We should not just print,
The firmware binary contains Management Engine (ME), but ME is not disabled!
We should say what to do next.According to the discussion on Matrix, one way to proceed is M-Flash, which disables ME and deploys the binary, but it is just for Z690. Currently, DTS is not capable of deploying DES binaries, which is a critical issue.
Actual behavior
Currently, DTS prints scary messages like the one in the title, with which users have no idea what to do with.
Screenshots
No response
Additional context
Such bugs lead to a rise in support tickets and a loss of focus by the Dasharo Team.
Solutions you've tried
No response
The text was updated successfully, but these errors were encountered: