Bug 1938462 - Fibocom L850 is not detected in the system
Summary: Fibocom L850 is not detected in the system
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Fedora
Classification: Fedora
Component: ModemManager
Version: 33
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Lubomir Rintel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-13 17:10 UTC by Edu Alcaniz
Modified: 2021-11-08 06:12 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-07 21:41:03 UTC
Type: Bug
Embargoed:
bcotton: fedora_prioritized_bug-


Attachments (Terms of Use)
Modem Manager GUI (25.70 KB, image/png)
2021-03-13 17:10 UTC, Edu Alcaniz
no flags Details

Description Edu Alcaniz 2021-03-13 17:10:20 UTC
Created attachment 1763170 [details]
Modem Manager GUI

Description of problem:
It seems that Fedora 33 doesn't detect Fibocom L850 or L830 in the Lenovo T490s


Version-Release number of selected component (if applicable):
33

How reproducible:

 ModemManager.service - Modem Manager
     Loaded: loaded (/usr/lib/systemd/system/ModemManager.service; enabled; vendor preset: enabled)
     Active: active (running) since Sat 2021-03-13 18:04:56 CET; 39s ago
   Main PID: 1320 (ModemManager)
      Tasks: 4 (limit: 38219)
     Memory: 10.0M
        CPU: 57ms
     CGroup: /system.slice/ModemManager.service
             └─1320 /usr/sbin/ModemManager

Mar 13 18:04:56 ealcaniz.localdomain systemd[1]: Starting Modem Manager...
Mar 13 18:04:56 ealcaniz.localdomain ModemManager[1320]: <info>  ModemManager (version 1.14.10-1.fc33) starting in system bus...
Mar 13 18:04:56 ealcaniz.localdomain systemd[1]: Started Modem Manager.
Mar 13 18:04:59 ealcaniz.localdomain ModemManager[1320]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.3': not supported by any plugin
Mar 13 18:04:59 ealcaniz.localdomain ModemManager[1320]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1f.6': not supported by any plugin


[ealcaniz@ealcaniz ~]$ lsusb
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 003: ID 04f2:b681 Chicony Electronics Co., Ltd ThinkPad T490 Webcam
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 004: ID 8087:0aaa Intel Corp. Bluetooth 9460/9560 Jefferson Peak (JfP)
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub





Steps to Reproduce:
1.
2.
3.

Actual results:
No detection of HW

Expected results:


Additional info:

Comment 1 Matthew Miller 2021-03-23 17:20:05 UTC
Is this a regression? (That is, did it work before?)

I know WWAN modems run into a lot of difficulties with regulatory compliance and are often hard to get with open source drivers. I know Lenovo is still working on support for the models they ship with Fedora Workstation preinstalled.

Comment 2 Ben Cotton 2021-03-24 17:19:26 UTC
In today's Prioritized Bugs meeting, we agreed to reject this as a prioritized bug as hardware enablement is generally not a qualifier for prioritized bug status and the effect is not widespread. 

https://meetbot.fedoraproject.org/fedora-meeting-1/2021-03-24/fedora_prioritized_bugs_and_issues.2021-03-24-15.05.log.html#l-55

Thank you for nominating it. We agree that this is a good thing to fix and encourage you to post about it in the Lenovo forums: https://forums.lenovo.com/t5/Fedora/bd-p/lx04_en

Comment 3 Peter Robinson 2021-04-30 21:29:56 UTC
It looks like it's based on the Intel LTE Modem which doesn't have support yet in the upstream kernel. The initial underlying, not support specific modems, platform has finally been posted upstream. Given it uses the MBIM interface there's likely no work to be done by ModemManager, in theory when the support lands in the kermel it should just work.

https://www.spinics.net/lists/linux-wireless/msg210149.html

Comment 4 Peter Robinson 2021-09-14 18:03:22 UTC
Should work with 5.14.x but probably also needs ModemManager 1.18.x so it should be supported with Fedora 35. Please test.

Comment 5 Edu Alcaniz 2021-09-14 18:38:51 UTC
Hi the last package available in FEdora 34 is

[ealcaniz@ealcaniz ~]$ rpm -qa | grep ModemManager
modem-manager-gui-mm-ModemManager-0.0.20-3.fc34.x86_64
ModemManager-glib-1.16.8-4.fc34.x86_64
ModemManager-1.16.8-4.fc34.x86_64
[ealcaniz@ealcaniz ~]$ 


When you said it Should work with 5.14.x ? what package? 


How I can test the package?

Comment 6 Peter Robinson 2021-09-14 19:01:24 UTC
> When you said it Should work with 5.14.x ? what package? 

Kernel

> How I can test the package?

Fedora 35 nightly live image?

Comment 7 Ben Cotton 2021-11-04 13:44:01 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 8 Ben Cotton 2021-11-04 14:13:32 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 9 Ben Cotton 2021-11-04 15:11:08 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 10 Edu Alcaniz 2021-11-05 07:18:47 UTC
Thanks, I am using Fedora 34 and the issue still happening. I think it is resolved in Fedora 35.

Comment 11 Edu Alcaniz 2021-11-05 11:37:45 UTC
I upgraded to Fedora 35



● ModemManager.service - Modem Manager
     Loaded: loaded (/usr/lib/systemd/system/ModemManager.service; enabled; vendor preset: enabled)
     Active: active (running) since Fri 2021-11-05 12:36:40 CET; 6s ago
   Main PID: 4766 (ModemManager)
      Tasks: 5 (limit: 38200)
     Memory: 2.3M
        CPU: 37ms
     CGroup: /system.slice/ModemManager.service
             └─4766 /usr/sbin/ModemManager

Nov 05 12:36:40 ealcaniz.localdomain systemd[1]: Starting Modem Manager...
Nov 05 12:36:40 ealcaniz.localdomain ModemManager[4766]: <info>  ModemManager (version 1.18.2-1.fc35) starting in system bus...
Nov 05 12:36:40 ealcaniz.localdomain ModemManager[4766]: [qrtr] socket lookup from 1:0
Nov 05 12:36:40 ealcaniz.localdomain ModemManager[4766]: [qrtr] initial lookup finished
Nov 05 12:36:40 ealcaniz.localdomain systemd[1]: Started Modem Manager.
Nov 05 12:36:42 ealcaniz.localdomain ModemManager[4766]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:14.3': >
Nov 05 12:36:42 ealcaniz.localdomain ModemManager[4766]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1c.4/00>
Nov 05 12:36:42 ealcaniz.localdomain ModemManager[4766]: <info>  [base-manager] couldn't check support for device '/sys/devices/pci0000:00/0000:00:1f.6': >
~
~

I hit the same issue

Comment 12 Edu Alcaniz 2021-11-05 11:38:14 UTC
[ealcaniz@ealcaniz ~]$ rpm -qa | grep Modem
ModemManager-glib-1.18.2-1.fc35.x86_64
ModemManager-1.18.2-1.fc35.x86_64
modem-manager-gui-mm-ModemManager-0.0.20-5.fc35.x86_64

Comment 13 Peter Robinson 2021-11-07 21:41:03 UTC
(In reply to Edu Alcaniz from comment #10)
> Thanks, I am using Fedora 34 and the issue still happening. I think it is
> resolved in Fedora 35.

Correct, although there may be still some selinux issues which are being tracked in a selinux bug.


Note You need to log in before you can comment on or make changes to this bug.