Huawei E620 does not connect in GPRS mode anymore, only UMTS

Bug #586894 reported by Lucio Crusca
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
linux (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: network-manager

I've got a Huawei E169 (seen as E620 by lsusb). Until Jaunty it used to work. I'm not sure about Karmic.

Now in Lucid it works only where there's UMTS/3G signal, but fails to connect in areas with only GPRS/GSM signal.
I've tried the same SIM card with another dongle and it works with GPRS too, and the same dongle+same SIM card in a UMTS area and it works. Same dongle, same SIM card, same GPRS place (my home), different OS (Windows 7) and it works (just to make sure I do have GPRS here and that the problem is not faulty hardware).

Maybe this is a duplicate of bug #446146 but I'm not sure.

ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: network-manager 0.8-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
CRDA: Error: [Errno 2] No such file or directory
Date: Fri May 28 18:18:46 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5)
IpRoute:
 10.150.44.0/24 dev wlan0 proto kernel scope link src 10.150.44.100 metric 2
 169.254.0.0/16 dev wlan0 scope link metric 1000
 default via 10.150.44.1 dev wlan0 proto static
Keyfiles: Error: [Errno 2] No such file or directory
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, user)
 LANG=it_IT.UTF-8
SourcePackage: network-manager

Revision history for this message
Lucio Crusca (lucrus) wrote :
Revision history for this message
Lucio Crusca (lucrus) wrote :

I've found a workaround: using a 2.6.34 mainline kernel in Lucid the bug disappears.
http://kernel.ubuntu.com/~kernel-ppa/mainline/

Revision history for this message
Lucio Crusca (lucrus) wrote :

Since changing the kernel the bug goes away, I assume this has nothing to do with network-manager

affects: network-manager (Ubuntu) → linux (Ubuntu)
tags: added: regression-release
Revision history for this message
Jeremy Foshee (jeremyfoshee) wrote :

Hi Lucio,

If you could also please test the latest upstream kernel available that would be great. It will allow additional upstream developers to examine the issue. Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Once you've tested the upstream kernel, please remove the 'needs-upstream-testing' tag. This can be done by clicking on the yellow pencil icon next to the tag located at the bottom of the bug description and deleting the 'needs-upstream-testing' text. Please let us know your results.

Thanks in advance.

    [This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

tags: added: needs-upstream-testing
tags: added: kj-triage
Changed in linux (Ubuntu):
status: New → Incomplete
Revision history for this message
Lucio Crusca (lucrus) wrote :

@Automated message; I've already tried 2.6.34 and it works
@Humans: see my posts on 2010-05-30

Changed in linux (Ubuntu):
status: Incomplete → New
tags: added: kernel-core
removed: needs-upstream-testing
Changed in linux (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
Revision history for this message
Lucio Crusca (lucrus) wrote :
Revision history for this message
the_mechanical (mechanical) wrote :

I have the same problem with ubuntu precise and kernel 3.2.0.
When i activate Mobile Broadband then i'm only able to connect when it is showing "UMTS Roaming". If "GSM Roaming" appears, then the connection will fail.
Solution for me: Repeating following things until UMTS Roaming is showed.
sudo service network-manager stop
sudo service network-manager start
Enable Mobile Broadband
Having a look wether GSM or UMTS is showing up. If it is GSM then repeat.
This problem occured since network-manager >0.5 !

Sometimes i could get angry, trying x times and no connection! Now i ordered a Router with USB-connection so i hopefully can connect without problems via WLAN. But this solves not the problem when i'm not at home.

Revision history for this message
penalvch (penalvch) wrote :

Lucio Crusca, this bug was reported a while ago and there hasn't been any activity in it recently. We were wondering if this is still an issue? If so, could you please test for this with the latest development release of Ubuntu? ISO images are available from http://cdimage.ubuntu.com/daily-live/current/ .

If it remains an issue, could you please run the following command in the development release from a Terminal (Applications->Accessories->Terminal), as it will automatically gather and attach updated debug information to this report:

apport-collect -p linux <replace-with-bug-number>

Also, could you please test the latest upstream kernel available following https://wiki.ubuntu.com/KernelMainlineBuilds ? It will allow additional upstream developers to examine the issue. Please do not test the daily kernel folder, but the one all the way at the bottom. Once you've tested the upstream kernel, please comment on which kernel version specifically you tested. If this bug is fixed in the mainline kernel, please add the following tags:
kernel-fixed-upstream
kernel-fixed-upstream-VERSION-NUMBER

where VERSION-NUMBER is the version number of the kernel you tested. For example:
kernel-fixed-upstream-v3.12-rc2

This can be done by clicking on the yellow circle with a black pencil icon next to the word Tags located at the bottom of the bug description. As well, please remove the tag:
needs-upstream-testing

If the mainline kernel does not fix this bug, please add the following tags:
kernel-bug-exists-upstream
kernel-bug-exists-upstream-VERSION-NUMBER

As well, please remove the tag:
needs-upstream-testing

Once testing of the upstream kernel is complete, please mark this bug's Status as Confirmed. Please let us know your results. Thank you for your understanding.

Changed in linux (Ubuntu):
status: Triaged → Incomplete
Revision history for this message
Lucio Crusca (lucrus) wrote :

@Christopher: are you really still working on this bug? Hasn't Lucid support ended on May 9, 2013? Btw, I found a workaround a long while ago, see my comment #2. And, on a side note, I'm not using Ubuntu anymore, let alone the Lucid release. Please don't get me wrong, I admire your commitment in fixing this, but honestly I'm not going to install Lucid anywhere now, it's too much work to get it going in my current hardware setup (I don't have the hardware I had in 2010 anymore).

Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in linux (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.