Quantcast

Garmin 205, bad payload size error, Linux Mint

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Garmin 205, bad payload size error, Linux Mint

Ian Dent

On almost every attempt to upload a .tcx track to my Garmin 205 device
using GPSbabel 1.5.2 I get the "bad payload size" error. The error
occurs at different times and always reports a different bad payload
size. For example:

./gpsbabel -t -i gtrnctr -f /home/ian/Documents/Bike/Routes/Simple.tcx
-o garmin -F usb:
[ERROR] GPS_Packet_Read_usb: Bad payload size 738197504

Sometimes the gpsbabel execution completes after reporting the error,
sometimes (more often) it doesn't complete and has to be stopped with
ctrlC.

Repeating the command will eventually succeed but takes about 40-50
attempts before it works.

This happens with all tcx files I use. I enclose a simple example tcx
file created using RidewithGPS and then exported.

./gpsbabel -t -D10 -i gtrnctr -f
/home/ian/Documents/Bike/Routes/Simple.tcx -o garmin -F usb: >error.txt
GPSBabel Version: 1.5.2
Waypoint type: 110
Chosen waypoint length 10
[ERROR] GPS_Packet_Read_usb: Bad payload size -1157627904
^C

I built this version of gpsbabel from the downloaded source. I'm running
Linux Mint 17.1

uname -a
Linux zoomint 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux

Using the version of gpsbabel included in Linux Mint I get the following:

gpsbabel -t -D10 -i gtrnctr -f
/home/ian/Documents/Bike/Routes/Simple.tcx -o garmin -F usb: >error2.txt
GPSBabel Version: 1.4.3
Waypoint type: 110
Chosen waypoint length 10
[ERROR] GPS_Packet_Read_usb: Bad payload size -1358954496
^C

Any advice on how to workaround this problem would be greatly
appreciated. If you need more information to help me then please ask.

I see there was some discussion of this problem (and possibly a
solution) in 2010 - see
http://sourceforge.net/p/gpsbabel/mailman/message/25565715/ I'm
certainly not an expert at programming (or building from source) so may
have included old libraries by mistake? I built the gpsbabel executable
by ./configure; make

Libusb-dev was installed and version is shown below

dpkg -l |grep libusb
ii  libgusb-dev 0.1.6-5
amd64 GLib wrapper around libusb1 - development files
ii  libgusb2:amd64 0.1.6-5
amd64 GLib wrapper around libusb1
ii  libusb-0.1-4:amd64
2:0.1.12-23.3ubuntu1                                amd64 userspace USB
programming library
ii  libusb-1.0-0:amd64
2:1.0.17-1ubuntu2                                   amd64 userspace USB
programming library
ii  libusb-1.0-0:i386
2:1.0.17-1ubuntu2                                   i386 userspace USB
programming library
ii  libusb-1.0-0-dev:amd64
2:1.0.17-1ubuntu2                                   amd64 userspace USB
programming library development files
ii  libusb-dev 2:0.1.12-23.3ubuntu1                                amd64
userspace USB programming library development files
ii  libusbmuxd2 1.0.8-2ubuntu1
amd64        USB multiplexor daemon for iPhone and iPod Touch devices -
library


Thanks,

Ian




------------------------------------------------------------------------------

_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc

Simple.tcx (12K) Download Attachment
error.txt (94K) Download Attachment
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Garmin 205, bad payload size error, Linux Mint

Robert Lipe-4
Hi, Ian.

Thanx for a well thought out post and for doing your homework.

To my knowledge, Martin was the only GPSBabel user that's encountered this.  The intersection of GPSBabel, any specific Garmin device (esp. the older and niche products like this) and Linux is very likely a very tiny number of individuals.  The "fix" that Martin made is triggered only on a Forerunner 305 (that's the 'gps_save_id' part of his change in gpsusbread.c (which is now gpsusbread.cc).  If I recall correctly, the Forerunner/Foretracker 305 and 205's were of the same generation, so it's certainly worth enabling his fix on your device and trying.  It should be harmless and easy to try - certainly easier than putting that combination on a logic analyzer or getting Garmin to comment on the USB implementation of a device that age.

Find the code that currently says:

