Ubuntu
network-manager package

D02HW (HuaweiE220 OEM product) modem doesn't answer the GPRS(HSDPA) command set

Bug #359063 reported by sunatomo
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
udev
Invalid
Undecided
Unassigned
network-manager (Ubuntu)
Expired
Undecided
Unassigned
Declined for Jaunty by Brian Murray

Bug Description

Binary package hint: network-manager

I'd installed the Jaunty , and try the huawei E220 CDMA (HSDPA) works.
My mobile provider is e-mobile (Japan).

In intrepid, I have to add the ' <append key="modem.command_sets" type="strlist">IS-707-A</append>' to work this modem correct at this mobile provider.

In Jaunty, I heard "hal-info" does not used and udev select the correct modem-setting (it uses nm-modem-probe to probe the modem command_sets).
nm-modem-probe shows this modem use GSM command_sets (I think it has to show CDMA to work in my enviroment).

I think this device has both GSM and CDMA modem command_sets, and there are both mobile providers use GSM or CDMA modem command_sets (many of mobile providers use GSM comannd_sets, but e-mobile use CDMA).

lsusb -v result:
Bus 002 Device 003: ID 12d1:1003 Huawei Technologies Co., Ltd. E220 HSDPA Modem / E270 HSDPA/HSUPA Modem
Device Descriptor:
  bLength 18
  bDescriptorType 1
  bcdUSB 1.10
  bDeviceClass 0 (Defined at Interface level)
  bDeviceSubClass 0
  bDeviceProtocol 0
  bMaxPacketSize0 64
  idVendor 0x12d1 Huawei Technologies Co., Ltd.
  idProduct 0x1003 E220 HSDPA Modem / E270 HSDPA/HSUPA Modem
  bcdDevice 0.00
  iManufacturer 1
  iProduct 2
  iSerial 0
  bNumConfigurations 1
  Configuration Descriptor:
    bLength 9
    bDescriptorType 2
    wTotalLength 85
    bNumInterfaces 3
    bConfigurationValue 1
    iConfiguration 0
    bmAttributes 0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower 500mA
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 0
      bAlternateSetting 0
      bNumEndpoints 3
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 255 Vendor Specific Subclass
      bInterfaceProtocol 255 Vendor Specific Protocol
      iInterface 3
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x81 EP 1 IN
        bmAttributes 3
          Transfer Type Interrupt
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0010 1x 16 bytes
        bInterval 128
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x82 EP 2 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x02 EP 2 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 1
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 255 Vendor Specific Class
      bInterfaceSubClass 255 Vendor Specific Subclass
      bInterfaceProtocol 255 Vendor Specific Protocol
      iInterface 3
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x85 EP 5 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x05 EP 5 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
    Interface Descriptor:
      bLength 9
      bDescriptorType 4
      bInterfaceNumber 2
      bAlternateSetting 0
      bNumEndpoints 2
      bInterfaceClass 8 Mass Storage
      bInterfaceSubClass 6 SCSI
      bInterfaceProtocol 80 Bulk (Zip)
      iInterface 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x83 EP 3 IN
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
      Endpoint Descriptor:
        bLength 7
        bDescriptorType 5
        bEndpointAddress 0x04 EP 4 OUT
        bmAttributes 2
          Transfer Type Bulk
          Synch Type None
          Usage Type Data
        wMaxPacketSize 0x0040 1x 64 bytes
        bInterval 0
cannot read device status, Operation not permitted (1)

