Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Sierra MC73xx working

    Scheduled Pinned Locked Moved
    Wireless
    13
    51
    33.4k
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • T
      tubs89
      last edited by

      How are you guys connecting the mPCIe card to a host?  Does a USB adapter work or do I need to find a mainboard that supports mPCIe to do these steps?

      1 Reply Last reply Reply Quote 0
      • T
        thanatos2k
        last edited by

        3g/4g modems almost all use the USB interface of Mini-PCI(e) so a USB adapter will work if you don't have a slot internally.

        "I know not with what weapons World War III will be fought, but World War IV will be fought with sticks and stones." - A. Einstein

        1 Reply Last reply Reply Quote 0
        • T
          tubs89
          last edited by

          @thanatos2k:

          3g/4g modems almost all use the USB interface of Mini-PCI(e) so a USB adapter will work if you don't have a slot internally.

          Thanks!

          1 Reply Last reply Reply Quote 0
          • T
            tubs89
            last edited by

            Thanks for these instructions!  I also followed this post to re-flash the firmware to Sprint: https://forum.pfsense.org/index.php?topic=120614.0.

            I had to run !BOOTHOLD via the AT interface prior to flashing the firmware to get the firmware to flash without an error.

            1 Reply Last reply Reply Quote 0
            • T
              tubs89
              last edited by

              I'm still having trouble - it appears the device is stuck in "Low Power Mode", similar to this post: https://sigquit.wordpress.com/2015/02/09/dell-branded-sierra-wireless-3g4g-modem-not-online/

              The output of !PCINFO:
              State: LowPowerMode
              LPM force flags - W_DISABLE:0, User:0, Temp:0, Volt:0, BIOS:1, GOBIIM:0
              W_DISABLE: 0
              Poweroff mode: 0
              LPM Persistent: 0

              Indicates the BIOS system is somehow converting the module to low power.  Googling reveals linux can do this with it's ACPI modules by accident/bug:
              https://lists.freedesktop.org/archives/libqmi-devel/2015-January/001084.html

              Anyone else struggling with this?

              1 Reply Last reply Reply Quote 0
              • T
                thanatos2k
                last edited by

                I've found with the DW5805 and DW5805e that even if you change the VID/PID to non-Dell configurations, they still need the FCC auth command to be sent before they will go out of low power mode. I've not found a way to send that command under FreeBSD. I'm currently using ModemManager on OpenWRT in a secondary atom box to do the 4G connections.

                "I know not with what weapons World War III will be fought, but World War IV will be fought with sticks and stones." - A. Einstein

                1 Reply Last reply Reply Quote 0
                • T
                  tubs89
                  last edited by

                  I think I found the key:
                  https://forum.sierrawireless.com/viewtopic.php?f=117&t=9771&sid=3c2d1cc46ccb965d2e37535a9ab142b1&start=15#p39184

                  The PCFCCAUTH can only be changed in a special mode with OPENLOCK command.  Trying to disable it via the AT console without OPENLOCK results in an error.

                  The older Sierra chips could be unlocked from here - https://github.com/bkerler/SierraWirelessGen.  But it sounds like the algorithm is updated.

                  I think there is a tool out there that let's you modify these settings outside the AT interface.  May be easier.

                  1 Reply Last reply Reply Quote 0
                  • M
                    meteora @Juancho1972
                    last edited by

                    @juancho1972 . can you upload the whole process? I am facing the same problem.

                    1 Reply Last reply Reply Quote 0
                    • F
                      fips @Juancho1972
                      last edited by

                      @juancho1972 Yes, please show the process.

                      1 Reply Last reply Reply Quote 0
                      • A
                        alexTM
                        last edited by stephenw10

                        So MC7355 and EM7355, which one is better to use with OpenWRT?

                        1 Reply Last reply Reply Quote 0
                        • stephenw10S
                          stephenw10 Netgate Administrator
                          last edited by

                          Hmm, seems like spam but...

                          That is the same card effectively. The MC version is mPCIe and the EM is m.2.

                          Steve

                          A 1 Reply Last reply Reply Quote 0
                          • A
                            alexTM @stephenw10
                            last edited by

                            @stephenw10 thanks

                            1 Reply Last reply Reply Quote 0
                            • M
                              mrneutron
                              last edited by mrneutron

                              Is anyone able to get this to work on a DW5808 (MC-7355) in 2020?
                              I've been following the procedure outlined by user FranciscoFranco in forum post #17.
                              I've experienced that the procedure does not work in 2020.
                              I tried to perform the process using Ubuntu 19.10 on a 8GB bootable USB flash drive with 2GB of persistent memory space. I also tried using a Ubuntu 19.10 Virtual Machine inside VMware Workstation. Both setups yielded the same failures.
                              One of the first steps is to run networkmanager and modemmanager in debug mode:
                              see https://www.freedesktop.org/wiki/Software/ModemManager/Debugging
                              $> sudo /usr/sbin/ModemManager --debug
                              This process fails to complete. The screen scrolls with text for about 1 minute then stops and never completes - even after waiting/watching for an hour. If you perform a CTRL-C to stop the command, it stops with a message that it failed.
                              Since this is one the first steps in the process, the rest cannot be accomplished.

                              1. has anyone been able to get this to work on a DW5808 (MC-7355) in 2020?
                              2. if not, why this would work in 2016 and not in 2020?
                              3. do I need to use a 2016 version of Ubuntu for this to work?

                              Thanks for any updates on this procedure.

                              1 Reply Last reply Reply Quote 0
                              • stephenw10S
                                stephenw10 Netgate Administrator
                                last edited by

                                Do you have the error it actually shows?

                                Did you try modprobing the serial driver onto the device?
                                https://forum.netgate.com/post/677772

                                M 1 Reply Last reply Reply Quote 0
                                • M
                                  mrneutron @stephenw10
                                  last edited by

                                  @stephenw10
                                  No, I didn't try any modprobe commands.

                                  from: sudo /usr/sbin/ModemManager --debug
                                  This is the last part of the output...says it didn't connect to the AT port and stops and waits, forever.

                                  ModemManager[5079]: <debug> [1595789997.248458] [plugin manager] task 0: min probing time elapsed
                                  ModemManager[5079]: <debug> [1595789997.248676] [plugin Manager] task 0: still 1 running probes (0 active): ens33
                                  ModemManager[5079]: <debug> [1595789997.248711] [plugin manager] task 0: no active tasks to probe
                                  ModemManager[5079]: <debug> [1595789997.248745] [plugin manager] task 0,ens33: deferred task completed, no suggested plugin
                                  ModemManager[5079]: <debug> [1595789997.248777] [plugin manager] task 0,ens33: finished in '2.502197' seconds
                                  ModemManager[5079]: <debug> [1595789997.248943] [plugin manager] task 0,ens33: not supported by any plugin
                                  ModemManager[5079]: <debug> [1595789997.248983] [device /sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0] fully ignoring port 'net/ens33' from now on
                                  ModemManager[5079]: <debug> [1595789997.249009] [plugin manager] task 0: no more ports to probe
                                  ModemManager[5079]: <debug> [1595789997.249028] [plugin manager] task 0: finished in '2.502562' seconds
                                  ModemManager[5079]: <info>  [1595789997.249077] Couldn't check support for device '/sys/devices/pci0000:00/0000:00:11.0/0000:02:01.0': not supported by any plugin
                                  ModemManager[5079]: <debug> [1595789997.249342] [plugin manager] task 1: min probing time elapsed
                                  ModemManager[5079]: <debug> [1595789997.249390] [plugin Manager] task 1: still 2 running probes (1 active): cdc-wdm0, wws35u1c2i12
                                  ModemManager[5079]: proxy configuration failed: closed
                                  ModemManager[5079]: <debug> [1595790026.390983] (usbmisc/cdc-wdm0) error checking MBIM support: 'Transaction timed out'
                                  ModemManager[5079]: <debug> [1595790026.391018] (usbmisc/cdc-wdm0) port is not MBIM-capable
                                  ModemManager[5079]: [/dev/cdc-wdm0] channel destroyed
                                  ModemManager[5079]: <debug> [1595790026.391300] [plugin manager] task 1,cdc-wdm0: found best plugin for port (Dell)
                                  ModemManager[5079]: <debug> [1595790026.391498] [plugin manager] task 1,cdc-wdm0: finished in '31.644019' seconds
                                  ModemManager[5079]: <debug> [1595790026.391536] [plugin manager] task 1,cdc-wdm0: found best plugin: Dell
                                  ModemManager[5079]: <debug> [1595790026.391557] [plugin manager] task 1,wws35u1c2i12: deferred task completed, got suggested plugin (Dell)
                                  ModemManager[5079]: <debug> [1595790026.391586] [plugin Manager] task 1: still 1 running probes (1 active): wws35u1c2i12
                                  ModemManager[5079]: <debug> [1595790026.391663] [plugin manager] task 1,wws35u1c2i12: checking with plugin 'Dell'
                                  ModemManager[5079]: <debug> [1595790026.391712] (Dell) [wws35u1c2i12] probing deferred until result suggested
                                  ModemManager[5079]: <debug> [1595790026.391748] [plugin manager] task 1,wws35u1c2i12: completed, got suggested plugin (Dell)
                                  ModemManager[5079]: <debug> [1595790026.391768] [plugin manager] task 1,wws35u1c2i12: finished in '31.644749' seconds
                                  ModemManager[5079]: <debug> [1595790026.391792] [plugin manager] task 1,wws35u1c2i12: best plugin matches device reported one: Dell
                                  ModemManager[5079]: <debug> [1595790026.391810] [plugin manager] task 1: no more ports to probe
                                  ModemManager[5079]: <debug> [1595790026.391827] [plugin manager] task 1: finished in '31.644885' seconds
                                  ModemManager[5079]: <info>  [1595790026.391870] [device /sys/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb1/1-1] creating modem with plugin 'Dell' and '2' ports
                                  ModemManager[5079]: <debug> [1595790026.391934] Dell-branded generic modem found...
                                  ModemManager[5079]: <warn>  [1595790026.399711] Could not grab port (usbmisc/cdc-wdm0): 'Cannot add port 'usbmisc/cdc-wdm0', unsupported'
                                  ModemManager[5079]: <debug> [1595790026.400072] (wws35u1c2i12) type 'net' claimed by /sys/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb1/1-1
                                  ModemManager[5079]: <debug> [1595790026.400336] Modem (Dell) '/sys/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb1/1-1' completely disposed
                                  ModemManager[5079]: <warn>  [1595790026.401515] Couldn't create modem for device '/sys/devices/pci0000:00/0000:00:11.0/0000:02:03.0/usb1/1-1': Failed to find primary AT port

                                  Then I did a CTRL-C

                                  ^CModemManager[5079]: <info>  [1595790115.488383] Caught signal, shutting down...
                                  ModemManager[5079]: <debug> [1595790115.488753] Stopping connection in object manager server
                                  ModemManager[5079]: <info>  [1595790115.497328] ModemManager is shut down
                                  ModemManager[5079]: <debug> [1595790115.497632] disposing MMSleepMonitor singleton (0x5614725aba90)
                                  ModemManager[5079]: <debug> [1595790115.497964] [sleep-monitor] dropping systemd sleep inhibitor
                                  eric@ubuntu-vm:~$ ^C
                                  eric@ubuntu-vm:~$

                                  1 Reply Last reply Reply Quote 0
                                  • stephenw10S
                                    stephenw10 Netgate Administrator
                                    last edited by

                                    I assume you stopped and disabled modem manager before that?

                                    You need to access an AT port somehow. If that cannot be done in Ubuntu it's probably possible in Windows.

                                    Steve

                                    M 1 Reply Last reply Reply Quote 0
                                    • M
                                      mrneutron @stephenw10
                                      last edited by

                                      @stephenw10 Yes, from reading this thread, I can tell that getting AT command access is crucial to changing the PID and VID numbers.
                                      Yes, I followed the documented process, and disabled and stopped the processes noted. But, since command 3 fails, I can't go on to command 4.
                                      sudo systemctl disable NetworkManager ModemManager
                                      sudo systemctl stop NetworkManager ModemManager
                                      sudo /usr/sbin/ModemManager --debug
                                      sudo /usr/sbin/NetworkManager --debug --log-level=DEBUG

                                      I just tried the modprobe lines. 1 gave an error. I tried starting ModemManager in debug mode after entering these 4 lines...no difference.
                                      eric@ubuntu-vm:~$ /sbin/modprobe cdc_wdm product=0x81a8 vendor=0x1199
                                      eric@ubuntu-vm:~$ /sbin/modprobe usbserial product=0x81a8 vendor=0x1199
                                      eric@ubuntu-vm:~$ /sbin/modprobe qmi_wwan product=0x81a8 vendor=0x1199
                                      modprobe: ERROR: could not insert 'qmi_wwan': Operation not permitted
                                      eric@ubuntu-vm:~$ /sbin/modprobe qcserial product=0x81a8 vendor=0x1199
                                      eric@ubuntu-vm:~$

                                      Given that the documented procedure doesn't work in Ubuntu 19.10, I have to guess:

                                      1. the procedure was not documented completely/accurately back in 2016
                                      2. the 2019 versions of software in the Ubuntu apt repository are not compatible with this procedure
                                      1 Reply Last reply Reply Quote 0
                                      • M
                                        mrneutron
                                        last edited by

                                        Here's the output of the perl script.
                                        eric@ubuntu-vm:~$ sudo perl swi_setusbcomp.pl -usbcomp=14
                                        Running in MBIM mode (driver=cdc_mbim)
                                        MBIM OPEN succeeded
                                        QMI msg '0x0021' returned status = 1
                                        MBIM QMI support verified
                                        supports 26 QMI subsystems:
                                        0x00 (1.5) 'QMI_CTL' - Control service
                                        0x01 (1.36) 'QMI_WDS' - Wireless data service
                                        0x02 (1.14) 'QMI_DMS' - Device management service
                                        0x03 (1.25) 'QMI_NAS' - Network access service
                                        0x04 (1.3) 'QMI_QOS' - Quality of service, err, service
                                        0x05 (1.10) 'QMI_WMS' - Wireless messaging service
                                        0x06 (1.0) 'QMI_PDS' - Position determination service
                                        0x07 (1.2) 'QMI_AUTH' - Authentication service
                                        0x08 (1.2) 'QMI_AT' - AT command processor service
                                        0x09 (2.1) 'QMI_VOICE' - Voice service
                                        0x0a (2.16) 'QMI_CAT2' - Card application toolkit service (new)
                                        0x0b (1.25) 'QMI_UIM' - UIM service
                                        0x0c (1.4) 'QMI_PBM' - Phonebook service
                                        0x11 (1.0) 'QMI_SAR' - Specific absorption rate service
                                        0x12 (1.0) 'QMI_IMSS' - IMS settings service
                                        0x17 (1.0) 'QMI_TS' - Thermal sensors service
                                        0x18 (1.0) 'QMI_TMD' - Thermal mitigation device service
                                        0x1a (1.10) 'QMI_WDA' - Wireless data administrative service
                                        0x1d (1.0) 'QMI_CSVT' - Circuit switched videotelephony service
                                        0x1e (1.0) 'QMI_QCMAP' - Qualcomm mobile access point service
                                        0x1f (1.0) 'QMI_IMSP' - IMS presence service
                                        0x20 (1.0) 'QMI_IMSVT' - IMS videotelephony service
                                        0x22 (1.0) 'QMI_COEX' - Coexistence service
                                        0x29 (1.0) 'QMI_RFRPE' - RF radiated performance enhancement service
                                        0xe1 (1.0) 'QMI_RMS' - Remote management service
                                        0xf0 (1.0) 'unknown' -
                                        QMI msg '0x0022' returned status = 1
                                        Got QMI DMS client ID '44'
                                        QMI msg '0x555b' returned status = 1
                                        Current USB composition: 14
                                        USB compositions:
                                        0 - HIP DM NMEA AT MDM1 MDM2 MDM3 MS NOT SUPPORTED
                                        1 - HIP DM NMEA AT MDM1 MS SUPPORTED
                                        2 - HIP DM NMEA AT NIC1 MS NOT SUPPORTED
                                        3 - HIP DM NMEA AT MDM1 NIC1 MS NOT SUPPORTED
                                        4 - HIP DM NMEA AT NIC1 NIC2 NIC3 MS NOT SUPPORTED
                                        5 - HIP DM NMEA AT ECM1 MS NOT SUPPORTED
                                        6 - DM NMEA AT QMI SUPPORTED
                                        7 - DM NMEA AT RMNET1 RMNET2 RMNET3 SUPPORTED
                                        8 - DM NMEA AT MBIM SUPPORTED
                                        9 - MBIM SUPPORTED
                                        10 - NMEA MBIM SUPPORTED
                                        11 - DM MBIM SUPPORTED
                                        12 - DM NMEA MBIM SUPPORTED
                                        13 - Config1: comp6 Config2: comp8 NOT SUPPORTED

                                        • 14 - Config1: comp6 Config2: comp9 SUPPORTED
                                          15 - Config1: comp6 Config2: comp10 NOT SUPPORTED
                                          16 - Config1: comp6 Config2: comp11 NOT SUPPORTED
                                          17 - Config1: comp6 Config2: comp12 NOT SUPPORTED
                                          18 - Config1: comp7 Config2: comp8 NOT SUPPORTED
                                          19 - Config1: comp7 Config2: comp9 SUPPORTED
                                          20 - Config1: comp7 Config2: comp10 NOT SUPPORTED
                                          21 - Config1: comp7 Config2: comp11 NOT SUPPORTED
                                          22 - Config1: comp7 Config2: comp12 NOT SUPPORTED
                                          Current setting is already '14'
                                          QMI msg '0x0023' returned status = 1
                                        1 Reply Last reply Reply Quote 0
                                        • stephenw10S
                                          stephenw10 Netgate Administrator
                                          last edited by

                                          Hmm, well if it can read that and is in composition 14 then you should be able to get an AT port.

                                          You might have to change the current config index to 6 if it's 9.

                                          What does lsusb -d 413C -v show.

                                          Also it looks like you loaded the usbserial driver using Sierra vendor and product ID. You need to use the current values so it attaches. So I assume?:
                                          modprobe usbserial product=0x818A vendor=0x413C

                                          Steve

                                          M 1 Reply Last reply Reply Quote 0
                                          • M
                                            mrneutron @stephenw10
                                            last edited by

                                            @stephenw10 that command line doesn't show us anything.

                                            eric@ubuntu-vm:~$ lsusb -d 413C -v
                                            Usage: lsusb [options]...
                                            List USB devices
                                            -v, --verbose
                                            Increase verbosity (show descriptors)
                                            -s [[bus]:][devnum]
                                            Show only devices with specified device and/or
                                            bus numbers (in decimal)
                                            -d vendor:[product]
                                            Show only devices with the specified vendor and
                                            product ID numbers (in hexadecimal)
                                            -D device
                                            Selects which device lsusb will examine
                                            -t, --tree
                                            Dump the physical USB device hierarchy as a tree
                                            -V, --version
                                            Show version of program
                                            -h, --help
                                            Show usage and help
                                            eric@ubuntu-vm:~$

                                            From what I read in this thread, the problem is that the driver for the standard Sierra Wireless 7355 is linked to a differen PID and VID, so the driver won't connect with the Dell version of the 7355.
                                            And, since the Dell version has no AT serial port, you can't sent it a command to change teh PID VID.

                                            Also from the tread, MBIM is supported. I believe that is an alternate port to send AT commands to? Someone posted that you can configure PUTTY to send commands to the MBIM port, but I'm not sure what port or BAUD rate to set, because they didn't list the specifics.

                                            Its not clear how they got this to work in 2016, and it doesn't seem to work in 2020....

                                            1 Reply Last reply Reply Quote 0
                                            • First post
                                              Last post