Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1950282

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

apport information

mtk_t7xx 0000:55:00.0: enabling device (0000 -> 0002)
mtk_t7xx 0000:55:00.0: PM configuration timed out
mtk_t7xx: probe of 0000:55:00.0 failed with error -110

Hi Vicamo,

Please let us know if you are able to pick the V5 driver patches already on top of Backported V4 changeset.
Please let us know if any additional help is needed.

Thanks and Best Regards,
Murali

Hi Vicamo,

Please let us know if you are able to pick the V5 driver patches already on top of Backported V4 changeset.
Please let us know if any additional help is needed.

Thanks and Best Regards,
Murali

Hi Vicamo / Stephane,

We manually downloaded the 5.17 specific kernel deb packages
from https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/intermediate-kernel/+packages
and we were able to successfully connect to the modem.

We did no see the issue mentioned in #20

We could use the mmcli -m 0 to get the modem firmware version

We will also attach the logs for your reference.

Thanks and Best Regards,
Murali

Hi Vicamo,

Please let us know once you have further updates on ADL FM350 integration on ADL-P RVP or other OEM devices.
Please do let us know if you need any help from our side.

Thanks and Best Regards,
Murali

Hi Canonical Team,

For FM350 5G 5000 on Windows, please use the attached Telephony tool for 5G.

For Linux, we are still waiting for Canonical team to help on the clarifications for creating the snap package for Firmware Update and Switching tool.

Thanks and Best Regards,
Murali

Hi Canonical Team,

Please request Fibocom team to share the latest modem firmware for FM350, as they would be able to share it.

Thanks and Best Regards,
Murali

Hi Canonical Team,

Please find the latest telephony tool 5G Telephony tool V5.0.29 also available in rdc

URL: https://rdc.intel.com
KitID： 727751
https://www.intel.com/content/www/us/en/secure/design/confidential/software-kits/kit-details.html?kitId=727751

Please try with this tool and let us know in case of any issues.

Thanks and Best Regards,
Murali

Latest FM350 is FR 1.26.13 (equivalent to 81600.0000.00.29.19.16_5000.0000.036.000.036_C40). Intel clarified that we should get that firmware from Fibocom and use that for testing.

hello.

In order to operate the Mediatek M80 5G device normally, I installed the linux-oem-5.17 - 5.17.0-9003.3+exp.11 package attached to the link below.

- https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/intermediate-kernel/+packages

However, after installing the kernel, the following log was output to dmesg, and the device was not recognized.

- mtk_t7xx 0000:55:00.0: enabling device (0000 -> 0002)
- mtk_t7xx 0000:55:00.0: PM configuration timed out
- mtk_t7xx: probe of 0000:55:00.0 failed with error -110

The kernel package was installed in ubuntu 22.04, and when the mmcli -L command was executed, the message "No modems were found" was output.

Are there any additional packages I need to install?

Please advise on how to solve it.

Thanks.

Hi Jaejeon,

The error you have reported seems to be similar to #20.

As provided in comment #23, We had manually downloaded the 5.17 specific kernel deb packages
from https://launchpad.net/~canonical-hwe-team/+archive/ubuntu/intermediate-kernel/+packages
and we were able to successfully connect to the modem.

We did no see the issue that you are mentioning.

We could use the mmcli -m 0 to get the modem firmware version

Please share the logs for your reference.
Any idea which modem firmware you are using ?

As indicated by Stephane in #30, you would need to get the latest modem firmware from Fibocom colleauges and update the firmware using Telephony tool provided by us in #27, if you have access to windows setup

Thanks and Best Regards,
Murali

Hello Muralidharan!

First of all, thanks for the quick reply.

After installing the link's kernel, manually reloading the mtk_t7xx kernel module confirmed that the modem device was found normally.

However, there is still no connection through mmcli, so the requested firmware and related dmesg log are attached.

