Interstellar_1

For those who are still using google, this recently added search query strips all of the extras from Google search, leaving behind just the links!

What is &udm=14?

Browser search query: https://www.google.com/search?q=%s&udm=14

My laptop is running out of storage space and I don't have anything I can remove anymore to increase it by much, so I'm thinking about building a pc. I'd also like to find a better gpu for doing video editing.

It will be the first one I've built, so I don't really know what I need. Also, does it matter for compatibility for Linux whether I go with AMD or Intel?

The high end of what I want to use it for is video editing with Kdenlive or Davinci Resolve, some modeling and animation in Blender, and some light gaming, like Minecraft or TUNIC.

I figure one of these guides might be useful, but I don't really know which.

Is there anything else I should know for setting up a PC to run Linux?

Edit: Maybe these guides from Logical Increments can help actually.

I'm currently using Fedora KDE Plasma, but I'd like to try out a tiling window manager. What would you all reccomend? I use my computer for school, so I would like it to be stable.

(not really pipewire itself but an interaction with wireplumber/libcamera/the kernel, but pipewire is what triggers the problem)

As seen in https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/2669 and https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/4115

The camera's /dev/video file is kept open (without streaming), sadly causing the camera to be powered on what looks to be most devices. For some reason, this completely nullifies the soc power management on modern laptops and can result in increases from 3W to 8W at idle!

On Intel laptops it's a bit easier to debug because you can see the Cstates in powertop not going low but it also wrecks AMD ones. Some laptops can reach lower cstates, but the camera module wastes a few W anyway.

I can't believe this shipped in Ubuntu, Fedora etc without anyone noticing, and for so long. This bug is quite literally wasting GWh of power and destroys the user experience of distros in laptops.

If you have a laptop with a switch that detaches the camera from the usb bus you are probably out of the water, just plug it when you use it and the problem is sidestepped. Removing uvcvideo and modprobing it on demand can also work. Disabling the camera in Lenovo's UEFI is what I did for a year until I finally found the issue on the tracker. Some laptops also seem to not be affected, but for me it happens to every machine I've tested.

Thanks to this comment for another workaround that tells wireplumber to ignore cameras. ~/.config/wireplumber/wireplumber.conf.d/10-disable-camera.conf

wireplumber.profiles = { main = { monitor.libcamera = disabled } }

Software that only captures cameras using pipewire is rare and this hasn't given me any problem. This should probably be shipped by distros while the problem is sorted out.

Note that most laptops will have other problems stopping them from reaching deep cstates, borked pcie sd card readers, ancient ethernet nics that don't support pcie sleep properly, outdated nvme firwmare... those are separate issues that most of the time can also be tackled with some dose of tlp, but it's all for nothing if the usb camera is keeping the soc awake!

Very interesting article!