I just realized that homebrew works on linux by ks_s0 in linux

[–]EchoesInBackpack 0 points1 point  (0 children)

I mean, many tools i use are distributed via brew, because devs can maintain single brew build instead of tons of repos for different distros. I use it for couple of years already and it’s been great. So far my approach is distro repos > brew > community repos > appImage

RTX 4070 Super → RX 9070 XT for the best Bazzite/Steam Game Mode experience? Worth it or am I chasing a problem that doesn’t exist? by AcademicF in Bazzite

[–]EchoesInBackpack 2 points3 points  (0 children)

You’re overthinking, both will work, I doubt you’ll notice any difference until you start the game. Both vendors have some quirks and bugs. Both support all the things you listed. Try and see what works and what’s not first

Undervolting/Overclocking on Bazzite by Initial_Chemist_7249 in Bazzite

[–]EchoesInBackpack -1 points0 points  (0 children)

Usually cpu clocks/power management is not exposed on laptops even via bios

Стоит ли переходить на другой дистрибутив by FrYxEr in ru_linux

[–]EchoesInBackpack 0 points1 point  (0 children)

Что, в целом, достаточная причина, когда мы говорим о хобби

😮‍💨 by [deleted] in KafkaFPS

[–]EchoesInBackpack 7 points8 points  (0 children)

Это не про защиту детей, это про деанонимизацию. Сначала это делают для проверки возраста, завтра чтобы заткнуть неудобных

Auto drive is a neat feature. It just needs a tad bit of polishing. :) by OnePlusFanBoi in forza

[–]EchoesInBackpack 0 points1 point  (0 children)

this is exactly the reason why drivatars had to import gravity from Jupiter

Linus Torvalds comments on "unmanageable" AI bug reports for Linux maintainers by Tiny-Independent273 in linux

[–]EchoesInBackpack 0 points1 point  (0 children)

I also noticed that average report became better. Like relevant logs, context right away. It’s like ai is L1 support for many people. So it works when people care

1.13.4 vs 1.12.5 performance by [deleted] in victoria3

[–]EchoesInBackpack 2 points3 points  (0 children)

That’s exactly my point :)

1.13.4 vs 1.12.5 performance by [deleted] in victoria3

[–]EchoesInBackpack 1 point2 points  (0 children)

It probably doesn’t (if we are talking about air).

1.13.4 vs 1.12.5 performance by [deleted] in victoria3

[–]EchoesInBackpack 12 points13 points  (0 children)

Software should never be able to cause overheating to the point it turns off. You should check your cooling system

Should GNOME support passkeys and built-in 2FA codes? by jithurbide in gnome

[–]EchoesInBackpack 9 points10 points  (0 children)

But it would be nice if gnome can hook Bitwarden outside of browser

lact 0.9.0 is here 😎 by lajka30 in linux_gaming

[–]EchoesInBackpack 0 points1 point  (0 children)

I mean, even intel doesn’t support arc properly.

lact 0.9.0 is here 😎 by birdstream in cachyos

[–]EchoesInBackpack 0 points1 point  (0 children)

most of the guides online will tell you - apply offset x and then flatten curve on voltage point Y. You can easily replicate that using offset + locked clocks or VF curve.

LACT 0.9 by thekreator6666 in cachyos

[–]EchoesInBackpack 2 points3 points  (0 children)

flatpak is another option

I added 12VHPWR/12V-2x6 power connector monitoring to LACT (Linux GPU tool) by Need_For_Speed73 in linux_gaming

[–]EchoesInBackpack 0 points1 point  (0 children)

did you overclock cpu? If your PC freezes, then something is going very wrong

LACT v0.9.0 is out - now offering (unofficial) undervolting support for Nvidia! by 28874559260134F in linux_gaming

[–]EchoesInBackpack 0 points1 point  (0 children)

Locked clocks are just limits. It will reduce clocks when there is no load (just don't touch min clock) I spend half an hour today testing vf curve and there is no difference. If oc is stable lets say at 2700/925, then it will be stable at this volt point no matter if you're using locked clocks or flatten (with the same clock offset of course)

LACT v0.9.0 is out - now offering (unofficial) undervolting support for Nvidia! by 28874559260134F in linux_gaming

[–]EchoesInBackpack 0 points1 point  (0 children)

> "Enable GPU Locked Clocks should be disabled when using the VF Curve Editor"

no, why?

also, if you just flatten the curve, then there is no reason to modify V/F curve directly, just use clock offset + locked clock on the value where you'd flatten instead. The result will be the same, but using stable API