Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Tue 21 Oct 2014, 08:49
All times are UTC - 4
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » System
Bluetooth & D-Bus, January 08
Post new topic   Reply to topic View previous topic :: View next topic
Page 6 of 7 [93 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7 Next
Author Message
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Mon 13 Apr 2009, 19:12    Post subject: Re: Not working for Puppy 2.14  

klasu777 wrote:
when i run "hcid -n", i get the following error message:
hcid: /lib/libc.so.6: version GLIBC_2.4 not found (required by hcid).

The bluetooth libraries and utilities in this thread are compatible only with Puppy 3.x and 4.x.
EDIT: For Puppy 2.x you must use the older bluetooth libraries contributed by forum member debernardis here -
http://www.debernardis.it/dotpups/experimental_BT_1.pup
D-Bus is not required with these older libraries.
I just added a note to the first post.

Last edited by tempestuous on Tue 14 Apr 2009, 04:14; edited 1 time in total
Back to top
View user's profile Send private message 
klasu777

Joined: 09 Apr 2009
Posts: 17

PostPosted: Tue 14 Apr 2009, 00:06    Post subject:  

Thanks for the pointer. I'm running problem after problem to get this running; i guess it's my inexperience with Puppy.

Given that the box on which i'm planning to run the result of this is very RAM-limited, i went on to run the same version of Puppy (i.e. 2.14 with no FPU) in virtuabox, running on a more powerful computer. I was hoping that giving it more resources there would make things easier.

Then i ran into gcc not being available in Puppy. After googling i found out that i need to install devx_214.sfs. That in itsself seems to be a non-trivial task. But i didn't even have the luxury of having this file completely downloaded. The reason: i couldn't mount the harddisk to allow Puppy to store the downloaded file. I will continue to report on my experience.

In the meantine, iw as wondering there is no pet or put package for this version of BlueZ.

Thanks,
Klaus.
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Tue 14 Apr 2009, 02:27    Post subject:  

klasu777 wrote:
In the meantine, iw as wondering there is no pet or put package for this version of BlueZ.

What about the "BlueZ" packages provided by daemon, which I just mentioned?
Back to top
View user's profile Send private message 
klasu777

Joined: 09 Apr 2009
Posts: 17

PostPosted: Tue 14 Apr 2009, 02:41    Post subject:  

I guess i'm missing something. I looked at those packages (http://www.murga-linux.com/puppy/viewtopic.php?mode=attach&id=2749 and http://www.murga-linux.com/puppy/viewtopic.php?mode=attach&id=2747) and they contain some few .h, .c, and make files.

Which to me means that they need to be built (configure, make, make install). Am i right?

Or if i'm missing something, i very much welcome your help.

Klaus.
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Tue 14 Apr 2009, 04:11    Post subject:  

Oops, sorry. I didn't realise that daemon packaged only the source code.
OK, those older BlueZ libraries/utilities were compiled by forum member debernardis, available here -
http://www.debernardis.it/dotpups/experimental_BT_1.pup
Back to top
View user's profile Send private message 
klasu777

Joined: 09 Apr 2009
Posts: 17

PostPosted: Tue 14 Apr 2009, 19:59    Post subject:  

Cool, thanks. I installed the package and i think i'm halfway through it. I now have the following files in my installation:

/lib/modules/2.6.18.1/kernel/net/bluetooth
/lib/modules/2.6.18.1/kernel/net/bluetooth/bluetooth.ko
/lib/modules/2.6.18.1/kernel/drivers/bluetooth
/sys/bus/bluetooth
/sys/class/bluetooth
/sys/module/bluetooth
/sys/bus/platform/devices/bluetooth
/sys/devices/platform/bluetooth

My question is now, how do i move from there? Is the driver loaded automatically with the OS?

I tried the following commands and they went just fine (that is, without any output or complain):

modprobe bluetooth
modprobe l2cap
modprobe rfcomm
modprobe hci-usb

Do i need them at all? In contrary, the following commands are not available:

hcid, sdpd, hciconfig, hcitool, etc.

Are they only for most recent version of BlueZ?

I tend to remember that the original link that you posted included a start script. Could you share it again?

Klaus.
Back to top
View user's profile Send private message 
klasu777

Joined: 09 Apr 2009
Posts: 17

PostPosted: Tue 14 Apr 2009, 20:45    Post subject:  

I found the starting script that was posted with BlueZ 2.10 source code. the content is this:

insmod /lib/modules/2.6.18.1/kernel/net/bluetooth/bluetooth.ko
insmod /lib/modules/2.6.18.1/kernel/net/bluetooth/l2cap.ko
insmod /lib/modules/2.6.18.1/kernel/net/bluetooth/rfcomm/rfcomm.ko
insmod /lib/modules/2.6.18.1/kernel/drivers/bluetooth/hci_usb.ko

/bt/hciconfig hci0 up
/bt/rfcomm bind 0 00:17:D5:A6:29:60 1
hcid
/bt/sdpd
ln -s /dev/rfcomm0 /dev/modem
/bt/sdptool add lan
/bt/sdptool add nap
/bt/sdptool add gn

The five first instructions are not needed because pupget does this when installing the package. All other commands fail because there is no hciconfig, rfcomm, hcid, spdtool tools.

Klaus.
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Tue 14 Apr 2009, 21:36    Post subject:  

klasu777 wrote:
I now have the following files in my installation:
...
/lib/modules/2.6.18.1/kernel/net/bluetooth/bluetooth.ko

No no. These are the bluetooth kernel modules, which you probably got from
http://www.murga-linux.com/puppy/viewtopic.php?p=85384#85384
or
http://www.debernardis.it/dotpups/bluetooth-modules-k2.6.18.1.pup
but they are only missing in Puppy v2.12 and 2.13.
Puppy 2.14 already contains the bluetooth kernel modules as standard.

klasu777 wrote:
the following commands are not available:
hcid, sdpd, hciconfig, hcitool, etc.

Then you're getting confused. These utilities are definitely contained in
http://www.debernardis.it/dotpups/experimental_BT_1.pup
Go back and install it again.

klasu777 wrote:
I found the starting script that was posted with BlueZ 2.10 source code

Well the best (Puppy-compatible) bluetooth setup commands are in the first post in this thread ...
... but ignore the first D-Bus related commands, because these older bluetooth libraries are not dependent on D-Bus.
Back to top
View user's profile Send private message 
klasu777

Joined: 09 Apr 2009
Posts: 17

PostPosted: Wed 15 Apr 2009, 00:38    Post subject:  

You are right. Somehow things got mixed up here. I now installed the experiemental_BT_1.pup. The strange thing is that all tools supposed to enable automatic pup package installation aren't working.

Anyway i extracted the file and ran the dotpup.sh script. All the commands that i claim to be missing are there.

Now, the following line that i'm supposed to run to get things started is making problems:

insmod /lib/modules/2.6.18.1/kernel/drivers/bluetooth/hci_usb.ko

The hci_usb.ko file cannot be found.

As a consequence the command "hciconfig hci0 up" doesn't work. i get the error message: "Can't get device info: No such device".

Beside that, all other commands work except the last one that return "Failed to open control socket: Protocl not supported".

And the light on my USB dongle is still off.
Any clue?

Thanks,
Klaus.
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Wed 15 Apr 2009, 01:19    Post subject:  

klasu777 wrote:
The strange thing is that all tools supposed to enable automatic pup package installation aren't working.

Dotpups and dotpets will fail to install properly if they are located in a directory path containing spaces. Spaces should not be used for Linux files and directories.

klasu777 wrote:
insmod /lib/modules/2.6.18.1/kernel/drivers/bluetooth/hci_usb.ko
The hci_usb.ko file cannot be found.

That's because with the Puppy 2.x series "non-standard" kernel modules were stored in a separate compressed file called "zdrv_..", and the insmod command does not have the logic to find them.

Where are you getting those instructions? Don't use them. Trust me - use the instructions in the first post in this thread. You will see that this is the command that should be used -
Code:
modprobe hci-usb
Back to top
View user's profile Send private message 
klasu777

Joined: 09 Apr 2009
Posts: 17

PostPosted: Wed 15 Apr 2009, 07:44    Post subject:  

Thank you. That was an amazing service. My dongle is now turned on. Two more questions:

1) May i send you some bounty?
2) The package does not contain OBEX. Any idea how to install that?

