I figured the root cause of the problem and a workaround. Journalctl shows this info when starting SVP:
this thread says rusticl is broken
https://www.svp-team.com/forum/viewtopic.php?id=3167&p=17
therefore disabling hardware acceleration, for now, makes svp work again
AMD is the gold standard for general user PCs in the last 5+ years. Intel simply cannot compete at the same energy expenditure/performance. At the same/close price/performance, Intel either burn a small thermonuclear power plant to deliver comparable performance, or simply is worse compared to similar Ryzens
Ryzens are like aliens compared to what AMD used to be before them
So I’d go with them
As for the GPU, if you want to use Linux forget Nvidia
Yeah, it’s advertised as 160hz and even amdgpu_top (which uses xrandr or something like it) says 159.96hz is the first preferred mode, the second being 100hz
I had this problem before with a Nvidia card which reset to 144hz after an update and I could never enable it again. However it’s a mystery as to why it boots up at 160hz in systemd-boot console, and goes back to 144hz when entering KDE or turning the display off
Just wish obsidian had better encryption support
How does it differ from arch install + choosing the DE?
My most paranoid config is disabling Ipv4
That’s it. If someone wants to attack me, they will need to adopt IPv6!
deleted by creator
deleted by creator
deleted by creator
…no ?
years ago I couln’t even dream of using bluetooth in linux; few weeks ago I found an old bluetooth dongle and now my usb speakers work just fine - even better than connecting via smartphone because plasma has sbc-xq codec easily selectable. It auto connects everytime I boot the pc, I just had to add btusb.enable_autosuspend=0 to kernel cmdline parameters
make sure you follow these guides, whicever distro you use
if it crashes, try sudo systemctl stop bluetooth.service and sudo systemctl start bluetooth.service
remember, bluetooth is a very cursed embrace-it-all protocol and may randomly crash/refuse to pair/connect unless you reset the devices manually, and this may happen with any hardware/software
Just don’t upgrade for a while and you become debian
It’s not like windows forcing you to reboot every Tuesday so Edge can come back
"A qsort vulnerability is due to a missing bounds check and can lead to memory corruption. It has been present in all versions of glibc since 1992. "
This one amazes me. Imagine how many vulnerabilities future researchers will discover in ancient software that persisted/persist for decades.
Tyvm for this very well structured guide, I didn’t even realize I was on lemmy until I hit the bottom of it
I thoroughly backup up my slow nvme before installing a new faster one. I actually didn’t even want to reuse the installation, just the files at /home.
So I mounted it at /mnt/backupnvme0n1, 2, etc and rsynced
The first few dry runs showed a lot of data was redundant, so I geniously thought “wow I should delete some of these”. And that’s when I did a classic sudo rm -rf in the /mnt root folder instead of /mnt/dirthathadthoseredundantfiles
Already switched to AMD to enjoy it