modules_force_load can be loaded earlier #103
Comments
... before switching to userland Resolves #103
Could you please share more information about the issue you see? Is the problem due to booster gets into userspace before all the Currently booster loads
The "before anything else is done" condition is quite vague and restrictive. One of the booster goals is to get into userspace as fast as possible. And to achieve it booster tries to exploit parallelism as much as possible. If loading modules needs to be done synchronously at the beginning of the booster execution then it limits parallelism a lot. So instead of "before anything else is done" I suggest to start with "before root filesystem is mounted" condition and see if it works. Please check |
|
I was lying, I thought I regenerated the image but I actually didn't. So I didn't enable Now actually trying to boot with What I originally meant to say is that this line can be moved further up in Line 662 in e825838 Making a few directory probably takes no time and it can run first, but we probably should be loading the modules before setting up the console font. Not sure if this actually makes a difference as I thought though, since I mistakenly assumed when I opened this issue that I will (dirtily) fix the symlinks, try again booting, then report back. |
there are few things that should be done before we load the modules. e.g. starting udev listener should start before we modules loading to avoid missing udev events. Moving virtual console config after loading modules sounds fine to me. |
... before switching to userland Issue #103
This gives more time for loading modules and makes the boot faster. Issue #103
|
With I originally thought that |
... before switching to userland Issue #103
This gives more time for loading modules and makes the boot faster. Issue #103
... before switching to userland Issue #103
This gives more time for loading modules and makes the boot faster. Issue #103
|
Closed by 9047c94 |
I'm using modules_force_load for KMS, and booster gives a little dissatisfying result because by the time the mode switch completes my display manager would already have started.
mkinitcpio loads its
MODULES"before anything else is done". I think we can do the same, since module loading is performed with a syscall and does not rely on any CLI utilities.The text was updated successfully, but these errors were encountered: