Can't get Sierra Wireless Aircard 340U to be recognized

Started by fctr, August 15, 2024, 02:16:40 AM

Previous topic - Next topic
For starters:

I know the device works, because I can get it working in other computers; none of them are running FreeBSD, however.

VID: 0x1199
PID: 0x9051

When running a root shell on OPNsense, I can see the device is plugged into the USB port, and it's recognized, but no drivers are loaded. I've tried switching the config to 1 (from 0), and the Aircard tries to act as a hard drive (probably with Windows drivers), but FreeBSD will have none of that and refuses to mount it.

Switching back to config 0, stops FreeBSD from trying to mount the hard drive, but nevertheless no network card, serial port, or anything useful I can work with.

FreeBSD lists this device as something it works with, but OPNsense refuses.

What am I doing wrong?



No such luck!

interface u3g.1 already present in the KLD 'kernel'!

Now what?

Quote from: fctr on August 22, 2024, 07:58:47 PM
interface u3g.1 already present in the KLD 'kernel'!

Well, then it works I'd say. Configure some PPP connection with that.

The closest ones in the kernel are:

product SIERRA EM7430_2         0x81cc  Sierra Wireless EM7430 Qualcomm Snapdragon X7 LTE-A
product SIERRA EM7455           0x9078  Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A

Can you dump more info?

# usbconfig
# dmesg | grep usb


Thanks,
Franco


Oh nevermind. After going through reams of source code, this one-off Sierra POS isn't supported by FreeBSD whatsoever.

Thanks AT&T. Thanks for nothing. I'm going with T-Mobile, next time.

And a sincere thank you to all those who've tried to help me. Next time I'll read before posting.

Well we can patch it. Expect a kernel to test later today :)

https://github.com/opnsense/src/commit/ed71ffba8d

# opnsense-update -zkr 24.7.2-sierra

and reboot. Let me know how it goes.


Cheers,
Franco

To be totally honest, I didn't expect this to go any further. But I will test. Perhaps tonight or tomorrow. You guys (and gals and whatever...) are the best!

OK, so major things have been happening since the patch.

1) FreeBSD now recognizes this is a serial device, and I can now see /dev/cuaU0.[0-3], /dev/cuaU0.[0-3].init, /dev/cuaU0.[0-3].lock, ttyU0.[0-3], ttyU0.[0-3].init, and ttyU0.[0-3].lock, as expected.
2) I can user minicom on ttyU0.1 at 115200 baud to successfully issue AT commands.
3) ATDT*99# does start a connection, but I can't seem to do anything with it
4) I can setup a Point-to-Point connection in the OPNSense interface, but I'm not sure what to do from here.

I could really use a little more hand holding at this point.

Quote from: fctr on August 25, 2024, 11:22:08 PM
4) I can setup a Point-to-Point connection in the OPNSense interface, but I'm not sure what to do from here.

I could really use a little more hand holding at this point.

https://docs.opnsense.org/manual/how-tos/cellular.html

Wow. RTFM. OK, touche.

I get all the way to step 3 without issue. Step 4 fails. Nothing in the PPP log (as expected) and no gateway from the 340U.

I tried entering the init string provided (thinking, it may help), but still nothing.

I feel I'm so close, I can taste success. Tell me where to look for more debugging info. And don't say https://www.freebsd.org/doc/handbook/ppp-troubleshoot.html.

That link is of little help.

Unfortunately, cannot really assist with that, no hardware. Last "dial-up" thing I got my hands on was CDMA and it was a complete nightmare.