0.7, 3G network Orange Icon 225 USB key not handled by network manager

Bug #288208 reported by Laurent GUERBY
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager (Ubuntu)
Expired
Low
Unassigned

Bug Description

Binary package hint: network-manager

As described in the comments of:

https://bugs.launchpad.net/ubuntu/+source/hal-info/+bug/284961

When I plug

"Bus 002 Device 004: ID 0af0:6971 Option"

Even after installing manually rezero and hal-info patch, network manager does not work:

After a reboot, here what I get when I plug the key

Oct 20 18:20:47 pc NetworkManager: <info> ttyHS0: driver is 'hso'.
Oct 20 18:20:47 pc NetworkManager: <debug> [1224519647.496808] setup_monitor_device(): No monitoring udi provided
Oct 20 18:20:47 pc NetworkManager: <info> Found new Modem device 'ttyHS0'.
Oct 20 18:20:47 pc NetworkManager: <info> (ttyHS0): exported as /org/freedesktop/Hal/devices/usb_device_af0_6971_Serial_Number_if0_serial_unknown_0
Oct 20 18:20:51 pc NetworkManager: <info> (ttyHS0): device state change: 1 -> 2
Oct 20 18:20:51 pc NetworkManager: <info> (ttyHS0): deactivating device (reason: 2).
Oct 20 18:20:51 pc NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed
Oct 20 18:20:51 pc NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed
Oct 20 18:20:51 pc NetworkManager: <info> (ttyHS0): device state change: 2 -> 3
Oct 20 18:21:20 pc NetworkManager: <info> Activation (ttyHS0) starting connection 'Orange 3Gb'
Oct 20 18:21:20 pc NetworkManager: <info> (ttyHS0): device state change: 3 -> 4
Oct 20 18:21:20 pc NetworkManager: <info> Activation (ttyHS0) Stage 1 of 5 (Device Prepare) scheduled...
Oct 20 18:21:20 pc NetworkManager: <info> Activation (ttyHS0) Stage 1 of 5 (Device Prepare) started...
Oct 20 18:21:20 pc NetworkManager: <debug> [1224519680.142206] nm_serial_device_open(): (ttyHS0) opening device...
Oct 20 18:21:20 pc NetworkManager: <info> Activation (ttyHS0) Stage 1 of 5 (Device Prepare) complete.
Oct 20 18:21:20 pc NetworkManager: <WARN> check_pin_done(): PIN checking failed
Oct 20 18:21:20 pc NetworkManager: <info> (ttyHS0): device state change: 4 -> 9
Oct 20 18:21:20 pc NetworkManager: <debug> [1224519680.326062] nm_serial_device_close(): Closing device 'ttyHS0'
Oct 20 18:21:20 pc NetworkManager: <info> Marking connection 'Orange 3Gb' invalid.
Oct 20 18:21:20 pc NetworkManager: <info> Activation (ttyHS0) failed.
Oct 20 18:21:20 pc NetworkManager: <info> (ttyHS0): device state change: 9 -> 3
Oct 20 18:21:20 pc NetworkManager: <info> (ttyHS0): deactivating device (reason: 0).
Oct 20 18:21:20 pc NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed
Oct 20 18:21:20 pc NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed

When I manually follow the instructions from :

http://www.equinoxefr.org/post/2008/04/21/la-clef-orange-icon-225-sur-ubuntu-804

Both the connect.sh script and the python app do work and manage to setup the 3G network access.

So this is a network manager problem. As for parameters, in France APN is "orange.ie", USER and PASS should be empty (no use) and PIN is "0000".

Please find attached bug-icon-225.tgz which has various info on my system.

Revision history for this message
Laurent GUERBY (laurent-guerby) wrote :
Revision history for this message
TorstenSchlabach (tschlabach) wrote :

To make this bug report a bit more tangible:

I understand that the SIM card used requires a PIN, but network manager does not ask the user to enter it. Therefore the SIM card is not unlocked and cannot work.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. The issue that you reported is one that should be reproducible with the live environment of the Desktop CD of the development release the Karmic Koala. It would help us greatly if you could test with it so we can work on getting it fixed in the next release of Ubuntu. You can find out more about the development release at http://www.ubuntu.com/testing/ . Thanks again and we appreciate your help.

Changed in network-manager (Ubuntu):
status: New → Incomplete
importance: Undecided → Low
Revision history for this message
Daniel Holm (danielholm) wrote :

Hi all,

I also got this problem with a '0af0:6971 Option'-modem.

Running 'ls /dev/ttyU* /dev/ttyA* /dev/mod*' gives that the file or dir doesnt exist.

This is with Karmic installed with all the latest updates (as in just now) and I did not have to install the rezero package or patch, it was recognized directly by NetworkManager.

This is from dmesg just after I inserted the modem:
[17668.610035] usb 6-1: new full speed USB device using uhci_hcd and address 5
[17668.782537] usb 6-1: configuration #1 chosen from 1 choice
[17668.795046] hso0: Disabled Privacy Extensions

Changed in network-manager (Ubuntu):
status: Incomplete → Confirmed
Revision history for this message
Kai Ritterbusch (kai-ritterbusch) wrote :

Hello,

for me, option icon 225 usb modem works sometimes. In Jaunty, you had to connect twice for it to work quite reliably.

with karmic it worked directly after configuration of the network manager. later it stopped working.

dmesg gave a modem-manager segfault.

The next time it happens, I will post the log here. Now I am online with option icon 225 stick after deleting the connection in nm and re-setup. If you need anything, please tell me.

Revision history for this message
Thomas Hood (jdthood) wrote :

The Option iCON 225 is listed upstream

    https://live.gnome.org/NetworkManager/MobileBroadband

as supported. Does anyone still have problems with it in Precise or Quantal?

Changed in network-manager (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for network-manager (Ubuntu) because there has been no activity for 60 days.]

Changed in network-manager (Ubuntu):
status: Incomplete → Expired
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.