Re: GPS with Sierra Wireless, Incorporated Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A (cdc-wdm0)

Hey! > ./configure --prefix=/usr --disable-static && make > sudo checkinstall --install=no > sudo dpkg -i libqmi_1.24.12-1_amd64.deb > > but during the install I got this error: > dpkg: errore nell'elaborare l'archivio libqmi_1.24.12-1_amd64.deb (--install): > tentata sovrascrittura di

Re: GPS with Sierra Wireless, Incorporated Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A (cdc-wdm0)

Hi Aleksander, I don't remember, but after your email I recompiled with ./configure --prefix=/usr --disable-static && make sudo checkinstall --install=no sudo  dpkg -i libqmi_1.24.12-1_amd64.deb but during the install I got this error: dpkg: errore nell'elaborare l'archivio

Re: GPS with Sierra Wireless, Incorporated Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A (cdc-wdm0)

Hey! -- >GPS | nmea: ¤ÅAΦUiΔΠ,,1aBéØΠ,X0aBEΓΩ5f4P > | ¤ÅA:t(ΔΠ,X0aBéøΠ,X0aBéØΠ*lXi > | ¤ÅA2Ej_Π,(1aRÇØΠNX0YDEΓΩ2ù5P > Λ | ¤ÅA:4*ΔΠAXDaBéØΠ,X0aBéØΠ,X0a"%L" > > How did you

Re: GPS with Sierra Wireless, Incorporated Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A (cdc-wdm0)

Hi Aleksander, something changed, now I can see the 3GPP position, but the GPS stream is always corrupted: mmcli -m 0  --location-get   --   3GPP |  operator code: 222    |  operator name: 50    | location area code: 86E9    | tracking area code:

Re: GPS with Sierra Wireless, Incorporated Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A (cdc-wdm0)

Hey, > I'm trying to get the GPS data from my modem, but I receive "strange" > character as output: > > mmcli -m 0 --location-status > >Location | capabilities: 3gpp-lac-ci, gps-raw, gps-nmea, > agps-msa, agps-msb > |

GPS with Sierra Wireless, Incorporated Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A (cdc-wdm0)

Hi, I'm trying to get the GPS data from my modem, but I receive "strange" character as output: mmcli -m 0  --location-status     Location | capabilities: 3gpp-lac-ci, gps-raw, gps-nmea, agps-msa, agps-msb    |  enabled:

Re: Sierra Wireless EM7455 dysfunctional

facturer=Sierra Wireless, Incorporated >S: Product=Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A >S: SerialNumber=LF62830495041014 >C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA >I: If#=12 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=qmi_wwan >I: If#=13 Alt= 1 #EPs= 2 Cls=0a(data )

Re: Sierra Wireless EM7455 dysfunctional

080] usb 1-2: config 1 has no interface number 1 2016-10-13T11:02:58.068693+02:00 x1carbon kernel: [5.397249] usb 1-2: New USB device found, idVendor=1199, idProduct=9079 2016-10-13T11:02:58.068693+02:00 x1carbon kernel: [5.397250] usb 1-2: New USB device strings: Mfr=1, Product=2, Serial

Sierra Wireless EM7455 dysfunctional

6 S: Manufacturer=Sierra Wireless, Incorporated S: Product=Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A S: SerialNumber=LF62830495041014 C: #Ifs= 2 Cfg#= 1 Atr=a0 MxPwr=500mA I: If#=12 Alt= 0 #EPs= 1 Cls=02(commc) Sub=0e Prot=00 Driver=cdc_mbim I: If#=13 Alt= 1 #EPs= 2 Cls=0a(data ) Sub=00 P

Re: Sierra Wireless EM7455

> > Am 04.08.2016 um 17:13 schrieb Nicolas Christener: > > tl;dr: the WWAN card works now! It might to be related to the SIM PIN. > > A now version of the linux kernel has been released for Arch linux. So with > > Name : libmbim > Version : 1.14.0-1 > > Name

Re: Sierra Wireless EM7455

Am 04.08.2016 um 17:13 schrieb Nicolas Christener: > tl;dr: the WWAN card works now! It might to be related to the SIM PIN. A now version of the linux kernel has been released for Arch linux. So with Name : libmbim Version : 1.14.0-1 Name

Re: Sierra Wireless EM7455

> What I think is happening (and Aleksander can correct me if not) is > there can be some provisioning data that is downloaded from the > operator to the SIM and/or device when it registers with the network. > Maybe the modem was never in an idle state long enough to do that, or > maybe Windows

Re: Sierra Wireless EM7455

On Thu, 2016-08-04 at 17:13 +0200, Nicolas Christener wrote: > Hi Dan :) > > On Wed, 2016-08-03 at 11:09 -0500, Dan Williams wrote: > [...] > > > > Any chance you can try the SIM in another WWAN card in the > > computer, or > > in a USB stick?  Or try the same EM7455 in Windows? > tl;dr: the