/var/log/syslog result:
Apr 10 20:08:13 eeepc-ubuntu kernel: [ 2770.596085] usb 2-2: new full speed USB device using uhci_hcd and address 2
Apr 10 20:08:13 eeepc-ubuntu kernel: [ 2770.757921] usb 2-2: configuration #1 chosen from 1 choice
Apr 10 20:08:13 eeepc-ubuntu kernel: [ 2770.764189] usb-storage: probe of 2-2:1.0 failed with error -1
Apr 10 20:08:14 eeepc-ubuntu kernel: [ 2770.824115] usb 2-2: USB disconnect, address 2
Apr 10 20:08:14 eeepc-ubuntu kernel: [ 2771.560080] usb 2-2: new full speed USB device using uhci_hcd and address 3
Apr 10 20:08:14 eeepc-ubuntu kernel: [ 2771.722874] usb 2-2: configuration #1 chosen from 1 choice
Apr 10 20:08:15 eeepc-ubuntu kernel: [ 2771.773389] usb-storage: probe of 2-2:1.0 failed with error -5
Apr 10 20:08:15 eeepc-ubuntu kernel: [ 2771.797199] usb-storage: probe of 2-2:1.1 failed with error -5
Apr 10 20:08:15 eeepc-ubuntu kernel: [ 2771.820189] usb-storage: probe of 2-2:1.2 failed with error -1
Apr 10 20:08:15 eeepc-ubuntu kernel: [ 2771.962246] USB Serial support registered for GSM modem (1-port)
Apr 10 20:08:15 eeepc-ubuntu kernel: [ 2771.962369] option 2-2:1.0: GSM modem (1-port) converter detected
Apr 10 20:08:15 eeepc-ubuntu kernel: [ 2771.962573] usb 2-2: GSM modem (1-port) converter now attached to ttyUSB0
Apr 10 20:08:15 eeepc-ubuntu kernel: [ 2771.962608] option 2-2:1.1: GSM modem (1-port) converter detected
Apr 10 20:08:15 eeepc-ubuntu kernel: [ 2771.962803] usb 2-2: GSM modem (1-port) converter now attached to ttyUSB1
Apr 10 20:08:15 eeepc-ubuntu kernel: [ 2771.962858] usbcore: registered new interface driver option
Apr 10 20:08:15 eeepc-ubuntu kernel: [ 2771.962866] option: v0.7.2:USB Driver for GSM modems
Apr 10 20:08:15 eeepc-ubuntu NetworkManager: <info> (ttyUSB1): ignoring due to lack of mobile broadband capabilties
Apr 10 20:08:15 eeepc-ubuntu nm-system-settings: SCPlugin-Ifupdown: device added (udi: /org/freedesktop/Hal/devices/usb_device_12d1_1003_noserial_if0_serial_usb_0, iface: (null)): iface not found
Apr 10 20:08:15 eeepc-ubuntu NetworkManager: <info> (ttyUSB0): found serial port (udev:GSM hal:GSM)
Apr 10 20:08:15 eeepc-ubuntu NetworkManager: <info> (ttyUSB0): new Modem device (driver: 'option')
Apr 10 20:08:15 eeepc-ubuntu NetworkManager: <info> (ttyUSB0): exported as /org/freedesktop/Hal/devices/usb_device_12d1_1003_noserial_if0_serial_usb_0
Apr 10 20:08:20 eeepc-ubuntu NetworkManager: <info> (ttyUSB0): device state change: 1 -> 2
Apr 10 20:08:20 eeepc-ubuntu NetworkManager: <info> (ttyUSB0): deactivating device (reason: 2).

nm-modem-probe result:
/lib/udev/nm-modem-probe --verbose /dev/ttyUSB1
L: main(): (/dev/ttyUSB1): usb-vid 0x0000 usb-pid 0x0000 usb-intf 0 driver '(null)'
L: main(): probing /dev/ttyUSB1
L: modem_send_command(): Sending: 'AT+GCAP
'
': modem_wait_reply(): Got: 'AT+GCAP
L: modem_wait_reply(): Got: 'AT+GCAP
+GCAP: +CGSM,+DS,+ES

OK
'
L: modem_probe_caps(): GCAP response: +GCAP: +CGSM,+DS,+ES
L: main(): /dev/ttyUSB1: caps (0x19) GSM

2009/05/28 added AT&V result

