Hello, I have a Garmin gps and wish I had know before I bought it that it wasn't plug an play with Navigatrix! I've been following all the directions over an over today and have pretty much lost the day so thought I ask if there is anyone that can get me over the hump.

I've gone through the steps to configure gpsd. I gone back and put ,/dev/ttyusb2, in to tell it where to find the file. When I get to the end and enter in the "sudo medit /etc/modprobe.d/blacklist.conf" I don't get anything. The command promp comes back. i booted with the usb GPS unplugged and then plugged it and unplugged it then looked at what the files say, but don't know how to decifer or use that info. When I run "lsusb" it shows my Garmin, and lists it as a usb! Still no usb inside the program though. If anyone knows what to do from here it would be much appreciated! This is what it shows
"Bus 001 device 002: ID091c 0003: Garmin international USB (various models)"
Bobby G

Let's see if I can remember how this is done.

I get confused and find it's best to start from the beginning, or at least some place recognisable. Are you working from the stick or have you committed to a hard drive installation? Have all failed attempts reverted to the original state? The number of times I have chased my tail because the changes never reverted meant the right solution would never work, and I would never know.

If you boot up the machine from a cold boot and plug in your gps. will let us see where (if) it gets assigned.

I believe the 18something-x need the -N flag to be set in /etc/defaults/gpsd file.

What type of Garmin is this model?

Thank you Moe for getting back to me!

I am running Navigatrix from a 8 gig stick and have the Garmin 18x model.
i did run some code you suggested to someone else to make sure my changes saved
I did do a check of the tail to see where it put the usb and i think that is what i wrote at the bottom of my message.. I was online on an Ipad reading the forum and not the computer so I wasn't able to post screen shots
I ran the -N with it except when I put in the place to find the usb on the third screen then i took the -N off.
i think you are right best to work through it piece by piece I believe you will see it when it comes up and obviously i am not familiar with having to input code or know what it means when I read it. I am starting a list of the code you suggest for different tasks.
I am living on the boat with no wi-fi but now am at Starbucks with wifi and someone stupid didn’t put his usb gps in his backpack

. I guess you said to boot, put the usb in. and run the tail command and send that to you. Ill do that. not sure what time zone your in Moe,is there a time your usually online? Im on Hawaii time here but will get on whenever your available.

As I recall the Garmin 18x doesn't like gpsd running as a daemon. There's some voodoo curse that is picks up the wrong driver and fails to negotiate with the gpsd. The gpsd then drops the device and moves on.

That may not be true at all, an the explanation may not fit reality and I might have just as well said the misapplator fails on a handshake with the dbus subsystem, because I don't know what that means either.

Tony, a delivery captain, who sails other people's boats upwind on short notice, also had a Garmin 18x, editing /etc/defaults/gpsd Adding the -N in GPSD_OPTIONS It is a good idea to follow the written instructions and use dpkg-reconfigure gpsd (as root) in case you can't modifying files without adding errors. I've learned, if working on a problem 'under the influence' it is better to have the machine worry about format.

If you feel lucky, careful, or invincible, just edit the file and be done with it.

Reboot and see if

• the gpsd gets it sorted out Run xgps, e.g.,
• dmesg | tail to see where the system is stashing it, in case the first attempt (-N) fails.

Other areas to look at while pondering the universe is the physical state of the connectors. Some equipment has enough age to develop personalities and idiosyncrasies. I have a keyboard that will not type a capital 'u'. It's not a problem in America, but doesn't work right in the uS of A.

nx@nx:~$ dmesg | tail
[ 403.852732] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by a2:99:9b:40:e6:1b
[ 480.745629] ata1.00: exception Emask 0x0 SAct 0x0 SErr 0x0 action 0x6
[ 480.745639] ata1.00: waking up from sleep
[ 480.745650] ata1: hard resetting link
[ 481.237827] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[ 481.246696] ata1.00: configured for UDMA/100
[ 481.246717] ata1: EH complete
[ 598.206075] usb 3-1: new full-speed USB device number 2 using xhci_hcd
[ 598.342551] usb 3-1: New USB device found, idVendor=091e, idProduct=0003
[ 598.342560] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
nx@nx:~$

This is what it came up with on 1st boot just now. I'll go in an reset again if you think i should


