Wireless Joint

Posted: **Thu Mar 09, 2023 6:56 am**

mtl26637 wrote: Wed Mar 08, 2023 5:52 pm First click of the download button results in a box that pops up and wants a serial number. LOL, I clicked the "download" button a second time and it started the download.

oh my

lol didnt think to do that!
So 1st pass on looking through the file.. could not see it easily.
There is a log file created for the install process but I dont have the modem so was not able to see any info on firmware install.
Need to find someone with it on a windows box and get them to install or check the folder from there last install for: log.txt

Will take another look over the HP install process today and see if can spot anything.. Unfortunately I have the latest HP one in place so it may skip it..
Half tempted to see what the Lenono process would think of the HP modem but would rather not break things..

Posted: **Thu Mar 09, 2023 1:40 pm**

Woooooot! Significant step forward! I hope!
Managed to free up the gear so could test further and after pain with the one sim yanked the one from my phone on that is probably the best network here.. well initial ping was great and performance was ok. (a that is after fixing the DNS yet again!)
Reboot and all hell breaks loose!!!!!

In testing tried got to point of disabling the modem and still the lag was there and bad!
nslookup was okish but slow for ip4 dns but then would take ages to get the ip6.. long story short..

Tried to enable dns caching and one of the step called for disabling systemd-resolved

after that naturally DNS was gone..

Deleted the linked resolf.conf and created a new file and populated......
Dang! ping is now better than ever!

Will test a few more reboots and have one last item need to get sorted if can get that then all reboot issues will be out the way and will try for moving to main router/antenna (areal points would be 1+2 too external pair and 3-4 to remote internal pair in a good spot)

Posted: **Fri Mar 10, 2023 3:20 pm**

Ok still some gremlins in the works but getting better..
The 2nd issue of making sure wwan is always default route is now stable..

The 1st issue.. Well while when is good is still lot better since the dns stuff was fixed! But
Restart/Reboots Seems when the system/modem starts its a 50/50 things will not be happy.
Also best to used shutdown -now as other reboot options are less likly to be ok..
This last reboot things were slow.. Firmware crashed after about 5 min and once firmware reloaded performance was great!

Looking through the logs looks like the driver signing didn't work properly so may need to re-build the MHI side again..
Slowly getting better.. Would love to know what firmware version was in that latest lenovo driver!

Posted: **Fri Mar 10, 2023 5:37 pm**

Am trying to use the lt4120 with the 6.2 Kernel with fedora 37 VM

Code: Select all

bash-5.2# uname -r
6.2.2-300.fc37.x86_64
mmcli 1.20.2
qmicli 1.32.2
mbimcli 1.28.2
bash-5.2# lspci | grep Wireless
00:05.0 Wireless controller [0d40]: Device 03f0:0a6c
bash-5.2# ls /dev | grep wwan
wwan0at0
wwan0at1
wwan0mbim0
wwan0qcdm0

but mmcli and qmicli put out errors. Cant even get ModemManager Debug mode to start as long as the Device is connected.

Code: Select all

bash-5.2# mmcli -G DEBUG
error: couldn't set logging level: 'Timeout was reached'
bash-5.2# qmicli -d /dev/wwan0mbim0 -w
error: couldn't open the QmiDevice: Cannot open device file '/dev/wwan0mbim0': Input/output error

i do remember eskaryo using proxmox. Did you have to pass through additional devices or do anything else special to get the modem running within a container?

My plan was to make a pull request for ModemManager 1.21.x to support fcc unlock for the HP pid out of the box but now im kinda stuck

bash-5.2# journalctl | grep mhi
Mar 11 00:23:54 fedora kernel: mhi-pci-generic 0000:00:05.0: MHI PCI device found: foxconn-sdx55
Mar 11 00:23:54 fedora kernel: mhi-pci-generic 0000:00:05.0: BAR 0: assigned [mem 0xf2000000-0xf2000fff 64bit]
Mar 11 00:23:54 fedora kernel: mhi-pci-generic 0000:00:05.0: using shared MSI
Mar 11 00:23:54 fedora kernel: mhi mhi0: Requested to power ON
Mar 11 00:24:14 muhannad kernel: mhi mhi0: Failed to reset MHI due to syserr state
Mar 11 00:24:14 muhannad kernel: mhi-pci-generic 0000:00:05.0: failed to power up MHI controller
Mar 11 00:24:14 muhannad kernel: mhi-pci-generic: probe of 0000:00:05.0 failed with error -110

Quick Websearch led me to another T99W175 user fixing this by increasing the "MHI_POST_RESET_DELAY_MS equals to 2000ms" now i have to find out how the hell i am doing this the easiest way for troubleshooting

Has anyone of you ever get into an error like this?

Posted: **Fri Mar 10, 2023 6:28 pm**

Code: Select all

bash-5.2# /sys/bus/pci/devices/0000:00:05.0/reset
bash: /sys/bus/pci/devices/0000:00:05.0/reset: No such file or directory
bash-5.2# echo 1 >/sys/bus/pci/devices/0000:00:05.0/remove
bash-5.2# echo 1 >/sys/bus/pci/rescan
bash-5.2# journalctl | grep mhi
Mar 11 00:24:14 muhannad kernel: mhi-pci-generic: probe of 0000:00:05.0 failed with error -110
Mar 11 01:00:18 muhannad kernel: mhi-pci-generic 0000:00:05.0: MHI PCI device found: foxconn-sdx55
Mar 11 01:00:18 muhannad kernel: mhi-pci-generic 0000:00:05.0: BAR 0: assigned [mem 0xf2000000-0xf2000fff 64bit]
Mar 11 01:00:18 muhannad kernel: mhi-pci-generic 0000:00:05.0: using shared MSI
Mar 11 01:00:18 muhannad kernel: mhi mhi0: Requested to power ON
Mar 11 01:00:40 muhannad kernel: mhi mhi0: Failed to reset MHI due to syserr state
Mar 11 01:00:40 muhannad kernel: mhi-pci-generic 0000:00:05.0: failed to power up MHI controller
Mar 11 01:00:40 muhannad kernel: mhi-pci-generic: probe of 0000:00:05.0 failed with error -110

Lokks like

-#define MHI_POST_RESET_DELAY_MS 500
+#define MHI_POST_RESET_DELAY_MS 2000

