Unknown enteties - HCL report

[Fu3coco]

---

DTS Version: 2.2.0
Motherboard: MSI z790-P WIFI (MS-7E06)
CPU: i5-14600K

Question:

I am trying to make an initial deployment through DTS to my motherboard, but when following the zero-touch deployment I get “Unknown” results on all of my report enteties, such as “TPM Info”, “Bios Info”, “Graphics VBT” etc.

And when I get to the selection of what firmware I want to flash, I only get the result “b) Return to main menu” – Isn’t there a CE (Community Edition) for this board?

The reason for me thinking that this board being supported is the following:

Following desktops are supported under Dasharo **Community** Support

[MSI PRO Z690-A](https://docs.dasharo.com/unified/msi/overview/)
[MSI PRO Z790-P](https://docs.dasharo.com/unified/msi/overview/)

Nontheless, shouldn’t the report generate some actual data?

[zirblazer]

The Z790-P does not actually have a community version, only the Z690-A, and it is the 2 years old 1.1.1 that doesn't even support Raptor Lake. What you can do is build yourself the 0.9.2 release binary for the Z790-P on your own: https://docs.dasharo.com/unified/msi/building-manual/

No idea about your DTS issues. Is your board a retail unit or it comes from a prebuild computer? I have seen some weird stuff since there are also Z790-P units that comes from prebuilds that have different SMBIOS info, but I only recall a single person reporting issues with DTS and such boards.

[Fu3coco]

First of, thanks for the reply.

The Z790-P does not actually have a community version, only the Z690-A, and it is the 2 years old 1.1.1 that doesn't even support Raptor Lake. What you can do is build yourself the 0.9.2 release binary for the Z790-P on your own: https://docs.dasharo.com/unified/msi/building-manual/

Good information, I did build the binary myself, two times acctually.
But they have different sha256sums, why is that?

My guess is that some metadata of the build differs, but can I verify somehow that is been built correctly (apart from testing it on my machine)?

I also wonder if I'll have to use this with the Z-Flash tool from MSI as used in this video (Naming the rom file to something along the lines of ".A09")?

No idea about your DTS issues. Is your board a retail unit or it comes from a prebuild computer? I have seen some weird stuff since there are also Z790-P units that comes from prebuilds that have different SMBIOS info, but I only recall a single person reporting issues with DTS and such boards.

It's been bought from a reputable vendor.
Can I attach any specific log for further investigation?

[zirblazer]

Good information, I did build the binary myself, two times acctually. But they have different sha256sums, why is that?

For reasons unknown, the binary that you compile on its own correspond to the SHA256 of the dev_signed ROM instead of the one with the same name. If everything went well, this is what you should have: https://dl.3mdeb.com/open-source-firmware/Dasharo/msi_ms7e06/v0.9.2/msi_ms7e06_v0.9.2_ddr5_dev_signed.rom.sha256

I also wonder if I'll have to use this with the Z-Flash tool from MSI as used in this video (Naming the rom file to something along the lines of ".A09")?

You can't do that in your board. M-Flash worked in Z690-A but not in Z790-P because MSI decided to introduce AMI Secure Flash and now binaries are signed, so you can't use MSI tools to flash it. What does work (And I tend to recommend) is MSI FlashBIOS, but recently two users in the same week reported issues with it where it eternally tries to flash. Is still the more straightforward way when it works.

It's been bought from a reputable vendor. Can I attach any specific log for further investigation?

I don't use DTS, so can't really help you here.

[Fu3coco]

For reasons unknown, the binary that you compile on its own correspond to the SHA256 of the dev_signed ROM instead of the one with the same name. If everything went well, this is what you should have: https://dl.3mdeb.com/open-source-firmware/Dasharo/msi_ms7e06/v0.9.2/msi_ms7e06_v0.9.2_ddr5_dev_signed.rom.sha256

Here I face an issue (I belive), after following all of the steps laid out in the manual, I do get a different SHA256 everytime.

For example, on my latest build I had the following:
2c6b4b725099a59ace6ab063844c828f4db1c38a26aa5ec30200f7b2be0524bb

How come that this happens and since it is happening, can I somehow verify it from Dasharo/3mdeb's websites?

You can't do that in your board. M-Flash worked in Z690-A but not in Z790-P because MSI decided to introduce AMI Secure Flash and now binaries are signed, so you can't use MSI tools to flash it. What does work (And I tend to recommend) is MSI FlashBIOS, but recently two users in the same week reported issues with it where it eternally tries to flash. Is still the more straightforward way when it works.

Alright, and I do just name it MSI.ROM and proceed as in the video from MSI?

I don't use DTS, so can't really help you here.

Fair enough.

[zirblazer]

For reasons unknown, the binary that you compile on its own correspond to the SHA256 of the dev_signed ROM instead of the one with the same name. If everything went well, this is what you should have: https://dl.3mdeb.com/open-source-firmware/Dasharo/msi_ms7e06/v0.9.2/msi_ms7e06_v0.9.2_ddr5_dev_signed.rom.sha256

Here I face an issue (I belive), after following all of the steps laid out in the manual, I do get a different SHA256 everytime.

For example, on my latest build I had the following: 2c6b4b725099a59ace6ab063844c828f4db1c38a26aa5ec30200f7b2be0524bb

How come that this happens and since it is happening, can I somehow verify it from Dasharo/3mdeb's websites?

What release are you compiling? msi_ms7e06_v0.9.2 ?
git clone https://github.com/Dasharo/coreboot.git -b msi_ms7e06_v0.9.2
?

It makes no sense that you're getting different SHA256 everytime you compile cause the whole idea is that builds are reproducible, so they should be consistent if you're using their containerized build environment.

SHA256 are public: https://docs.dasharo.com/variants/msi_z790/releases/#v092-2024-12-10
The one that you should get belongs to msi_ms7e06_v0.9.2_ddr5_dev_signed.rom
b6621f0052a07546ecf5f50d9e524b99cb73589692e62e7c7fe4a6f67c9b6390

[Fu3coco]

What release are you compiling? msi_ms7e06_v0.9.2 ? git clone https://github.com/Dasharo/coreboot.git -b msi_ms7e06_v0.9.2 ?

Yes, the msi_ms7e06_v0.9.2.
Just to be certain that we refer to the same shasum, in the Coreboot folder, upon compilation, two files gets generated - msi_ms7e06_v0.9.2_ddr5.rom & msi_ms7e06_v0.9.2_ddr5.rom.sha256.

This is the shasum I am talking about.

It makes no sense that you're getting different SHA256 everytime you compile cause the whole idea is that builds are reproducible, so they should be consistent if you're using their containerized build environment.

I agree, I find this very odd - Therefore I am wondering if I do anything wrong.

• I did some testing, and it was my fault, I got a different shasum if I wrote sudo ./build.sh z790p_ddr5 - Bad habit.

As soon as I wrote ./build.sh z790p_ddr5 I get the same b6621f0052a07546ecf5f50d9e524b99cb73589692e62e7c7fe4a6f67c9b6390

SHA256 are public: https://docs.dasharo.com/variants/msi_z790/releases/#v092-2024-12-10 The one that you should get belongs to msi_ms7e06_v0.9.2_ddr5_dev_signed.rom b6621f0052a07546ecf5f50d9e524b99cb73589692e62e7c7fe4a6f67c9b6390

Should I anyhow rename this file to "MSI.rom" and use MSI FlashBIOS as showed in the linked video?

Thanks in advance.

[zirblazer]

Should I anyhow rename this file to "MSI.rom" and use MSI FlashBIOS as showed in the linked video?

Yes.
Note that FlashBIOS can be really picky with USB Flash Drive used, if it correctly detects and is flashing it should begin blinking and turn Fans on. Also make sure that you sync after copying file, because I had issues where Linux command line appears to have finished but it never actually flush the data so you have a corrupted file, after copying reboot computer and check SHA256 of file on Flash Drive before using FlashBIOS.
You can also try using FlashBIOS with MSI own ROMs just to see if it works.

[Fu3coco]

Just to make this clear:

• Rename the file to MSI.rom
• Copy it to a flashdrive in FAT32 format
• Remove and re-insert the flashdrive and verify that the file on the flashdrive has the correct SHA256
• Insert into the "marked" usbport of the motherboard and try to flash - If it works it will flash and start the fans.

Have I understood this correctly?

[zirblazer]

• Remove and re-insert the flashdrive and verify that the file on the flashdrive has the correct SHA256

I would do a full reboot instead of replugging it. Heck, I trust more Windows than Linux when copying files to a removable Flash Drive since that experience.