Re: Sierra Wireless EM7455

On Wed, 2016-08-03 at 05:47 +0200, Nicolas Christener wrote: > Hi Dan :) > > On Tue, 2016-08-02 at 16:53 -0500, Dan Williams wrote: > [...] > > > > I forget; have you tried the SIM in a different device, and if so > > does > > that work correctly? > The SIM works in a Android phone and also in a

Re: Sierra Wireless EM7455

On Tue, 2016-08-02 at 22:42 +0200, Nicolas Christener wrote: > Hi :) > > Today I updated my system firmware and searched some more information > regarding my issue. Then I found this - which seems related: > https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commi > t/drivers >

Re: Sierra Wireless EM7455

Hi :) Today I updated my system firmware and searched some more information regarding my issue. Then I found this - which seems related: https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers /net/usb/cdc_ncm.c?id=c086e7096170390594c425114d98172bc9aceb8a I now run a 4.6.5

Re: Sierra Wireless EM7455

Hi Dan, Aleksander Thank you very much for having a look into my issue, please see below for more info. On Thu, 2016-07-28 at 10:10 -0500, Dan Williams wrote: [...] > But given that it's a Sierra, I wonder if Nicolas could run the > following on the modem's AT port: > > AT!ERR=0 > AT!GCCLR > >

Re: Sierra Wireless EM7455

On Wed, Jul 27, 2016 at 10:29 PM, Nicolas Christener <li...@0x17.ch> wrote: > I saw some other mails regarding the same topic but was not able to find a > solution for my problem. I got a Thinkpad T460s and run into problems with the > built in Sierra Wireless EM7455. >

Sierra Wireless EM7455

Hi all :) I saw some other mails regarding the same topic but was not able to find a solution for my problem. I got a Thinkpad T460s and run into problems with the built in Sierra Wireless EM7455. I built libmbim and libqmi from master and rebuild ModemManger (1.6.0) which seems to pick the two

Re: Sierra Wireless EM7455

Am 13.06.2016 um 01:39 schrieb Aleksander Morgado: > Ralph, could you get the latest ModemManager "qmi-over-mbim" branch, > rebuild and retry? The latest change I did in the branch is > specifically to test your usecase, so it would be great if you could > do that. > > You'll need libqmi and

Re: Sierra Wireless EM7455

On Fri, Jun 3, 2016 at 4:53 AM, Ralph Plawetzki wrote: > just for the record please find attached in short what goes wrong: > [EM7455 gets local IP] http://pastebin.com/K7j10Y64 Ralph, could you get the latest ModemManager "qmi-over-mbim" branch, rebuild and retry? The

Re: Sierra Wireless EM7455

Am 09.06.2016 um 20:43 schrieb Bjørn Mork: > That should work, but with NAT in your ISPs network. The address is > part of the "Shared Address Space" for carrier grade NAT. See > https://tools.ietf.org/html/rfc6598 Yeah, that's true. I bought an USB UMTS modem stick at the supermarket and with

Re: Sierra Wireless EM7455

