X55 T99W175 modem

[fabri01]

I found out 4pda figured out how to enable USB mode. You have to bridge the leftmost pads on the back. You might need to cover the pads for CONFIG_3 on certain adapters or boards but didn't have to on mine.
you also might want to switch it to the Thales MV31 customer id using AT^CUSTOMER=14. It's only USB2.0 so you're probably limited to under 400Mbps.

I've tested it for a bit and it works well with ModemManager. I think it should also work out of the box on OpenWRT given it's a standard QMI or MBIM interface over USB just like the T77W968. If you can get this working over PCIe it's even better since you aren't capped by USB2.

Can you explain how you did the hardware modification? Is it something difficult? Is it possible to revert the mod and return to PCIe mode?
I read that there is an AT command that can switch the module in USB mode. Which module brand have you tested it? Is it working without any hardware modifications? I have bought a Dell DW5930e and it will arrive in 3 weeks.

[Transfluxor]

Hello guys, to enable USB 2.0, I do not recommend soldering a jumper; it is better to solder a 10-15k resistor 0402.
https://4pda.to/forum/index.php?showtop ... =129461423
If you solder the jumper and poorly insulate pin 3, you can burn the modem.
If you solder a resistor, then nothing bad will happen to the modem - if you don’t isolate pin 3, the USB simply won’t turn on because pin 3 will sit on the ground. If you need PCIe mode, then with a soldered resistor, you can simply remove the insulation from pin 3 and the USB mode will be disabled.
To insulate the pin I use polyimide tape.

Yes, there is also such a moment - for some engineering samples of T99W175 pin 3 is just ground and there is no point in touching it.
But in any case, it is better to solder a resistor.

[PaddyX]

First of all, thanks for your answer. I would like to ask a couple of questions:
1) I've found a cheaper DELL DW5930e Foxconn T99W175 X55. Is this working with OpenWRT or Linux?
2) Is your HP branded T99 not working with OpenWRT?
3) I would prefer to run the module in PCIe mode in order to get max speed. I have a desktop PC and i've found this adapter: https://www.ebay.it/itm/374929149444?mk ... media=COPY
Do you think it will work or do you have any pcie adapter to recommend me?
4) Does the AT command to put the module in USB mode without soldering works?

1) Linux would be better
2) Last test HP was still not working by defauil (would have to do some compiling)
3) Think have seen mention of that adapter before, If system has the stadard pci slot they expect it should work (cant guarentee)
4) As stated in the last post above: If pin 3 is grounded then it is hard set in PCI.. Most of these modems are in this format.

[BillA]

Hello guys, to enable USB 2.0, I do not recommend soldering a jumper; it is better to solder a 10-15k resistor 0402.
https://4pda.to/forum/index.php?showtop ... =129461423
If you solder the jumper and poorly insulate pin 3, you can burn the modem.
If you solder a resistor, then nothing bad will happen to the modem - if you don’t isolate pin 3, the USB simply won’t turn on because pin 3 will sit on the ground. If you need PCIe mode, then with a soldered resistor, you can simply remove the insulation from pin 3 and the USB mode will be disabled.
To insulate the pin I use polyimide tape.

Yes, there is also such a moment - for some engineering samples of T99W175 pin 3 is just ground and there is no point in touching it.
But in any case, it is better to solder a resistor.

Reading the translated 4PDA thread, not sure if this is the right method... correct me if I'm wrong.
https://4pda-to.translate.goog/forum/in ... y129097775

The edge connector's red pin in this pic needs to be covered with either Kapton tape, or several layers of conformal coating.




Then the pins in the red circled either shorted, or better yet jumpered with a 1 Kohm resistor for safety.

[Transfluxor]

Reading the translated 4PDA thread, not sure if this is the right method... correct me if I'm wrong.
https://4pda-to.translate.goog/forum/in ... y129097775

That's right, on the front side of the module there are odd pins from right to left - 1,3,5,7...
I would rather cover pin 3 with Kapton tape; if the USB mode is not needed, it’s easier to remove the tape. In general, I installed/removed the T99W175 modem many times (30-40 at least), the adhesive tape did not go away.
The left pin in the circle is the Vcc power supply, the right one is pin 3, which is connected inside the modem as I think to GPIO.
You can install whatever resistor you want, but even with 15k it works without problems.
There is another option to cut off the GND line from pin 3 on the USB adapter. Or additionally solder 3.3V through a resistor to pin 3 of M2 Key B cut off from GND. Then there will be no need to solder anything on the modem itself.

[BillA]

Reading the translated 4PDA thread, not sure if this is the right method... correct me if I'm wrong.
https://4pda-to.translate.goog/forum/in ... y129097775

