Vjylku

Buying a "Used" Router

If angels and devils are the same species, why would their mortal offspring appear physically different?

Minimum Viable Product for RTS game?

Sensor logger for Raspberry Pi in a stratospheric probe

Maybe pigeonhole problem?

Are all power cords made equal?

Coworker asking me to not bring cakes due to self control issue. What should I do?

How bad is a Computer Science course that doesn't teach Design Patterns?

Create an animation that plots the following two functions

How can I prevent an oracle who can see into the past from knowing everything that has happened?

smartctl reports overall health test as passed but the tests failed?

Why does a single AND gate need 60 transistors?

How to tell if effect is algebraic?

Did ancient Germans take pride in leaving the land untouched?

Why write a book when there's a movie in my head?

Count repetitions of an array

How long has this character been impersonating a Starfleet Officer?

Do we still track damage on indestructible creatures?

What could cause an entire planet of humans to become aphasic?

Dealing with an internal ScriptKiddie

Is there a way to pause a running process on Linux systems and resume later?

Is the percentage symbol a constant?

Equivalent of "illegal" for violating civil law

What would be some possible ways of escaping higher gravity planets?

How can I automatically launch GPSD on startup?

How do I allow non-root access to /ttyUSB0 on 12.04?How can I delay a specific program on startup?How can I stop workspaces from switching automatically to other workspaces when selecting different applications?How can I launch Ubuntu Variants and Betas on GCE?How can I check for updates automatically but not on startup?Discord Won't Launch 16.04How to startup a script automatically after loginhow can I recover /etc/security/limits.conf?SSH Private Key doesn't automatically load on startupHow can I launch any application using terminal?How to run a shell script automatically after startup and wake-up from hibernate?

4

I am trying to figure out, what is preventing gpsd from automatically connecting to an external GPS BU 353 dongle via USB and receiving data. I have the same issue on both of my laptops (with different hardware), so this is purely a software configuration issue.

I have managed to get gpsd working manually, using the following steps, but every time my machine is powered off, I must go through these steps again.

1. sudo killall gpsd



2. 
   

   Remove any sockets gpsd might have left behind with :

   
   
   

   sudo rm /var/run/gpsd.sock

   
   


3. 
   

   Check the device path:

   
   
   

   dmesg - which shows PLU353 
   
   

   
   


4. 
   

   Ensure no other programs are using the device. There are none listed

   
   
   

   lsof -n | grep /dev/ttyUSB0
   
   

   
   


5. 
   

   Manually launch gpsd:

   
   
   

   sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock
   
   

   
   



6. xgps sees the GPS output - so this works

My best guesses are that gpsd needs to join a group or be given additional permissions, or alternatively, that it is an issue with udev configuration. But I am blundering about in the dark, just making wild guesses.

16.04 configuration

share|improve this question

edited 30 mins ago

Tim

19.9k1486141

asked 5 hours ago

Geoffrey-cGeoffrey-c

211

New contributor

Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Rather than lsof -n | grep /dev/ttyUSB0, I'd use sudo lsof /dev/ttyUSB0 - no need to grep
  
  – waltinator
  5 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Possible duplicate of How do I allow non-root access to /ttyUSB0 on 12.04?
  
  – N0rbert
  5 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This has 2 answers from high-reputation (~20k) users, and it still hasn't been edited! Guys - tidy it up when you answer, it's a key part of keeping this site high-quality! @waltinator, remember to try to fix everything in the question when you edit it!
  
  – Tim
  34 mins ago
  
  
  

  
  
  
  

add a comment | 

4

I am trying to figure out, what is preventing gpsd from automatically connecting to an external GPS BU 353 dongle via USB and receiving data. I have the same issue on both of my laptops (with different hardware), so this is purely a software configuration issue.

I have managed to get gpsd working manually, using the following steps, but every time my machine is powered off, I must go through these steps again.

1. sudo killall gpsd



2. 
   

   Remove any sockets gpsd might have left behind with :

   
   
   

   sudo rm /var/run/gpsd.sock

   
   


3. 
   

   Check the device path:

   
   
   

   dmesg - which shows PLU353 
   
   

   
   


4. 
   

   Ensure no other programs are using the device. There are none listed

   
   
   

   lsof -n | grep /dev/ttyUSB0
   
   

   
   


5. 
   

   Manually launch gpsd:

   
   
   

   sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock
   
   

   
   



6. xgps sees the GPS output - so this works

My best guesses are that gpsd needs to join a group or be given additional permissions, or alternatively, that it is an issue with udev configuration. But I am blundering about in the dark, just making wild guesses.

16.04 configuration

share|improve this question

edited 30 mins ago

Tim

19.9k1486141

asked 5 hours ago

Geoffrey-cGeoffrey-c