AT&V
&C: 2; &D: 2; &F: 0; E: 1; L: 0; M: 0; Q: 0; V: 1; X: 0; Z: 0; S0: 0;
S3: 13; S4: 10; S5: 8; S6: 2; S7: 50; S8: 2; S9: 6; S10: 14; S11: 95;
+FCLASS: 0; +ICF: 3,3; +IFC: 2,2; +IPR: 115200; +DR: 0; +DS: 0,0,2048,6;
+WS46: 12; +CBST: 0,0,1;
+CRLP: (61,61,48,6,0),(61,61,48,6,1),(240,240,52,6,2);
+CV120: 1,1,1,0,0,0; +CHSN: 0,0,0,0; +CSSN: 0,0; +CREG: 0; +CGREG: 0;
+CFUN:; +CSCS: "IRA"; +CSTA: 129; +CR: 0; +CRC: 0; +CMEE: 0; +CGDCONT: (1,"IP","emb.ne.jp","0.0.0.0",0,0)
; +CGDSCONT: ; +CGTFT: ; +CGEQREQ: (1,2,0,0,0,0,2,0,"0E0","0E0",3,0,0),(2,2,0,0,0,0,2,0,"0E0","0E0",3,0,0),(3,2,0,0,0,0,2,0,"0E0","0E0",3,0,0),(4,2,0,0,0,0,2,0,"0E0","0E0",3,0,0),(5,2,0,0,0,0,2,0,"0E0","0E0",3,0,0),(6,2,0,0,0,0,2,0,"0E0","0E0",3,0,0),(7,2,0,0,0,0,2,0,"0E0","0E0",3,0,0),(8,2,0,0,0,0,2,0,"0E0","0E0",3,0,0),(9,2,0,0,0,0,2,0,"0E0","0E0",3,0,0),(10,2,0,0,0,0,2,0,"0E0","0E0",3,0,0),(11,2,0,0,0,0,2,0,"0E0","0E0",3,0,0),(12,2,0,0,0,0,2,0,"0E0","0E0",3,0,0),(13,2,0,0,0,0,2,0,"0E0","0E0",3,0,0),(14,2,0,0,0,0,2,0,"0E0","0E0",3,0,0),(15,2,0,0,0,0,2,0,"0E0","0E0",3,0,0),(16,2,0,0,0,0,2,0,"0E0","0E0",3,0,0)
; +CGEQMIN: ; +CGQREQ: ; +CGQMIN: ; ; +CGEREP: 0,0; +CGCLASS: "A";
+CGSMS: 3; +CSMS: 0; +CMGF: 0; +CSMP: ,,0,0;
+CSDH: 0; +CSCB: 0,"",""; +FDD: 0; +FAR: 0; +FCL: 0; +FIT: 0,0; +ES: ,,;
+ESA: 0,,,,0,0,255,; +CMOD: 0; +CVHU: 1; ; +CPIN: ,; +CMEC: 0,0,0;
+CKPD: 1,1; +CGATT: 1; +CGACT: 0; +CPBS: "SM"; +CPMS: "SM","SM","SM";
+CNMI: 0,0,0,0,0; +CMMS: 2; +FTS: 0; +FRS: 0; +FTH: 3; +FRH: 3; +FTM: 96;
+FRM: 96; +CCUG: 0,0,0; +COPS: 0,2,""; +CUSD: 0; +CAOC: 1; +CCWA: 0;
+CLVL: 2; +CMUT: 0; +CPOL: 0,2,"",0,0,0; +CPLS: 0; +CTZR: 0; +CLIP: 0;
+COLP: 0; +CLIR: 0; ^PORTSEL: 0; ^CPIN: ,; ^ATRECORD: 0;
^FREQLOCK: 11010860,12481268\0x00

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

can you check what the ATI command gives for you when send to /dev/ttyUSB1?

Revision history for this message
sunatomo (naiyu) wrote :

Hello Alexander, thank you for your reply.
I'd checked the ATI command and the result was below.

$ echo -e "ATI\r" > /dev/ttyUSB1
$ tr -s "\n" < /dev/ttyUSB1

^BOOT:12695676,0,0,0,38
^C

Brian Murray (brian-murray)
summary: - CDMA modem don't anser the correct command set
+ CDMA modem don't answer the correct command set
Alexander Sack (asac)
Changed in udev:
status: New → Invalid
Revision history for this message
Alexander Sack (asac) wrote : Re: CDMA modem don't answer the correct command set

please check the AT+GMM command too.

Please double check that you are using the right APN.

