I have one of these devices too: $ lsusb Bus 005 Device 002: ID 0403:6001 Future Technology Devices International, Ltd FT232 USB-Serial (UART) IC Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 003 Device 002: ID 046d:c03d Logitech, Inc. M-BT96a Pilot Optical Mouse Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 002 Device 004: ID 03f0:3611 Hewlett-Packard PSC 2410 PhotoSmart Bus 002 Device 003: ID 413c:2003 Dell Computer Corp. Keyboard Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
but I don't see this precise problem. $ dmesg |grep latency [ 0.540690] pci 0000:00:01.0: setting latency timer to 64 [ 0.540704] pci 0000:00:1c.0: setting latency timer to 64 [ 0.540723] pci 0000:00:1c.1: setting latency timer to 64 [ 0.540730] pci 0000:00:1e.0: setting latency timer to 64 [ 0.572644] pcieport 0000:00:01.0: setting latency timer to 64 [ 0.572778] pcieport 0000:00:1c.0: setting latency timer to 64 [ 0.572926] pcieport 0000:00:1c.1: setting latency timer to 64 [ 0.642441] ata_piix 0000:00:1f.1: setting latency timer to 64 [ 0.863461] ata_piix 0000:00:1f.2: setting latency timer to 64 [ 0.868809] ehci_hcd 0000:00:1d.7: setting latency timer to 64 [ 0.888362] uhci_hcd 0000:00:1d.0: setting latency timer to 64 [ 0.888640] uhci_hcd 0000:00:1d.1: setting latency timer to 64 [ 0.888915] uhci_hcd 0000:00:1d.2: setting latency timer to 64 [ 0.889195] uhci_hcd 0000:00:1d.3: setting latency timer to 64 [ 2.984776] tg3 0000:02:00.0: setting latency timer to 64 [ 15.215316] nouveau 0000:01:00.0: setting latency timer to 64 [ 18.011806] Intel ICH 0000:00:1e.2: setting latency timer to 64 This is with linux-image-2.6.32-25-generic version 2.6.32-25.44 $ uname -a Linux ubuntu 2.6.32-25-generic #44-Ubuntu SMP Fri Sep 17 20:26:08 UTC 2010 i686 GNU/Linux I do have a problem with the device, however. It is not responding properly when queried by /usr/bin/digitemp_DS9097U. Let me know if you want me to file a separate bug, but for now here's the problem: What I used to get was $ digitemp_DS9097U -s /dev/ttyUSB0 -a -q Sep 28 20:01:25 Sensor 0 C: 21.56 F: 70.81 Sep 28 20:01:26 Sensor 1 C: 23.06 F: 73.51 ie there are two one-wire temperature sensors plugged into the usb serial device. Now what I get is: $ digitemp_DS9097U -s /dev/ttyUSB0 -a -q Error 5: DS2480B Adapter Not Detected Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed Error 10: Read COM Failed This works ok on: Linux ubuntu 2.6.32-22-generic #36-Ubuntu SMP Thu Jun 3 22:02:19 UTC 2010 i686 GNU/Linux It also worked ok on: Linux ubuntu 2.6.32-24-generic #43-Ubuntu SMP Thu Sep 16 14:17:33 UTC 2010 i686 GNU/Linux It does not work on either of these mainline builds: 2.6.32-0206322109-generic 2.6.36-999.201009261124 The same error seems to be occurring. Shortly I'll attach two straces - one where the digitemp program works (2.6.32-22-generic) and another where it does not (2.6.24-25-generic). -- FTDI based USB to serial adapter no longer works https://bugs.launchpad.net/bugs/655868 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
