Page 1 of 2
Bluetooth on Puppy
Posted: Mon 03 Oct 2005, 22:31
by saintlangton
Simple question to say but probably hard to answer...
Would it be possible to get bluetooth working in Puppy?
What would it take? There are several bluetooth-interface programs for Linux. Would it just be a matter of compiling them and then it'd work? Or would it need kernel patches and/or other heavy-duty work?
For PCLinuxOS (My other linux OS of choice, for when I need something that puppy can't (yet) do. IMHO a very fine OS but
so slow and bloaty compared to Puppy) I just opened synaptic & applied everything that said it was anything to do with Bluetooth. Now I have all the functionality I need (and more probably)
It'd be nice if I could have this in Puppy, It's the only thing that I'm currently having to go outside Puppy for now Graveman has arrived for CD burning. (I never got on with Puppy's previous CD burner)
Cheers
Chris Langton
Posted: Tue 04 Oct 2005, 02:44
by tempestuous
You need -
1. the Bluetooth kernel modules. Puppy is missing these modules, but some of them are in Barry's separate module download at
ftp://ibiblio.org/pub/linux/distributio ... ete.tar.gz
2. the BlueZ utilities, from
http://www.bluez.org/download.html
Party on
Posted: Sun 06 Nov 2005, 02:23
by Guest
You need -
You know what they say, let the good time roll.
Posted: Tue 28 Mar 2006, 13:08
by klooooo
Hello,
I want to install this module (modules-2.4.29-complete.tar.gz) but I don't know how.
Someone can tell me how to do?
Thanks
can't install
Posted: Sat 08 Apr 2006, 18:02
by ApeMan
I also can't figure out how to install these .gz packages.
I tried uncompressing them. which worked, but I could not run the install files afterwards.
I also tried to use PupGet to install an alien package, but I get the PupGet package format error: "Packages are only allowed to install to top-level directories /usr /etc and /root. This package wants to install elsewhere, so aborting this script. This package is now deleted."
Any tips on how to get this working?
Thanks,
ApeMan
Posted: Fri 18 Aug 2006, 08:40
by debernardis
OK. I compiled and installed:
1. bluez-libs-3.2
2. dbus-0.91 (which was needed as a dependency for the following)
3. bluez-utils-3.2
but I could not find the bluetooth kernel modules - plus I'm on puppy 2.02 with kernel 2.6.16.7 so those from the thread are no good.
Do I need to recompile my kernel or is there a workaround?
Posted: Fri 18 Aug 2006, 09:21
by fluxit
Posted: Sun 20 Aug 2006, 12:01
by debernardis
I downloaded those modules. Tried to insmod, but:
Code: Select all
sh-3.1# pwd
/root/my-downloads/all-modules/kernel/drivers/bluetooth
sh-3.1# ls
bcm203x.ko bpa10x.ko dtl1_cs.ko hci_vhci.ko
bfusb.ko bt3c_cs.ko hci_uart.ko
bluecard_cs.ko btuart_cs.ko hci_usb.ko
sh-3.1# insmod hci_usb.ko
insmod: error inserting 'hci_usb.ko': -1 Unknown symbol in module
sh-3.1# dmesg | tail -n 4
hci_usb: Unknown symbol hci_free_dev
hci_usb: Unknown symbol hci_alloc_dev
hci_usb: Unknown symbol hci_unregister_dev
hci_usb: Unknown symbol hci_register_dev
sh-3.1#
What am I doing wrong?
Posted: Sun 20 Aug 2006, 18:38
by fluxit
hci_usb.ko is dependent on bluetooth.ko
insmod /root/my-downloads/all-modules/kernel/net/bluetooth/bluetooth.ko
Posted: Mon 21 Aug 2006, 11:20
by debernardis
Got it, thanks.
Now I am able to i
nsmod bluetooth.ko and
insmod hci_usb.ko
this way I can see my usb bluetooth adapter with
cat /proc/bus/usb/devices
then in order to make it work I had to do
(taken from
http://www.teaparty.net/technotes/blue-gprs.html )
This wakes up the interface so that I can have this:
Code: Select all
sh-3.1# /usr/local/sbin/hciconfig
hci0: Type: USB
BD Address: 00:E0:98:AE:2B:C9 ACL MTU: 192:8 SCO MTU: 64:8
UP RUNNING PSCAN ISCAN
RX bytes:71 acl:0 sco:0 events:8 errors:0
TX bytes:31 acl:0 sco:0 commands:8 errors:0
and this
Code: Select all
sh-3.1# hcitool scan
Scanning ...
00:0E:ED:AE:D7:3B EdB
Nice; so it sees my phone.
All right? Not so, indeed.
It seems that the daemons hcid and sdpd are not really up.
I did
Code: Select all
/usr/local/sbin/hcid
/usr/local/sbin/sdpd
/usr/local/bin/rfcomm
but:
Code: Select all
sh-3.1# ps -ae | grep hcid
15739 root 584 S grep hcid
sh-3.1# ps -ae | grep sdpd
16070 root 584 S grep sdpd
sh-3.1# ps -ae | grep rfcomm
16125 root 580 S grep rfcomm
sh-3.1#
so what we can see is the good ol' grep activity but no daemons.
In fact when I go looking for dialup-capable devices I get
Code: Select all
sh-3.1# sdptool search DUN
Inquiring ...
Failed to connect to SDP server on 00:0E:ED:AE:D7:3B: Protocol not supported
sh-3.1#
Any hint?
Posted: Tue 22 Aug 2006, 06:57
by debernardis
This thing is quickly becoming much too complex for me...
I tried to start hcid:
Code: Select all
sh-3.1# /usr/local/sbin/hcid -n -f /etc/bluetooth/hcid.conf
hcid[9565]: Bluetooth HCI daemon
hcid[9565]: Can't open system message bus connection: Failed to connect to socket /usr/local/var/run/dbus/system_bus_socket: No such file or directory
hcid[9565]: Unable to get on D-Bus
There is one directory /usr/local/var/run/dbus but it's empty.
I'll stick with my kubuntu and use puppy from time to time but without bluetooth
Posted: Tue 22 Aug 2006, 07:46
by fluxit
I don't have any bluetooth devices here or I would continue regardless.
If you need any more help, let me know.
Perhaps someone else has more experience with this subject...
--Lee
Posted: Tue 22 Aug 2006, 10:01
by debernardis
By now it seems I have the problem of making the dbus-daemon work.
If someone is interested to join my effort, I'll state more clearly my steps.
Posted: Tue 07 Nov 2006, 18:53
by Lobster
I am scared . . .
Someone gave me a USB Bluetooth dongle so I can transfer pics from my phone . . .
But the list of things that has to be done - too hard
Is anyone up to dotpupping this? I can test it and I am sure a few others will too. Isn't Bluetooth support one of the options that can be turned on when the kernel is compiled?
All help appreciated.
any progress?!!??....
Posted: Tue 05 Dec 2006, 01:19
by gop00
I was wondering if there was any progress on this issue? I copied /usr/local/var/run/dbus/system_bus_socket file in that directory but now it says "Failed to connect to socket /usr/local/var/run/dbus/system_bus_socket: Connection refused"
Doing some progress...wondering if other people were successful at resolving this issue.
Posted: Sat 23 Dec 2006, 08:04
by tempestuous
debernardis,
You have done some good troubleshooting. From a more recent forum thread, it appears that the problem may be due to Puppy not having ALL bluetooth modules (and maybe firmware, too).
I have just supplied the full set of modules/libs/utils/firmware here
http://www.murga-linux.com/puppy/viewto ... 5384#85384
Maybe you will have more success with these installed?
SOLVED
Posted: Sat 30 Dec 2006, 02:32
by daemon
I have solved that problem with Bluetooth!!
The hcid didn't start because it has some problems with dbus. (try hcid -n ).
While trying to fix this problem i have found out that old versions of bluetooth-utils didn't require dbus, it's optional there. So, I have found libs and utils version 2.10 (instead of 3.8.), compiled them, and it WORKS (I had previously uninstalled dbus, libs3.8 and utils3.8.). It has some problems with pin helper, but with fixed pin IT WORKS. Now i can connect to gprs, and use bluetooth LAN!.
I have used puppy 2.12 (upgraded from 2.02 especially for bluetooth, in 2.02 there is no rfcomm.ko module) and modules from previous post (i didn't use zdrv.sfs because of VERY expensive traffic)
Here is my bluetooth startup script and OLD versions of libs and utils (they are very hard to find)
p.s. Sorry for bad english!
Posted: Sat 30 Dec 2006, 06:46
by debernardis
I'll try ASAP
Posted: Sat 30 Dec 2006, 15:09
by DrDeaf
Hello all.... I am a noob.pup but the Bluetooth connectivity would be huge for me. I currently use a Bluetooth LG CU500 GPRS phone with a Nokia 770, but if the Bluetooth info could be put into a "HowTo" and a straightforward file download that I could follow I'd be a happy (desktop) camper.
Cheers!
D
Posted: Tue 02 Jan 2007, 07:05
by debernardis
Hello Daemon,
I suspect that on your machine there are remnants of previous trials to make BT work, because following your instructions I am stuck to the creation of /dev/rfcomm0.
Follow me please:
I have downloaded and installed the BT modules dotpup;
I have downloaded the old versions of bluez-libs and bluez-utils;
./configure - make - make install for both
I have opened your script and executed the single lines
All the 4 insmod are OK;
hciconfig hci 0 up gives no output as it should I guess; then i give
hciconfig and I see my interface;
I gave also the commented out hciconfig cc my-address
and a hciconfig auth my-address in order to pair - and pairing was OK
Then:
you give rfcomm bind 0 my-address my-channel (for my phone channel is 2)
I give the command, seems OK
in fact when I give rfcomm show I get rfcomm0: my-address channel 2 clean
Good? No
going on with hcid, sdpd
but when I look for /dev/rfcomm0, there is
no /dev/rfcomm0 so nothing to link to /dev/modem and going on no joy with the following instructions.
So my problem is to create rfcomm0
Look at
https://help.ubuntu.com/community/BluetoothDialup :
this says he creates rfcomm0 by issuing sudo /etc/init.d/bluez-utils restart (but we haven't that in our setting).
So what next? How did you get to have /dev/rfcomm0
Thanks