Sierra Wireless EM7455

Bjørn Mork bjorn at mork.no
Wed Jun 1 09:00:14 UTC 2016


Ralph Plawetzki <ralph at purejava.org> writes:

> Hi Bjørn,
>
> the weird thing is, that it worked last week when I got the laptop.
> I read in the Arch forum that qmi-over-mbim is work in progress and
> installed libqmi and libmbim compiled from the qmi-over-mbim branches
> right away.
>
> I could connect to the 1&1 (vodafone) network without issueing the
> --dms-set-fcc-authentication command before.
>
> After that I checked the Lenovo drivers on Windows (it's dual boot) and
> installed a Sierra Wireless driver which seemed to be newer, but was
> not. Maybe this was an error. The device still works on Windows 10 64
> bit. Although I installed the download from the Lenovo site and the
> installer says "Installing Sierra Wireless ..." it reads "Microsoft
> driver" in the driver properties. My feeling is that the device stopped
> working when I started to fiddle with the driver :/

Maybe.  It should not, of course.

There might have been a firmware upgrade behind the scene here.  The
Lenovo driver package includes a number of firmware images and operator
settings.  And the Vodafone ones are particularily complex, changing a
number of settings which I don't know the meaning of and/or don't
understand why need to be operator specific. Vodafones newest settings
(02.14.03.00_Vodafone_000.008_000) even include country specific data,
which makes some sense for things like country specific APNs.  But they
also set things like "MBIM_CUSTOM_DATACLASS" which seems to just be a
string description of the custom class.  It is set to "4G" by default
for all countries except ZA, where it is set to "LTE".  Go figure.  No
other operator does unecessary stuff like that AFAIK.

But none of that should really matter.  If it works for Windows, then it
should of course work for Linux.  Maybe there is some new magic command
sequence we need to use?


Bjørn


More information about the ModemManager-devel mailing list