Given this is a questing (25.10) install, it's probable you're now editing the wrong file; in questing we moved to an A/B boot setup where the runtime boot artefacts are under /boot/firmware/current (so your runtime kernel command line is now /boot/firmware/current/cmdline.txt).
If you're confident your kernel cmdline changes won't cause any problems you can simply edit /boot/firmware/current/cmdline.txt, reboot, and you should find the results appear in /proc/cmdline. Alternatively, if you want to test the cmdline.txt changes using the A/B mechanism: $ sudo flash-kernel $ sudo vi /boot/firmware/new/cmdline.txt $ sudo reboot The flash-kernel run sets up the "new" boot assets under /boot/firmware/new. You then edit /boot/firmware/new/cmdline.txt and reboot. If the boot succeeds, /boot/firmware/new will become /boot/firmware/current (so /boot/firmware/new/cmdline.txt will become /boot/firmware/current/cmdline.txt, and your former /boot/firmware/current/cmdline.txt will become /boot/firmware/old/cmdline.txt). -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2134605 Title: Values in "/boot/firmware/cmdline.txt" not applied to "/proc/cmdline" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-raspi/+bug/2134605/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
