I'm not up on the steps to do to get the debug (if you can list the command(s) 
to run?).

BUT -

After the last reboot which has 252.12-1~deb12u1  I saw

lrwxrwxrwx 1 root root           9 2023-08-17 16:29 ttyUSB-nut -> gpiochip0

Which is wrong - So I unplugged and replugged the cable and looked again and 
see:

lrwxrwxrwx 1 root root 15 2023-08-23 11:57 ttyUSB-nut -> bus/usb/001/003

Which is also wrong...

Nothing unusual in syslog:

2023-08-23T11:57:33.070249-05:00 localhost kernel: [502060.481676] ftdi_sio ttyUSB0: FTDI USB Serial Device converter now disconnected from ttyUSB0
2023-08-23T11:57:33.070259-05:00 localhost kernel: [502060.481724] ftdi_sio 
1-8:1.0: device disconnected
2023-08-23T11:57:35.772093-05:00 localhost kernel: [502063.187387] usb 1-8: new full-speed USB device number 3 using xhci_hcd 2023-08-23T11:57:35.924035-05:00 localhost kernel: [502063.341331] usb 1-8: New USB device found, idVendor=0403, idProduct=6001, bcdDevice= 6.00 2023-08-23T11:57:35.924054-05:00 localhost kernel: [502063.341345] usb 1-8: New USB device strings: Mfr=1, Product=2, SerialNumber=3
2023-08-23T11:57:35.924056-05:00 localhost kernel: [502063.341352] usb 1-8: 
Product: FT232R USB UART
2023-08-23T11:57:35.924058-05:00 localhost kernel: [502063.341358] usb 1-8: 
Manufacturer: FTDI
2023-08-23T11:57:35.924060-05:00 localhost kernel: [502063.341363] usb 1-8: 
SerialNumber: AJV9MKOY
2023-08-23T11:57:35.928058-05:00 localhost kernel: [502063.345376] ftdi_sio 1-8:1.0: FTDI USB Serial Device converter detected
2023-08-23T11:57:35.928077-05:00 localhost kernel: [502063.345482] usb 1-8: 
Detected FT232R
2023-08-23T11:57:35.928080-05:00 localhost kernel: [502063.346643] usb 1-8: FTDI USB Serial Device converter now attached to ttyUSB0


--
--------------------------------------------------------------------------------
Karl Schmidt                                  EMail k...@lrak.net
3209 West 9th Street                          Ph (785) 841-3089
Lawrence, KS 66049

Being wrong, is the natural state of experts.
-Malcolm Kendrick
--------------------------------------------------------------------------------

Reply via email to