Sierra MC73xx working

stephenw10

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

mrneutron

@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....

stephenw10

What device and product ID is it showing now?

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

Steve

mrneutron

@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.

stephenw10

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

mrneutron

@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

stephenw10

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

kevs

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!

stephenw10

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.

kevs

Hi Sir @stephenw10

Thank you for your response!

nanoken

2023 MC7355 WORKING

EDIT - GUIDE BELOW - (MC7355 INFORMATION WAS EVERYWHERE SO I WILL PUT THE STEPS BELOW TO HELP SOMONE)

Load Windows 10/11
2.Go here - https://zukota.com/posts/sierra-wireless-em7455-how-to-enable-com-ports/. - Download the .IMA and make the USB as the guide describes and follow the steps.
3.Back to windows - Follow the the BELOW guide up to the point where it says to connect to the COM port in windows via PUTTY
https://zukota.com/posts/sierra-wireless-em7455-how-to-make-it-work-with-an-older-lenovo-laptop/
4.Type the following in Putty once connected to the com port AT!UDVID=1199 and AT!UDPID=9041 and then at!reset
back to PFSENSE, it should now show at least
6.now to figure out how to set it up in PFSENSE :)

Dobby_

@nanoken said in Sierra MC73xx working:

6.now to figure out how to set it up in PFSENSE :)

Both a pretty old, but for installing and setting up a
LTE modem in pfSense it is even actual anymore.

pfSense 4G WAN configuration

LTE troubleshooting on pfSense

stephenw10

As well as changing the USB IDs to something u3g will recognise you may also need to set the USB composition so it presents an AT port to pfSense.