bluetooth usb adapter

_gnomm · 05-29-2006, 07:44 AM

slackware 10.2 and current

after installing bluez and kde-bluetooth...

when i'm plugging in my usb bluetooth adapter i'm receiving a massage can not connect to sdp server??

what should i do?? how to run this server or what should i install??

Help me please!!!!!!!!!!!!!

_gnomm · 05-30-2006, 01:45 AM

very strange thing...

its an official slackware forum and nobody have ever had such a problem???

any ideas??????

i made the full installation of slack 10.2 and current!!!

how did you get your bluetooth up?????

kite · 05-30-2006, 02:34 AM

Is there a rc.bluetooth or something in /etc/rc.d/ which you should start first?

_gnomm · 05-31-2006, 05:40 AM

ok if nobody can help i think that is the time to give up...

Alien Bob · 05-31-2006, 05:46 AM

Well unless you specify exactly which programs you installed and where you got them, and what you tried to run and what the exact error messages were, I cannot help you and by the looks of this thread, the same goes for the other forum members. I don't use bluetooth but some Googling reveals that the bluez sdp program might actually be in a separate package. Since you did not offer more detail, I cannot determine if you need to install more software.

Eric

_gnomm · 05-31-2006, 06:53 AM

ok...

first of all i installed slackware 10.2 full

this packages where downloaded from www.linuxpackages.net
then
kdebluetooth
bluez-libs
bluez-utils

that is all!!

in other distros such as mandriva2006 this is enough and it works!

so i'm pluggining my device and in systray i see message that usb bluetooth device is plugged in, but after 2 seconds i receive another message:

failed to connect to sdp server!!

when i'm pulling off my device in systray i receive a message that the usb bluetooth device was unplugged!!

also on www.linuxpackages.net i downloaded bluez-sdp but its for slackware 9.1 any way i installed it too, and i've got no success!!

the same i tried with slackware-current

so here is my problem!!!

synapse · 06-02-2006, 01:54 AM

Hi try
/sbin/sdp start

then insert usb bluetooth adaptor

Will check on this tonight and see if i cannot lend a hand here

cheers

_gnomm · 06-02-2006, 02:20 AM

Hi!!!

here it is:

gnom@gnom:~$ /sbin/sdp start
-bash: /sbin/sdp: No such file or directory

drkstr · 06-02-2006, 08:01 PM

