gpsd, gdal and gpsdrive


as promised I’ve dropped gpsd 2.32, gdal 1.3.2 and gpsdrive 2.10 from cvs at the openSUSE buildservice. I hope they will be build soon. gpsdrive will be the last package, it depends on gdal and it is blocked atm.

Please let me know if you have problems. I dunno if the gpsd udev script works as expected. There is a bug in gpsd which doesn’t detect my device using the F command.

gpsdrive has dropped their gpsd so you have to use the original gpsd.Please let me know if something doesn’t work for you.

You can download it from or your favourite repository mirror 😉

You may also like...

2 Responses

  1. Ulrich Voigt says:


    I have just updated the SuSE 10.1 kernel to and I do now have the problem that the /proc/bus/usb/devices directory is missing. From some websearch I have found the bug which sounds to me that this might be no longer supported.

    Due to the /proc/bus/usb/devices problem gpsd is no longer working. Can you confirm this and can you also compile a new version which runs with the most up to date SuSE 10.1?


  2. Ulrich Voigt says:

    I have to add some infos to my last comment:

    The problem seems to be located in the garmin_gps module.
    If I connect a SIRF GPS everything works.

    If I connect a brand new Garmin GPS 18 I get the follwoing messages (started gpsd -n -N -D 5 /dev/ttyUSB0):
    gpsd: launching (Version 2.34)
    gpsd: listening on port gpsd
    gpsd: shmat(0,0,0) succeeded
    gpsd: shmat(0,0,0) succeeded
    gpsd: shmat(0,0,0) succeeded
    gpsd: shmat(0,0,0) succeeded
    gpsd: running with effective group ID 0
    gpsd: running with effective user ID 0
    gpsd: opening GPS data source at ‘/dev/ttyUSB0’
    gpsd: speed 9600, 8N1
    gpsd: Can’t open /proc/bus/usb/devices
    gpsd: no probe matched…
    gpsd: gpsd_activate(1): opened GPS (5)

    My current kernel is the taken from SuSE (no recompilation):
    Linux swe2-sp #1 SMP Wed Dec 13 09:34:50 UTC 2006 x86_64 x86_64 x86_64 GNU/Linux

    I hope that helps to locate the error.


Leave a Reply

Your email address will not be published. Required fields are marked *