211

New contributor

Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Rather than lsof -n | grep /dev/ttyUSB0, I'd use sudo lsof /dev/ttyUSB0 - no need to grep
  
  – waltinator
  5 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Possible duplicate of How do I allow non-root access to /ttyUSB0 on 12.04?
  
  – N0rbert
  5 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  This has 2 answers from high-reputation (~20k) users, and it still hasn't been edited! Guys - tidy it up when you answer, it's a key part of keeping this site high-quality! @waltinator, remember to try to fix everything in the question when you edit it!
  
  – Tim
  34 mins ago
  
  
  

  
  
  
  

add a comment | 

I am trying to figure out, what is preventing gpsd from automatically connecting to an external GPS BU 353 dongle via USB and receiving data. I have the same issue on both of my laptops (with different hardware), so this is purely a software configuration issue.

I have managed to get gpsd working manually, using the following steps, but every time my machine is powered off, I must go through these steps again.

1. sudo killall gpsd



2. 
   

   Remove any sockets gpsd might have left behind with :

   
   
   

   sudo rm /var/run/gpsd.sock

   
   


3. 
   

   Check the device path:

   
   
   

   dmesg - which shows PLU353 
   
   

   
   


4. 
   

   Ensure no other programs are using the device. There are none listed

   
   
   

   lsof -n | grep /dev/ttyUSB0
   
   

   
   


5. 
   

   Manually launch gpsd:

   
   
   

   sudo gpsd /dev/ttyUSB0 -F /var/run/gpsd.sock
   
   

   
   



6. xgps sees the GPS output - so this works

My best guesses are that gpsd needs to join a group or be given additional permissions, or alternatively, that it is an issue with udev configuration. But I am blundering about in the dark, just making wild guesses.

16.04 configuration

share|improve this question

edited 30 mins ago

Tim

19.9k1486141

asked 5 hours ago

Geoffrey-cGeoffrey-c

211

New contributor

Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited 30 mins ago

Tim

19.9k1486141

asked 5 hours ago

Geoffrey-cGeoffrey-c

211

New contributor

Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

share|improve this question

edited 30 mins ago

Tim

19.9k1486141

asked 5 hours ago

Geoffrey-cGeoffrey-c

211

New contributor

Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

edited 30 mins ago

Tim

19.9k1486141

edited 30 mins ago

Tim

19.9k1486141

asked 5 hours ago

Geoffrey-cGeoffrey-c

211

New contributor

Geoffrey-c is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.

asked 5 hours ago

Geoffrey-cGeoffrey-c

211

2 Answers
2

active

oldest

votes

7

You're correct - it is a group membership problem. First, see who owns the device:

ls -l /dev/ttyUSB0

On MY system, I don't have /dev/ttyUSB0, so I'll use /dev/ttyS0 instead

walt@bat:~(0)$ ls -l /dev/ttyS0

crw-rw---- 1 root dialout 4, 64 Feb 23 08:19 /dev/ttyS0

walt@bat:~(0)$ 

The output of the ls command shows that it's owned by root:dialout, and allows group access to the device.

Add your user to the dialout (or whatever is right for your system) group with:

sudo adduser $USER dialout

Then to make this group membership take effect, logout/login, OR newgrp dialout to start a shell with that group membership.

Check your group membership with /usr/bin/id.

share|improve this answer

answered 5 hours ago

waltinatorwaltinator

22.5k74169

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hi Waltinator, I have run and get the same output ls -l /dev/ttyUSB0 giviing crw-rw---- 1 root dialout 188, 0 Feb 24 19:10 /dev/ttyUSB0
  
  – Geoffrey-c
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Additionally, I am in the dialout group as I just posted and I also tried adding gpsd into the dialout group as well and rebooting, but no joy
  
  – Geoffrey-c
  2 hours ago
  

  
  
  
  

add a comment | 

2

• open TCP port 2947 in your firewall (if you wish other network clients access)


• make sure your username is in group dialout


• in terminal, edit /etc/default/gpsd
  
  
  
  
  • 
    sudo -H gedit /etc/default/gpsd # edit the gpsd settings file
  
  
  • change DEVICES="" to DEVICES="/dev/ttyUSB0" # /dev name may be different
  
  
  • save and quit gedit
  
  
  • 
    sudo systemctl restart gpsd # restart gpsd
  
  
  
  

gpsmon, cgps, and xgps will now work properly.

share|improve this answer

edited 3 hours ago

answered 5 hours ago

heynnemaheynnema

