so it seems that without any config, the traffic passes from wlan1 to wlan0’s network flawlessly; but traffic from wlan0 network stops at the Android device, even with iptables -P FORWARD ACCEPT, so I’m clueless on what to do next

how could I set up NAT like this ? thanks

ip r

default via 192.168.15.1 dev enp3s0 proto dhcp src 192.168.15.32 metric 100
192.168.15.0/24 dev enp3s0 proto kernel scope link src 192.168.15.32 metric 100
192.168.38.0/24 via 192.168.15.21 dev enp3s0    

Mind sharing whhich situations would a timecard be useful ? Probably something that requires enhanced time precision, I just can’t figure it out

These updates land on testing quickly, however due to the several packages updated at once, they all need to be tested by volunteers, and only when all of them are signed it’s pushed out of testing

Already switched to AMD to enjoy it

I figured the root cause of the problem and a workaround. Journalctl shows this info when starting SVP:

• Video: 0 GPU OpenCL device(s) on rusticl [OpenCL 3.0] (Mesa/X.org)*

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

deleted by creator

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

lol my cat actually meows and asks to be vacuumed

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.