| View previous topic :: View next topic |
| Author |
Message |
daviessm
n00b
Joined: 20 May 2005
Posts: 36
|
 Posted: Sat Aug 16, 2008 8:55 pm Post subject: bluetooth daemons exiting when connection attempted [solved] |
 |
|
Hi,
I'm having a problem with bluetooth using the latest stable bluez-libs and bluez-utils: the services (hcid, sdpd, rfcomm) start with no visible problems. I can scan for devices with hcitool and the computer is visible when I scan from my phone. However, when I try to pair the two devices in any way, the bluetooth services seem to stop. sdpd writes a 'terminating...' line to syslog and the phone reports an error.
The odd thing is, the exact same configuration (I copied the /etc/bluetooth/* files across) works perfectly on my other laptop.
Can anyone help me find where the problem is? Let me know if you need any configuration files or anything to help me diagnose this!
Thanks
Last edited by daviessm on Wed Aug 20, 2008 6:27 pm; edited 1 time in total |
|
| Back to top |
|
 |
daviessm
n00b
Joined: 20 May 2005
Posts: 36
|
| Posted: Sun Aug 17, 2008 9:27 am Post subject: |
|
|
I've got my phone with me now so here's a bit more information..
With the bluetooth service started (/etc/init.d/bluetooth start) if I try to connect ppp1 which is a GPRS connection over my phone with the following configuration: | Code: | config_ppp1=( "ppp" )
link_ppp1="/dev/rfcomm0"
phone_number_ppp1=( "*99***1#" )
username_ppp1='web'
password_ppp1='web'
pppd_ppp1=(
"maxfail 10"
"noauth"
"lcp-echo-interval 5"
"lcp-echo-failure 12"
"debug"
"noipdefault"
"defaultroute"
"usepeerdns"
"ipcp-accept-remote"
"ipcp-accept-local"
"holdoff 3"
"noaccomp noccp nobsdcomp nodeflate nopcomp novj novjccomp"
"115200"
"lock"
"nocrtscts"
)
chat_ppp1=(
'ABORT' 'BUSY'
'ABORT' 'ERROR'
'ABORT' 'NO ANSWER'
'ABORT' 'NO CARRIER'
'ABORT' 'NO DIALTONE'
'ABORT' 'Invalid Login'
'ABORT' 'Login incorrect'
'TIMEOUT' '5'
'' 'ATZ'
'OK' 'ATM0'
'OK' 'ATDT\T'
'TIMEOUT' '60'
'CONNECT' ''
'TIMEOUT' '5'
'~--' ''
) |
I get the following messages in syslog: | Code: | Aug 17 10:05:29 eee pppd[9258]: Plugin passwordfd.so loaded.
Aug 17 10:05:29 eee pppd[9259]: pppd 2.4.4 started by root, uid 0
Aug 17 10:05:29 eee rc-scripts: WARNING: net.ppp1 has started but is inactive
Aug 17 10:05:33 eee sdpd[8386]: terminating...
Aug 17 10:06:00 eee chat[9357]: Can't get terminal parameters: Input/output error
Aug 17 10:06:00 eee pppd[9259]: Connect script failed
Aug 17 10:06:01 eee pppd[9259]: Hangup (SIGHUP)
Aug 17 10:06:01 eee pppd[9259]: Failed to open /dev/rfcomm0: No such device |
Notice the sdpd[8386] terminating... line - this happens as soon as it tries to connect to the phone over bluetooth.
If I restart the bluetooth service and try to pair the two devices on the phone interface (Symbian S60v3) as soon as the 'enter PIN' dialogue pops up on the phone it beeps and says unable to connect, and I see the following in syslog: | Code: | Aug 17 10:21:45 eee hcid[30352]: Bluetooth HCI daemon
Aug 17 10:21:46 eee sdpd[30378]: Bluetooth SDP daemon
Aug 17 10:22:19 eee sdpd[30378]: terminating... |
..where the first two lines are where the service started and the third where it terminated unexpectedly.
The bluetooth device is a | Code: | | Bus 005 Device 002: ID 0b05:b700 ASUSTek Computer, Inc. |
on my EeePC 1000.
Has anyone seen this before and could shed some light on it?  Thanks |
|
| Back to top |
|
|
daviessm
n00b
Joined: 20 May 2005
Posts: 36
|
| Posted: Wed Aug 20, 2008 6:28 pm Post subject: |
|
|
| SOLVED: using the latest bluetooth kernel driver (btusb instead of hci_usb) and the latest unstable bluez-libs and bluez-utils versions worked. |
|
| Back to top |
|
|
|
Networking & Security
