Unable to Connect to Garmin eTrex Using Usb to Serial
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
linux-kernel-headers (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gpsbabel
I am not sure exactly where this bug is located. Here is a summary of the problem:
I am trying to connect mu Garmin eTrex via a usb to serial connector and download tracks. The usb to serial uses a well known chip set and is corrected detected:
Oct 22 07:44:16 scamper kernel: [ 1068.953367] usb 5-1: pl2303 converter now attached to ttyUSB0
Oct 22 07:48:57 scamper kernel: [ 1350.542746] usb 5-1: USB disconnect, address 7
Oct 22 07:48:57 scamper kernel: [ 1350.543003] pl2303 ttyUSB0: pl2303 converter now disconnected from ttyUSB0
Oct 22 07:48:57 scamper kernel: [ 1350.543038] pl2303 5-1:1.0: device disconnected
Oct 22 07:49:31 scamper kernel: [ 1384.472677] usb 5-1: new full speed USB device using uhci_hcd and address 8
Oct 22 07:49:31 scamper kernel: [ 1384.633321] pl2303 5-1:1.0: pl2303 converter detected
Oct 22 07:49:31 scamper kernel: [ 1384.646366] usb 5-1: pl2303 converter now attached to ttyUSB0
Now I try to download the waypoints using gpsbabel:
sudo gpsbabel -i garmin -f /dev/ttyUSB0 -o gpx -F waypoints.gpx
This doesn't return any errors, but just hangs waiting for data until I hit ctlr-C. I have tried setting the interface on the Garmin to "Garmin" and "NMEA". I have also tried using gpsd, but still not managed to connect to the eTrex.. I have also tried connecting using gpsd with the same results.
Now if I try on the same computer running Maverick using Windows XP running under Virtual Box, I can connect to the eTrex. If I install Lucid on the computer, I can connect to the eTrex with no problem. I get similar results on another computer runing Maverick. So this seems to point to a problem with the usb to serial driver, or the kernel.
Ian.
I don't think that this is a gpsbabel bug. Versions of gpsbabel that shipped with Lucid show the same bug. Unfortunately, syslog and messages don't provide any information. I suspect that it is either a bug in the usb to serial driver or the kernel. If anyone can tell me how I can provide more debug information, I'll happily do it.
Note changed package to linux-kernel- headers as there doesn't seem to be a pacakge I can find either for the kernel of kernel drivers.