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.

How **SHIT** you are, USA!!!

(...)

   LD [M]  drivers/scsi/csiostor/csiostor.o

  CC [M]  drivers/scsi/smartpqi/smartpqi_init.o

PLEASE submit a bug report to https://github.com/llvm/llvm-project/issues/ and include the crash backtrace, preprocessed source, and associated run script.

Stack dump:

0. Program arguments: clang -Wp,-MMD,drivers/scsi/smartpqi/.smartpqi_init.o.d -nostdinc -I./arch/x86/include -I./arch/x86/include/generated -I./include -I./arch/x86/include/uapi -I./arch/x86/include/generated/uapi -I./include/uapi -I./include/generated/uapi -include ./include/linux/compiler-version.h -include ./include/linux/kconfig.h -include ./include/linux/compiler_types.h -D__KERNEL__ --target=x86_64-linux-gnu -fintegrated-as -Werror=unknown-warning-option -Werror=ignored-optimization-argument -Werror=option-ignored -Werror=unused-command-line-argument -fmacro-prefix-map=./= -std=gnu11 -fshort-wchar -funsigned-char -fno-common -fno-PIE -fno-strict-aliasing -mno-sse -mno-mmx -mno-sse2 -mno-3dnow -mno-avx -fcf-protection=branch -fno-jump-tables -m64 -falign-loops=1 -mno-80387 -mno-fp-ret-in-387 -mstack-alignment=8 -mskip-rax-setup -mtune=generic -mno-red-zone -mcmodel=kernel -Wno-sign-compare -fno-asynchronous-unwind-tables -mretpoline-external-thunk -mindirect-branch-cs-prefix -mfunction-return=thunk-extern -mharden-sls=all -fpatchable-function-entry=16,16 -fno-delete-null-pointer-checks -O2 -fstack-protector-strong -ftrivial-auto-var-init=zero -fno-stack-clash-protection -pg -mfentry -DCC_USING_NOP_MCOUNT -DCC_USING_FENTRY -falign-functions=16 -fstrict-flex-arrays=3 -fno-strict-overflow -fno-stack-check -Wall -Wundef -Werror=implicit-function-declaration -Werror=implicit-int -Werror=return-type -Werror=strict-prototypes -Wno-format-security -Wno-trigraphs -Wno-frame-address -Wno-address-of-packed-member -Wmissing-declarations -Wmissing-prototypes -Wframe-larger-than=2048 -Wno-gnu -Wvla -Wno-pointer-sign -Wcast-function-type -Wimplicit-fallthrough -Werror=date-time -Werror=incompatible-pointer-types -Wenum-conversion -Wextra -Wunused -Wno-unused-but-set-variable -Wno-unused-const-variable -Wno-format-overflow -Wno-format-overflow-non-kprintf -Wno-format-truncation-non-kprintf -Wno-override-init -Wno-pointer-to-enum-cast -Wno-tautological-constant-out-of-range-compare -Wno-unaligned-access -Wno-enum-compare-conditional -Wno-enum-enum-conversion -Wno-missing-field-initializers -Wno-type-limits -Wno-shift-negative-value -Wno-sign-compare -Wno-unused-parameter -g -gdwarf-5 -DMODULE -DKBUILD_BASENAME=\"smartpqi_init\" -DKBUILD_MODNAME=\"smartpqi\" -D__KBUILD_MODNAME=kmod_smartpqi -c -o drivers/scsi/smartpqi/smartpqi_init.o drivers/scsi/smartpqi/smartpqi_init.c

1. <eof> parser at end of file

2. Code generation

 #0 0x00007b958a9c4d90 llvm::sys::PrintStackTrace(llvm::raw_ostream&, int) (/usr/lib/libLLVM.so.18.1+0x7c4d90)

 #1 0x00007b958a9c226d llvm::sys::CleanupOnSignal(unsigned long) (/usr/lib/libLLVM.so.18.1+0x7c226d)

 #2 0x00007b958a8a88e9 (/usr/lib/libLLVM.so.18.1+0x6a88e9)

 #3 0x00007b9589c50ae0 (/usr/lib/libc.so.6+0x3cae0)

 #4 0x00007b958caa12f4 llvm::MCAssembler::registerSymbol(llvm::MCSymbol const&) (/usr/lib/libLLVM.so.18.1+0x28a12f4)

 #5 0x00007b958cae94f1 llvm::MCObjectStreamer::emitValueImpl(llvm::MCExpr const*, unsigned int, llvm::SMLoc) (/usr/lib/libLLVM.so.18.1+0x28e94f1)

 #6 0x00007b958b660640 llvm::AddressPool::emit(llvm::AsmPrinter&, llvm::MCSection*) (/usr/lib/libLLVM.so.18.1+0x1460640)

 #7 0x00007b958b6d7b8b llvm::DwarfDebug::endModule() (/usr/lib/libLLVM.so.18.1+0x14d7b8b)

 #8 0x00007b958b66fb1b llvm::AsmPrinter::doFinalization(llvm::Module&) (/usr/lib/libLLVM.so.18.1+0x146fb1b)

 #9 0x00007b958ab78e0d llvm::FPPassManager::doFinalization(llvm::Module&) (/usr/lib/libLLVM.so.18.1+0x978e0d)

