Zigbee devices have their pairing process defined on the device. It’s just a method of generating a trust with a Zigbee network, so whatever method will end up with the same result.
Those IKEA devices have issues being part of multiple networks in my experience. Some are not even capable, so if that’s your plan, expect problems.
Whoops, you are correct. Sorry about that!
If you’re literally unfamiliar with the technical process of this, I suggest you go back and read a guide, so every step very literally, and then come back if you have a problem.
It’s very obvious that’s you’re skipping steps or ignoring something.
As long as it has Internet access you can do whatever you want like any other normal machine.
I’m so lost here…
Is it not already DEAD simple?
I’m guessing it’s similar to this: https://discuss.kde.org/t/plasma-doesnt-start-when-external-monitors-are-plugged-in/17350
You’re probably on a laptop and have multiple GPUs enabled at the same time. If not, you’re defining Nvidia drivers with something trying to be smart about when to enable the actual outputs or not.
You can either make sure to have the display turned on, or make it super clear to the drivers to always enable a display regardless of whether it detects a display.
It still starts the KDE session, but it’s probably on another term output. Hit ALT+F1 and see if it shows, but it depends on the distro, so it could F1, F6, F7…etc
Well in that log, it actually DOES use the right GPU. There are some other errors you have going on in there though, like you seem to have AV1 encoding selected somewhere in your settings, but this RTX 3070 doesn’t support AV1 encoding (on the fly) AFAIK.
Try launching the app this same, setting all your hardware encoding stuff back to defaults, then see if you can get it working. In these logs it IS picking up the second pipewire display, so that’s good, but launch this way again without AV1 enabled then upload the logs again and let’s see what’s happening.
Missed your logs link, but there’s some hints in there.
You have both an Intel GPU and Nvidia GPU in that laptop, and it’s selecting your Intel while trying to use Nvidia compatible settings. So you need to try and force everything to either work on Nvidia, or everything to work on Intel. It can’t do both without splitting the settings per GPU, which I don’t think is an option in OBS.
There’s a multitude of things going on here probably, but you need some debug logs to find. My guess is because your machine probably has multiple GPUs enabled, it’s picking the inactive one, or you have multiple portal methods install and it’s choosing the wrong.
Can you get some logs?
For running a Lemmy server, or you mean the desktop app? I’m confused on what your goal is here.
Yeah, that’s not a straight Debian image, it’s a yunohost image.
Stock Debian images are here: https://www.debian.org/distrib/
Where’d you get the image? It sure seems like you installed a yunohost image of Debian. See here for the default credentials to try logging in: https://doc.yunohost.org/admin/command_line/
Need more info. Is this in a desktop, via SSH…etc?
Where’d you get the Debian image from?
No, you can’t install the drivers manually if they aren’t supported. Nvidia does rolling driver releases removing aged out hardware, and the drivers do not support new versions with older hardware. Same with Windows.
Nouveau is the only option you have as far as hardware acceleration goes, but if these are laptops, you’d be better off just using the Intel graphics, because that’s what’s available, and they are very power efficient.
Power consumption is immediately bad once you engage the Nvidia hardware. Disable it in the BIOS. You won’t have better performance in any meaningful way, just horrible battery life, especially since these are devices so old the modern drivers won’t support the hardware.
I’m confused here…you DO know you can just reprogram the device over USB and overwrite everything, right?
Well then hold it for 10s and cut power to it while still holding the button.
The link literally had today’s date…
This is the issue. There are all kinds of special steps needed because of various issues.
Skip Garuda and go for a distro that is known to work well on Surface like Fedora, Arch, or Mint.