-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
NV56TU code does not build (reported in DM by Theirry) #1139
Comments
To validate this, defconfig needs to be expended into ooldconfig. Here I can only refer to what is under defconfig of ref config at
TLDR: code, paths + reference config needs to build under Heads and then Heads features tested on my side under linuxboot/heads#1835 |
This comment was marked as off-topic.
This comment was marked as off-topic.
@mkopec is it already resolved in: linuxboot/heads#1846 ? |
Needed to change path from novacustom-blobs (private) to dasharo-blobs (public). The FSPs themselves are the same.
Probably need to add a new step in CI, but this is the first release, so I'm not sure if EC FW needs to be included
Not sure about this one, so far I've managed to build coreboot with LPSS UART for debugging. coreboot logs end with jumping to payload, but nothing happens afterwards (on console or on screen) |
linuxboot/heads#1846 (comment)
|
Component
Dasharo firmware
Device
NovaCustom V56 14th Gen
Dasharo version
v0.9.0
Dasharo Tools Suite version
No response
Test case ID
No response
Brief summary
Commit reference config points to bad FSP paths, no recipe to build EC
How reproducible
I'm unsure; I'm just reporting what Thierry sent me in DM. I assume it should 100%.
linuxboot/heads#1835
How to reproduce
Try to build https://docs.dasharo.com/variants/novacustom_v560tu/releases/#v090-2024-07-18
Expected behavior
Dasharo (coreboot+UEFI) builds correctly based on the provided information in the release.
Actual behavior
No sure, no logs, no error messages received. Someone has to try to reproduce that and confirm this is valid.I'm not sure. No logs, no error messages were
Screenshots
No response
Additional context
It blocks Heads development. From Thierry:
Solutions you've tried
No response
The text was updated successfully, but these errors were encountered: