Lucid No 3G connection with Huawei E620

Bug #603830 reported by Mirko
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
modemmanager (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: modemmanager

Hi,

since Karmic I'm not able to establish a 3G connection. Actually I am working with Lucid.
I have a Asus eeePC 1000 HG with a built in Huwei E630 3G Card.
lsusb give me the following Information back. Bus 001 Device 002: ID 12d1:1001 Huawei Technologies Co., Ltd. E620 USB Modem

Following Information I get at the syslog.
Jul 10 02:41:39 trymon-laptop NetworkManager: <info> Activation (ttyUSB0) starting connection 'T-mobile (D1) connection 1'
Jul 10 02:41:39 trymon-laptop NetworkManager: <info> (ttyUSB0): device state change: 3 -> 4 (reason 0)
Jul 10 02:41:39 trymon-laptop NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 10 02:41:39 trymon-laptop NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
Jul 10 02:41:39 trymon-laptop NetworkManager: <info> (ttyUSB0): device state change: 4 -> 6 (reason 0)
Jul 10 02:41:39 trymon-laptop NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
Jul 10 02:41:39 trymon-laptop NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
Jul 10 02:41:39 trymon-laptop NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
Jul 10 02:41:39 trymon-laptop NetworkManager: <info> (ttyUSB0): device state change: 6 -> 4 (reason 0)
Jul 10 02:41:39 trymon-laptop NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
Jul 10 02:42:40 trymon-laptop NetworkManager: <WARN> stage1_prepare_done(): GSM modem connection failed: (32) Network timeout
Jul 10 02:42:40 trymon-laptop NetworkManager: <info> (ttyUSB0): device state change: 4 -> 9 (reason 1)
Jul 10 02:42:40 trymon-laptop NetworkManager: <info> Marking connection 'T-mobile (D1) connection 1' invalid.
Jul 10 02:42:40 trymon-laptop NetworkManager: <info> Activation (ttyUSB0) failed.
Jul 10 02:42:40 trymon-laptop NetworkManager: <info> (ttyUSB0): device state change: 9 -> 3 (reason 0)
Jul 10 02:42:40 trymon-laptop NetworkManager: <info> (ttyUSB0): deactivating device (reason: 0).
Jul 10 02:42:40 trymon-laptop NetworkManager: <info> Policy set 'Auto Fritz!Box Fon WLAN 7170' (wlan0) as default for routing and DNS.

The Networkmanager Version is 0.8

The Data of the Linux are
Description: Ubuntu 10.04.1 LTS
Release: 10.04
2.6.32-24-generic #38-Ubuntu SMP Mon Jul 5 09:22:14 UTC 2010 i686 GNU/Linux

I am thankful for every advice to solve the problem.

Revision history for this message
Kenny Meyer (knny-myer) wrote :

Thanks for reporting this bug!

Please, follow the instructions here: https://wiki.ubuntu.com/DebuggingNetworkManager in the section Debugging 3G problems and then attach the information to this bug report, please.

Revision history for this message
Mirko (mirko-gasparovic) wrote :

Hi,

thank you for your response. See attached the NetworkManager log.

Revision history for this message
Mirko (mirko-gasparovic) wrote :

And the Modem Log

Revision history for this message
Mirko (mirko-gasparovic) wrote :

And as last log the mm-test.py result

GSM modem
Driver: 'option1'
Modem device: '/sys/devices/pci0000:00/0000:00:1d.7/usb1/1-6'
Data device: 'ttyUSB0'
Vendor: huawei
Model: EM770
Version: 11.104.14.01.55
IMEI: <private>
IMSI: <private>
Signal quality: 51
Scanning...
T-Mobile D: current (UMTS)
T-Mobile D: available (GSM)
E-Plus: forbidden (GSM)
o2 - de: available (GSM)
Vodafone.de: available (UMTS)
Vodafone.de: available (GSM)
o2 - de: available (UMTS)
E-Plus: forbidden (UMTS)

Revision history for this message
Kenny Meyer (knny-myer) wrote :

Thanks, Mirko, for attaching the missing logs.

Could you please try connecting to your 3G network with your wireless card switched off? Describe what's happening. Still the same error? Maybe you can find something interesting in the logs?

Changed in modemmanager (Ubuntu):
status: New → Confirmed
Kenny Meyer (knny-myer)
summary: - Lucid No 3G connection with Huwei E620
+ Lucid No 3G connection with Huawei E620
Revision history for this message
Mirko (mirko-gasparovic) wrote :

Hi, I have deactivated the WLAN connection at the NetworkManager and created the logs again.

Revision history for this message
Mirko (mirko-gasparovic) wrote :

And again the modem log.

Revision history for this message
Mirko (mirko-gasparovic) wrote :

For additional Information. Actually I deactivated in the BIOS as functions but the 3G function and couldn't establish a connection.
With the Sasic3G I could establish a connection. So I have for this case a workaround. It would be nicer I could use the NetworkManager, as I could use it with 9.04.

The log of the connection with Sasik3G

Jul 12 00:00:19 trymon-laptop modem-manager: Caught signal 15, shutting down...
Jul 12 00:00:19 trymon-laptop modem-manager: (ttyUSB0) closing serial device...
Jul 12 00:00:59 trymon-laptop pppd[8220]: pppd 2.4.5 started by root, uid 0
Jul 12 00:00:59 trymon-laptop pppd[8220]: Using interface ppp0
Jul 12 00:00:59 trymon-laptop pppd[8220]: Connect: ppp0 <--> /dev/ttyUSB0
Jul 12 00:00:59 trymon-laptop pppd[8220]: CHAP authentication succeeded
Jul 12 00:00:59 trymon-laptop pppd[8220]: CHAP authentication succeeded
Jul 12 00:00:59 trymon-laptop kernel: [ 278.887564] PPP BSD Compression module registered
Jul 12 00:00:59 trymon-laptop kernel: [ 278.923358] PPP Deflate Compression module registered
Jul 12 00:01:01 trymon-laptop pppd[8220]: Could not determine remote IP address: defaulting to 10.64.64.64
Jul 12 00:01:01 trymon-laptop pppd[8220]: Cannot determine ethernet address for proxy ARP
Jul 12 00:01:01 trymon-laptop pppd[8220]: local IP address 10.171.165.72
Jul 12 00:01:01 trymon-laptop pppd[8220]: remote IP address 10.64.64.64
Jul 12 00:01:01 trymon-laptop pppd[8220]: primary DNS address 193.254.160.1
Jul 12 00:01:01 trymon-laptop pppd[8220]: secondary DNS address 10.74.83.22

Revision history for this message
Mirko (mirko-gasparovic) wrote :

The correct name is Sakis3G.

Revision history for this message
Kenny Meyer (knny-myer) wrote :

Mirko, I'm glad you found a workaround.

If you're interested in getting feedback to this problem within ModemManager, try to get in touch with the developers of the project.

Revision history for this message
akirak (troski) wrote :

Hi, i have the sabe bug with the NetworkManager, the device (the huawei e620) is detected as modem, but it doesn't connects even with the rigth provider options

Revision history for this message
Kenny Meyer (knny-myer) wrote :

@akirak, how do your logs look like?

Revision history for this message
Mirko (mirko-gasparovic) wrote :

Hi,

the past Weeks, I tried to find the reason for this Bug together with Dan Williams, one of the NM Developers.
This isn't a NM Problem. It's the Modem Manager. Finally he told me the following, which I will share with you.

---
Ok, we've seen this before once or twice; with the Huawei E1552 and
there's a bug on gnome.org for it. We're not quite sure what's causing
it, but the Huawei firmware does not appear to be standards compliant
for the AT+COPS command. It may work if you wait for the modem to
auto-register with the network before starting the connection in NM.
But for now I guess we'll need to work around the problem where the
modem just goes idle when we tell it to start looking for providers :(

Dan
---

So there is actually no working solution except to use the Sakis3G Script, which works quite good.

Revision history for this message
akirak (troski) wrote :
Revision history for this message
akirak (troski) wrote :
Revision history for this message
akirak (troski) wrote :

Those are the logs of nm and mm, the mm-test.py said:

GSM modem
Driver: 'option1'
Modem device: '/sys/devices/pci0000:00/0000:00:10.4/usb1/1-2'
Data device: 'ttyUSB1'
Vendor: huawei
Model: E1552
Version: 11.608.12.00.00
IMEI: <private>
IMSI: <private>
Signal quality: 64
Scanning...
DIGITEL GSM: current (UMTS)

Revision history for this message
Mirko (mirko-gasparovic) wrote :

A few days ago, I have updated to Maverick Meerkat Alpha 3 and the 3G connection works again.
So if they don't change to much until the release at modem-manager and NetworkManager this problem should be solved with a update to 10.10.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers