I am having the same trouble that everyone else has had...my bluetooth
DUN connection with my Treo 650 worked fine in Edgy, but now in Feisty
it no longer works. Any help anybody can give would be appreciated.
Otherwise I am relegated to (shudder) Vista, where the Bluetooth DUN
works without a hitch.
[EMAIL PROTECTED]:~$ hciconfig
hci0: Type: USB
BD Address: 00:02:72:05:D3:C3 ACL MTU: 1017:8 SCO MTU: 64:0
UP RUNNING PSCAN
RX bytes:5367 acl:61 sco:0 events:186 errors:0
TX bytes:2461 acl:71 sco:0 commands:88 errors:0
hcitool cc produces no output, but hcitool auth says "not connected".
Even with my DUN turned on on the treo:
[EMAIL PROTECTED]:~$ hcitool scan
Scanning ...
00:07:E0:20:78:75 jstroup
my /etc/bluetooth/hcid.conf:
[EMAIL PROTECTED]:~$ cat /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 auto;
#pin_helper /etc/bluetooth/feed-pin.sh;
# 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 "0000";
}
# Default settings for HCI devices
device {
# Local device name
# %d - device id
# %h - host name
name "%h (%d)";
# Local device class
#class 0x50020c
class 0x3e0100;
#class 0x100;
# Default packet type
#pkt_type DH1,DM1,HV1;
# Inquiry and Page scan
iscan enable; pscan enable;
discovto 0;
# 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;
auth enable;
encrypt enable;
}
my /etc/bluetooth/rfcomm.conf:
[EMAIL PROTECTED]:/etc/bluetooth$ cat rfcomm.conf
#
# RFCOMM configuration file.
#
rfcomm0 {
# # Automatically bind the device at startup
bind yes;
#
# # Bluetooth address of the device
device 00:07:e0:20:78:75;
# device 11:22:33:44:55:66;
#
# # RFCOMM channel for the connection
channel 1;
#
# # Description of the connection
comment "Treo650";
# comment "Example Bluetooth device";
}
--
Bluetooth no longer working after upgrade to Feisty
https://bugs.launchpad.net/bugs/110375
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
