kanotix.com
Hardware - Bluetooth only working one way...
shame - 27.10.2006, 16:26 Uhr
Titel: Bluetooth only working one way...
I'm fully dist-upgraded and I've been trying out bluetooth with mixed success.
I can send files to my phone via kbtobexclient no problem but when I start kbluetoothd and try to send anything to kanotix from my phone, the phone doesn't pick up kanotix at all, no devices found.
On my previous install of kanotix bluetooth worked fine with this particular phone and I don't remember having to configure anything in kanotix then, I'm sure it all just worked.
hifi25nl - 28.10.2006, 13:21 Uhr
Titel:
I had the same problems myself with Nokia E61. I have resolved uninstalling bluetooth with:
apt-get remove --purge kdebluetooth
apt-get remove --purge bluez-utils
After that you can reinstall bluez-utils and kdebluetooth. The problem is that maybe the first times all is working and the telephone can find the computer but after something is changed (what???) and is impossible to send a file from the mobile. However you can send from the computer with kbtobexclient or you can send-receive with obex://[<address of mobile>]:<channel>/
My hcid.conf is the default one and rfcomm.conf is
Zitat:
rfcomm0 {
bind yes;
device <device_address>;
channel 10;
comment "<your_comment>";
}
Piero
shame - 28.10.2006, 22:56 Uhr
Titel:
I tried removing and reinstalling bluez-utils and kdebluetooth and it's still not working and /etc/bluetooth is now completely empty.
shame - 29.10.2006, 02:47 Uhr
Titel:
How do I get the files back in /etc/bluetooth that were there when I first installed kanotix?
piper - 29.10.2006, 15:12 Uhr
Titel:
I am not positive on this (I do not have it installed nor do I use it) but I think it needs these (maybe more)
bluetooth
bluemon
bluez-hcidump
bluez-utils
kdebluetooth
libbluetooth2
You can probably install bluetooth by apt-get or synaptic and also remember to unfreeze it.
K-menu > Control Center > Kanotix > Boot (log in as Admin) > Freeze > Uncheck "Freeze Services" hit apply > Services > Under Disabled Services, click on "whatever", click on the < button to switch it to Active Service's, then go back to > Freeze > Check "Freeze Services" hit apply close
shame - 29.10.2006, 22:06 Uhr
Titel:
I have installed every bluetooth, bluez* and obex related package I can find and /etc/bluetooth is still empty.
Can anyone confirm bluetooth is working for them and maybe post their hcid.conf?
I've never needed to do anything with rfcomm.conf on any distro.
I'm wondering if their is a fault with one of the packages because I've occasionaly had trouble setting up bluetooth to send files to the computer but it is usually an auth issue but in this case the phone isn't even detecting the computer at all.
In the middle of typing this I had an idea to look through my backups and I copied over /etc/bluetooth from a previous version of kanotix which was working then but it still doesn't work with this installation.
I've also tried hcid.conf files from my suse and ubuntu installs, both of which have fully working bluetooth.
piper - 29.10.2006, 22:58 Uhr
Titel:
apt-get install kdebluetooth bluez-utils kbluetoothd kbtobexclient kbserialchat
works fine, if you don't unfreeze it, goodluck.
shame - 30.10.2006, 00:39 Uhr
Titel:
kbluetoothd, kbtobexclient and kbserialchat are all components of of kdebluetooth and can't be apt-got.
I really don't know what's up with it, I removed purged reinstalled dpkg-reconfigured several times.
When I start kbluetoothd there are no errors and it does see the bluetooth device it just deosn't seem to want to transmit. Also it is set to always visible
piper - 30.10.2006, 02:20 Uhr
Titel:
shame hat folgendes geschrieben::
kbluetoothd, kbtobexclient and kbserialchat are all components of of kdebluetooth and can't be apt-got.
Well, I just used h2's script to remove it period (bluetooth) lets try a different way out of many.
apt-get install bluez-utils libbluetooth1 libbluetooth1-dev bluez-pin
Then go HERE and get the deb, then dpkg -i kdebluetooth-<version>.deb
You might have to add to your source list (if you get a 404 error on the link HERE)
# kdebluetooth
deb http://fred.hexbox.de/debian ./
apt-get update, apt-get install kdebluetooth
Restart KDE
or
Download the following packages
bluez-hcidump (optional, shows USB device debug info)
bluez-pin (necessary)
bluez-utils (necessary)
libbluetooth1 (necessary, Debian installs it automatically)
libsdp2 (necessary, Debian installs it automatically)
obexftp (optional, sending/recpetion for old-skool handsets)
obexserver (necessary)
gnome-bluetooth (optional, sending/reception for Gnome2)
kdebluetooth (optional, sending/reception for KDE)
There are other ways, google is your friend
shame - 30.10.2006, 23:38 Uhr
Titel:
I got the 404 error with the link and file or directory not found with the repo.
I started from scratch, removed every bluetooth related package, copied over the /etc/bluetooth files from the livecd again and reinstalled the basic stuff again.
For some strange reason it is now working perfectly.
I've rebooted several times and it has continued to work without further problems.
shame - 03.11.2006, 22:43 Uhr
Titel:
And now it's suddenly stopped working again...
Holger-K - 04.11.2006, 20:12 Uhr
Titel:
Hello shame,
you have to install passkey-agent from deb-Packages. Only compile this little part
and copy it to /usr/local/bin or somewhere else that could be found in your PATH.
Next start passkey-agent in the background. Then make a connection to your phone with e.g. cat /dev/rfcomm0 to transfer and confirm the key.
Look at /var/lib/bluetooth/A:R:E:S:S/linkkeys where you will find the encrypted key.
article.gmane.org/gmane.linux.bluez.user/10761
Have fun .....
shame - 04.11.2006, 22:49 Uhr
Titel:
I tried that but it didn't work. I don't think the passkey thing is the problem.
It isn't getting that far because my phone simply isn't seeing the computer so it has nothing to send a passkey to.
Holger-K - 05.11.2006, 11:05 Uhr
Titel:
OK, let's make it step-by-step .....
What do you see here? -->
Code:
hcitool scan
Scanning ...
00:0X:X1:1X:1X:11 Nokia 6230
04:X8:88:X8:88:9X NokiaXY
... and then --->
Code:
rfcomm show 0
rfcomm0: 04:X8:88:X8:88:9X channel 1 clean
Now start
Code:
passkey-agent --default 1234 &
... and
Code:
cat < /dev/rfcomm0
On your phone you should see something like ... accept connection (OK), and
please insert pin (1234)
First part DONE!
^C to interrupt 'cat'
Open in KMenu the kbluetoothd --> configuration --> paired devices
There --> File location setup
Under Link key file there must be the correct location of the linkkeys.
Next click on the symbol, and you will see your phone-symbol.
Click at the symbol and at
OBEX File transfer
......
shame - 05.11.2006, 20:28 Uhr
Titel:
hcitool scan - shows my phone and address
rfcomm show 0 - Get info failed: No such device
After reinstalling suse, I've just gotten round to trying bluetooth on that, which worked perfectly.
I then booted back into kanotix and simply tried sending a file from my phone to the newly added (suse) device and I got the dialogue asking if I want to accept a file which I answered yes and it is now saved on kanotix.
It might not be the right way of doing things but at least it is working.
gmx99 - 04.03.2007, 21:26 Uhr
Titel:
Or you can try:
rfcomm must be ok and the file PIN has to contain 1234.
1. modprobe bluetooth rfcomm l2cap
2. hcitool scan
3. create a /bin/bluepin with:
#!/bin/bash
cat /etc/bluetooth/pin
4. rfcomm bind 0 00:00:00:00:00:00 with the number from 2.
5. echo "ATZ" > /dev/rfcomm0
6. now you have to insert the PIN for pairing
7. execute normaly modemlink and gprsconnect
Goes!
look at http://debian.blauzahn.net/ only german
gmx99
Alle Zeiten sind GMT + 1 Stunde
PNphpBB2 © 2003-2007