That's right, on the front side of the module there are odd pins from right to left - 1,3,5,7...
I would rather cover pin 3 with Kapton tape; if the USB mode is not needed, it’s easier to remove the tape. In general, I installed/removed the T99W175 modem many times (30-40 at least), the adhesive tape did not go away.
The left pin in the circle is the Vcc power supply, the right one is pin 3, which is connected inside the modem as I think to GPIO.
You can install whatever resistor you want, but even with 15k it works without problems.
There is another option to cut off the GND line from pin 3 on the USB adapter. Or additionally solder 3.3V through a resistor to pin 3 of M2 Key B cut off from GND. Then there will be no need to solder anything on the modem itself.

I think a 1-10K resistor would make a good protection just in case (it's TTL lines so there's no high Amps there). Plus it would allow switching between the modes easily by simply covering or removing the pin cover.
I'm just a bit confused about the modes, so with the pin covered and a short or resistor in place it's USB mode.
What' the exact name of the other mode when the pin is not covered/grounded? Is it PCI or some other funky sh*t? hehe
Any why is it that for some an AT-command is enough to switch modes?

[Transfluxor]

I think a 1-15K resistor would make a good protection just in case (it's TTL lines so there's no high Amps there). Plus it would allow switching between the modes easily by simply covering or removing the pin cover.
I'm just a bit confused about the modes, so with the pin covered and a short or resistor in place it's USB mode.
What' the exact name of the other mode when the pin is not covered/grounded? Is it PCI or some other funky sh*t? hehe
Any why is it that for some an AT-command is enough to switch modes?

The resistor is not installed because of the TTL line, but because of protection against a possible short circuit between Vcc and GND INSIDE the modem. If there is low resistance, the resistor will heat up. It’s up to you to decide.
Regarding the modem configuration commands, you yourself gave a link to 4pda. It’s all written there, I’m too lazy to explain it here.

[fabri01]

I really should just pony up like PaddyX and build my own OpenWRT release and fixup the module but I'm really being lazy and idealistic and don't want to spend the time on it nor do I want to have an OpenWRT instance with kernel headers and gcc bloating it all up. Anyway, here's to hoping that script does the trick!

I've built Openwrt with the power patch and 6.1 kernel.It was not that hard and long (perhaps the first time compile took a bit longer) and some time to figure out how to apply the patch via quilt.
Though I'm still waiting for my T99W175 to arrive, I've flashed the image to new mini pc and plugged the USB with T77W968 - all well.

Can you explain the steps to build Openwrt image with the power patch?

[fabri01]

Many thanks, got it and will be investingating it

Try AT^PCIEMODE=0. Works without soldering on a different module of mine. It's mentioned by nok3 on 4pda. (I wasn't sure if it was fine to link so I didn't link it)

Hi, in which brand version of the module did you tried the AT^PCIEMODE=0?
I bought a Dell DW5930e and I would like to know if it is possible to use in USB mode without having to do the hardware modifications

[BillA]

Many thanks, got it and will be investingating it

Try AT^PCIEMODE=0. Works without soldering on a different module of mine. It's mentioned by nok3 on 4pda. (I wasn't sure if it was fine to link so I didn't link it)

Hi, in which brand version of the module did you tried the AT^PCIEMODE=0?
I bought a Dell DW5930e and I would like to know if it is possible to use in USB mode without having to do the hardware modifications

Just try the AT-command and if it's not switching to USB mode then you need to make the hardware mod.

[fabri01]

I've received the module and I am trying to get it working in OpenWRT and debian. Right now both of them show this error in dmesg:

Code: Select all

mhi-pci-generic 0000:06:10.0: MHI PCI device found: foxcom-sdx55
mhi-pci-generic 0000:06:10.0: BAR 0: assigned Imem 0xc1600000-0xc1600fff 64bit]
mhi-pci-generic 0000:06:10.0: using shared MSI
mhi mhiO: Requested to power ON
mhi mhi0: Power on setup success
mhi mhi0: Direct firmware load for qcom/sdx55m/sbl.mbn failed with error -2
mhi mhiO: Falling back to sysfs fallback for: qcom/sdx55m/sbl1.mbn
mhi mhi0: Error loading firmware: -12
mhi-pci-generic 0000:06:10.0: failed to power up MHI controller
mhi-pci-generic: probe of 0000:06:10.0 failed with error -110

How can I fix it?

[BillA]

I've received the module and I am trying to get it working in OpenWRT and debian. Right now both of them show this error in dmesg:

Code: Select all

mhi-pci-generic 0000:06:10.0: MHI PCI device found: foxcom-sdx55
mhi-pci-generic 0000:06:10.0: BAR 0: assigned Imem 0xc1600000-0xc1600fff 64bit]
mhi-pci-generic 0000:06:10.0: using shared MSI
mhi mhiO: Requested to power ON
mhi mhi0: Power on setup success
mhi mhi0: Direct firmware load for qcom/sdx55m/sbl.mbn failed with error -2
mhi mhiO: Falling back to sysfs fallback for: qcom/sdx55m/sbl1.mbn
mhi mhi0: Error loading firmware: -12
mhi-pci-generic 0000:06:10.0: failed to power up MHI controller
mhi-pci-generic: probe of 0000:06:10.0 failed with error -110