nx@nx:~$ dmesg | tail
[ 65.628097] wlan0: associate with a2:99:9b:40:e6:1b (try 1/3)
[ 65.659929] wlan0: RX AssocResp from a2:99:9b:40:e6:1b (capab=0x411 status=0 aid=1)
[ 65.660014] wlan0: associated
[ 65.660053] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[ 65.660110] cfg80211: Calling CRDA for country: XZ
[ 65.679929] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by a2:99:9b:40:e6:1b
[ 65.931673] init: samba-ad-dc main process (3519) terminated with status 1
[ 65.999616] Process accounting resumed
[ 92.550672] init: plymouth-upstart-bridge main process ended, respawning
[ 92.567202] init: plymouth-upstart-bridge main process ended, respawning
nx@nx:~$ lsusb
Bus 006 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 008 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 005 Device 002: ID 064e:e263 Suyin Corp.
Bus 005 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 007 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 002: ID 091e:0003 Garmin International GPS (various models)
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 002: ID 05dc:a81d Lexar Media, Inc.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
nx@nx:~$ dmesg | tail
[ 65.660110] cfg80211: Calling CRDA for country: XZ
[ 65.679929] wlan0: Limiting TX power to 20 (20 - 0) dBm as advertised by a2:99:9b:40:e6:1b
[ 65.931673] init: samba-ad-dc main process (3519) terminated with status 1
[ 65.999616] Process accounting resumed
[ 92.550672] init: plymouth-upstart-bridge main process ended, respawning
[ 92.567202] init: plymouth-upstart-bridge main process ended, respawning
[ 194.726350] usb 3-1: USB disconnect, device number 2
[ 207.172151] usb 3-1: new full-speed USB device number 3 using xhci_hcd
[ 207.321255] usb 3-1: New USB device found, idVendor=091e, idProduct=0003
[ 207.321264] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
nx@nx:~$
i ran reconfigure gpsd again found on window 3 a usb location I had put in was still there, took it out and rebooted and this is what came up.
so i just ran reconfigure gpsd again and that 3rd screen still had the location I put in after I ran some code in one of your suguestions to someone else to save his work. Ill try to find the way to stop that

I created a persistance file and now the ttyusb3 is staying even when I change or reconfigure

I don't know what is going on here

This is not consistent with booting up the machine and then inserting the usb-gps.

It looks like you booted with the gps attached and then disconnected it, and then reattached it 12 seconds later

What you don't see is the gps device being assigned to system 'device' (/dev/ttyXXXwhatever) You see the /dev/ttyACM0 is the location of the gps on the system.

For some reason the udev system is not picking up the device and assigning it to a system device.

Let's make sure this is what is going on, and I'm not making things up. This will give me time to figure out the how to tell the system every time is sees idVendor=091e, idProduct=0003 that it will put it some place gpsd can see it.

I had noticed that it didnt look like yours and did not pick up on the why. thank you. so meanwhile Ive figured out how to delete the persistence file. then being connected to the internet here I was able to copy and paste your blacklist code and it finally worked, imagine that. you would think I was a drunken sailor. So I put the hash tag in front and saved. (sorry scared of the correct spelling of octtuhorpe?). Great word!
I will hope you have a easy time figuring out what will fix that

fresh reboot without gps in, then attached Moe.

nx@nx:~$ dmesg | tail
[ 33.636295] IPv6: ADDRCONF(NETDEV_UP): wlan0: link is not ready
[ 34.310998] r8169 0000:05:00.0 eth0: link down
[ 34.313330] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 34.703160] init: alsa-restore main process (2331) terminated with status 99
[ 36.099838] Process accounting resumed
[ 36.507936] init: samba-ad-dc main process (2470) terminated with status 1
[ 41.017736] init: plymouth-upstart-bridge main process ended, respawning
[ 61.713568] usb 3-1: new full-speed USB device number 2 using xhci_hcd
[ 61.849959] usb 3-1: New USB device found, idVendor=091e, idProduct=0003
[ 61.849968] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
nx@nx:~$

Typically you will see the device assigned as with another gps Your's is not finishing the task of attaching the device to the system.

We can write the udev rule to make this happen, when I sift through my notes, or if you want to jump ahead.

Let's try a little experiment.

gpsd has a handful of udev rules already. (/lib/udev/rules.d/40-gpsd.rules) Your Garmin is already listed....that maybe the problem.In lines 36-37 you seeThe experiment it to place a # at the begining of line 37 (#ATTRS{idVendor}=="091e", ATTRS{idProduct}=="0003", SYMLINK+="gps%n", RUN+="/lib/udev/gpsd.hotplug"

