more verbose output for NM

[Marco Moock]

Am Sun, 5 May 2024 16:56:45 +0200
schrieb Frédéric Martinsons <frederic.martinsons at gmail.com>:

> Morever if you are debugging wwan and if modem manager is in the
> loop, look at https://modemmanager.org/docs/modemmanager/debugging/

Thanks!
That is what I was looking for.

PS: The issue was that fcc unlock wasn't enabled by default.
https://modemmanager.org/docs/modemmanager/fcc-unlock/

Sadly, that information isn't being shown to the user nor logged by
default in journald.
I think such messages should belong to the error log instead of the
debug log.

<wrn> [1714923293.861865] [modem0] Failure
<inf> [1714923293.861900] [modem0] couldn't update power state: Invalid transition
<dbg> [1714923293.861923] [modem0] attempting FCC unlock...
<dbg> [1714923293.862201] [fcc unlock dispatcher] singleton created
<dbg> [1714923293.862455] [fcc unlock dispatcher] Cannot run fcc unlock operation from /etc/ModemManager/fcc-unlock.d/03f0:4e1d: file doesn't exist
<dbg> [1714923293.862559] [fcc unlock dispatcher] Cannot run fcc unlock operation from /usr/lib64/ModemManager/fcc-unlock.d/03f0:4e1d: file doesn't exist
<dbg> [1714923293.862686] [modem0] couldn't run FCC unlock: fcc unlock operation launch aborted: no valid program found