Qualcomm Snapdragon X55 5G does not turn on

Bug #1973289 reported by Nikolaj Hansen
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
modemmanager (Ubuntu)
New
Undecided
Unassigned
network-manager (Ubuntu)
New
Undecided
Unassigned

Bug Description

The system tries to configure the device, but never manages to turn on the hardware. I have to do it by hand by using

sudo qmicli -p -d /dev/wwan0mbim0 --device-open-auto --dms-foxconn-set-fcc-authentication=0

I also have a case here on ask ubuntu:

https://askubuntu.com/questions/1407956/ubuntu-22-04-lts-qualcomm-snapdragon-x55-5g-networkmanager-config

  -----------------------------------
  General | path: /org/freedesktop/ModemManager1/Modem/0
           | device id: 7099c435a92638d780ea65442842224ca7bfcf8c
  -----------------------------------
  Hardware | manufacturer: foxconn
           | model: Qualcomm Snapdragon X55 5G
           | firmware revision: T99W175.F0.0.0.5.7.GC.004
           | 076
           | carrier config: GCF
           | carrier config revision: 0A000804
           | h/w revision: Qualcomm Snapdragon X55 5G
           | supported: gsm-umts, lte, 5gnr
           | current: gsm-umts, lte, 5gnr
           | equipment id: 015805000279146
  -----------------------------------
  System | device: /sys/devices/pci0000:00/0000:00:1c.0/0000:08:00.0
           | drivers: mhi-pci-generic
           | plugin: foxconn
           | primary port: wwan0mbim0
           | ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim),
           | wwan0qcdm0 (qcdm)
  -----------------------------------
  Status | unlock retries: sim-pin2 (3)
           | state: disabled
           | power state: low
           | signal quality: 0% (cached)
  -----------------------------------
  Modes | supported: allowed: 3g; preferred: none
           | allowed: 4g; preferred: none
           | allowed: 3g, 4g; preferred: 4g
           | allowed: 3g, 4g; preferred: 3g
           | allowed: 5g; preferred: none
           | allowed: 4g, 5g; preferred: 5g
           | allowed: 4g, 5g; preferred: 4g
           | allowed: 3g, 5g; preferred: 5g
           | allowed: 3g, 5g; preferred: 3g
           | allowed: 3g, 4g, 5g; preferred: 5g
           | allowed: 3g, 4g, 5g; preferred: 4g
           | allowed: 3g, 4g, 5g; preferred: 3g
           | current: allowed: 3g, 4g; preferred: 4g
  -----------------------------------
  Bands | supported: utran-1, utran-3, utran-4, utran-6, utran-5, utran-8,
           | utran-9, utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5,
           | eutran-7, eutran-8, eutran-12, eutran-13, eutran-14, eutran-17,
           | eutran-18, eutran-19, eutran-20, eutran-25, eutran-26, eutran-28,
           | eutran-29, eutran-30, eutran-32, eutran-34, eutran-38, eutran-39,
           | eutran-40, eutran-41, eutran-42, eutran-46, eutran-48, eutran-66,
           | eutran-71, utran-19
           | current: utran-1, utran-4, utran-6, utran-5, utran-8, utran-9,
           | utran-2, eutran-1, eutran-2, eutran-3, eutran-4, eutran-5, eutran-7,
           | eutran-8, eutran-12, eutran-13, eutran-14, eutran-17, eutran-18,
           | eutran-19, eutran-20, eutran-25, eutran-26, eutran-28, eutran-29,
           | eutran-30, eutran-32, eutran-34, eutran-38, eutran-39, eutran-40,
           | eutran-41, eutran-42, eutran-46, eutran-48, eutran-66, eutran-71,
           | utran-19
  -----------------------------------
  IP | supported: ipv4, ipv6, ipv4v6
  -----------------------------------
  3GPP | imei: 015805000279146
           | enabled locks: fixed-dialing
  -----------------------------------
  3GPP EPS | ue mode of operation: csps-2
           | initial bearer ip type: ipv4v6
  -----------------------------------
  SIM | primary sim path: /org/freedesktop/ModemManager1/SIM/0
           | sim slot paths: slot 1: /org/freedesktop/ModemManager1/SIM/0 (active)
           | slot 2: /org/freedesktop/ModemManager1/SIM/1

This worked better in 21.10 where the modem could be turned on and

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: network-manager-gnome 1.24.0-1ubuntu3
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri May 13 10:51:14 2022
InstallationDate: Installed on 2021-05-25 (352 days ago)
InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1)
SourcePackage: network-manager-applet
UpgradeStatus: Upgraded to jammy on 2022-04-25 (18 days ago)
nmcli-nm:
 RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN
 running 1.36.4 connected started full enabled enabled disabled enabled disabled

Revision history for this message
Nikolaj Hansen (barnabasdk) wrote :
Revision history for this message
Nikolaj Hansen (barnabasdk) wrote :

This is a bug on certified hardware

https://ubuntu.com/certified/202102-28710

tags: added: network wwan
affects: network-manager-applet (Ubuntu) → network-manager (Ubuntu)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.