Yeah performance and energy efficiency is one of the factors behind the decision Valve made with the screen. The display is on par with entry small factor laptops from late '00s (in resolution, otherwise obviously better).
Yeah performance and energy efficiency is one of the factors behind the decision Valve made with the screen. The display is on par with entry small factor laptops from late '00s (in resolution, otherwise obviously better).
I keep forgetting mods also mean physical modifications of hardware and I was really confused how Valve can support upping resolution on a screen.
Idea of modding hardware in general feels risky af to me. But I’m glad it’s possible, worthwile, and apparently quietly supported by Valve.
They make a lot of good decisions with it.
Seems like it is maintained but not ported to Plasma 6, yet anyway.
Interesting. Do they point to arch repos or provide their own like Manjaro? I haven’t thought about a rolling release atomic distro before.
Modernity ruining children for millenia!
I think you can use grafana to present vidgets from different dashboards in one.
Well the good news is yoi don’t have to upgrade anything, or everything at once. You can get the display now and when your CPU isn’t enough switch mobo and ram then.
IIRC krunner works as a commandline tool, so maybe you could do what you want with something like yakuake, or even make a wrapper for krunner with those additional options.
It seems like something I could use as well. I’ll note it down to take a look later.
I’ve recently used dioxus with rust to build a native app with webview. Way cheaper than electron and the like.
I use a 2016 Asus Zenbook with integrated intel gpu.
The performance is comparable. The only thing that’s different is latency, obviously, although it’s fairly negligible on LAN, and encoding/decoding sometimes createa artifacts and smudges, but it’s better at higher bandwidth.
I found a report so I didn’t do it myself again. It seems it’s fixed even though the report isn’t.
I’ve just checked and it’s fixed. Must have sliped by me.
My box sits in my closet, so can’t really help much with docker or vm. But I use sunshine server with moonlight client. Keep in mind you can’t fight latency that comes from distance between server and client. I can use 4/5G for turn based or active pause games but wouldn’t try anything real time. On cable my ping is under ms, enough to play shooters as badly as I do these days.
I use AMD for CPU and GPU, and wouldn’t try nvidia if using Linux as sever.
I did use to run a VM in xenserver/xcp-ng and passthrough gpu with a mock hdmi screen plug. A windows 10 vm, ran very well bar pretty crap CPU but I did get around 30fps in 1080p tarkov, sometimes more with amd upscalling. Back then I was using parsec, but found sunshine and moonlight works better for me.
I should also mention I never tried to support multiple users. You can probably play “local” multiplayer with both parsec and moonlight, but any setup that shares one GPU will require some vgpu proprietary fuckery, so easiest is to buy a PC with multiple gpus and assign one to each VM directly.
And the regression from last patch with drag and drop freezing Dolphin entirely seems unfixed. Honestly I think it’s the first time in 7 years I’m affected by an annoying KDE bug, but it still stings regressions are not first priority :(
I’m both impressed and bemused why they’d use bash.
We fork until there’s nothing else!
I think this lead me on the right path: https://community.ui.com/questions/Having-trouble-allowing-WOL-fowarding/5fa05081-125f-402b-a20c-ef1080e288d8#answer/5653fc4f-4d3a-4061-866c-f4c20f10d9b9
This is for edgerouter, which is what I use, but I suppose opensense can do this just as well.
Keep in mind, don’t use 1.1.1.1 for your forwarding address, use one in your LAN range, just outside of DHCP because this type of static routing will mess up a connection to anything actually on this IP.
This is how it looks in my edge os config:
protocols {
static {
arp 10.0.40.114 {
hwaddr ff:ff:ff:ff:ff:ff
}
}
}
10.0.40.114 is the address I use to forward WoL broadcast to.
Then I use an app called Wake On Lan on Android and set it up like this: Hostname/IP/Broadcast address: 10.0.40.114 Device IP: [actual IP I want to wake up on the same VLAN/physical network] WOL Port: 9
This works fine if you’re using the router as the gateway for both VPN and LAN, but it will get messy with masquarade and NAT - then you have to use port forwarding I guess, and it should work from WAN.
I just wanted it to be over VPN to limit my exposure (even if WoL packets aren’t especially scary).
There is a trick you could do to send a WoL packet to a separate IP on the sender network and modify it so it is repreated on the network of the machine you want to wake up.
I can’t find docs on thisb on mobile, but can look for it later.
It can’t work like a typical IP packet routing tho. I’ve only made it work with a VPN connection.
Another thing you can do is ssh to your router and send a WoL packet from there on the machine’s LAN.
It’s generic advice, but check kompose
- it can translate docker compose yml into a bunch of k8s objects, as far as it sensibly can.
The mose issues can come from setting up volumes, since docker has different expectations towards the underlying filesystem.
It does save a bunch of work of rewriting everything by hand.
The fact that cuda means ‘wonders’ in polish is living in my mind rent free several days after I read about nvidia news.