Save, reboot, insert the gps, and then run again, to see if the system is attaches it to a system device.

You are also running the gpsd as a non-daemon, that is with the -N flag set in /etc/defaults/gpsd.

If there is still is no attachment run and un/plug the gps to see how the system handles the gps.

Thanks Moe I was away and am back trying it out. here is the rules I changed now I will reboot.
# udev rules for gpsd
#
# This file is Copyright (c) 2010 by the GPSD project
# BSD terms apply: see the file COPYING in the distribution root for details.
#
# GPSes don't have their own USB device class. They're serial-over-USB
# devices, so what you see is actually the ID of the serial-over-USB chip.
# Fortunately, just two of these account for over 80% of consumer-grade
# GPS sensors. The gpsd.hotplug wrapper script will tell a running gpsd
# that it should look at the device that just went active, because it
# might be a GPS.
#
# The following setup works on Debian and Ubuntu - something similar
# will apply on other distributions:
#
# /lib/udev/rules.d/25-gpsd.rules
# /lib/udev/gpsd.hotplug
#
# Setting the link in /lib/udev/rules.d activates the rule and determines
# when to run it on boot (similar to init.d processing).

SUBSYSTEM!="tty", GOTO="gpsd_rules_end"

# Prolific Technology, Inc. PL2303 Serial Port [linux module: pl2303]
ATTRS{idVendor}=="067b", ATTRS{idProduct}=="2303", SYMLINK+="gps%n", RUN+="/lib/udev/gpsd.hotplug"
# ATEN International Co., Ltd UC-232A Serial Port [linux module: pl2303]
ATTRS{idVendor}=="0557", ATTRS{idProduct}=="2008", SYMLINK+="gps%n", RUN+="/lib/udev/gpsd.hotplug"
# PS-360 OEM (GPS sold with MS Street and Trips 2005) [linux module: pl2303]
ATTRS{idVendor}=="067b", ATTRS{idProduct}=="aaa0", SYMLINK+="gps%n", RUN+="/lib/udev/gpsd.hotplug"
# FTDI 8U232AM / FT232 [linux module: ftdi_sio]
ATTRS{idVendor}=="0403", ATTRS{idProduct}=="6001", SYMLINK+="gps%n", RUN+="/lib/udev/gpsd.hotplug"
# Cypress M8/CY7C64013 (Delorme uses these) [linux module: cypress_m8]
ATTRS{idVendor}=="1163", ATTRS{idProduct}=="0100", SYMLINK+="gps%n", RUN+="/lib/udev/gpsd.hotplug"
# Cypress M8/CY7C64013 (DeLorme LT-40)
ATTRS{idVendor}=="1163", ATTRS{idProduct}=="0200", SYMLINK+="gps%n", RUN+="/lib/udev/gpsd.hotplug"
# Garmin International GPSmap, various models (tested with Garmin GPS 18 USB) [linux module: garmin_gps]
# ATTRS{idVendor}=="091e", ATTRS{idProduct}=="0003", SYMLINK+="gps%n", RUN+="/lib/udev/gpsd.hotplug"
# Cygnal Integrated Products, Inc. CP210x Composite Device (Used by Holux m241 and Wintec grays2 wbt-201) [linux module: cp210x]
ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea60", SYMLINK+="gps%n", RUN+="/lib/udev/gpsd.hotplug"
# Cygnal Integrated Products, Inc. [linux module: cp210x]
ATTRS{idVendor}=="10c4", ATTRS{idProduct}=="ea71", SYMLINK="gps%n", RUN+="/lib/udev/gpsd.hotplug"
# u-blox AG, u-blox 5 (tested with Navilock NL-402U) [linux module: cdc_acm]
ATTRS{idVendor}=="1546", ATTRS{idProduct}=="01a5", SYMLINK="gps%n", RUN+="/lib/udev/gpsd.hotplug"
# u-blox AG, u-blox 6 (tested with GNSS Evaluation Kit TCXO) [linux module: cdc_acm]
ATTRS{idVendor}=="1546", ATTRS{idProduct}=="01a6", SYMLINK="gps%n", RUN+="/lib/udev/gpsd.hotplug"
# MediaTek (tested with HOLUX M-1200E) [linux module: cdc_acm]
ATTRS{idVendor}=="0e8d", ATTRS{idProduct}=="3329", SYMLINK="gps%n", RUN+="/lib/udev/gpsd.hotplug"

