WWAN Cellular configuration, device not found

[perezmarc]

Hello,
I'm trying to configure a WANN modem M.2 based on chipset Qualcomm x55 as internet interface.
In theory, it has Linux support and found some users having no issue in this forum.

The problem is that when I try to set the device as interface, it says no devices are there.
I've tried following the documentation for WWAN, but since my device is not found I fail to proceed.

What am I missing and how can I properly troubleshoot?

I've tried installing the packages related qmi, here's my full list of opkg list:

base-files - 1550-r23630-842932a63d
bnx2-firmware - 20230804-1
busybox - 1.36.1-1
ca-bundle - 20230311-1
cgi-io - 2022-08-10-901b0f04-21
dbus - 1.13.18-12
dnsmasq - 2.89-4
dropbear - 2022.82-5
e2fsprogs - 1.47.0-2
firewall4 - 2023-09-01-598d9fbb-1
fstools - 2023-02-28-bfe882d5-1
fwtool - 2019-11-12-8f7fe925-1
getrandom - 2022-08-13-4c7b720b-2
glib2 - 2.74.0-5
grub2 - 2.06-5
grub2-bios-setup - 2.06-5
grub2-efi - 2.06-5
hostapd - 2023-09-08-e5ccbfc6-6
hostapd-common - 2023-09-08-e5ccbfc6-6
iw - 5.19-1
iwinfo - 2023-07-01-ca79f641-1
iwlwifi-firmware-iwl7265 - 20230804-1
jansson4 - 2.14-3
jshn - 2023-05-23-75a3b870-1
jsonfilter - 2018-02-04-c7e938d6-1
kernel - 5.15.137-1-47964456485559d992fe6f536131fc64
kmod-amazon-ena - 5.15.137-1
kmod-amd-xgbe - 5.15.137-1
kmod-ath - 5.15.137+6.1.24-3
kmod-ath10k - 5.15.137+6.1.24-3
kmod-ath9k - 5.15.137+6.1.24-3
kmod-ath9k-common - 5.15.137+6.1.24-3
kmod-b43 - 5.15.137+6.1.24-3
kmod-bcma - 5.15.137-1
kmod-bnx2 - 5.15.137-1
kmod-button-hotplug - 5.15.137-3
kmod-cfg80211 - 5.15.137+6.1.24-3
kmod-crypto-acompress - 5.15.137-1
kmod-crypto-aead - 5.15.137-1
kmod-crypto-ccm - 5.15.137-1
kmod-crypto-cmac - 5.15.137-1
kmod-crypto-crc32c - 5.15.137-1
kmod-crypto-ctr - 5.15.137-1
kmod-crypto-gcm - 5.15.137-1
kmod-crypto-gf128 - 5.15.137-1
kmod-crypto-ghash - 5.15.137-1
kmod-crypto-hash - 5.15.137-1
kmod-crypto-hmac - 5.15.137-1
kmod-crypto-manager - 5.15.137-1
kmod-crypto-null - 5.15.137-1
kmod-crypto-rng - 5.15.137-1
kmod-crypto-seqiv - 5.15.137-1
kmod-crypto-sha512 - 5.15.137-1
kmod-e1000 - 5.15.137-1
kmod-e1000e - 5.15.137-1
kmod-forcedeth - 5.15.137-1
kmod-fs-vfat - 5.15.137-1
kmod-hwmon-core - 5.15.137-1
kmod-i2c-algo-bit - 5.15.137-1
kmod-i2c-core - 5.15.137-1
kmod-igb - 5.15.137-1
kmod-igc - 5.15.137-1
kmod-input-core - 5.15.137-1
kmod-iwlwifi - 5.15.137+6.1.24-3
kmod-ixgbe - 5.15.137-1
kmod-lib-cordic - 5.15.137-1
kmod-lib-crc-ccitt - 5.15.137-1
kmod-lib-crc32c - 5.15.137-1
kmod-lib-lzo - 5.15.137-1
kmod-libphy - 5.15.137-1
kmod-mac80211 - 5.15.137+6.1.24-3
kmod-mdio - 5.15.137-1
kmod-mdio-devres - 5.15.137-1
kmod-mhi-bus - 5.15.137-1
kmod-mhi-pci-generic - 5.15.137-1
kmod-mii - 5.15.137-1
kmod-nf-conntrack - 5.15.137-1
kmod-nf-conntrack6 - 5.15.137-1
kmod-nf-flow - 5.15.137-1
kmod-nf-log - 5.15.137-1
kmod-nf-log6 - 5.15.137-1
kmod-nf-nat - 5.15.137-1
kmod-nf-reject - 5.15.137-1
kmod-nf-reject6 - 5.15.137-1
kmod-nfnetlink - 5.15.137-1
kmod-nft-core - 5.15.137-1
kmod-nft-fib - 5.15.137-1
kmod-nft-nat - 5.15.137-1
kmod-nft-offload - 5.15.137-1
kmod-nls-base - 5.15.137-1
kmod-nls-cp437 - 5.15.137-1
kmod-nls-iso8859-1 - 5.15.137-1
kmod-nls-utf8 - 5.15.137-1
kmod-phy-realtek - 5.15.137-1
kmod-ppp - 5.15.137-1
kmod-pppoe - 5.15.137-1
kmod-pppox - 5.15.137-1
kmod-pps - 5.15.137-1
kmod-ptp - 5.15.137-1
kmod-r8169 - 5.15.137-1
kmod-random-core - 5.15.137-1
kmod-slhc - 5.15.137-1
kmod-ssb - 5.15.137-1
kmod-tg3 - 5.15.137-1
kmod-usb-core - 5.15.137-1
kmod-usb-net - 5.15.137-1
kmod-usb-net-cdc-ether - 5.15.137-1
kmod-usb-net-cdc-mbim - 5.15.137-1
kmod-usb-net-cdc-ncm - 5.15.137-1
kmod-usb-net-qmi-wwan - 5.15.137-1
kmod-usb-serial - 5.15.137-1
kmod-usb-serial-option - 5.15.137-1
kmod-usb-serial-wwan - 5.15.137-1
kmod-usb-wdm - 5.15.137-1
libattr - 2.5.1-1
libblkid1 - 2.39-2
libblobmsg-json20230523 - 2023-05-23-75a3b870-1
libc - 1.2.4-4
libcbor0 - 0.8.0-1
libcomerr0 - 1.47.0-2
libdbus - 1.13.18-12
libevdev - 1.13.0-1
libexpat - 2.5.0-1
libext2fs2 - 1.47.0-2
libf2fs6 - 1.16.0-1
libffi - 3.4.2-2
libfido2-1 - 1.12.0-1
libgcc1 - 12.3.0-4
libiwinfo-data - 2023-07-01-ca79f641-1
libiwinfo20230701 - 2023-07-01-ca79f641-1
libjson-c5 - 0.16-3
libjson-script20230523 - 2023-05-23-75a3b870-1
libkmod - 31-1
liblucihttp-ucode - 2023-03-15-9b5b683f-1
liblucihttp0 - 2023-03-15-9b5b683f-1
libmbedtls12 - 2.28.5-2
libmbim - 1.28.4-1
libmnl0 - 1.0.5-1
libmount1 - 2.39-2
libncurses6 - 6.4-2
libnftnl11 - 1.2.6-1
libnl-tiny1 - 2023-07-27-bc92a280-1
libopenssl3 - 3.0.12-1
libparted - 3.6-1
libpci - 3.10.0-1
libpcre2 - 10.42-1
libpthread - 1.2.4-4
libqmi - 1.32.4-1
libqrtr-glib - 1.2.2-3
libreadline8 - 8.2-1
librt - 1.2.4-4
libsmartcols1 - 2.39-2
libss2 - 1.47.0-2
libubox20230523 - 2023-05-23-75a3b870-1
libubus20230605 - 2023-06-05-f787c97b-1
libuci20130104 - 2023-08-10-5781664d-1
libuclient20201210 - 2023-04-13-007d9454-1
libucode20230711 - 2023-11-07-a6e75e02-1
libudev-zero - 1.0.1-1
libustream-mbedtls20201210 - 2023-02-25-498f6e26-1
libuuid1 - 2.39-2
logd - 2022-08-13-4c7b720b-2
losetup - 2.39-2
lsblk - 2.39-2
luci - git-23.051.66410-a505bb1
luci-app-firewall - git-23.306.38853-a0466cd
luci-app-opkg - git-23.311.75635-769b30c
luci-base - git-23.306.39416-c86c256
luci-light - git-23.024.33244-34dee82
luci-mod-admin-full - git-19.253.48496-3f93650
luci-mod-network - git-23.313.56166-6da284d
luci-mod-status - git-23.306.52197-bdcd3e0
luci-mod-system - git-23.306.39416-7d3abf8
luci-proto-ipv6 - git-21.148.48881-79947af
luci-proto-modemmanager - git-23.338.81439-5f6fc19
luci-proto-ppp - git-21.158.38888-88b9d84
luci-proto-qmi - git-21.231.25157-5ff3ef7
luci-ssl - git-23.035.26083-7550ad6
luci-theme-bootstrap - git-23.306.39416-c86c256
mkf2fs - 1.16.0-1
modemmanager - 1.20.6-12
mtd - 26
netifd - 2023-11-10-35facc83-1.1
nftables-json - 1.0.8-1
odhcp6c - 2023-05-12-bcd28363-20
odhcpd-ipv6only - 2023-10-24-d8118f6e-1
openssh-keygen - 9.5p1-1
openssh-server - 9.5p1-1
openwrt-keyring - 2022-03-25-62471e69-2
opkg - 2022-02-24-d038e5b6-2
parted - 3.6-1
partx-utils - 2.39-2
pciids - 0.359-1
pciutils - 3.10.0-1
ppp - 2.4.9.git-2021-01-04-4
ppp-mod-pppoe - 2.4.9.git-2021-01-04-4
procd - 2023-06-25-2db83655-2
procd-seccomp - 2023-06-25-2db83655-2
procd-ujail - 2023-06-25-2db83655-2
px5g-mbedtls - 10
qmi-utils - 1.32.4-1
r8169-firmware - 20230804-1
resize2fs - 1.47.0-2
rpcd - 2023-07-01-c07ab2f9-1
rpcd-mod-file - 2023-07-01-c07ab2f9-1
rpcd-mod-iwinfo - 2023-07-01-c07ab2f9-1
rpcd-mod-luci - 20230123-1
rpcd-mod-rrdns - 20170710
rpcd-mod-ucode - 2023-07-01-c07ab2f9-1
terminfo - 6.4-2
ubox - 2022-08-13-4c7b720b-2
ubus - 2023-06-05-f787c97b-1
ubusd - 2023-06-05-f787c97b-1
uci - 2023-08-10-5781664d-1
uclient-fetch - 2023-04-13-007d9454-1
ucode - 2023-11-07-a6e75e02-1
ucode-mod-fs - 2023-11-07-a6e75e02-1
ucode-mod-html - 1
ucode-mod-math - 2023-11-07-a6e75e02-1
ucode-mod-nl80211 - 2023-11-07-a6e75e02-1
ucode-mod-rtnl - 2023-11-07-a6e75e02-1
ucode-mod-ubus - 2023-11-07-a6e75e02-1
ucode-mod-uci - 2023-11-07-a6e75e02-1
ucode-mod-uloop - 2023-11-07-a6e75e02-1
uhttpd - 2023-06-25-34a8a74d-1
uhttpd-mod-ubus - 2023-06-25-34a8a74d-1
uqmi - 2022-10-20-c8c9f105-1
urandom-seed - 3
urngd - 2023-11-01-44365eb1-1
usign - 2020-05-23-f1f65026-1
wireless-regdb - 2023.09.01-1
wpa-supplicant - 2023-09-08-e5ccbfc6-6
wwan - 2019-04-29-6
zlib - 1.2.13-1

