Running gpsbabel with my Garmin eTrex Vista C software version 2.60
returns the following error:
jansw@...:~> gpsbabel -D9 -w -i garmin -f usb: -o gpx -F foo.gpx
GPSBabel Version: 1.3.0
usb_set_configuration failed: could not set config 1: Operation not
I am running SuSe Linux 10.0 with kernel 2.6.13-15.10
After switicing on my Garmin device it is recognized by Linux.
Bus 003 Device 001: ID 0000:0000
Bus 002 Device 002: ID 05e3:0502 Genesys Logic, Inc. GL620USB GeneLink
Bus 002 Device 001: ID 0000:0000
Bus 001 Device 027: ID 091e:0003 Garmin International GPSmap 60C / GPS
18 / Vista C
Bus 001 Device 002: ID 05e3:0606 Genesys Logic, Inc.
Bus 001 Device 001: ID 0000:0000
and also /var/log/messages takes note of it by writing:
Aug 21 23:15:53 athlon kernel: drivers/usb/serial/usb-serial.c: USB
Serial support registered for Garmin GPS usb/tty
Aug 21 23:15:53 athlon kernel: garmin_gps 1-2.4:1.0: Garmin GPS usb/tty
Aug 21 23:15:53 athlon kernel: usb 1-2.4: Garmin GPS usb/tty converter
now attached to ttyUSB0
Aug 21 23:15:53 athlon kernel: usbcore: registered new driver garmin_gps
jansw@...:~> lsmod | grep gps
garmin_gps 17284 0
usbserial 28776 1 garmin_gps
usbcore 112512 6 garmin_gps,usbserial,usblp,usbnet,uhci_hcd
Reading the FAQ suggests to remove (rmmod) garmin_gps from the kernel.
This does not solve (or change) the above problem, but /var/log/messages
then writes only:
Aug 21 23:53:46 athlon kernel: usb 1-2.4: new full speed USB device
using uhci_hcd and address 33
Of course lsmod then returns no *gps* modules.
Any help would be welcome. The more since it once worked (with an
earlier version of gpsbabel, an earlier version of SuSe linux and an
earlier version of the garmin software ... >:o ).
From: Robert Lipe <robertlipe@us...> - 2006-08-21 22:15:16
> jansw@...:~> gpsbabel -D9 -w -i garmin -f usb: -o gpx -F foo.gpx
> GPSBabel Version: 1.3.0
> usb_set_configuration failed: could not set config 1: Operation not
EPERM tells us the permissions on your dev node are insufficient. If you
run it as root it works, right?
It's likely that Suse does it in some way just different enough to be
annoying, but see the first section of
Bonus points for providing writeup for any needed Suse-specific info
for that page.