aint my Problem AFAIK the fix already made it into [url=
https://git.kernel.org/pub/scm/linux/ke ... acb7419d8a]5.16[/url]

Posted: **Sat Mar 11, 2023 3:50 am**

Have see a couple of fail to start issues.. I used the - 5000 timeout in the early testing but not since.

The biggest improvement I had was:
+++ b/drivers/bus/mhi/pci_generic.c
@@ -637,7 +637,7 @@ static void mhi_pci_recovery_work(struct work_struct *work)
if (err)
goto err_try_reset;

- err = mhi_sync_power_up(mhi_cntrl);
+ err = mhi_async_power_up(mhi_cntrl);
if (err)
goto err_unprepare;

This turned from fail to start on the reboot too starts every time on reboot.. Previous to this I had to hard power power the system every time!

There was another fix as well I need to sort out for stability. It is around modemmanager where it connects with all available protocols so if have mbim and QMI then it will use both. The modem gets into a state due to both protocols active. Cant Find the details at the moment. I found details of in on lenovo site were they had figured it out and fixed it.

EDIT: Working on a list of all these nigly things as have seen all to often small things can have far reaching impacts so good to get them addressed!
A current need is also to find a command line on how to force MM to reload its drivers for full modem restart while system is up..

Posted: **Sat Mar 11, 2023 11:37 am**

Thank you! i remember reading about something where QMI and MBIM where blocking each other or something like that.. ill also take a look for that Link. I tried every way that got into my mind starting that Modem, Soft Reset, Hard Reset Cold Start. Never got it recognized by ModemManager. Was really hoping i could get around compiling the Kernel by Myself now where 6.2 is already available... Isn't there any way to test this with a command or config file or whatnot? I have tried the async command in ModemManager but that's something different than doing it on the Driver Level i guess

echo 1 >/sys/bus/pci/devices/0000:00:05.0/remove
echo 1 >/sys/bus/pci/rescan

propably aint what you where looking for restarting the modem?

Making a list sounds like a great idea! IMO it would be nice to post the fixes like:

+++ b/drivers/bus/mhi/pci_generic.c
@@ -637,7 +637,7 @@ static void mhi_pci_recovery_work(struct work_struct *work)
if (err)
goto err_try_reset;

- err = mhi_sync_power_up(mhi_cntrl);
+ err = mhi_async_power_up(mhi_cntrl);
if (err)
goto err_unprepare;

at the Github Page of the mhi Driver as a Commit or whatever.. you have already done all the Work testing and posting the patched Code so lets share it with the Developers? https://github.com/torvalds/linux/blob/ ... _generic.c is this the right link?

Fedora is doing a TestWeek of the new 6.2 Kernel till Thursday, i will propose your fixes to them and see what they say if that's okey with you?

Will try to figure our how to compile that Kernel for the next 6 hours to 6 years

Got a Error i never seen before after a fresh install of fedora 37 with 6.2.3 Kernel " mhi_wwan_mbim: probe of mhi0_IP_HW0_MBIM failed with error -5"

bash-5.2# dmesg | grep mhi
[ 4.012104] mhi-pci-generic 0000:00:05.0: MHI PCI device found: foxconn-sdx55
[ 4.013219] mhi-pci-generic 0000:00:05.0: BAR 0: assigned [mem 0xf2000000-0xf2000fff 64bit]
[ 4.024154] mhi-pci-generic 0000:00:05.0: using shared MSI
[ 4.045766] mhi mhi0: Requested to power ON
[ 4.045801] mhi mhi0: Power on setup success
bash-5.2# lspci | grep wireless
bash-5.2# lspci | grep Wireless
00:05.0 Wireless controller [0d40]: Device 03f0:0a6c
bash-5.2# journalctl | grep mhi
Mar 11 09:58:11 fedora kernel: mhi-pci-generic 0000:00:05.0: MHI PCI device found: foxconn-sdx55
Mar 11 09:58:11 fedora kernel: mhi-pci-generic 0000:00:05.0: BAR 0: assigned [mem 0xf2000000-0xf2000fff 64bit]
Mar 11 09:58:11 fedora kernel: mhi-pci-generic 0000:00:05.0: using shared MSI
Mar 11 09:58:11 fedora kernel: mhi mhi0: Requested to power ON
Mar 11 09:58:11 fedora kernel: mhi mhi0: Power on setup success
Mar 11 09:58:31 muhannad kernel: mhi_wwan_mbim mhi0_IP_HW0_MBIM: 100: Failed to receive START channel command completion
Mar 11 09:58:31 muhannad kernel: mhi_wwan_mbim mhi0_IP_HW0_MBIM: 101: Failed to reset channel, still resetting
Mar 11 09:58:31 muhannad kernel: mhi_wwan_mbim mhi0_IP_HW0_MBIM: 100: Failed to reset channel, still resetting
Mar 11 09:58:31 muhannad kernel: mhi_wwan_mbim: probe of mhi0_IP_HW0_MBIM failed with error -5
Mar 11 09:58:33 muhannad kernel: mhi_wwan_ctrl mhi0_DUN2: 92: Failed to receive START channel command completion
Mar 11 09:58:54 muhannad kernel: mhi_wwan_ctrl mhi0_DUN: 32: Failed to receive START channel command completion
bash-5.2# mmcli -V
mmcli 1.20.2
Copyright (2011 - 2022) Aleksander Morgado
License GPLv2+: GNU GPL version 2 or later <http://gnu.org/licenses/gpl-2.0.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

bash-5.2# mmcli -S
error: couldn't request to scan devices: 'Timeout was reached'
bash-5.2# mmcli -S
successfully requested to scan devices
bash-5.2# mmcli -L
error: couldn't create manager: Timeout was reached
bash-5.2# mmcli -L
error: couldn't create manager: Timeout was reached
bash-5.2# dmesg | grep mhi
[ 4.012104] mhi-pci-generic 0000:00:05.0: MHI PCI device found: foxconn-sdx55
[ 4.013219] mhi-pci-generic 0000:00:05.0: BAR 0: assigned [mem 0xf2000000-0xf2000fff 64bit]
[ 4.024154] mhi-pci-generic 0000:00:05.0: using shared MSI
[ 4.045766] mhi mhi0: Requested to power ON
[ 4.045801] mhi mhi0: Power on setup success
[ 24.216910] mhi_wwan_mbim mhi0_IP_HW0_MBIM: 100: Failed to receive START channel command completion
[ 24.216998] mhi_wwan_mbim mhi0_IP_HW0_MBIM: 101: Failed to reset channel, still resetting
[ 24.217035] mhi_wwan_mbim mhi0_IP_HW0_MBIM: 100: Failed to reset channel, still resetting
[ 24.217082] mhi_wwan_mbim: probe of mhi0_IP_HW0_MBIM failed with error -5
[ 26.777091] mhi_wwan_ctrl mhi0_DUN2: 92: Failed to receive START channel command completion
[ 47.257021] mhi_wwan_ctrl mhi0_DUN: 32: Failed to receive START channel command completion
[ 67.737111] mhi_wwan_ctrl mhi0_DIAG: 4: Failed to receive START channel command completion
[ 88.217023] mhi_wwan_ctrl mhi0_DUN2: 92: Failed to receive START channel command completion
[ 108.697096] mhi_wwan_ctrl mhi0_DUN: 32: Failed to receive START channel command completion
[ 129.177097] mhi_wwan_ctrl mhi0_DUN2: 92: Failed to receive START channel command completion
[ 129.177202] mhi_wwan_ctrl mhi0_MBIM: 12: Failed to receive START channel command completion
[ 149.657103] mhi_wwan_ctrl mhi0_DUN: 32: Failed to receive START channel command completion
[ 170.137051] mhi_wwan_ctrl mhi0_DUN2: 92: Failed to receive START channel command completion
[ 190.617066] mhi_wwan_ctrl mhi0_DUN: 32: Failed to receive START channel command completion
[ 264.857076] mhi_wwan_ctrl mhi0_DUN2: 92: Failed to receive START channel command completion
[ 285.337085] mhi_wwan_ctrl mhi0_DUN: 32: Failed to receive START channel command completion
[ 305.816929] mhi_wwan_ctrl mhi0_DIAG: 4: Failed to receive START channel command completion
bash-5.2# journalctl | grep mhi
Mar 11 09:58:11 fedora kernel: mhi-pci-generic 0000:00:05.0: MHI PCI device found: foxconn-sdx55
Mar 11 09:58:11 fedora kernel: mhi-pci-generic 0000:00:05.0: BAR 0: assigned [mem 0xf2000000-0xf2000fff 64bit]
Mar 11 09:58:11 fedora kernel: mhi-pci-generic 0000:00:05.0: using shared MSI
Mar 11 09:58:11 fedora kernel: mhi mhi0: Requested to power ON
Mar 11 09:58:11 fedora kernel: mhi mhi0: Power on setup success
Mar 11 09:58:31 muhannad kernel: mhi_wwan_mbim mhi0_IP_HW0_MBIM: 100: Failed to receive START channel command completion
Mar 11 09:58:31 muhannad kernel: mhi_wwan_mbim mhi0_IP_HW0_MBIM: 101: Failed to reset channel, still resetting
Mar 11 09:58:31 muhannad kernel: mhi_wwan_mbim mhi0_IP_HW0_MBIM: 100: Failed to reset channel, still resetting
Mar 11 09:58:31 muhannad kernel: mhi_wwan_mbim: probe of mhi0_IP_HW0_MBIM failed with error -5
Mar 11 09:58:33 muhannad kernel: mhi_wwan_ctrl mhi0_DUN2: 92: Failed to receive START channel command completion
Mar 11 09:58:54 muhannad kernel: mhi_wwan_ctrl mhi0_DUN: 32: Failed to receive START channel command completion
Mar 11 09:59:14 muhannad kernel: mhi_wwan_ctrl mhi0_DIAG: 4: Failed to receive START channel command completion
Mar 11 09:59:35 muhannad kernel: mhi_wwan_ctrl mhi0_DUN2: 92: Failed to receive START channel command completion
Mar 11 09:59:55 muhannad kernel: mhi_wwan_ctrl mhi0_DUN: 32: Failed to receive START channel command completion
Mar 11 10:00:16 muhannad kernel: mhi_wwan_ctrl mhi0_DUN2: 92: Failed to receive START channel command completion
Mar 11 10:00:16 muhannad kernel: mhi_wwan_ctrl mhi0_MBIM: 12: Failed to receive START channel command completion
Mar 11 10:00:36 muhannad kernel: mhi_wwan_ctrl mhi0_DUN: 32: Failed to receive START channel command completion
Mar 11 10:00:57 muhannad kernel: mhi_wwan_ctrl mhi0_DUN2: 92: Failed to receive START channel command completion
Mar 11 10:01:17 muhannad kernel: mhi_wwan_ctrl mhi0_DUN: 32: Failed to receive START channel command completion
Mar 11 10:02:31 muhannad kernel: mhi_wwan_ctrl mhi0_DUN2: 92: Failed to receive START channel command completion
Mar 11 10:02:52 muhannad kernel: mhi_wwan_ctrl mhi0_DUN: 32: Failed to receive START channel command completion
Mar 11 10:03:12 muhannad kernel: mhi_wwan_ctrl mhi0_DIAG: 4: Failed to receive START channel command completion
Mar 11 10:03:33 muhannad kernel: mhi_wwan_ctrl mhi0_MBIM: 12: Failed to receive START channel command completion
Mar 11 10:03:33 muhannad kernel: mhi_wwan_ctrl mhi0_DUN2: 92: Failed to receive START channel command completion
bash-5.2#

Posted: **Sat Mar 11, 2023 12:12 pm**

Feel free to mention items found and pointed out!
Pain I also see is many thing have been fixed here and there but are very slow getting into main builds and some shortly after being added get overwritten and lost again!

Futher: sync vs async mentioned! Make sure it is the correct instance as the line is found in two places and only needs the the correct one
https://lore.kernel.org/all/bb0efc0dbc4 ... urora.org/

Also if they could finally get the HP ID in place so compiling is not needed at all!!
There was quite some work done to pull as much as possible together on git and add a load of ID's:
https://yhbt.net/lore/all/2021031612423 ... gmail.com/

For the disable MBIM in modemmanager. Cant seem to find the original discussion for it but wondering if the following was a part of the work done and they did take a revised piece of work to get it fixed..
https://www.openembedded.org/pipermail/ ... 18163.html
Will keep on searching as want to capture the fill details.

One would have liked is to be able to make these config changed without having to re-compile everything!

RE"echo 1 >/sys/bus/pci/devices/0000:00:05.0/remove
echo 1 >/sys/bus/pci/rescan

propably aint what you where looking for restarting the modem?"

Will test it out, may be of interest as found just telling the OS to turn the device off did not change the state of the modem and with that normally a reboot is a way to do a complete reload if that does the same it may be of interest. Thanks!!

Posted: **Sat Mar 11, 2023 12:21 pm**

RE: " mhi_wwan_mbim: probe of mhi0_IP_HW0_MBIM failed with error -5"
Found mentioned in https://github.com/openwrt/mt76/issues/548
https://access.redhat.com/solutions/1131503
Altho looks like it should have been fixed by the version you are on.. unless is one that overwrote again... but is couple of people saying works in some versions and not others.. Also seems was seen around Wifi
hmmmmm
EDIT: Looks like what they had was on USB but would not surprise me if some common code was on the PCI side..
https://bugzilla.redhat.com/show_bug.cgi?id=453171

Posted: **Sat Mar 11, 2023 1:58 pm**

I guess now would be a good time to ask for getting those fixes into mainbuild as one of the 6.2 Kernels Changelog entrys was adding support for HP X55 Modem PID in the Driver.

Before i dive into building the Kernel and ModemManager i would like to test the Modem in an Windows VM just to make sure its not broken and can actually be used the way i set it up. My guess would be that the modem still has the Firmware installed that it was initially shipped with.

Will take another look over the HP install process today and see if can spot anything.. Unfortunately I have the latest HP one in place so it may skip it..
Half tempted to see what the Lenono process would think of the HP modem but would rather not break things..

What did you have in Mind i could look for in that process?

Also i found some more errors in the journal: " <warn> [plugin/generic] could not grab port wwan0mbim0: Cannot add port 'wwan/wwan0mbim0', unhandled port type"

EDIT: maybe this is what you where looking for?

To see that it works automatically, restart computer (so both modem and ModemManager are reset, but you can reset the modem with mmcli and restart ModemManager via systemd) and try to connect to network or enable the modem (mmcli -m 0 --enable).
If transition error didn't happen, it worked

https://gitlab.freedesktop.org/mobile-b ... quests/806

Also found this huge patch i red about last summer that never made it

...
PCI_DEVICE(0x17cb, 0x0300)
...
...
PCI_DEVICE(0x03f0, 0x0a6c)
...T99W175 can not support MBIM/RmNet on the same time, choose Y
+ here for MBIM, N for RmNet.
...
This is way too much for a single patch. Please split your changes into a
series of patches

https://lore.kernel.org/lkml/2021031612 ... gmail.com/

Posted: **Sat Mar 11, 2023 4:19 pm**

"Will take another look over the HP install process today and see if can spot anything.. Unfortunately I have the latest HP one in place so it may skip it..
"Half tempted to see what the Lenono process would think of the HP modem but would rather not break things.."
"What did you have in Mind i could look for in that process?"

Think I found it.. it was the install log to try and figure out were/what the firmware file was: HP also has a log and got the notion to check what has been installed and in it found:
STEP PASS] Install driver [mbfwdriver] successful
[STEP PASS] Add register EnableLTEReportingOnNSA successful
[STEP Check] start wait for FW upgrade, Current: 0
[STEP Check] start wait for FW upgrade, Current: 3
.........................................
[STEP Check] start wait for FW upgrade, Current: 90
[STEP WARN] firmware update process over 90 seconds, Current: 93
[STEP PASS] FW upgrade PASS
[STEP PASS] Copy file [SDx55_Version.dll] to target successful
==================== Driver Install Complete ====================
errorlevel=0

