0.7 3G: Nokia N95-3 (RM160) not detected (Bluetooth)

Bug #262574 reported by Craig Ringer
6
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

The Nokia N95-3 (RM160) doesn't seem to be detected by NetworkManager as an available bluetooth rfcomm gsm modem. The phone does appear as a paired device in the gnome bluetooth preferences and is set as trusted.

The phone is on, but does NOT have bluetooth discovery enabled. It should not have to have BT discovery turned on for NM to use it; I don't have to have it on to connect through bluetooth manually. However, for the sake of this testing I've turned visibility back on.

It works fine when I connect manually (visible or invisible). I use this setup script:

#!/bin/bash -x
BT=00:1D:E9:F5:55:AF
if test "$(id -u)" -ne 0 ; then
 exec sudo $0
fi
CHAN=$(sdptool search --bdaddr $BT DUN | awk '/Channel/ { print $2}')
rfcomm release 2
rfcomm bind 2 "$BT" "$CHAN"
rfcomm
pon telstrabt

(where "BT" is the Bluettooth MAC address of the device).

This script first finds the correct rfcomm channel for the DUN service, then sets an rfcomm binding up for it before invoking pppd to chat to the modem and negoitiate PPP. It's necessary to do the DUN probe each time because the rfcomm channel ID tends to change when the phone is rebooted.

I'll attach the peers file and chat script I use, too, along with lshal output and all the rest.

Revision history for this message
Craig Ringer (ringerc) wrote :
Revision history for this message
Craig Ringer (ringerc) wrote :
Revision history for this message
Craig Ringer (ringerc) wrote :
Revision history for this message
Craig Ringer (ringerc) wrote :

Note: I can also browse the phone with OBEX via the Gnome bluetooth applet, so it's otherwise behaving quite fine.

Revision history for this message
Craig Ringer (ringerc) wrote :
Revision history for this message
Craig Ringer (ringerc) wrote :
Revision history for this message
Craig Ringer (ringerc) wrote :
Revision history for this message
Alexander Sack (asac) wrote :

can you provide lshal when you just have the bluetooth pairing on (and no usb cable connected)?

Changed in network-manager:
status: New → Incomplete
Revision history for this message
Craig Ringer (ringerc) wrote :

I've attached lshal output with the default, unchanged hal-info package and no tweaks in /etc/hal/fdi . The phone was not connected over USB. A bluetooth pairing exists which is trusted on both ends. An OBEX connection from phone to host over BT was active at the time lshal was run. The phone was set to visible in its bluetooth control panel.

Package versions:

ii bluez-gnome 0.25-0ubuntu2 Bluetooth utilities for GNOME
ii bluez-utils 3.36-1ubuntu1 Bluetooth tools and daemons
ii gnome-bluetooth 0.11.0-0ubuntu2 GNOME Bluetooth tools.
ii hal-info 20080508+git20080601-1ubuntu2~nm1 Hardware Abstraction Layer - fdi files
ii network-manager 0.7~~svn20080818t061112+eni1-0ubu network management framework daemon
ii network-manager-gnome 0.7~~svn20080817t183748-0ubuntu1 network management framework (GNOME frontend)

(hal-info and NM are from the NM PPI)

The phone properly exposes a DUN interface over SDP, so with an existing pairing it should be discoverable even with visibility off.

Revision history for this message
Craig Ringer (ringerc) wrote :

Sorry, just to clarify: The testing in the last comment was done on a system running yesterday's intrepid.

Revision history for this message
Craig Ringer (ringerc) wrote :

... and now with the attachment.

Note that there's also a built-in USB HSDPA modem (a Dell 5520) in the machine, which will be shown in the attached lshal output.

Revision history for this message
Craig Ringer (ringerc) wrote :

New lshal output attached as requested.

Changed in network-manager:
status: Incomplete → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.