19.6k22158

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Wrong device name, and from what can be seen in first post, he doesn't have to open any ports for it to work; only re-start gpsd as root.
  
  – vidarlo
  4 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @vidarlo fixed. Thanks! The open port IS required if you want any of the gps software to find the daemon output.
  
  – heynnema
  4 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @vidarlo please consider reversing your down vote. Thanks!
  
  – heynnema
  4 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  No, not unless you have modified /etc/ufw/before.rules, which by default allows all on lo interface. In addition, it should be noted that gpsd may use a socket as well, which does not touch the network stack at all. As I stated; in the question it works after restarting gpsd, without any modification to the firewall rules.
  
  – vidarlo
  4 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @vidarlo ok... educate me... where is there any documentation about modifying /etc/ufw/before.rules, and what would you modify there? Also, re: tcp port... "Client applications will communicate with gpsd via a TCP/IP port, 2947 by default)".
  
  – heynnema
  3 hours ago
  

  
  
  
  

 | 
show 15 more comments

Your Answer

StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "89"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);

StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});

function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});


}
});

Geoffrey-c is a new contributor. Be nice, and check out our Code of Conduct.

draft saved

draft discarded

Sign up or log in

StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});

Sign up using Google

Sign up using Facebook

Sign up using Email and Password

Post as a guest

Name

Email

Required, but never shown

StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2faskubuntu.com%2fquestions%2f1120881%2fhow-can-i-automatically-launch-gpsd-on-startup%23new-answer', 'question_page');
}
);

Post as a guest

Name

Email

Required, but never shown

7

You're correct - it is a group membership problem. First, see who owns the device:

ls -l /dev/ttyUSB0

On MY system, I don't have /dev/ttyUSB0, so I'll use /dev/ttyS0 instead

walt@bat:~(0)$ ls -l /dev/ttyS0

crw-rw---- 1 root dialout 4, 64 Feb 23 08:19 /dev/ttyS0

walt@bat:~(0)$ 

The output of the ls command shows that it's owned by root:dialout, and allows group access to the device.

Add your user to the dialout (or whatever is right for your system) group with:

sudo adduser $USER dialout

Then to make this group membership take effect, logout/login, OR newgrp dialout to start a shell with that group membership.

Check your group membership with /usr/bin/id.

share|improve this answer

answered 5 hours ago

waltinatorwaltinator

22.5k74169

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hi Waltinator, I have run and get the same output ls -l /dev/ttyUSB0 giviing crw-rw---- 1 root dialout 188, 0 Feb 24 19:10 /dev/ttyUSB0
  
  – Geoffrey-c
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Additionally, I am in the dialout group as I just posted and I also tried adding gpsd into the dialout group as well and rebooting, but no joy
  
  – Geoffrey-c
  2 hours ago
  

  
  
  
  

add a comment | 

7

You're correct - it is a group membership problem. First, see who owns the device:

ls -l /dev/ttyUSB0

On MY system, I don't have /dev/ttyUSB0, so I'll use /dev/ttyS0 instead

walt@bat:~(0)$ ls -l /dev/ttyS0

crw-rw---- 1 root dialout 4, 64 Feb 23 08:19 /dev/ttyS0

walt@bat:~(0)$ 

The output of the ls command shows that it's owned by root:dialout, and allows group access to the device.

Add your user to the dialout (or whatever is right for your system) group with:

sudo adduser $USER dialout

Then to make this group membership take effect, logout/login, OR newgrp dialout to start a shell with that group membership.

Check your group membership with /usr/bin/id.

share|improve this answer

answered 5 hours ago

waltinatorwaltinator

22.5k74169

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Hi Waltinator, I have run and get the same output ls -l /dev/ttyUSB0 giviing crw-rw---- 1 root dialout 188, 0 Feb 24 19:10 /dev/ttyUSB0
  
  – Geoffrey-c
  2 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Additionally, I am in the dialout group as I just posted and I also tried adding gpsd into the dialout group as well and rebooting, but no joy
  
  – Geoffrey-c
  2 hours ago
  

  
  
  
  

add a comment | 

You're correct - it is a group membership problem. First, see who owns the device:

ls -l /dev/ttyUSB0

On MY system, I don't have /dev/ttyUSB0, so I'll use /dev/ttyS0 instead

walt@bat:~(0)$ ls -l /dev/ttyS0

crw-rw---- 1 root dialout 4, 64 Feb 23 08:19 /dev/ttyS0

walt@bat:~(0)$ 

The output of the ls command shows that it's owned by root:dialout, and allows group access to the device.

Add your user to the dialout (or whatever is right for your system) group with:

sudo adduser $USER dialout

Then to make this group membership take effect, logout/login, OR newgrp dialout to start a shell with that group membership.

Check your group membership with /usr/bin/id.

share|improve this answer

answered 5 hours ago

waltinatorwaltinator

22.5k74169

ls -l /dev/ttyUSB0

walt@bat:~(0)$ ls -l /dev/ttyS0

