2. What repository:branch are you using to build from?
[ x ] Heads:Master
[ ] Other (please specify)
3. What version of coreboot are you trying to build
produced ROM's have no commit ID, source tree is up-to-date, so it should be 2399-g515ca5d
4. In building the rom where did you get the blobs?
[ ] No blobs required
[ ] Provided by the company that installed Heads on the device
[ ] Extracted from a backup rom taken from this device
[ ] Extracted from another backup rom taken from another device (please identify the board model)
[ x ] Extracted from the online bios using the automated tools provided in Heads
[ ] I don't know
5. If using the automated tools to get the blobs did you run the relevant scripts in the blobs directory
[ ] Yes
[ ] No
6. What operating system are you using
Debian-12 AppVM on QubesOS 4.2.3 ( with Docker and Nix installed after provided guides)
Please describe the problem
My build system produces Roms with different hashes than CircleCi, the Roms are only named e.g. t430-hotp-maximized-.rom (no commit-id). I even built a fresh docker image on a new created VM and built from a fresh cloned git-tree with the same result
To Reproduce
Steps to reproduce the behavior:
1.Create a build environment in a qubes AppVM after the guide in the documentation
Oessel
commented
11 hours ago
Context of the Build
1. What board are you trying to build?
t430-hotp-maximized
2. What repository:branch are you using to build from?
3. What version of coreboot are you trying to build
produced ROM's have no commit ID, source tree is up-to-date, so it should be 2399-g515ca5d
4. In building the rom where did you get the blobs?
5. If using the automated tools to get the blobs did you run the relevant scripts in the blobs directory
6. What operating system are you using
Debian-12 AppVM on QubesOS 4.2.3 ( with Docker and Nix installed after provided guides)
Please describe the problem
My build system produces Roms with different hashes than CircleCi, the Roms are only named e.g. t430-hotp-maximized-.rom (no commit-id). I even built a fresh docker image on a new created VM and built from a fresh cloned git-tree with the same result
To Reproduce Steps to reproduce the behavior:
1.Create a build environment in a qubes AppVM after the guide in the documentation
docker run -e DISPLAY=$DISPLAY --network host --rm -ti -v $(pwd):$(pwd) -w $(pwd) linuxboot/heads:dev-env -- make BOARD=t430-hotp-maximizedExpected behavior System produces a reproductible rom
Screenshots If applicable, add screenshots to help explain your problem.
Additional context Please excuse my incomplete description, i'll try to provide any information you need