Also, it would be appreciated if you could advise on where to get information about the firmware of the device or where to obtain the package file.

thank you.

And, here is dmesg log which is filtered with 'mtk_t7xx'

Hi Jaejeon,

As indicated by Stephane in #30, you would need to get the latest modem firmware from Fibocom colleauges and update the firmware using Telephony tool provided by us in #27, if you have access to windows setup

We would request you to retry with the latest modem firmware and share us the test results, with the updated modem firmware.

Thanks and Best Regards,
Murali

Hi Jaejeon,

Please let us know if there are any further opens in this ticket and if not, can we close the ticket.

Thanks and Best Regards,
Murali

We are now running a Dell platform certification with the module, it has an issue about no signal, we are collaborating with ODM to clarify it. Could we leave the bug for a while, I'll notify here once everything is clear.

Thanks,

Hi KC,

Sure, Please share more details once you have more updates.
In case there is a ticket for No Signal issue, please do share.

Thanks and Best Regards,
Murali

to SRU team
this is why & when we would need this modemmanager package soon

at least 2 of top 3 PC OEMs have introduced new RPL-based platforms + FM350-GL to launch with Jammy (22.04) in Q1 '23 and with the fore-runners we need conclude the "feature complete" image release by Nov-18, 2022, and final (production candidate) release by Dec-09, 2022

So the requested timelines for modemmanager updated package is SRU (for Jammy) by the end of Nov '22.

Status changed to 'Confirmed' because the bug affects multiple users.

The 1.20 components have been uploaded to the 22.04 SRU queue now.

@oem it would be nice if you could improve the bug description to have a more detailed testcase and regression potential section

@seb

Sorry, I did not see the modemmanager (1.20.0-1ubuntu1) in jammy-proposed, would you please confirm the process?

% rmadison modemmanager
 modemmanager | 1.0.0-2ubuntu1 | trusty | source, amd64, arm64, armhf, i386, powerpc, ppc64el
 modemmanager | 1.0.0-2ubuntu1.1 | trusty-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el
 modemmanager | 1.4.12-1ubuntu1 | xenial | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
 modemmanager | 1.6.4-1ubuntu0.16.04.1 | xenial-updates | source, amd64, arm64, armhf, i386, powerpc, ppc64el, s390x
 modemmanager | 1.6.8-2ubuntu1 | bionic | source, amd64, arm64, armhf, i386, ppc64el, s390x
 modemmanager | 1.10.0-1~ubuntu18.04.2 | bionic-updates | source, amd64, arm64, armhf, i386, ppc64el, s390x
 modemmanager | 1.12.8-1 | focal | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.18.6-1~ubuntu20.04.1 | focal-updates | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.18.6-1 | jammy | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.19~git20220905-0ubuntu2 | kinetic | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.20.0-1~ubuntu22.10.1 | kinetic-proposed | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x
 modemmanager | 1.20.0-1ubuntu1 | lunar | source, amd64, arm64, armhf, i386, ppc64el, riscv64, s390x

Hello You-Sheng, or anyone else affected,

Accepted libmbim into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libmbim/1.28.0-1~ubuntu20.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello You-Sheng, or anyone else affected,

Accepted libqmi into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libqmi/1.32.0-1ubuntu0.22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello You-Sheng, or anyone else affected,

Accepted modemmanager into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/modemmanager/1.20.0-1~ubuntu22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