So suspect the SDx55_Version.dll is the firmware..
Would recommend getting the modem on a windows system and upgrade in a 'supported' way

What would try is see if the process has /? flag options could be run to get more details logs.. So the other angle was also to find a way to extract it so could get a usable option to flash within openwrt..

Checking further found in SP144352 \src\Drivers
...
14/03/2022 00:57 1,950 ReadMe.txt
24/02/2022 07:50 121,344 SDx55_Version.dll

With the txt file mentioning:
// FOTA - v1.0.7.5 (T99W175.F0.1.0.0.9 (AP076). Win10 20H1 & Win11 22000 HLK)
Checked: Firmware Over the Air (FOTA)

Ah yes! Another item to mention.. Part of the reason was very interested in firmware was due to a lot of crashing firmware and loads of people of reporting crashes

Lenovo threads did a lot of talking and discussing this and thanks to a much more active support channel they came to the conclusion that "issues with versions bellow 075". in searching at the time I had seen as high as T99W175.F0.1.0.0.9.TO.006.079 mentioned.. but HP takes an age to catch up and looks like release every 3 months

But thanks to there last update it at least got me 1 point over 076

Has been a better at a firmware level, since that update have only had one crash.

"""Also found this huge patch i red about last summer that never made it
...
PCI_DEVICE(0x17cb, 0x0300)
...
...
PCI_DEVICE(0x03f0, 0x0a6c)
...T99W175 can not support MBIM/RmNet on the same time, choose Y
+ here for MBIM, N for RmNet.
...
This is way too much for a single patch. Please split your changes into a
series of patches
https://lore.kernel.org/lkml/2021031612 ... gmail.com """

Ah that sound like it

Part of what I read was that the reviewers didn't like such a massive update and asked for it to be broken down into smaller modules.. and that's were the store ended or went into slow mode..
EDIT: Would be realy good to get that set of fixes into a full release!

Slow mode is the same for my newer router! git has had the fix for the install packages for 8 months now and still they have not release install packages for it

So i am stuck using of mice and modems rooter on it..

Posted: **Sat Mar 11, 2023 5:01 pm**

mtl26637 wrote: Sun Mar 05, 2023 4:11 pm ...For the unlock scripts I just copied the 105b to 03f0 and the 105b:e0ab to 03f0:0a6c. This worked for me after copying or linking the scripts as suggested on the ModemManager FCC unlock instructions. Keep in mind for anyone using Openwrt the default link command does not work the same as what is instructed on the ModemManager page. Instead I just copied the scripts to the unlock folder rather than linking them.

So i would do that like this? or am i missing something? I dont really understand "/etc/ModemManager/fcc-unlock.d" because i dont have /etc

Code: Select all

cd  /usr/share/ModemManager/fcc-unlock.available.d/
cp 105b:e0ab  /usr/share/ModemManager/fcc-unlock.available.d/03f0:0a6c
cp 105b  /usr/share/ModemManager/fcc-unlock.available.d/03f0
qmicli -p -d /dev/wwan0mbim0 --device-open-mbim --dms-foxconn-set-fcc-authentication=00
qmicli -p -d /dev/wwan0mbim0 --device-open-mbim --dms-get-operating-mode

PaddyX wrote: Sat Mar 11, 2023 4:19 pm So suspect the SDx55_Version.dll is the firmware..
Would recommend getting the modem on a windows system and upgrade in a 'supported' way What would try is see if the process has /? flag options could be run to get more details logs.. So the other angle was also to find a way to extract it so could get a usable option to flash within openwrt..

Here someone tried to flash the firmware of the X5 HP Modem on Linux. He extracted the file got alot of logs and got the modem into Downloade mode on Linux flashed and than bricked his modem

but i have no idea where he found the logs https://abarouski.blogspot.com/2016/06/ ... t4120.html

When i installed HP Drivers on Win in the past those where with a GUI and opened a cmd window at some point of the installation process in the background at most, nothing to put flags in just the regular "accept Terms" ... "OK" .. "install" -Buttons. I have no idea where i could get those logs
:/ what do you mean by upgrade in a "supported" way? How did you upgrade?

EDIT: Downloading that Win10 iso takes ages i really need that T99W175 modem to work lol

Posted: **Sat Mar 11, 2023 5:43 pm**

Muhannad wrote: Sat Mar 11, 2023 5:01 pm When i installed HP Drivers on Win in the past those where with a GUI and opened a cmd window at some point of the installation process in the background at most, nothing to put flags in just the regular "accept Terms" ... "OK" .. "install" -Buttons. I have no idea where i could get those logs
:/ what do you mean by upgrade in a "supported" way? How did you upgrade?

EDIT: Downloading that Win10 iso takes ages i really need that T99W175 modem to work lol

Apologies, the "supported" was a little joke at HP writing everything on windows and leaning windows way..
So was along the lines of, without knowing if they do anything odd/funny with it then using it the way the programmed to carry out the work means its going to do the needed things..

"When i installed HP Drivers on Win in the past those where with a GUI and opened a cmd window at some point of the installation process in the background at most, nothing to put flags in just the regular "accept Terms" ... "OK" .. "install" -Buttons. I have no idea where i could get those logs"

I see your point! Sometimes things can be well hidden!

I took another quick looks at it.. 1st removed the Echo off so could see the output:
"install /?
REM echo off
REM The following is required in all INSTALL.CMD files
if exist c:\system.sav\util\SetVariables.cmd Call c:\system.sav\util\SetVariables.cmd
set version=1.03c
Set block=C:\SWSetup\SP144352\
CD /D "C:\SWSetup\SP144352\"
REM Remove the REM from the next line if your component does not support Silent Install (Application Recovery)
REM Erase /F /Q *.CVA
REM Add the command-line to have your component to be installed properly
Pushd src
src>if not defined FCC_LOG_FOLDER goto BPS
if exist "C:\SWSetup\SP144352\src\Uninstall.cmd" call "C:\SWSetup\SP144352\src\Uninstall.cmd"

Uninstall.cmd looks to be the next section.. It launches: SDx55DriverUninstallTool_v1.0.0.11.exe

in the src folder is also the log file mentioned..
it ended:
11/03/2023 23:39:02 Deleted File : C:\fota_running.txt
11/03/2023 23:39:02 Deleted File : c:\sim_service_running.txt
11/03/2023 23:39:10 DeviceRemove.exe "MBFW\{30334630-3041-3643-3034-3134464F5843}"
11/03/2023 23:39:10 No matching devices found.No devices were removed.

So need to get the modem back on to check further.. Will see if can find time tomorrow to move things around.. Altho if is no debug then will just see what I posted before.

Posted: **Sat Mar 11, 2023 5:49 pm**

Muhannad wrote: Sat Mar 11, 2023 5:01 pm So i would do that like this? or am i missing something? I dont really understand "/etc/ModemManager/fcc-unlock.d" because i dont have /etc

Code: Select all

cd  /usr/share/ModemManager/fcc-unlock.available.d/
cp 105b:e0ab  /usr/share/ModemManager/fcc-unlock.available.d/03f0:0a6c
cp 105b  /usr/share/ModemManager/fcc-unlock.available.d/03f0
[/quote]

Yes, that is the way to create the unlock scripts for the 03f0:0a6c modem.  ModemManager stopped unlocking these modems by default awhile back and have included instructions on how to unlock them manually.  Upon installation of ModemManager the scripts are always located in "/usr/share/ModemManager/fcc-unlock.available.d/*".  You must copy or link the unlock scripts to the correct ModemManager installation folder depending on which OS you are using.  When using Ubuntu or similar, the scripts must be linked to "/etc/ModemManager/fcc-unlock.d/*".  When using Openwrt this location is "/usr/lib/ModemManager/fcc-unlock.d/*".  If all else fails, create both locations and copy or link them to both.

Now, in regards to the HP.  The MHI driver does NOT include the 03f0:0a6c modem.  The only exception to this is the latest 6.2 kernel where I did notice it has been added.  This is based on kernels provided by kernel.org.  This may not be the case with other kernels provided via other sources I don't know.  Thing is, Openwrt does not use the latest kernels and the latest kernel used is 5.15.x so you must build the MHI driver with the 03f0:0a6c included for Openwrt to work on the HP.  This is how I have got it to work for me.

Posted: **Sat Mar 11, 2023 5:50 pm**

Muhannad wrote: Sat Mar 11, 2023 5:01 pm So i would do that like this? or am i missing something? I dont really understand "/etc/ModemManager/fcc-unlock.d" because i dont have /etc
Code: Select all
cd  /usr/share/ModemManager/fcc-unlock.available.d/
cp 105b:e0ab  /usr/share/ModemManager/fcc-unlock.available.d/03f0:0a6c
cp 105b  /usr/share/ModemManager/fcc-unlock.available.d/03f0

Yes, that is the way to create the unlock scripts for the 03f0:0a6c modem. ModemManager stopped unlocking these modems by default awhile back and have included instructions on how to unlock them manually. Upon installation of ModemManager the scripts are always located in "/usr/share/ModemManager/fcc-unlock.available.d/*". You must copy or link the unlock scripts to the correct ModemManager installation folder depending on which OS you are using. When using Ubuntu or similar, the scripts must be linked to "/etc/ModemManager/fcc-unlock.d/*". When using Openwrt this location is "/usr/lib/ModemManager/fcc-unlock.d/*". If all else fails, create both locations and copy or link them to both.

Now, in regards to the HP. The MHI driver does NOT include the 03f0:0a6c modem. The only exception to this is the latest 6.2 kernel where I did notice it has been added. This is based on kernels provided by kernel.org. This may not be the case with other kernels provided via other sources I don't know. Thing is, Openwrt does not use the latest kernels and the latest kernel used is 5.15.x so you must build the MHI driver with the 03f0:0a6c included for Openwrt to work on the HP. This is how I have got it to work for me.

Posted: **Sat Mar 11, 2023 6:20 pm**

i once had a HP Notebook which refused to boot after i upgraded the ram. Official Reason was it had blacklist every non hp branded ram on every device Worldwide because of FCC regulations...

PaddyX wrote: Sat Mar 11, 2023 5:43 pm in the src folder is also the log file mentioned..
it ended:
11/03/2023 23:39:02 Deleted File : C:\fota_running.txt
11/03/2023 23:39:02 Deleted File : c:\sim_service_running.txt
11/03/2023 23:39:10 DeviceRemove.exe "MBFW\{30334630-3041-3643-3034-3134464F5843}"
11/03/2023 23:39:10 No matching devices found.No devices were removed.

