01-03-2019 07:39 PM
Final story: Lenovo remove "whilte list" from x1C6 BIOS version 1.34. If you have x1C6, you can use any wwan card after 1.34 update.
Sadly doesn't seem to be the case — upgraded to 1.34 via fwupd, "Unauthorized" still triggers with EM7455 and AT!CUSTOM="FASTENUMEN",1.
01-03-2019 08:24 PM
01-03-2019 08:44 PM
There's nothing new in that thread. People report success with Sierra's EM7455/7345. These modems are known for long boot times (at least with FASTENUMEN off), so these success reports only reinforce my hypothesis.
X1Y3's BIOS apparently works differently if the FASTENUMEN trick doesn't work for you.
01-04-2019 08:04 AM
01-04-2019 11:12 PM - edited 01-04-2019 11:14 PM
There is another detail I have initially missed and just discovered that might be of interest to you.
The AT!CUSTOM="FASTENUMEN" setting is actually not boolean. It accepts integers from 0 to 3, which toggle various behavior depending on cold/warm boot condition.
Try invoking AT!CUSTOM="FASTENUMEN",2. This setting configures the modem for slow enumeration on cold boot and fast enumeration on warm boot. This means that the modem will reappear faster on S3 resume, but still evade whitelist checks when the system is cold-booted.
(Caveat emptor: I only tested this lightly. If you trigger a whitelist failure somehow, do a full power-off to force a cold boot and slow enumeration.)
01-05-2019 01:42 AM
Yes, this is described in SIerra Wireless EM7xxx AT manual, applied to both 7455 and 7565.
Actually Fast USB is Qualcomm feature, applied to Huawei ME906 too. But AT command password for advanced mode is unknown to us.
My original intent is, if 7455 works, I will buy EM7565 from digikey and use 7565 instead. But it failed on X1y3.
01-09-2019 05:31 AM
Does it make sense to buy a 7565 as replacemente for Fibocom L850-GL on X1C6? Can it work both on Win10 and Manjaro?
I am heavily relying on WWNA lately and after the latest updates it has been a hell with BSODs...
01-24-2019 04:57 AM
FYI, if someone is experiencing problem when em7455 is not connecting to the network (after fastenumen set to 2 or 0) - try this command: AT!PCOFFEN=2
My modem started to connect just fine in both win10 and Ubuntu18.04 after that!