| Summary: | boot params cannot be modified in joule with meta-intel | ||
|---|---|---|---|
| Product: | [Runtime] Installation | Reporter: | Benjamin Esquivel <benjamin.esquivel> |
| Component: | Installation | Assignee: | Saul Wold <sgw> |
| Status: | RESOLVED ReportedUpstream | QA Contact: | |
| Severity: | normal | ||
| Priority: | Medium | CC: | alejandro.hernandez, benjamin.esquivel, kevin.tian, sgw |
| Version: | unspecified | ||
| Target Milestone: | Future | ||
| Hardware: | Other | ||
| OS: | Multiple | ||
| Whiteboard: | |||
| OS type for building Yocto: | --- | Type of Regression: | --- |
| Verified: | Documentation change: | Don't know | |
|
Description
Benjamin Esquivel
2016-10-21 17:45:20 UTC
There is a known BIOS bug that causes a hang with the console, there is a partial work-around for systemd-boot, which allows selecting which boot label, but still hangs again when attempting to edit the boot params. Ok, so this is going to be something like Waiting for upstream? or how do we mark it dependant on the fix you mention? As mentioned this is a BIOS issue and can not be addressed from the bootloader, marking this WaitForUpstream Marking future until we learn more from the firmware team Waiting For Upstream status is being removed, changing to Accepted. This is a know upstream issue with the Joule Bios, as the Joule has been EOL'ed I am closing this bug |