How can I fix it?

Try this command: AT^PCIEMODE=0
Repower the router/modem and check if you're still getting an error.
If yes, then try the hardware mod.

[fabri01]

Try this command: AT^PCIEMODE=0
Repower the router/modem and check if you're still getting an error.
If yes, then try the hardware mod.

I don't want to use it in USB mode, I want to use it in PCIe mode

[BillA]

Try this command: AT^PCIEMODE=0
Repower the router/modem and check if you're still getting an error.
If yes, then try the hardware mod.

I don't want to use it in USB mode, I want to use it in PCIe mode

There's not a huge speed difference, sometimes you gotta use what works.

[mtl26637]

FCC locked? Did you make sure to unlock? Pretty sure we've covered how to in this thread at some point. I know its in one of the T99W175 threads here on site. Check ModemManager FCC unlock procedure page for specifics. Anytime you see MHI power up failure its more than likely something to do with the FCC lock.

[fabri01]

FCC locked? Did you make sure to unlock? Pretty sure we've covered how to in this thread at some point. I know its in one of the T99W175 threads here on site. Check ModemManager FCC unlock procedure page for specifics. Anytime you see MHI power up failure its more than likely something to do with the FCC lock.

Fixed the problem. I had to execute the QTUNER AT command. Now I am able to use it in PCIe Mode reaching 500Mbit in 5G indoor.

[fabri01]

I used to get that power-up issue on my VM too, I don't think that is necessarily directly tied to FCC Unlocking

I ended up writing a VM hook to power cycle and disconnect the modem when the VM powered up which took care of it but hell I might try USB mode anyway, that would solve some cabling frustrations

Here's that script for anyone else VM'ing this thing. You will need to update the path to whatever your actual PCI ID is

#!/bin/bash

Code: Select all

if [ $2 == "pre-start" ]
then
    echo "modem-hookscript: Resetting Modem for Virtual Machine $1"
    echo 0 > /sys/bus/pci/devices/0000\:02\:00.0/power_state
    echo 1 > /sys/bus/pci/devices/0000\:02\:00.0/power_state
    echo 1 > /sys/bus/pci/devices/0000\:02\:00.0/remove
    echo 1 > /sys/bus/pci/rescan
fi

Can you explain me better what does the script do? I imagine that I should use it in OpenWRT VM. Does the script turn off the module (PCI device) and then restart it?

[fabri01]

I have a Dell T99W175 DW5930e with T99W175.F0.1.0.0.9.GC.004.065 firmware and I am using it in PCI mode.
With 065 firmware I found a bug: I am not able to see 4CA band (20+3+7+1) with AT^CA_INFO neither with AT^DEBUG. Only three of them are shown. Is it only a graphical issue or does the module not connect with 4CA? Is this issue fixed in newer firmware version?

I have found online rev096 firmware by Lenovo and someone say that I can use Lenovo firmware on Dell, is it true? Does someone tried it?

[fabri01]

I have found online rev096 firmware by Lenovo and someone say that I can use Lenovo firmware on Dell, is it true? Does someone tried it?

I may be oversimplifying this, but the take I've got on this module is that it doesn't matter who oem'd yours, you can change customer mode and it'll become the other device. Change customer to Dell and run the firmware update then change customer back to Lenovo, assuming the Lenovo mode is preferable for your connectivity

So if I have Dell module and I want to install Lenovo firmware, do I need to change customer or do I just install the firmware without having to change customer?

[fabri01]

I used to get that power-up issue on my VM too, I don't think that is necessarily directly tied to FCC Unlocking

I ended up writing a VM hook to power cycle and disconnect the modem when the VM powered up which took care of it but hell I might try USB mode anyway, that would solve some cabling frustrations

Here's that script for anyone else VM'ing this thing. You will need to update the path to whatever your actual PCI ID is

#!/bin/bash

Code: Select all

if [ $2 == "pre-start" ]
then
    echo "modem-hookscript: Resetting Modem for Virtual Machine $1"
    echo 0 > /sys/bus/pci/devices/0000\:02\:00.0/power_state
    echo 1 > /sys/bus/pci/devices/0000\:02\:00.0/power_state
    echo 1 > /sys/bus/pci/devices/0000\:02\:00.0/remove
    echo 1 > /sys/bus/pci/rescan
fi

I've tried executing those command on proxmox via SSH, but I am getting Permission Denied. After obtaining permission with chmod, now I get write error: Input/output error

[PaddyX]