I just got a bluetooth dongle and had to do a little fenagling to it to work on my Slack-box ( bluez is built for debian based systems). First, remove the bluez packages you just intalled. You will need to download the latest version of dbus prior to installing bluez. then you need to get the latest bluez code from cvs and check out all the modules (I don't think util2/lib2 are needed). Once you have the current source you need to compile/install libs. Then compile utils like so:

Code:

./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var --enable-all
make
make install DESDIR=<temporary build directory>

when it is finished compiling, cd to your temporary build directory and rename 'etc/init.d' to 'etc/rc.d' and then rename 'etc/rc.d/bluetooh' to 'etc/rc.d/rc.bluetooth'. When this is done, open up the rc.bluetooth file and change NAME to rc.bluetooth then tawrds the bottom where it says N= change the path to '/etc/rc.d'

When this is done, build it into a package by following the instructions on linuxpackages.net

When everything is installed, run the service with 'sh /etc/rc.d/rc.bluetooth start'

Let me know if you need any other help.

regards,
...drkstr

_gnomm · 06-03-2006, 11:09 AM

i installed dbus-0.61

while installing bluez-libs i got errors:

Quote:

gnom@gnom:~/Desktop/bluetooth/bluez-libs-2.25$ ./configure
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking whether build environment is sane... yes
checking for gawk... gawk
checking whether make sets $(MAKE)... yes
checking whether to enable maintainer-specific portions of Makefiles... no
checking for gcc... gcc
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc accepts -g... yes
checking for gcc option to accept ANSI C... none needed
checking for style of include used by make... GNU
checking dependency style of gcc... gcc3
checking for a BSD-compatible install... /usr/bin/ginstall -c
checking build system type... i686-pc-linux-gnu
checking host system type... i686-pc-linux-gnu
checking for a sed that does not truncate output... /usr/bin/sed
checking for egrep... grep -E
checking for ld used by gcc... /usr/i486-slackware-linux/bin/ld
checking if the linker (/usr/i486-slackware-linux/bin/ld) is GNU ld... yes
checking for /usr/i486-slackware-linux/bin/ld option to reload object files... -r
checking for BSD-compatible nm... /usr/bin/nm -B
checking whether ln -s works... yes
checking how to recognise dependent libraries... pass_all
checking how to run the C preprocessor... gcc -E
checking for ANSI C header files... yes
checking for sys/types.h... yes
checking for sys/stat.h... yes
checking for stdlib.h... yes
checking for string.h... yes
checking for memory.h... yes
checking for strings.h... yes
checking for inttypes.h... yes
checking for stdint.h... yes
checking for unistd.h... yes
checking dlfcn.h usability... yes
checking dlfcn.h presence... yes
checking for dlfcn.h... yes
checking the maximum length of command line arguments... 32768
checking command to parse /usr/bin/nm -B output from gcc object... ok
checking for objdir... .libs
checking for ar... ar
checking for ranlib... ranlib
checking for strip... strip
checking if gcc supports -fno-rtti -fno-exceptions... no
checking for gcc option to produce PIC... -fPIC
checking if gcc PIC flag -fPIC works... yes
checking if gcc static flag -static works... yes
checking if gcc supports -c -o file.o... yes
checking whether the gcc linker (/usr/i486-slackware-linux/bin/ld) supports shared libraries... yes
checking whether -lc should be explicitly linked in... no
checking dynamic linker characteristics... GNU/Linux ld.so
checking how to hardcode library paths into programs... immediate
checking whether stripping libraries is possible... yes
checking if libtool supports shared libraries... yes
checking whether to build shared libraries... yes
checking whether to build static libraries... yes
configure: creating libtool
configure: creating ./config.status
config.status: creating Makefile
config.status: creating include/Makefile
config.status: creating src/Makefile
config.status: creating bluez.pc
config.status: creating config.h
config.status: config.h is unchanged
config.status: executing depfiles commands
gnom@gnom:~/Desktop/bluetooth/bluez-libs-2.25$ make
make all-recursive
make[1]: Entering directory `/home/gnom/Desktop/bluetooth/bluez-libs-2.25'
Making all in include
make[2]: Entering directory `/home/gnom/Desktop/bluetooth/bluez-libs-2.25/include'
make[2]: Leaving directory `/home/gnom/Desktop/bluetooth/bluez-libs-2.25/include'
Making all in src
make[2]: Entering directory `/home/gnom/Desktop/bluetooth/bluez-libs-2.25/src'
if /bin/sh ../libtool --mode=compile gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -Wall -O2 -D_FORTIFY_SOURCE=2 -MT bluetooth.lo -MD -MP -MF ".deps/bluetooth.Tpo" \
-c -o bluetooth.lo `test -f 'bluetooth.c' || echo './'`bluetooth.c; \
then mv -f ".deps/bluetooth.Tpo" ".deps/bluetooth.Plo"; \
else rm -f ".deps/bluetooth.Tpo"; exit 1; \
fi
gcc -DHAVE_CONFIG_H -I. -I. -I.. -I../include -Wall -O2 -D_FORTIFY_SOURCE=2 -MT bluetooth.lo -MD -MP -MF .deps/bluetooth.Tpo -c bluetooth.c -fPIC -DPIC -o .libs/bluetooth.o
bluetooth.c:38:33: bluetooth/bluetooth.h: No such file or directory
bluetooth.c:39:27: bluetooth/hci.h: No such file or directory
bluetooth.c:41: error: syntax error before '*' token
bluetooth.c: In function `baswap':
bluetooth.c:43: error: `dst' undeclared (first use in this function)
bluetooth.c:43: error: (Each undeclared identifier is reported only once
bluetooth.c:43: error: for each function it appears in.)
bluetooth.c:44: error: `src' undeclared (first use in this function)
bluetooth.c: At top level:
bluetooth.c:50: warning: type defaults to `int' in declaration of `bdaddr_t'
bluetooth.c:50: error: syntax error before '*' token
bluetooth.c: In function `batostr':
bluetooth.c:52: warning: implicit declaration of function `bt_malloc'
bluetooth.c:52: warning: initialization makes pointer from integer without a cast
bluetooth.c:57: error: `ba' undeclared (first use in this function)
bluetooth.c: At top level:
bluetooth.c:62: error: syntax error before '*' token
bluetooth.c:63: warning: return type defaults to `int'
bluetooth.c: In function `strtoba':
bluetooth.c:67: error: `uint8_t' undeclared (first use in this function)
bluetooth.c:67: error: `ba' undeclared (first use in this function)
bluetooth.c:67: error: `bdaddr_t' undeclared (first use in this function)
bluetooth.c:72: error: syntax error before "strtol"
bluetooth.c:77: error: syntax error before ')' token
bluetooth.c: At top level:
bluetooth.c:80: warning: type defaults to `int' in declaration of `bdaddr_t'
bluetooth.c:80: error: syntax error before '*' token
bluetooth.c: In function `ba2str':
bluetooth.c:82: error: `uint8_t' undeclared (first use in this function)
bluetooth.c:82: error: syntax error before "b"
bluetooth.c:84: error: `bdaddr_t' undeclared (first use in this function)
bluetooth.c:84: error: syntax error before ')' token
bluetooth.c:85: error: `str' undeclared (first use in this function)
bluetooth.c:86: error: `b' undeclared (first use in this function)
bluetooth.c: At top level:
bluetooth.c:89: error: syntax error before "bdaddr_t"
bluetooth.c: In function `str2ba':
bluetooth.c:91: error: `uint8_t' undeclared (first use in this function)
bluetooth.c:91: error: syntax error before "b"
bluetooth.c:92: error: `str' undeclared (first use in this function)
bluetooth.c:96: error: `b' undeclared (first use in this function)
bluetooth.c:96: error: syntax error before "strtol"
bluetooth.c:101: error: `ba' undeclared (first use in this function)
bluetooth.c:101: error: `bdaddr_t' undeclared (first use in this function)
bluetooth.c:101: error: syntax error before ')' token
bluetooth.c: At top level:
bluetooth.c:105: warning: type defaults to `int' in declaration of `bdaddr_t'
bluetooth.c:105: error: syntax error before '*' token
bluetooth.c: In function `ba2oui':
bluetooth.c:107: error: `uint8_t' undeclared (first use in this function)
bluetooth.c:107: error: syntax error before "b"
bluetooth.c:109: error: `bdaddr_t' undeclared (first use in this function)
bluetooth.c:109: error: syntax error before ')' token
bluetooth.c:110: error: `str' undeclared (first use in this function)
bluetooth.c:110: error: `b' undeclared (first use in this function)
bluetooth.c: At top level:
bluetooth.c:162: error: conflicting types for 'bt_malloc'
bluetooth.c:52: error: previous implicit declaration of 'bt_malloc' was here
bluetooth.c:172: error: syntax error before "code"
bluetooth.c: In function `bt_error':
bluetooth.c:174: error: `code' undeclared (first use in this function)
bluetooth.c:177: error: `HCI_UNKNOWN_COMMAND' undeclared (first use in this function)
bluetooth.c:179: error: `HCI_NO_CONNECTION' undeclared (first use in this function)
bluetooth.c:181: error: `HCI_HARDWARE_FAILURE' undeclared (first use in this function)
bluetooth.c:183: error: `HCI_PAGE_TIMEOUT' undeclared (first use in this function)
bluetooth.c:185: error: `HCI_AUTHENTICATION_FAILURE' undeclared (first use in this function)
bluetooth.c:187: error: `HCI_PIN_OR_KEY_MISSING' undeclared (first use in this function)
bluetooth.c:189: error: `HCI_MEMORY_FULL' undeclared (first use in this function)
bluetooth.c:191: error: `HCI_CONNECTION_TIMEOUT' undeclared (first use in this function)
bluetooth.c:193: error: `HCI_MAX_NUMBER_OF_CONNECTIONS' undeclared (first use in this function)
bluetooth.c:194: error: `HCI_MAX_NUMBER_OF_SCO_CONNECTIONS' undeclared (first use in this function)
bluetooth.c:196: error: `HCI_ACL_CONNECTION_EXISTS' undeclared (first use in this function)
bluetooth.c:198: error: `HCI_COMMAND_DISALLOWED' undeclared (first use in this function)
bluetooth.c:199: error: `HCI_TRANSACTION_COLLISION' undeclared (first use in this function)
bluetooth.c:200: error: `HCI_ROLE_SWITCH_PENDING' undeclared (first use in this function)
bluetooth.c:202: error: `HCI_REJECTED_LIMITED_RESOURCES' undeclared (first use in this function)
bluetooth.c:203: error: `HCI_REJECTED_PERSONAL' undeclared (first use in this function)
bluetooth.c:204: error: `HCI_QOS_REJECTED' undeclared (first use in this function)
bluetooth.c:206: error: `HCI_HOST_TIMEOUT' undeclared (first use in this function)
bluetooth.c:208: error: `HCI_UNSUPPORTED_FEATURE' undeclared (first use in this function)
bluetooth.c:209: error: `HCI_QOS_NOT_SUPPORTED' undeclared (first use in this function)
bluetooth.c:210: error: `HCI_PAIRING_NOT_SUPPORTED' undeclared (first use in this function)
bluetooth.c:211: error: `HCI_CLASSIFICATION_NOT_SUPPORTED' undeclared (first use in this function)
bluetooth.c:212: error: `HCI_UNSUPPORTED_LMP_PARAMETER_VALUE' undeclared (first use in this function)
bluetooth.c:213: error: `HCI_PARAMETER_OUT_OF_RANGE' undeclared (first use in this function)
bluetooth.c:214: error: `HCI_QOS_UNACCEPTABLE_PARAMETER' undeclared (first use in this function)
bluetooth.c:216: error: `HCI_INVALID_PARAMETERS' undeclared (first use in this function)
bluetooth.c:217: error: `HCI_SLOT_VIOLATION' undeclared (first use in this function)
bluetooth.c:219: error: `HCI_OE_USER_ENDED_CONNECTION' undeclared (first use in this function)
bluetooth.c:220: error: `HCI_OE_LOW_RESOURCES' undeclared (first use in this function)
bluetooth.c:221: error: `HCI_OE_POWER_OFF' undeclared (first use in this function)
bluetooth.c:223: error: `HCI_CONNECTION_TERMINATED' undeclared (first use in this function)
bluetooth.c:225: error: `HCI_REPEATED_ATTEMPTS' undeclared (first use in this function)
bluetooth.c:227: error: `HCI_REJECTED_SECURITY' undeclared (first use in this function)
bluetooth.c:228: error: `HCI_PAIRING_NOT_ALLOWED' undeclared (first use in this function)
bluetooth.c:229: error: `HCI_INSUFFICIENT_SECURITY' undeclared (first use in this function)
bluetooth.c:231: error: `HCI_UNSUPPORTED_REMOTE_FEATURE' undeclared (first use in this function)
bluetooth.c:233: error: `HCI_SCO_OFFSET_REJECTED' undeclared (first use in this function)
bluetooth.c:235: error: `HCI_UNKNOWN_LMP_PDU' undeclared (first use in this function)
bluetooth.c:236: error: `HCI_INVALID_LMP_PARAMETERS' undeclared (first use in this function)
bluetooth.c:237: error: `HCI_LMP_ERROR_TRANSACTION_COLLISION' undeclared (first use in this function)
bluetooth.c:238: error: `HCI_LMP_PDU_NOT_ALLOWED' undeclared (first use in this function)
bluetooth.c:239: error: `HCI_ENCRYPTION_MODE_NOT_ACCEPTED' undeclared (first use in this function)
make[2]: *** [bluetooth.lo] Error 1
make[2]: Leaving directory `/home/gnom/Desktop/bluetooth/bluez-libs-2.25/src'
make[1]: *** [all-recursive] Error 1
make[1]: Leaving directory `/home/gnom/Desktop/bluetooth/bluez-libs-2.25'
make: *** [all] Error 2
gnom@gnom:~/Desktop/bluetooth/bluez-libs-2.25$

drkstr · 06-03-2006, 02:14 PM

Quote:

bluetooth.c:38:33: bluetooth/bluetooth.h: No such file or directory
bluetooth.c:39:27: bluetooth/hci.h: No such file or directory

erm... did you check out all the modules from the CVS? It doesn't appear that you are compiling the CVS version, it looks like you are compiling bluez-2.25. If you did get from the CVS, what does your utils directory look like? You should have these files in '<CVS DIR>/utils/include/'. Is this not the case?

regards,
...drkstr

**edit**
quick guide to CVS...

cvs -d

server:anonymous@cvs.bluez.org:/cvsroot/bluez login
<enter at password prompt>

cvs -d

server:anonymous@cvs.bluez.org:/cvsroot/bluez co -P modulename

Get all the modules listed here

you will then need to cd to '<CVS DIR>/libs' and run './bootstrap' to make the config file. Same goes for utils directory.
**edit**

**edit again**
those arn't smilies .it's a ': pserver' with no space.

_gnomm · 06-03-2006, 04:01 PM

ok thank you for help, it's a little complicated for me, but i'll try to manage!!

drkstr · 06-03-2006, 06:07 PM

It's not as bad as it looks. Just give it a try and let me know if I can answer anything for you.

regards,
...drkstr

drkstr · 06-03-2006, 07:08 PM

Hey it's me again, sorry.

I mentioned earlier that I wasn't sure if you needed to libs2/utils2 modules from the CVS but it turns out you do. You need to build/install these first since they have some functionality that was not copied over to libs/utils, which is just an upgrade from the ilbs2/utils2. I didn't notice this at first since since I was not neading the stuff from those modules at the time.

regards,
...drkstr

drkstr · 06-06-2006, 07:32 PM

errr... sorry, I withdraw my statement. libs2/utils2 are out dated and are not needed (and could in fact cause it to not work). Have you figured it out already or do you still need some assistance?

I have it working 100% now so feel free to ask if you need any help. Sorry for the confusion, I was in the process of getting it working myself when you posted your question. Since I couldn't find any documentation on it, I have just been kind of experimenting. I think I have all the kinks worked out now.

regards,
...drkstr