Bug 634195
| Summary: | Cannot connect to Internet with N900 | |||
|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | David Woodhouse <dwmw2> | |
| Component: | NetworkManager | Assignee: | Dan Williams <dcbw> | |
| Status: | CLOSED WONTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | |
| Severity: | medium | Docs Contact: | ||
| Priority: | low | |||
| Version: | 13 | CC: | dcbw, myllynen | |
| Target Milestone: | --- | |||
| Target Release: | --- | |||
| Hardware: | All | |||
| OS: | Linux | |||
| Whiteboard: | ||||
| Fixed In Version: | Doc Type: | Bug Fix | ||
| Doc Text: | Story Points: | --- | ||
| Clone Of: | ||||
| : | 637138 (view as bug list) | Environment: | ||
| Last Closed: | 2011-06-28 12:49:10 UTC | Type: | --- | |
| Regression: | --- | Mount Type: | --- | |
| Documentation: | --- | CRM: | ||
| Verified Versions: | Category: | --- | ||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
| Cloudforms Team: | --- | Target Upstream Version: | ||
| Embargoed: | ||||
| Bug Depends On: | ||||
| Bug Blocks: | 637138 | |||
|
Description
David Woodhouse
2010-09-15 13:35:01 UTC
So I tried Bluetooth, since that works too with wvdial and DUN is supposed to be supported. I tried to make the laptop pair with the phone, but it doesn't seem to show up in the 'Device search' when I select 'Set up new device...' from the bluetooth applet. Despite the fact that I can *see* the Inquiry results come in with hcidump. I tried pairing the other way round, initiated from the phone, but that didn't work either -- I never got the option to enable DUN on the phone when I pair them that way round. Earlier today I *did* somehow manage to pair them from the laptop side, although I'd deleted that pairing to redo my testing and file this bug. And then although it let me set up the device for DUN and choose my APN, etc., it still didn't turn up in NetworkManager. Aha, problem #1 in pairing -- despite having *tried* to go back to the initial state to restart from scratch, by removing the device in the applet GUI, it hadn't actually deleted the link keys. By removing all trace of the N900's bdaddr from all files in /var/lib/bluetooth, I can make it show up in the device search again.
Next problem... although the phone shows me a PIN and asks me to confirm, and in hcidump I see the same PIN:
> HCI Event: User Confirmation Request (0x33) plen 10
bdaddr 20:D6:07:55:3D:C2 passkey 839899
... the applet doesn't do anything useful; just keeps saying 'Connecting to 'dwmw2's N900'... until it times out and declares that the connection failed.
After taking hci0 device down, removing the btusb.ko module, killing bluetoothd and restarting everything, I finally managed to make it pair OK. Asked to use it to access the Internet (DUN) and was taken through the APN setup... but still it doesn't appear in NetworkManager. How am I supposed to connect? Sep 15 15:06:54 macbook modem-manager: (rfcomm0) closing serial device... Sep 15 15:06:54 macbook modem-manager: (rfcomm0) opening serial device... Sep 15 15:06:54 macbook modem-manager: (Generic): GSM modem /sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.1 claimed port rfcomm0 Sep 15 15:06:55 macbook NetworkManager[7233]: <info> ignoring modem 'rfcomm0' (no associated Bluetooth device) Sep 15 15:06:55 macbook modem-manager: Modem /org/freedesktop/ModemManager/Modems/2: Equipment identifier set (356938035851428) Sep 15 15:06:55 macbook modem-manager: (rfcomm0) closing serial device... After removing the bluetooth pairing (which worked this time) and doing it all *again*, it actually works... pairing... Sep 15 15:11:11 macbook bluetoothd[10063]: Discovery session 0x7f6a852de700 with :1.144 activated Sep 15 15:11:17 macbook bluetoothd[10063]: Stopping discovery Sep 15 15:11:19 macbook bluetoothd[10063]: link_key_request (sba=00:21:E9:D7:FA:E4, dba=20:D6:07:55:3D:C2) Sep 15 15:11:19 macbook bluetoothd[10063]: io_capa_request (sba=00:21:E9:D7:FA:E4, dba=20:D6:07:55:3D:C2) Sep 15 15:11:21 macbook bluetoothd[10063]: io_capa_response (sba=00:21:E9:D7:FA:E4, dba=20:D6:07:55:3D:C2) Sep 15 15:11:28 macbook bluetoothd[10063]: link_key_notify (sba=00:21:E9:D7:FA:E4, dba=20:D6:07:55:3D:C2, type=5) Sep 15 15:11:29 macbook bluetoothd[10063]: probe failed with driver input-headset for device /org/bluez/10063/hci0/dev_20_D6_07_55_3D_C2 ... probing for DUN configuration... Sep 15 15:11:38 macbook bluetoothd[10063]: link_key_request (sba=00:21:E9:D7:FA:E4, dba=20:D6:07:55:3D:C2) Sep 15 15:11:38 macbook bluetoothd[10063]: link_key_request (sba=00:21:E9:D7:FA:E4, dba=20:D6:07:55:3D:C2) Sep 15 15:11:38 macbook modem-manager: (rfcomm0) opening serial device... Sep 15 15:11:39 macbook modem-manager: (rfcomm0) closing serial device... Sep 15 15:11:39 macbook modem-manager: (rfcomm0) opening serial device... Sep 15 15:11:39 macbook modem-manager: (Generic): GSM modem /sys/devices/pci0000:00/0000:00:1a.0/usb3/3-1/3-1.1 claimed port rfcomm0 Sep 15 15:11:39 macbook NetworkManager[7233]: <info> ignoring modem 'rfcomm0' (no associated Bluetooth device) Sep 15 15:11:39 macbook modem-manager: Modem /org/freedesktop/ModemManager/Modems/3: Equipment identifier set (356938035851428) Sep 15 15:11:39 macbook modem-manager: (rfcomm0) closing serial device... ... and then after I select the network/APN ... Sep 15 15:12:02 macbook NetworkManager[7233]: <warn> (20:D6:07:55:3D:C2): failed to look up interface index Sep 15 15:12:02 macbook NetworkManager[7233]: <info> BT device dwmw2's N900 (20:D6:07:55:3D:C2) added (DUN) Sep 15 15:12:02 macbook NetworkManager[7233]: <info> (20:D6:07:55:3D:C2): new Bluetooth device (driver: 'bluez' ifindex: -1) Sep 15 15:12:02 macbook NetworkManager[7233]: <info> (20:D6:07:55:3D:C2): exported as /org/freedesktop/NetworkManager/Devices/7 Sep 15 15:12:02 macbook NetworkManager[7233]: <info> (20:D6:07:55:3D:C2): now managed Sep 15 15:12:02 macbook NetworkManager[7233]: <info> (20:D6:07:55:3D:C2): device state change: 1 -> 2 (reason 2) Sep 15 15:12:02 macbook NetworkManager[7233]: <info> (20:D6:07:55:3D:C2): deactivating device (reason: 2). Sep 15 15:12:02 macbook NetworkManager[7233]: <info> (20:D6:07:55:3D:C2): device state change: 2 -> 3 (reason 0) Sep 15 15:12:02 macbook dbus: [system] Rejected send message, 1 matched rules; type="method_return", sender=":1.139" (uid=0 pid=10063 comm="/usr/sbin/bluetoothd) interface="(unset)" member="(unset)" error name="(unset)" requested_reply=0 destination=":1.144" (uid=500 pid=10247 comm="bluetooth-wizard)) So I have it working... but it's taken me hours, and the power is back on now anyway so I can switch back to wireless. And I still only have it working over Bluetooth; not over the USB cable. That's not very useful, because my experience is that Bluetooth dialup support doesn't actually remain working from week to week; next time I need it I'm sure it'll be broken again.
The fact that I needed to sacrifice three chickens and wipe my configuration and repair the Bluetooth devices four times before it worked -- and the fact that I *did* manage to pair and ask for DUN earlier and still it didn't show up in NetworkManager, are probably all bugs on the BlueZ side.
But why can't I connect using the USB cable?
udi = '/org/freedesktop/Hal/devices/usb_device_421_1c8_noserial_if6_serial_unknown_0'
info.capabilities = {'serial', 'modem'} (string list)
info.category = 'serial' (string)
info.parent = '/org/freedesktop/Hal/devices/usb_device_421_1c8_noserial_if6' (string)
info.product = 'Serial Port' (string)
info.subsystem = 'tty' (string)
info.udi = '/org/freedesktop/Hal/devices/usb_device_421_1c8_noserial_if6_serial_unknown_0' (string)
linux.device_file = '/dev/ttyACM0' (string)
linux.hotplug_type = 2 (0x2) (int)
linux.subsystem = 'tty' (string)
linux.sysfs_path = '/sys/devices/pci0000:00/0000:00:1d.7/usb2/2-1/2-1:1.6/tty/ttyACM0' (string)
modem.command_sets = {'V.250'} (string list)
serial.device = '/dev/ttyACM0' (string)
serial.originating_device = '/org/freedesktop/Hal/devices/usb_device_421_1c8_noserial_if6' (string)
serial.port = 0 (0x0) (int)
serial.type = 'unknown' (string)
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed. |