Bluetooth on Puppy
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
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?
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
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!
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!
- Attachments
-
- bt2.sh.gz
- My bluetooth startup script.
- (244 Bytes) Downloaded 2118 times
- debernardis
- Posts: 180
- Joined: Sat 12 Nov 2005, 08:01
- Contact:
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
Cheers!
D
- debernardis
- Posts: 180
- Joined: Sat 12 Nov 2005, 08:01
- Contact:
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
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
- debernardis
- Posts: 180
- Joined: Sat 12 Nov 2005, 08:01
- Contact:
I am going on learning.
And I learned that I have to create the /dev/rfcomm0 node,
and I should do it this way:
I'll do it
And I learned that I have to create the /dev/rfcomm0 node,
and I should do it this way:
Code: Select all
mknod -m 666 /dev/rfcomm0 c 216 0
Last edited by debernardis on Wed 03 Jan 2007, 05:23, edited 1 time in total.
- debernardis
- Posts: 180
- Joined: Sat 12 Nov 2005, 08:01
- Contact:
Whoa!
It did work, by following step by step this: http://www.artm-friends.at/rm/bluetooth ... -HOWTO.txt
and I'm presently posting through a gprs connection
Now I'll prepare a dotpup and a howto - somebody please get it and make a wizard... we'll have a BT puppy soon. Next step - obex!
and I'm presently posting through a gprs connection
Now I'll prepare a dotpup and a howto - somebody please get it and make a wizard... we'll have a BT puppy soon. Next step - obex!
Sorry, i have read a lot of FAQ's, HOWTO's, etc while getting this to work, and i have forgotten some steps i made...
Now i have 2 problems:
1. I cannot initiate LAN connection from my laptop. I only can run listening daemon on laptop(puppy) and then connect from pc(Windows Vista). Have anyone any idea?
2. My GPRS Provider is a bit buggi, when i connect in windows i have to wait about 1 minute while windows says "Loging in to network...". In linux it causes BIG problems. When i try to connect to GPRS pppd successfully creates ppp0, then waits a bit (20-30 seconds) and dies because of timeout. After 5-6 retries it finally connects. Where can i increse this timeout?
Now i have 2 problems:
1. I cannot initiate LAN connection from my laptop. I only can run listening daemon on laptop(puppy) and then connect from pc(Windows Vista). Have anyone any idea?
2. My GPRS Provider is a bit buggi, when i connect in windows i have to wait about 1 minute while windows says "Loging in to network...". In linux it causes BIG problems. When i try to connect to GPRS pppd successfully creates ppp0, then waits a bit (20-30 seconds) and dies because of timeout. After 5-6 retries it finally connects. Where can i increse this timeout?
- debernardis
- Posts: 180
- Joined: Sat 12 Nov 2005, 08:01
- Contact:
Daemon: sorry at the present time I am unable to help you! But eventually I'll learn.
For an experimental howto on gprs bluetooth connection go see http://puppylinux.org/wikka/ExperimentalBT and report your experiences and thoughts
For an experimental howto on gprs bluetooth connection go see http://puppylinux.org/wikka/ExperimentalBT and report your experiences and thoughts
I have solved my problem with gprs!
Now it connects 100%
I think speed does not matter, so may be returned to 115200, i made it 56700 just for safety.
Here are my pppd config files:
Peers:
Chatscript:
I was editing scripts, originally created by kppp (i edited only peer script).
Now it connects 100%
I think speed does not matter, so may be returned to 115200, i made it 56700 just for safety.
Here are my pppd config files:
Peers:
Code: Select all
noauth
connect "/usr/sbin/chat -v -f /etc/ppp/chatscripts/akos"
/dev/rfcomm0
#115200
57600
defaultroute
#noipdefault
user
usepeerdns
nodetach
debug
#xonxoff
crtscts
receive-all
novj
nodeflate
noccp
Code: Select all
ABORT ERROR
ABORT RING
ABORT BUSY
ABORT "NO CARRIER"
ABORT VOICE
ABORT "NO DIALTONE"
ABORT "NO ANSWER"
REPORT CONNECT
"" "ATZ"
OK ATDT*99#
TIMEOUT 60
CONNECT \c
- debernardis
- Posts: 180
- Joined: Sat 12 Nov 2005, 08:01
- Contact:
Call for scripting
Friends,
is there anybody who's got time and will to convert my howto in
http://puppylinux.org/wikka/ExperimentalBT
to a script (shell or puppybasic or whatever) to automate connection?
At present I have no time and also I'm clueless at scripting but that could be useful for everybody.
is there anybody who's got time and will to convert my howto in
http://puppylinux.org/wikka/ExperimentalBT
to a script (shell or puppybasic or whatever) to automate connection?
At present I have no time and also I'm clueless at scripting but that could be useful for everybody.
Re: Call for scripting
BT would also be useful to me, but at present I'm busy with other projects and don't have the time to help youdebernardis wrote:Friends,
is there anybody who's got time and will to convert my howto in
http://puppylinux.org/wikka/ExperimentalBT
to a script (shell or puppybasic or whatever) to automate connection?
At present I have no time and also I'm clueless at scripting but that could be useful for everybody.
Perhaps later, if no one else volunteers.
Paul
Methinks Raspberry Pi were ideal for runnin' Puppy Linux
- debernardis
- Posts: 180
- Joined: Sat 12 Nov 2005, 08:01
- Contact:
I have put together kinda of a script to automate gprs connection.
In order to make it work you must have:
1) mac address and dun channel of your phone (to be hardcoded into the script);
2) gprs connection scripts for pppd for your telco.
Everything is described in the wiki page; the script is attached in this message.
Please testers let me know their results!
In next step I would like to automate phone selection. Then, going on, there is obex to be added, maybe from http://openobex.triq.net/ - and phone filesystem mounting (p3nfs ?).
Help is really welcome
EDIT 24-1-07 uploaded new version of the script, modified the wiki accordingly
In order to make it work you must have:
1) mac address and dun channel of your phone (to be hardcoded into the script);
2) gprs connection scripts for pppd for your telco.
Everything is described in the wiki page; the script is attached in this message.
Please testers let me know their results!
In next step I would like to automate phone selection. Then, going on, there is obex to be added, maybe from http://openobex.triq.net/ - and phone filesystem mounting (p3nfs ?).
Help is really welcome
EDIT 24-1-07 uploaded new version of the script, modified the wiki accordingly
- Attachments
-
- gprs-connect.gz
- (352 Bytes) Downloaded 1405 times
- Béèm
- Posts: 11763
- Joined: Wed 22 Nov 2006, 00:47
- Location: Brussels IBM Thinkpad R40, 256MB, 20GB, WiFi ipw2100. Frugal Lin'N'Win
daemon,
Your phone supports bluetooth and USB.
So you should be able to do things.
ObexFTP via bluetooth f.e.
Your phone supports bluetooth and USB.
So you should be able to do things.
ObexFTP via bluetooth f.e.
Time savers:
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
Find packages in a snap and install using Puppy Package Manager (Menu).
[url=http://puppylinux.org/wikka/HomePage]Consult Wikka[/url]
Use peppyy's [url=http://wellminded.com/puppy/pupsearch.html]puppysearch[/url]
p3nfs
Some addresses with some info about p3nfs below.- and phone filesystem mounting (p3nfs ?)
http://ocaoimh.ie/2003/05/10/linux-to-s ... fer-howto/
Note: from above webpage: Start Bluetooth services: /etc/init.d/bluetooth start
Puppy does not have this file on my machine. Or /etc/rc.d/init.d/bluetooth start
http://www.koeniglich.de/p3nfs.html - has .SIS files for phone.
-
- Posts: 452
- Joined: Thu 20 Mar 2008, 01:48
hi, I got myself "almost" connected with gprs, but my operator use username and password, how do I put username and password in the pppd script? I'm using puppy 3.01...
i browse around and find this...
# Username and password:
# If username and password are required by the APN, put here the username
# and put the username-password combination to the secrets file:
# /etc/ppp/pap-secrets for PAP and /etc/ppp/chap-secrets for CHAP
# authentication. See pppd man pages for details.
# Example, Radiolinja operator pap-secrets:
# "rlnet" * "internet" *
#user "rlnet"
#user "Orange"
from... http://www.bigsoft.co.uk/projects/bluetooth/
what is it mean ?
thank you
i browse around and find this...
# Username and password:
# If username and password are required by the APN, put here the username
# and put the username-password combination to the secrets file:
# /etc/ppp/pap-secrets for PAP and /etc/ppp/chap-secrets for CHAP
# authentication. See pppd man pages for details.
# Example, Radiolinja operator pap-secrets:
# "rlnet" * "internet" *
#user "rlnet"
#user "Orange"
from... http://www.bigsoft.co.uk/projects/bluetooth/
what is it mean ?
thank you
-
- Posts: 5464
- Joined: Fri 10 Jun 2005, 05:12
- Location: Australia
The correct way to specify username and password for ppp connections is to add this line to both /etc/ppp/pap-secrets and /etc/ppp/chap-secrets
Obviously, replace "MYUSERNAME" and "MYPASSWORD" with your true values, and don't forget the asterisk in the middle.
Another thing to try is wvdial, since the wvdial configuration file makes it obvious where to put the username and password. However, you would probably need to Google for all the other GPRS settings for wvdial. Do a Google search for "wvdial GPRS".
But I wouldn't assume that ppp chat scripts necessarily need to specify username/password. GPRS connections are not standard; different service providers use different login processes.
From the instructions provided by my Motorola K1 mobile phone, it appears that the phone holds data service settings, including username/passwords.
Forum members daemon and debernardis are the experts on this subject. They may have further information.
Code: Select all
MYUSERNAME * MYPASSWORD
Another thing to try is wvdial, since the wvdial configuration file makes it obvious where to put the username and password. However, you would probably need to Google for all the other GPRS settings for wvdial. Do a Google search for "wvdial GPRS".
But I wouldn't assume that ppp chat scripts necessarily need to specify username/password. GPRS connections are not standard; different service providers use different login processes.
From the instructions provided by my Motorola K1 mobile phone, it appears that the phone holds data service settings, including username/passwords.
Forum members daemon and debernardis are the experts on this subject. They may have further information.
-
- Posts: 452
- Joined: Thu 20 Mar 2008, 01:48
hi, thank you...
but
I have found one method which work for me, . I edit the file /etc/ppp/peers/gprs
I add these simple code :
user xxxx
password zzzz
(xxxx,zzzz are standart username and password from ISP)
it work without changing other thing, in fact I writing this on linux connection.
I thank you again...
but
I have found one method which work for me, . I edit the file /etc/ppp/peers/gprs
I add these simple code :
user xxxx
password zzzz
(xxxx,zzzz are standart username and password from ISP)
it work without changing other thing, in fact I writing this on linux connection.
I thank you again...