ACTION=="remove", RUN+="/lib/udev/gpsd.hotplug"

LABEL="gpsd_rules_end"

x:~$ dmesg | tail
[ 68.742383] cfg80211: (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 1700 mBm), (N/A)
[ 68.742387] cfg80211: (5250000 KHz - 5330000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (0 s)
[ 68.742391] cfg80211: (5490000 KHz - 5600000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (0 s)
[ 68.742395] cfg80211: (5650000 KHz - 5710000 KHz @ 40000 KHz), (300 mBi, 2000 mBm), (0 s)
[ 68.742398] cfg80211: (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 3000 mBm), (N/A)
[ 68.742401] cfg80211: (57240000 KHz - 63720000 KHz @ 2160000 KHz), (N/A, 4000 mBm), (N/A)
[ 68.746938] wlan0: Limiting TX power to 30 (30 - 0) dBm as advertised by a2:99:9b:40:e6:1b
[ 117.115499] usb 3-1: new full-speed USB device number 2 using xhci_hcd
[ 117.264408] usb 3-1: New USB device found, idVendor=091e, idProduct=0003
[ 117.264416] usb 3-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
nx@nx:~$

i did it twice to watch it as you will notice

udevadm monitor
monitor will print the received events for:
UDEV - the event which udev sends out after rule processing
KERNEL - the kernel uevent

KERNEL[560.206565] remove /devices/pci0000:00/0000:00:10.1/usb3/3-1/3-1:1.0 (usb)
UDEV [560.208671] remove /devices/pci0000:00/0000:00:10.1/usb3/3-1/3-1:1.0 (usb)
KERNEL[560.209607] remove /devices/pci0000:00/0000:00:10.1/usb3/3-1 (usb)
UDEV [560.210851] remove /devices/pci0000:00/0000:00:10.1/usb3/3-1 (usb)
KERNEL[623.766204] add /devices/pci0000:00/0000:00:10.1/usb3/3-1 (usb)
KERNEL[623.769087] add /devices/pci0000:00/0000:00:10.1/usb3/3-1/3-1:1.0 (usb)
UDEV [623.797684] add /devices/pci0000:00/0000:00:10.1/usb3/3-1 (usb)
UDEV [623.801011] add /devices/pci0000:00/0000:00:10.1/usb3/3-1/3-1:1.0 (usb)
KERNEL[632.759577] remove /devices/pci0000:00/0000:00:10.1/usb3/3-1/3-1:1.0 (usb)
UDEV [632.761697] remove /devices/pci0000:00/0000:00:10.1/usb3/3-1/3-1:1.0 (usb)
KERNEL[632.763401] remove /devices/pci0000:00/0000:00:10.1/usb3/3-1 (usb)
UDEV [632.764594] remove /devices/pci0000:00/0000:00:10.1/usb3/3-1 (usb)

I'm trying to be precise here, because

• I don't have a Garmin 18X usb gps to test
• The last 18X we worked on responded to changes
• your 18X did not respond to that modification (-N)
• I don't have a Garmin 18X....

That's the problem with complex systems, a work-around may become a stumbling block, if something else changes in the system. What was that?

Is there still a reason to blacklist the garmin_gps driver?

I don't know, we are just looking for reasons it's not working. Walk around, poke it with a stick and ponder if would work if it were different.

gpsd creates and keeps a list of gps devices on a system. When a new device is added to the system gpsd queries it, and if it can't provide gps data, that device is dropped from the list.

Your gps isn't even making it to the list.

Let's look at gps being plugged inNow, compared to yoursIn both (yours and mine) the udev event after rule processing was the same as the kernel event, except your device is not loading the module (like usb-serial) to stick on the usb hub module, so it might be assigned a system device /dev/ttyUSBX

Long story short, lets unblacklist the garmin_gps module. Live wild and freeLines 37-38I don't know what they are talking about, but, put an # Octothorpe in front of #blacklist garmin_gps This comments it out.

And cover your bases with the file looks suspiciously similarSuspiciously do the same #blacklist garmin_gps, just in case.

Save, reboot and check for change. If we, and I mean you, strike out on removing the blacklist and gpsd.rules change, revert to the original gpsd.rulesand remove the octothorpe you added earlier.

Cross your fingers. Test with xgps (Menu>Navigation>Gps Satellites). Tell yourself this is fun.

bert@robert-HP-Pavilion-g4-Notebook-PC:~$ dmesg |tail
[ 54.162410] init: anacron main process (1027) killed by TERM signal
[ 55.207640] audit_printk_skb: 108 callbacks suppressed
[ 55.207645] audit: type=1400 audit(1472396256.133:48): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/lib/cups/backend/cups-pdf" pid=2813 comm="apparmor_parser"
[ 55.207657] audit: type=1400 audit(1472396256.133:49): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2813 comm="apparmor_parser"
[ 55.208291] audit: type=1400 audit(1472396256.133:50): apparmor="STATUS" operation="profile_replace" profile="unconfined" name="/usr/sbin/cupsd" pid=2813 comm="apparmor_parser"
[ 62.980415] pps_core: LinuxPPS API ver. 1 registered
[ 62.980423] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
[ 62.991175] pps_ldisc: PPS line discipline registered
[ 62.991535] pps pps0: new PPS source usbserial0
[ 62.991548] pps pps0: source "/dev/ttyUSB0" added
robert@robert-HP-Pavilion-g4-Notebook-PC:~$
looky looky Ive got hooky

Is that a 'Yeah for our side'?

Does the gpsd pick up on the aloof, yet well known Garmin gps signal so other system functions and applications function and applicate?

Was that without the octothorpe (has a rule)? or with the octothorpe commenting out the udev rule? (It shouldn't matter)

Out of curiosity, does it matter if the -N flag is set?

So.... Now it's doing what you wanted assigning the Garmin, after I put the octothorpe in both spots and saved, rebooted. Then I still did not see any GPS action, so I ran the configure again and put in where the GPS was got to the -N screen and it was already off so I saved it that way. I rebooted, still GPS is not showing up as working

aloha Moe! so this is where i am, at the dock instead of sailing! it is what it is, you have been awesome i really appreciate it! One thing I did is download this program onto my removable hard disk where my maps were stashed so I dont have to use 2 usb ports.

I put the octothorpe in the two places and when I rebooted the first time xgps showed the garmin in the line below the screen being on tty/USB0. at the same time no data for gps was coming through. I went into reconfigure and added the place where the garmin was showing up with the tail command, deleted the -N, and rebooted. Rebooting then attaching the garmin and it comes up with the garmin getting asigned too USB0. I still have no gps data coming through. I deleted the octothorpe's, to see if and what changed and once again the Garmin is not assigned a tty/, so i put them back in and this is where I am at. Garmin is geting asigned but not working. Can you work with me now that it is assigned to tweak something to use it? I am pretending this is fun! like sticking a needle in my ear an pushing! J/K really not bad, just would rather be learning to use the charts and programs than the code! In the long run I probably will be better off knowing a few of these tasks.
Thank you for your help!

robert@robert-HP-Pavilion-g4-Notebook-PC:~$ dmesg | tail
[ 279.125524] usbserial: USB Serial support registered for generic
[ 279.135149] usbcore: registered new interface driver garmin_gps
[ 279.135264] usbserial: USB Serial support registered for Garmin GPS usb/tty
[ 279.135344] garmin_gps 3-1:1.0: Garmin GPS usb/tty converter detected
[ 279.135620] usb 3-1: Garmin GPS usb/tty converter now attached to ttyUSB0
[ 296.854693] pps_core: LinuxPPS API ver. 1 registered
[ 296.854697] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <[email protected]>
[ 296.861036] pps_ldisc: PPS line discipline registered
[ 296.861400] pps pps0: new PPS source usbserial0
[ 296.861413] pps pps0: source "/dev/ttyUSB0" added
robert@robert-HP-Pavilion-g4-Notebook-PC:~$

I went in to reconfigure and put in the gps location and left the -N and this came back to me. "robert@robert-HP-Pavilion-g4-Notebook-PC:~$ sudo dpkg-reconfigure gpsd
[sudo] password for robert:
gpsd:SHOUT: vendor/product match with 091e:0003 found
gpsd:ERROR: PPS ioctl(TIOCMIWAIT) failed: 25 Inappropriate ioctl for device"
I like the shout! but am thinking I need to remove the -N? dont know the error message means.