Thanx but i figured it out no issues wid it now. there is one error that i get when my bluetooth starts. One of the services(i forgot the name will post as soon as i enter linux) is not starting and i am also having problems in connecting to devices using passkey(for file transfer service)bcos of which file transfer service is not working whereas the object push is working fine(as it does not ask for passkey) i am using kdbluetooth.

Any idea vat the error might b?

Thanx in advance.

kdebluetooth does not support my device so I am not sure what the problem is with it (never used it). However, the guide worked for me when I set up p3nfs which is like a command line version of kdebluetooth. This leads me to belive the problem is with kdebluetooth. Run it from the command line and reposrt any errors you are getting, maybe I can help, maybe not.

regards,
...drkstr

the service which is nt starting is kbemusedsrv. I think it is causin problems in file transfer service. The other thing is the change u made in the passkey in the config file. the system is nt chkin the pass key even if i giv the rt 1 the service does nt start.

Juss chk it out if it can be sorted otherwise i hav no issues wid usin object push service which works fine as well.

Thanx

Cheers!!!

When I wrote the guide, I was able to get kdebluetooth (an all of it's base applications) to start with no problems. I have not tested any actual transfers so I can't help you there, but it sounds like your problem is starting before the file transfers, correct?

Please list the exact error you start the service. You might want to also open the actual startup script and see where it's failing. Try running the the command manually and see is the error message is any different. You can also give strace a try. 'strace -o debugfile.out command will dump some debugging info to debugfile.out.

Let me know if you still need some additional help (but I will need a little bit more info since I can't check it on my computer)

regards,
...drkstr

omg, the insanity...

Make sure you have bt stuff compiled into kernel.

Install dbus which to work *correctly* requires a rebuild of udev or use the
one in current. Compile and install openobex, bluez-libs, bluez-utils, and kdebluetooth.
create an rc.bluetooth script to start services at boot.

Voila, you are good to go.

I do have some packs other than the dbus pack here
but they are built on a dlg system and I "cannot guarantee" that they will work on a stock
slackware system seeming as some of pats stuff is borked as usual.

BT works just fine on my system with the stock udev for 10.2

Other that, you just restated everything it says in my guide but without explaining how to do it. Thanks?

By borked, do you mean built for a stable server server environment instead of a shaky cutting edge "play toy" with all the newest technology? If so, maybe Slackware isn't the best distro for you. You might want to give Gentoo a try. Pat gives us the tools to screw up our own systems, but he won't do it for us.

...drkstr

If you have dealt with this udev/dbus/hal stuff as long as I have you can tell exactly
what I am talking about just reading through the build scripts. Things being purposely
left out that should be there. Take some time and read through them. I do have to say
kudos to piter punk for whipping udev into shape though... gratz to him. Looks like finally
the dlg guys won't have to rebuild this pack to work properly.

And the reason for my bt post is because there is like 1000 lines in the tutorial and it is
really not as difficult as it is shown. Very basic actually. I have bt working in gnome and
kde and it took nothing near what is posted here to get it up and running.

You're probably right. I don't really use for anything other then my bluetooth dongle. It works for me so I didn't explore the issue any further.

It admit is quite lengthy, but then again, it wasn't really written for people at your skill level. If you were bothered by the length, all you had to do was read the table of contents and the first section called "kernel support".

PS:
Everett, WA. huh? I see a lot of washingtonians on LQ. The NW must be down with Linux. Woot woot!

Yeah, I'm originally from here but moved to VA 6 years ago then moved back last year. Don't really
like it here during the 9mo of rain but VA bites 10 times worse with the military there. I don't
have anything against the military, but it seems to be the way of life there, atleast on the coast
where I was at and really wasn't for me.

I reread how I posted my first comment and probably should have done it a little different so as to not
sound like I was dogging the post. Just stating that it's quite easy to do but then again I spent quite alot
of time in the beginning figuring it out myself. The slight slam on dlg is what set me off seeming as though
most that dog it have never tried it and are going by heresay from pat's lemmings as I call them. My philosophy
is, if one is running a server that needs that type of security, they shouldn't be running a desktop on their system
anyhow. Just a note to everyone who doubts, and I'm not directing this at you, I have ran dlg for a few years now
and have not once ran into any instabilities nor have I ran into any problems with security. The whole pam issue that
seems so taboo in the slack world is in my mind completely bogus considering that there has been maybe one
security advisory that I've seen in the last few years compared to how many on X? But yet pat continues to include
that. Makes no sense to me but then again everyone has their own ideas of how things should be and regardless of
what faults I may see with slackware, the advantages out weigh them, which is why I will continue to use it over any
other distro.

Anyhow.. Howdy Neighbor

I was about to ask WTH you were talking about, but now I see what you're saying. I didn't even notice you mentioned dlg until I went back and read it just now. My apologies, I wasn't slamming dlg at all, I thought you were saying Slackware in general was "borked" (which might of made me just a tiny bit onery). Now I see it was just a misunderstanding. You're 100% right, Slackware is kind of lacking when it comes to Gnome. It would be nice to have the choice like you did back in the day.

Sorry man, wasn't trying to dog on your WM. They're all the same to me. I just use KDE because it was there, I'm no big fan or anything. Say something bad about Slackware though, then it's on! JK

...drkstr

Thanks for the howto.

Might be useful to note a problem I encountered in setting up a headset [ Slackware 10.1; kernel 2.6.16.16; bluez-utils-3.5; bluez-lib-3.5].

I could not get the headset to work since the passkey (added to /etc/bluetooth/hcid.conf) did not appear to be sent when
the headset requested it during pairing.

To get it to work, I did the following:

-Change the security manager mode in /etc/bluetooth/hcid.conf (instead of auto type 'user' ):

security user

- Put headset in pairing mode

- Run the passkey-agent binary, which I found under the <bluez-utils install dir>, with the passkey (it will just sit there until you start btsco -see below):

$ <bluez-utils installdir>/hcid/passkey-agent --default 0000

- In another window, start btsco so that the headset will request the key:

$ btsco <headset-address>

At this point the passkey-agent should send the key. Test that it is working using for example:

$ aplay -D plughw:1 -t au <soundfile>.au

It seems that the auto mode for the security manager in /etc/bluetooth/hcid.conf is not working as it should - the hcid daemon does not appear to get or send the password when requested.

thanks for the tip liutabme!

Unfortunatly, I can't edit the guide posted on LQ (only a moderator can). If it's okay with you though, I would like to add to the official guide on my website if it's okay with you. Let me know if it's not, otherwise, I'm going to add it.

Thanks!
...aaron

Yes that's fine. Thanks again for your howto.

I had bluetooth going on my laptop under Slack 10.2/kernel 2.6.13 for ages. No problem. Usual cheapo USB bluetooth dongle, did much data transfer and occasional GPRS modem action with my Nokia phone. Then upon redoing the system to Slack 11.1/kernel 2.6.19 I get no joy. Basically hcid refuses to run, with errors about not finding some dbus-related socket file.

hcid[6195]: Can't open system message bus connection: Failed to connect to socket /usr/var/run/dbus/system_bus_socket: No such file or directory

The dongle itself -is- detected: hciconfig shows all the details correctly.

I've tried several methods of installing the relevant packages, from source, from other peoples' prebuilt slack-packages, (and of course the well-documented method from drkstr (thanks!).)

This dbus thing is driving me mad . Any hints greatly appreciated.

Dr Glomph
Hamburg, Germany and Seattle WA USA

Hello, and welcome to LQ!

I have been able to use bluetooth after my upgrade to Slackware 11.0. If I were to take a stab at it, I would try looking into the kernel to see if there are any incompatibilities/misconfigurations with such a new kernel. If you still can't get it working, try posting the relevant portions of your kernel .config as well as the version numbers (CVS dates?) to the source you were compiling. I'm assuming there were no build errors or warnings?

Best regards,
...aaron