Changed in network-manager (Ubuntu):
status: New → Incomplete
Revision history for this message
sunatomo (naiyu) wrote :
Download full text (5.0 KiB)

I'd send the "ATI" , "AT+GMM" and "AT+CGDCONT?" command to /dev/ttyUSB0,
here is the result of that (via minicom)
--------------------- minicom result start ----------------------
ATI
Manufacturer: huawei
Model: D02HW
Revision: 11.005.08.00.168
IMEI: 356060012695676
+GCAP: +CGSM,+DS,+ES

OK

AT+GMM
D02HW

OK

AT+CGDCONT?
+CGDCONT: 1,"IP","emb.ne.jp","0.0.0.0",0,0
------------------ minicom result end -----------------

And I'd checked this device to run with pppconfig, pon poff scripts.
pon and poff works correct.

Here's my config of pppconfig
--------- pppconfig-peer start -----------------------
hide-password
noauth
connect "/usr/sbin/chat -v -f /etc/chatscripts/emobile"
debug
/dev/ttyUSB0
115200
defaultroute
noipdefault
user "em"
remotename emobile
ipparam emobile
---------- pppconfig-peer end ---------------------
using phone number in pppconfig is *99***1#
(CID number 1, APN is "emb.ne.jp" that was modem's default setting)

And I made the GSM config via nm-connection-editor, and I connected the mobile-broadband
here is the syslog message.
---------- syslog (NetworkManager) -----------
Apr 15 23:32:45 eeepc-ubuntu NetworkManager: <info> Activation (ttyUSB0) starting connection 'e-mobile'
Apr 15 23:32:45 eeepc-ubuntu NetworkManager: <info> (ttyUSB0): device state change: 3 -> 4
Apr 15 23:32:45 eeepc-ubuntu NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 15 23:32:45 eeepc-ubuntu NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
Apr 15 23:32:45 eeepc-ubuntu NetworkManager: <debug> [1239805965.439117] nm_serial_device_open(): (ttyUSB0) opening device...
Apr 15 23:32:45 eeepc-ubuntu NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
Apr 15 23:32:45 eeepc-ubuntu NetworkManager: <info> (ttyUSB0): powering up...
Apr 15 23:33:01 eeepc-ubuntu NetworkManager: <WARN> automatic_registration_response(): Automatic registration failed: not registered and not s
earching.
Apr 15 23:33:01 eeepc-ubuntu NetworkManager: <info> (ttyUSB0): device state change: 4 -> 9
Apr 15 23:33:01 eeepc-ubuntu NetworkManager: <debug> [1239805981.030361] nm_serial_device_close(): Closing device 'ttyUSB0'
Apr 15 23:33:01 eeepc-ubuntu NetworkManager: <info> Marking connection 'e-mobile' invalid.
Apr 15 23:33:01 eeepc-ubuntu NetworkManager: <info> Activation (ttyUSB0) failed.
Apr 15 23:33:01 eeepc-ubuntu NetworkManager: <info> (ttyUSB0): device state change: 9 -> 3
Apr 15 23:33:01 eeepc-ubuntu NetworkManager: <info> (ttyUSB0): deactivating device (reason: 0).
Apr 15 23:33:01 eeepc-ubuntu NetworkManager: <info> Policy set 'home' (ra0) as default for routing and DNS.
Apr 15 23:33:01 eeepc-ubuntu NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed
Apr 15 23:33:01 eeepc-ubuntu NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed
Apr 15 23:33:20 eeepc-ubuntu kernel: [ 7096.189114] ===>rt_ioctl_giwscan. 2(2) BSS returned, data->length = 323
Apr 15 23:33:26 eeepc-ubuntu NetworkManager: <info> Activation (ttyUSB0) starting connection 'e-mobile'
Apr 15 23:33:2...

Read more...

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

can you remove libmbca0 package for testing and remove your configured connection from the connection editor. on next start NM will create "Auto GSM Connection" entries. maybe those work better?

Revision history for this message
sunatomo (naiyu) wrote :

I'd remove the libmbca0 package, reboot and try testing the "Auto GSM Connection".
I only edit the "Auto GSM Connection" in configuration user, password, and APN value.
But, it doesn't connect.
Here is syslog when I'm tryng the connection using "Auto GSM Connection"

--------------------- syslog start --------------------
Apr 16 19:21:20 eeepc-ubuntu NetworkManager: <info> Activation (ttyUSB0) starting connection 'Auto GSM Connection'
Apr 16 19:21:20 eeepc-ubuntu NetworkManager: <info> (ttyUSB0): device state change: 3 -> 4
Apr 16 19:21:20 eeepc-ubuntu NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) scheduled...
Apr 16 19:21:20 eeepc-ubuntu NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) started...
Apr 16 19:21:20 eeepc-ubuntu NetworkManager: <debug> [1239877280.661163] nm_serial_device_open(): (ttyUSB0) opening device...
Apr 16 19:21:20 eeepc-ubuntu NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
Apr 16 19:21:20 eeepc-ubuntu NetworkManager: <info> (ttyUSB0): powering up...
Apr 16 19:21:36 eeepc-ubuntu NetworkManager: <WARN> automatic_registration_response(): Automatic registration failed: not registered and not searching.
Apr 16 19:21:36 eeepc-ubuntu NetworkManager: <info> (ttyUSB0): device state change: 4 -> 9
Apr 16 19:21:36 eeepc-ubuntu NetworkManager: <debug> [1239877296.021389] nm_serial_device_close(): Closing device 'ttyUSB0'
Apr 16 19:21:36 eeepc-ubuntu NetworkManager: <info> Marking connection 'Auto GSM Connection' invalid.
Apr 16 19:21:36 eeepc-ubuntu NetworkManager: <info> Activation (ttyUSB0) failed.
Apr 16 19:21:36 eeepc-ubuntu NetworkManager: <info> (ttyUSB0): device state change: 9 -> 3
Apr 16 19:21:36 eeepc-ubuntu NetworkManager: <info> (ttyUSB0): deactivating device (reason: 0).
Apr 16 19:21:36 eeepc-ubuntu NetworkManager: nm_system_device_flush_ip4_routes_with_iface: assertion `iface_idx >= 0' failed
Apr 16 19:21:36 eeepc-ubuntu NetworkManager: nm_system_device_flush_ip4_addresses_with_iface: assertion `iface_idx >= 0' failed

