Page 3 of 12 FirstFirst 12345 ... LastLast
Results 21 to 30 of 119

Thread: Howto: Connect ZTE MF627 3G modem with NM0.7

  1. #21
    Join Date
    Dec 2007
    Beans
    8

    Re: Howto: Connect ZTE MF627 3G modem with NM0.7

    BrinX, can you post a dmesg and /var/log/syslog excerpt?


    Anyone having any luck on jaunty? I have 3 UK MF627. I've installed udev-extras, but I don't think it's kicking in.

    dmesg says this:
    Code:
    [40732.620069] usb 1-1: new high speed USB device using ehci_hcd and address 3
    [40732.768214] usb 1-1: configuration #1 chosen from 1 choice
    [40732.954729] Initializing USB Mass Storage driver...
    [40732.965516] usb-storage: device ignored
    [40732.965639] usbcore: registered new interface driver usb-storage
    [40732.965650] USB Mass Storage support registered.
    and lsusb has it as a mass storage device (with no name supplied by Linux in the first line, as is usual):

    Code:
    $ sudo lsusb -v
    Bus 001 Device 003: ID 19d2:2000  
    Device Descriptor:
      bLength                18
      bDescriptorType         1
      bcdUSB               2.00
      bDeviceClass            0 (Defined at Interface level)
      bDeviceSubClass         0 
      bDeviceProtocol         0 
      bMaxPacketSize0        64
      idVendor           0x19d2 
      idProduct          0x2000 
      bcdDevice            0.00
      iManufacturer           2 ZTE,Incorporated
      iProduct                1 ZTE CDMA Technologies MSM
      iSerial                 0 
      bNumConfigurations      1
      Configuration Descriptor:
        bLength                 9
        bDescriptorType         2
        wTotalLength           32
        bNumInterfaces          1
        bConfigurationValue     1
        iConfiguration          0 
        bmAttributes         0xe0
          Self Powered
          Remote Wakeup
        MaxPower              500mA
        Interface Descriptor:
          bLength                 9
          bDescriptorType         4
          bInterfaceNumber        0
          bAlternateSetting       0
          bNumEndpoints           2
          bInterfaceClass         8 Mass Storage
          bInterfaceSubClass      6 SCSI
          bInterfaceProtocol     80 Bulk (Zip)
          iInterface              0 
          Endpoint Descriptor:
            bLength                 7
            bDescriptorType         5
            bEndpointAddress     0x01  EP 1 OUT
            bmAttributes            2
              Transfer Type            Bulk
              Synch Type               None
              Usage Type               Data
            wMaxPacketSize     0x0200  1x 512 bytes
            bInterval               0
          Endpoint Descriptor:
            bLength                 7
            bDescriptorType         5
            bEndpointAddress     0x81  EP 1 IN
            bmAttributes            2
              Transfer Type            Bulk
              Synch Type               None
              Usage Type               Data
            wMaxPacketSize     0x0200  1x 512 bytes
            bInterval               0
    Device Qualifier (for other device speed):
      bLength                10
      bDescriptorType         6
      bcdUSB               2.00
      bDeviceClass            0 (Defined at Interface level)
      bDeviceSubClass         0 
      bDeviceProtocol         0 
      bMaxPacketSize0        64
      bNumConfigurations      1
    Device Status:     0x0001
      Self Powered
    But nothing else happens. As it says 'device ignored' I can't get at the mass storage volume.

    I tried grabbing the usb_modeswitch config from http://www.greenhughes.com/content/zte-mf627-easy-way
    and trying to 'flip' it manually:

    Code:
    $ sudo usb_modeswitch -c /etc/usb_modeswitch_zte_mf627.conf 
    
     * usb_modeswitch: tool for controlling "flip flop" mode USB devices
     * Version 0.9.7 (C) Josua Dietze 2009
     * Works with libusb 0.1.12 and probably other versions
    
    Looking for target devices ...
     No devices in target mode or class found
    Looking for default devices ...
     Found default devices (1)
    Prepare switching, accessing device 003 on bus 001 ...
    Looking for active driver ...
     No driver found. Either detached before or never attached
    Setting up communication with interface 0 ...
    Trying to send the message to endpoint 0x01 ...
     Sending the message returned error -110. Trying to continue
    -> Run lsusb to note any changes. Bye
    No change there. Error -110 is ETIMEOUT.

    I had a poke around the kernel source - in drivers/usb/storage/unusual_devs.h the device is listed:
    Code:
    UNUSUAL_DEV(  0x19d2, 0x2000, 0x0000, 0x0000,
                    "Onda ET502HS",
                    "USB MMC Storage",
                    US_SC_DEVICE, US_PR_DEVICE, NULL,
                    US_FL_IGNORE_DEVICE),
    That's what's causing the 'device ignored' messages. But it's slightly odd that the name at least isn't showing in lsusb.

    Do I have to recompile my kernel without this entry?

  2. #22
    Join Date
    May 2006
    Beans
    24

    Re: Howto: Connect ZTE MF627 3G modem with NM0.7

    Quote Originally Posted by CCK View Post
    See if I can explain how I got my Austrlian version MF627 USB key working on my 2 laptops (dell and hp) with ubuntu 8.10.

    Firstly you should have got the usb_modeswitch in http://www.draisberghof.de/usb_modeswitch/#download as mentioned in previous post.

    Then backup your /etc/usb_modeswitch.conf somewhere - your home directory as an example.

    Now replace your /etc/usb_modeswitch.conf with the following content:

    Code:
    ########################################################
    # ZTE MF628+ (tested version from Telia / Sweden) 
    # ZTE MF626 
    # 
    # Contributor: Joakim Wennergren
    
    DefaultVendor=  0x19d2
    DefaultProduct= 0x2000
    
    TargetVendor=   0x19d2
    TargetProduct=  0x0064
    
    MessageEndpoint=0x01
    MessageContent="55534243123456782000000080000c85010101180101010101000000000000"
    Now create a file /etc/udev/rules.d/999-zte.rules with the following content:
    Code:
    SUBSYSTEM=="usb", SYSFS{idProduct}=="2000", SYSFS{idVendor}=="19d2", RUN +="/usr/sbin/usb_modeswitch"
    SUBSYSTEM=="usb", SYSFS{idProduct}=="0064", SYSFS{idVendor}=="19d2", RUN +="/sbin/modprobe usbserial vendor=0x19d2 product=0x0064"
    For the above file there were a couple of typo - please check my follow up post.

    Then create a file /usr/share/hal/fdi/information/20thirdparty/20-zte-mf627.fdi with the following content:

    Code:
    <!-- -*- SGML -*- -->
    <deviceinfo version="0.2">
    <device>
    <!-- ZTE MF627 HSDPA USB dongle -->
    <match key="@info.parent:usb.vendor_id" int="0x19d2">
    <match key="@info.parent:usb.product_id" int="0x0064">
    <match key="@info.parent:usb.interface.number" int="2">
    <append key="modem.command_sets" type="strlist">GSM-07.07</append>
    <append key="modem.command_sets" type="strlist">GSM-07.05</append>
    <append key="info.capabilities" type="strlist">modem</append>
    </match>
    </match>
    </match>
    </device>
    </deviceinfo>
    Plug in your USB modem now. Around 5 to 10 seconds later "do lsusb" to check the output. There should be a line with some entry like "ID 19d2:0064" after around 5 to 10 seconds. This means that your udev rules together with usb_modeswitch is working.

    Do a ls -l /dev/ttyUSB0 and ls -l /dev/ttyUSB1. You should see those entries.

    By this time if you are alreday logged in to gnome you may see network manager prompt you on entering mobile broadbank setup for the detected modem.
    Works brilliantly, thank you.

    Seems so much faster than my E220 which i have been using.

  3. #23
    Join Date
    May 2006
    Beans
    24

    Re: Howto: Connect ZTE MF627 3G modem with NM0.7

    Quote Originally Posted by caliston View Post
    BrinX, can you post a dmesg and /var/log/syslog excerpt?


    Anyone having any luck on jaunty? I have 3 UK MF627. I've installed udev-extras, but I don't think it's kicking in.

    dmesg says this:
    Code:
    [40732.620069] usb 1-1: new high speed USB device using ehci_hcd and address 3
    [40732.768214] usb 1-1: configuration #1 chosen from 1 choice
    [40732.954729] Initializing USB Mass Storage driver...
    [40732.965516] usb-storage: device ignored
    [40732.965639] usbcore: registered new interface driver usb-storage
    [40732.965650] USB Mass Storage support registered.
    and lsusb has it as a mass storage device (with no name supplied by Linux in the first line, as is usual):

    Code:
    $ sudo lsusb -v
    Bus 001 Device 003: ID 19d2:2000  
    Device Descriptor:
      bLength                18
      bDescriptorType         1
      bcdUSB               2.00
      bDeviceClass            0 (Defined at Interface level)
      bDeviceSubClass         0 
      bDeviceProtocol         0 
      bMaxPacketSize0        64
      idVendor           0x19d2 
      idProduct          0x2000 
      bcdDevice            0.00
      iManufacturer           2 ZTE,Incorporated
      iProduct                1 ZTE CDMA Technologies MSM
      iSerial                 0 
      bNumConfigurations      1
      Configuration Descriptor:
        bLength                 9
        bDescriptorType         2
        wTotalLength           32
        bNumInterfaces          1
        bConfigurationValue     1
        iConfiguration          0 
        bmAttributes         0xe0
          Self Powered
          Remote Wakeup
        MaxPower              500mA
        Interface Descriptor:
          bLength                 9
          bDescriptorType         4
          bInterfaceNumber        0
          bAlternateSetting       0
          bNumEndpoints           2
          bInterfaceClass         8 Mass Storage
          bInterfaceSubClass      6 SCSI
          bInterfaceProtocol     80 Bulk (Zip)
          iInterface              0 
          Endpoint Descriptor:
            bLength                 7
            bDescriptorType         5
            bEndpointAddress     0x01  EP 1 OUT
            bmAttributes            2
              Transfer Type            Bulk
              Synch Type               None
              Usage Type               Data
            wMaxPacketSize     0x0200  1x 512 bytes
            bInterval               0
          Endpoint Descriptor:
            bLength                 7
            bDescriptorType         5
            bEndpointAddress     0x81  EP 1 IN
            bmAttributes            2
              Transfer Type            Bulk
              Synch Type               None
              Usage Type               Data
            wMaxPacketSize     0x0200  1x 512 bytes
            bInterval               0
    Device Qualifier (for other device speed):
      bLength                10
      bDescriptorType         6
      bcdUSB               2.00
      bDeviceClass            0 (Defined at Interface level)
      bDeviceSubClass         0 
      bDeviceProtocol         0 
      bMaxPacketSize0        64
      bNumConfigurations      1
    Device Status:     0x0001
      Self Powered
    But nothing else happens. As it says 'device ignored' I can't get at the mass storage volume.

    I tried grabbing the usb_modeswitch config from http://www.greenhughes.com/content/zte-mf627-easy-way
    and trying to 'flip' it manually:

    Code:
    $ sudo usb_modeswitch -c /etc/usb_modeswitch_zte_mf627.conf 
    
     * usb_modeswitch: tool for controlling "flip flop" mode USB devices
     * Version 0.9.7 (C) Josua Dietze 2009
     * Works with libusb 0.1.12 and probably other versions
    
    Looking for target devices ...
     No devices in target mode or class found
    Looking for default devices ...
     Found default devices (1)
    Prepare switching, accessing device 003 on bus 001 ...
    Looking for active driver ...
     No driver found. Either detached before or never attached
    Setting up communication with interface 0 ...
    Trying to send the message to endpoint 0x01 ...
     Sending the message returned error -110. Trying to continue
    -> Run lsusb to note any changes. Bye
    No change there. Error -110 is ETIMEOUT.

    I had a poke around the kernel source - in drivers/usb/storage/unusual_devs.h the device is listed:
    Code:
    UNUSUAL_DEV(  0x19d2, 0x2000, 0x0000, 0x0000,
                    "Onda ET502HS",
                    "USB MMC Storage",
                    US_SC_DEVICE, US_PR_DEVICE, NULL,
                    US_FL_IGNORE_DEVICE),
    That's what's causing the 'device ignored' messages. But it's slightly odd that the name at least isn't showing in lsusb.

    Do I have to recompile my kernel without this entry?
    Got mine going in Jaunty, udev-extras did not seem to do anything so i followed CCk's instructions and i am using it now.

    Checking lsusb does not give a description of the device, but if you check dmesg you should see "usb 2-5: GSM modem (1-port) converter now attached to ttyUSB0" it's actually there 3 times but at least it is working.
    Last edited by Meads; May 28th, 2009 at 12:49 PM.

  4. #24
    Join Date
    Dec 2007
    Beans
    8

    Re: Howto: Connect ZTE MF627 3G modem with NM0.7

    I had another go. I installed the kernel from karmic (2.6.30-5-generic) and was able to see the /dev/ttyUSB0 device in the log:

    Code:
    kernel: [  570.520055] usb 1-1: new high speed USB device using ehci_hcd and address 5
    kernel: [  570.666039] usb 1-1: configuration #1 chosen from 1 choice
    kernel: [  570.668743] option 1-1:1.0: GSM modem (1-port) converter detected
    kernel: [  570.668930] usb 1-1: GSM modem (1-port) converter now attached to ttyUSB0
    kernel: [  570.752362] option1 ttyUSB0: GSM modem (1-port) converter now disconnected from ttyUSB0
    kernel: [  570.752409] option 1-1:1.0: device disconnected
    I think this was an interaction with udev. I killed udev and hal and managed to get the /dev/ttyUSB0 device to stay up, but I couldn't get any sense out of it with minicom. The syslog does suggest NetworkManager was interacting with the device on one occasion (not when I tried minicom, as I had no X)

    But having broken the nvidia video driver by forcing a karmic kernel on top of jaunty, it was not very usable so I had to drop back to the jaunty standard kernel (2.6.28-11-generic, as used in my previous post).

    I also tried some USB diagnostic programs: usb-robot and usbreset. I got somewhere with these - tried to send the USB modeswitch packet by hand - it didn't complain, but I wasn't able to reset the device properly to make Linux spot that it had flipped mode. I did get a -2 error from usb_modeswitch afterwards which matches the error in the troubleshooting section of the usb_modeswitch page for MF626 (the answer: rebuild the kernel without the unusual_devs.h entry. Not tried that yet).

    The Russian Gentoo thread linked to on the usb_modeswitch page ((Google English translation) has some other things to try, including killing the ZeroCD function permanently. Perhaps I'd be best trying to rebuild my usb_storage module as a start.
    Last edited by caliston; May 28th, 2009 at 01:31 PM.

  5. #25
    Join Date
    Sep 2007
    Beans
    41
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Howto: Connect ZTE MF627 3G modem with NM0.7

    Quote Originally Posted by caliston View Post
    Anyone having any luck on jaunty? I have 3 UK MF627. I've installed udev-extras, but I don't think it's kicking in.
    Hi caliston,

    I'm also trying to get an MF637 from 3 UK working. I'm having the exact same problem as you. I have installed udev-extras, but I'm not even getting it mounted as a drive.

    Anyone in the UK on Jaunty getting it to work?

    Cheers,
    AJ

  6. #26
    Join Date
    Sep 2007
    Beans
    41
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Howto: Connect ZTE MF627 3G modem with NM0.7

    I'm getting much closer ...
    Since the udev-extras tip didn't work for me, I went back to jfernyhough's original post.
    Now, I see the 3Connect icon on the desktop, and unmount it.

    Here's where it goes a little funny. If I click on Network Manager, I see
    "Mobile Broadband (ZTE Incorporated ZTE CDMA Technologies MSM), along with three choices: two for O2 (which I had working with a different phone with an O2 SIM) and one for 3, with I added manually in NetworkManager under the "Edit Connections" option.

    If I look at the options for 3, all I have is
    Number = *99#
    APN = 3internet

    This is different from the O2 settings, which also include username and password, and the APN is mobile.o2.co.uk

    Are there any changes I should have here?

    Otherwise, when I try to connect to "3", I get the swirling connection icon followed by the message "GSM Network Disconnected - You are now offline"

    I should be in a 3G coverage area for 3 (I'm going to pop the SIM into a 3G phone next to verify), but according to 3's coverage maps, I should be fine.

    Cheers,
    AJ

  7. #27
    Join Date
    Sep 2007
    Beans
    41
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Howto: Connect ZTE MF627 3G modem with NM0.7

    I've confirmed via a handset that I'm getting a 3G signal from 3 at my house.

    Update: I've tried the dongle with a Win2K laptop, and it worked fine. So the dongle and my coverage are ok. It's my Ubuntu setup that still needs tweaking then.
    Last edited by amj; May 31st, 2009 at 06:09 AM.

  8. #28
    Join Date
    Sep 2007
    Beans
    41
    Distro
    Ubuntu 10.10 Maverick Meerkat

    Re: Howto: Connect ZTE MF627 3G modem with NM0.7

    I decided to delete all the Mobile Broadband connections (O2 and 3), reboot, and plug in again. When I did that, the modem was detected, and the broadband setup app popped up. I selected 3, and took the defaults.
    Same result ... tries to connect, but then disconnects. Oddly, there are two lines for selecting 3.

    I'm wondering if the fact that two connections are being listed is part of the problem. I've tried three ways to set up:
    - the udev-extras method
    - the shell script on the USB stick
    - the original method as outlined in this thread.

    I wonder if I have two slightly different modems set up as a result.
    Please advise which files I can post here to analyse?

    Cheers,
    AJ
    Attached Images Attached Images

  9. #29
    Join Date
    Jun 2009
    Beans
    12
    Distro
    Ubuntu 10.04 Lucid Lynx

    Swirling but not connecting

    I notice a few people having the same symptoms as my system:

    • eee-pc 901


    • Stock 9.04 Jaunty


    • Network Manager 0.7.0.100

    I had already disabled the auto-run on the MF627 by sticking it in a Windows machine, and sending it an AT+ZCDRUN=8 command. I had also used the Network Manager "wizard" to create a connection for Three UK.

    However, when I tried to connect, it had that endless swirling, followed by "You are disconnected" message.

    I dropped it into Gnome Dialler (which is basically a GUI for wvdial), and looked at the log. What it was showing as a connection happening (via ttyUSB2) and then pppd was failing to start correctly. (That's odd, as I use Gnome Dialler to connect to Orange 3G via Bluetooth and a Nokia N95, and it's fine for that - using /dev/rfcomm0 as a port).

    What fixed it for me was setting pppd to setuid to root, so that it always runs with root privs. That involved doing a:

    Code:
    sudo chmod +s /usr/sbin/pppd
    Now it connects fine. No idea *what* it is that's requiring root level to operate, and I haven't the patience to try going through everything.

    However I am also seeing the problem of the device just disappearing randomly, and needing replugging. Would love to see a fix for that one.

  10. #30
    Join Date
    Aug 2008
    Location
    Athens Greece
    Beans
    971
    Distro
    Ubuntu 12.04 Precise Pangolin

    Re: Howto: Connect ZTE MF627 3G modem with NM0.7

    Hi, I would like to add a note:
    ZTE modems when attached to the USB port, kernel/udev/hal (I don't know exactly) assigns at least 3 ports:
    /dev/ttyUSB0 /dev/ttyUSB1 /dev/ttyUSB2 (and sometimes /dev/ttyUSB3)
    assuming that there is NO other usbserial-ised peripheral. This behaviour is different if you boot with or without the modem attached.

    The usable port for data communication is the highest (2 or 3) and the highest minus 2 (0 or 2), resulting to a connection via /dev/ttyUSB0 or /dev/ttyUSB2 when there is no /dev/ttyUSB3. If the last one exists you must use /dev/ttyUSB1 or /dev/ttyUSB3!

    This is because the ZTE modems use other ports for firmware update or GPS interface and the designers choose this port numbering. The 2 usable ports are the one used for data (ppp) and the other used for telemetry (signal strength, volume of data traffic, etc).

    Huawei modems usually attached as 3 ports: /dev/ttyUSB0 /dev/ttyUSB1 /dev/ttyUSB2
    At Huawei modems the 2 first two (0,1) are for data and telemetry, both work to connect as with the ZTE but with the different numbering.

    Most developers have access to Huawei or "like Huawei" modems. That's why they have debugged them. We (users of ZTE modems) must provide specific info to developers to help them solve our bugs (including usb modeswitch or other "tricks"). A modem must be pluged in and go. Rarely the modem manufacturer supplies technical info to developers.

    In the case above where Network Manager assigns 2 set of provider, the possible good one is the last shown (2nd or 4th in my case!).

    Regards,
    George

    EDIT: info about "Using ZTE MF636 with various UBUNTU versions" at:
    http://www.acomelectronics.com/Georg...EonUBUNTU.html
    Last edited by GeorgeVita; June 7th, 2009 at 11:14 PM. Reason: link added

Page 3 of 12 FirstFirst 12345 ... LastLast

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •