Fix install script raspi cmdline message #12842
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Proposed Changes
Updated the error message for memory cgroup detection to reflect the correct location of the
cmdline.txt
file on Raspberry Pi systems running Raspberry Pi OS Bookworm or later (released in 2023). The file path has changed from/boot/cmdline.txt
to/boot/firmware/cmdline.txt
due to the new firmware structure introduced in Raspberry Pi OS Bookworm.Types of Changes
Docs
Verification
The change can be verified by:
cgroup_memory=1 cgroup_enable=memory
in the kernel command line)./boot/firmware/cmdline.txt
instead of/boot/cmdline.txt
./boot/firmware/
directory.Testing
This change is a minor text update to an error message and does not affect the core functionality of k3s. Existing integration tests for cgroup detection should suffice, as the change only modifies the displayed file path. No new tests are required, but manual verification on a Raspberry Pi running Bookworm can confirm the updated message appears as expected.
Linked Issues
None
User-Facing Change
Further Comments
This change corrects an outdated file path in the error message, addressing confusion for Raspberry Pi users on Bookworm or later, where boot configuration files moved to
/boot/firmware/
. The fix is straightforward, aligning the error message with the current Raspberry Pi OS filesystem. No alternative approaches were considered, as this directly resolves the issue.