Suggested fix is:
Write a simple udev-rule which will assign symlink /dev/whatever to right device by its VID & PID.
1 - Find out what is on ttyUSB
dmesg | grep ttyUSB
2 - list all attributes of the device and pick out a unique identifier set, eg idVendor + idProduct (and if necessary SerialNumber if you have more than one device with the same idVendor and idProduct).
udevadm info --name=/dev/ttyUSB1 --attribute-walk
3 - Create a file /etc/udev/rules.d/99-usb-serial.rules with something like this line in it:
SUBSYSTEM=="tty", ATTRS{idVendor}=="1234", ATTRS{idProduct}=="5678", SYMLINK+="your_device_name"
4 - Load the new rule:
sudo udevadm trigger
5 - Verify what happened:
ls -l /dev/your_device_name
will show what ttyUSB number the symlink went to. If it's /dev/ttyUSB1, then verify who owns that and to which group it belongs:
ls -l /dev/ttyUSB1
Then just for the fun of it:
udevadm test -a -p $(udevadm info -q path -n /dev/your_device_name)
Write a simple udev-rule which will assign symlink /dev/whatever to right device by its VID & PID.
1 - Find out what is on ttyUSB
dmesg | grep ttyUSB
2 - list all attributes of the device and pick out a unique identifier set, eg idVendor + idProduct (and if necessary SerialNumber if you have more than one device with the same idVendor and idProduct).
udevadm info --name=/dev/ttyUSB1 --attribute-walk
3 - Create a file /etc/udev/rules.d/99-usb-serial.rules with something like this line in it:
SUBSYSTEM=="tty", ATTRS{idVendor}=="1234", ATTRS{idProduct}=="5678", SYMLINK+="your_device_name"
4 - Load the new rule:
sudo udevadm trigger
5 - Verify what happened:
ls -l /dev/your_device_name
will show what ttyUSB number the symlink went to. If it's /dev/ttyUSB1, then verify who owns that and to which group it belongs:
ls -l /dev/ttyUSB1
Then just for the fun of it:
udevadm test -a -p $(udevadm info -q path -n /dev/your_device_name)