This looks pretty much right.
Could you run
/usr/sbin/gpsd -D 2 -N -F /var/run/gpsd.sock -P /var/run/gpsd.pid
on the console and see if gpsd starts properly - it should stay in the the
foreground and produce a lot of debug output.
If that works well - could the problem reside in usplash? Seems you're using
that, and I remember that it had a similar bug in Debian. Not exactly sure any
more, though.
Walter_Wittel wrote:
+
printf
> + start-stop-daemon --start --quiet --exec /usr/sbin/gpsd -- -F /var/run/gpsd.sock -P /var/run/gpsd.pid
This looks pretty much right.
Could you run
/usr/sbin/gpsd -D 2 -N -F /var/run/gpsd.sock -P /var/run/gpsd.pid
on the console and see if gpsd starts properly - it should stay in the the
foreground and produce a lot of debug output.
If that works well - could the problem reside in usplash? Seems you're using
that, and I remember that it had a similar bug in Debian. Not exactly sure any
more, though.
-- bzed.de http:// www.debian. org
ECA1 E3F2 8E11 2432 D485 DD95 EB36 171A 6FF9 435F
Bernd Zeimetz Debian GNU/Linux Developer
http://
GPG Fingerprints: 06C8 C9A2 EAAD E37E 5B2C BE93 067A AD04 C93B FF79