Thanks

[perezmarc]

uqmi -d /dev/cdc-wdm0 --get-data-status
Failed to open device

[AndrewZ]

Are you talking about T99W175 modem?
Where it is plugged to? Are you sure that PCI lines are present on the M.2 connector you use?
What is in lspci -nn response?
It's too early to talk about QMI, etc.

[frollic]

@AndrewZ

What is in lspci response?

Which is basically what you were told to post yesterday already, @perezmarc.

[perezmarc]

Apologies if I did not see the answer.

Yes, it's Foxconn T99W175 modem based on chipset Qualcom X55.

Here's the response of lspci:

00:00.0 Host bridge: Intel Corporation Device 4e24
00:02.0 VGA compatible controller: Intel Corporation JasperLake [UHD Graphics] (rev 01)
00:04.0 Signal processing controller: Intel Corporation Dynamic Tuning service
00:08.0 System peripheral: Intel Corporation Device 4e11
00:14.0 USB controller: Intel Corporation Device 4ded (rev 01)
00:14.2 RAM memory: Intel Corporation Device 4def (rev 01)
00:15.0 Serial bus controller: Intel Corporation Serial IO I2C Host Controller (rev 01)
00:15.1 Serial bus controller: Intel Corporation Serial IO I2C Host Controller (rev 01)
00:16.0 Communication controller: Intel Corporation Management Engine Interface (rev 01)
00:17.0 SATA controller: Intel Corporation Device 4dd3 (rev 01)
00:1a.0 SD Host controller: Intel Corporation Device 4dc4 (rev 01)
00:1c.0 PCI bridge: Intel Corporation Device 4db8 (rev 01)
00:1c.1 PCI bridge: Intel Corporation Device 4db9 (rev 01)
00:1c.4 PCI bridge: Intel Corporation Device 4dbc (rev 01)
00:1c.5 PCI bridge: Intel Corporation Device 4dbd (rev 01)
00:1c.6 PCI bridge: Intel Corporation Device 4dbe (rev 01)
00:1f.0 ISA bridge: Intel Corporation Device 4d87 (rev 01)
00:1f.3 Audio device: Intel Corporation Jasper Lake HD Audio (rev 01)
00:1f.4 SMBus: Intel Corporation Jasper Lake SMBus (rev 01)
00:1f.5 Serial bus controller: Intel Corporation Jasper Lake SPI Controller (rev 01)
01:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
02:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
03:00.0 Network controller: Intel Corporation Wireless 7265 (rev 61)
04:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)
05:00.0 Ethernet controller: Intel Corporation I211 Gigabit Network Connection (rev 03)

It does not look like it's there, right?

[perezmarc]

This is the hardware.

[AndrewZ]

The modem is not there, so I would assume that there are no PCI lines on the M.2 connector being used.

[mk24]

Is PCIe wired to the modem slot? Many boards only have USB connected to the modem slot, and if the modem is PCI only, it is not going to work there.

Does lsusb show the modem?

[perezmarc]

lsusb

Bus 001 Device 002: ID 8087:0a2a
Bus 002 Device 001: ID 1d6b:0003 Linux 5.15.137 xhci-hcd xHCI Host Controller
Bus 001 Device 001: ID 1d6b:0002 Linux 5.15.137 xhci-hcd xHCI Host Controller

There are only 2 usb ports in the board.

What do you mean that there are not pci lines on the m.2 being used?

[AndrewZ]

They are simply not there (highly likely pins 41,43,47,49 are not connected on the PCB). It probably has USB lines (pins 7,9) that you don't need for this modem.

[perezmarc]

So no modem can be connected to a m.2, right?
What options could I have now? maybe connect the modem to the 3rd usb port in the board with a USB - M.2 adaptor (if it exists) ?

[AndrewZ]

You can try a USB capable modem in this M.2 slot.

[perezmarc]

The pins look like they are there though, right?

[AndrewZ]

Obviously they are there ) Think electrical signals, not just pins. For visual analysis check if traces are coming to the pins I mentioned.
If your device has a SIM card slot - check which connector (M.2, mPCIe) it is wired to. If it is connected to M.2, then most likely it has USB signals as well and you could use another modem there.