mark

@9488fcea02a9 @sxan Almost all printers work now, since they have to support IPP Anywhere to be useable by phones

@arsCynic Nvidia drivers, prime offload with Wayland is still a no go.

@ColdWater You could write a small kernel module that just triggers one as soon as it’s loaded

@6R1MR34P3R Some of the LILYGO devices are great for use straight out of the box. I have a T-Echo as my portable device, the T-Deck Plus is also an option if you want something completely stand-alone rather than controlled over Bluetooth or USB. Note that the 868MHz band is more widely used due to congestion on 433MHz, (915MHz is for the Americas and isn’t legal here)

@iii @6R1MR34P3R Depends on how good of a setup you want, but you can start for less than €50.

@gi1242 The US government, not Red Hat themselves.

@xavier666 Given that Canonical is a British company, that’s not something that could happen at all. Red Hat is anyone’s guess given that the law doesn’t really mean anything to them any more.

@dontblink You would have to write a PAM module to do that

@Pogogunner At least on Debian based distros, it’s all part of the driver installation.

As for how it works at the hardware/kernel level the iGPU take some of system RAM to use as VRAM, so all the kernel has to do is give the dGPU a DMA buffer into that. The final piece is for the iGPU driver to send a synchronisation signal to the dGPU when it’s ready to receive the (partial-)frame.

@jeena @Pogogunner

I’m going to assume that it is possible to put both the dedicated and integrated GPUs to work, though I’ve never seen this kind of setup.

Every single laptop with a dGPU does that, as I’m typing this now only Minecraft is using the dGPU while everything else is on the iGPU. Everything is fully performant (including YT videos), and it greatly increases battery life.

@jeena As always the Arch wiki has you covered. PRIME, is the system you need. It’s slightly easier with the monitor plugged into the iGPU, (that’s how laptops are wired).

@harsh3466 That should work, as always with dd the potential disaster is getting if and of the wrong way around and wiping the old drive.

@GregorTacTac If you use containers you can map something like 8080 on the host to 80 in the container. Generally it’s recommended to have a reverse proxy listening on 80 and 443 with all your individual applications on localhost only high ports.

@Tippon That is a big part of the point behind containers, you don’t have any long term state inside them. Migration is just a case of copying the configuration over along with the contents of any persistent volumes.

It’s worth looking into Podman instead of Docker, the daemon-less architecture makes it more lightweight and secure as it’s easier to have rootless containers. Management can also be easer as being a Red Hat project it integrates well into Systemd.

With your existing server on Xubuntu you may as well stick with Ubuntu Server or Debian for the familiarity.