Lenovo (x260) and EM7455

[Bjørn Mork]

Bjørnar Ness <bjornar.ness at gmail.com> writes:

> That worked, and I now have serial interfaces. Seems W_DISABLE is true, dont
> know if that means anything:
> State: Low Power Mode
> LPM voters - Temp:0, Volt:0, User:0, W_DISABLE:1, IMSWITCH:1, BIOS:0
> LPM persistence - None

W_DISABLE is the rfkill input (often known as pin #20 on the older
mini-PCIe modules.  Are you sure this isn't just you having tested
rfkill?  I hope so...

It it weren't for the unexpected W_DISABLE, then IMSWITCH would explain
your problems:  This means that there is a mismatch between the firmware
images on the module and the firmware image it is configured to use,
possibly automatically based on SIM.

You can get this info with QMI, but the Sierra AT command implementation
gives a nice output since you have AT.  This is how my EM7455 looks:

at!image?                                                                                                                                    
TYPE SLOT STATUS LRU FAILURES UNIQUE_ID   BUILD_ID
FW   1    GOOD   1   0 0      ?_?         02.05.07.00_?
FW   2    GOOD   2   0 0      ?_?         02.08.02.00_?
FW   3    EMPTY  0   0 0                  
FW   4    EMPTY  0   0 0                  
Max FW images: 4
Active FW image is at slot 2

TYPE SLOT STATUS LRU FAILURES UNIQUE_ID   BUILD_ID
PRI  FF   GOOD   0   0 0      002.007_000 02.08.02.00_GENERIC
PRI  FF   GOOD   0   0 0      002.006_000 02.08.02.00_ORANGE-EU
Max PRI images: 50


OK
at!impref?
!IMPREF: 
 preferred fw version:    02.08.02.00
 preferred carrier name:  GENERIC
 preferred config name:   GENERIC_002.007_000
 current fw version:      02.08.02.00
 current carrier name:    GENERIC
 current config name:     GENERIC_002.007_000

OK

And I believe it was like this from delivery.  But I did boot Windows
once, so that could have changed it. Don't remember if I booted Windows
with the original "Lenovo" SIM or with a Telenor SIM.  If the latter,
then I assume the GENERIC PRI could be a result of that.

I assume you have a mismatch between preferred and current?  Do you have
Windows on that laptop?  If you have, then booting that is by far the
easiest and safest way to get the correct firmware image installed.

Otherwise we'll have to move to the experimental section :)


Bjørn