#10 0x00007b958ab85149 llvm::legacy::PassManagerImpl::run(llvm::Module&) (/usr/lib/libLLVM.so.18.1+0x985149)

#11 0x00007b959392f21f clang::EmitBackendOutput(clang::DiagnosticsEngine&, clang::HeaderSearchOptions const&, clang::CodeGenOptions const&, clang::TargetOptions const&, clang::LangOptions const&, llvm::StringRef, llvm::Module*, clang::BackendAction, llvm::IntrusiveRefCntPtr<llvm::vfs::FileSystem>, std::unique_ptr<llvm::raw_pwrite_stream, std::default_delete<llvm::raw_pwrite_stream>>, clang::BackendConsumer*) (/usr/lib/libclang-cpp.so.18.1+0x152f21f)

#12 0x00007b9593cadd95 clang::BackendConsumer::HandleTranslationUnit(clang::ASTContext&) (/usr/lib/libclang-cpp.so.18.1+0x18add95)

#13 0x00007b9592989f23 clang::ParseAST(clang::Sema&, bool, bool) (/usr/lib/libclang-cpp.so.18.1+0x589f23)

#14 0x00007b959441a7c1 clang::FrontendAction::Execute() (/usr/lib/libclang-cpp.so.18.1+0x201a7c1)

#15 0x00007b95943bbad7 clang::CompilerInstance::ExecuteAction(clang::FrontendAction&) (/usr/lib/libclang-cpp.so.18.1+0x1fbbad7)

#16 0x00007b959446e11d clang::ExecuteCompilerInvocation(clang::CompilerInstance*) (/usr/lib/libclang-cpp.so.18.1+0x206e11d)

#17 0x00005bddd4459284 cc1_main(llvm::ArrayRef<char const*>, char const*, void*) (/usr/bin/clang-18+0x13284)

#18 0x00005bddd445d5ba (/usr/bin/clang-18+0x175ba)

#19 0x00007b95940f7175 (/usr/lib/libclang-cpp.so.18.1+0x1cf7175)

#20 0x00007b958a8a8d3a llvm::CrashRecoveryContext::RunSafely(llvm::function_ref<void ()>) (/usr/lib/libLLVM.so.18.1+0x6a8d3a)

#21 0x00007b95940f9aa6 (/usr/lib/libclang-cpp.so.18.1+0x1cf9aa6)

#22 0x00007b95940b5529 clang::driver::Compilation::ExecuteCommand(clang::driver::Command const&, clang::driver::Command const*&, bool) const (/usr/lib/libclang-cpp.so.18.1+0x1cb5529)

#23 0x00007b95940b591c clang::driver::Compilation::ExecuteJobs(clang::driver::JobList const&, llvm::SmallVectorImpl<std::pair<int, clang::driver::Command const*>>&, bool) const (/usr/lib/libclang-cpp.so.18.1+0x1cb591c)

#24 0x00007b95940d38c4 clang::driver::Driver::ExecuteCompilation(clang::driver::Compilation&, llvm::SmallVectorImpl<std::pair<int, clang::driver::Command const*>>&) (/usr/lib/libclang-cpp.so.18.1+0x1cd38c4)

#25 0x00005bddd445febd clang_main(int, char**, llvm::ToolContext const&) (/usr/bin/clang-18+0x19ebd)

#26 0x00005bddd4450fb5 main (/usr/bin/clang-18+0xafb5)

#27 0x00007b9589c39c88 (/usr/lib/libc.so.6+0x25c88)

#28 0x00007b9589c39d4c __libc_start_main (/usr/lib/libc.so.6+0x25d4c)

#29 0x00005bddd4451015 _start (/usr/bin/clang-18+0xb015)

clang: error: clang frontend command failed with exit code 139 (use -v to see invocation)

clang version 18.1.8

Target: x86_64-unknown-linux-gnu

Thread model: posix

InstalledDir: /usr/bin

clang: note: diagnostic msg: 

********************

PLEASE ATTACH THE FOLLOWING FILES TO THE BUG REPORT:

Preprocessed source(s) and associated run script(s) are located at:

clang: note: diagnostic msg: /tmp/smartpqi_init-60f254.c

clang: note: diagnostic msg: /tmp/smartpqi_init-60f254.sh

