Navigation

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

    Sierra MC73xx working

    Wireless
    11
    48
    24571
    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.
    • 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
        • stephenw10
          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
              • stephenw10
                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
                  • stephenw10
                    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
                        • stephenw10
                          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
                            • stephenw10
                              stephenw10 Netgate Administrator last edited by

                              What device and product ID is it showing now?

                              Did you try modprobing the usb serial driver using those values?

                              Steve

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

                                @stephenw10 said in Sierra MC73xx working:

                                What device and product ID is it showing now?

                                Same Dell custom IDs, as before. VID: 0x413C , PID: 81A8

                                Did you try modprobing the usb serial driver using those values?

                                Yes. I tried that several posts back. Remember, one of the modprobe commands gave me an error?
                                Later, I tried all 4 of the modprobe commands with sudo at the start.
                                With sudo, I didn't get errors, but it didn't help...same lack of functionality.

                                I just got a standard MC7355 card and it shows the desired VID: 0x1199. PID: 0x9041 IDs.

                                I'm going to give up on that horrible Dell Wireless card.
                                I don't need an impossible puzzle.

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

                                  Right but the output you posted here showed the wrong vendor ID:

                                  eric@ubuntu-vm:~$ /sbin/modprobe usbserial product=0x81a8 vendor=0x1199

                                  You would need to modprobe against the current IDs to get a com port and then switch it.
                                  If you tried that and it still didn't work I would probably be trying to do it Windows if you decide have another go at it. Otherwise the factory card should work far more easily.

                                  Steve

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

                                    @stephenw10,
                                    So, are you saying the modprobe lines should be?

                                    $ sudo /sbin/modprobe cdc_wdm product=0x81a8 vendor=0x413c
$ sudo /sbin/modprobe usbserial product=0x81a8 vendor=0x413c
$ sudo /sbin/modprobe qmi_wwan product=0x81a8 vendor=0x413c
$ sudo /sbin/modprobe qcserial product=0x81a8 vendor=0x413c
                                    1 Reply Last reply Reply Quote 0
                                    • stephenw10
                                      stephenw10 Netgate Administrator last edited by

                                      Yes exactly, you are telling the driver to attach to that specific device.

                                      K 1 Reply Last reply Reply Quote 0
                                      • K
                                        kevs @stephenw10 last edited by

                                        Hi Sir @stephenw10,

                                        Sorry for bringing up this old post, May I ask if this modem/4G is supported by Netgate pfsense?

                                        Actually, this is based on Netgate websites but I am afraid if the modems without h and s at the end will work in Netgate pfsense.

                                        (https://docs.netgate.com/pfsense/en/latest/cellular/hardware.html)

                                        The Huawei E8372 instead of Huawei E8372h without h at the end.

                                        As well as,
                                        The Huawei E3372 LTE USB-stick instead of Huawei E3372s LTE USB-stick without s at the end.

                                        and

                                        The Huawei E3372 LTE USB-stick instead of Huawei E3372h LTE USB-stick without h at the end.

                                        Thank you!

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

                                          I've not used any of those myself so I can't say. The best way is to just check other threads for existing reports of success.

                                          1 Reply Last reply Reply Quote 1
                                          • K
                                            kevs last edited by

                                            Hi Sir @stephenw10

                                            Thank you for your response!

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