Another Huawei E353 problem … usb_modeswitch not finding device



  • I have been struggeling with this all day and would really appreciate if someone could help me out here …

    First command below shows that VID=0x12d1 and PID=0x14fe, but then usb_modeswitch does not find those ID's and quits with "Nothing to do"

    I don't see any /dev/cu* devices ...

    [2.0.2-RELEASE][admin@pfsense.localdomain]/root/usb_switch(31): usbconfig -d 1.2 dump_device_desc
    ugen1.2: <huawei mobile="" huawei="">at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON

    bLength = 0x0012
      bDescriptorType = 0x0001
      bcdUSB = 0x0200
      bDeviceClass = 0x0000
      bDeviceSubClass = 0x0000
      bDeviceProtocol = 0x0000
      bMaxPacketSize0 = 0x0040
      idVendor = 0x12d1
      idProduct = 0x14fe
      bcdDevice = 0x0102
      iManufacturer = 0x0002  <huawei>iProduct = 0x0001  <huawei mobile="">iSerialNumber = 0x0000  <no string="">bNumConfigurations = 0x0001

    [2.0.2-RELEASE][admin@pfsense.localdomain]/root/usb_switch(49): usb_modeswitch -c e353.txt -W

    • usb_modeswitch: handle USB devices with multiple modes
    • Version 1.2.1 (C) Josua Dietze 2011
    • Based on libusb0 (0.1.12 and above)

    ! PLEASE REPORT NEW CONFIGURATIONS !

    DefaultVendor=  0x12d1
    DefaultProduct= 0x14fe
    TargetVendor=  0x12d1
    TargetProduct=  0x1506
    TargetClass=    not set
    TargetProductList=""

    DetachStorageOnly=0
    HuaweiMode=0
    SierraMode=0
    SonyMode=0
    QisdaMode=0
    GCTMode=0
    KobilMode=0
    SequansMode=0
    MobileActionMode=0
    CiscoMode=0
    MessageEndpoint=  not set
    MessageContent="55534243123456780000000000000011062000000100000000000000000000"
    NeedResponse=0
    ResponseEndpoint= not set

    InquireDevice enabled (default)
    Success check disabled
    System integration mode disabled

    Looking for target devices …
    No devices in target mode or class found
    Looking for default devices ...
    No devices in default mode found. Nothing to do. Bye.</no></huawei></huawei></huawei>



  • In Windoze the two ID's are VID 0x12d1, PID 0x14fe … and ... VID 0x12d1, PID 0x1506

    ... am I correct in assuming that this modem should then work fine in pfSense, since other people have reported success for VID 0x12d1, PID 0x1506 modems ... pr is it not that simple? Would two modems with the same VID, PID use the exact same driver or are there other factors?

    If it is already switched to the correct mode, why is it not showing a /dev/cu.. device?  Please help.



  • You might get a better result if you try using a snapshot build of pfSense 2.1 which has more up to date device drivers than pfSense 2.0.x. (pfSense 2.0.x is based on FreeBSD 8.1. pfSense 2.1 is based on FreeBSD 8.3.)



  • Thanks wallabybob!

    I now have the following under /dev
    [2.1-BETA1][admin@pfsense.localdomain]/root(6): ls /dev/cu*
    /dev/cuaU0      /dev/cuaU0.lock /dev/cuaU1.init /dev/cuaU2      /dev/cuaU2.lock
    /dev/cuaU0.init /dev/cuaU1      /dev/cuaU1.lock /dev/cuaU2.init

    … and have setup PPP interfaces, which actually go as far as to show me dBm and signal % values ... but under status>system logs the following is showing ...

    ppp: [opt1_link0] CHAT: +CGDCONT=1,"IP","internet"
    ppp: [opt1_link0] CHAT: Detected Hayes compatible modem.
    ppp: [opt1_link0] CHAT: The modem responded with "ERROR" to the command "AT&F&C1&D2E0S0=0M1" at ModemCmd: label.
    ppp: [opt1_link0] MODEM: chat script failed
    ppp: [opt1_link0] Link: DOWN event
    ppp: [opt1_link0] LCP: Down event

    … also ...

    [2.1-BETA1][admin@pfsense.localdomain]/root(8): usbconfig -d 1.2 dump_device_desc show_ifdrv
    ugen1.2: <huawei mobile="" huawei="">at usbus1, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON
    ugen1.2.0: umodem0: <huawei 0="" 2="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 1.02,="" addr="">ugen1.2.1: umodem1: <huawei 0="" 2="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 1.02,="" addr="">ugen1.2.2: umodem2: <huawei 0="" 2="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 1.02,="" addr="">ugen1.2.3: umass0: <huawei 0="" 2="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 1.02,="" addr="">ugen1.2.4: umass1: <huawei 0="" 2="" huawei="" mobile,="" class="" 0,="" rev="" 2.00="" 1.02,="" addr="">bLength = 0x0012
      bDescriptorType = 0x0001
      bcdUSB = 0x0200
      bDeviceClass = 0x0000
      bDeviceSubClass = 0x0000
      bDeviceProtocol = 0x0000
      bMaxPacketSize0 = 0x0040
      idVendor = 0x12d1
      idProduct = 0x1c05
      bcdDevice = 0x0102
      iManufacturer = 0x0002  <huawei>iProduct = 0x0001  <huawei mobile="">iSerialNumber = 0x0000  <no string="">bNumConfigurations = 0x0001

    … should umodem* not be u3g* in the above?

    Thanks again for the help, it at least feels like I'm getting somewhere.</no></huawei></huawei></huawei></huawei></huawei></huawei></huawei></huawei>


Locked