• 92 Posts
  • 3.25K Comments
Joined 2 years ago
cake
Cake day: July 7th, 2023

help-circle




  • Post specs on the KVM. I think to do what you’re asking it to do it needs an EDID stand-in/passthrough to be able to explain the capabilities of the monitor and “hold” it’s place when inactive instead of just sending info that’s in standby or something.

    I believe what’s happening is the signal to the cable is cut off from the monitor, making your GPU think it’s been unplugged, and there is no event to say “hey, I’m plugged back in”.

    Confirm a few things:

    1. Switch to Windows, wait maybe 15s, then switch back and see if the display is still working.
    2. Unplug and replug the display cable to the KVM after the display stops outputting and see if it comes back.





  • So desktops don’t work like laptops in this sense.

    On a laptop, the bus for the video output ports can be connected to one or both GPUs, and the software does the graphics switching or offloading.

    On a desktop, there is no consolidated bus between the PCIe card and the onboard graphics, so you can’t switch between which GPU is rendering what on hardware alone. It’s the whole display that is rendered on the device you’re plugged into.

    Windows does have some sort of offloading utility that allows for this i believe, but I’ve never used it so don’t know how well it works.

    On Linux, your display server (X or Wayland) needs to address one GPU at a time to render things.

    You can totally use both GPUs with multiple monitors, but I think that’s defeating the purpose you have in mind.











  • Well you’ve definitely overcomplicated things by introducing a lot of different variables into the mix. What you’ve set up is a hat on a hat. An abstraction on top of another abstraction.

    Let me break it down and just ask: are you just trying to ensure your friends can only access certain addresses on your network, and you’re using Tailscale ACLs for that purpose? It sounds like you just want proper routing security at the edge of your network and are going this route to avoid having to do that maybe?

    Tailscale has a place and works great for lots of things, but using it like this is going to cause all kinds of problems eventually. You’re basically just advertising a bunch of confused routes to the coordinator like this, and DERP connections will eventually fail or freak out because you’re providing multiple paths to different things if I’m reading this right. You’re also introducing A LOT of network overhead because of this, and I can forsee a lot of connectivity issues in gaming throughput if that’s the main purpose.