On Mon, 9 Jul 2007, Peter Warrick wrote: > Apologies if this has been written about before but I was not able to > find anything in the archives for this specific issue. > > I have a device running kernel 2.6.15 with everything compiled into > the kernel for USB serial support. > > I've tried multiple usb serial converters (FTDI, KeySpan, PL2303) and > I can't get any of them to work. I've plugged them all into my linux > workstation and they all come up just fine so I know they work with > linux. I've even checked the driver source and they are identical to > what I have on my linux workstation. > > The best I've seen so far is that the Keyspan at least gets something > to be spit out to /var/log/messages... > > Jul 9 18:13:28 host user.debug kernel: hub 1-0:1.0: state 5 ports 2 > chg 0000 evt 0002 > Jul 9 18:13:28 host user.debug kernel: tangox-ehci-hcd tangox-ehci- > hcd: GetStatus port 1 status 001002 POWER sig=se0 CSC > Jul 9 18:13:28 host user.debug kernel: hub 1-0:1.0: port 1, status > 0100, change 0001, 12 Mb/s > Jul 9 18:13:28 host user.debug kernel: hub 1-0:1.0: debounce: port > 1: total 100ms stable 100ms status 0x100 > > That's it. The FTDI and the PL2303 don't cause any output to /var/log/ > messages when plugged in. > > I checked /proc/bus/usb and it was empty so I used the command mount - > t usbfs none /proc/bus/usb/ and that fixed that up. I now have a > 001/, 002/, and a devices file. > > Here's what I have in the /var/log/messages in terms of usb. It > appears that the everything installed correctly and that hotplug is > installed as well.
> Jul 9 18:09:56 host user.info kernel: usb 2-1: new low speed USB > device using tangox-ohci-hcd and address 2 > Jul 9 18:09:56 host user.err kernel: usb 2-1: device descriptor read/ > 64, error -145 > Jul 9 18:10:10 host user.info kernel: usb 2-1: new low speed USB > device using tangox-ohci-hcd and address 3 > Jul 9 18:10:11 host user.err kernel: usb 2-1: device descriptor read/ > 64, error -145 > > I don't want to spam the message so let me know if there is anything > else that could help diagnose this problem. I've been working on this > for about a month and I've tried compiling the modules right into the > kernel and also just leaving everything as modules. Neither works. Is > there something I've missed? The only thing I can think of is that I > read something about BIOS settings but this device doesn't have a > BIOS in terms of a PC. As far as I know, everything is on. > > Thanks for any help or suggestions. It's possible that you've got a wiring error on your board. For instance, swapping the D+ and D- lines could cause something like this. Alan Stern ------------------------------------------------------------------------- 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
