Thanks for looking Jan. The only other usb messages were the startup messages associated with the linkUSB and the wifi adaptor (which continued to work normally) which were from several days earlier when it was last rebooted. Those for the linkUSB are
Feb 27 16:00:44 pi004 kernel: [ 3.883218] usb 1-1.4: new full-speed USB device number 4 using dwc_otg Feb 27 16:00:44 pi004 kernel: [ 4.021406] usb 1-1.4: New USB device found, idVendor=0403, idProduct=6001 Feb 27 16:00:44 pi004 kernel: [ 4.031837] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3 Feb 27 16:00:44 pi004 kernel: [ 4.045681] usb 1-1.4: Product: FT232R USB UART Feb 27 16:00:44 pi004 kernel: [ 4.053654] usb 1-1.4: Manufacturer: FTDI Feb 27 16:00:44 pi004 kernel: [ 4.061018] usb 1-1.4: SerialNumber: A501HXW7 Feb 27 16:00:44 pi004 kernel: [ 11.355906] usbcore: registered new interface driver usbserial Feb 27 16:00:44 pi004 kernel: [ 11.356020] usbcore: registered new interface driver usbserial_generic Feb 27 16:00:44 pi004 kernel: [ 11.356124] usbserial: USB Serial support registered for generic Feb 27 16:00:44 pi004 kernel: [ 11.412223] usbcore: registered new interface driver ftdi_sio Feb 27 16:00:44 pi004 kernel: [ 11.412352] usbserial: USB Serial support registered for FTDI USB Serial Device Feb 27 16:00:44 pi004 kernel: [ 11.412715] ftdi_sio 1-1.4:1.0: FTDI USB Serial Device converter detected Feb 27 16:00:44 pi004 kernel: [ 11.412956] usb 1-1.4: Detected FT232RL Feb 27 16:00:44 pi004 kernel: [ 11.465368] usb 1-1.4: FTDI USB Serial Device converter now attached to ttyUSB0 I too had expected to see messages about the usb device being disconnected, or something similar, but there is nothing. I don't know whether it may be relevant but I have a udev rule to map the device to /dev/linkUSB but there is no mention of this anywhere in the log, as far as I can see. Colin On 3 March 2017 at 13:24, Jan Kandziora <j...@gmx.de> wrote: > Am 02.03.2017 um 10:21 schrieb Colin Law: >> Running a LinkUSB on a pi zero (Raspbian Jessie), with owserver >> 3.1p4-1 from jessie testing, I very occasionally (every few weeks) see >> in syslog >> >> Mar 1 22:10:50 pi004 kernel: [194834.694657] ftdi_sio ttyUSB0: failed >> to get modem status: -110 >> Mar 1 22:11:00 pi004 kernel: [194844.694679] ftdi_sio ttyUSB0: failed >> to get modem status: -110 >> Mar 1 22:11:06 pi004 kernel: [194850.694734] ftdi_sio ttyUSB0: >> ftdi_set_termios FAILED to set databits/stopbits/parity >> Mar 1 22:11:07 pi004 kernel: [194851.694724] ftdi_sio ttyUSB0: >> ftdi_set_termios urb failed to set baudrate >> Mar 1 22:11:12 pi004 kernel: [194856.694771] ftdi_sio ttyUSB0: urb >> failed to clear flow control >> Mar 1 22:11:22 pi004 kernel: [194866.694810] ftdi_sio ttyUSB0: failed >> to get modem status: -110 >> Mar 1 22:11:27 pi004 kernel: [194871.694819] ftdi_sio ttyUSB0: urb >> failed to clear flow control >> > These are messages from the ftdi_sio USB driver. All this usually means > the kernel simply cannot talk to the USB converter. Please check your > kernel log for USB related messages. > > Kind regards > > Jan > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, SlashDot.org! http://sdm.link/slashdot > _______________________________________________ > Owfs-developers mailing list > Owfs-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/owfs-developers ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot _______________________________________________ Owfs-developers mailing list Owfs-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/owfs-developers