crw-rw---- 1 root dialout 4, 64 Feb 23 08:19 /dev/ttyS0

walt@bat:~(0)$ 

sudo adduser $USER dialout

share|improve this answer

answered 5 hours ago

waltinatorwaltinator

22.5k74169

answered 5 hours ago

waltinatorwaltinator

22.5k74169

answered 5 hours ago

waltinatorwaltinator

22.5k74169

2

• open TCP port 2947 in your firewall (if you wish other network clients access)


• make sure your username is in group dialout


• in terminal, edit /etc/default/gpsd
  
  
  
  
  • 
    sudo -H gedit /etc/default/gpsd # edit the gpsd settings file
  
  
  • change DEVICES="" to DEVICES="/dev/ttyUSB0" # /dev name may be different
  
  
  • save and quit gedit
  
  
  • 
    sudo systemctl restart gpsd # restart gpsd
  
  
  
  

gpsmon, cgps, and xgps will now work properly.

share|improve this answer

edited 3 hours ago

answered 5 hours ago

heynnemaheynnema

19.6k22158

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Wrong device name, and from what can be seen in first post, he doesn't have to open any ports for it to work; only re-start gpsd as root.
  
  – vidarlo
  4 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @vidarlo fixed. Thanks! The open port IS required if you want any of the gps software to find the daemon output.
  
  – heynnema
  4 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @vidarlo please consider reversing your down vote. Thanks!
  
  – heynnema
  4 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  No, not unless you have modified /etc/ufw/before.rules, which by default allows all on lo interface. In addition, it should be noted that gpsd may use a socket as well, which does not touch the network stack at all. As I stated; in the question it works after restarting gpsd, without any modification to the firewall rules.
  
  – vidarlo
  4 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @vidarlo ok... educate me... where is there any documentation about modifying /etc/ufw/before.rules, and what would you modify there? Also, re: tcp port... "Client applications will communicate with gpsd via a TCP/IP port, 2947 by default)".
  
  – heynnema
  3 hours ago
  

  
  
  
  

 | 
show 15 more comments

2

• open TCP port 2947 in your firewall (if you wish other network clients access)


• make sure your username is in group dialout


• in terminal, edit /etc/default/gpsd
  
  
  
  
  • 
    sudo -H gedit /etc/default/gpsd # edit the gpsd settings file
  
  
  • change DEVICES="" to DEVICES="/dev/ttyUSB0" # /dev name may be different
  
  
  • save and quit gedit
  
  
  • 
    sudo systemctl restart gpsd # restart gpsd
  
  
  
  

gpsmon, cgps, and xgps will now work properly.

share|improve this answer

edited 3 hours ago

answered 5 hours ago

heynnemaheynnema

19.6k22158

• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  Wrong device name, and from what can be seen in first post, he doesn't have to open any ports for it to work; only re-start gpsd as root.
  
  – vidarlo
  4 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @vidarlo fixed. Thanks! The open port IS required if you want any of the gps software to find the daemon output.
  
  – heynnema
  4 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @vidarlo please consider reversing your down vote. Thanks!
  
  – heynnema
  4 hours ago
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  No, not unless you have modified /etc/ufw/before.rules, which by default allows all on lo interface. In addition, it should be noted that gpsd may use a socket as well, which does not touch the network stack at all. As I stated; in the question it works after restarting gpsd, without any modification to the firewall rules.
  
  – vidarlo
  4 hours ago
  
  
  

  
  
  
  


• 
  
  
  

  
  

  
  
  
  
  
  

  
  
  @vidarlo ok... educate me... where is there any documentation about modifying /etc/ufw/before.rules, and what would you modify there? Also, re: tcp port... "Client applications will communicate with gpsd via a TCP/IP port, 2947 by default)".
  
  – heynnema
  3 hours ago
  

  
  
  
  

 | 
show 15 more comments

• open TCP port 2947 in your firewall (if you wish other network clients access)


• make sure your username is in group dialout


• in terminal, edit /etc/default/gpsd
  
  
  
  
  • 
    sudo -H gedit /etc/default/gpsd # edit the gpsd settings file
  
  
  • change DEVICES="" to DEVICES="/dev/ttyUSB0" # /dev name may be different
  
  
  • save and quit gedit
  
  
  • 
    sudo systemctl restart gpsd # restart gpsd
  
  
  
  

gpsmon, cgps, and xgps will now work properly.

share|improve this answer

edited 3 hours ago

answered 5 hours ago

heynnemaheynnema

19.6k22158

share|improve this answer

edited 3 hours ago

answered 5 hours ago

heynnemaheynnema

19.6k22158

answered 5 hours ago

heynnemaheynnema

19.6k22158

answered 5 hours ago

heynnemaheynnema

19.6k22158