Revision history for this message
sunatomo (naiyu) wrote :

I'd like to see the debug messagges of NetworkManager (Especially at ATcommannds).
And I'like to check the behaivior of NetworkManger, if this modem manually configure as CDMA (IS-707-A).

Does someone tell the methods for above how do I configure?

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

to get AT commands do:

sudo killall NetworkManager

export NM_SERIAL_DEBUG=1
sudo NetworkManager --no-daemon

...
now you will see the comands as they flow.

CDMA might be a workaround because the command set is so simple that it just selects some default profile on your SIM. The right fix is to make this work with GSM command set.

Revision history for this message
sunatomo (naiyu) wrote :

I'd added the NM_SERIAL_DEBUG enviroment args to 1 and checked the connection.
Here's the result of syslog (NetworkManager output)

May 7 19:39:55 eeepc-ubuntu NetworkManager: <debug> [1241692795.738849] nm_serial_device_open(): (ttyUSB0) opening device...
May 7 19:39:55 eeepc-ubuntu NetworkManager: <info> Activation (ttyUSB0) Stage 1 of 5 (Device Prepare) complete.
May 7 19:39:55 eeepc-ubuntu NetworkManager: <debug> [1241692795.848876] nm_serial_debug(): Sending: 'ATZ E0 V1 X4 &C1 +FCLASS=0 '
May 7 19:39:55 eeepc-ubuntu NetworkManager: <debug> [1241692795.906829] nm_serial_debug(): Got: 'ATZ E0 V1 X4 &C1 +FCLASS=0 '
May 7 19:39:55 eeepc-ubuntu NetworkManager: <debug> [1241692795.916967] nm_serial_debug(): Got: 'ATZ E0 V1 X4 &C1 +FCLASS=0 OK '
May 7 19:39:55 eeepc-ubuntu NetworkManager: <debug> [1241692795.917147] nm_serial_debug(): Sending: 'AT+CPIN? '
May 7 19:39:55 eeepc-ubuntu NetworkManager: <debug> [1241692795.936987] nm_serial_debug(): Got: ' +CPIN: READY OK '
May 7 19:39:55 eeepc-ubuntu NetworkManager: <debug> [1241692795.937146] nm_serial_debug(): Sending: 'ATZ E0 V1 X4 &C1 +FCLASS=0 '
May 7 19:39:56 eeepc-ubuntu NetworkManager: <debug> [1241692796.004022] nm_serial_debug(): Got: ' OK '
May 7 19:39:56 eeepc-ubuntu NetworkManager: <info> (ttyUSB0): powering up...
May 7 19:39:56 eeepc-ubuntu NetworkManager: <debug> [1241692796.004286] nm_serial_debug(): Sending: 'AT+CFUN=1 '
May 7 19:39:56 eeepc-ubuntu NetworkManager: <debug> [1241692796.026087] nm_serial_debug(): Got: ' OK '
May 7 19:39:56 eeepc-ubuntu NetworkManager: <debug> [1241692796.026278] nm_serial_debug(): Sending: 'AT+CGMM '
May 7 19:39:56 eeepc-ubuntu NetworkManager: <debug> [1241692796.044084] nm_serial_debug(): Got: ' D02HW OK '
May 7 19:39:56 eeepc-ubuntu NetworkManager: <debug> [1241692796.044362] nm_serial_debug(): Sending: 'AT+CREG? '
May 7 19:39:56 eeepc-ubuntu NetworkManager: <debug> [1241692796.064042] nm_serial_debug(): Got: ' +CREG: 0,0 OK '

