NetStumbler.org Forums - View Single Post

Mirlyn · 06-08-2003

Bad news. Last trip I took it pooped on me again. After 5 hours, the gpsd service seems to have crashed. A few things I've noticed so far:

1) GPSDrive works fantastic by itself, without kismet running. I left the laptop running in the car for two days straight without it crashing. I never started kismet, just let GPSdrive run (with my local maps and all). Kismet works fine for days too. When used together, the setup crashes it seems.

2) With Kismet running, after several hours (3+), gpsdrive will lock up and its' terminal window will repeat "loop detected, please report!" and the X-display will crash and go away (going back to the terminal window). About five minutes later (after the X-display crash), gpsd crashes and kismet loses coordinates. After the first crash of the X-display for the night, both gpsd and gpsdrive programs won't run but 10-15 minutes before they crash again. I tried the -i switch and it isn't having any effect now. When the GPS is set to Garmin mode, I can't start the gpsd daemon in gpsdrive so kismet won't ever get the coordinates.

3) The laptop has a few IRQ settings in the BIOS, I've tried two of the four listed, and it doesn't seem to affect it. I'm on my way out again tonight and I'll try the other two settings.

GPS is an eTrex Legend and the laptop is a Thinkpad 390X running RH8.0. I read a short piece in another recent thread here about problems with IBMs...will search for more about them when I get home--hope I'm not fighting an unknown problem.

I've tried redownloading/reinstalling kismet and gpsdrive--same problem. I'm using GPSDrive 1.32 and Kismet 2.8.1.

Any ideas would be appreciated. I hate looking down and realizing I've lost coordinates sometime during the drive and not knowing where/when.

06-08-2003	#11 (permalink)
Mirlyn social engineer Join Date: Aug 2002 Location: Wichita, Kansas Posts: 48	Bad news. Last trip I took it pooped on me again. After 5 hours, the gpsd service seems to have crashed. A few things I've noticed so far: 1) GPSDrive works fantastic by itself, without kismet running. I left the laptop running in the car for two days straight without it crashing. I never started kismet, just let GPSdrive run (with my local maps and all). Kismet works fine for days too. When used together, the setup crashes it seems. 2) With Kismet running, after several hours (3+), gpsdrive will lock up and its' terminal window will repeat "loop detected, please report!" and the X-display will crash and go away (going back to the terminal window). About five minutes later (after the X-display crash), gpsd crashes and kismet loses coordinates. After the first crash of the X-display for the night, both gpsd and gpsdrive programs won't run but 10-15 minutes before they crash again. I tried the -i switch and it isn't having any effect now. When the GPS is set to Garmin mode, I can't start the gpsd daemon in gpsdrive so kismet won't ever get the coordinates. 3) The laptop has a few IRQ settings in the BIOS, I've tried two of the four listed, and it doesn't seem to affect it. I'm on my way out again tonight and I'll try the other two settings. GPS is an eTrex Legend and the laptop is a Thinkpad 390X running RH8.0. I read a short piece in another recent thread here about problems with IBMs...will search for more about them when I get home--hope I'm not fighting an unknown problem. I've tried redownloading/reinstalling kismet and gpsdrive--same problem. I'm using GPSDrive 1.32 and Kismet 2.8.1. Any ideas would be appreciated. I hate looking down and realizing I've lost coordinates sometime during the drive and not knowing where/when.