X55 T99W175 modem

[PaddyX]

So the firmware fun on lenovo ver: Still working on.. One item noticed when was cross checking the HP vs Lenovo..

HP:
Manufacturer: HP
Model: Qualcomm Snapdragon X55 5G
Firmware: T99W175.F0.1.0.0.9.VF.008
076
Network type: 3GPP
Data class: UMTS, HSDPA, HSUPA, LTE, 5G, 5G

Lenovo:
Manufacturer: Qualcomm
Model: Qualcomm Snapdragon X55 5G
Firmware: T99W175.F0.1.0.0.5.VF.007
016
Network type: 3GPP
Data class: UMTS, HSDPA, HSUPA, LTE, 5G, 5GSA

The HP actuily sais HP while the lenovo sais Qualcomm.. Any chance you can cross check your lenovo and see what the Manufacturer value is.
Also another strange one, the lenoco seems to have all its pug/conectors in place while the HP just has the 4 antena mounts.. And noticed a differing value in Data class: ie: hp: 5G vs Lenovo: 5GSA
(Early 5G networks have been based on 5G non-standalone architecture, using a 5G Radio Access Network that anchors to existing Evolved Packet Core networks. 5G standalone, on the other hand, anchors to a cloud-native 5G Core network using service-based architecture.)(5G SA is a true 5G network, end to end, using 5G radios on the edge and a 5G core) Got me wondering if this could be part of why was not able to force 5g mode on the HP...

When have time will be moving it onto my linux system so can cross check and flash it as the process seems leaning toward linix and not managed to find a windows route yet..

[mtl26637]

So the firmware fun on lenovo ver: Still working on.. One item noticed when was cross checking the HP vs Lenovo..

Eskaryo and I covered a lot of the firmware stuff on page 1 of this thread. Might go back and skim through our back and forth for details. Ultimately I believe a sim swap on a windows box should trigger the firmware update process. Swapping to a different sim provider or a back and forth between different providers seems to have worked in the past. Might give that a shot or revisit if you had tried before?

[PaddyX]

oh yes thanks for that reminder! Most interesting!

eskaryo think had Lenovo
manufacturer: foxconn
model: Qualcomm Snapdragon X55 5G

mtl26637 and you mentioned having both: Lenovo and HP With think bellow being your Lenovo: (seen via mmcli -m 0 output)
manufacturer: generic
model: Snapdragon(TM) X55

Interesting.. Will work on getting the linux system back up and check the vendor values. Also will be able to manualy flash it easier there are the moment..

Thanks again!!

[mtl26637]

Have 2 Lenovo and 1 HP. Currently running one of the Lenovo versions:

Code: Select all

  _______                     ________        __
 |       |.-----.-----.-----.|  |  |  |.----.|  |_
 |   -   ||  _  |  -__|     ||  |  |  ||   _||   _|
 |_______||   __|_____|__|__||________||__|  |____|
          |__| W I R E L E S S   F R E E D O M
 -----------------------------------------------------
 OpenWrt 23.05.0-rc3, r23389-5deed175a5
 -----------------------------------------------------
root@OpenWrt:~# mmcli -m 0
  -----------------------------------
  General  |                    path: /org/freedesktop/ModemManager1/Modem/0
           |               device id: ###
  -----------------------------------
  Hardware |            manufacturer: foxconn
           |                   model: Qualcomm Snapdragon X55 5G
           |       firmware revision: T99W175.F0.1.0.0.9.TO.006
           |                          055
           |          carrier config: T-mobile
           | carrier config revision: 0A000506
           |            h/w revision: Qualcomm Snapdragon X55 5G
           |               supported: gsm-umts, lte, 5gnr
           |                 current: gsm-umts, lte, 5gnr
           |            equipment id: ###
  -----------------------------------
  System   |                  device: /sys/devices/pci0000:00/0000:00:1c.3/0000:02:00.0
           |                 drivers: mhi-pci-generic
           |                  plugin: foxconn
           |            primary port: wwan0mbim0
           |                   ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim),
           |                          wwan0qcdm0 (ignored)
  -----------------------------------
  Numbers  |                     own: ###
  -----------------------------------
  Status   |                    lock: sim-pin2
           |          unlock retries: sim-pin2 (10)
           |                   state: connected
           |             power state: on
           |             access tech: lte, 5gnr
           |          signal quality: 34% (cached)
  -----------------------------------
  Modes    |               supported: allowed: 3g; preferred: none
           |                          allowed: 4g; preferred: none
           |                          allowed: 3g, 4g; preferred: 4g
           |                          allowed: 3g, 4g; preferred: 3g
           |                          allowed: 5g; preferred: none
           |                          allowed: 4g, 5g; preferred: 5g
           |                          allowed: 4g, 5g; preferred: 4g
           |                          allowed: 3g, 5g; preferred: 5g
           |                          allowed: 3g, 5g; preferred: 3g
           |                          allowed: 3g, 4g, 5g; preferred: 5g
           |                          allowed: 3g, 4g, 5g; preferred: 4g
           |                          allowed: 3g, 4g, 5g; preferred: 3g
           |                 current: allowed: 3g, 4g, 5g; preferred: 5g
  -----------------------------------
  Bands    |               supported: utran-1, utran-3, utran-4, utran-6, utran-5, utran-8,
           |                          utran-9, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5,
           |                          eutran-7, eutran-8, eutran-12, eutran-13, eutran-14, eutran-17,
           |                          eutran-18, eutran-19, eutran-20, eutran-25, eutran-26, eutran-28,
           |                          eutran-29, eutran-30, eutran-32, eutran-34, eutran-38, eutran-39,
           |                          eutran-40, eutran-41, eutran-42, eutran-46, eutran-48, eutran-66,
           |                          eutran-71, utran-19, ngran-1, ngran-2, ngran-3, ngran-5, ngran-7,
           |                          ngran-8, ngran-12, ngran-20, ngran-25, ngran-28, ngran-38, ngran-40,
           |                          ngran-41, ngran-48, ngran-66, ngran-71, ngran-77, ngran-78, ngran-79
           |                 current: utran-1, utran-3, utran-4, utran-6, utran-5, utran-8,
           |                          utran-9, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5,
           |                          eutran-7, eutran-8, eutran-12, eutran-13, eutran-14, eutran-17,
           |                          eutran-18, eutran-19, eutran-20, eutran-25, eutran-26, eutran-28,
           |                          eutran-29, eutran-30, eutran-32, eutran-34, eutran-38, eutran-39,
           |                          eutran-40, eutran-41, eutran-42, eutran-46, eutran-48, utran-19,
           |                          ngran-1, ngran-2, ngran-3, ngran-5, ngran-7, ngran-8, ngran-12,
           |                          ngran-20, ngran-28, ngran-38, ngran-41, ngran-66, ngran-71, ngran-77,
           |                          ngran-78, ngran-79
  -----------------------------------
  

