

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.
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.
Upvote for OSnews. Been around forever, and they keep staying alive.
I’m so lost here…
Is it not already DEAD simple?
It’s not bulletproof, but I’ve seen it live, so it happens. Proof:
When you increase your resolution, your monitor switches power modes. At a higher refresh rate, a dirty power signal can cause artifacts on the screen. Usually this means that you’d see bit crawl on the edges of the screen, but it could show display artifacts like you describe depending on the panel controller.
If your UPS took a hit during a thunderstorm, you could easily have a damaged rectifier in the UPS. That rectifier is responsible for smoothing the power signal coming out the ports on your UPS. A dirty signal can do the above as I mentioned.
You wouldn’t notice a problem on your machine because it’s own PSU smooths those signals out, but a monitor doesn’t have that.
I meant switch the power plug for the monitor to a different outlet.
Check your package manager logs to find out. Also check dmesg
just in case.
Edit: you know what…try changing the outlet the monitor is plugged into and see if anything changes. Curious if the signal is weird or the rectifier got damaged by a surge. Maybe try the wall as well to find out if it still does it.
Probably surge damage, honestly. Was your monitor plugged into the UPS or another surge protector, or just into a wall? Do you have any other cables connecting to your machine that aren’t on the UPS or a surge protector? Also, a power strip is not equal to a surge protector.
As far as the cause, if you’re seeing artifacts on screen past a certain position on the screen, that’s the screen or cable, not the GPU. Your display adapter sends fully rendered frames to the display and wouldn’t have a specific part of the frame that is corrupted if damaged. Anecdotally speaking, if a GPU has damage, it just won’t work.
Also, you may want to check the capacitors on your card and motherboard to make sure they’re all still flat and not bulging. If bulging, you took took surge damage and need to redo your cabling to make sure everything is protected.
This may be helpful: https://www.tutorialworks.com/podman-rootless-volumes/#how-to-allow-a-rootless-podman-container-to-write-to-a-volume
The real trick is set the “:Z” flag for the volume. This usually solves most problems, but will not allow that same volume to be used with other running containers.
These prices are absolutely insane when compared to a Deck. WTF.
Why are there so many different types of bread at the store? Or mustard, ketchup, milk…etc.
It’s mostly personal preference and reputation. Ubuntu has a shit reputation right now because of some poor decision making, and Fedora has a solid reputation and doesn’t cause problems.
That’s pretty much it.
Removed by mod
Removed by mod
Removed by mod
Removed by mod
Removed by mod
Removed by mod
The main power draws on a laptop are the display, the GPU, and CPU in that order. If you can’t tame the first two, the third won’t matter if we’re discussing hardware platforms in the past 5 years.
If you can tune one distro to be as power efficient as you like, any of them can do it. There is no functional difference between any of them that is not configurable.
The most power efficient and balanced platform you’re going to get is an AMD APU for general work, or something REALLY weak but efficient like the lowest of low-end Intel like the n-series chips.
Anything with Nvidia in it is going to drain your battery quickly, even if not being utilized (that’s a hardware design thing I won’t go into).
Exactly. MBR is pretty much not used at this point except on legacy hardware where EFI is not supported. As mentioned, it’s also unreliable in this particular combo.
Removing this does two things:
Ensures the most reliable way of installing is enforced by default
Removed untested and entangled bits of code that allows this to work (though the volume of code removed won’t be huge)