Klaus.
Back to top
View user's profile Send private message 
tempestuous

Joined: 10 Jun 2005
Posts: 5271
Location: Australia

PostPosted: Wed 15 Apr 2009, 10:59    Post subject:  

Older versions of OpenOBEX now here -
http://www.murga-linux.com/puppy/viewtopic.php?p=85384#85384
Back to top
View user's profile Send private message 
jakfish

Joined: 18 Jul 2008
Posts: 756

PostPosted: Fri 17 Apr 2009, 19:11    Post subject:
Subject description: Ericsson T39m Successful Bluetooth Connection with Puppy 4.1.2
 

Just a note to say that because of the work of so many and the great pets listed in this thread, it's possible to connect Puppy 4.1.2 to a Ericsson T39m via bluetooth and surf/email. Here are the configured files:

/etc/bluetooth/hcid.conf

#
# HCI daemon configuration file.
#

# HCId options
options {
# Automatically initialize new devices
autoinit yes;

# Security Manager mode
# none - Security manager disabled
# auto - Use local PIN for incoming connections
# user - Always ask user for a PIN
#
security user;

# Pairing mode
# none - Pairing disabled
# multi - Allow pairing with already paired devices
# once - Pair once and deny successive attempts
pairing multi;

# Default PIN code for incoming connections
passkey "1234";
}

# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "BlueZ (%d)";

# Local device class
class 0x000100;

# Default packet type
#pkt_type DH1,DM1,HV1;

# Inquiry and Page scan
iscan enable; pscan enable;

# Default link mode
# none - no specific policy
# accept - always accept incoming connections
# master - become master on incoming connections,
# deny role switch on outgoing connections
lm accept,master;

# Default link policy
# none - no specific policy
# rswitch - allow role switch
# hold - allow hold mode
# sniff - allow sniff mode
# park - allow park mode
lp rswitch,hold,sniff,park;
}


/etc/bluetooth/rfcomm.conf

#
# RFCOMM configuration file.
#

rfcomm0 {
# # Automatically bind the device at startup
bind yes;
#
# # Bluetooth address of the device
device 00:80:37:01:86:E6;
#
# # RFCOMM channel for the connection
channel 1;
#
# # Description of the connection
comment "Example Bluetooth device";
}


/etc/wvdial.conf

[Dialer Defaults]
Modem = /dev/rfcomm0
Baud = 115200
Init1 = ATZ
Init2 = ATQ0 V1 E1 S0=0 &C1 &D2 +FCLASS=0
Carrier Check = no
Dial Command = ATDT
Phone = *99***1#
Username = web
Password = web
Stupid Mode = yes
Auto Reconnect = no


And here is the script I use to start things up:

rm -f /var/run/dbus/*
dbus-uuidgen --ensure
dbus-daemon --system
sleep 1
modprobe bluetooth
modprobe l2cap
modprobe rfcomm
modprobe hci-usb
sleep 2
hcid
sdpd
passkey-agent --default 1234 &
sleep 1
rfcomm bind /dev/rfcomm0 00:80:37:01:86:E6 1


Addendum 1: in the helpful experimental bluetooth wiki, it's suggested that you pair THROUGH THE PHONE, and that worked for me.

Addendum 2: obviously, dialed number/password/etc are country/user specific. But what is interesting with the Ericson T39m (and perhaps other phones), if you program the APN/DSN addresses into the phone, you do not need to include this info in your pupdial modem dialout or anywhere else in puppy. I found that by simply dialing the GPRS number, the T39m did the rest.

I realize this is an ancient phone (I need a phone with infrared to connect to my Psion), but perhaps this will help other users nonetheless, and my gratitude to the many who helped out with puppy bluetooth.

Jake
Back to top
View user's profile Send private message 
didik


Joined: 05 Jan 2009
Posts: 44
Location: Bandung, Indonesia

PostPosted: Mon 22 Jun 2009, 00:53    Post subject:  

klasu777 wrote:

Do i need them at all? In contrary, the following commands are not available:

hcid, sdpd, hciconfig, hcitool, etc.

Are they only for most recent version of BlueZ?

Klaus.


So, where are hcid, sdpd commands?
bluez-4.40 doesn't include those daemons.

-eko didik widianto
bandung@indonesia
Back to top
View user's profile Send private message Visit poster's website Yahoo Messenger 
Chewi


Joined: 17 Aug 2008
Posts: 31
Location: Perth, Scotland

PostPosted: Thu 25 Jun 2009, 06:28    Post subject:  

Stereo Bluetooth is another name for A2DP so yes. I think most Bluetooth capable phones have it so I wouldn't say it's anything special.
_________________
Running Puppy 4.00 on a Toshiba Libretto 70CT. That's a Pentium 120MMX, 32MB RAM machine the size of a VHS cassette! It works like a charm. I even have wireless (WPA) and Bluetooth. Very Happy
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 6 of 7 [93 Posts]   Goto page: Previous 1, 2, 3, 4, 5, 6, 7 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » Advanced Topics » Additional Software (PETs, n' stuff) » System
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1030s ][ Queries: 12 (0.0154s) ][ GZIP on ]