In general it sounds like you want ‘tiling’. There are multiple window managers that does this, e.g. AwesomeWM, i3, Sway, River etc.

Additionally you typically have ‘tiling scripts’ that work on top of Gnome and Kwin (Plasma), however unsure what the capabilities are there.

I can atleast speak for Sway:

Here you can can move/select the current focused window relative to whatever key strokes you prefer, the defaults are using Vim-bindings, but arrow keys are also pretty common.

For grabbing a specific window (like in an ordered manner) is probably something that you would need to extend through scripting if the ‘basic’ movement isn’t enough.

Note: A tiling window manager is quite different (in usage) from a stacking one (which is what one is mostly used to) tiling capabilities/scripts

Der8auer’s video is worth a watch, he got one of the Redditor’s card:

https://youtu.be/Ndmoi1s0ZaY

Yes, so R&D and finalizing the model weight is done on NVIDIA GPUs (I guess you need an excessive amount of VRAM).

Inference is probably gonna be offloaded to consumers in the end where the NPU is taking care of the inference cost (See Apple, Qualcomm etc)

Not the best on AI/LLM terms, but I assume that training the models was done on Nvidia, while inference (using the model/getting the data from the model) is done on Huawei chips

To add: Training the model is a huge single-cost expense, while inference is a continuous expense.

Are you by chance using an integrated GPU?

Noticed that my AMD Radeon 680M uses quite a lot of RAM as shared memory.

Using something like amdgpu_top will show how much RAM your iGPU is using, metric is ‘GTT’

The whole downside is that not everyone is a data horder with space for videos

Some media players allows for streaming directly using yt-dlp, e.g.;

mpv <youtube url>

Will use yt-dlp if installed

One thing to try is to update the firmware of the controller, however that needs to be done on Windows, the Arch Wiki has some additional info where people explain pairing issues

There’s also a section on “able to pair but no inputs” in the troubleshooting section on the same Wiki page

Not what I expected, good thing you managed to get it solved!

That dump didn’t reveal any particular useful information, however it seems like multiple people are reporting issues with mesa + segfault, e.g. https://bbs.archlinux.org/viewtopic.php?id=301550

Mesa v24.3.2-1 in Arch should revert that issue, Mesa v24.3.1 seems to be the problem one

You could check the backtrace of one of your crashes

coredumpctl debug
> bt

And then dump that trace here

It might be related to Mesa/GPU drivers

Sounds like you might just be max’ing out the capacity of the coax cable as well (depending on length/signal integrity). E.g. ITGoat (not sure how trustworthy this webpage is, just an example) lists 1 Gbps as the maximum for coax while you would typically expecting less than that, again depending on your situation (cable length, material, etc)

What’s your situation into the wall? Depending on country/ISP/regulations they might give you up to 1000 Mbps under the assumption that it’s a single line going to a single user, however quite often that line is shared with potentially a lot of different customers.

Some countries allows you to buy packages where you have a standalone line going to your wall, however at an additional cost

If all nodes are connected through ethernet to each other (or at least one common node) you could go for OpenWRT’s ‘Dumb AP’ setup as well

Edit: Already mentioned here; https://feditown.com/comment/1980836

Maintainer has been absent for some time so kernel v6.11 and v6.12 isn’t supported OOTB, to get it to work with kernel v6.11 you need to pull the fix from: !48

Additionally you can try and force use amdgpu rather than radeon, by setting the kernel flags:

radeon.cik_support=0 radeon.si_support=0 amdgpu.cik_support=1 amdgpu.si_support=1 amdgpu.dc=1

Source

Device initalization failed according to the Xorg logs;

1. Dump your firmware version
2. Dump your kernel version
3. Dump your kernel logs (dmesg or journalctl -k)

Running: swaymsg for_window "[app_id=mpv] opacity 0.5"

Works as expected on my end, are you missing just executing for_window?

Note, you can also add multiple rules in the same execution, e.g.

for_window {
    [app_id=mpv] opacity 0.85
    [app_id=LibreWolf] opacity 0.85
}

Also, note that app_id of LibreWolf is capitalized in that manner. You can get that information [app_id, shell etc] by running swaymsg -t get_tree

Feel like most people still do the scripting in Bash for portability reasons, and then just run Fish as the interactive shell

Archlinux’s XZ was compromised as well.

News post

Git change for not using tarballs from source

Nice, then you should be able to run vkcube to verify whether your GPU is activated properly.

You can do several “iterations” here as well.

1. Install Mangohud so you can visibly see if your GPU is activated correctly
2. Run mangohud vkcube-wayland - Does it use your Nvidia GPU?
3. Run mangohud vkcube - Does it use your Nvidia GPU?

If Step 2 nor 3 shows your Nvidia GPU you can try and force it with: mangohud vkcube-wayland --gpu_number 0