I'm not sure what to look for. This is what it's saying when I plug in the device now.
Dec 31 19:47:53 host user.debug kernel: hub 1-0:1.0: state 5 ports 2 chg 0000 evt 0002 Dec 31 19:47:53 host user.debug kernel: tangox-ehci-hcd tangox-ehci- hcd: GetStatus port 1 status 001803 POWER sig=j CSC CONNECT Dec 31 19:47:53 host user.debug kernel: hub 1-0:1.0: port 1, status 0501, change 0001, 480 Mb/s Dec 31 19:47:53 host user.debug kernel: hub 1-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x501 Dec 31 19:47:53 host user.debug kernel: tangox-ehci-hcd tangox-ehci- hcd: port 1 full speed --> companion Dec 31 19:47:53 host user.debug kernel: tangox-ehci-hcd tangox-ehci- hcd: GetStatus port 1 status 003801 POWER OWNER sig=j CONNECT Dec 31 19:47:53 host user.debug kernel: hub 1-0:1.0: port 1 not reset yet, waiting 50ms Dec 31 19:47:53 host user.debug kernel: tangox-ehci-hcd tangox-ehci- hcd: GetStatus port 1 status 003002 POWER OWNER sig=se0 CSC Dec 31 19:47:53 host user.debug kernel: hub 1-0:1.0: state 5 ports 2 chg 0000 evt 0002 Dec 31 19:47:53 host user.debug kernel: hub 2-0:1.0: state 5 ports 2 chg 0000 evt 0002 Dec 31 19:47:53 host user.debug kernel: tangox-ohci-hcd tangox-ohci- hcd: GetStatus roothub.portstatus [0] = 0x00010101 CSC PPS CCS Dec 31 19:47:53 host user.debug kernel: hub 2-0:1.0: port 1, status 0101, change 0001, 12 Mb/s Dec 31 19:47:53 host user.debug kernel: hub 2-0:1.0: debounce: port 1: total 100ms stable 100ms status 0x101 Dec 31 19:47:53 host user.debug kernel: tangox-ohci-hcd tangox-ohci- hcd: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS PES CCS Dec 31 19:47:53 host user.info kernel: usb 2-1: new full speed USB device using tangox-ohci-hcd and address 2 Dec 31 19:47:54 host user.debug kernel: tangox-ohci-hcd tangox-ohci- hcd: GetStatus roothub.portstatus [0] = 0x00100103 PRSC PPS PES CCS Dec 31 19:47:54 host user.debug kernel: usb 2-1: ep0 maxpacket = 8 Dec 31 19:47:54 host user.debug kernel: usb 2-1: default language 0x0409 Dec 31 19:47:54 host user.debug kernel: usb 2-1: new device strings: Mfr=1, Product=2, SerialNumber=3 Dec 31 19:47:54 host user.info kernel: usb 2-1: Product: USB Serial Converter Dec 31 19:47:54 host user.info kernel: usb 2-1: Manufacturer: FTDI Dec 31 19:47:54 host user.info kernel: usb 2-1: SerialNumber: FTDCJBUZ Dec 31 19:47:54 host user.debug kernel: usb 2-1: hotplug Dec 31 19:47:54 host user.debug kernel: usb 2-1: adding 2-1:1.0 (config #1, interface 0) Dec 31 19:47:54 host user.debug kernel: usb 2-1:1.0: hotplug Dec 31 19:47:54 host user.debug kernel: usbserial_generic 2-1:1.0: usb_probe_interface Dec 31 19:47:54 host user.debug kernel: usbserial_generic 2-1:1.0: usb_probe_interface - got id Dec 31 19:47:54 host user.debug kernel: drivers/usb/core/inode.c: creating file '002' It definitely sees it and knows its an FTDI which I do have the driver compiled in. Regards, Peter On 9-Jul-07, at 11:24 PM, Greg KH wrote: > On Mon, Jul 09, 2007 at 09:21:28PM -0600, Peter Warrick wrote: >> Ok, now I've gotten it to be recognized by the kernel and it sees >> that it is an FTDI type device. It creates the file in /proc/bus/usb >> as well. I have setup all my devices using mknod /dev/usb/ttyUSB0 c >> 188 0 etc.. But when I try to do an stty -F /dev/usb/ttyUSB0 all I >> get is... >> >> stty: /dev/usb/ttyUSB0: No such device >> >> Did I miss a step? > > Does the kernel say that it saw the device and properly bound it to > the > ttyUSB device? > > thanks, > > greg k-h ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Linux-usb-users@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-users