Above is output from OpenWrt/ModemManager. Looks like it shows "Qualcomm" for whatever reason. Not even sure its on latest firmware at this point but its been running solid for a year or 2 (for the most part).

[fabri01]

I have problem with this module using it in a Openwrt VM running on Proxmox. The module works at first boot, but if I turn off VM and restart, the module doesn't work. I get failed to power up MHI controller error -110, and I can't see the wwan0 port in /dev. If I turn off and restart again the VM, now the module works. So every time I have to turn off and restart twice. Why is this happening? How can I fix it?
I have already tried compiling the openwrt kernel and apply the patch to the pci_generic.c file. If I use async inside mhi_pci_probe function I don't get error in dmesg regarding failed power up, but I can't see the module in /dev even if I restart the VM several time. If I use sync function it works one in two time.

[PaddyX]

I have problem with this module using it in a Openwrt VM running on Proxmox. The module works at first boot, but if I turn off VM and restart, the module doesn't work. I get failed to power up MHI controller error -110, and I can't see the wwan0 port in /dev. If I turn off and restart again the VM, now the module works. So every time I have to turn off and restart twice. Why is this happening? How can I fix it?
I have already tried compiling the openwrt kernel and apply the patch to the pci_generic.c file. If I use async inside mhi_pci_probe function I don't get error in dmesg regarding failed power up, but I can't see the module in /dev even if I restart the VM several time. If I use sync function it works one in two time.

There was another item to add to the pci_generic.c I mentioned it:
Sat Mar 11, 2023 9:50 am
Have see a couple of fail to start issues.. I used the - 5000 timeout in the early testing but not since.

In my early testing I had a lot of not starting and showing up. Turned out to be it was just taking its time and the default timeout was too short.. altho I dont have the issue any more would advise trying it.
Had tried to find it before so not sure if this is the one but looks like they had some take even longer and changed it up to 8000:
https://patchwork.kernel.org/project/li ... /#23867447
On cold boot, device can take slightly more than 5 seconds to start.
Increase the timeout to prevent MHI power-up issues.

As for the async this is a must! without it anytime there is an issue it will not be able to restart. This was a huge issue for me when had the firmware crashing a lot and when anything tried to cycle the modem it would not come back! So if you are ever running without this you are looking for trouble!

[BillA]

I have problem with this module using it in a Openwrt VM running on Proxmox. The module works at first boot, but if I turn off VM and restart, the module doesn't work. I get failed to power up MHI controller error -110, and I can't see the wwan0 port in /dev. If I turn off and restart again the VM, now the module works. So every time I have to turn off and restart twice. Why is this happening? How can I fix it?
I have already tried compiling the openwrt kernel and apply the patch to the pci_generic.c file. If I use async inside mhi_pci_probe function I don't get error in dmesg regarding failed power up, but I can't see the module in /dev even if I restart the VM several time. If I use sync function it works one in two time.

Under the System Log look for something like this

Tue Nov 5 01:57:02 2024 : Create PCie 1 Interface Name : 1 /dev/wwan0at0
Tue Nov 5 01:57:02 2024 : Create PCie 1 Interface Name : 2 /dev/wwan0mbim0
Tue Nov 5 01:57:02 2024 : Create PCie 1 Interface Name : 3 /dev/wwan0qcdm0
Tue Nov 5 01:57:02 2024 : Create PCie 1 Interface Name : 4 /dev/wwan0qmi0

In the latest GoldenOrb, PCIe devices are wwan0at0 symbolic linked to ttyUSB92.
During a soft boot it may show up as ttyUSB, but on hard boot as ttyUSB92, both pointing to wwan0at0.