Hello All, finaly back and got my 2nd modem.. Had a quesion, the lenovo modem, is there somthing that has to be done to get its firmware to update?
I have tried many times and cant seem to get it to trigger.

Currently Windows reports:
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

Looked like the latest was: T99W175.F0.1.0.0.9.VF.008.096 from nz7wn09w.exe
In cross checking it looks like there may be a couple of differnt versions with differt FW numbers..
Have tried several re-installs n reboots, also do have the sim in as did see it looks like if the sim is not there it wont trigger firmware upgrade.. This got me wandering if even that i have a sim in it does not like somthing about it.. Sim is Vodafone but my not recognise the one from country am in.. as did see:
The following firmware versions are included in this release.
Network Firmware Version
---------------- -----------------------------
Generic T99W175.F0.1.0.0.9.GC.004.096
AT&T T99W175.F0.1.0.0.9.AT.009.096
China Mobile T99W175.F0.1.0.0.9.CC.005.096
China Telecom T99W175.F0.1.0.0.9.CT.005.096
China Unicom T99W175.F0.1.0.0.9.CU.005.096
Deustche Telekom T99W175.F0.1.0.0.9.DT.003.096
Docomo T99W175.F0.1.0.0.9.DO.007.096
EE T99W175.F0.1.0.0.9.EE.002.096
Firstnet T99W175.F0.1.0.0.9.A2.009.096
KDDI T99W175.F0.1.0.0.9.KD.008.096
Orange T99W175.F0.1.0.0.9.OG.005.096
Rakuten T99W175.F0.1.0.0.9.RT.002.096
Softbank T99W175.F0.1.0.0.9.SB.010.096
Swisscom T99W175.F0.1.0.0.9.SC.005.096
Telefonica T99W175.F0.1.0.0.9.TF.008.096
Telstra T99W175.F0.1.0.0.9.TE.008.096
TIM T99W175.F0.1.0.0.9.TM.002.096
TMobile T99W175.F0.1.0.0.9.TO.006.096
Verizon T99W175.F0.1.0.0.9.VZ.009.096
Vodafone T99W175.F0.1.0.0.9.VF.008.096

[PaddyX]

hmm, yea for my HP ver it was just part of the driver install but try as might the lenovo one is not interested and nothing in the logs to show it is even trying or doing any check. Some items made it sound like would happen after a reboot but still nada. And yes was on windows and the same system had done the HP on. Not sure if somthing else is blocking. Tried seeing if was some old HP software blocking but could not see anything. Will have another look over.
Managed to find the FW file on its own so looking into manual flashing.

[fabri01]

I've tried executing those command on proxmox via SSH, but I am getting Permission Denied. After obtaining permission with chmod, now I get write error: Input/output error

You don't execute the commands via ssh, you reference it in the vm.conf file. Additionally you need to determine your device path because mine is unlikely to be the same as yours. It works with my environment which is running VE 8.2.

I have followed the guide to add a hookscript to a VM, but after starting openwrt VM proxmox crash and I have to force reboot the PC. I have executed this command to add the script to the vm: qm set 100 --hookscript local:snippets/hook.sh

Do I need to write your script in .sh file or .pl file?

[fabri01]

Do I need to write your script in .sh file or .pl file?

Yes, you have to put the script into the file you are referencing. local:snippets/hook.sh

Keep on hacking, you're getting close. Still though, seriously consider using this module in USB mode for your own sanity.

I've built openwrt image and kernel from source and applied the power patch and the modem seem to be stable. I am getting more than 400Mbit in Download. The only issue I am facing is that, if I poweroff openwrt VM, then the next start the module doesn't work (I get mhi power up error), so I need to power off the VM, and restart again. The second time always works.

[fabri01]

Do I need to write your script in .sh file or .pl file?

Yes, you have to put the script into the file you are referencing. local:snippets/hook.sh

Keep on hacking, you're getting close. Still though, seriously consider using this module in USB mode for your own sanity.

Tried again, but I get error when starting the VM due to permission denied. If I execute chmod 777 on the pci device path, I get input/output error

[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.

[Gadget]

I found out 4pda figured out how to enable USB mode. You have to bridge the leftmost pads on the back. You might need to cover the pads for CONFIG_3 on certain adapters or boards but didn't have to on mine.
you also might want to switch it to the Thales MV31 customer id using AT^CUSTOMER=14. It's only USB2.0 so you're probably limited to under 400Mbps.

I've tested it for a bit and it works well with ModemManager. I think it should also work out of the box on OpenWRT given it's a standard QMI or MBIM interface over USB just like the T77W968. If you can get this working over PCIe it's even better since you aren't capped by USB2.

Hi Hikaru or anyone else, can you point me in the direction of a tutorial which will show me how to enable USB support for the T99W175.43 please.

Also is the USB2 limitation stemming from the modem controller itself once enabled ?