

That might be your issues. What kernel are you on?
That might be your issues. What kernel are you on?
And you’re saying you’ve tried this? It’s all software, so I don’t see why it wouldn’t work: https://gitlab.freedesktop.org/pipewire/pipewire/-/wikis/Virtual-Devices#loopback
You’re trying simple mixers when what you need is elaborate pipewire configs.
Some things I would try before going that route:
qasmixer
pavucontrol
Both similar, but qasmixer has a few GUI things to twiddle with that pavucontrol does not. Give them a shot.
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:
WOW. That is cool as hell. This guy has a great mind to think of working something like this up.
On Prime you can make your iGPU the primary (display connected to motherboard), and offload some rendering to the dGPU with some caveats. It was only working on Xorg for awhile, but maybe it works better under Wayland now. Couldn’t tell you.
I would assume that means it’s not configured. What do the logs say?
You heard wrong. Nvidia doesn’t play nice with Linux.
Of course it works just fine, but it can be somewhat problematic for beginners. You’d still be better off going with AMD just to avoid issues if you’re only concerned about “plug and play”.
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.
I’m not sure what in the world these other answers are, but that is not how GPUs work if you’re talking about a desktop.
If you’re talking about a laptop, this is not going to work in Linux.
It’s hard to tell from your description if this is desktop or laptop, btw. Post the model of it is a laptop as this will be important.
The real question is: why do you need this much memory?
If it’s not actually going to be used, you’re spending more money acquiring it now than you would later.
Why? It’s free if you don’t setup a custom runner and those cover your areas.
🤦
Sure, bud. Read up the chain.
At what point do imagine that DHCP is not in play here?
Y’all keep talking about randomized MAC like it’s a tool of anonymity or something. Wow.
It’s a Boolean setting on Android, and there is no reason to change this. OP doesn’t understand networking.
Because the MAC address isn’t a part of the tcp/ip exchange. You’re specifically addressing TCP/IP only.
If you’re trying to block something by MAC address, you’re doing it wrong.
Why the name change though? Most projects put up a deprecation notice on the old one and a link to the new if they do this.
The PCB is probably shedding at this point, so the contacts have a gap. You could try putting a nub of something in there for added pressure, but it surely still won’t feel right while playing.
Is buying a used controller out of the question?
Okay then if Wireguard, you need to punch through your NAT and allow that port access to the world, then to fix your outing issue, you need to look up split-tunneling. That should solve the issues you’re seeing if I’m reading this right.
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.
I don’t understand why you’re posting.
He voluntarily left that community and left a lot of words behind justifying why, and I think your post falls into the trappings of things he hated about having to commune with certain people.
It certainly seems like he wants to be left alone, so just leave him alone.