Huawei Modem Usb Driver

[John]

HIi found new USB modem driver. On ML I was using huawei universal v 4.25.05 driver with bulitin connect feature trough network prefs. this driver still work on Mavericks but was little crappy took long time to connect. On device manufacturer I found new driver for MBA 2013 that is working better and is version 4.25.45 link is consumer.huawei.com/en/support/downloads/detail/index.htm?id=17263 named MobileConnectDriver for Mac Book Air 2013 from 31th august 2013. It connects faster but like previous driver it is not showing time on menu bar like in ML. where can i enable time for menu bar?

hey. it is E176, very old model. i use it without mobile connect app. just directly dialing trough network settings or trough menu bar icon. it is behaving differently like on ML. when i dial it shows connecting then authenticating. after that i see time all zeroes. but it seem it is frozen and no connection. after half a minute time in menu bar shows like 32 secs and counting up. then connection is working.

Hi , i am using Macbook pro(OS X 10.9) . i hav problems with Huawei usb modem , the device not detecting. (device model is E303D) . i installed MobileConnectDriver for Mac Book Air 2013 bt still not working. ?

Coming in a form-factor of a USB-stick, it is capable of maintaining quite a high-speed internet connection, and apparently it supports all the international LTE standards because I was using it in several countries without problems.

If memory serves me well, I did not perform any unlocking operations, and it just works fine with SIM-cards from other operators than Megafon. I must say, however, I never tried it with any other russian operators - the only SIM-cards I was using it with were the ones from norwegian operators (Telia and Phonero).

From the Revision value we can see that is starts with 21, which means that the modem has the STICK firmware. The HILINK revision numbers start with 22. More details about firmware types are here (in russian).

Rebooted to normal mode and installed this driver. Now it did show a dialog window about blocked extension, and there was a whole bunch of them in Security & Privacy (most likely just some other stuff I had installed in past), for some reason already pre-selected and grayed out:

Alright then, I rebooted back to Recovery mode, enabled SIP back and rebooted to normal mode. But after loading into normal mode I got a dialog window about blocked/updated system extension, and modem was no longer discoverable:

A while back I installed a USB 3G modem (a Three Mobile Huawei D160G and Mobile Partner software) on my Windows 2008 64 bit development box. I immediately encountered a problem where upon starting a Windows 2003 Standard Edition VM in Virtual Server 2005R2 the host OS would crash with a Blue Screen of Death periodically.

The blue screen problems continued however and I noticed that the uninstaller hadn't removed the network adapter it created when the 3G software was installed. I deleted this but suspect that there's still something left over that's causing Virtual Server 2005R2 to BSOD.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\hwcdcmdm0 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\hwdatacard HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\hwusbapp HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\hwusbser

