xmm7360 / xmm7360-pci

PCI driver for Fibocom L850-GL modem based on Intel XMM7360 modem
422 stars 82 forks source link

failed state on startup and failed to connect after restart service #227

Closed zeretkk closed 2 months ago

zeretkk commented 3 months ago

Hey, i have fresh fedora installation with this plugin installed on my ThinkPad A285 with XMM7360. After reboot i have "No SIM" in my gnome settings, and modem in failed state:

➜  ~ mmcli -m 0
  -----------------------------
  General  |              path: /org/freedesktop/ModemManager1/Modem/0
           |         device id: 0aba5cca839ac8b2d833b17c09ffdc538eb681b2
  -----------------------------
  Hardware |      manufacturer: Fibocom
           |             model: L850 LTE Module","L850
           | firmware revision: 18500.5001.00.05.27.30
           |         supported: gsm-umts, lte
           |           current: gsm-umts, lte
           |      equipment id: 015184005031831
  -----------------------------
  System   |            device: /sys/devices/pci0000:00/0000:00:01.5/0000:05:00.0
           |           physdev: /sys/devices/pci0000:00/0000:00:01.5/0000:05:00.0
           |           drivers: iosm
           |            plugin: Intel
           |      primary port: wwan0at1
           |             ports: wwan0 (net), wwan0at1 (at)
  -----------------------------
  Status   |             state: failed
           |     failed reason: sim-missing
           |       power state: low
  -----------------------------
  Modes    |         supported: allowed: 3g, 4g; preferred: none
           |           current: allowed: 3g, 4g; preferred: none
  -----------------------------
  3GPP     |              imei: 015184005031831

Manager service status:

Jul 04 15:23:01 fedora ModemManager[942]: <msg> [base-manager] modem for device '/sys/devices/pci0000:00/0000:00:01.5/0000:05:00.0' successfully created
Jul 04 15:23:01 fedora ModemManager[942]: <msg> [modem0] state changed (unknown -> locked)
Jul 04 15:23:01 fedora ModemManager[942]: <wrn> [modem0] modem couldn't be initialized: Couldn't check unlock status: SIM not inserted
Jul 04 15:23:01 fedora ModemManager[942]: <msg> [modem0] state changed (locked -> failed)
Jul 04 15:23:07 fedora ModemManager[942]: <wrn> [modem0] port wwan0at1 timed out 2 consecutive times
Jul 04 15:23:10 fedora ModemManager[942]: <wrn> [modem0] port wwan0at1 timed out 3 consecutive times
Jul 04 15:23:13 fedora ModemManager[942]: <wrn> [modem0] port wwan0at1 timed out 4 consecutive times
Jul 04 15:23:16 fedora ModemManager[942]: <wrn> [modem0] port wwan0at1 timed out 5 consecutive times
Jul 04 15:23:19 fedora ModemManager[942]: <wrn> [modem0] port wwan0at1 timed out 6 consecutive times
Jul 04 15:23:19 fedora ModemManager[942]: <wrn> [modem0] error initializing: Modem in failed state: sim-missing

After restarting modemanager service, i immediate take connection failed notification: image Same message when i trying to enable connection in gnome settings image tried few SIM-cards of different operators, that's works under windows, same behavior

manager status:

Jul 04 15:34:23 fedora ModemManager[4541]: <msg> [modem0] simple connect state (7/10): wait to get packet service state attached
Jul 04 15:34:23 fedora ModemManager[4541]: <msg> [modem0] simple connect state (8/10): bearer
Jul 04 15:34:23 fedora ModemManager[4541]: <msg> [modem0] simple connect state (9/10): connect
Jul 04 15:34:23 fedora ModemManager[4541]: <msg> [modem0] state changed (registered -> connecting)
Jul 04 15:34:23 fedora ModemManager[4541]: <msg> [modem0] mobile equipment request to deactivate context (cid 0)
Jul 04 15:34:23 fedora ModemManager[4541]: <wrn> [modem0/bearer2] connection attempt #12 failed: "No report available"
Jul 04 15:34:23 fedora ModemManager[4541]: <msg> [modem0] state changed (connecting -> registered)
Jul 04 15:34:23 fedora ModemManager[4541]: <msg> [modem0/bearer2] connection #12 finished: duration 0s
Jul 04 15:34:23 fedora ModemManager[4541]: <wrn> [modem0] couldn't connect bearer: "No report available"
Jul 04 15:34:23 fedora ModemManager[4541]: <msg> [modem0] mobile equipment request to activate context (cid 0)
zeretkk commented 3 months ago

gues most of this issue is related to modemmanager, and it should be the MM issue...