usb 4-1: configuration #1 chosen from 1 choice usb 4-1: new full speed USB device using uhci_hcd and address 6 hub 4-0:1.0: unable to enumerate USB device on port 1

usb 4-1: device descriptor read/all, error -32 usb 4-1: device descriptor read/8, error -32 usb 4-1: new full speed USB device using uhci_hcd and address 5 usb 4-1: new full speed USB device using uhci_hcd and address 4 usb 4-1: device descriptor read/all, error -84 usb 4-1: new full speed USB device using uhci_hcd and address 3 usb 4-1: can't read configurations, error -84 usb 4-1: unable to read config index 0 descriptor/all usb 4-1: new full speed USB device using uhci_hcd and address 2 Last edit at 02:01AM by Freeman.Īnd done dmesg, it shows the following error : Now, you should have no problem using this device for RepRap like a normal serial port.

To /etc/modules with the vendor and product numbers you found. As much fun as you had doing this, there is some chance you want to do this automatically in the future. Usbcore: registered new interface driver usbserial_genericĬongratulations, your link is up - in this example, the device can be used on /dev/ttyUSB0. Usb 1-1: generic converter now attached to ttyUSB0 Usbserial_generic 1-1:1.0: generic converter detected Near the end, you should see something like: Sudo modprobe usbserial vendor=0x4348 product=0x5523įinally, check dmesg again to ensure it loaded properly. Now, we can load up the driver for this device: Which returns the summary list again, but now showing the new USB device: Now, plug the device back in, and run lsusb again: You will see a summary list of your USB devices on the system, I only have one: The easiest way to find the information is to first unplug the device, then run lsusb: Now, we need to figure out the device vendor number and product number to tell the usbserial driver. Usb 1-1: configuration #1 chosen from 1 choice Usb 1-1: new full speed USB device using uhci_and address 2 Torward the end of the messages, you should see this:

After plugging in the device, first check the hardware messages to see the device was detected: If you are using the usb -> RS232 adapter, the serial drivers may need to be installed for the device to work properly. The procedure for using the USB adapter from the BOM wasn't in the wiki - nor was it immediately obvious, so, here goes.

Gigaware usb to serial driver 26-949