I bought a used HP Elitebook on eBay for a similar purpose. I can browse and do video calls on a bigger screen when the fancy strikes. Pretty much any used business laptop should work. I think I paid about $300 for mine and I paid extra for particular hardware I thought was neat but you don’t have to. Only thing to keep in mind is the battery will likely be pretty worn.
The idea of single, double, and triple buffering revolves around how many framebuffers we use for display rendering. Typically, we go with double buffering, displaying one framebuffer while rendering happens on the other. Swap them, and the cycle continues. The goal is to prevent screen tearing and glitches from popping up on the screen.
Honestly, I haven’t explored Vulkan yet. I initially chose GLES 2.0 as the primary renderer to ensure compatibility with a wide range of hardware. Introducing Vulkan myself would be a time-consuming task unless I receive assistance.
Regarding XWayland, Louvre doesn’t currently support it, so it’s naturally excluded. Well, it technically can run in rootful mode, but that is somewhat pointless. To enable independent window management, I believe I would need to create a mini X server, a task I haven’t tackled as of now.
Probably all of them have better Vulkan than opengl drivers (due to drivers being simpler). David Arlie rather quickly implemented first Vulkan driver for AMD once Vulkan was first released. Just in case you need incentive.
I was thinking of starting something similar as a learning exercise, but I’m really limited in time and not skilled as much in c++, so it would probably lead nowhere. Now I can just build on top - if I get any time for this, will come probably with questions.
Anyway, this idea was to make something modern. Without the legacy crap. Actual goals were:
Vulkan only (move gfx API Info the future)
no x/xwayland (most of the apps in newer toolkits already support Wayland, the others I’d rather avoid)
Interesting, I don’t recall where I read about Vulkan support still being experimental in many Mesa drivers; it might have been an outdated post. I’ll look into it, and perhaps I’ll decide to dive into learning Vulkan. Additionally, there are buffer-sharing mechanisms that already work smoothly with GLES, so I need to explore if the situation is similar for Vulkan. Thanks for your response, and if you have the time and inclination to help include it, feel free to do so! 😄
How do you handle which GPU is used in which game? I would guess you have an AMD iGPU, and a Nvidia GPU for games, right? Maybe something along those lines got updated?
That’s correct, but i mostly let the laptop handle it, unless i know for a fact that a game needs/doesn’t need the N GPU, in which case i either manually switch it over or (and this is the case for wine apps through bottles) i configure the program to only use the iGPU
The issue isn’t with Linux directly so any distro you use will do the same.
It could be a hardware issue that the machine is not dissipating heat.
Or it could be that you need some kind of driver/controller software for fan. It sounds like the system isn’t properly controlling the fan. It leaves it low when it doesn’t defect usage but when it does, instead of increasing the fan a little bit at a time, it just goes full tilt to be safe. It probably cannot read the temperature sensors and so has no idea whether your need cooling or not.
I don’t know the answer but do some googling around system temperature reading on that model and see if there is a module you need to install.
linux
Top
This magazine is from a federated server and may be incomplete. Browse more on the original instance.