All autopkgtests for the newly accepted libmbim (1.28.0-1~ubuntu20.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

fwupd/1.7.9-1~22.04.1 (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#libmbim

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

All autopkgtests for the newly accepted libqmi (1.32.0-1ubuntu0.22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

fwupd/1.7.9-1~22.04.1 (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#libqmi

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

All autopkgtests for the newly accepted modemmanager (1.20.0-1~ubuntu22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

fwupd/1.7.9-1~22.04.1 (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#modemmanager

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

request regression test on ~device-certification channel. https://chat.canonical.com/canonical/pl/mbrptg5713fbxqmwk8ooc97dmh

Tested on machine with FM350 installed, with oem 6.0.0-1006 kernel, modem manager 1.20.0-1~ubuntu22.04.1, libmbim-glib4 1.28.0-1~ubuntu20.04 and libqmi-glib5 1.32.0-1~ubuntu0.22.04.1. System can connect to 5g network.

  -----------------------------------
  General | path: /org/freedesktop/ModemManager1/Modem/0
            | device id: b429ecd3cf5b14431f765b3a415cda29db1d504b
  -----------------------------------
  Hardware | manufacturer: generic
            | model: MBIM [14C3:4D75]
            | firmware revision: 81600.0000.00.29.21.24_GC
            | D47
            | h/w revision: V1.0.6
            | supported: gsm-umts, lte, 5gnr
            | current: gsm-umts, lte, 5gnr
            | equipment id: 358198520003138
  -----------------------------------
  System | device: /sys/devices/pci0000:00/0000:00:1c.0/0000:71:00.0
            | drivers: mtk_t7xx
            | plugin: generic
            | primary port: wwan0mbim0
            | ports: wwan0 (net), wwan0at0 (at), wwan0mbim0 (mbim)
  -----------------------------------
  Status | lock: sim-pin2
            | unlock retries: sim-pin2 (3)
            | state: connected
            | power state: on
            | access tech: lte, 5gnr
            | signal quality: 64% (cached)
  -----------------------------------
  Modes | supported: allowed: 3g; preferred: none
            | allowed: 4g; preferred: none
            | allowed: 3g, 4g; preferred: none
            | allowed: 5g; preferred: none
            | allowed: 3g, 5g; preferred: none
            | allowed: 4g, 5g; preferred: none
            | allowed: 3g, 4g, 5g; preferred: none
            | current: allowed: 3g, 4g, 5g; preferred: none
  -----------------------------------
  IP | supported: ipv4, ipv6, ipv4v6
  -----------------------------------
  3GPP | imei: 358198520003138
            | enabled locks: fixed-dialing
            | operator id: 46692
            | operator name: Chunghwa Telecom
            | registration: home
            | packet service state: attached
  -----------------------------------
  3GPP EPS | ue mode of operation: csps-2
            | initial bearer path: /org/freedesktop/ModemManager1/Bearer/0
            | initial bearer apn: internet
            | initial bearer ip type: ipv4v6
  -----------------------------------
  3GPP 5GNR | mico mode: disabled
  -----------------------------------
  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/S...

The verification of the Stable Release Update for libmbim has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package libmbim - 1.28.0-1~ubuntu20.04.1

---------------
libmbim (1.28.0-1~ubuntu20.04.1) jammy; urgency=medium

  * Backport the newer modemmanager stack to the LTS as part of
    new hardware enablement including FM350 modems
    (lp: #1950282)

 -- Sebastien Bacher <email address hidden> Tue, 13 Dec 2022 13:35:17 +0100

This bug was fixed in the package modemmanager - 1.20.0-1~ubuntu22.04.1

---------------
modemmanager (1.20.0-1~ubuntu22.04.1) jammy; urgency=medium

  * Backport the newer modemmanager stack to the LTS as part of
    new hardware enablement including FM350 modems
    (lp: #1950282)

 -- Sebastien Bacher <email address hidden> Tue, 13 Dec 2022 13:38:07 +0100

This bug was fixed in the package libqmi - 1.32.0-1ubuntu0.22.04.1

---------------
libqmi (1.32.0-1ubuntu0.22.04.1) jammy; urgency=medium

  * Backport the newer modemmanager stack to the LTS as part of
    new hardware enablement including FM350 modems
    (lp: #1950282)

 -- Sebastien Bacher <email address hidden> Tue, 22 Nov 2022 13:17:29 +0100

Status changed to 'Confirmed' because the bug affects multiple users.