NC - SC

NC - SC

◇◇◇◇◇ REMARK – THIS IS NOT MY MAIN BLOG ◇◇◇◇◇◇

The Better Blog Version is ON WORDPRESS *****To jest blog pomocniczy. Podstawowy jest tu (link trzeba przekopiować): **** https://tradycyjnyyahwista.wordpress.com/ STRUKTURA STRONY:•Wordpress blog zasadniczy, NOWOŚĆ: INDEKS A...Z. Bogate menu, galerie, *AKTUALIZACJE*, ŹRÓDŁA! •Blogger to blog pomocniczy – notatki, też komentarz itp. •YT – playlisty (aż z kilkanaście, PL i ENG.), WYCINKI - FRAGMENTY •Rumble – filmiki, filmy i WYCINKI, Dżek •JustPaste – pozostałe materiały i notatki, koment.

Search This Blog

Showing posts with label initrd. Show all posts
Showing posts with label initrd. Show all posts

Wednesday, March 19, 2025

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!!!!!

Monday, September 2, 2024

Patched sr0 loading (Linux CD-ROM) @udev: 5 TIMES OK now WHEN in /usr/lib/initcpio/hooks/udev changed into systemd-udevd -c 1 to avoid parallelization.

4 warm reboots + 1 full turn off/on power cycle so far.

Seems NOT to be a problem with master/slave statuses in BIOS — bigger probability that udev sequence is a solution, more tests required. Some null BIOS entries also turned into manual none option – but correlation is with udev command (below). We have several udev command, but this is a initial one.

Part of new initcpio hook – remember to mkinitcpio -p ... to recreate CPIO

(...)
    quiet="$(getarg quiet)"
    if [ "${quiet}" = "y" ]; then
        /usr/lib/systemd/systemd-udevd -c 1 --daemon --resolve-names=never >/dev/null 2>&1
    else
        /usr/lib/systemd/systemd-udevd -c 1 --daemon --resolve-names=never
    fi
(...)

The cost is is booting is slower, black screen. Not the same as Porteus distro.

But better than to replace the udev, or bothering with SysV IMO nonsense.
When with systemd we have soft-reboot, containers (for example, an additional user-mode Debian in the form of a fs tree) and good status-info system with systemd' commands and wrappers (timertab program is one interesting wrapper example).

One most important thing is that udev has two „parts”: the main system's one -and- the initcpio one.

Thus, there is the necessity to update initcpio files.
Testing DVD mastering suite was k3b application – outputting diagnostic messages to terminal emulator (after usual-slower k3b init). If I remember, is is important – early mounting CD doesn't suffice when after „umount” situation can return the same. This is reason to check it with k3b, and additionally, this app has CD verify option within burning process (a contrario to xfburn).

Linux has several mainline BUGS. One with CD-ROM, second with REDUNDANT SPIN-DOWN during hibernation.

One can think that US programmers aren't lazy... NO, NO..... reality is that bunch, BUNCH of them are derailed persons. Why they concentrate on „new, new new”??!!!! Even kexec reboot is their amnesia.

Tuesday, August 27, 2024

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.