Now testing non-nvidia INITCPIO w/ 4 modules-load.d entries (see manpages, you VERY VERY stupid USA).

Minus early KMS [Kernel-Mode-Setting], plus modules-load contents shown -as some „third option” — Xorg can't load this modules precisely, thus we ought code-in into.

•Don't rely in Xorg Server kernel-mode///XF86///DRM (Direct Rendering Manager)///other, whatever named... driver autoloading!!!! You don't need all this ...ing chaos more. Only a framebuffer console, fb-d startup is normality. The high-resolution framebuffer console, at normal Linux bootup times!

[root@ 5.10.10-64  /]$ cat /etc/modules-load.d/nv.conf
nvidia 
nvidia-drm 
nvidia-modeset 
nvidia-uvm
[root@ 5.10.10-64  /]$

& intensive testing, as usual here.

Remember!!! Open Source NVIDIA remains nonsense still!!!! Don't be sado-masochistic!!! I think they deserve only lawsuit!!! AS BANK!!!!!

Testing /lib/modules-load.d/cdrecord.conf interference (of cdrecord package)

Still bugs – this ZEROS want to „create” new forums to boast it. They simply need new bugs in disorder to announce that they make „progress” and work. An paper SHIT of work... . This Linux sado-masochists, as other masses, stay at old BIOS traditions of bug, bugs, bugs. Crappy apes to boast with other liars, and shit cycle of „you can”. Idiots using new SSD, while Linux allways have big amount of small files. CAN YOU UNDERSTAND WHILE I NOT USE „CANDY” WORD „DIFFERENT” STUPID OVERSCIENTIFIC SHIT?

And why „sg” module in other place than udev? You put in in udev, crap... maybe and you stupid talking you made new distro? Aha – you already taked that systemd is „bad”... what in exchange, USA without future?

And you even cannot tell your people at start, that systemd-udevd DOES IS in the initcpio (I found it by using lsinitcpio command). If  y o u   can't explain work of basic system tool, why you open APE-epic mouth at forums (OFTEN W/O EVEN ONE REPLY YOU FALLIING AMERICA). USA is the place of corruption, lie, colonialism, void „oy” „oy” things.

Possible RACE CONDITION?? Could not initialize device "/dev/sr0". Already updated kernel, NO EFFECT – STRICTER: A HALFY (0.5) EFFECT.

HALFY (0.5) EFFECT. Race condition... – as in life...

Next example how STUPID are open source guys. Similar problems are with NVIDIA – everything seems to depend on random & initrd (MB size!??).

–or– maybe udev rules loading randomly in order?

Yes, systemd is so bad. I experienced it – cannot help in system-wide „threads” – a queue of driver modules. How to hard-core it in startup process??

HOW SHIT YOU ARE, USA.

Then, I cannot stand on POV that Linux is better that Windows. BOTH are faulty, source of bugs.

On Linux, you see plenty of it. One (more) example Xorg can't start sometimes, HALFY it can simply.

It's random. But in reality, a random means that if don't know the real cause – yews, simply. Nothing more. No bigger threading study here, then.

... and, you don't know precisely how to remove fsck runs. Trust a „new” boot parameter or not?

In IT, something new can't mean useful. I contains plenty of, even most stupid (3×HD spindown by s2disk, in summary) –things.