clang: note: diagnostic msg: 

********************

make[5]: *** [scripts/Makefile.build:244: drivers/scsi/smartpqi/smartpqi_init.o] Error 1

make[4]: *** [scripts/Makefile.build:485: drivers/scsi/smartpqi] Error 2

make[3]: *** [scripts/Makefile.build:485: drivers/scsi] Error 2

make[2]: *** [scripts/Makefile.build:485: drivers] Error 2

make[1]: *** [/HIBERPATCH/original/linux611/src/linux-6.11-rc3/Makefile:1925: .] Error 2

1) I repaired it, but... LuxCore DLL-hell at compiling - it's NOT as straight / bug-free as it can seem – long process but now OK | 2) SSE2 instruction set is enough speed for most of graphics processing - WHY?

A LuxCore Render Linux compilation – long, problematic process with a dll-hell

Repeating bugs in the process of LuxCore Render compilation, when I compiled it for approx. month of time. I mean both bugs originating from LuxCore compilation environment at the (too?) proud author(s) -site, AND the difficulty operating CMake – when there's even alternatives, and all this bisons, meson, ninja, autoconf..... and last, but not the least – QMake – I feel nervous looking at that. Much problem in Linux world was building of compiz-git package – AFTER much TIME you are being familar with the clang C++/C compiler compilation process. And a compiz dependency, the protobuf library of Google – turned to be copied to /usr/local/... or its subdir.

Similar strategy needs to be done when dealing with some other apps that depend on ICU-xx internalization library,

First, most important question - where is a point that Linux system (concretely, Arch Linux) goes?

Contantly changing of the most basic system elements – even Debian users aren't glad when they are forced to using old package versions – I tried evento „run” non-functioning App Image.

I made convenience script that replaces the ENV. to „LD.” it to old, previoulsly-copied version of ICU lib. Then I could run some programs OK, with gmrun application „activator”/runner possibilities. As in Linux world, things aren't changing so speedily, this way of operating and administering Linux system – in my opinion tends to remain.

When chaotic vision of system growth makes things complicated, and more scalable

I see it, as a repeating pattern, in process of upgrading the system. In my experience some things need to be compiled but other of course can't – I'm not fan of Gentoo user-compiled system solutions. I do compilation when it suits needs – I „omitted” one importand bug by it, so far. AppImage is not usual solution, I don't believe in it – instead of depleting system RAM, I prefer .so object sharing in RAM. And more, I prefer such techniques of optimizing application code.

If we would use Linux apps wisely, the additional CPU power would have less point of EVEN usability of too-multithreading/CPUs in the MB.

I don't need AVX, SSE3 plus, multi-multi, hyper threading – if you can't program algorithms (esp. browser HTML / +the Java runtime) with proper degree of optimization, then you should direct your time meditating on general information technology issues. One example are the criteria of automatization – you fear it, but life shows it will be necessary in future. Similar issue is to be understood when thinking about relation of internet browsers (esp. in matters of WebGL). Way you use a product implicate the calculational complexity in the main-or-GPU processor. If you make a wise applications (for example, not China/Japan pokemon-go animations in Blender –» ), •then CPU/GPU execution is simpler, and even Watts from your power supply are overall more effective (smaller energy consumption, means more $$$s, to write some of advantages).

They think maybe that pikaur helper and all this „chaotic” solves problems. No, w/o proper philosophy, it can't be done.