Am 09.06.2016 um 18:03 schrieb Ralph Plawetzki: > I see. I am not sure whether it says 'Lenovo' or 'Sierra' on lsusb. Bus 001 Device 006: ID 1199:9079 Sierra Wireless, Inc Ralph ___ ModemManager-devel mailing list

Re: Sierra Wireless EM7455

Am 09.06.2016 um 20:43 schrieb Bjørn Mork: > intended to work. But maybe not for Internet? Are there other APNs you > can use? Can you verify that the APN you are using works (for Internet > access) on e.g. a phone? No, the APN is right for my provider/contract. The SIM card used to work with

Re: Sierra Wireless EM7455

On Thu, Jun 9, 2016 at 12:24 PM, Bjørn Mork wrote: >>> How difficult will it be to restrict this to Sierra modems with QMI >>> service support? Or was that the set you meant we should >>> unconditionally try the command on? If so, then I say "go!". >> >> I tried the QMI MBIM

Re: Sierra Wireless EM7455

On Thu, Jun 9, 2016 at 11:53 AM, Bjørn Mork wrote: >> What do you guys think, should we unconditionally try to send the FCC >> auth via QMI over MBIM in the generic MBIM implementation? E.g. during >> the power-up sequence. > > My memory lasts exactly this far: . > > Did we test

Re: Sierra Wireless EM7455

Aleksander Morgado writes: > On Thu, Jun 9, 2016 at 12:27 AM, Ralph Plawetzki wrote: >> My modem needs that too and I can get it online, but as described it >> gets a local IP then. From searching the web, many people had problems >> getting the

Re: Sierra Wireless EM7455

Ralph Plawetzki writes: > Am 09.06.2016 um 18:03 schrieb Aleksander Morgado: >> On Thu, Jun 9, 2016 at 12:27 AM, Ralph Plawetzki wrote: >> This is interesting then; the modem does get online (as opposed to the >> QMI modems, which fail to set the

Re: Sierra Wireless EM7455

Am 09.06.2016 um 18:03 schrieb Aleksander Morgado: > On Thu, Jun 9, 2016 at 12:27 AM, Ralph Plawetzki wrote: > This is interesting then; the modem does get online (as opposed to the > QMI modems, which fail to set the full-power mode), and it even gets > an IP assigned, but

Re: Sierra Wireless EM7455

Am 09.06.2016 um 17:09 schrieb Dan Williams: > QMI and MBIM are just different ways to talk to the modem's firmware. > Like languages. QMI is proprietary to Qualcomm, older than MBIM, and > ties much more closely to the firmware architecture of Qualcomm chips. > > MBIM is a "standard" protocol

Re: Sierra Wireless EM7455

maybe the firmware) is responsible for retrieving an IP, from my > point > of view it does not make sense to go any further from this point. > > > > > This is a Lenovo modem in a Lenovo laptop, right?  If not then I > > got the > > rest wrong.  But in case that is

Re: Sierra Wireless EM7455

On Fri, 2016-06-03 at 20:36 +0200, Ralph Plawetzki wrote: > Am 03.06.2016 um 17:15 schrieb Dan Williams: > > > > For allowed modes, combinations are joined with "|".  That's non- > > obvious I suppose, though 'mmcli --help-modem' does say: > > > >   --set-allowed-modes=[MODE1|MODE2...]   Set

Re: Sierra Wireless EM7455

On Fri, 2016-06-03 at 14:38 +0200, Ralph Plawetzki wrote: > Am 03.06.2016 um 14:09 schrieb Aleksander Morgado: > > > > --set-preferred-mode must be given along with --set-allowed-modes; > > and > > as values for them you should use one of the combinations listed as > > supported when showing the

Re: Sierra Wireless EM7455

On Wed, Jun 1, 2016 at 7:22 PM, Dan Williams wrote: > On Wed, 2016-06-01 at 19:20 +0200, Aleksander Morgado wrote: >> On Wed, Jun 1, 2016 at 7:13 PM, Dan Williams wrote: >> > >> > On Wed, 2016-06-01 at 15:46 +0200, Aleksander Morgado wrote: >> > > >> > > On Wed,

Re: Sierra Wireless EM7455