So need to get the modem back on to check further.. Will see if can find time tomorrow to move things around.. Altho if is no debug then will just see what I posted before.

Hmm i could try to undelete those files with Testdisk right after installing the Driver. Tell me when you found something ill wait with the Driver installation so we can get the log hopefully

mtl26637 wrote: Sat Mar 11, 2023 5:50 pm You must copy or link the unlock scripts to the correct ModemManager installation folder depending on which OS you are using. When using Ubuntu or similar, the scripts must be linked to "/etc/ModemManager/fcc-unlock.d/*". When using Openwrt this location is "/usr/lib/ModemManager/fcc-unlock.d/*". If all else fails, create both locations and copy or link them to both.

The Modem appeared under /dev after upgrading Kernel from 6.1.14 to 6.2.3 on Fedora. But there aint no /etc dir but a /lib/ dir without ModemManager. Somehow i got a convincing result by running "/usr/share/ModemManager/fcc-unlock.available.d/03f0 wwan0mbim0 wwan0mbim0" but cant confirm as long as i haven't fixed the Issue with the async which will hopefully bring the Modem alive

Code: Select all

bash-5.2# uname -r
6.2.3-300.fc37.x86_64
bash-5.2# find / -type d -name 'ModemManager'
find: ‘/run/user/1000/gvfs’: Permission denied
/usr/share/licenses/ModemManager
/usr/share/doc/ModemManager
/usr/share/ModemManager
/usr/lib64/ModemManager
bash-5.2# cd /usr/share/ModemManager/fcc-unlock.available.d/
bash-5.2# cp 105b:e0ab  /usr/share/ModemManager/fcc-unlock.available.d/03f0:0a6c
bash-5.2# cp 105b  /usr/share/ModemManager/fcc-unlock.available.d/03f0
bash-5.2# /usr/share/ModemManager/fcc-unlock.available.d/03f0 wwan0mbim0 wwan0mbim0
error: couldn't open the QmiDevice: Transaction timed out
Could not determine SDX55 firmware version. Falling back to old unlock method
error: couldn't open the QmiDevice: Transaction timed out
SDX55 FCC unlock v1 failed

Don't really know what to look for in the journal

Posted: **Mon Mar 20, 2023 4:52 pm**

Well good news my side. With the last few updates of the kernel and the async fix things have been stable so will be ordering a new areal and when it arrives will see about moving over to it as my primary.

Thanks for the mention of the HP modem being in the MHI files already in newer kernels! I cross checked and could see them. What I also checked for was the async fix and it was not in any of the latest kernels

On another note I was playing with openwrt to see if could get it working and it looks like they may need to do some more work on openwrt..
It always gives an error when trying to run mmcli scan! it errors like it does not have the rights or something is missing.
I used the same kernel version on a ubuntu box to generate the mhi_pci_generic file..
On the side did find openwrt seems to be based on debian so need to re-check this and see if can leverage it..

Edit: Ah recalled, Still not managed to get 5G only mode to work! Thoughts either signal strength is to low, ISP fibbing! or does not like the antennas!
With the proper 5G antennas and moving to a much better spot will see what is left on the list..

Posted: **Thu Mar 30, 2023 9:25 am**

@eskaryo

if you already have a working serial port (/dev/wwan0at0) with it, you can just run `AT^CUSTOMER=6` to convert the PID. 6 is Lenovo iirc. 1 should be Telit which isn't even in mainline yet. I tried everything on 6.2 and only the telit vid/pid pair didnt work. So yeah, you dont have to do the pid spoofing in proxmox

as for openwrt, maybe applying this PR should work https://github.com/openwrt/openwrt/pull/11011

Also they ran out of the 5G modules on ebay

I wanted one

Posted: **Thu Mar 30, 2023 3:41 pm**

The HP variant is basically the only one that isn't supported in latest openwrt snapshot at this point. If you install latest snapshot then use opkg to install luci. After you have luci installed you can then search and install any/all the software with "mhi", "modemmanager", *qmi*, "mbim" and all is good. Still may have to mess with FCC unlock and ModemManager APN and TTL settings but that about it at this point. If your able to use AT command to change to lenovo version then even the HP is usable at this point without building with manual edits to the MHI driver. Just gotta know your way around Openwrt/ModemManager a little.

Ya I was able to grab one of those from fleabay before they disappeared, couldn't turn it down for $25 for a 5G modem that competes with the best out there. Quite a steal. There more out there just not quite that cheap unfortunately.

Posted: **Fri Mar 31, 2023 12:02 am**

HP and Telit actually. Telit one might be obscure (AT^CUSTOMER=1 or 2 I forgot).
That was for those people who can plug it in a laptop or something and run a newer version of the kernel and not bother updating their openwrt instances. Like in eskaryo's case where host has 6.1 and potentially an owrt guest on 5.15. Wouldn't need to spoof pid in that case.
Otherwise they can just apply the 6.1 patch by Ansuel to be able to get it working. There are a lot more changes from 5.15 which snapshot is on to 6.1 in regards to mhi and wwan core.

If anyone has extras and willing to let go of one

Posted: **Sat Apr 01, 2023 8:34 am**

Does anyone have any recommendations of an adapter from Ali for a sim card that can be used with this modem? I saw about the Ableconn one, but it is sold on Amazon and is quite expensive...
Also, would plugging such an adapter into one like this https://www.aliexpress.com/item/1005004700605966.html (PCIe to Mini PCIe) work? I will use the modem on a desktop motherboard (x86 Proxmox host with OpenMPTCProuter guest), and it has no Mini PCIe obviously, so I need some kind of similar adapter solution.

Posted: **Sat Apr 01, 2023 9:14 am**

That would likely work as it is PCI. For the modems mentioned they are usually PCI mode only..
The other item to mention is what other ports does it have as there are other m.2 ports that can be converted over..
I have verified if the adapter is good can go from:
m.2 m key (usualy for storage)
m.2 a/e key (usualy wifi module)

Posted: **Sat Apr 01, 2023 11:17 am**

PaddyX wrote: Sat Apr 01, 2023 9:14 am The other item to mention is what other ports does it have as there are other m.2 ports that can be converted over..

What other ports does my x86 machine have? The motherboard is an Atermiter DDR4 Turbo D4 Motherboard. But I would prefer an x1 or x2 PCIe adapter.
What about the SIM card part, do you know any adapter that adds one? My carrier doesn't support eSIM...

Posted: **Sat Apr 01, 2023 3:05 pm**

Ableconn is the best! the option to jumper pci only mode only is what makes it great! I tried another and was no go so waist of money. and the problem is many don't tell you if they are usb only or what protocols are available!

Also forgot to mention with PCIe to Mini PCIe you still have to get the Ableconn to convert to the final m.2 b key with sim!

Posted: **Sat Apr 01, 2023 3:21 pm**

isthiscre@iv wrote: Sat Apr 01, 2023 11:17 am What other ports does my x86 machine have? The motherboard is an Atermiter DDR4 Turbo D4 Motherboard. But I would prefer an x1 or x2 PCIe adapter.
What about the SIM card part, do you know any adapter that adds one? My carrier doesn't support eSIM...

Took a look and looks like it may have: Ports (depending on the flavour):
NVME M.2
SATA M.2
2x pcix1 slots

Should not be a problem using the PCIx1 slot.. As mentioned as long as PCI is properly supported and passed through then is fine.

RE: What about the SIM card part, do you know any adapter that adds one?
You will still need a 2nd adapter on top of the pcix one. for that the Ableconn-MPEX-134B-Mini-PCIe-Adapter is the best! as know it works and it has the sim slot included on it!
https://www.amazon.com/Ableconn-MPEX-13 ... B0779727FY

Posted: **Mon Apr 03, 2023 1:36 am**

isthiscre@iv wrote: Sat Apr 01, 2023 8:34 am Does anyone have any recommendations of an adapter from Ali for a sim card that can be used with this modem? I saw about the Ableconn one, but it is sold on Amazon and is quite expensive...
Also, would plugging such an adapter into one like this https://www.aliexpress.com/item/1005004700605966.html (PCIe to Mini PCIe) work? I will use the modem on a desktop motherboard (x86 Proxmox host with OpenMPTCProuter guest), and it has no Mini PCIe obviously, so I need some kind of similar adapter solution.

If you don't mind taobao, https://item.taobao.com/item.htm?id=583003660515 No issues with sim card either as they have options to include sim slots. If you already have an existing sim slot, it's also wired to that.

They also have PCIe to M.2 B with USB+PCIe! Pretty cool if you dont want nested adapters. just browse at https://shihetec.taobao.com/
Bunch of cheap adapters for different use cases. Just select 5G and put a note that you want 3042 so they'll solder a threaded socket in the 3042 hole.
4G option might not have the pcie lanes wired.

Ableconn was way too much to ship to my place and also way too expensive. I probably got this for less than half the cost. If your 5G module also supports dual sim, this can do it.
IMHO if you can order from taobao, this one is the best. I also got an M.2 A+E to Mini PCIe so I can use the adapter on wifi m.2 slots.

Posted: **Mon Apr 03, 2023 7:04 am**

Hikaru_ wrote: Mon Apr 03, 2023 1:36 am
isthiscre@iv wrote: Sat Apr 01, 2023 8:34 am Does anyone have any recommendations of an adapter from Ali for a sim card that can be used with this modem? I saw about the Ableconn one, but it is sold on Amazon and is quite expensive...
Also, would plugging such an adapter into one like this https://www.aliexpress.com/item/1005004700605966.html (PCIe to Mini PCIe) work? I will use the modem on a desktop motherboard (x86 Proxmox host with OpenMPTCProuter guest), and it has no Mini PCIe obviously, so I need some kind of similar adapter solution.
If you don't mind taobao, https://item.taobao.com/item.htm?id=583003660515 No issues with sim card either as they have options to include sim slots. If you already have an existing sim slot, it's also wired to that.

They also have PCIe to M.2 B with USB+PCIe! Pretty cool if you dont want nested adapters. just browse at https://shihetec.taobao.com/
Bunch of cheap adapters for different use cases. Just select 5G and put a note that you want 3042 so they'll solder a threaded socket in the 3042 hole.
4G option might not have the pcie lanes wired.

Ableconn was way too much to ship to my place and also way too expensive. I probably got this for less than half the cost. If your 5G module also supports dual sim, this can do it.
IMHO if you can order from taobao, this one is the best. I also got an M.2 A+E to Mini PCIe so I can use the adapter on wifi m.2 slots.

