Provide solutions when printing warnings

[PLangowski]

Dasharo/dasharo-issues#859

[PLangowski]

@miczyg1 When ME is not disabled, we tell the user to use FlashBIOS https://docs.dasharo.com/guides/firmware-update/#known-issues.
What about The firmware binary to be flashed contains Management Engine (ME), but ME is not writable!? Is the solution identical here?

[miczyg1]

@miczyg1 When ME is not disabled, we tell the user to use FlashBIOS https://docs.dasharo.com/guides/firmware-update/#known-issues. What about The firmware binary to be flashed contains Management Engine (ME), but ME is not writable!? Is the solution identical here?

One can use FlashBIOS or simply use FUM and boot to DTS shell and flash the binary manually. The latter will work on any platform.

[PLangowski]

@miczyg1 What are the exact steps that the user needs to take in order to take manual steps in DTS with FUM?

[miczyg1]

@miczyg1 What are the exact steps that the user needs to take in order to take manual steps in DTS with FUM?

When the DTS is booted over iPXE after enbling FUM, one has to interrupt the standard update process. The enter the shell, download the desired binary and flash it with flashrom -w <fie> --ifd -i fd -i me (added the descriptor too, because it could be locked)

[PLangowski]

@miczyg1 So for example sending the interrupt signal by pressing CTRL+C will work?

[miczyg1]

@miczyg1 So for example sending the interrupt signal by pressing CTRL+C will work?

No idea.

[PLangowski]

@miczyg1 After CTRL+C the update starts again. It seems that the only way to enter the shell is for the update to run and fail. I think we first have to resolve Dasharo/dasharo-issues#1211 (and Dasharo/dasharo-issues#712)

[m-iwanicki]

@PLangowski you should maybe also rework ME warning as currently it's a little misleading. Issue: #22 (should I migrate it to dasharo-issues?)