gnokii-users
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Bluetooth and 6310i


From: Dimitris Stasinopoulos
Subject: Bluetooth and 6310i
Date: Thu, 3 Jul 2003 09:52:40 +0300
User-agent: KMail/1.5

Hi everyone, I've been trying to get Bluetooth working on my laptop for 
the last few days, and I had some problems, mainly because I used 2.4.18 
and I couldn't upgrade to 2.4.21 (due to ACPI issues). Until I discovered 
Marcel's patches for 2.4.18. I got a Gigabyte bluetooth USB dongle, which 
works fine on my desktop. I used the same on my notebook, and everything 
seemed to work fine: The adapter is recognised, I can scan for devices, 
etc. If I scan, my phone is detected ("Nokia 6310i"). If I try to connect 
to the phone using the rfcomm utility, the phone asks for my 
authorization ("Connect with LinuxNotebook?") & authentication ("Enter 
passcode"). After that, the phone says "Paired with LinuxNotebook", and 
is "stuck" on the "Connecting" screen. rfcomm says "Press CTRL-C for 
hangup", which means that it thinks the phone is connected. Of course, I 
can't actually use the link.

Now, if I bind the channel for use, the first time that I will try to 
connect to the phone using gnokii, I get a small timeout:

address@hidden:~ > gnokii --identify
GNOKII Version 0.5.2
Can't connect: Resource temporarily unavailable
Couldn't open PHONET device: Resource temporarily unavailable
Telephone interface init failed: Command failed.
Quitting.

After that, every attempt fails immediately:

address@hidden:~ > gnokii --identify
GNOKII Version 0.5.2
Can't connect: Device or resource busy
Couldn't open PHONET device: Device or resource busy
Telephone interface init failed: Command failed.
Quitting.

Any ideas here? Kernel 2.4.18 with bluetooth patch mh7 and gnokii 0.5.2.
Attached are my hcid and rfcomm config files.

Dimitris

-- 
Python? That is for children. A Klingon Warrior uses only machine code, 
keyed in on the front panel switches in raw binary. That is the savage 
way!

Attachment: hcid.conf
Description: Text Data

Attachment: rfcomm.conf
Description: Text document


reply via email to

[Prev in Thread] Current Thread [Next in Thread]