Option iCon 225 (HSDPA USB stick) cannot connect (Jaunty Jackalope 9.04)

Bug #368325 reported by gabriela
48
This bug affects 2 people
Affects Status Importance Assigned to Milestone
NetworkManager
New
Undecided
Unassigned
mobile-broadband-provider-info (Ubuntu)
Invalid
Low
Unassigned
network-manager (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: network-manager

I'm using an Asus EeePC 1000H and am trying to use my Option Icon 225 internet USB stick (got this by Orange Switzerland). I seem to encounter similar problems as other users wrote, but on a brand new installed and completely updated Jaunty Jackalope (9.04).

This is what happens and can be reproduced: When I connect the stick the first time, a wizard appears, which lets me choose my country (Switzerland) and my provider (Orange). After clicking "Apply" (I'm not sure about the English menus, buttons and dialogs) a message appears at the upper right corner. It tells me that I can start the connection by clicking on the network icon. I do this, select "Orange". After that I get a small dialog box asking for the PIN code, which I type in correctly. Everything looks great, but then it will not connect. There's a small black box at the upper right corner telling me: "GSM Network - you are now offline". It doesn't matter if I boot the EeePC with the stick connected or if I connect it afterwards.

On that EeePC I first had Xandros (preinstalled by Asus). The stick worked there, but I prefer Ubuntu.

I attach two log files (syslog and serial log) of what's logged while connecting the stick and trying to get it work.

If you need other logs, please tell me how to get them. I'm not very experienced in this.

Gabriela

Revision history for this message
gabriela (salvie) wrote :
Revision history for this message
gabriela (salvie) wrote :
Revision history for this message
chinhow (ah-how402) wrote :

I have the exact same problem, however, i'm using Option GTM380 pci-e card with Celcom ISP (Malaysia). I start the connection then it will show "GSM Network - you are now offline". From the log, it shows "Modem initialization timed out" (stage 1 of 5)... Hope somebody can help to fix this, Thanks!

p/s: It's ok on intrepid, but break when i clean installed Jaunty.

Apr 28 22:00:45 iBuntu NetworkManager: <info> Activation (ttyHS0) starting connection 'Celcom'
Apr 28 22:00:45 iBuntu NetworkManager: <info> (ttyHS0): device state change: 3 -> 4
Apr 28 22:00:45 iBuntu NetworkManager: <info> Activation (ttyHS0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 28 22:00:45 iBuntu NetworkManager: <info> Activation (ttyHS0) Stage 1 of 5 (Device Prepare) started...
Apr 28 22:00:45 iBuntu NetworkManager: <debug> [1240927245.299895] nm_serial_device_open(): (ttyHS0) opening device...
Apr 28 22:00:45 iBuntu NetworkManager: <info> Activation (ttyHS0) Stage 1 of 5 (Device Prepare) complete.
Apr 28 22:00:56 iBuntu NetworkManager: <WARN> init_done(): Modem initialization timed out
Apr 28 22:00:56 iBuntu NetworkManager: <info> (ttyHS0): device state change: 4 -> 9
Apr 28 22:00:56 iBuntu NetworkManager: <debug> [1240927256.000798] nm_serial_device_close(): Closing device 'ttyHS0'
Apr 28 22:00:56 iBuntu NetworkManager: <info> Marking connection 'Celcom' invalid.
Apr 28 22:00:56 iBuntu NetworkManager: <info> Activation (ttyHS0) failed.
Apr 28 22:00:56 iBuntu NetworkManager: <info> (ttyHS0): device state change: 9 -> 3
Apr 28 22:00:56 iBuntu NetworkManager: <info> (ttyHS0): deactivating device (reason: 0).

Revision history for this message
gabriela (salvie) wrote :

I tried it on Intrepid, when Jaunty wasn't out yet. The stick didn't work there, either.

Revision history for this message
thepro (baer) wrote :

I think i'm facing the similar problem having an Option Icon 255. Currently, i'm unable to attach a serial log, but the bug description is the same on my machine. I've run Ubuntu 9.04 from live CD and tried to get a 3G connection. I will attach my debug files in about 2 week, then I will have plenty of time.

Revision history for this message
rapax (rmettier) wrote :

Exact same problem here, using an Acer Aspire One with Jaunty and an Icon225 USB modem for Orange Switzerland. Same symptoms, down to the letter.

I'd also be glad to provide any further information about this bug. Just let me know what you need me to do.

Revision history for this message
ali_o_kan (ali-o-kan) wrote :
Download full text (3.7 KiB)

Me too.

Ubuntu remix 9.04 sur mon eeePC 901, Icon225 USB modem for Mobistar Belgium.

Daemon.log

Apr 24 17:06:49 aliokan-laptop NetworkManager: <info> Activation (ttyHS0) starting connection 'Mobistar (personal)'
Apr 24 17:06:49 aliokan-laptop NetworkManager: <info> (ttyHS0): device state change: 3 -> 4
Apr 24 17:06:49 aliokan-laptop NetworkManager: <info> Activation (ttyHS0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 24 17:06:49 aliokan-laptop NetworkManager: <info> Activation (ttyHS0) Stage 1 of 5 (Device Prepare) started...
Apr 24 17:06:49 aliokan-laptop NetworkManager: <debug> [1240585609.942392] nm_serial_device_open(): (ttyHS0) opening device...
Apr 24 17:06:49 aliokan-laptop NetworkManager: <info> Activation (ttyHS0) Stage 1 of 5 (Device Prepare) complete.
Apr 24 17:06:50 aliokan-laptop NetworkManager: <info> (ttyHS0): powering up...
Apr 24 17:06:50 aliokan-laptop NetworkManager: <info> Registered on Home network
Apr 24 17:06:50 aliokan-laptop NetworkManager: <info> Associated with network: +COPS: 0,0,"Mobistar",2
Apr 24 17:06:50 aliokan-laptop NetworkManager: <info> Activation (ttyHS0) Stage 2 of 5 (Device Configure) scheduled...
Apr 24 17:06:50 aliokan-laptop NetworkManager: <info> Activation (ttyHS0) Stage 2 of 5 (Device Configure) starting...
Apr 24 17:06:50 aliokan-laptop NetworkManager: <info> (ttyHS0): device state change: 4 -> 5
Apr 24 17:06:50 aliokan-laptop NetworkManager: <info> (ttyHS0): device state change: 5 -> 6
Apr 24 17:06:50 aliokan-laptop NetworkManager: <info> Activation (ttyHS0) Stage 2 of 5 (Device Configure) complete.
Apr 24 17:06:50 aliokan-laptop NetworkManager: <info> Activation (ttyHS0) Stage 2 of 5 (Device Configure) scheduled...
Apr 24 17:06:50 aliokan-laptop NetworkManager: <info> Activation (ttyHS0) Stage 2 of 5 (Device Configure) starting...
Apr 24 17:06:50 aliokan-laptop NetworkManager: <info> (ttyHS0): device state change: 6 -> 5
Apr 24 17:06:51 aliokan-laptop NetworkManager: <info> Activation (ttyHS0) Stage 2 of 5 (Device Configure) complete.
Apr 24 17:06:51 aliokan-laptop NetworkManager: <info> Authentication successful!
Apr 24 17:06:58 aliokan-laptop NetworkManager: <info> Connected, Woo!
Apr 24 17:06:58 aliokan-laptop NetworkManager: <info> Activation (ttyHS0) Stage 3 of 5 (IP Configure Start) scheduled.
Apr 24 17:06:58 aliokan-laptop NetworkManager: <info> Activation (ttyHS0) Stage 3 of 5 (IP Configure Start) started...
Apr 24 17:06:58 aliokan-laptop NetworkManager: <info> (ttyHS0): device state change: 5 -> 7
Apr 24 17:06:58 aliokan-laptop NetworkManager: <info> Activation (ttyHS0) Stage 3 of 5 (IP Configure Start) complete.
Apr 24 17:06:58 aliokan-laptop NetworkManager: <info> Activation (ttyHS0) Stage 4 of 5 (IP Configure Timeout) scheduled...
Apr 24 17:06:58 aliokan-laptop NetworkManager: <info> Activation (ttyHS0) Stage 4 of 5 (IP Configure Timeout) started...
Apr 24 17:06:58 aliokan-laptop NetworkManager: <info> (ttyHS0): device state change: 7 -> 9
AApr 24 17:06:49 aliokan-laptop NetworkManager: <debug> [1240585609.942392] nm_serial_device_open(): (ttyHS0) opening device...
Apr 24 17:06:58 aliokan-laptop NetworkManager: <debug> [12...

Read more...

Revision history for this message
chinhow (ah-how402) wrote :

ok, i've solved my problem... kind of...

the main problem is usbserial module is not available in the 2.6.28-11 kernel, it's built into the kernel...

first, find the vendor and product id of ur modem, just type "lsusb" in the terminal,

Example:
Bus 004 Device 002: ID 0af0:7211 Option

then, the work-around is add "usbserial.vendor=0xXXXX usbserial.product=0xXXXX" to /boot/grub/menu.lst

Example (Option GTM380):
title Ubuntu 9.04, kernel 2.6.28-11-generic
uuid bd7a0e7b-1038-4409-9d2f-f6a9399fb035
kernel /boot/vmlinuz-2.6.28-11-generic root=UUID=bd7a0e7b-1038-4409-9d2f-f6a9399fb035 ro quiet splash usbserial.vendor=0x0af0 usbserial.product=0x7211
initrd /boot/initrd.img-2.6.28-11-generic
quiet

Reboot and u should be able to connect to internet... at least for me... pls feedback if this works for u guys... Thanks!

Revision history for this message
ali_o_kan (ali-o-kan) wrote :

I just tested your solution, but after reboot, the connection 3G is not visible in NetworkManager.

aliokan@aliokan-laptop:~$ lsusb
Bus 004 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 001 Device 004: ID 0c45:62c0 Microdia Pavilion Webcam
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 005 Device 002: ID 0b05:b700 ASUSTek Computer, Inc.
Bus 005 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 003: ID 0af0:6971 Option
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub

aliokan@aliokan-laptop:~$ sudo vi /boot/grub/menu.lst

title Ubuntu 9.04, kernel 2.6.28-11-generic
uuid 53357e50-e6a0-4b50-86c7-668a11e4053f
kernel /vmlinuz-2.6.28-11-generic root=UUID=4acafa8e-9e21-4cb8-acc7-1c49dabdc7b0 ro quiet splash usbserial.vendor=0x0af0 usbserial.product=0x6971
initrd /initrd.img-2.6.28-11-generic
quiet

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

please try the following patch.

Changed in network-manager (Ubuntu):
status: New → Confirmed
Revision history for this message
Alexander Sack (asac) wrote :
Revision history for this message
ali_o_kan (ali-o-kan) wrote :

How does one apply the patch? This is the first time for me. :p

Revision history for this message
gabriela (salvie) wrote :

Unfortunately, I don't know how to apply the patch, too.

Revision history for this message
thepro (baer) wrote :

I'm currently unable to try it out on Jaunty but I suggest the following.
I have searched for the network manager source and is seems that the patch is already applied in version 0.71. Source is available at http://ftp.gnome.org/pub/GNOME/sources/NetworkManager/0.7/ .
I found a debian packet for this version at: http://packages.ubuntu.com/de/jaunty/i386/network-manager/download .
Just look for the following deb packet:
network-manager_0.7.1~rc4.1.cf199a964-0ubuntu2_i386.deb

Maybe someone can try to install this packet with apt-get and report if it solves the issue maybe with the additional suggestion of chinhow.

Additionaly, i would like to know if Alexander Sack's patch does also solve the problem for an Option Icon 255 instead of 225. I have an 255 and the bug behaviour is completely the same.

Revision history for this message
gabriela (salvie) wrote :

@thepro: I had a look in Synaptic. The version of my "network-manager" module already seems to be "0.7.1~rc4.1.cf199a964-0ubuntu2".

@Alexander Sack: is your patch a patch for "hso/hsoconnect" by pharscape.org? If it isn't, I'd be happy to know how to apply it.

I didn't try to use the hso/hsoconnect solution by pharscape.org, because I'd rather wait for a real (official) Ubuntu solution. I'm reluctant in using non-official modules. You never know if they will be updated and if regular Ubuntu updates could set them out of order.

gabriela

Revision history for this message
Rapax (xxi-rapax) wrote :

Ok, I've tried the patch, and either I'm doing something wrong (very probable), or it doesn't work.

I tried to ways to apply it:
1) I downloaded the sources for 'network-manager' from packages.ubuntu.com for the relevant kernel, both the orig.tar.gz and the diff.gz files. I unpacked the orig.tar.gz and applied the diff.gz files with 'patch -p1'. I then applied the patch provided here, also with 'patch -p1'. I then tried to 'make deb', but apparently, there's no information about making deb packages in the Makefile, so I stopped there.
2) I installed the network manager sources through 'apt-get source network-manager' to /usr/src/. I then applied the provided patch to the source files, again with 'patch -p1...', and then tried 'dpkg-buildpackage -b'. This created a bunch of .deb files, which I installed with dpkg -i *.deb. So far, everything was looking good.
I rebooted, but now network-manager doesn't start at all any more, and nothing I do seems to get my network up and running anymore.

I then tried to reinstall the original network-manager package (that I had downloaded beforehand, to be safe), but while the installation went smoothly, I still have no working network manager.

I'm probably going to go for a clean reinstall of jaunty this evening or tomorrow.

So, if you can see where I went wrong, please drop me a hint. Or if you need info from any log files, just let me know.

Revision history for this message
thepro (baer) wrote :

@gabriela It's really strange I looked into the network manager 0.71 source code on packages.ubuntu.com and this version does not contain the changes of the above attached patch. Consequently, the current version 0.71 installed via synaptic does not include the patch.
However, the network manager 0.71 version on http://ftp.gnome.org/pub/GNOME/sources/NetworkManager/0.7/ does include the changes of the above patch!

Maybe someone can try the src from http://ftp.gnome.org/pub/GNOME/sources/NetworkManager/0.7/ additionaly I found a forum entry that explained how to install an older network manager from source the general procedure for the newer version should not differ that much. Here is the link for the mentioned forum entry: http://ubuntuforums.org/showthread.php?t=610828

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

to build with patch do:

sudo apt-get install build-essential
sudo apt-get install fakeroot
sudo apt-get build-dep network-manager

mkdir /tmp/test

cd /tmp/test

<<<download the patch here as "mypatch.diff">>>

# get sources:
apt-get source network-manager

# patch sources:
cd network-manager-*/
patch -p1 < ../mypatch.diff

# build package
dpkg-buildpackage -rfakeroot

# now install new packages:
cd ../
sudo dpkg -i *.deb

Revision history for this message
gabriela (salvie) wrote :

Alexander, this didn't work, either.

I've applied the patch as you wrote.

I wasn't able to connect. And after a reboot of my EeePC the mobile internet connection didn't even show up in the menu (when you click on the network icon), even when the stick was plugged.

gabriela

Revision history for this message
Bambr (s-bambr) wrote :

I have this problem too.

Asus eeePc 901
Ubuntu 9.04
Option Icon 225
network-manager_0.7.1~rc4.1.cf199a964-0ubuntu2_i386.deb

Revision history for this message
thepro (baer) wrote :

I found a workaround for my Option Icon 255. I entered a dummy username and password in my mobile broadband connection settings, because these values were usually blank for my carrier O2 Germany. Then, I'm able to connect and the connection does not drop anymore as it was the case without specified username and password.
My carrier O2 requires no username and password and ignores these values, maybe network manager should set the authentication type to 0 (this stands for none), when blank password and username are given. Currently, it sets the authentication type to 1 (stands for PAP = Password Authentication Protocol) and sends empty strings for username and password.

This behaviour is reflected in gabriela's log:
NetworkManager: <debug> [1240880027.417063] nm_serial_debug(): Sending: 'AT$QCPDPP=1,1,"",""
Then the authentication failed:
NetworkManager: <WARN> hso_auth_done(): Authentication failed
and the connection is dropped

@gabriela your seriallog implies that you have not specified username and password too. Maybe you can try some dummy values, and my workaround works for the option icon 225, too.

As a result, I can confirm that the Option Icon 255 works out-of-the-box in Jaunty, when a dummy username and password is used. Maybe, network manager should use none authentication, when no username and password are specified in the mobile broadband connection's settings.

Revision history for this message
rapax (rmettier) wrote :

@thepro: Thank you! That simple workaround actually solved the problem. You're brilliant, and I'm frustrated that I didn't think of trying this myself ;)

I can hereby officially confirm: Icon 225 with Orange Switzerland works perfectly in Jaunty if any username/password is set. I set none/none and it's working like a dream now.

Revision history for this message
gabriela (salvie) wrote :

OMG! Why can't everything be as simple as that? thepro, you are my hero.

I normally don't need any username/password for my iCon 225, so I didn't dare to enter any username/password. But it works with dummy values.

The only thing that doesn't work now is "disconnect". But pulling the plug or shutting down my netbook will do this.

You made me happy, because finally I can take my netbook out, using Ubuntu :-)

gabriela

Revision history for this message
Bambr (s-bambr) wrote :

Really big thanks to you.

I live in Ukraine and my 3g operator is Utel.

Your method is right for me.

Revision history for this message
Gerd (gerd-armbruster) wrote :

The workaround works perfect with
- Ubuntu 9.04 Netbook Remix
- Acer Aspire 110
- o2 Provider Germany

I can start AND stop the connection without any problems

Thank you thepro

Revision history for this message
Andres Mujica (andres.mujica) wrote :

According to original's reporter this is not a bug on NM, but in mobile-broadband-provider info, where is needed a proper entry for the orange ISP used by Gabriela

Changed in network-manager (Ubuntu):
status: Confirmed → Invalid
Changed in mobile-broadband-provider-info (Ubuntu):
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
P Karppinen (flameandthefire) wrote :

I can confirm that this OPTION ICON 225 USB stick + Ubuntu 9.04 Jaunty connection problem affects also finnish mobile internet service provider DNA connection.

Those finnish customers who are customers of DNA service provider in Finland and have Option Icon 225 USB stick (more familiar name to this is "mokkula" here in Finland) will need to edit connection settings to match below settings:

DNA Finland mobile 3G wireless broadband connection with Ubuntu Linux Jaunty 9.04 connection settings
=============================================================

APN: internet <-------- This value is automatically configured by Ubuntu Jaunty 9.04 so no need to edit this.
Username: guest <------- This value ("guest") needs to be manually entered, otherwise connection will not work properly.
Password: guest <------- This value ("guest") needs to be manually entered, otherwise connection will not work properly.

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

Does anyone know if this has been fixed in newer versions?

Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

No, the username and password aren't in mbpi yet.

Revision history for this message
Marius B. Kotsbak (mariusko) wrote :

You mean mbpi does not support usernames/passwords or that it lacks entries for some providers?

Maybe those network operators have stopped requiring login?

Revision history for this message
Bhavani Shankar (bhavi) wrote :

Sorry for the late response. Do you still require a password to login to your service provider using the latest m-b-p-i package?

Regards
Bhavani

Revision history for this message
Bhavani Shankar (bhavi) wrote :

Marking bug incomplete due to lack of data presently

Regards
Bhavani

Changed in mobile-broadband-provider-info (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Bhavani Shankar (bhavi) wrote :

Closing this bug for now due to insufficient data presently.

Changed in mobile-broadband-provider-info (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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