ModemManager | Modem Manager mirror

I found it out myself (interesting how asking questions helps you thinking...):

The issue was in the systemd recipe itself and related to the systemd-compat-units recipe. I was able to fix it with this in my layer's recipes-core/systemd/systemd_%.bbappend:

I suspect that is debug output and doesn't mean the recipe is excluded. Have you looked at the modemmanager recipe to see if it has a DEPENDS on gobject-introspection-native and perhaps gobject-introspection? If not, or the PACKAGECONFIG isn't set, try adding the DEPENDS or enabling the PACKGECONFIG?

Also, have you tried simply building "bitbake object-introspection-native" and "bitbake object-introspection". You should get an error about why they ar disabled if you try and build them directly and they are excluded/disabled for some reason.

I found the problem myself. In my Docker compose file, I specified an order of containers via "depends_on". This order prevented my memory from filling up at once. However, after a reboot/crash the "restart:always" function kicked in and started all 11 containers at once.

Note: As docker-compose I also used a docker container (aarch64 - problems) which could possibly lead to this problem.

use ls -ld /usr/share to see what the permissions on the directory are (without -d, you get the contents and their permissions).

Use code like:

You should be able to utilize ModemManager to get the GPS location instead of getting it directly. This way you can avoid using the same serial port from two services.

There is documentation on how to do this from the command line using the mmcli tool in the ModemManager manpage: https://www.freedesktop.org/software/ModemManager/man/1.0.0/mmcli.8.html#lbBC

There is also a libmm-glib library which you should be able to use from Python via GObject Introspection without running the command line tool.

If you only need to suppress "Permission denied" messages. You can redirect errors to /dev/null:

It may be that the SIM is not working properly or the modem is not recognizing it.

This is what the output

kthreadd is not a process started by systemd. Kthreadd is a worker thread daemon (kernel thread in itself) started by the kernel.

pstree is more to do with the user space processes that shows the parent and child hierarchy.

In my opinion you should not include kthreadd in your implementation. One of the way to find the kernel threads is /proc/$pid/cmdline is empty for kernel threads.