bluetooth usb adapter
 

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!!!!!!!!!!!!!

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?????

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

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

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

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!!!

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

Hi!!!

here it is:

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

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: 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

i installed dbus-0.61

while installing bluez-libs i got errors:

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:pserver:anonymous@cvs.bluez.org:/cvsroot/bluez login
<enter at password prompt>

cvs -d:pserver: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.

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

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

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

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

i didn't try it yet, a little busy, and have some probs with my ISP so internet at home is down,but on weekend i think everything will be ready and i'll try it out, i need it working!!!!!
i think i'll have some questions!!!

thanks a lot for you assistance!!!

Hi drkstr!

How about writing a quick HOWTO on what you found out here in this thread? You've made me mighty curious.

Eric

Getting bluez to work on Slackware
 

Good Idea, all the information is kind of fragmented and goes back and forth, so I will put it all together to sum it up.

moved guide to LQ tutorials section here

GOOD WORK drkstr!!!!!!!!!!!

i'll try it!! thanks a lot!!!!!

ok i did it!!!

everything was fine but...

root@gnom:~# /etc/rc.d/rc.bluetooth start
which: no hid2hci in (/sbin:/bin:/usr/sbin:/usr/bin)
Starting Bluetooth subsystem: hcid sdpdCan't open HIDP control socket: Protocol not supported
hiddCan't open RFCOMM control socket: Protocol not supported
rfcomm.
root@gnom:~#

you need to enable both of those in your kernel as modules.

regards,
...drkstr

**edit**
more specificly:

ok, it works!!!

i can see my phone and phone can see my system, but, kdebluetooth is not working!! and how to pair devices??and to send files to each other??

in other systems kdebluetooth makes it all, is it possible in slackware and how??

It depends on your phone. Not all manufacturers release the specs to their devices. For instance, I have a nokia 9300 which does not have native Linux support. Thankfully, Rudolph Koenig developed support for my device (and a few others) with p3nfs. Be warned though, this is pretty hard to set up and only works on the commands line. Search the web to see if there are any gui tools that support your device. A few that come to mind are 'plptools' and 'kandy' (which comes with KDE). If you are unsure, let me know what device you have and maybe I can find something for you.

regards,
...drkstr

**edit**
Are you saying you got kdebluetooth to work with your phone on other distros? If so, let me know and I'll see if I can figure out why it's not working in Slackware.

i have nokia 6680 and samsung e720 anyway...

as i told before in mandriva 2006 i installed:

kde-bluetooth
bluez-libs
bluez-utils

i plug in my device and it works, i pull it off and plugg again and it works!!! with out typing any commands!!!with default kernel!
that is all!!



i make the right click on file and send it to bluetooth device..
it gives me to choose from avaliable devices, what ever bluetooth device it be!!
almost the same way i send files back to computer!!

Sorry been awhile since I read the first post.

I have updated the guide I wrote to give directions for installing kdebluetooth but I ran into a snag with QT. It does not support dynamic instalation directories which prevents you from building it into a package. You can do a regular 'make install', or you can wait until later tonight when I come up with a work around and update the guide again.

I strongly recomend waiting since I havn't had time to test it yet.

regards,
...drkstr

ok, take your time!!!!!

thank you again for your help!!!

do you need this? or it's just an interest?

kdebluetooth does not support my phone, but I am always willing to spend the time proving that you can do anything on Slackware that you can do on other distros. ;)

FYI:
I am rebuilding QT right now on my home computer. I'll see how it turns out when I get home from work. Be fare warned though, it takes an ungodly amount of time to compile. The first time I went though it took about an hour on my PIV 2.8 Ghz!

I'll update the guide again once I get kdebluetooth running but I will need your help debugging since I have no way of testing if it works or not. Just make sure you run kdebluetooth from the command line so you can report any errors, if any.

regards,
...drkstr

As you will find out, every kernel is different. What one distro includes in its kernel build is not neccesarily in another distros kernel build.

This is a prime example of this. Bluetooth kernel options are not enabled in the standard kernel configs in Slackware, but obviously are in your previous distro. That is a prime reason why the very first thing I do after a fresh install is to recompile my kernel, enabling what I need, and disabling what I do not. Again, bluetooth support comes to mind. As does my specific video, chipset, ports, filesystems, network, wireless, sound, etc.

ok, i'm ready for help, and ready to compile with my 2000 Mhz laptop all night long!!!

just tell me the commands and a full guide, how and what to do, because i installed linux 6 months before and it takes time to understand how it works and why... but i want to know!!!and i'll try to understand!!!!


i've already understood this, and i don't know how many times i've already compiled it, and it's a little copmlicated to make some things in my laptop working such as hibirnate or standby, and fan,wifi and so on, but i'm trying and some day i'll do it with your help i hope!!!!

OK, well as it turns out, building kdebluetooth is a little bit more work then I had thought since it uses newer parts of KDE that were not implemented in Slackware-10.2. I was just about to rebuild my entire KDE from the ground up when I realized it would probably be easier to just upgrade KDE from slackware-current. I am still working out a few kinks in building kdebluetooth but if you want to get started upgrading KDE I'll give you some basic instructions in the mean time.

note: I have been able to upgrade to the current KDE and it seems to be running OK, but I can't grantee it's stability. Upgrading to the current KDE requires you to upgrade some key system dependencies with it. You might want to make sure you have backed up any important data before doing this.

added these instructions to the guide here

More to come!
...drkstr

so i have to download and upgrade these packages and after that download CVS of kde-bluetooth and to install it! right??

and i don't have to make changes in dbus, bluez-libs and bluez-utils that i built and installed,leave it as it is, and not to reinstall them??

Ok, I have it running now. Give it a try and let me know if it works for your phone, and any error messages you might get. Please be thorough and specific. Also, make sure you reread the entire portion of the guide that relates to kdebluetooth (it's changed a bit).

regards,
...drkstr

ok, i didn't see the link to guide...

i'll need some time to give it a try, so when i'll get enough free time i'll try it...

i wonder, if there was no such HOWTo (i was looking for it for a long time) till now, does it mean that no one didn't try to do it in slackware?because as i can see it's a little complicated for some one new to linux to understand which libraries and packages to install???

That's a very good question, and unfortunately, I don't really know the answer. I had a hard time finding information myself and had to just figure a lot of it out on my own. The good news is, now there is one such HOWTO. I'm sure it needs to be polished a little bit, so let me know how it works out.

regards,
...drkstr

I have made a small change in the guide. Please see the updated section in modifiying the bluez-util build. You will need to modify your /etc/bluetooth/hcid.conf a little to work better with kdebluetooth.

regards,
...drkstr

ok, there is one more day till weekend and i'll try it...

Please direct any more discussion on this topic here

This will prevent information form being fragmented and make it easier to find.

thanks!
...drkstr