On Wed, 2016-06-01 at 19:20 +0200, Aleksander Morgado wrote: > On Wed, Jun 1, 2016 at 7:13 PM, Dan Williams wrote: > > > > On Wed, 2016-06-01 at 15:46 +0200, Aleksander Morgado wrote: > > > > > > On Wed, Jun 1, 2016 at 11:15 AM, Ralph Plawetzki > > org> > > >

Re: Sierra Wireless EM7455

On Wed, Jun 1, 2016 at 7:13 PM, Dan Williams wrote: > On Wed, 2016-06-01 at 15:46 +0200, Aleksander Morgado wrote: >> On Wed, Jun 1, 2016 at 11:15 AM, Ralph Plawetzki >> wrote: >> > >> > iface_modem_firmware_initialize_ready(): Couldn't initialize >> >

Re: Sierra Wireless EM7455

On Wed, 2016-06-01 at 15:46 +0200, Aleksander Morgado wrote: > On Wed, Jun 1, 2016 at 11:15 AM, Ralph Plawetzki > wrote: > > > > iface_modem_firmware_initialize_ready(): Couldn't initialize > > interface: > > 'Firmware not supported' > We should change that message; it does

Re: Sierra Wireless EM7455

Ralph Plawetzki writes: > Firmware could be the prob as I startet ModemManager in debug mode which > gave me an [mm-broadband-modem.c:9231] > iface_modem_firmware_initialize_ready(): Couldn't initialize interface: > 'Firmware not supported' > > http://pastebin.com/5V8xcC6y >

Re: Sierra Wireless EM7455

Am 01.06.2016 um 11:00 schrieb Bjørn Mork: > 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

Re: Sierra Wireless EM7455

