| Summary: | systemd-boot: Timeout of zero not working | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Yocto Project Subprojects] Wic | Reporter: | Markus Faymann <Markus.Faymann> | ||||||
| Component: | wic | Assignee: | Trevor Woerner <twoerner> | ||||||
| Status: | NEW --- | QA Contact: | |||||||
| Severity: | normal | ||||||||
| Priority: | Undecided | ||||||||
| Version: | v0.3.0 | ||||||||
| Target Milestone: | --- | ||||||||
| Hardware: | x86 | ||||||||
| OS: | Multiple | ||||||||
| Whiteboard: | |||||||||
| OS type for building Yocto: | --- | Type of Regression: | --- | ||||||
| Verified: | Documentation change: | --- | |||||||
| Attachments: |
|
||||||||
Created attachment 5238 [details]
Example Kickstart file where issue occurs
|
Created attachment 5237 [details] Patch When using the systemd-boot bootloader in a Kickstart file, you cannot supply a bootloader timeout of zero. The wic component changes it to 5. This is because of the line loader_conf += "timeout %d\n" % (bootloader.timeout or 5) in bootimg_efi.py. The attached patch fixes the issue. The issue is still present in the most recent commit (dfec4f2318). It was possible to set the timeout to zero when using the Scarthgap release of Yocto.