canadaduane

Keep an eye on Pop COSMIC. It isn't ready yet, but I'd give it 4 months and I think it would be a great match for something like rpi.

This makes more sense, thanks.

Is it possible to get this to work with OBS studio? I see the author mentions OBS as an "Alternative Project" but it seems ideal to have these pieces work together.

This is really cool in concept, but it is SO SLOW. OMG.

I've started playing with Chimera Linux. Super interesting hybrid between BSD-like systems (ports, BSD-derived userland tools) and the Linux kernel, with neat design choices like LLVM compiler instead of gcc and musl C instead of glibc. I think of it as a next-gen Void Linux.

Yes, it's supposed to be animated. I saw it animating earlier today. However, I can no longer see an animation (Firefox and Chromium both tested). Strange!

I wonder if it is related to these:

• https://gitlab.freedesktop.org/drm/intel/-/issues/6154
• https://gitlab.freedesktop.org/drm/intel/-/issues/4858

Install intel-gpu-tools. Set GPU to max frequency: sudo intel_gpu_frequency -m

If this fixes the issue as it did for "L L", the speculation is that the root cause is related to on-demand frequency management.

Some great coverage here: https://www.businessinsider.com/russian-officers-sold-black-sea-fleet-intel-ukrainian-fighters-report-2023-9

Here's how I would investigate this:

1. Try disabling MolecularNodes (and any other add-on) just to be sure it isn't the culprit
2. The CPU usage seems like an important clue. When you say "My computer is not locked due to memory, CPU, nor GPU usage", how does this relate to "just noticed that Blender is still using 100% CPU"? Any chance it is trying to render via CPU instead of GPU?
3. Check the journalctl logs on the command-line, i.e. in the Terminal app, type journalctl | grep -i blender (the symbol between journalctl and grep is a pipe aka vertical bar) I'd be looking for things like crashed processes, warnings, or errors, especially around the time of the freeze.

Ah, thanks! Slightly different location, but basically the same. Here we go:

$ grep CONFIG_KERNEL_ /boot/config-6.4.6-76060406-generic
# CONFIG_KERNEL_GZIP is not set
# CONFIG_KERNEL_BZIP2 is not set
# CONFIG_KERNEL_LZMA is not set
# CONFIG_KERNEL_XZ is not set
# CONFIG_KERNEL_LZO is not set
# CONFIG_KERNEL_LZ4 is not set
CONFIG_KERNEL_ZSTD=y

So the kernel is "zstd" compressed.

OTOH, I'm not sure if this means anything about initrd (ASCII cpio archive??)

$ file /boot/initrd.img-6.4.6-76060406-generic 
/boot/initrd.img-6.4.6-76060406-generic: ASCII cpio archive (SVR4 with no CRC)

Wow, this told me much more than I expected; however, I'm still not sure if it's zstd:

/boot/vmlinuz-6.4.6-76060406-generic: Linux kernel x86 boot executable bzImage, version 6.4.6-76060406-generic (jenkins@warp.pop-os.org) #202307241739~1694621917~22.04~ac5e1a8 SMP PREEMPT_DYNAMIC Wed S, RO-rootFS, swap_dev 0XD, Normal VGA

bzImage sounds like...bzip2, maybe?

When I check this file, it is already set at COMPRESS=zstd. However, I'm not sure if it's working as I think, because the vmlinuz-6.4* kernel file is not a zstd file? Maybe it uses zstd for just a portion of the binary...