3G/LTE Modem (Huawei ME909u -521) on boot - USB driver not loading
-
I installed pfSense on a slow USB-memory-stick, and booted from that.
ME909u-521 gets identified and shows 5 serial ports, from cuaU0.0 to 0.4
Configured PPP to port /dev/cuaU0.0, and added &F0E1Q0 to init string.
Yes, it connects and works.Now the problem still lies how to make it work from much faster SSD-disk…
-
I installed pfSense on a slow USB-memory-stick, and booted from that.
ME909u-521 gets identified and shows 5 serial ports, from cuaU0.0 to 0.4
Configured PPP to port /dev/cuaU0.0, and added &F0E1Q0 to init string.
Yes, it connects and works.Now the problem still lies how to make it work from much faster SSD-disk…
Have you figured out how to solve this I am having what seems to be the same problem with a Sierra MC7355
-
Hi guys.
I have here the same problem.
On the running system, plugged off the miniPCIe modem, plugged it in again an its recognized.
But that can't be the plan.
Any new advisories to get the modem recognized?Tried all the recommendations, no luck.
Cheers
Nora -
Hi
some more output:
After plugged off and plugged in the modem.ugen2.3: <huawei technology="">at usbus2 u3g0: <huawei mobile="" connect="" -="" modem="">on usbus2 u3g0: Found 5 ports. ugen2.3: <huawei technology="">at usbus2 (disconnected) u3g0: at uhub4, port 3, addr 3 (disconnected) ugen2.3: <huawei technology="">at usbus2 u3g0: <huawei mobile="" connect="" -="" modem="">on usbus2 u3g0: Found 5 ports.</huawei></huawei></huawei></huawei></huawei>
then the usbconfig dump_device_desc
.. .. ugen2.3: <huawei mobile="" huawei="" technology="">at usbus2, cfg=0 md=HOST spd=HIGH (480Mbps) pwr=ON (500mA) bLength = 0x0012 bDescriptorType = 0x0001 bcdUSB = 0x0200 bDeviceClass = 0x0000 <probed by="" interface="" class="">bDeviceSubClass = 0x0000 bDeviceProtocol = 0x0000 bMaxPacketSize0 = 0x0040 idVendor = 0x12d1 idProduct = 0x1573 bcdDevice = 0x0228 iManufacturer = 0x0001 <huawei technology="">iProduct = 0x0002 <huawei mobile="">iSerialNumber = 0x0003 <0123456712ABCA17> bNumConfigurations = 0x0003</huawei></huawei></probed></huawei>
Where can we do some configuration to recognize this card?
I found an other peace of documentation here:
I don't know if i'm allowed to post an foreign URL ?
But I don't know if this could help?Any help is greatly appreciated
Nora
-
Usbmodeswitch is needed with some usb-type modemsticks, it can change the stick's mode to modem, from the original usb-memory-mode offering typically some installer software for Windows.
As far as I know, ME909 mPCIe-module does not need usbmodeswitch, at least not for it's original purpose.
But maybe it can still be possible to help or re-run the recognition procedure with usbmodeswitch, I don't know.
I quess the core of this problem is somewhere in FreeBSD code, maybe some driver or other USB-related thing causing a timing problem and locking the bus/module.
The best alternative would be if some BSD- or pfSense developer looked at it… -
I have here the same problem.
On the running system, plugged off the miniPCIe modem, plugged it in again an its recognized.
But that can't be the plan.
Any new advisories to get the modem recognized?I've spent a substantial amount of time struggling with this issue: APU board, Huawei ME909u-521, boot from SSD disk. It doesn't matter if the modem is plugged into the motherboard connector or into a USB connector using adapter. Neither this is pfSense-spesific, OPNsense does the same, actually it's the underlying up-to-date freeBSD. AFAIK, old enough (maybe 9.x?) freeBSD did work. But it seems to be essential that 1) the board used is APU and 2) having the Huawei module plugged in during cold boot, the result will be a failure. Plug it in when the system is running, it works.
I've been in touch with PC Engines' support, last week I heard they were able to reproduce the problem and promised to investigate it. So I'll keep my fingers crossed there will be a bios update to fix this some day.
As a workaround I'm using Sierra MC7455 in my most urgent application. It works out-of-the-box, needs no init strings. Unfortunately I've found no way how to get any info about the radio link quality while the connection is active.
-
Hi
I've been in touch with PC Engines' support, last week I heard they were able to reproduce the problem and promised to investigate it. So I'll keep my fingers crossed there will be a bios update to fix this some day.
Is this topic covered in some forum / git on pcengines?
Any news about it?As a workaround I'm using Sierra MC7455 in my most urgent application. It works out-of-the-box, needs no init strings. Unfortunately I've found no way how to get any info about the radio link quality while the connection is active.
I hope there is a solution nearly.
I don't want to spend an other 100$ for an other LTE card.Best regards
Nora -
Hello again
Any further tries.
I updated the BIOS of the apu3b4 from legacy 4.0.7.1 to legacy apu3 v4.0.12
I tought it might be helping.
Created the USB install media
and made the install.
While booting the install media it sees the Huawai modem:.. ugen1.3: <huawei technology="">at usbus1 u3g0: <huawei mobile="" connect="" -="" modem="">on usbus1 u3g0: Found 5 ports. ..</huawei></huawei>
After install is competed, it doesn't recognise it anymore:
.. ugen1.3: <unknown>at usbus1 (disconnected) ..</unknown>
What can be done to reslove this issue?
I read on pcengines, there's a new board revision, Version apu3c:
- Improve compatibility with LTE modem modules: Disconnect SMB_DAT / SMB_CLK signals (1.8V level on Quectel).
- Improve compatibility with LTE modem modules: No stuff diodes D4 / D17, option resistor bypass (extremely low VIL on Huawei modems, sensitive to incoming EMI).
- Optional SIM presence indicator / SIM card detect.
- Disable non-functional NCT5104D watchdog timer.
- Increase 3.3V current limit to allow for two simultaneous LTE modems.
- Some DFM changes.
Any help is appreciated
Cheers
Nora -
I updated the BIOS of the apu3b4 from legacy 4.0.7.1 to legacy apu3 v4.0.12
What can be done to reslove this issue?
I recommend trying v4.0.16 bios. After the very first tests I've made, it looks promising. The bios seems to be already available on PC Engines' page, I got it directly from their support a few days ago. But I believe it's exactly the same version…
-
So the problem here is simply that the modem is not given enough time to initialise at boot?
You could try increasing the value of kern.cam.boot_delay or autoboot_delay in loader.conf(.local).
Steve