I rather treated Linux system as modern. How an error! Arch Linux seems to be modern, especially because of ability to complex-repair and „simplicity” of elasticity – DIY compiling things from AUR shapes system user experience into quickly-resolvable as the needs arising. But this Arch Linux typical approach does have its counterpart. Very flexible system is compromised by time spent in actualisation (including its part, compiling software). Things have some huge bugs, and this turns to be a point when disadvantage of Linux approaches. You have bugs in DE, you have bugs in LuxCore Render (disappeared when I linked whole Bfor Artists into KDbg – ONLY THAT SUFFICES! – LuxCore Render NO MORE STALLED the Blender remake, that is, Bfor Artists, suite.

But it can't be done at all times.

I'm a man, not desiring to replace system elements in an unpredictable way. And definitely, not want to await Blender „Modern” ugly pokemons in Blender / Bforartists suite. Why you must repeat China's errors, America?

Think more about philosophy and spirituality – as Robert Monroe said, you are more that your physical body. As intelliogent being, we must care about ourselves, not only this machines, PCs, smartfons (EGL library). We are NOT „pocket humans”. We are more worthy that systems that we are programming, and also, administering.

Things not need to be quicker, quicker, quicker.

OpenCL was somewhat fine, but selective. Why to make such mess in era of multiprocessor motherboards??! If it really be... fine... then, GPU would be in BIOS as another main processor option !!! But is doesn't. You should m e d i t a t e on 3D graphics rendering process, not only „eat” it mentally. That's it.

•As in life. Contemplation matters, but it mustn't be limited to external, peripheral env. Be humans, NOT the monkeys or other animals!!

•Why I don't „believe” 100% in USA when dependent on China hardware... still. Such a big problem... . But bigger problem would be if Americal even turned to [be the]China.... This 'd make the spiral, a cascade of problems – avoiding that starts certainly at clues contained in this article!

LuxCore older MB SSE2 Compile?-partly FIX…Rule:1CPU1MB|Part Two: »LUXRAY...

Part 2 – Clang compiler checked (pgrep – OK), actualization of system Clang package brought one error-fix instantly, main issue now (as moths ago...) remains CMake rules that are applied also to... 1 of static .a libraries: "LinuxCompile-master/target-64-sse2/lib/libboost_python310.a', needed by 'bin/luxcoredemo'.". Other details are on the video. *Factor of build processes is symlinking & copying of Py #include files from Blender-Python-compatible downgraded (by command downgrade without r letter on its name ending) Python version. Some flexibility here is available by using Arch Linux.

(Rule 1CPU1MB = fully local compilation, no strange MS Azure platform/env, no intranet nor etc. – budget solution and satisfaction from not giving money to pokemonny devel– – – opment). I don't need „max factor” games, i don't need 8-core-threaded Pentium CPU processing units. Really Ultra/Giga HD resolution games, games, games the addiction makes big fun, joy, time waste & happiness?! Rendering can be scientific & spiritual art. ZAKHAR: BOTH. #SSE2 #mnemonics #luxcore #compilation #boost #linking #compilation #clang #luxcore #libraries #cmake #aur #archlinux #IT

Mind is ~ machine to load/service/fix/„upgrade”/„transfer”/buy it!^Kurt...

Course cannot be curse... . It is NOT important to write strange language (I mean Kurt Goedel nomenclature of „grammatical” writing) elements correctly/ultracorrectly. Details aren't sometimes crucial if man want be human... . But it is uncomprehensible how you can crash good software.

#brain #mind #software #soft #IT #Goedel #theorem #celebral #cortex #neocortex #mindbodysoul #dualism #monism #hebrew #analysis #metalanguage #paradoxes #mathematics #scientific #americans #science #intermediate #luxcore #compilation #defects #bugs #consolidation #philosophy #metascience #metalogic #maths #thinkingschool #celebrum #biology #transhumanism #indepth #logic #discoveries #course #timemachine

LuxCore uncrash stabilization Bash/Py scripts – Blender console rendering

Bash & Python toolkit to trick LuxCore Renderer plugin exporter/&standalone to the normality, with latencied preface descr... . Blender render preview is erratical & even distractionful. This is NOT full fix, but makes fun:: —Lux Standalone is for previewing rendering. And, 4abstraction(kosherization), •Standalone LuxCore UI window is for single, AND „unshown process” standalone script module is for animations (VERY QUICK **OPENCL** KERNELS RENDERING DESPITE RELAUNCHING BLENDER PROCESS). Trick to step above bad bug of SUSPENDING rendering „packet”: Blender+LuxCore+Python in combination. Even if this occurs only in „too complex” scenes – behind scenes is laziness of US programmers. AND By USA I mean whole USA worldwide collony. Occupation of minds by this, that, old, new versions of software & other inventions, –That rendering is known to be simply stable. BUT I TESTED IT – OPENCL KERNEL COMPILATION IS VERY FAST TO THIS POINT, –Both commandline & Linux, first script small & ultra simple, 2nd longer. FIRST CAN RENDER OPENCL ANIMATIONS BY SHORTLY RENDERING ITS KERNELS!!, –Application ver. Blender 2.80, •Lux ver. 2.2 . I don't bother with SSE3+ / AVX... instruction set motherboards „ultra super hiper–viper change of [ha ha] renewal” (in other words, pokemonnism). –Triade of softwares in packet, as I searched, can p r o b a b l y be repaired by new Python multithreaded ongoing version......... . Remember: All in USA is an experiment. This has heavy implications. Pokemonny nature of ppl is reflecting also on the programming spheres, informatics, IT tech. —thus, I decided NOT to inform forums additionally. USA has its „freedom” – I think that it should be read as laziness & more of the rome... . #strictness #LuxCore #standalone #combination #programming #OpenCL #Blender #script #tools #scientific #rendering #Bash #Python #KDevelop #crash #error #debugging #workaround #toolset #toolkit #GIL #GlobalInterpreterLock #buggy #solution #step #opencl #kernels #Featherpad #trick #hack #stability #test #unattended #preview #UI #ZRAM #listing #coding #clipboard #parcellite