Kismet + Gpsdrive problem

Flashtek-uk · 08-18-2006

Hi everyone..

Please forgive me if this is not the right place to ask but I have a problem with using the two listed above together.

I understand that GPSDrive is supposed to draw on the map the locations of detected WiFi networks.. however this does not work for me (neither kismet or gpsdrive people seem to be able to help me)

I fire up Kismet.. wait a moment or two for it to detect a few networks.

I then fire up gpsdrive with SQL support enabled.

At the console I get;

~$ gpsdrive

SQL: connected to localhost as gast using geoinfo

kismet server found
select() call: Bad file descriptor
select() call: Bad file descriptor
select() call: Bad file descriptor
select() call: Bad file descriptor
select() call: Bad file descriptor

the last message repeats forever... and gpsdrive will not play ball.

If it helps at all I am running Ubuntu Edgy with;

gpsdrive (c) 2001-2004 Fritz Ganter <ganter@ganter.at>

Version 2.09
$Id: gpsdrive.c,v 1.525 2004/03/03 20:46:47 ganter Exp $

and

Kismet 2006.04.R1

If anyone can please give me some pointers I would be very grateful...

Thorn · 08-18-2006

Quote:

Originally Posted by Flashtek-uk

Hi everyone..

Please forgive me if this is not the right place to ask but I have a problem with using the two listed above together.

...

Moved to the Unix/Linux Forum.

The Newbie Lounge is "The place to come to ask your basic NetStumbler/WiFi questions before moving on to the rest of the forum." This problem is neither basic nor anything to do with NetStumbler. While people here may have some answers for you, your best bet would be to try the Kismet Forums.

nayr · 09-21-2006

I had same issue, not 100% sure what solved it but for ubuntu but try this:

if you have a symbilic link /usr/lib/libmysqlclient. so remove it
apt-get install libmysqlclient10

try it again, if it still dosent work then were only half way there..
remove mysql-server-5 and install mysql-server-4.1 and mysql-client-4.1 from universe

I read in the debian bug list that mysql-server v5 does not play well with gpsdrive.. so then I downgraded and it still didnt work, then I checked the README.sql one more time and noticed it wanted libmysqlclient10 and not libmysqlclient14 like I had installed.. Not sure what it was specifically but running mysql-server 4.1 & installing libmysqlclient10 fixed it for me.

08-18-2006	#1 (permalink)
Flashtek-uk Registered Member Join Date: Aug 2006 Location: Devon, UK Posts: 1	Kismet + Gpsdrive problem Hi everyone.. Please forgive me if this is not the right place to ask but I have a problem with using the two listed above together. I understand that GPSDrive is supposed to draw on the map the locations of detected WiFi networks.. however this does not work for me (neither kismet or gpsdrive people seem to be able to help me) I fire up Kismet.. wait a moment or two for it to detect a few networks. I then fire up gpsdrive with SQL support enabled. At the console I get; ~$ gpsdrive SQL: connected to localhost as gast using geoinfo kismet server found select() call: Bad file descriptor select() call: Bad file descriptor select() call: Bad file descriptor select() call: Bad file descriptor select() call: Bad file descriptor the last message repeats forever... and gpsdrive will not play ball. If it helps at all I am running Ubuntu Edgy with; gpsdrive (c) 2001-2004 Fritz Ganter <ganter@ganter.at> Version 2.09 $Id: gpsdrive.c,v 1.525 2004/03/03 20:46:47 ganter Exp $ and Kismet 2006.04.R1 If anyone can please give me some pointers I would be very grateful...

09-21-2006	#3 (permalink)
nayr Registered Member Join Date: Sep 2006 Posts: 1	I had same issue, not 100% sure what solved it but for ubuntu but try this: if you have a symbilic link /usr/lib/libmysqlclient. so remove it apt-get install libmysqlclient10 try it again, if it still dosent work then were only half way there.. remove mysql-server-5 and install mysql-server-4.1 and mysql-client-4.1 from universe I read in the debian bug list that mysql-server v5 does not play well with gpsdrive.. so then I downgraded and it still didnt work, then I checked the README.sql one more time and noticed it wanted libmysqlclient10 and not libmysqlclient14 like I had installed.. Not sure what it was specifically but running mysql-server 4.1 & installing libmysqlclient10 fixed it for me. Last edited by nayr : 09-21-2006 at 01:56 AM.

Thread Tools
Show Printable Version Email this Page
Display Modes
Linear Mode Switch to Hybrid Mode Switch to Threaded Mode