Jetson-io config chage not saved

No other way. At least not able to be changed by ssh.

This is bootloader behavior.

All right. It’s complicated, but thanks for the explanation.

Is it still valid that the previously suggested m.2 ( NVMe??) as a boot disk solves the problem?

If your board can load extlinux.conf from any kind of boot device, then jetson-io change could be saved.

What a “jetson-io change” is just a path to a modified device tree file (dtb) file in extlinux.conf.

Your problem is “system cannot find a correct extlinux.conf, so it gave up”. And the default priority to search the file is according to the cbo file I shared in the document.

Currently, nvme has the highest priority, so bootlaoder tries to search it first.