[SOLVED (Cause: FCC lock)] ModemManager: 'Invalid transition'

43615 · 2022-03-07 10:21:18

After setting up a 3G connection and trying to activate it, ModemManager fails immediately. Journal entries from one attempt:

Mar 07 11:18:27 thiccpad-arch audit[560]: USYS_CONFIG pid=560 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics interface="wlo1" ifindex=4 args=2000 pid=706 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
Mar 07 11:18:27 thiccpad-arch NetworkManager[560]: <info>  [1646648307.6247] audit: op="statistics" interface="wlo1" ifindex=4 args="2000" pid=706 uid=1000 result="success"
Mar 07 11:18:27 thiccpad-arch kernel: audit: type=1111 audit(1646648307.621:142): pid=560 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics interface="wlo1" ifindex=4 args=2000 pid=706 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
Mar 07 11:18:29 thiccpad-arch NetworkManager[560]: <info>  [1646648309.2830] device (cdc-wdm0): Activation: starting connection 'O2' (586830be-c384-4f1c-9df7-d8548e49762f)
Mar 07 11:18:29 thiccpad-arch audit[560]: USYS_CONFIG pid=560 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-activate uuid=586830be-c384-4f1c-9df7-d8548e49762f name="O2" pid=706 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
Mar 07 11:18:29 thiccpad-arch NetworkManager[560]: <info>  [1646648309.2832] audit: op="connection-activate" uuid="586830be-c384-4f1c-9df7-d8548e49762f" name="O2" pid=706 uid=1000 result="success"
Mar 07 11:18:29 thiccpad-arch NetworkManager[560]: <info>  [1646648309.2834] device (cdc-wdm0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Mar 07 11:18:29 thiccpad-arch kernel: audit: type=1111 audit(1646648309.281:143): pid=560 uid=0 auid=4294967295 ses=4294967295 msg='op=connection-activate uuid=586830be-c384-4f1c-9df7-d8548e49762f name="O2" pid=706 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
Mar 07 11:18:29 thiccpad-arch ModemManager[563]: <info>  [modem0] simple connect started...
Mar 07 11:18:29 thiccpad-arch ModemManager[563]: <info>  [modem0] simple connect state (3/8): enable
Mar 07 11:18:29 thiccpad-arch ModemManager[563]: <info>  [modem0] state changed (disabled -> enabling)
Mar 07 11:18:29 thiccpad-arch ModemManager[563]: <warn>  [modem0] Failure
Mar 07 11:18:29 thiccpad-arch ModemManager[563]: <warn>  [modem0] Failure
Mar 07 11:18:29 thiccpad-arch ModemManager[563]: <warn>  [modem0] couldn't enable interface: 'Invalid transition'
Mar 07 11:18:29 thiccpad-arch ModemManager[563]: <info>  [modem0] state changed (enabling -> disabled)
Mar 07 11:18:29 thiccpad-arch NetworkManager[560]: <info>  [1646648309.3784] device (cdc-wdm0): state change: prepare -> disconnected (reason 'user-requested', sys-iface-state: 'managed')
Mar 07 11:18:29 thiccpad-arch ModemManager[563]: <info>  [modem0] simple connect started...
Mar 07 11:18:29 thiccpad-arch ModemManager[563]: <info>  [modem0] simple connect state (3/8): enable
Mar 07 11:18:29 thiccpad-arch ModemManager[563]: <info>  [modem0] state changed (disabled -> enabling)
Mar 07 11:18:29 thiccpad-arch ModemManager[563]: <warn>  [modem0] Failure
Mar 07 11:18:29 thiccpad-arch ModemManager[563]: <warn>  [modem0] Failure
Mar 07 11:18:29 thiccpad-arch ModemManager[563]: <warn>  [modem0] couldn't enable interface: 'Invalid transition'
Mar 07 11:18:29 thiccpad-arch ModemManager[563]: <info>  [modem0] state changed (enabling -> disabled)
Mar 07 11:18:30 thiccpad-arch audit[560]: USYS_CONFIG pid=560 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics interface="wlo1" ifindex=4 args=0 pid=706 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'
Mar 07 11:18:30 thiccpad-arch NetworkManager[560]: <info>  [1646648310.6039] audit: op="statistics" interface="wlo1" ifindex=4 args="0" pid=706 uid=1000 result="success"
Mar 07 11:18:30 thiccpad-arch kernel: audit: type=1111 audit(1646648310.601:144): pid=560 uid=0 auid=4294967295 ses=4294967295 msg='op=statistics interface="wlo1" ifindex=4 args=0 pid=706 uid=1000 result=success exe="/usr/bin/NetworkManager" hostname=? addr=? terminal=? res=success'

This process repeats many times per second and it doesn't give up, which eventually makes the system unresponsive.
The exact same hardware did work perfectly on an earlier installation; the only relevant difference is that I used iwd and Plasma's default connection editor instead of NetworkManager and plasma-nm. Sorry if that's inaccurate/irrelevant, I'm nowhere near experienced.

All software is up to date, hardware:
HP EliteBook 8770w
HP un2430 Mobile Broadband Module

Last edited by 43615 (2022-03-09 10:48:33)

43615 · 2022-03-07 11:07:27

Update: After rebooting because of something unrelated, MM no longer recognizes the modem at all (-L says "No modems were found"). No idea why or what to do.

SUB-ISSUE RESOLVED

by booting from the live ISO and trying to connect with it.

Last edited by 43615 (2022-03-09 07:47:55)

ewaller · 2022-03-07 14:46:08

Not sure I can help with #1, but #2 may be because of an improper kernel update.

Compare the output of uname -a and of pacman -Q linux (Assuming you are running the stock kernel. Change this command as appropriate if not)
Ensure the version numbers match.

43615 · 2022-03-08 04:34:32

Both say 5.16.12.arch1-1, more ideas?

-thc · 2022-03-08 16:37:22

I would try to discern between OS-related or hardware-related issue by booting from a Live OS boot medium (Arch install, Ubuntu, PEBakery Windows etc.) and try to reproduce this error there.

43615 · 2022-03-09 07:45:52

Booted with the live Arch ISO (2022-03-01), the modem is available in mmcli but won't connect (exactly the same log entries as above, invalid transition). After booting back into my existing system, however, the modem somehow reappeared both in mmcli and the graphical settings menu (sub-issue resolved). I guess it disabled itself for some reason (I think there was an update to usb_modeswitch) and needed a wakeup call? Still won't connect, same error.

Last edited by 43615 (2022-03-09 07:49:37)

-thc · 2022-03-09 07:52:40

Is a FCC lock in place?

43615 · 2022-03-09 08:14:24

Wow, definitely looks like it. Makes sense that it doesn't work now, since MM only stopped doing it automatically in 1.18.4. Can't find any information/tools for unlocking my specific model, MM doesn't have a script for it.
Model: HP un2430, ID: 03f0:371d

-thc · 2022-03-09 08:58:25

Does downgrading modemmanager to 1.18.4 work?
Is there some tool on HP's download page for this model?

43615 · 2022-03-09 10:47:28

Already checked HP's download site. The only potentially relevant things are some "driver discs" of unknown content, which are only available for old SLED and RHEL versions.

I seem to have found a hack solution though: Just made a link named like my ID to the only available HP script, and apparently that somehow worked! Command for reference:

ln -sf /usr/share/ModemManager/fcc-unlock.available.d/1199 /etc/ModemManager/fcc-unlock.d/03f0:371d

(If you have a different model, get its ID from lsusb and substitute the destination name accordingly)
Definitely suboptimal, but it works. I won't be using the WWAN much anyway (considering my provider disabled 3G service recently, so this modem only gets 2G), it's only a just-in-case backup.
If you're from months/years in the future, please search for a proper unlock script/tool before resorting to this hack.

Last edited by 43615 (2022-03-09 10:49:30)

doak · 2022-05-17 13:35:51

I am speeking from the future

A good explanation to the topic including current solutions are available here: https://modemmanager.org/docs/modemmanager/fcc-unlock/

Arch Linux

#1 2022-03-07 10:21:18

[SOLVED (Cause: FCC lock)] ModemManager: 'Invalid transition'

#2 2022-03-07 11:07:27

Re: [SOLVED (Cause: FCC lock)] ModemManager: 'Invalid transition'

SUB-ISSUE RESOLVED

#3 2022-03-07 14:46:08

Re: [SOLVED (Cause: FCC lock)] ModemManager: 'Invalid transition'

#4 2022-03-08 04:34:32

Re: [SOLVED (Cause: FCC lock)] ModemManager: 'Invalid transition'

#5 2022-03-08 16:37:22

Re: [SOLVED (Cause: FCC lock)] ModemManager: 'Invalid transition'

#6 2022-03-09 07:45:52

Re: [SOLVED (Cause: FCC lock)] ModemManager: 'Invalid transition'

#7 2022-03-09 07:52:40

Re: [SOLVED (Cause: FCC lock)] ModemManager: 'Invalid transition'

#8 2022-03-09 08:14:24

Re: [SOLVED (Cause: FCC lock)] ModemManager: 'Invalid transition'

#9 2022-03-09 08:58:25

Re: [SOLVED (Cause: FCC lock)] ModemManager: 'Invalid transition'

#10 2022-03-09 10:47:28

Re: [SOLVED (Cause: FCC lock)] ModemManager: 'Invalid transition'

#11 2022-05-17 13:35:51

Re: [SOLVED (Cause: FCC lock)] ModemManager: 'Invalid transition'

Board footer