Am 01.06.2016 um 10:31 schrieb Bjørn Mork: > That's unexpected. This isn't going to be easy :( Thanks anyway!! > Wild guessing now. Maybe the network/modem/MM don't like that you didn't > disconnect first? You could try a full reset, followed by the same USB > reset and *then* fcc-auth +

Re: Sierra Wireless EM7455

've already sent the command. > > Ok. > >> Resetting MC7455 ... ok > > Thanks for the exact directions! > > [root@six tmp]# ./usbreset 1199:9079 > Resetting Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A ... ok > [root@six tmp]# > > That looks good. > >>

Re: Sierra Wireless EM7455

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

Re: Sierra Wireless EM7455

[root@six tmp]# ./usbreset 1199:9079 Resetting Sierra Wireless EM7455 Qualcomm Snapdragon X7 LTE-A ... ok [root@six tmp]# That looks good. > you will have to reconnect. Does it make any difference? I tried to connect via network manager right away. First time without issueing a --dms-set-fcc-au

Re: Sierra Wireless EM7455

Ralph Plawetzki writes: >> Stefan Armbruster writes: >> >>qmicli -p -d /dev/cdc-wdm0 --device-open-mbim --dms-set-fcc-authentication > > Hi list, > > I still have problems to get the modem connect to the net. > libqmi and libmbim are compiled from the qmi-over-mbim

Re: Sierra Wireless EM7455

Hi, TL;DR: I'm still stuck here. Connection is successfully established but on ip level tcpdump only shows outgoing and no incoming packets. Current situation is as follows: * using "qmi-over-mbim" branch for libmbim and libqmi * calling `sudo qmicli -v -p -d /dev/cdc-wdm0 --device-open-mbim

Re: Sierra Wireless EM7455

That helped a lot - thanks a ton, Bjorn. After sending FCC authentication connecting to my mobile provider through network-manager works like a charm. Device wwan0 gets an IP address assigned. Tracing wwan0 with tcpdump shows only outgoing packets and not a single incoming packet. Since

Re: Sierra Wireless EM7455

Bjørn Mork writes: > ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var > --libdir=/usr/lib/x86_64-linux-gnu --libexecdir=/usr/lib/libqmi > --enable-mbim-qmux > > > Not sure about the libexecdir, though. Does the Ubuntu package have > that there, with qmi-proxy

Re: Sierra Wireless EM7455

Stefan Armbruster writes: > pkg-config --modversion mbim-glib returns 1.12.2. So that explains the missing support. The configure script should warn about this... > # find /usr -name "libmbim*.so" > /usr/lib/libmbim-glib.so > /usr/lib/x86_64-linux-gnu/libmbim-glib.so >

Re: Sierra Wireless EM7455

pkg-config --modversion mbim-glib returns 1.12.2. # find /usr -name "libmbim*.so" /usr/lib/libmbim-glib.so /usr/lib/x86_64-linux-gnu/libmbim-glib.so So my build from git gets installed to /usr/lib and the the one in /usr/lib/x86_64-linux-gnu/ is from the Ubuntu packages archive. How to deal

Re: Sierra Wireless EM7455

Thanks for the build instructions. I've followed them closely, but unfortunately I still get a time out upon "Allocate CID". # qmicli -v -p -d /dev/cdc-wdm0 --device-open-mbim --dms-set-fcc-authentication [06 Mai 2016, 20:43:30] [Debug] [/dev/cdc-wdm0] Opening device with flags 'proxy, mbim'...

Re: Sierra Wireless EM7455

On Fri, May 6, 2016 at 10:12 AM, Bjørn Mork wrote: > Yes, this is unnecessarily complicated and error prone. I just didn't > implement all the user friendly parts in my quick-and-dirty first hack. > Feel free to fix :) At the very least, qmicli should do some sanity > checking and

Re: Sierra Wireless EM7455

Stefan Armbruster writes: > Aleksander, I've just reinstalled qmi-over-mbim branches (both libmbim > and libqmi) using ./configure --prefix=/usr; make; sudo make install > and still getting the same result: > > # qmicli -v -d /dev/cdc-wdm0 --dms-set-fcc-authentication

Re: Sierra Wireless EM7455

Aleksander, I've just reinstalled qmi-over-mbim branches (both libmbim and libqmi) using ./configure --prefix=/usr; make; sudo make install and still getting the same result: # qmicli -v -d /dev/cdc-wdm0 --dms-set-fcc-authentication [06 Mai 2016, 09:36:45] [Debug] [/dev/cdc-wdm0] Opening device

Re: Sierra Wireless EM7455

On Sat, Apr 23, 2016 at 9:41 PM, Stefan Armbruster wrote: > As mentioned previously I've installed Ubuntu 16.04 with default > modemmanager, libmbin, libqmi. Additional the "qmi-over-mbim" branch > stuff is installed in /usr/local. For the "qmi-over-mbim" branch

Re: Sierra Wireless EM7455

Stefan Armbruster writes: > I've built qmi-over-mbim branch for both, libqmi and libmbim. `make > install` puts the stuff to /usr/local. > > However I always get "CID allocation failed", see below. Do I have to > reset something beforehand? Upon startup of the machine

Re: Sierra Wireless EM7455

lt;<<< tlv_length = 4 <<<<<< message = "Allocate CID" (0x0022) <<<<<< TLV: <<<<<< type = "Service" (0x01) <<<<<< length = 1 <<<<<< value = 02 <<&

Re: Sierra Wireless EM7455

On Wed, Apr 13, 2016 at 8:48 PM, Stefan Armbruster <ste...@armbruster-it.de> wrote: > my new Thinkpad X1 Yoga is equipped with a Sierra Wireless EM7455 LTE > card, which does not work right now. I have installed Ubuntu 16.04 > with a 4.6-RC2 mainline kernel. > >

Sierra Wireless EM7455

Hi, my new Thinkpad X1 Yoga is equipped with a Sierra Wireless EM7455 LTE card, which does not work right now. I have installed Ubuntu 16.04 with a 4.6-RC2 mainline kernel. The card is detected by modemmanager, but not accessible in network manager. Its state in mmcli is always "disabled&

Re: Sierra Wireless EM7455

Andreas Fett <andreas.f...@secunet.com> 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 &qu

Sierra Wireless EM7455

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 wit