[systemd-devel] Fail to load network modules properly

[Łukasz Słaboń]

Well after analysing dmesg I see that only difference between successful
and failed boot is the time when ext4 main partition is mounted for the
second time. In failed boot it is mounted between cfg80211 module and wl
module. Detailed dmesg listing is in my first message.
That is why I asked is there any possibility to force loading cfg80211
module only after main partition is mounted for the second time. I assume
that is should be done somehow by systemd. But I'm not experienced enough
to solve this by myself.

Łukasz Słaboń


On Tue, Jan 29, 2019 at 4:50 PM Colin Guthrie <gmane at colin.guthr.ie> wrote:

> Łukasz Słaboń wrote on 28/01/2019 19:23:
> > Yes, as far as I know it should load firmware. Is there a possibility to
> > force loading wl driver and module only after partition is mounted? I
> > assume that something systemd scripts needs to be changed to force
> > different boot sequence.
>
> Firmware is usually stored in the /usr tree. systemd typically requires
> that /usr is available from early boot (i.e. before modules are
> initialised).
>
> If /usr is a separate partition, it is the job of the initrd to ensure
> /usr is mounted prior to pivoting into systemd on the filesystem.
>
> If the module is compiled into the kernel or included in the initrd,
> then the firmware file would also typically have to be included in the
> initrd too.
>
> dracut takes care of all this for you, not sure about other initrd
> generators.
>
> Col
>
> --
>
> Colin Guthrie
> gmane(at)colin.guthr.ie
> http://colin.guthr.ie/
>
> Day Job:
>   Tribalogic Limited http://www.tribalogic.net/
> Open Source:
>   Mageia Contributor http://www.mageia.org/
>   PulseAudio Hacker http://www.pulseaudio.org/
>   Trac Hacker http://trac.edgewall.org/
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20190130/f73937e2/attachment-0001.html>