No issues with ordering from there)
I checked the first link that you posted, and in the description it says USB 2.0, and visually, the lanes that are connected seem to be too few for carrying PCIe signal, even on the 5G version (maybe marketing thing? It's just an adapter).
Do you have the link for the "PCIe to M.2 B with USB+PCIe" adapter that you mentioned? The store has so many listings, so it's a bit hard to find...

Also, yes, I will not buy the Ableconn, as with shipping the price is pretty much same as the modem (or more, depending on brand of the modem). I am in contact with the admin of a thread about 4G/5G modems on 4PDA (Russian forum) that has designed his own adapter (and got it manufactured) that plugs into an M key NVMe socket (usual socket of NVMe SSDs on motherboards), so I may also buy an adapter from him. The only issue is shipping from Russia right now... But he promised to check the price for shipping etc.
I will post an update on that too, if I end up buying it.

Posted: **Mon Apr 03, 2023 9:28 am**

isthiscre@iv wrote: Mon Apr 03, 2023 7:04 am No issues with ordering from there)
I checked the first link that you posted, and in the description it says USB 2.0, and visually, the lanes that are connected seem to be too few for carrying PCIe signal, even on the 5G version (maybe marketing thing? It's just an adapter).
Do you have the link for the "PCIe to M.2 B with USB+PCIe" adapter that you mentioned? The store has so many listings, so it's a bit hard to find...

Also, yes, I will not buy the Ableconn, as with shipping the price is pretty much same as the modem (or more, depending on brand of the modem). I am in contact with the admin of a thread about 4G/5G modems on 4PDA (Russian forum) that has designed his own adapter (and got it manufactured) that plugs into an M key NVMe socket (usual socket of NVMe SSDs on motherboards), so I may also buy an adapter from him. The only issue is shipping from Russia right now... But he promised to check the price for shipping etc.
I will post an update on that too, if I end up buying it.

I can confirm that the 5G version (black one) has pcie lanes btw

Their second pic is a T99W175 with the 5G adapter.

M.2 Key B to Mini PCIe: https://item.taobao.com/item.htm?id=583003660515
Select "Sky Blue 5G_SIM*2" for PCIe. Message them to customize it to 3042

M.2 Key B to PCIe: https://item.taobao.com/item.htm?id=599012341033
Select 3042. All pcie lanes connected

M.2 Key B to M.2 Key B+M: https://item.taobao.com/item.htm?id=599011797818
Don't need that adapter from russia

They seem to have it here. Just select 3042. does seem like it has pcie lanes connected. (they also mention)

They have a lot more adapters which might be interesting to some. (including extending such adapters via FPC cables.) so best to look around. There's not much listings once you go to the categories.

Posted: **Mon Apr 03, 2023 12:19 pm**

Hello all,
I was excited to see the reasonable price I could get one of these lenovo version modems for. I've got it in the Ablecom adapter on an old system and it seems to be working but I have a few questions I thought I'd get input from you pioneers on.

First: I'm on an old firmware and I'd like advice about what version is working best to upgrade to, and also for any guidance on doing the upgrade safely under linux preferably.

Second: I'd really like to be able to change the IMEI # and I'm pretty sure I've seen reference to this somewhere but am having trouble finding it now. I tried the AT+EMGR command and it is not working at least on this firmware version. I see some references to a windows app that can do it for snapdragon android phones but again I figured you guys might have some suggestions.

Thank you in advance!

Posted: **Tue Apr 04, 2023 5:22 am**

Hikaru_ wrote: Mon Apr 03, 2023 1:36 am Ableconn was way too much to ship to my place and also way too expensive. I probably got this for less than half the cost. If your 5G module also supports dual sim, this can do it.
IMHO if you can order from taobao, this one is the best. I also got an M.2 A+E to Mini PCIe so I can use the adapter on wifi m.2 slots.

yea i found a very interesting adapter from m-key to b-key with sim but the shipping was insane!! $60+

Ended up getting https://www.aliexpress.com/item/4001160 ... 1802tt90Mv
That converts from m.2 m NVME no problem but will still need the pcie > m.2-B with sim!
I used it to test on my main windows system.. The one thing to be awair of is if multiple of you the cascade of adapters has sim have the sim in the final adapter that has the modem on it..

Posted: **Tue Apr 04, 2023 3:05 pm**

pwalsh110 wrote: Mon Apr 03, 2023 12:19 pm Hello all,
I was excited to see the reasonable price I could get one of these lenovo version modems for. I've got it in the Ablecom adapter on an old system and it seems to be working but I have a few questions I thought I'd get input from you pioneers on.

First: I'm on an old firmware and I'd like advice about what version is working best to upgrade to, and also for any guidance on doing the upgrade safely under linux preferably.

Second: I'd really like to be able to change the IMEI # and I'm pretty sure I've seen reference to this somewhere but am having trouble finding it now. I tried the AT+EMGR command and it is not working at least on this firmware version. I see some references to a windows app that can do it for snapdragon android phones but again I figured you guys might have some suggestions.

Thank you in advance!

Do a quick firmware update on windows. Might be too old of a version to be updated via fwupd. I did a fw update on windows then updated in linux since it seems to have newer firmware.

For IMEI repair, assuming linux:

Code: Select all


# Delete IMEI first
AT^NV=550,0
# Reset
AT+CFUN=1,1

# Under root
# Figure out the bus id of the module in lspci. should be something like 0000:01:01.1
echo 1 > /sys/bus/pci/devices/<bus id here>/remove

# rescan to reinit
echo 1 > /sys/bus/pci/rescan

# Set IMEI <find the doc to calculate this>
AT^NV=550,0,"08,0A,00,00,00,00,00,00,00"

# Reset 
AT+CFUN=1,1

# Under root
# Figure out the bus id of the module in lspci. should be something like 0000:01:01.1
echo 1 > /sys/bus/pci/devices/<bus id here>/remove

# rescan to reinit
echo 1 > /sys/bus/pci/rescan

and you're done.

Posted: **Tue Apr 04, 2023 3:12 pm**

PaddyX wrote: Tue Apr 04, 2023 5:22 am yea i found a very interesting adapter from m-key to b-key with sim but the shipping was insane!! $60+

Ended up getting https://www.aliexpress.com/item/4001160 ... 1802tt90Mv
That converts from m.2 m NVME no problem but will still need the pcie > m.2-B with sim!
I used it to test on my main windows system.. The one thing to be awair of is if multiple of you the cascade of adapters has sim have the sim in the final adapter that has the modem on it..

Oh yeah I found those on ali as well. But buying from ali is more of a PITA than taobao for me surprisingly. (Postal service sucks here)

I also found a key b -> key b with sim that's made by the same manufacturers. no m.2 b -> minipcie with pcie lanes though sadly. also why a friend referred me to his favorite adapter shop. the ones I linked. Thankfully they had the adapters I needed.

If you have a cascade of adapters, it's fine as long as the lanes are connected. an example would be the shihetech adapters. you can get m.2 B to minipcie without sim slots then use the one you linked for sims. (no point though since they ahve key B to key M)

To check for PCIe support: just check the 6th and 7th pins on the top smaller connector

Screenshot 2023-04-05 at 4.10.29.png

to check if sim is passthrough the mini pcie slot, check if the back side has all these pins connected.

Screenshot 2023-04-05 at 4.11.36.png

Posted: **Fri May 12, 2023 11:38 pm**

Hello, I am running latest Proxmox VE on my server, and have a VM with latest OpenWrt SNAPSHOT, r22847-5ca3386c8a (Linux OpenWrt 5.15.110 #0 SMP Fri May 12 01:15:47 2023 x86_64 GNU/Linux). I got the modem passed through to the VM with Proxmox, but even though it sees it, it errors out.
It's a Lenovo T99W175.00, and the dmesg has this:

Code: Select all

mhi-pci-generic 0000:00:10.0: MHI PCI device found: foxconn-sdx55
[    7.745559] mhi-pci-generic 0000:00:10.0: BAR 0: assigned [mem 0x100000000-0x100000fff 64bit]
[    7.750397] mhi-pci-generic 0000:00:10.0: using shared MSI
[    7.754556] mhi mhi0: BHI offset: 0xffffffff is out of range: 0x1000
[    7.755971] mhi-pci-generic 0000:00:10.0: failed to prepare MHI controller
[    7.934264] mhi-pci-generic: probe of 0000:00:10.0 failed with error -22

This is lspci:

Code: Select all

00:10.0 Unassigned class [ff00]: Foxconn International, Inc. Device e0ab

I saw https://github.com/kristrev/mhi-for-kernel-4.14 in this discussion, but I'm using latest snapshot and installed the following kmods:

Code: Select all

kmod-mhi-bus kmod-mhi-net kmod-mhi-pci-generic kmod-mhi-wwan-ctrl kmod-mhi-wwan-mbim

So I guess that I shouldn't need the GitHub MHI, as it's for older kernel also, right?

What could be wrong? How do I get it to work?

Posted: **Tue May 16, 2023 5:29 am**

Hello and the fray continues

If recall -22 is EINVAL (invalid argument). Also errors before are likely the better areas to check..
Of what I can see “mhi mhi0: BHI offset: 0xffffffff is out of range: 0x1000” seems to be the most ???
In trying to check around, just for info even:
https://lore.kernel.org/lkml/2023032710 ... hinkpad/T/
“If the BHIOFF or BHIEOFF range checks fail, they return EINVAL. ERANGE
is a better error code since it implies an out of range condition.”
So far in digging not finding any solid hits and in what can read seems like may be a config issue of some kind..
“So I guess that I shouldn't need the GitHub MHI, as it's for older kernel also, right?” Not necessarily! Not due to older kernel but the challenge have had with the higher versions in that they don’t always have all the fixes we have seen to be needing..
That you have the Lenovo version likely puts you in a better place for trying to work down this channel.
Items would have normally recommend checking:
-What firmware is the modem at? Most of the older firmware have stability and other issues and is only in the last 6 or so months they have finally got more stable with Lenovo getting there ahead of HP.. Would also try to get it onto a windows system to both update firmware and test function on windows..
-There was another async fix that massively impacted stability if there was any kind of restart/reboot and this did not make it into the new versions and think it is not in openwrt yet! To work around this any time the system has a modem issue and or the modem does not come up power the system off completely and then start otherwise you will be chasing your tail so to speak..
-Openwrt: The MHI and bits needed to get this working on openwrt are still very very new! While it has been mentioned in this thread that it is now possible to get the Lenovo working on Openwrt there is still a lot of preference to be using a Linux OS!
Proxmox VE: May need to put in detailed config info for around this as it has been mentioned and ‘working’ to a degree but will need to compare config with eskaryo.
The other challenge I am still trying to get time and work out is how to get debugging going and the challenge is this usually means re-compile and openwrt and this is next level pain.. To the point of mention of actually compiling openwrt directly…

Posted: **Thu May 18, 2023 1:01 pm**

PaddyX wrote: Tue May 16, 2023 5:29 am Also errors before are likely the better areas to check..

I can send the whole dmesg if needed, but it doesn't seem like there are other errors...

PaddyX wrote: Tue May 16, 2023 5:29 am Not necessarily! Not due to older kernel but the challenge have had with the higher versions in that they don’t always have all the fixes we have seen to be needing..

So should I try compiling the GitHub MHI? Will it not matter that the kernel of my OpenWRT install is higher than 4.14, or how would I compile for the right one?

PaddyX wrote: Tue May 16, 2023 5:29 am What firmware is the modem at? ... Would also try to get it onto a windows system to both update firmware and test function on windows..

How would I check the firmware version and update it?
I booted a Windows 10 VM and initially it didn't find any drivers for the modem, so it showed up as nothing in particular in device manager.
Then I downloaded the drivers from Lenovo (https://support.lenovo.com/us/en/downlo ... ga-6th-gen - nz7wn08w.exe v58) and it started recognizing it, but it doesn't initialize the modem correctly...

PaddyX wrote: Tue May 16, 2023 5:29 am There was another async fix that massively impacted stability

Are those fixes included in the GitHub MHI or are they something else?

PaddyX wrote: Tue May 16, 2023 5:29 am The MHI and bits needed to get this working on openwrt are still very very new! While it has been mentioned in this thread that it is now possible to get the Lenovo working on Openwrt there is still a lot of preference to be using a Linux OS!

I tried on a Ubuntu 23.04 Desktop VM (kernel 6.2.0), but the mhi errors are the exact same ones as the ones from the dmesg that I sent before from OpenWRT...

PaddyX wrote: Tue May 16, 2023 5:29 am Proxmox VE: May need to put in detailed config info for around this as it has been mentioned and ‘working’ to a degree but will need to compare config with eskaryo.

What exact config info should I post? My Proxmox install has all default settings and the VM running OpenWRT has regular VM settings...
The only other thing that I did was to make it not initialize the modem prior to passing to the VM, and I did that by using the exact same method that @eskaryo posted before (adding mhi_pci_generic to /etc/modprobe.d/pve-blacklist.conf).

Posted: **Mon May 22, 2023 7:24 pm**

eskaryo wrote: Mon May 22, 2023 12:53 pm @isthiscre@iv

I am not using my T99W175 currently, I was running into MHI initialization frustration and discovered I don't even have 5g service where I live so I went back to a T77W968 simply because it inits perfectly every time.

The behavior you are experiencing is something I also observed, the hypervisor needed to have power removed for the device to be in a clean-init state and I felt like it was just an annoying thing to have to manage.

Custom modules built with the state correction PaddyX outlined should be applied to the hypervisor and guest/container and that should resolve.

I wouldn't mind getting back over on this module, it boots and connects more rapidly than the T77- I just need to take the time to build the module with the aforementioned fixes. Since I don't have 5G out here, the impetus is not strong.

The hypervisor needed to have power removed for the device? What do you mean by that?
Is blacklisting the driver alone like I did not enough? If so, how do I do that?
If I do

Code: Select all

echo 1 >/sys/bus/pci/devices/0000:08:00.0/remove

on the hypervisor, when starting the VM, it will fail because it can't find the right PCIe device to pass through

Code: Select all

TASK ERROR: no PCI device found for '0000:08:00'

So I guess that you are talking about something else...

What custom modules are you referring to? Is it the mhi driver from GitHub or something else?
If so, then why should it be applied to hypervisor also if it has mhi driver blacklisted? Seems like that would have the wrong effect if the goal is to pass the modem uninitialized.

Edit:
I decided to try shutting the Windows VM down and doing

Code: Select all

echo 1 >/sys/bus/pci/devices/0000:08:00.0/remove

, then

Code: Select all

echo 1 >/sys/bus/pci/rescan

and starting the VM again multiple times, and slowly, some devices started to appear, although the MhiHost initialization error from the previous Windows screenshots that I posted remains (strangely only in events tab, in general tab it now says that it's working fine).
This also made the network adapter appear etc but it has errors so it disappeared when I tried enabling it.

When I tried running the OpenWRT snapshot VM after this, the dmesg changed, now it looks like this:

Code: Select all

[    7.858310] mhi-pci-generic 0000:00:10.0: MHI PCI device found: foxconn-sdx55
[    7.859982] mhi-pci-generic 0000:00:10.0: BAR 0: assigned [mem 0x100000000-0x100000fff 64bit]
[    7.861808] mhi-pci-generic 0000:00:10.0: enabling device (0000 -> 0002)
[    7.865159] mhi-pci-generic 0000:00:10.0: using shared MSI
[    7.871924] mhi mhi0: Requested to power ON
[    7.873724] mhi mhi0: Power on setup success
[   52.437119] mhi_wwan_ctrl mhi0_DUN: 33: Failed to receive RESET channel command completion
[   52.438607] mhi_wwan_ctrl mhi0_DUN: 33: Failed to reset channel, still resetting
[   72.917863] mhi_wwan_ctrl mhi0_DUN: 32: Failed to receive RESET channel command completion
[   72.917868] mhi_wwan_ctrl mhi0_DUN: 32: Failed to reset channel, still resetting
[   79.317924] mhi_wwan_ctrl mhi0_MBIM: 13: Failed to receive RESET channel command completion
[   79.319497] mhi_wwan_ctrl mhi0_MBIM: 13: Failed to reset channel, still resetting
[   99.798253] mhi_wwan_ctrl mhi0_MBIM: 12: Failed to receive RESET channel command completion
[   99.800148] mhi_wwan_ctrl mhi0_MBIM: 12: Failed to reset channel, still resetting
[  122.838833] mhi mhi0: Did not enter M3 state, MHI state: M0, PM state: M?->M3
[  122.840274] mhi-pci-generic 0000:00:10.0: failed to suspend device: -5

And just to make sure, I tried on that 6.2 kernel Ubuntu VM as well, and it had the same dmesg, but it also had this after "Power on setup success":

Code: Select all

Wait for device to enter SBL or Mission mode

Seems like at least something is working maybe, and I really hope that I can get it running eventually...
Init errors are bad, but if I can init it fine once, I can just leave the VM running for months. So I guess that it shouldn't be that problematic in my case.
And I have 5G in the area, so it would be really useful to be able to use this modem...

Posted: **Mon May 29, 2023 10:41 am**

Have you tried it in the host without passing through? I'm currently running it on OpenWrt 23.05 snapshot which is on 5.15 with no patches for mhi pci. It's in an IPQ4019 router with an adapter both from taobao. Running FW: T99W175.F0.1.0.0.9.GC.004 079 with a lenovo module.

Posted: **Wed May 31, 2023 11:56 am**

Hikaru_ wrote: Mon May 29, 2023 10:41 am Have you tried it in the host without passing through? I'm currently running it on OpenWrt 23.05 snapshot which is on 5.15 with no patches for mhi pci. It's in an IPQ4019 router with an adapter both from taobao. Running FW: T99W175.F0.1.0.0.9.GC.004 079 with a lenovo module.

Hmm, I'm thinking it's some issue with firmware maybe? The adapters seem to work fine as everything is at least visible in the dmesg and Windows (I got 2 of the ones that you sent before from Taobao), but I still have issues even on a separate system with just Ubuntu installed (no virtualization, Proxmox or similar).

This is the dmesg from that system (didn't paste output because the machine had no internet etc for outputting to text so I took a photo):

Could it be some other issue? Or do I contact the seller because the modem might be DoA?
The seller seems to have good ratings, so I hope that he sends a new one in that case, as the customer protection already ran out...

Edit:
I have done literally everything possible with the help of someone to get it working (got it into some special modes, changed firmware, tried doing some other hardware etc) and it appears to have a bootloop issue that cannot be fixed, so it's probably a hardware issue after all... RIP

Posted: **Thu Jun 08, 2023 4:46 pm**

Have you tried bare metal windows? if yes, yeah might be DoA. I actually got more of the lenovo cards for cheap and havent had any similar issues. Although I only tried it on an RK3588 SBC and not my router with PCIe.

Posted: **Tue Jun 13, 2023 1:43 pm**

isthiscre@iv wrote: Wed May 31, 2023 11:56 am Hmm, I'm thinking it's some issue with firmware maybe?
......
Edit:
I have done literally everything possible with the help of someone to get it working (got it into some special modes, changed firmware, tried doing some other hardware etc) and it appears to have a bootloop issue that cannot be fixed, so it's probably a hardware issue after all... RIP

Apologies, things have been crazy busy my side so not managed to catch up or do much more on my system..
What firmware were you on and what are you using now?
I have the Hp and did a lot of reading on the lenovo side. Had massive issues with firmware from the begining! And only recently managed to get a high enough version..
If you have managed to upgrade to the latest then it should be more stable. On the older builds I had massive issues with the modem crashing out.. but seem to recall for some of them it would actualy mention in the log a firware crash so mayby grep the logs for firmware.,.. I mentioned this earlier in this post:
got my modem on: T99W175.T0.0.0.4.1.GC.003.028
Had seen mention as high as T99W175.F0.1.0.0.9.TO.006.079 and mention and other issues with versions bellow 075.. So anything 75 or above should be better..

Tried looking up the error and found some mention in https://gitlab.freedesktop.org/mobile-b ... issues/644
didnt have the time to do a final re-check but there was some mention of the wrong sim slot being selected or a sim issue.. I know i had some fun when using two levels of adapters as both had sim slots so had to make sure the sim was on the same converter that held the modem..

RE Are those fixes included in the GitHub MHI or are they something else?
From what we got from testing most of the fixes had made it into the later kernels/mhi but what had not made it in was the async one and for me this was the one that if anything happened and the modem crashed it would never be able to restart withough a hard boot of everything! For it you have to compile +++ b/drivers/bus/mhi/pci_generic.c
@@ -637,7 +637,7 @@ static void mhi_pci_recovery_work(struct work_struct *work)
if (err)
goto err_try_reset;

- err = mhi_sync_power_up(mhi_cntrl);
+ err = mhi_async_power_up(mhi_cntrl);
if (err)
goto err_unprepare;
Also double check as there are two places that look similar and you need to mod the correct one.. Will try to check in again soon..

EDIT: One item to clarify.. The Firmware! I tried a lot of firware versions along the way, partly due to for a long time there was no stable version.. Also what needs to be reminded, things can get re-broken! Have seen it so many times and we even found it on other aspects of issues with the over all issues arround this.. Problems re-occuring and crazy amount of time to get fixes in!! What we have seen is things are getting better but its slow!

Posted: **Sun Jul 16, 2023 4:33 am**

Hi guys! I’m new here!

I have a T99W175 HP variant working perfectly on OPENWRT.

I would like to order one more to put on my LHGG CAT6 antenna from Mikrotik.

In order for a modem to work with ROS it needs to support MBIM over usb. I have mini pcie to m2 b key adapter but I would like your opinion on this one.

I don’t know if it’s safe to give it a try or if I will break the modem or even worse the LHGG.

Some help would be greatly appreciated

Posted: **Wed Jul 19, 2023 5:36 am**

Hello Xristos

Interesting to hear "I have a T99W175 HP variant working perfectly on OPENWRT."
What is the version of openwrt?
What is the router hardware?
-Quick lookup: or is it working in the Mikrotik Router OS?
Was it an openwrt from microtec or came with the router?

RE: "In order for a modem to work with ROS it needs to support MBIM over usb. I have mini pcie to m2 b key adapter but I would like your opinion on this one"

The HP/Lenovo ones usualy have USB channels hard disabled so would not work with any USB in the works.. hence the wating to know hardware above..

RE: "I don’t know if it’s safe to give it a try or if I will break the modem or even worse the LHGG."
It should not damage the modem. It just wont be seen.
Further USB converters, I have an old one and a new one and my other 1gig modem did not work in the old one so does seem like there is some new config in the new usb convertes so double check what the specs are.. Also have tested my HP T99W175 in the USB converter and was not seen at all and since moving it to a PC with m.2 it works fine and have moved it back and forth without issue.. Just be cairful of static and dont touch any contacts etc!

Posted: **Sun Aug 06, 2023 9:34 am**

xristos wrote: Sun Jul 16, 2023 4:33 am Hi guys! I’m new here!

I have a T99W175 HP variant working perfectly on OPENWRT.

Where are you using it? On what hardware? Can you please share the Openwrt version you're using?

Thank you

Posted: **Thu Sep 07, 2023 7:49 am**

Not seen any update from him

On the good side I had another issue were they didnt support my main router hardware at alll and can see now in the latest future test builds it got added! So have to hope that the change was made in one of those latest builds.

Have been trying to find some time to get down time on the router to play with it but things have been too busy

If have a suported router maby try gettting on the latest test builds and try it.
I need to get my other router stable and setup so can free the main up for testing.

Keep us posted

Posted: **Sat Sep 16, 2023 5:31 pm**

So, for now there is no way to use this T99W175 on openwrt? I have the lenovo variant, and I've been unable to use it since I purchased it because I have USB3.0 adapters everywhere and never had the occasion to work with PCIE mode, neither I have the hardware (custom router / expensive lenovo laptop) to use it.

Anybody has something to suggest for capable hardware to run this modem with OpenWRT?

Posted: **Wed Oct 04, 2023 3:52 pm**

Hello eskaryo, sorry for the delay, things have been crazy and trying to find my power supply after a massive tidy up

RE: could post your mhi_pci_generic.ko file
When managed to get it up will try to get this for you. Note the version I will have is based on linux os and not openwrt..
Still have not found time to get my internet backonto my old router so can get playing with this again.

RE: Also- how can we ask the OpenWRT group to maybe update their mhi_pci_generic kmod to include?
Think in the latest builds they do have it but the challenge is you generaly get it as they give it.. App there is a way to compile but have not managed to figure it out..

Posted: **Mon Oct 09, 2023 5:17 pm**

Hello eskaryo

Attaching the file as requested. it is based on 6.1.7 kernel and have seen a number of changes as the versions go up..

Now that have the system back will see about moving to the latest and test /check again as they have already got upto 6.6. rc5 so has been while since was last able to work on this. As mentioned with the attached file had it stable and no problems with reboots and re-iterate make sure the firmware on the modem is high enough as there was crashing issues on old firwares!!
Also if the async is not in place then any firmware crash or soft reboot will break everything untill a hard reboot!

Note: I have ordered to make my life a little easier a lenovo ver of the modem.. hope to have it by Jan
-Also looking into getting another micro system, likly a lenovo with full m.2 slots also to make my life a little easier as my one needs more than 1 converter stacked so hope with a proper m.2 to go back to just 1 and a good one at that..

Posted: **Tue Nov 14, 2023 5:39 am**

So there is Lenovo/HP/Dell versions. Dell seems to be the cheapest, but the least hassle is with the Lenovo - is that correct?

Posted: **Tue Nov 14, 2023 9:03 am**

And one more

How do you know if the adapter is with PCIE lines ? E.g. if I would need a full PCIE adapter (not miniPCIE) would this work https://item.taobao.com/item.htm?id=599012341033 ?

Posted: **Thu Nov 16, 2023 4:17 pm**

@eskaryo no problem

good to see you still arround and keeping busy

@geraigerai For a couple of reasons would aim for lenovo! I got an HP as was better price and took ages to get needed fixed firmware and still have to hack the files for linux! While Lenovo has been far ahead on the firmware and better supported! Also keep an eye on ebay as desided to get a 2nd and found a lenovo one on ebay for $24! Amazing price and must have got very lucky! Just trying to get it back to me now

hope to have a path for it to get to me in Jan!

Posted: **Fri Nov 17, 2023 5:05 am**

eskaryo wrote: Wed Nov 15, 2023 8:01 pm At this point the only thing that I'd say is difficult is the fact that OpenWRT does not yet have a release with a patched mhi_pci_generic module which is needed to ensure clean power-on of the modem.

So how can I build the OpenWRT with the patched version? I've checked out the master branch of the openwrt, but it does not seem to contain the `pci_generic.c` file nor did I find anything with `mhi_sync_power_up` or `mhi_async_power_up`.
And also on the master the TESTING kernel version is 6.1, so openwrt is not there yet with 6.2 ? What am I missing?

I've bought the Lenovo version for 50eur shipped with taxes (Dell was 40eur, but it was marked as prototype, so was a bit afraid to buy that) and planing to put that into x86 Fujitsu Futuro S920 thin client. So while waiting for the hardware I thought I'd compile the openwrt from source with the patches

EDIT:
Ok, it seems I need to build first, and then use quilt for patch applying, not as straight forward as I thought

Posted: **Fri Nov 17, 2023 9:51 am**

The latest stable version has support (23.05). It actually has for awhile now really. The only trick is having to install some of the software after installing openwrt to your device. The quickest and easiest way to get up and running is to install openwrt on your device. Connect an internet connection to your device and go to the /system/software tab and search and install everything usng the following searches:
"mbim"
"qmi"
"mhi"
"modemmanager"

Not sure if every package that you will see is needed but since your running on x86 machine storage shouldn't come into play anyway. This will also work with the latest snapshots but you will need to add "luci" to the software list and will need to install it from command line first.

Once, installed you will need to link/copy the fcc-unlock information to the appropriate location and restart. Once this is completed restart and you should be good to go with Lenovo versions. The HP version still has not been added to the list so it still requires building. The Dell and other brands I have not tried.

You may have to mess around with dns/dhcp lan/gateway settings initially to get a working internet connection to download the software but once you have downloaded and installed it should work. Just don't forget to change things back to their default settings before restarting. There are potential issues along the way like latest modem firmware not playing nice with fcc-unlock but it is doable as I've been running a couple of these since August, 2022. I've never ran into any of the power issues that others mention and have never had to 'patch'. I did see some kernel faults along the way in the past but they seem to have went away for me, can't explain that one.

Posted: **Fri Nov 17, 2023 6:32 pm**

Futher install everything usng the following searches:
"mbim"
"qmi"
"mhi"
"modemmanager"

I would offer one item, there was a stability issue mentioned on lenovo site about if had two of the protocols at the same time, they both try talk to the modem and it hangs it up.. if recall it was if both MHI and QMI active they both try to talk to the modem so confuse it.
If recall if using pci then is mhi route while if is other usb side could be qmi or mbim..
Question would be what is the output of lsusb and lspci
mbim would be if is mbim mode and that would be seen via lsusb aka the pci would not use it..

Generaly the lenovo/hp would be pci so mhi is the must..
Them modemmanager

had a fantastic new round of learning curve arround those as got another 4g modem and had a load of fighting to get it working including removing the fcc-lock perminetly at the modem level on it and some other fun!

Posted: **Thu Nov 23, 2023 1:24 pm**

PaddyX wrote: Fri Nov 17, 2023 6:32 pm Futher install everything usng the following searches:
"mbim"
"qmi"
"mhi"
"modemmanager"

I would offer one item, there was a stability issue mentioned on lenovo site about if had two of the protocols at the same time, they both try talk to the modem and it hangs it up.. if recall it was if both MHI and QMI active they both try to talk to the modem so confuse it.
If recall if using pci then is mhi route while if is other usb side could be qmi or mbim..
Question would be what is the output of lsusb and lspci
mbim would be if is mbim mode and that would be seen via lsusb aka the pci would not use it..

Generaly the lenovo/hp would be pci so mhi is the must..
Them modemmanager

had a fantastic new round of learning curve arround those as got another 4g modem and had a load of fighting to get it working including removing the fcc-lock perminetly at the modem level on it and some other fun!

you only need to install the last two. lsusb wouldn't output anything. it's mbim and qmi over pcie.

Posted: **Thu Nov 23, 2023 1:25 pm**

geraigerai wrote: Tue Nov 14, 2023 9:03 am And one more How do you know if the adapter is with PCIE lines ? E.g. if I would need a full PCIE adapter (not miniPCIE) would this work https://item.taobao.com/item.htm?id=599012341033 ?

That would definitely work

You can see on the PCB that it has the traces.
I got my adapters from them too.

Posted: **Sun Nov 26, 2023 6:45 am**

eskaryo wrote: Sat Nov 25, 2023 6:07 pm 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.

Posted: **Tue Nov 28, 2023 6:13 pm**

To many anoying hangups in the modem world. have had more than my fair share!
-24hrs, this is a royal pain, as takes awhile to realise was actuly arround the same time the day before the things stalled out and changed as somtimes takes time to realise things have stalled.. - Setup timer power socket for 2 am restart = sweet sarenity! (seeing this on my range extender now days so have to re-plug before starting work each morning..
-T99W175 async / sync issue, any time there was a re-conect, firmware crash or restart the modem would not come up propely! pain and only way to work arround was reboot untill the mhi was fixed!!
-Firmware, so many issues it is not funny!
-LTE band!! This is a fun one, we have some dead bands here and some are poor, have had it a good few times and tonight was bad! Modem comes up fine and connected over 3 bands and 10 min later conection is dead and is only on a single band. Removed that band from the list and locked and back to nice and satable..

Further the small pc. it has not been without its own fun!! Plenty problems with 3 layers of network managers messing up latency like crazy and DNS! and after lots of cleanup and still left with it loses DNS settings. And bazar thing is i vi the config file and just save it without change and presto it works again.. When have time will be looking at trying a later kernel..
5G - still have yet to have joy with it and come across some that mentioned some locations faux 4g to look like 5g. Hope to get a 5g phone soon so can double check. but other projects are taking priority.

Posted: **Wed Nov 29, 2023 4:35 pm**

Oh thanks will check out the dns items!!

RE Firmware, for sure, the latest versions have finaly brough the much needed stability! Well worth trying to update to latest!

Posted: **Fri Dec 01, 2023 5:33 am**

How do I send AT commands to this modem? And can anyone share the PDF from Thales? I see /dev/wwan0at0 but at least cannot directly connect with picocom

Edit:
And how do you upgrade the firmware on lenovo version on linux? Currently I have T99W175.F0.1.0.0.7.GC.004 027

Posted: **Fri Dec 01, 2023 10:24 am**

I've found minicom to be the easiest. I posted how to use it on page 1 of this thread, about ~40th post.

Note, sometimes for whatever reason when you open minicom and enter an AT command you wont get a response, just close out of minicom and reopen and try again. I usually start with "ATI" to make sure everything is working and I get a valid response.

Posted: **Fri Dec 01, 2023 11:23 am**

mtl26637 wrote: Fri Dec 01, 2023 10:24 am I usually start with "ATI" to make sure everything is working and I get a valid response.

Or use" ATE" to enable terminal echo so you can see what you type, it should work on minicom I think.

Posted: **Sat Dec 02, 2023 2:35 am**

Ok, what got me confused is that you have to type everything uppercase

not like for T77W968 which seems to be case insensitive, e.g.:

Code: Select all

root@OpenWrt:~# mmcli -m 0 --command="AT^CA_INFO?"
response: 'LTE serving information :
PCC info: Band is LTE_B1, Band_width is 20.0 MHz
SCC1 info: Band is LTE_B3, Band_width is 20.0 MHz
SCC2 info: Band is LTE_B7, Band_width is 20.0 MHz
PCC info: Band is NR5G_N78, Band_width is 200.0 MHz'
root@OpenWrt:~# mmcli -m 0 --command="at^ca_info?"
error: command failed: 'GDBus.Error:org.freedesktop.ModemManager1.Error.Connection.NoCarrier: No carrier'

Minicom worked, but it seemed to cut of the output (possibly because modemanager was also using that port, and picocom simply did not work at all.

It seem quite some commands are supported from T77W968. E.g. to disable certain LTE bands you can do AT^SLBAND:

Code: Select all

 root@OpenWrt:~# mmcli -m 0 --command="AT^SLBAND?"
response: ' WCDMA,Enable Bands :1,2,4,5,6,8,9,19,
 WCDMA,Disable Bands:
 LTE,Enable Bands :1,2,3,4,5,7,8,12,13,14,17,18,19,20,25,26,28,29,30,32,34,38,39,40,41,42,46,48,66,71,
 LTE,Disable Bands:
 NR5G,Enable Bands :1,2,3,5,7,8,12,20,25,28,38,40,41,48,66,71,77,78,79,
 NR5G,Disable Bands:'
root@OpenWrt:~# mmcli -m 0 --command="AT^SLBAND=LTE,1,28"
response: ''
root@OpenWrt:~# mmcli -m 0 --command="AT^SLBAND?"
response: ' WCDMA,Enable Bands :1,2,4,5,6,8,9,19,
 WCDMA,Disable Bands:
 LTE,Enable Bands :1,2,3,4,5,7,8,12,13,14,17,18,19,20,25,26,29,30,32,34,38,39,40,41,42,46,48,66,71,
 LTE,Disable Bands:28,
 NR5G,Enable Bands :1,2,3,5,7,8,12,20,25,28,38,40,41,48,66,71,77,78,79,
 NR5G,Disable Bands:'

Or you can just select the ones you want by only enabling those:

Code: Select all

root@OpenWrt:~#  mmcli -m 0 --command="AT^SLBAND=LTE,2,1,3,7"
response: ''
root@OpenWrt:~# mmcli -m 0 --command="AT^SLBAND?"
response: ' WCDMA,Enable Bands :1,2,4,5,6,8,9,19,
 WCDMA,Disable Bands:
 LTE,Enable Bands :1,3,7,
 LTE,Disable Bands:2,4,5,8,12,13,14,17,18,19,20,25,26,28,29,30,32,34,38,39,40,41,42,46,48,66,71,
 NR5G,Enable Bands :1,2,3,5,7,8,12,20,25,28,38,40,41,48,66,71,77,78,79,
 NR5G,Disable Bands:'

For the changes to take effect you must restart the modem (rebooting the machine might not be enough if power is not interrupted)

Code: Select all

root@OpenWrt:~# mmcli -m 0 --command="AT+RESET"

other possible commands of interest

Code: Select all

#print various network info
mmcli -m 0 --command="AT^DEBUG?"

#print CA info:
mmcli -m 0 --command="AT^CA_INFO?"

speedtest shows me ~670-700Mbit/s (both speedtest result & OpenWRT realtime graphs) but using curl on http I was not able to go above 300Mbit/s even with parallel streams. Iphone shows 1Gbit/s using speedtest
My RSRP seems to be quite low, so probably need to work on placing the modem somewhere or adding better antennas

Code: Select all

 nr_rsrp:-94.4dBm rx_diversity: 15 (-93.7dBm,-105.2dBm,-93.4dBm,-90.3dBm)

So far on Linux OpenWrt 6.1.62 with that power patch applied seems to have been stable for 24+ hours, so probably I'll just leave the firmware as is.

Overall for the price - cannot complain

Posted: **Wed Dec 27, 2023 2:35 am**

geraigerai wrote: Sat Dec 02, 2023 2:35 am So far on Linux OpenWrt 6.1.62 with that power patch applied seems to have been stable for 24+ hours, so probably I'll just leave the firmware as is.

Overall for the price - cannot complain

Hello, I'm trying to build a router too with this module. Can I ask you which version of the module you have chosen? In which type of router you put the module and how is connected(pci, usb...)?

Posted: **Tue Mar 26, 2024 10:33 am**

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.

Posted: **Tue Mar 26, 2024 10:34 am**

piotrKalw wrote: Wed Dec 27, 2023 2:35 am
Hello, I'm trying to build a router too with this module. Can I ask you which version of the module you have chosen? In which type of router you put the module and how is connected(pci, usb...)?

It's PCIe. But the USB hack was just publicized.

Posted: **Thu Mar 28, 2024 12:36 pm**

Hikaru_ wrote: Tue Mar 26, 2024 10:34 am
piotrKalw wrote: Wed Dec 27, 2023 2:35 am
Hello, I'm trying to build a router too with this module. Can I ask you which version of the module you have chosen? In which type of router you put the module and how is connected(pci, usb...)?
It's PCIe. But the USB hack was just publicized.

Ohh prey tell, were can i find info on the USB hack just publicized? edit, ah i noteded some ref in above post but if there was other details would be interested in finding them

Finaly made progres on finding were settings had been moved to on my other modem so was wandering if they are hidden in another area as well...

Posted: **Thu Mar 28, 2024 3:56 pm**

PaddyX wrote: Thu Mar 28, 2024 12:36 pm Finaly made progres on finding were settings had been moved to on my other modem so was wandering if they are hidden in another area as well...

It's on a Russian site called 4PDA, the link below should Google translate the site automatically.
https://4pda-to.translate.goog/forum/in ... x_tr_tl=en

Specifically, click on the "Attached images" at the bottom of the post to see the mods.
You have to cover the pin in pic#1, and bridge the pads in pic#2.
https://4pda-to.translate.goog/forum/in ... y129097775

Posted: **Fri Mar 29, 2024 1:44 pm**

Many thanks, got it and will be investingating it

Posted: **Sat Mar 30, 2024 2:26 pm**

PaddyX wrote: Fri Mar 29, 2024 1:44 pm 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)

Posted: **Sat Mar 30, 2024 2:28 pm**

BillA wrote: Thu Mar 28, 2024 3:56 pm Specifically, click on the "Attached images" at the bottom of the post to see the mods.
You have to cover the pin in pic#1, and bridge the pads in pic#2.
https://4pda-to.translate.goog/forum/in ... y129097775

You don't have to cover pin 3 if your adapter or m.2 slot doesn't pull it to ground btw. Also the AT command to switch from pcie mode works on the 1.0.0.9 FW in my testing. I've updated all my modules so I can't comment on anything older.

Posted: **Sat Mar 30, 2024 4:52 pm**

Hikaru_ wrote: Sat Mar 30, 2024 2:28 pm
BillA wrote: Thu Mar 28, 2024 3:56 pm Specifically, click on the "Attached images" at the bottom of the post to see the mods.
You have to cover the pin in pic#1, and bridge the pads in pic#2.
https://4pda-to.translate.goog/forum/in ... y129097775
You don't have to cover pin 3 if your adapter or m.2 slot doesn't pull it to ground btw. Also the AT command to switch from pcie mode works on the 1.0.0.9 FW in my testing. I've updated all my modules so I can't comment on anything older.

I was just referencing that 4PDA post, showing both the hardware mod and AT commands.
Maybe newer firmware versions need the hardware mod, but I haven't tested it myself.

Posted: **Sun Mar 31, 2024 9:13 am**

BillA wrote: Sat Mar 30, 2024 4:52 pm I was just referencing that 4PDA post, showing both the hardware mod and AT commands.
Maybe newer firmware versions need the hardware mod, but I haven't tested it myself.

I'm just adding to the post since I've done the mod

I've tested it on both the 1.0.0.X fw. You really only need it if pin 3 is tied to ground on your adapter/slot. It isn't a matter of firmware since this is just the config pins.
The AT^PCIEMODE=0 command seems to work though without any hardware mods on the 1.0.0.9. Haven't tested 6.0.0.6 since that's the version for a different variant of T99W175. Reference: https://github.com/fwupd/firmware-lenov ... 1260807326

Posted: **Sun Apr 07, 2024 3:35 am**

Hi, I’m interested in building a custom router with this cheap 5G module. I’ve found that right now this module cost about 60/70€. I read some posts, but I think things have changed through the years. How is the support in Linux right now? Do I need to patch the kernel and recompile it or is it everything ready to support the module? What should I buy to use it in Linux PC or openwrt x64? I have a desktop motherboard with pcie slot and m2 key m. What adapter do I need? Does someone has openwrt on x64 PC and is using this module as a router? What are the difference between Dell, HP, Lenovo, Foxconn?

Posted: **Sun Apr 07, 2024 9:58 am**

fabri01 wrote: Sun Apr 07, 2024 3:35 am Hi, I’m interested in building a custom router with this cheap 5G module. I’ve found that right now this module cost about 60/70€. I read some posts, but I think things have changed through the years. How is the support in Linux right now? Do I need to patch the kernel and recompile it or is it everything ready to support the module? What should I buy to use it in Linux PC or openwrt x64? I have a desktop motherboard with pcie slot and m2 key m. What adapter do I need? Does someone has openwrt on x64 PC and is using this module as a router? What are the difference between Dell, HP, Lenovo, Foxconn?

Go for the lenovo one. It has better support and driver/firware rate. There was one on that had it working on openwrt but for myself I had gone with HP and that is not as compatable so had to go the linux route. With a little bit of work it can be done!
Need to have another round with it to figure out issues on my side.. Also my location the 5g is a little odd like they just converted 4g+ so have not managed to get the modem into 5g mode yet. Again need to do another round of testing as some sims did not support it and some contacts and since last trying they have updated my other contracts to 5g covered.. (hoping to get a 5g phone soon to be able to cross check)

Posted: **Sun Apr 07, 2024 11:39 am**

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?
2) 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?
3) Does the AT command to put the module in USB mode without soldering works?

Wireless Joint

X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem

Re: X55 T99W175 modem