On 2021-03-12 at 21:05, David wrote: > So I guess the answer is either in the kernel, or systemd, > but I don't know, and I found no further clues about that in > either the Arch Linux wiki [1] or the Debian Reference [2] > or the Debian wiki [3]. > > So I will stay silent now and wait for someone who knows more > to answer :) > > [1] https://wiki.archlinux.org/index.php/Network_manager > [2] https://www.debian.org/doc/manuals/debian-reference/ch05.en.html > [3] https://wiki.debian.org/NetworkConfiguration
I wouldn't say that I particularly know more; in fact I may know less. However, if I were encountering such symptoms and had (as has apparently happened here) searched the system for mention of the key term 'wwan' without finding it, the next places I'd look for clues would be A: dmesg and B: the contents of /var/log/. (If running systemd, I'd probably also want to investigate the contents of the journal, but I don't know proper syntax for that beyond the name 'journalctl'.) It might be necessary to make sure you're booting with appropriate message verbosity; IIRC, systemd may default to a quieter boot than sysvinit does, so you may have to adjust some grub parameters and reboot. In principle, however, I'd expect that if such devices are being set up at boot time there'd have to be some details about that logged during the boot process, and such logging would have to go to one or more of those three places. -- The Wanderer The reasonable man adapts himself to the world; the unreasonable one persists in trying to adapt the world to himself. Therefore all progress depends on the unreasonable man. -- George Bernard Shaw
signature.asc
Description: OpenPGP digital signature