if (gps_save_id == 484

and change it to 
  if ((gps_save_id == 484 || gps_save_id == 450) 

rebuild and see if that's better.  Your debug output says your device ID is 450, so in English, that's "if the device id = Martin's device OR the device id = your device... do that horrible thing.


Since he was seeing it on tracks and you're using courses, there may be some additional fiddling with that chain of logic in that 'if'  to catch your case, but let's try the easy things first.  Frankly, since you uniquely have the failing combination, if that easy thing doesn't work,  the next step will be to add debug prints of all that jazz and see what case isn't true for the failing packet. gusb_pkt is defined in jeeps/garminusb.h  

If your debug output shows the same style of failure his did (notice the missing 0x14 (that's decimal 20) that you see us stuffing back into pkg.gusb_pkt.type after moving everything right), we're on the right track.

Look earlier in that thread and see where the pattern breaks.

RX (intr) [36]:14 00 00 00 22 00 00 00 18 00 00 00 92 f8 a9 20 c7 c5 56 06 43 a0 52 26 a8 d1 23 44 69 ec db 45 00 ff 00 00 ..................V.C.R....Di..E....(TRKDAT  )
RX timestamps: 1275596996.980597/1275596996.981579
RX (intr) [36]:14 00 00 00 22 00 00 00 18 00 00 00 ad f3 a9 20 84 c3 56 06 4c a0 52 26 3c 8a 24 44 cb 4e dc 45 00 ff 00 00 ..................V.L.R....D.N.E....(TRKDAT  )
RX timestamps: 1275596996.981616/1275596996.983577
RX (intr) [35]:00 00 00 22 00 00 00 18 00 00 00 8f ef a9 20 42 c1 56 06 53 a0 52 26 44 05 25 44 6e a2 dc 45 00 ff 00 00 ...............B.V.S.R.D..Dn..E....(UNKNOWN )
[ERROR] GPS_Packet_Read_usb: Bad payload size -1895825408

I *think* everything being tested there is lower level than would be affected by CRS vs. TRK, but I'd be very happy to never look at that Garmin spec again...

Let us know how it plays out!

RJL



On Sun, Nov 15, 2015 at 2:35 PM, Ian Dent <[hidden email]> wrote:

On almost every attempt to upload a .tcx track to my Garmin 205 device
using GPSbabel 1.5.2 I get the "bad payload size" error. The error
occurs at different times and always reports a different bad payload
size. For example:

./gpsbabel -t -i gtrnctr -f /home/ian/Documents/Bike/Routes/Simple.tcx
-o garmin -F usb:
[ERROR] GPS_Packet_Read_usb: Bad payload size 738197504

Sometimes the gpsbabel execution completes after reporting the error,
sometimes (more often) it doesn't complete and has to be stopped with
ctrlC.

Repeating the command will eventually succeed but takes about 40-50
attempts before it works.

This happens with all tcx files I use. I enclose a simple example tcx
file created using RidewithGPS and then exported.

./gpsbabel -t -D10 -i gtrnctr -f
/home/ian/Documents/Bike/Routes/Simple.tcx -o garmin -F usb: >error.txt
GPSBabel Version: 1.5.2
Waypoint type: 110
Chosen waypoint length 10
[ERROR] GPS_Packet_Read_usb: Bad payload size -1157627904
^C

I built this version of gpsbabel from the downloaded source. I'm running
Linux Mint 17.1

uname -a
Linux zoomint 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux

Using the version of gpsbabel included in Linux Mint I get the following:

gpsbabel -t -D10 -i gtrnctr -f
/home/ian/Documents/Bike/Routes/Simple.tcx -o garmin -F usb: >error2.txt
GPSBabel Version: 1.4.3
Waypoint type: 110
Chosen waypoint length 10
[ERROR] GPS_Packet_Read_usb: Bad payload size -1358954496
^C

Any advice on how to workaround this problem would be greatly
appreciated. If you need more information to help me then please ask.

I see there was some discussion of this problem (and possibly a
solution) in 2010 - see
http://sourceforge.net/p/gpsbabel/mailman/message/25565715/ I'm
certainly not an expert at programming (or building from source) so may
have included old libraries by mistake? I built the gpsbabel executable
by ./configure; make

Libusb-dev was installed and version is shown below

dpkg -l |grep libusb
ii  libgusb-dev 0.1.6-5
amd64 GLib wrapper around libusb1 - development files
ii  libgusb2:amd64 0.1.6-5
amd64 GLib wrapper around libusb1
ii  libusb-0.1-4:amd64
2:0.1.12-23.3ubuntu1                                amd64 userspace USB
programming library
ii  libusb-1.0-0:amd64
2:1.0.17-1ubuntu2                                   amd64 userspace USB
programming library
ii  libusb-1.0-0:i386
2:1.0.17-1ubuntu2                                   i386 userspace USB
programming library
ii  libusb-1.0-0-dev:amd64
2:1.0.17-1ubuntu2                                   amd64 userspace USB
programming library development files
ii  libusb-dev 2:0.1.12-23.3ubuntu1                                amd64
userspace USB programming library development files
ii  libusbmuxd2 1.0.8-2ubuntu1
amd64        USB multiplexor daemon for iPhone and iPod Touch devices -
library


Thanks,

Ian




------------------------------------------------------------------------------

_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc



------------------------------------------------------------------------------
Presto, an open source distributed SQL query engine for big data, initially
developed by Facebook, enables you to easily query your data on Hadoop in a
more interactive manner. Teradata is also now providing full enterprise
support for Presto. Download a free open source copy now.
http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Garmin 205, bad payload size error, Linux Mint

Ian Dent
Robert,

Thanks very much for your advice. Seems to work well. The transfer may take slightly longer but that is no problem at all (a couple of extra seconds maybe although I'm guessing).

My device is actually a Garmin Edge 205 rather a Forerunner 205 but adding the correct device id certainly removed the problem. Maybe implement this as a code change for all of Edge 205, 305 and Forerunner 205, 305?

I take your point that I'm probably in a small group using Edge devices with Linux but, looking around the internet for help, I don't think I'm the only person who has hit problems.

No idea why I've hit the problem as I can't see anything odd that I've done with my PC. Never mind its working now so I can concentrate on cycling!

For anyone else hitting a similar problem they should follow Robert's instructions. The gpsusbread.cc file is in the jeeps subdirectory of the downloaded source code. Make sure you make the right edit (check the brackets) exactly as Robert says.

Thanks again,

Ian

On 16/11/15 03:26, Robert Lipe wrote:
Hi, Ian.

Thanx for a well thought out post and for doing your homework.

To my knowledge, Martin was the only GPSBabel user that's encountered this.  The intersection of GPSBabel, any specific Garmin device (esp. the older and niche products like this) and Linux is very likely a very tiny number of individuals.  The "fix" that Martin made is triggered only on a Forerunner 305 (that's the 'gps_save_id' part of his change in gpsusbread.c (which is now gpsusbread.cc).  If I recall correctly, the Forerunner/Foretracker 305 and 205's were of the same generation, so it's certainly worth enabling his fix on your device and trying.  It should be harmless and easy to try - certainly easier than putting that combination on a logic analyzer or getting Garmin to comment on the USB implementation of a device that age.

Find the code that currently says:

if (gps_save_id == 484

and change it to 
  if ((gps_save_id == 484 || gps_save_id == 450) 

rebuild and see if that's better.  Your debug output says your device ID is 450, so in English, that's "if the device id = Martin's device OR the device id = your device... do that horrible thing.


Since he was seeing it on tracks and you're using courses, there may be some additional fiddling with that chain of logic in that 'if'  to catch your case, but let's try the easy things first.  Frankly, since you uniquely have the failing combination, if that easy thing doesn't work,  the next step will be to add debug prints of all that jazz and see what case isn't true for the failing packet. gusb_pkt is defined in jeeps/garminusb.h  

If your debug output shows the same style of failure his did (notice the missing 0x14 (that's decimal 20) that you see us stuffing back into pkg.gusb_pkt.type after moving everything right), we're on the right track.

Look earlier in that thread and see where the pattern breaks.

RX (intr) [36]:14 00 00 00 22 00 00 00 18 00 00 00 92 f8 a9 20 c7 c5 56 06 43 a0 52 26 a8 d1 23 44 69 ec db 45 00 ff 00 00 ..................V.C.R....Di..E....(TRKDAT  )
RX timestamps: 1275596996.980597/1275596996.981579
RX (intr) [36]:14 00 00 00 22 00 00 00 18 00 00 00 ad f3 a9 20 84 c3 56 06 4c a0 52 26 3c 8a 24 44 cb 4e dc 45 00 ff 00 00 ..................V.L.R....D.N.E....(TRKDAT  )
RX timestamps: 1275596996.981616/1275596996.983577
RX (intr) [35]:00 00 00 22 00 00 00 18 00 00 00 8f ef a9 20 42 c1 56 06 53 a0 52 26 44 05 25 44 6e a2 dc 45 00 ff 00 00 ...............B.V.S.R.D..Dn..E....(UNKNOWN )
[ERROR] GPS_Packet_Read_usb: Bad payload size -1895825408

I *think* everything being tested there is lower level than would be affected by CRS vs. TRK, but I'd be very happy to never look at that Garmin spec again...

Let us know how it plays out!

RJL



On Sun, Nov 15, 2015 at 2:35 PM, Ian Dent <[hidden email]> wrote:

On almost every attempt to upload a .tcx track to my Garmin 205 device
using GPSbabel 1.5.2 I get the "bad payload size" error. The error
occurs at different times and always reports a different bad payload
size. For example:

./gpsbabel -t -i gtrnctr -f /home/ian/Documents/Bike/Routes/Simple.tcx
-o garmin -F usb:
[ERROR] GPS_Packet_Read_usb: Bad payload size 738197504

Sometimes the gpsbabel execution completes after reporting the error,
sometimes (more often) it doesn't complete and has to be stopped with
ctrlC.

Repeating the command will eventually succeed but takes about 40-50
attempts before it works.

This happens with all tcx files I use. I enclose a simple example tcx
file created using RidewithGPS and then exported.

./gpsbabel -t -D10 -i gtrnctr -f
/home/ian/Documents/Bike/Routes/Simple.tcx -o garmin -F usb: >error.txt
GPSBabel Version: 1.5.2
Waypoint type: 110
Chosen waypoint length 10
[ERROR] GPS_Packet_Read_usb: Bad payload size -1157627904
^C

I built this version of gpsbabel from the downloaded source. I'm running
Linux Mint 17.1

uname -a
Linux zoomint 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux

Using the version of gpsbabel included in Linux Mint I get the following:

gpsbabel -t -D10 -i gtrnctr -f
/home/ian/Documents/Bike/Routes/Simple.tcx -o garmin -F usb: >error2.txt
GPSBabel Version: 1.4.3
Waypoint type: 110
Chosen waypoint length 10
[ERROR] GPS_Packet_Read_usb: Bad payload size -1358954496
^C

Any advice on how to workaround this problem would be greatly
appreciated. If you need more information to help me then please ask.

I see there was some discussion of this problem (and possibly a
solution) in 2010 - see
http://sourceforge.net/p/gpsbabel/mailman/message/25565715/ I'm
certainly not an expert at programming (or building from source) so may
have included old libraries by mistake? I built the gpsbabel executable
by ./configure; make

Libusb-dev was installed and version is shown below

dpkg -l |grep libusb
ii  libgusb-dev 0.1.6-5
amd64 GLib wrapper around libusb1 - development files
ii  libgusb2:amd64 0.1.6-5
amd64 GLib wrapper around libusb1
ii  libusb-0.1-4:amd64
2:0.1.12-23.3ubuntu1                                amd64 userspace USB
programming library
ii  libusb-1.0-0:amd64
2:1.0.17-1ubuntu2                                   amd64 userspace USB
programming library
ii  libusb-1.0-0:i386
2:1.0.17-1ubuntu2                                   i386 userspace USB
programming library
ii  libusb-1.0-0-dev:amd64
2:1.0.17-1ubuntu2                                   amd64 userspace USB
programming library development files
ii  libusb-dev 2:0.1.12-23.3ubuntu1                                amd64
userspace USB programming library development files
ii  libusbmuxd2 1.0.8-2ubuntu1
amd64        USB multiplexor daemon for iPhone and iPod Touch devices -
library


Thanks,

Ian




------------------------------------------------------------------------------

_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc




------------------------------------------------------------------------------
Presto, an open source distributed SQL query engine for big data, initially
developed by Facebook, enables you to easily query your data on Hadoop in a
more interactive manner. Teradata is also now providing full enterprise
support for Presto. Download a free open source copy now.
http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: Garmin 205, bad payload size error, Linux Mint

Robert Lipe-4
Thanx.  Committed per https://github.com/gpsbabel/gpsbabel/commits/master/jeeps/gpsusbread.cc

As for the performance concern, I agree this is totally gross, but it really doesn't matter how quickly something doesn't work.

On Mon, Nov 16, 2015 at 2:23 PM, Ian Dent <[hidden email]> wrote:
Robert,

Thanks very much for your advice. Seems to work well. The transfer may take slightly longer but that is no problem at all (a couple of extra seconds maybe although I'm guessing).

My device is actually a Garmin Edge 205 rather a Forerunner 205 but adding the correct device id certainly removed the problem. Maybe implement this as a code change for all of Edge 205, 305 and Forerunner 205, 305?

I take your point that I'm probably in a small group using Edge devices with Linux but, looking around the internet for help, I don't think I'm the only person who has hit problems.

No idea why I've hit the problem as I can't see anything odd that I've done with my PC. Never mind its working now so I can concentrate on cycling!

For anyone else hitting a similar problem they should follow Robert's instructions. The gpsusbread.cc file is in the jeeps subdirectory of the downloaded source code. Make sure you make the right edit (check the brackets) exactly as Robert says.

Thanks again,

Ian


On 16/11/15 03:26, Robert Lipe wrote:
Hi, Ian.

Thanx for a well thought out post and for doing your homework.

To my knowledge, Martin was the only GPSBabel user that's encountered this.  The intersection of GPSBabel, any specific Garmin device (esp. the older and niche products like this) and Linux is very likely a very tiny number of individuals.  The "fix" that Martin made is triggered only on a Forerunner 305 (that's the 'gps_save_id' part of his change in gpsusbread.c (which is now gpsusbread.cc).  If I recall correctly, the Forerunner/Foretracker 305 and 205's were of the same generation, so it's certainly worth enabling his fix on your device and trying.  It should be harmless and easy to try - certainly easier than putting that combination on a logic analyzer or getting Garmin to comment on the USB implementation of a device that age.

Find the code that currently says:

if (gps_save_id == 484

and change it to 
  if ((gps_save_id == 484 || gps_save_id == 450) 

rebuild and see if that's better.  Your debug output says your device ID is 450, so in English, that's "if the device id = Martin's device OR the device id = your device... do that horrible thing.


Since he was seeing it on tracks and you're using courses, there may be some additional fiddling with that chain of logic in that 'if'  to catch your case, but let's try the easy things first.  Frankly, since you uniquely have the failing combination, if that easy thing doesn't work,  the next step will be to add debug prints of all that jazz and see what case isn't true for the failing packet. gusb_pkt is defined in jeeps/garminusb.h  

If your debug output shows the same style of failure his did (notice the missing 0x14 (that's decimal 20) that you see us stuffing back into pkg.gusb_pkt.type after moving everything right), we're on the right track.

Look earlier in that thread and see where the pattern breaks.

RX (intr) [36]:14 00 00 00 22 00 00 00 18 00 00 00 92 f8 a9 20 c7 c5 56 06 43 a0 52 26 a8 d1 23 44 69 ec db 45 00 ff 00 00 ..................V.C.R....Di..E....(TRKDAT  )
RX timestamps: 1275596996.980597/1275596996.981579
RX (intr) [36]:14 00 00 00 22 00 00 00 18 00 00 00 ad f3 a9 20 84 c3 56 06 4c a0 52 26 3c 8a 24 44 cb 4e dc 45 00 ff 00 00 ..................V.L.R....D.N.E....(TRKDAT  )
RX timestamps: 1275596996.981616/1275596996.983577
RX (intr) [35]:00 00 00 22 00 00 00 18 00 00 00 8f ef a9 20 42 c1 56 06 53 a0 52 26 44 05 25 44 6e a2 dc 45 00 ff 00 00 ...............B.V.S.R.D..Dn..E....(UNKNOWN )
[ERROR] GPS_Packet_Read_usb: Bad payload size -1895825408

I *think* everything being tested there is lower level than would be affected by CRS vs. TRK, but I'd be very happy to never look at that Garmin spec again...

Let us know how it plays out!

RJL



On Sun, Nov 15, 2015 at 2:35 PM, Ian Dent <[hidden email]> wrote:

On almost every attempt to upload a .tcx track to my Garmin 205 device
using GPSbabel 1.5.2 I get the "bad payload size" error. The error
occurs at different times and always reports a different bad payload
size. For example:

./gpsbabel -t -i gtrnctr -f /home/ian/Documents/Bike/Routes/Simple.tcx
-o garmin -F usb:
[ERROR] GPS_Packet_Read_usb: Bad payload size 738197504

Sometimes the gpsbabel execution completes after reporting the error,
sometimes (more often) it doesn't complete and has to be stopped with
ctrlC.

Repeating the command will eventually succeed but takes about 40-50
attempts before it works.

This happens with all tcx files I use. I enclose a simple example tcx
file created using RidewithGPS and then exported.

./gpsbabel -t -D10 -i gtrnctr -f
/home/ian/Documents/Bike/Routes/Simple.tcx -o garmin -F usb: >error.txt
GPSBabel Version: 1.5.2
Waypoint type: 110
Chosen waypoint length 10
[ERROR] GPS_Packet_Read_usb: Bad payload size -1157627904
^C

I built this version of gpsbabel from the downloaded source. I'm running
Linux Mint 17.1

uname -a
Linux zoomint 3.13.0-37-generic #64-Ubuntu SMP Mon Sep 22 21:28:38 UTC
2014 x86_64 x86_64 x86_64 GNU/Linux

Using the version of gpsbabel included in Linux Mint I get the following:

gpsbabel -t -D10 -i gtrnctr -f
/home/ian/Documents/Bike/Routes/Simple.tcx -o garmin -F usb: >error2.txt
GPSBabel Version: 1.4.3
Waypoint type: 110
Chosen waypoint length 10
[ERROR] GPS_Packet_Read_usb: Bad payload size -1358954496
^C

Any advice on how to workaround this problem would be greatly
appreciated. If you need more information to help me then please ask.

I see there was some discussion of this problem (and possibly a
solution) in 2010 - see
http://sourceforge.net/p/gpsbabel/mailman/message/25565715/ I'm
certainly not an expert at programming (or building from source) so may
have included old libraries by mistake? I built the gpsbabel executable
by ./configure; make

Libusb-dev was installed and version is shown below

dpkg -l |grep libusb
ii  libgusb-dev 0.1.6-5
amd64 GLib wrapper around libusb1 - development files
ii  libgusb2:amd64 0.1.6-5
amd64 GLib wrapper around libusb1
ii  libusb-0.1-4:amd64
2:0.1.12-23.3ubuntu1                                amd64 userspace USB
programming library
ii  libusb-1.0-0:amd64
2:1.0.17-1ubuntu2                                   amd64 userspace USB
programming library
ii  libusb-1.0-0:i386
2:1.0.17-1ubuntu2                                   i386 userspace USB
programming library
ii  libusb-1.0-0-dev:amd64
2:1.0.17-1ubuntu2                                   amd64 userspace USB
programming library development files
ii  libusb-dev 2:0.1.12-23.3ubuntu1                                amd64
userspace USB programming library development files
ii  libusbmuxd2 1.0.8-2ubuntu1
amd64        USB multiplexor daemon for iPhone and iPod Touch devices -
library


Thanks,

Ian




------------------------------------------------------------------------------

_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc





------------------------------------------------------------------------------
Presto, an open source distributed SQL query engine for big data, initially
developed by Facebook, enables you to easily query your data on Hadoop in a
more interactive manner. Teradata is also now providing full enterprise
support for Presto. Download a free open source copy now.
http://pubads.g.doubleclick.net/gampad/clk?id=250295911&iu=/4140
_______________________________________________
Gpsbabel-misc mailing list http://www.gpsbabel.org
[hidden email]
To unsubscribe, change list options, or see archives, visit:
https://lists.sourceforge.net/lists/listinfo/gpsbabel-misc
Loading...