Re: Altair Plugin

2016-04-05 Thread Dan Williams
On Tue, 2016-04-05 at 15:35 +0100, Patrick Clark wrote: > Hi, > > I am currently running ModemManager-1.4.2 which supports an Altair > plugin > for their LTE modem. The device is found by ModemManger and can be > seen > using the command: > > mmcli -L > > However the device is locked: > >

Re: SIM7100E

2016-04-05 Thread Dan Williams
On Tue, 2016-04-05 at 10:56 +0200, Yegor Yefremov wrote: > I have a problem with SIM7100E. Though kernel creates wwan0 device, > it > is not visible in ModemManager. Try the following patch if you can; also ensure you are building ModemManager with QMI support (which is the default).  Basically,

Altair Plugin

2016-04-05 Thread Patrick Clark
Hi, I am currently running ModemManager-1.4.2 which supports an Altair plugin for their LTE modem. The device is found by ModemManger and can be seen using the command: mmcli -L However the device is locked: mmcli -m 0 --simple-status Status | state: 'locked' If I turn on debug I see that

Re: Sierra Wireless EM7455

2016-04-05 Thread Bjørn Mork
Andreas Fett writes: > Hi list, > > I'm dealing with a Sierra Wireless EM7455 as used in Lenovos T460s. > > For this modem the mbim driver attaches and works well (ie the sim can > be unlocked) until I try to connect. It then fails during a "set > radio-state" command.

Sierra Wireless EM7455

2016-04-05 Thread Andreas Fett
Hi list, I'm dealing with a Sierra Wireless EM7455 as used in Lenovos T460s. For this modem the mbim driver attaches and works well (ie the sim can be unlocked) until I try to connect. It then fails during a "set radio-state" command. I tried mbimcli with --set-radio-state=on with the same

SIM7100E

2016-04-05 Thread Yegor Yefremov
I have a problem with SIM7100E. Though kernel creates wwan0 device, it is not visible in ModemManager. # mmcli -m 5 /org/freedesktop/ModemManager1/Modem/5 (device id '3c942a37f458697974838e1226b26ded4c5644d6') - Hardware | manufacturer: 'SIMCOM INCORPORATED'

[PATCH] Fixed cgmi_retries in dell_custom_init

2016-04-05 Thread Carlo Lobrano
Initialized "cgmi_retries" variable from CustomInitContext with the same value as the other retries, moreover the context is now allocated with g_slice_new0. Before this changes, when cgmi_retries assumed big values during the probing of no AT-capable ports, the command AT+CGMI