Do you have a different PC to make the attempt? On Fri, Dec 11, 2020 at 10:09 AM Ken Stephens <[email protected]> wrote:
> Just plugging it into the 2.0 port by itself without another cable > connected: > $dmesg -T > . > . > . > [Fri Dec 11 09:45:48 2020] usb 2-1.1: new full-speed USB device number 28 > using ehci-pci > [Fri Dec 11 09:45:48 2020] usb 2-1.1: device descriptor read/64, error -32 > [Fri Dec 11 09:45:48 2020] usb 2-1.1: device descriptor read/64, error -32 > [Fri Dec 11 09:45:48 2020] usb 2-1.1: new full-speed USB device number 29 > using ehci-pci > [Fri Dec 11 09:45:48 2020] usb 2-1.1: device descriptor read/64, error -32 > [Fri Dec 11 09:45:48 2020] usb 2-1.1: device descriptor read/64, error -32 > [Fri Dec 11 09:45:48 2020] usb 2-1-port1: attempt power cycle > [Fri Dec 11 09:45:49 2020] usb 2-1.1: new full-speed USB device number 30 > using ehci-pci > [Fri Dec 11 09:45:49 2020] usb 2-1.1: device not accepting address 30, > error -32 > [Fri Dec 11 09:45:49 2020] usb 2-1.1: new full-speed USB device number 31 > using ehci-pci > [Fri Dec 11 09:45:50 2020] usb 2-1.1: device not accepting address 31, > error -32 > [Fri Dec 11 09:45:50 2020] usb 2-1-port1: unable to enumerate USB device > > Exasperated, > Ken > > On Fri, Dec 11, 2020 at 9:40 AM Ken Stephens <[email protected]> > wrote: > > > # lsusb > > Bus 002 Device 003: ID 17e9:4301 DisplayLink > > Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub > > Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub > > Bus 003 Device 009: ID 046d:0802 Logitech, Inc. Webcam C200 > > Bus 003 Device 004: ID 046d:c318 Logitech, Inc. Illuminated Keyboard > > Bus 003 Device 003: ID 045e:00cb Microsoft Corp. Basic Optical Mouse v2.0 > > Bus 003 Device 002: ID 0409:0058 NEC Corp. HighSpeed Hub > > Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > Bus 001 Device 003: ID 058f:a014 Alcor Micro Corp. Asus Integrated Webcam > > Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub > > Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub > > > > On Fri, Dec 11, 2020 at 9:06 AM Johnathan Mantey <[email protected]> > > wrote: > > > >> What is the output from lsusb? > >> > >> On Thu, Dec 10, 2020 at 10:08 PM Ken Stephens < > [email protected] > >> > > >> wrote: > >> > >> > I subscribe to a monthly electronic surprise box > >> > <https://www.instructables.com/HackerBox-0061-Props/>. This month's > >> > surprise is a Propeller 2 8x32bit processor on a circuit board that > >> > connects to a computer with USB. The circuit board and chip are > RT232RL > >> > Serial USB Interface. > >> > > >> > The FT232RL chip by ftdichip.com does not identify itself to the usb > >> > hubs. Tried many. Tried different cables. Loaded the suggested > >> driver. > >> > It's transmit and receive lights flash when plugged in. The dmesg > >> output > >> > when device is plugged into a 3.0 port is: > >> > > >> > [Thu Dec 10 21:32:13 2020] usb 3-1: new full-speed USB device number > 14 > >> > using xhci_hcd > >> > [Thu Dec 10 21:32:13 2020] usb 3-1: device descriptor read/64, error > -71 > >> > [Thu Dec 10 21:32:13 2020] usb 3-1: device descriptor read/64, error > -71 > >> > [Thu Dec 10 21:32:14 2020] usb 3-1: new full-speed USB device number > 15 > >> > using xhci_hcd > >> > [Thu Dec 10 21:32:14 2020] usb 3-1: device descriptor read/64, error > -71 > >> > [Thu Dec 10 21:32:14 2020] usb 3-1: device descriptor read/64, error > -71 > >> > [Thu Dec 10 21:32:14 2020] usb usb3-port1: attempt power cycle > >> > [Thu Dec 10 21:32:15 2020] usb 3-1: new full-speed USB device number > 16 > >> > using xhci_hcd > >> > [Thu Dec 10 21:32:15 2020] usb 3-1: Device not responding to setup > >> address. > >> > [Thu Dec 10 21:32:15 2020] usb 3-1: Device not responding to setup > >> address. > >> > [Thu Dec 10 21:32:15 2020] usb 3-1: device not accepting address 16, > >> error > >> > -71 > >> > [Thu Dec 10 21:32:15 2020] usb 3-1: new full-speed USB device number > 17 > >> > using xhci_hcd > >> > [Thu Dec 10 21:32:15 2020] usb 3-1: Device not responding to setup > >> address. > >> > [Thu Dec 10 21:32:16 2020] usb 3-1: Device not responding to setup > >> address. > >> > [Thu Dec 10 21:32:16 2020] usb 3-1: device not accepting address 17, > >> error > >> > -71 > >> > [Thu Dec 10 21:32:16 2020] usb usb3-port1: unable to enumerate USB > >> device > >> > > >> > The dmesg output when device is plugged into a 2.0 port: > >> > [Thu Dec 10 22:03:09 2020] usb 2-1.2.3: new full-speed USB device > >> number 9 > >> > using ehci-pci > >> > [Thu Dec 10 22:03:09 2020] usb 2-1.2.3: device descriptor read/64, > error > >> > -32 > >> > [Thu Dec 10 22:03:09 2020] usb 2-1.2.3: device descriptor read/64, > error > >> > -32 > >> > [Thu Dec 10 22:03:09 2020] usb 2-1.2.3: new full-speed USB device > >> number 10 > >> > using ehci-pci > >> > [Thu Dec 10 22:03:09 2020] usb 2-1.2.3: device descriptor read/64, > error > >> > -32 > >> > [Thu Dec 10 22:03:09 2020] usb 2-1.2.3: device descriptor read/64, > error > >> > -32 > >> > [Thu Dec 10 22:03:09 2020] usb 2-1.2-port3: attempt power cycle > >> > [Thu Dec 10 22:03:10 2020] usb 2-1.2.3: new full-speed USB device > >> number 11 > >> > using ehci-pci > >> > [Thu Dec 10 22:03:10 2020] usb 2-1.2.3: device not accepting address > 11, > >> > error -32 > >> > [Thu Dec 10 22:03:11 2020] usb 2-1.2.3: new full-speed USB device > >> number 12 > >> > using ehci-pci > >> > [Thu Dec 10 22:03:11 2020] usb 2-1.2.3: device not accepting address > 12, > >> > error -32 > >> > [Thu Dec 10 22:03:11 2020] usb 2-1.2-port3: unable to enumerate USB > >> device > >> > > >> > The kernel is configured properly: > >> > # uname -r > >> > 5.9.12-100.fc32.x86_64 > >> > $ grep -i xhci /boot/config-$(uname -r) > >> > CONFIG_USB_XHCI_HCD=y > >> > CONFIG_USB_XHCI_DBGCAP=y > >> > CONFIG_USB_XHCI_PCI=y > >> > CONFIG_USB_XHCI_PCI_RENESAS=y > >> > CONFIG_USB_XHCI_PLATFORM=m > >> > CONFIG_USB_ROLES_INTEL_XHCI=m > >> > > >> > Any wizards out there that have an idea what is happening and how I > can > >> fix > >> > it? Or shall I chock it up to a bad chip. > >> > > >> > Thanks, > >> > Ken > >> > _______________________________________________ > >> > PLUG: https://pdxlinux.org > >> > PLUG mailing list > >> > [email protected] > >> > http://lists.pdxlinux.org/mailman/listinfo/plug > >> > > >> _______________________________________________ > >> PLUG: https://pdxlinux.org > >> PLUG mailing list > >> [email protected] > >> http://lists.pdxlinux.org/mailman/listinfo/plug > >> > > > _______________________________________________ > PLUG: https://pdxlinux.org > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > _______________________________________________ PLUG: https://pdxlinux.org PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