('AT+CREG?' result ' +CREG: 0,0 OK ' continues 15 times)

May 7 19:40:11 eeepc-ubuntu NetworkManager: <WARN> automatic_registration_response(): Automatic registration failed: not registered and not searching.

If I enter the 'AT+CGREG?' manually, it returns '+CGREG: 0,1 OK'
I think "priv->needs_cgreg" value have to be "true" (nm-gsm-device.c line 456)

Revision history for this message
sunatomo (naiyu) wrote :

I'd modified the nm-gsm-device.c and checked this modem works well.

Here is my modified point (nm-gsm-device.c diff result).

$diff nm-gsm-device.c.old nm-gsm-device.c
489a490
> case 4: /* Huawei E220 (Known as D02HW) */
 507c508
< const char *responses[] = { "E160G", "F3507g", "D5530", "MD300", NULL };
---
> const char *responses[] = { "E160G", "F3507g", "D5530", "MD300", "D02HW", NULL };

Are threre any auto-detect method for select the best setting to toggle for "AT+CREG" and "AT+CGREG" ?
If there are no method, we have to add the each modem's "AT+CGMM" reply-result to nm-gsm-device.c, to use the "AT+CGREG".

Jun Kobayashi (jkbys)
Changed in network-manager (Ubuntu):
status: Incomplete → New
sunatomo (naiyu)
description: updated
summary: - CDMA modem don't answer the correct command set
+ D02HW (HuaweiE220 OEM product) modem doesn't answer the GSM command set
summary: - D02HW (HuaweiE220 OEM product) modem doesn't answer the GSM command set
+ D02HW (HuaweiE220 OEM product) modem doesn't answer the GPRS(HSDPA)
+ command set
Revision history for this message
ironstorm (ironstorm-gmail) wrote :

Hi, I'm in Japan atm and I rented one of these modems, fortunately I was able to get it working by downloading gnome-ppp on my hotel connection.

But I'm wondering if this is fixed in Karmic Network Manager packages?

Revision history for this message
Rolf Leggewie (r0lf) wrote :

I believe the situation for emobile-branded Huawei E220 has gotten even worse. I cannot connect with lucid gnome-ppp, pon or network-manager at all. Connection with karmic gnome-ppp was still fine. I reported this regression as bug 574192). Please share your experiences.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

sunatomo, what is your current status on this bug? FWIW, my experiences in bug 574192 are still unchanged.

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

Other bug subscribers

Remote bug watches

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