Bug 2248665
| Summary: | akmods doesn't understand fedora systemd-boot installs and mistakes updateloaderentries/grubby for an actual grub system | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Maxime Gervais <gervais.maxime> |
| Component: | akmods | Assignee: | Nicolas Chauvet (kwizart) <kwizart> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | low | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 39 | CC: | hdegoede, hobbes1069, jeremy.linton, kwizart, leigh123linux, negativo17, nicolas.vieville, travier |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | akmods-0.5.8-6.fc39 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-12-15 19:03:45 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Maxime Gervais
2023-11-08 08:48:10 UTC
So, I addd a --default-kernel option to sdubby/updateloaderentries but that doesn't fix the problem because the sed vmlinux fails to parse the version from the resulting pat. As such I opened a PR https://src.fedoraproject.org/rpms/akmods/pull-request/17 to tweak akmods so that it understands this situation and goes ahead and uses its bootctl logic instead. I'm also going to reassign this BZ to that component, with the understanding that at some point i'm going to push the change to support --default-kernel but that probably isn't the best fix for akmods. I've merged the PR and building for f39+. Can I use this as an opportunity to ask how to deal with kernel cmdline options with systemd-boot(and/or sdubby) ? We prefer to use cmdline because it's easier to switch back to nouveau on boot for any reason while still having the nvidia driver installed rather that tweak anything from the config userspace. ostree systems make that task even more relevant. (see also https://bugzilla.rpmfusion.org/show_bug.cgi?id=6809) Also seems there is a need to clarify the situation with alternatives bootloader entries: Anyone of you tried boom-boot: https://koji.fedoraproject.org/koji/buildinfo?buildID=2328172 ? (In reply to Nicolas Chauvet (kwizart) from comment #3) > Also seems there is a need to clarify the situation with alternatives > bootloader entries: > Anyone of you tried boom-boot: > https://koji.fedoraproject.org/koji/buildinfo?buildID=2328172 ? My bad, seems like for a different purpose (I even used it some time ago). re: comment 2 above: I'm not 100% sure I understand the question. But the sdubby package is providing a grubby like utility for programmatically updating the BLS/kernel command line entries to solve the problem of not having to worry about grub vs systemd-boot BLS entries. But as you point out there are various other utilities that can do both as well, so just using grubby isn't the only choice. FEDORA-2023-8cbf675b24 has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2023-8cbf675b24 FEDORA-2023-8cbf675b24 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2023-8cbf675b24` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2023-8cbf675b24 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2023-8cbf675b24 has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. |