Re: [beagleboard] usb-serial device doesn't appear in /dev. Need a udev rule?
Hi - I have one of these startech devices - and I see the same behavior -
out of the box if I plug it in, I get:
lsusb says:
Bus 001 Device 023: ID 14b0:3410 StarTech.com Ltd.
the kernel log says:
Sep 21 16:06:09 overkill kernel: [104648.529334] usb 1-1.5.1.3: new
full-speed USB device number 23 using ehci-pci
Sep 21 16:06:09 overkill kernel: [104648.655372] usb 1-1.5.1.3: New USB
device found, idVendor=14b0, idProduct=3410
Sep 21 16:06:09 overkill kernel: [104648.655379] usb 1-1.5.1.3: New USB
device strings: Mfr=1, Product=2, SerialNumber=3
Sep 21 16:06:09 overkill kernel: [104648.655383] usb 1-1.5.1.3: Product:
StarTech.com Adapter
Sep 21 16:06:09 overkill kernel: [104648.655387] usb 1-1.5.1.3:
Manufacturer: StarTech.com
Sep 21 16:06:09 overkill kernel: [104648.655390] usb 1-1.5.1.3:
SerialNumber: 1321
But it does not attach to a ttyUSB port.
I don't know how to patch / compile the kernel driver as noted below -
could someone walk me through this, or could someone compile the patch
below, and let me know how to test it?
It would be nice to get this fixed in the kernel.
I'm currently testing on:
Linux overkill 3.11.0-26-generic #45-Ubuntu SMP Tue Jul 15 04:02:06 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux
Thanks,
Dan
On Monday, January 6, 2014 5:49:39 PM UTC-6, Nuno wrote:
On 01/05/2014 01:07 AM, loonsailor wrote:
The Startech device, with the TI chipset, continues to have the same
problem. I've tried a couple of other converters, Keyspan and Trendnet,
both of which use the Prolific chipset, and they do work, making both
Hi,
if you feel brave enough, you could try to patch the kernel
drivers/usb/serial/ti_usb_3410_5052.{c,h} files and add the startech usb
vendor id, see attachment.
Since I don't have that device, I cannot test it myself, but if
works
with you it can then be sent upstream.
Which kernel do you have (cat /proc/version)? I could compile the
module for you, if you are willing to test it.
regards,
Nuno
--
http://aeminium.org/nuno/
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Re: [beagleboard] usb-serial device doesn't appear in /dev. Need a udev rule?
My Startech device worked on my Windows 7 box, but not on my BBB / Rev C. The Solution: I ran a usb cable from my BBB to a USB hub that has its own power supply, then ran the Startech PL2303 from the hub to my modem. Worked fine. It was apparently a problem of not having enough power to operate correctly. On Sunday, January 5, 2014 1:07:19 AM UTC-5, loonsailor wrote: The Startech device, with the TI chipset, continues to have the same problem. I've tried a couple of other converters, Keyspan and Trendnet, both of which use the Prolific chipset, and they do work, making both /dev/serial devices and /dev/ttyUSB0. It may be fixable with the Startech converter, but since the other converters work straight out of the box, I'm just going to use one of them and move on to the next step of making my system work. Thanks for the help, Nuno! On Saturday, January 4, 2014 9:48:07 AM UTC-8, Nuno wrote: On 01/04/2014 10:22 AM, loonsailor wrote: When I sudo, I no longer get an error on the modprobe (duh!), but it still doesn't make a device at the /dev level, like /dev/ttyusb0 or similar. Should it? Or should I just have my software, which expects a serial device (it's talking to a weather station) directly access /dev/bus/usb/001/003. If I want a tty-type device, is it enough to 'ln -s /dev/bus/... /dev/ttyUSB', either manually or with udev, or does a usb-serial device need some sort of pseudo-driver for serial protocols? Thanks again! Hi, you might want to take a look at 'dmesg' to see if a device is created when inserting the kernel module. This is what I get when connecting a pl2303 based usb-rs232 adapter: - (desktop x86 machine): ~$ uname -a Linux antec 3.8.0-34-generic #49-Ubuntu SMP Tue Nov 12 18:00:10 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux ~$ lsb_release -a LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch Distributor ID:Ubuntu Description:Ubuntu 13.04 [83848.138366] usb 2-1.8.6: new full-speed USB device number 8 using ehci-pci [83848.231040] usb 2-1.8.6: New USB device found, idVendor=067b, idProduct=2303 [83848.231045] usb 2-1.8.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [83848.231047] usb 2-1.8.6: Product: USB-Serial Controller [83848.231050] usb 2-1.8.6: Manufacturer: Prolific Technology Inc. [83848.231337] pl2303 2-1.8.6:1.0: pl2303 converter detected [83848.232879] usb 2-1.8.6: pl2303 converter now attached to ttyUSB0 - (beaglebone black) ~$ uname -a Linux bb2 3.8.13-bone28 #1 SMP Fri Sep 13 01:11:14 UTC 2013 armv7l armv7l armv7l GNU/Linux ~$ lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 13.10 [ 472.737991] usb usb1: usb wakeup-resume [ 472.738086] usb usb1: usb auto-resume [ 472.738138] hub 1-0:1.0: hub_resume [ 472.738259] hub 1-0:1.0: port 1: status 0101 change 0001 [ 472.840661] hub 1-0:1.0: state 7 ports 1 chg 0002 evt [ 472.840787] hub 1-0:1.0: port 1, status 0101, change , 12 Mb/s [ 472.946041] usb 1-1: new full-speed USB device number 2 using musb-hdrc [ 473.065944] usb 1-1: default language 0x0409 [ 473.066357] usb 1-1: udev 2, busnum 1, minor = 1 [ 473.066401] usb 1-1: New USB device found, idVendor=067b, idProduct=2303 [ 473.066439] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 473.066473] usb 1-1: Product: USB-Serial Controller [ 473.066505] usb 1-1: Manufacturer: Prolific Technology Inc. [ 473.071233] usb 1-1: usb_probe_device [ 473.071294] usb 1-1: configuration #1 chosen from 1 choice [ 473.072221] usb 1-1: adding 1-1:1.0 (config #1, interface 0) [ 473.080129] hub 1-0:1.0: state 7 ports 1 chg evt 0002 [ 473.080247] hub 1-0:1.0: port 1 enable change, status 0103 [ 473.175207] usbcore: registered new interface driver usbserial [ 473.175427] usbcore: registered new interface driver usbserial_generic [ 473.175638] usbserial: USB Serial support registered for generic [ 473.193055] usbcore: registered new interface driver pl2303 [ 473.193317] usbserial: USB Serial support registered for pl2303 [ 473.193446] pl2303 1-1:1.0: usb_probe_interface [ 473.193487] pl2303 1-1:1.0: usb_probe_interface - got id [ 473.193564] pl2303 1-1:1.0: pl2303 converter detected [ 473.206726] usb 1-1: pl2303 converter now attached to ttyUSB0 As you can see, there's a ttyUSB0 device being created. Can you show what you get from 'dmesg' or /var/log/kern.log ? Cheers, Nuno -- http://aeminium.org/nuno/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe
Re: [beagleboard] usb-serial device doesn't appear in /dev. Need a udev rule?
On 01/05/2014 01:07 AM, loonsailor wrote:
The Startech device, with the TI chipset, continues to have the same
problem. I've tried a couple of other converters, Keyspan and Trendnet,
both of which use the Prolific chipset, and they do work, making both
Hi,
if you feel brave enough, you could try to patch the kernel
drivers/usb/serial/ti_usb_3410_5052.{c,h} files and add the startech usb
vendor id, see attachment.
Since I don't have that device, I cannot test it myself, but if works
with you it can then be sent upstream.
Which kernel do you have (cat /proc/version)? I could compile the
module for you, if you are willing to test it.
regards,
Nuno
--
http://aeminium.org/nuno/
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
BeagleBoard group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
diff --git a/drivers/usb/serial/ti_usb_3410_5052.c b/drivers/usb/serial/ti_usb_3410_5052.c
index c9a3569..085afb3 100644
--- a/drivers/usb/serial/ti_usb_3410_5052.c
+++ b/drivers/usb/serial/ti_usb_3410_5052.c
@@ -146,6 +146,7 @@ static int closing_wait = TI_DEFAULT_CLOSING_WAIT;
static struct usb_device_id ti_id_table_3410[] = {
{ USB_DEVICE(TI_VENDOR_ID, TI_3410_PRODUCT_ID) },
{ USB_DEVICE(TI_VENDOR_ID, TI_3410_EZ430_ID) },
+ { USB_DEVICE(STARTECH_VENDOR_ID, TI_3410_PRODUCT_ID) },
{ USB_DEVICE(MTS_VENDOR_ID, MTS_GSM_NO_FW_PRODUCT_ID) },
{ USB_DEVICE(MTS_VENDOR_ID, MTS_CDMA_NO_FW_PRODUCT_ID) },
{ USB_DEVICE(MTS_VENDOR_ID, MTS_CDMA_PRODUCT_ID) },
@@ -174,6 +175,7 @@ static struct usb_device_id ti_id_table_5052[] = {
static struct usb_device_id ti_id_table_combined[] = {
{ USB_DEVICE(TI_VENDOR_ID, TI_3410_PRODUCT_ID) },
{ USB_DEVICE(TI_VENDOR_ID, TI_3410_EZ430_ID) },
+ { USB_DEVICE(STARTECH_VENDOR_ID, TI_3410_PRODUCT_ID) },
{ USB_DEVICE(MTS_VENDOR_ID, MTS_GSM_NO_FW_PRODUCT_ID) },
{ USB_DEVICE(MTS_VENDOR_ID, MTS_CDMA_NO_FW_PRODUCT_ID) },
{ USB_DEVICE(MTS_VENDOR_ID, MTS_CDMA_PRODUCT_ID) },
diff --git a/drivers/usb/serial/ti_usb_3410_5052.h b/drivers/usb/serial/ti_usb_3410_5052.h
index 4a2423e..10a2879 100644
--- a/drivers/usb/serial/ti_usb_3410_5052.h
+++ b/drivers/usb/serial/ti_usb_3410_5052.h
@@ -28,6 +28,7 @@
/* Vendor and product ids */
#define TI_VENDOR_ID 0x0451
#define IBM_VENDOR_ID 0x04b3
+#define STARTECH_VENDOR_ID 0x14b0
#define TI_3410_PRODUCT_ID 0x3410
#define IBM_4543_PRODUCT_ID 0x4543
#define IBM_454B_PRODUCT_ID 0x454b
Re: [beagleboard] usb-serial device doesn't appear in /dev. Need a udev rule?
On 01/03/2014 10:52 PM, loonsailor wrote: 'ERROR: could not insert 'ti_usb_3410_5052': Operation not permitted'. Thanks for the help. This is a bit new to me. Try to do that using sudo or as root :) sudo modprobe ti_usb_3410_5052 If you want a more permanent solution that survives reboots, you can either put that module into /etc/modules or setup udev to load it on insertion. regards, Nuno -- http://aeminium.org/nuno/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] usb-serial device doesn't appear in /dev. Need a udev rule?
On Sat, Jan 4, 2014 at 8:22 AM, Nuno Sucena Almeida n...@aeminium.org wrote: On 01/03/2014 10:52 PM, loonsailor wrote: 'ERROR: could not insert 'ti_usb_3410_5052': Operation not permitted'. Thanks for the help. This is a bit new to me. Try to do that using sudo or as root :) sudo modprobe ti_usb_3410_5052 If you want a more permanent solution that survives reboots, you can either put that module into /etc/modules or setup udev to load it on insertion. Can you confirm this resolved your issue? regards, Nuno -- http://aeminium.org/nuno/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out. -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] usb-serial device doesn't appear in /dev. Need a udev rule?
When I sudo, I no longer get an error on the modprobe (duh!), but it still doesn't make a device at the /dev level, like /dev/ttyusb0 or similar. Should it? Or should I just have my software, which expects a serial device (it's talking to a weather station) directly access /dev/bus/usb/001/003. If I want a tty-type device, is it enough to 'ln -s /dev/bus/... /dev/ttyUSB', either manually or with udev, or does a usb-serial device need some sort of pseudo-driver for serial protocols? Thanks again! On Saturday, January 4, 2014 6:23:44 AM UTC-8, Jason Kridner wrote: On Sat, Jan 4, 2014 at 8:22 AM, Nuno Sucena Almeida nu...@aeminium.orgjavascript: wrote: Try to do that using sudo or as root :) sudo modprobe ti_usb_3410_5052 -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] usb-serial device doesn't appear in /dev. Need a udev rule?
The Startech device, with the TI chipset, continues to have the same problem. I've tried a couple of other converters, Keyspan and Trendnet, both of which use the Prolific chipset, and they do work, making both /dev/serial devices and /dev/ttyUSB0. It may be fixable with the Startech converter, but since the other converters work straight out of the box, I'm just going to use one of them and move on to the next step of making my system work. Thanks for the help, Nuno! On Saturday, January 4, 2014 9:48:07 AM UTC-8, Nuno wrote: On 01/04/2014 10:22 AM, loonsailor wrote: When I sudo, I no longer get an error on the modprobe (duh!), but it still doesn't make a device at the /dev level, like /dev/ttyusb0 or similar. Should it? Or should I just have my software, which expects a serial device (it's talking to a weather station) directly access /dev/bus/usb/001/003. If I want a tty-type device, is it enough to 'ln -s /dev/bus/... /dev/ttyUSB', either manually or with udev, or does a usb-serial device need some sort of pseudo-driver for serial protocols? Thanks again! Hi, you might want to take a look at 'dmesg' to see if a device is created when inserting the kernel module. This is what I get when connecting a pl2303 based usb-rs232 adapter: - (desktop x86 machine): ~$ uname -a Linux antec 3.8.0-34-generic #49-Ubuntu SMP Tue Nov 12 18:00:10 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux ~$ lsb_release -a LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch Distributor ID:Ubuntu Description:Ubuntu 13.04 [83848.138366] usb 2-1.8.6: new full-speed USB device number 8 using ehci-pci [83848.231040] usb 2-1.8.6: New USB device found, idVendor=067b, idProduct=2303 [83848.231045] usb 2-1.8.6: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [83848.231047] usb 2-1.8.6: Product: USB-Serial Controller [83848.231050] usb 2-1.8.6: Manufacturer: Prolific Technology Inc. [83848.231337] pl2303 2-1.8.6:1.0: pl2303 converter detected [83848.232879] usb 2-1.8.6: pl2303 converter now attached to ttyUSB0 - (beaglebone black) ~$ uname -a Linux bb2 3.8.13-bone28 #1 SMP Fri Sep 13 01:11:14 UTC 2013 armv7l armv7l armv7l GNU/Linux ~$ lsb_release -a No LSB modules are available. Distributor ID:Ubuntu Description:Ubuntu 13.10 [ 472.737991] usb usb1: usb wakeup-resume [ 472.738086] usb usb1: usb auto-resume [ 472.738138] hub 1-0:1.0: hub_resume [ 472.738259] hub 1-0:1.0: port 1: status 0101 change 0001 [ 472.840661] hub 1-0:1.0: state 7 ports 1 chg 0002 evt [ 472.840787] hub 1-0:1.0: port 1, status 0101, change , 12 Mb/s [ 472.946041] usb 1-1: new full-speed USB device number 2 using musb-hdrc [ 473.065944] usb 1-1: default language 0x0409 [ 473.066357] usb 1-1: udev 2, busnum 1, minor = 1 [ 473.066401] usb 1-1: New USB device found, idVendor=067b, idProduct=2303 [ 473.066439] usb 1-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0 [ 473.066473] usb 1-1: Product: USB-Serial Controller [ 473.066505] usb 1-1: Manufacturer: Prolific Technology Inc. [ 473.071233] usb 1-1: usb_probe_device [ 473.071294] usb 1-1: configuration #1 chosen from 1 choice [ 473.072221] usb 1-1: adding 1-1:1.0 (config #1, interface 0) [ 473.080129] hub 1-0:1.0: state 7 ports 1 chg evt 0002 [ 473.080247] hub 1-0:1.0: port 1 enable change, status 0103 [ 473.175207] usbcore: registered new interface driver usbserial [ 473.175427] usbcore: registered new interface driver usbserial_generic [ 473.175638] usbserial: USB Serial support registered for generic [ 473.193055] usbcore: registered new interface driver pl2303 [ 473.193317] usbserial: USB Serial support registered for pl2303 [ 473.193446] pl2303 1-1:1.0: usb_probe_interface [ 473.193487] pl2303 1-1:1.0: usb_probe_interface - got id [ 473.193564] pl2303 1-1:1.0: pl2303 converter detected [ 473.206726] usb 1-1: pl2303 converter now attached to ttyUSB0 As you can see, there's a ttyUSB0 device being created. Can you show what you get from 'dmesg' or /var/log/kern.log ? Cheers, Nuno -- http://aeminium.org/nuno/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] usb-serial device doesn't appear in /dev. Need a udev rule?
On 01/03/2014 08:36 PM, loonsailor wrote: Bus 001 Device 003: ID 14b0:3410 StarTech.com Ltd. A quick search leads me to the 'ti_usb_3410_5052' module, is it being loaded? You can check with lsmod: ~$ lsmod ~$ modinfo -d ti_usb_3410_5052 TI USB 3410/5052 Serial Driver regards, Nuno -- http://aeminium.org/nuno/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
Re: [beagleboard] usb-serial device doesn't appear in /dev. Need a udev rule?
Yes, I guess so. ubuntu@weather:~$ lsmod Module Size Used by g_multi56263 0 libcomposite 17081 1 g_multi ubuntu@weather:~$ modinfo -d ti_usb_3410_5052 TI USB 3410/5052 Serial Driver So, what does this tell me? I still don't know how to get a serial device that my program can use. Or, should it just use /bus/usb/001/003? I tried 'modprobe ti_usb_3410_5052', and I get 'ERROR: could not insert 'ti_usb_3410_5052': Operation not permitted'. Thanks for the help. This is a bit new to me. On Friday, January 3, 2014 6:34:56 PM UTC-8, Nuno wrote: On 01/03/2014 08:36 PM, loonsailor wrote: Bus 001 Device 003: ID 14b0:3410 StarTech.com Ltd. A quick search leads me to the 'ti_usb_3410_5052' module, is it being loaded? You can check with lsmod: ~$ lsmod ~$ modinfo -d ti_usb_3410_5052 TI USB 3410/5052 Serial Driver regards, Nuno -- http://aeminium.org/nuno/ -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups BeagleBoard group. To unsubscribe from this group and stop receiving emails from it, send an email to beagleboard+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
