„Unlocking” (the) SysRQ REISUB hotkey is overmarketed!! & NVIDIA freezes EVEN when doing NOTHING in the foreground • and it freezes VERY suddenly. (PLUS: about #KWin)

NVIDIA freezes even when taking a some pause... . Linux is such system that is underworked, of course Xorg-bypass vt force-switch was used... •SysRQ's overmarketed!

I know Scroll Lock can be „another” SysRq on „different” keyboards. But the Linux can be different from usability and productivity.

 

•I know it is free/open-ware (mainly) market.

You have Linuxes in corpo-compatible style (CentOS), „one” workstation (Fedora), full-corpo (old Red Hat...), and...?

And what? Still old problems of synchronization, thread locks... But it does is certain way to prove computers are not gods, as some seem to „deep-in” virtual so-called reality, BIG shit of AI processing, robotics areas – NEXT big-shit NLP op.

Yea, computers are as great book library. But Linux users sometimes not growing old stuff... .

They also make new-and-worser instead of fixing errors in the old. Almost as Windows...

Kwin definitely WORSER than compiz & emerald pair. Programmers lazy-working. One from pros maybe is it can detect wrong NVIDIA functioning.

 

(but... monotonic uptime of 3:14:58.300968 is better than system „crashy” suspend after start). 

 

And a fisheye lens effect – the same as astronauts have. All America is a bluff, simply – LIE and waste.

Linux centered at effects – why this metacity-or-clone, when I need long distance from screen to eyes?! To save the oculistic health.

And, BTW, what a nonsense naming the monitor as the panel – yes, control panel for controlling morons.

Kwin supports this idea – theme editing IMO as Wayland screen parameters nano-editing. Yes, the „nano-”, in user experience scale.

Again, if SysRq not-so-hacky, (even certain kernel-mode debugger not ported to x86/new kernels!!!), then why to LIE to PEOPLE, and build false sense of popularity/specific IT glared glory?!

Linuxes arose and decline, still failed at basis – NVIDIA.

Not DRI, DRM or DDX. The base core of everything – the code runtime quality.

Unless, someone uses CLI mode only. But they broke even Blender, some version (+!!!) not working under mere nouveau.

 

Two-computer debugging... we can NOT even set the chvt command. And the MALFORMED Oracle VM/Virtual Box. NONVIRTUAL BUGS.

Dysthopian Linux as banking dysthopia. Lacking at its.. even KERNEL basis!

„Ecosystems”, when the nature not having such bugs! In such extents!

I assumed – Mac also not perfect... perhaps all we have to install manually, with plenty of non-standarized package manages (main system lacking EVEN package manager?!!). Problems with installation, less problems perhaps when daily utilization. If the Mac supports hibernation... I doubt.

The BUG and its subBUG, a NVIDIA „combo” test: „standard” Linux OS hardlock now occured (but overally- softer), I am NOT blaming NV yet.

•1. __GL_SYNC_TO_VBLANK=0
•2. __GL_YIELD=USLEEP 

After longer time after bootup from hibernation – the overally softer variant.

Several days PC remained very stable – as usual, in previous experiences. Methodology is (I have not wrote it yet on blog...) that I concentrate mainly on recovering from „hour-to-hour” system/Xorg instability that started in some meantime. 

Compiz ALT+TAB static switcher plugin quick-switch test shows still black background (instead of lock).

That is, when several reboots tend not to helping. Instead, when several (partly, long!) days of hibernated system lasts OK – test is in its main part, fullfilled.

Years ago, I thought it was rtkit of web browser(s) messing with Xorg/simply, the Linux I use.

The non-specific bug – IMO – all Linuxes are similar..

But rtkit was challenging. FireDragon not have such process and functions OK (except per several working days time-span).

NVIDIA big bug has its „smaller” and „bigger” part sub-bug(s).

And why rtkit?? I think usage of rtkit is a history. I had to end rtkit process, chmod/delete it, or change priority manually all the time... .

But the above not with NVIDIA bugs... . They remain, and forums indicate that on AMDGPU/Radeon situation not better.

 

Thus replacing (upgrading) graphic card – rather nonsense here.

And life is NOT «as a» computer. Remember also about Kurt Goedel's theorem, blog Reader.

 and...

This is a supplementary blog... rather than main WP-blog one. 

Learn 3 Linux areas, requiring increased AWARENESS, or even instant REACTION after UNIX-like OS installation.

I NOT tested big variety of Linux distros of course – but we can assume that there is some VERY bad habit across „some” distro lines, as in Arch (-Bang, Manjaro...)

1. NVIDIA proprietary threading – [Xid] bugs here: , seems similar to hibernation/s2disk problems

–a tricky issue, I  hope the env. combo helps: even when proper environment applied, FPS can be 1 (Xorg/glxgears) – see blog entry about „NVIDIA combo” [in testing]

2. CD/DVD/BD writer driver – also, here (Arch Linux with standard kernel, before KNOPPIX'ed) – its fault of Arch developers, even not to mention necessarity of placing some disk vendor id into some kernel internal hibernation special-treating PM list

KNOPPIX is so mature distro – replacing Linux kernel (contains basic [non-NVIDIA...] drivers automatically] across the distributions repairs even >1 problem. I not had to edit kernel source code in such manner!!!

 

They broke it overwhelmingly.

3. Hibernation/s2disk HDD spindown BEFORE even PC actually shutdowns – what a shame!! My blog covers it in basic details. Again, simplest way is replace it to the KNOPPIX kernel.

Do not forget about modules (drivers!) & recreating initrd. Maybe, also, some „extra” modules (in other directory... but all stuff under /lib/modules).

Along KNOPPIX-ation of the Arch, or other faulty Linux system, I recommend Fedora inside chroot/systemd's nspawn command, or similar. 

This one is user-mode solution – and the previous 3 was kernel-mode ones.

Fedora can be better than Debian, if you need GUI applications stability, and, as I assumed – the stability of package manager process.

 

No removing autoinstalled unneeded, blah blah... QGiS and Libre Office runs OK (remember, these are older versions – but usable, esp. when there remains LIBRE OFFICE bug with picture transparency/some image-op widgets BUG). 

All similar bugs shows you Babel/ity of social fragmentation – more precisely, the fall of America.

W/o PROPER religion you have no peace needed to fix the computer problems. To try, to wait, even to sit down with the machine. 

All my Linux tests show you an important rule of UNIX-like operating system: if NOT regulated, some BUGGY processes 'd be RANDOM, or 1/0 yes/no–autoCONVERTING.

Preface:

(I do NOT know precisely how with hibernation in another UNIX-like, Mac for example, etc.). I concentrate on „mere” (but good if you'll be hard-working) Linuxes: Arch Linux usermode running on KNOPPIX kernel.

I do not like term userland if its too exclusive: Windows term is USERMODE – simplifies things with an uniform nomenclature.

Hibernation is one of 3 areas, where Linux needs instant ADDITIONAL out-of-the-box operation to apply manually.

•Hibernation, in its GUI/graphical/DRM/DDX/framebuffer stuff depends on NVIDIA. But in my (current) experiences so far, it does NOT seem to be problem with hibernation „as it is”. Dmesg log „Xid” errors can arose even if no hibernating Linux! But they simply seem —

—only: seem, to be straight hibernation issues.

     If we cease using Windows, then GLX (that is, proprietary one Open GL library from NVIDIA installer) MULTITHREADING bugs we could treat, improperly – as the source of screen tearing, console switch system crash (but this bug was actually GONE! Even on proprietary!) bugs. 

Its multithreading, NOT the hibernation. NVIDIA env combo applied – still in testing phase.

I even do not know, if DDX (that is, some Xorg driver) also has similar problems

 – environment variables combo has been applied also to running Xorg instance.

 

1. Do not rely on /etc/profile – I remember my old negative experiences.

2. Systemd may have its own env managing – thus copy everything into several bootup script execution places, even into .xbindkeysrc, for making surety.

 

It is overall complicated slightly, requiring maybe making startcompiz script along some startlxqt variant – but:

If we have some help from NVIDIA, then why not to experiment with the Linux starting environment? 

As stated in the title, randomness of some Linux OS behaviors imply we must have proper, long-lasting timespan for proper methodology of tests (now monotonic system uptime: 2 days, 0:49:35.459530)

 

Maybe as in Blu-Ray writer test: when it turned out the need to copy KERNEL from KNOPPIX, and it works OK months – as in GLX test: firstly, strong need to wait, simply, wait and be much patient here.

Linux requires patience, and a good PAPER book.

I hate smartphones. Not important if from China or not. 

Smartphone (and electricity!!) SLAVERY