0

I added to the cmdline.txt instructions

usb-storage.quirks=152d:0578:u force_mac_address=dc:a6:32:e6:58:51

to correct issues with a sata-usb interface and to change the mac address.

The quirks are effective for the boot, but at a reboot, the cmdline edit is gone and the sata-usb interface does not work properly anymore. When I check, I see that the edit is lost in the cmdline.txt file.

How can I prevent the overwriting of the edit?

From reading various suggestions, I have the impression, that the first cmdline.txt is setting things up and booting afterwards uses a reduced set of the arguments. Is this correct? Details?

user855443
  • 119
  • 1
  • 5

1 Answers1

1

At least one answer here suggests that the code that parses /boot/cmdline.txt is picky. AIUI, /boot/cmdline.txt contains a single command line, only the first line of the file is read and parameters must be space separated on that line. The answer cited above suggests that it's possible to insert comment lines preceded with #, so you could try that if you like. /boot is a FAT partition, and so the files on it can be edited by virtually any computer... BUT BEWARE OF WINDOWS EDITORS. It would also be a good idea to make a copy of the original /boot/cmdline.txt file, and keep that in a safe place.

IOW: Try putting your entire cmdline entry on a single line with no newline character, no comments, etc - just a single line with all the commands.

Seamus
  • 23,558
  • 5
  • 42
  • 83