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 hibernation. Show all posts
Showing posts with label hibernation. Show all posts

Tuesday, June 17, 2025

*Monotonic* uptime in Linux hibernation increased by 1, into a 5 days now.

I think it was maybe due to FireDragon browser. No graphic card upgrade!!! Still older nvidia.

I don't know if crash (second time!!) has been from swap, or if it was from NVIDIA bugs. SysRq magic key combinations are slightly overmarketed! Reset combination was needed.

Wednesday, May 28, 2025

FireDragon far exceeds BOTH Waterfox and Firefox BY STABILITY÷÷&÷÷quickness („UNCRASHY” element in #Linux), and in the s2disk process better RAM impact.

Maybe not full „Lindows”... still (BUT – I found out now that Qt and Xlib mixing is NOT possible.)

Extracting AppImage was OK, no icu ver. lib errs, nor other libraries problems.

Fast browser FireDragon consolidated with #R language – maybe this has been revolutionary step. And WORKS under Xorg.

I still hate Wayland „smartphonization” of API (irony – when this API is REALLY shit). When you can't port it simply, code a 0.5-code... WHAT THIS USA IS, & WAS?? But browser is OK.

Sunday, March 23, 2025

Memory leak of 882-877 =5MB after hibernation?? Browser was in text-mode only. AND: they USA are so STUPID, **that** possibility under NOUVEAU the same error aroses!!!

They're so IMPOSSIBLY stupid, certainly... they do bad and good simultaneously, shits of hybrids... [ARURT-US!!!]

 •Test circumstances - [EDIT] I omitted copying certain param into „shadow” module subsystem... &... THE PROPER ONE.

„Clear” initcpio: no nvidia, no nouveau & /etc/modprobe.d/nvidia.conf filled-in.
And  NVreg_PreserveVideoMemoryAllocations=1 as copy from boot cmdline:
 

/etc/modprobe.d/nvidia.conf        :

...

 6 options nvidia  NVreg_PreserveVideoMemoryAllocations=1
 7 options nvidia_drm  NVreg_PreserveVideoMemoryAllocations=1
 8 options nvidia_modeset   NVreg_PreserveVideoMemoryAllocations=1
 9 options nvidia_uvm  NVreg_PreserveVideoMemoryAllocations=1
10 

.... 

# Defined in /root/.config/fish/functions/BASH.fish @ line 50
function hibertest
   s2disk -P "shutdown method"="reboot"
end

Standard GLX info program [EDIT — that is, before the 1-param duplication from cmdline...]:

 root@Knoppix /# glxinfo |grep -i "mem"

Gives
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 886 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 882 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 882 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 882 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 882 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 882 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 882 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# hibertest
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 877 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 877 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 877 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 877 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /# glxinfo |grep -i "mem"
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
    GLX_NV_robustness_video_memory_purge, GLX_NV_swap_group,
    GLX_NV_multisample_coverage, GLX_NV_robustness_video_memory_purge,
Memory info (GL_NVX_gpu_memory_info):
    Dedicated video memory: 1024 MB
    Total available memory: 1024 MB
    Currently available dedicated video memory: 877 MB
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
    GL_NVX_gpu_memory_info, GL_NV_ES1_1_compatibility,
    GL_NV_gpu_program5, GL_NV_gpu_program5_mem_extended,
    GL_NV_robustness_video_memory_purge, GL_NV_shader_atomic_counters,
    GL_NV_transform_feedback2, GL_NV_uniform_buffer_unified_memory,
    GL_NV_vertex_attrib_integer_64bit, GL_NV_vertex_buffer_unified_memory,
root@Knoppix /#

Thursday, March 13, 2025

Again s2disk failures, BUT:: 1×Hibernated under NV proprietary & restored under NOUVEAU initcpio. 1×HIBERNATION OK

Preface

Indeed, its maybe not full J. S. Mill's methodology here.

•„halfy-simply” OK..............

•Half-success, rather, is NOT success.

„Darwin's award” for whole America: Real causes are undefined still.

 Maybe kernel Crng / random number seed/?? 
•After combination in title, Brave „halfy-simply” OK – that means, full test is needed.
•Testing as usual, with heavy measures. YouTube JavaScript is always heavy, even to the „subconscious” users accepting in-marketing lags (that immoral you see literally everywhere, as NLP is definitely worst US colonialization of world — because (also), mutually interlinked with overally business corruption (beginning with Window$, they arurt-us continued abusive money [&immaterial values esp.] abominations in Linux.
And it is completely irrelevant if you name similar as crypto, or... not. 
Even YouTube is some crypto, in reality. Nontransparent practice of most Linux „enthusiasts” consist of buggy, non-working (the hibernation is only 1 example – some time, menu-cache...) stuff.

Thus, NLP and CBDC is a polymorphism... overworked USA thinks that a solution to bug is a patch, no... . THEY LIE YOU ALL THE TIME, DEVALUATING YOUR OWN TIME, OR EVEN –MONEY.

Solution would be only reworking of operating system – YOU SHIT CHANGING (REVERSING/INVERTING) YOUR F...ING MORALITY, A BIT OF CRAP, ALONG.

Wednesday, February 19, 2025

After combining boot „cmdline” with NVreg_PreserveVideoMemoryAllocations=1 , 2× HIBERNATION OK

Preface:
» Even Brave full-crash DID NOT indicated graphic card crash!!!

I restarted Brave successfully (a contrario previous times, when FULL [not-soft] reboot was needed).
In summary, two resumed hibernations, along one brave crash & Brave restart!

Final /proc/cmdline addition list of parameters:

• nvidia_drm.modeset=1

• nvidia_drm.fbdev=1 

•NVreg_PreserveVideoMemoryAllocations=1

This is a complete misunderstanding that you can't join such info into quick handbook, USA!!! Only this „joy”, „gaming”!!!!

You don't need to study forums!!!! How simple is this.... – a some rule, that proper guide-book is far more important than forums, with all selective quietness (!!!), & other NLP sh*ts.

Not website but „Compiled HTML Help” 'd be OK... YOU CAN'T... even make manpages .... that 'd be simply-usable...

I think also your U. S. „L/R problems” are also from your f***ng, sinful-THUS-stupid, antimorality... . The one nation, that is in „big bit” comparable to Russia...

I hear NLP when listening to U. S. music (there are some honorable exceptions).

Saturday, September 7, 2024

Bad bug of hibernation causes 3 HDD spindowns in a full s2disk cycle -SUDDENLY I found THIS[after I reduced it to 2]

Possible solution for hibernation problem

But why it is not in /proc/... filesystem already??

Documentation abilities of Linuxed USA is still very poor – it frustrates so much. I remember Microsoft MSDN, it was written in good manner, easy to read, find, etc. . But in Linux, some Qt help program does is – but seems to be still in early stage. The sh**it of problem is having to remember next, next – why Windows had XP with good hibernation feature and Linux to this days, on the same BIOS (!!!) spins down HDD three times?

Maybe not BIOS is bad, but OS(es) itself.

Windows XP hiber-OK => Windows 7 regression (with the same BIOS, understand!!!). And now some strange module lines to #define some boolean value?? Hopefully, someone can think libata has 150k of lines — rather NOT.

Compilation furtherly – not believing programming groups – why?

Because („caused [to]”...) they, in my theory at least, have fun of old „technique” of making partial product (0.5-working, in other word aka „halfy”) — in disorder to make fun of repairing, repairing... . The worst feature of America, since „multipersons” don't trusting „original” G-d – they manipulate also Bible, even named it after Babel. If they can't read Hebrew „code”, they MUST have weak programming abilities – it is a general correlation of reality. In exegesis, a good code is helpful also. Letter by letter /literally/ in so-called „prehistoric” (!!!) languages „sin” can mean „China”. Atheists have NO good software philosophy, rather an POV of stupidity. If C++ programmer is „baptist”, then (IMO) he doesn't code in bug-resistant manner. 

You have poor religion, you are poor „informatician”. 

Those groups simply can't. Why they not opening BIOS/UEFI source code – an one example of thesis' evidence. 

...ATA flags?? You made source code (almost?) unreadable by „horkages”, „DMAs” and _do_ 's!!

Why not one „uncloned” procedure, but this nested ...do.... PM's function names and stuff?? Effect of years of laziness, addiction to music (why monopoly of Apple, can't do fusion with portable hardware producers?? You like your shit Babel crap, when stupid immoral can make money almost from nothing (aka fiduciary value in „eco”nomy). Some of this „rule” we see in „real life” of game industry (the most), and fears of incompatibility of Rockbox MP3 player „BIOS”.

Friday, September 6, 2024

Kernel recompilation BAD caveat (next!): .config's NOUVEAU is *NOT* marked (y/m) automatically/remains only commended out!!...

  • —Despite make defconfig/localmodconfig/THE ETC.!!
  • Similar problem is when installing Debian (EVEN both user/kernel-land packages ) inside chrooted container (or usual system as „well”, USTUPID): it is sado-masonism of USA — „deb configuring” have auto-remove even needed packages — we are not robots to discern it as bug!! Deb „configure” IMO does is equivocative — see Arch Linux pacman philosophy (!!!),
  • Hibernation patch is in 1/3 OK – is means, HDD spindown turned from amount of 3 (three), to the smaller 2 (two) value.
  • Yea, even if restoration failed to reach its end (drivers re-initialization, maybe from lacking of nouveau module - as above) – some crash – see what USA „colonization”, „mega”, „giga”, „super”, „explore”, „discover”, „fun//ky” (etc.) is not that morality that you should have ***to be really happy**** (NOT the «APE»).

Monday, September 2, 2024

LINUX HIBERNATION PATCH: CAUSED HDD SPIN DOWNS 3-TIMES (!!!) — REDUCED TO 2 now — working part of the bug FIX: I managed to ELIMINATE the one case, about the SNAPSHOT image saving image – HDD SPINDOWN REDUNDANCE!! STUPID PROGRAMMERS

So far general stub with conditional if, (nouveau KMS waits...)

In any standard Linux distribution, when you hibernate system to HDD – the disk is powered down 3 TIMES, NOT due to stupidity of Linux programmers

The bug is when uswsusp but reaches swsusp in kernel.

The bug means i short terms that HDD is powered down (spinned down that you can hear it clearly!!) unnecessary times (as in Windows 7, XP & even W2000 had hibernation functionality normal). They made code reusing in the improper manner.

HDD SPINDOWN REDUNDANCE!! STUPID PROGRAMMERS (& users).

„I can't believe” — — that you all not observed it — WHAT is your intuition??? And, where!!! You maybe wait for Fedora, Cent OS... wait, wait... waiting and lazy.... . HOW!!! Really you are unmoral SHIT that group of idiots made idiotal continuum (even if they name themselves Linux system programmers). „We” are not automatons – THINK! 

Monday, August 19, 2024

NVIDIA/Xorg screen (RE)DRAW BUG as a next case from multievidence of (un)corporate RATS: both business and open source „mans”!!

When using Linux ope*RAT*ing system, remember about it overwhelming downsides!

But the worst is HIBERNATION. And shut up stupids forum maniacs!

People don't write about topic THAT GOING INTO s2disk AND (!!!) RETURNING, THE HDD DRIVE SPINS DOWN [the HDD LIFETIME] in summary THREE TIMES, NOT THE ONE AMOUNT NEEDED — a. before saving image b. when power downs (and, again, NOT ACPI!!!!!) c. while resuming!!!! WHAT YOU NOT UNDERSTAND??

— How this is even possible, crappy people!! Errors, bugs at fundamental kernel-mode levels!!!

They have hope that new approach into NVIDIA drivers will make the Xorg/Wayland experience normalized?

When errors last from nouveau times/usage??!! Discovered at KNOPPIX distribution. The screen not whole crashing, but modern Blender repaints often in black. I remember also the mouse problem to this day. *Your* stupidity, you cannot even maintain Linice debugger – I saw 32-bit version (DWORD—compilation problem) now, 2024.
•Even more! Can't check one Rebecca Black OS Wayland operating (- checked by pgrep to surety! -), because screen completely damages (source of naming convention...!!) at startup!

If *you* would stop bad NLP, then you'd have more mind abilities.

Linux is not such revolution. It lacks in graphics, and power management. Simple sleep operation (to RAM) sometimes crashes whole system. Some fear can arise when VT-switch, still. Some people like standard Linux VT, and you crap do regress Blender (both in BI and memory consumption/loading times by main program file size), VTs (some a'la VT remake layers when you cannot even in.... QUICK simple words explain usage of fbsplash), IF YOU CANNOT MAKE SOMETHING REPAIRED THEN YOU CREATE REGRESSION MAYBE DELIBERATELY!?? Does KWin/Wayfire support ALL compiz options (as ccsm) or NOT?!!

*You* must stand in truth!! Fake mans == apes!

You programmers/testers/bug reporters & forums „staff” are •lazy, •news-oriented, •stupid/ADHD•unlogical – WHY s2disk informs me about page poisoning, when I am sure that my RAM are OK!!! && And why you cannot make comprehenvive manpage about differentating basic concepts: KMS, framebuffer, ...x...dga, DRM!!!

Basic programming layer is making key concepts simple & logical – not jumping with manpage, info, wiki, forum.

Linux OS lacks documentation ability – its structure is very confusing (in comparison with M$' MSDN Library / aka MSDN Collection). Kernel code comments are non-encyclopedical, non-scientific (w/o making big difference in sys-freeze, disk-freeze, suspend and hibernation). Yea, particular KDE program makes help pages user experience a bit better. But it is NOT what we need. But again, very strange that variety of naming conventions and DE amount harden the ability to quickness – productiveness. As Babel thing, once again.

Friday, August 16, 2024

'nolpm' parameter at Linux kernel command line NOT suppressed REDUNDANT HDD spin down — shortening hard disk lifetime. SHIT OPEN SOURCE NEO-PROPRIETARY LIARS

Understand what written?
You crap think that SSD disks are better?? WHY STUPID!!?
Marketing worms!! FALSE opensource co-workers, compared to Windows!! MONOPOLY of laziness.
They go into opensource to help others- or- to accumulate experience to return into buggy proprietary??? WHAT experience?? In managing of new HYBRID mainboard  „cards”: crap-shit hybrid modules?? BE CURSED!!! 


Thursday, August 15, 2024

A HIDDEN **bug in Linux kernel**/driver SHORTENS your internal HDD lifetime, most stupid POPCORNED people — by unnecessary spindown the drive before hibernation.

Tested 6.5.13-7-MANJARO s2disk && the system freeze function alone.

Both generates UNNECESSARY HDD SPINDOWN. I know this sound very well, SMART is „OK”, this are ONLY by hibernation (some signs that ALSO AT... RESUME!!!!)
On earlier versions I don't had occasion to even try to hear it – because of noise isolation I use.

Of course, method was 'shutdown'. Why to bother also with ACPI??

More at previous blog entry. Doubting it has been repaired – to my intuition, they definitely can't. The kernel „new” „better” „features” are so boring... they can't even cooperate with Intel Software — (that is, SSEx) the Emulator – NOT WORKING despite some longer command-line parameters config, mere crap, exception privileged instruction....

Maybe you're so happy apes due to... factual corporate-heart (still)?

–Despite freeware origin destinations that are freedom, portability, robustness, easy deployment (as in Porteus distribution) .... 

The bug is in freeze functionality, that is part of s2disk/swsusp layer also

echo freeze > /sys/power/state   reproduce it.

–residing probably in HDD driver kernel module.

—I assume that all versions „higher” are affected.
—Some Vista-or-later had this error also. I remember this detail perfectly.

More about issue at previous blog entry.

Wednesday, August 14, 2024

Messed up, *regression* Linux kernel: the sys-freeze command-line SPINS DOWN *also* the internal HDD!!!!! Cause »YOU« are genuinely STUPID – can’t COOPERATE as in free, as in corpocrate-ware (often).

What I mean about that?

echo freeze > /sys/power/state

And this f***ing, STUPID internet forums: blah blah try this, and go THIS and THIS. Try compatible OpenSUSE, try easy Ubuntu, ... try customizable Arch LinuxWhy need to comment even a comment (even nested forum comments(?!!) ).


—Genuinely STUPID USA!!!


Why you have such multi entries in forums topic categories (or „tags”?? Who has knowledge how REALLY you are empty-minded?)

Linux has been made (-not- created!! We, you are NOT Creators!!!) with „freedom” and also other „usability”, „openness”, „zero-paid”, etc..

But… you think one, but do the …. second „one”. Simply, MUCH hypocrisy.

You start, and can’t end (that is, made sth simple & natural, really FREE from errors)

Working with software with China hardware was especially the most bad idea. Embargo is OK idea – but but only when ON, not in OFF mixed-mode state.


 Similarly as this disk turning into hibernation.


If you can’t operate computers properly.. ONLY THIS STUPID Raspberry Pi

We are NOT computers. Assembler shows CLEARLY, yea, CLEARLY that some theorems can be TRUE, but nonevidenceable in formal logic system.

One of these are, the increasing necessity to unanimalize the society. Maybe some new key-point for slowing down IT industry??

European soul can’t understand America clearly! Its impossible.


Bad inventions, wars — arose from USA. **Cursed** location of immorality, let take the affairs of prolonged colonies across the world. Zero, not a hero. And a question slightly harder: why two „l” letters, not one??

Then, the conspiracy theories tend to be important. Even free, open computer software are in link with corporate, evil-oriented rat race.

Problem has been indicated initially even at Poland slavery’ country, by one Ryszard Sobkowski headline.

Multitudes talking: Bible, Jesus, worship. But not in computer science?? WHY? Moral dwarves.
So tiny amount of bug-free areas. Bugs, bugs everywhere… shit society elements. Even your language has bugs. Can’t stand English minus signs across the text. ENG has too much irony, its Babelic, *not* „angel-England”.

Monday, February 13, 2023

Both Cycles & Eevee: WORSER volumetrics VS Classic Blender Internal (→2....

Naivety that „future” / „„nonlegacy”” (what irony…) releases of Blender(/Bforartists) would be OK in cloud volumetric rendering must be cancelled... . Bfor have nice icons, but whole rendering are so nervous. Some ADHD of Americans. They think you should wait, wait, wait... . Ver, ver+, version»#.###... . Firstly repair what you have made buggy. Then, you will have proper field to add new functionality. Step after step. All with Spirituality. ...... There is some rationale of distance of „made” and „mad”. Two „bla bla best... fast... good for animations...” (do YOU mean that ugly, unmoral , pokemonny unpeaced anime? Or beautiful, natural, solid ... — they EVEN can't normalize Lux...!) are BAD in order to take Blender 3D graphics seriously. THEY REMOVED IT, the FK, even made black, sometimes I think ugly Blender GUI motive) according to functions of the packet?? Subliminal programming?). LUX IS COMPATIBLE WITH ZRAM & 3GB RAM, **DESPITE*** ITS EVEN INSTABILITY (?mainly PY-GIL?) . WHY YOU DON"T CONSOLIDATE CYCLES/EEVEE WITH LUXCORE? America seems to be ”good, yea” but the truth still remains that it is only empty, waste narcissism. Citizens are bad, then why require more morality from .... politicians? Bad corporations? Citizens are NOT ok. Instead of drawing such pokemons, the pokemon-goY, better solution for US is changing FAITH. Do NOT trust FREEWARE, do NOT trust stefania church baptists. Trust HaShem of Jewish instead. Freedom from money/nonprofit corporations is possible only in the proper Orientality. 3D Renderings are very handy here. Orientals have very interesting lookings (POV) around Earth & Cosmic topics. •My experiences demands assuming that selectivity of software engineers is so big, that they even don't account hibernation feature – that is, by measuring renderers (as even in Lux!!) times. Soft is hole – ful, buggy, semi-featured (halfy) as in closed, as in free soft. •Some persons would silently require that customer would replace graphics cards so often... for what? Even driver replacing (and checking if DKMS if for concrete kernel) is time-consuming. If U need pokemons, tell politics.... . Enjoy, US, small things... . Ha ha... #blender #bforartists #rendering #test #ranking #zram #linux #clouds #volumetric #OpenVDB #Cycles #Internal #Eevee #hibernation #crash #XServer #Xorg #OOM #bug #software #methodology #experiences #opensource #testing #packet #pros #cons #wtf #plugins #generator #noise #deformations #delicate #classic #apel #raytracing #evening #cloudscape #distorted #unaccurate #details #panel #settings #underlight #highlight #whatisbest #old #legacy #s2disk #modelling #3dblender #issue #actualization #pixels #mosaic #sunlight #sunbeams