The hwdatacard registry entry has a value named ImagePath which points to system32\DRIVERS\ewusbmdm.sys. This file physically doesn't exist (presumably deleted at uninstall time) and it's definately related to the Huawei adapter (it has a DisplayName value of Huawei DataCard USB Modem and USB serial so I'm guessing all of the hw* entries above are related to this device.

The problem it seems isn't left over drivers from the 3G USB dongle, but a hardware fault on the machine. I flattened the machine and installed Windows 7 Ultimate and the problem remains where Virtual PC 7 does exactly the same thing.

So, obviously, the stock image I installed does not support ppp filtering. I did the test above because if I compile the kernel myself and enable PPP and USB ACM options as indicated in the article above, then I am unable to see the modem mount as a ttyUSBx or ttyACMx device.

It appears to recognise the modem as a huawei. As an aside, I have been successful in using ppp and chat scripts to get the modem to connect to the internet; however, for my application, Connman and Ofono are preferred to manage multiple ways to establish internet.

If you really need to use this modem, you may also check if you can put your modem into another mode (e.g. qmi/mbim) with usb_modeswitch ( Draisberghof - Software - USB_ModeSwitch). Unfortunately this is out of Toradexes scope.

@mikec , you may have a try with usb-modeswitch. Build BSP from OpenEmbedded with usb-modeswitch and config files. Add IMAGE_INSTALL_append = " usb-modeswitch usb-modeswitch-data" to local.conf.

Flash new BSP to your module. When plugin modem, you can find it in mass storage mode.

you may add DefaultVendor and DefaultProduct to it. Then use usb-modeswitch to enable it. Now check it with lsusb, this device is not in mass storage mode any more and another network interface is added.

I ran into a bug that crashed dwc2_lowlevel_hw_disable when using the dongle in "HiLink router mode" with kmod-usb-net-cdc-ether, so flashed the dongle to "stick mode" and now using kmod-usb-net-huawei-cdc-ncm instead.

it looks like some part of netifd may be confused whether the "option mode" clause should really be "option modes", when I added both options it silenced the error but didn't help the interface to start.

If I use minicom -D /dev/cdc-wdm0

I don't get any response to AT commands, but then if I try the same when the stick is plugged into the Fedora PC, I get no responses either, so that may not be significant

Wrt the config: Did /dev/cdc-wdm0 work as an AT command management device in Fedora? IIRC, different Huawei firmwares beahve differently here. But if the /dev/ttyUSBx device works, then I guess this isn't important.

This is misleading at best. That might have been the original meaning, but the option driver is now a multi-vendor generic fast USB serial driver. And it specifically supports the serial functions of most Huawei 3G and LTE modems.

That is pointless. Did you try this yourself? The usb-wwan module is only a support module with some shared functions for option, qcserial and ipw drivers. It supports no modems by itself. But the option driver depends on it, so it will be installed when you install it.

It can be a bit confusing, because you have to use the /dev/cdc-wdm0 on some Huawei modems. On most you can use either the /dev/cdc-wdm0 or the /dev/ttyUSBx devices. And yet another bunch is like yours where you have to use /dev/ttyUSBx.

Not sure how far it's getting with that, but "ip route show" doesn't have anything on the wwan0 interface, and the interface has no IP address, Interface still shows "up" but without receiving any bytes ...

Actually I just ran modemmanager in debug mode

however the output is too big to paste here,

I tried to upload as an attachment, but it apparently I'm only authorised to upload ,jpgs etc

can someone authorise me to upload a .txt file?

I've encountered the same problem with LT4112 on a HP Folio 1040 G1 w/ Windows 8.1 X64, also full updated.

The problem originates with having issues connecting through the modem and getting "Limited Internet Access". Therefor we uninstalled the drivers to troubleshoot the modem, and now we can't get it back. Everything works flawless on Windows 7 X64 - but not Windows 8.1 X64.

The only time I've got it to work (WWAN+Sleep... and I hardly know how I did it) is when the gobi driver tells me that it's manufactured by Microsoft, and not MBB Incorporated. That's how it's delivered from HP out of the box. Managed to get it that way once, but don't remember how I did it. I think I tinkered with the COM-ports that appears after driver installation. Those COM-ports aren't there the looking at an OOTB machine.

Most modern usb modems include a "router" inside, and the linux drivers configure it to pop up as an interface after initialisation. The router will then simulate an ethernet port and route all internet traffic through it.

Essentially these lines will monitor for these interface names, and if they are there from boot, or plugged in afterwards (hotplugged) they will be initialised to run as an internet interface, using dhcp to set up the ip, gateway and other parameters.

then the modem has been configured as a fake ethernet port (eth1) and you will get internet traffic. The modem's built-in router runs a firewall that blocks internet access from the outside, but any calls from the inside will be routed correct.

after plugging in the 4g dongle, run the below command and your dongle will be installed and now you must set up a new connection after the installation, sure this will help out who are all out there...

I am trying to make a Huawei Brovi E3372-325 USB LTE model work with a Raspberry Pi. Out of the box, it shows as a CDROM when plugging it in. (This is apparently used to automatically run the driver installation on Windows.)

So far, I found this post with a udev rules configuration file. That enables the modem when hotplugging it while the system is running by running usb_modeswitch. However, if the modem is plugged in on boot, it does not work, instead showing as a CD ROM.

Therefore, I am now trying to write a system service to run usb_modeswitch on boot. As a step towards that, I booted with the modem plugged in and then tried executing the usb_modeswitch commands from the configuration file manually. However, that does not have the intended effect.

Apparently, upon being powered on, the modem shows itself as a modem for a second, then switches to CDROM mode, but does not seem to accept commands switching it back to modem mode. The CDROM mode is intended for automatic driver installation in Windows. Though, that also means that when the driver is installed, the drive can be switched back to modem mode. So, it seems that usb_modeswitch and the Windows driver use different commands to switch to modem mode?

3a8082e126