Running Sensly installer replaces boot parameters in Raspi's cmdline.txt file while installer is runningUart_enable.sh.
This is bad, because cmdline may have custom modifications and removing them may make Raspi inaccessible.
A suggestion, instead:
- parse existing cmdline parameters
- remove only known parameters which are known to cause issues
- add your own parameters
- leave other parameters untouched
echo "dwc_otg.lpm_enable=0 console=tty1 root=/dev/mmcblk0p2 rootfstype=ext4 elevator=deadline fsck.repair=yes rootwait quiet splash plymouth.ignore-serial-consoles" >> /boot/cmdline.txt
sed -i -e '1s/^/#/' /boot/cmdline.txt
https://github.com/Altitude-Tech/Sensly_Install/blob/d1fe3bbe0dd4055a0a13e7c8399043a8ddae1b85/Uart_enable.sh#L5,L6
Running Sensly installer replaces boot parameters in Raspi's
cmdline.txtfile while installer is runningUart_enable.sh.This is bad, because cmdline may have custom modifications and removing them may make Raspi inaccessible.
A suggestion, instead:
https://github.com/Altitude-Tech/Sensly_Install/blob/d1fe3bbe0dd4055a0a13e7c8399043a8ddae1b85/Uart_enable.sh#L5,L6