The Linux Thread - The Autist's OS of Choice

Only exception are manufacturers like Logitech which usually offer insane battery life, mostly because they deal in volume massive enough that they've got their own silicon or can afford better engineers who actually know how to program a minimalist MCU.
That's why I still use their mice even though their actual software is atrocious and often installs or updates itself without permission if you don't do everything possible to stop it from doing that. My current mouse batteries are at something like 10% after two years of nearly constant use.

But to get it working on Linux with the generic drivers took two commands from the terminal. Thanks to all sorts of unwanted (and uninstalled) Logitech crap, I had to edit something like a dozen lines of the registry because despite having a setting in the control panel for reversing the scroll direction, it was continuously overruling that and setting it back the wrong way.

This should have been a one line edit but thanks to Logitech software taking a dump in the registry, there were many places it could have been. So I just carpet bombed the registry with repeated edits until it behaved itself, crossing my fingers it wouldn't mess anything else up.
 
Linus Torvalds has given a shoutout to Asahi Linux.
On a personal note, the most interesting part here is that I did the
release (and am writing this) on an arm64 laptop. It's something I've
been waiting for for a _loong_ time, and it's finally reality, thanks
to the Asahi team. We've had arm64 hardware around running Linux for a
long time, but none of it has really been usable as a development
platform until now.

It's the third time I'm using Apple hardware for Linux development - I
did it many years ago for powerpc development on a ppc970 machine.
And then a decade+ ago when the Macbook Air was the only real
thin-and-lite around. And now as an arm64 platform.

Not that I've used it for any real work, I literally have only been
doing test builds and boots and now the actual release tagging. But
I'm trying to make sure that the next time I travel, I can travel with
this as a laptop and finally dogfooding the arm64 side too.

Hector Martin, expert on making things up about his living friend Byuu, must be ecstatic.
 
1659458886104.png


Is he right?
 
I am not an internals guy. But he's right. You can confirm the fractional scaling thing by the dire warnings (in gnome at least) that using fractional values will fuck with performance. The obsession with security-your-nose-off-to-spite-your-face has been a day 1 thing with Wayland. It mostly all checks out.
 
I've become rather attached to Manjaro (KDE flavor) for daily use. It's Arch, but with the voodoo hidden behind GUIs and is the only rolling release I've used that doesn't shit itself at least once a year.

(I've cursed myself now, haven't I?)
 
Which distro do you guys recommend for beginners? I'm looking at Linux Mint & Ubuntu and either one seem to be my top choices for my first distro.
Mint because its free from ubuntu's retardation, yet benefits from ubuntu/debian's large install space. If ANY instructions exist for linux, you can bet they work on mint.

I'll also throw in Manjero is nice, but I just like KDE plasma. It also mostly just works, but can occasionally have some arch weirdness. Kubuntu is the ubuntu base with KDE plasma and is quite nice.
 
Is he right?
No. That's a really extreme conclusion to reach from the examples he gives.

"Rendering is totally broken" doesn't follow from some apps stalling from lack of callback. He acknowledges it's fixable, and for 95% of apps that use a framework like gtk or qt it's irrelevant because the code that manages it is in the library.

"integer scaling" is fixable, and is in the process of being fixed.

"overly secure" is the only design decision that can't easily be changed. The only reason X keyloggers haven't been more of an issue is because Linux doesn't have enough of a marketshare for people to bother. It's not a hypothetical problem.

"synchronization" is just strange. It's never going to result in enough overhead to be noticeable even from the perspective of battery power consumption.

There are two main reasons wayland has been so long coming. The first is nvidia refusing to modernize their drivers. The other is because porting to it from X is a massive undertaking. Gnome/gtk got there first because the development was paid for. QT supports wayland, but KDE isn't ready because kwin is maintained by three part time volunteers.
 
  • Informative
Reactions: Churros con Manteca
X has a security extension for untrusted programs, exactly so they couldn't e.g. keylog. This extension is a bit forgotten although it is relatively new compared to some others and was really made for a networked X that'd run programs off other computers. That said, I do use it (together with namespace sandboxing) and it works fine for it's intent. The problem with the hypothetical X keylogger is a bit overblown as-is IMO. Every modern browser sandboxes e.g. javascript away from that kind of access and if any malicious code can escape that sandbox and gain that much control over the parent process you've got bigger problems than a keylogger. Same with any other untrusted program- if you don't trust them, why do you run them unsecured to begin with? They can do far nastier stuff than log your keyboard input. Don't let people bedazzle you: executing code from random servers all over the world was and is a mistake. That's the attack vector for a normal end user and the very concept is faulty.

Maybe tranny janny distro maintainers should focus on building distros that aren't broken by default instead of playing politics and waiting for the next shiny troon wunderwaffe to solve all their problems.

Wayland is dead in the water, it came up often in this thread and I keep saying the same thing, so I'll just quote myself:
Wayland is around now for so long and it doesn't catch on. It's dead in the water. The sooner people realize this the sooner cleaning up X can begin. All these projects that say "We'll build [thing] from scratch and it'll be better without all the complexity" don't realize that all that complexity and the edge cases are important and ended up in the source of the original project for a reason and if you end up seeking to be just as usable, your project will just end up doing the same and looking the same. Either that or outsource the complexity to external projects, making the situation often even worse because now you've effectively abolished universally valid standards. (What wayland does)

Linus Torvalds has given a shoutout to Asahi Linux.
I used to be similarily excited about ARM as actual desktop system. I'm not anymore. At this point it has all the same problems the amd64 world has and the high end ARMs and low end x86s aren't far apart each other on metrics like power consumption and performance, with the difference that shit on x86 actually works and isn't a compatibility nightmare because there are no standards and ARM SoC manufacturers don't give a shit about linux. (besides their custom hacked 3-4.x kernels for the smartphone of the week)
 
So, I just moved from Linux Mint to Fedora in order to try gpu passthrough. I got closer to getting it working, but still not getting drivers to install.

Anyways, thats not why I'm posting.

2 questions I have to ask.

1) I think I read that if I host a partition on my drive called /home, that is where my user documents, downloads, ect will be located automatically. Is this true, as I've setup a partition with fedora that way. If so, handy for being able to reinstall os's without losing data or having to move it first.

2) if I let my computer idle, it dims the screen off but nothing I do gets it to wake up. I have to fully power the machine off to be able to use it again.

How would I go about finding what the cause is? Though I already suspect its the drivers I've used for gpu passthrough.
 
So, I just moved from Linux Mint to Fedora in order to try gpu passthrough. I got closer to getting it working, but still not getting drivers to install.

Anyways, thats not why I'm posting.

2 questions I have to ask.

1) I think I read that if I host a partition on my drive called /home, that is where my user documents, downloads, ect will be located automatically. Is this true, as I've setup a partition with fedora that way. If so, handy for being able to reinstall os's without losing data or having to move it first.

2) if I let my computer idle, it dims the screen off but nothing I do gets it to wake up. I have to fully power the machine off to be able to use it again.

How would I go about finding what the cause is? Though I already suspect its the drivers I've used for gpu passthrough.
1. Yes, your /home contains all your documents, settings, downloads etc. This does make it easier to switch distros down the line. You just have to remember to not repartition when you install a new distro.

2. With a GPU passthrough setup, the passed GPU is not available to Linux to use. So the passthrough shouldn’t be affecting this. It could be some kernel bug with your Linux GPU (Intel iGPUs are notorious for these, I have struggled with bugs with Intel iGPUs for years with rare relief). I would recommend just disabling the screen blanking and turn off the monitor yourself when you aren’t using it. This is what I do, but electricity is cheap here so I don’t have to sweat forgetting to turn it off.
 
2) if I let my computer idle, it dims the screen off but nothing I do gets it to wake up. I have to fully power the machine off to be able to use it again.

How would I go about finding what the cause is? Though I already suspect its the drivers I've used for gpu passthrough.
Assuming this is NVIDIA you probably ran into one of those bugs where the drivers aren't picking up the kernel callback on keyboard input correctly.

Just disable power management at every level you can. I wouldn't fight it.
 
2) if I let my computer idle, it dims the screen off but nothing I do gets it to wake up. I have to fully power the machine off to be able to use it again.

How would I go about finding what the cause is? Though I already suspect its the drivers I've used for gpu passthrough.

You can read through previous events with the journalctl utility. There are also (usually) text dumps you can browse in /var/log/.

The first thing I'd do is see if you can ping the machine when trying to wake it from sleep. If it's not awake enough to respond, it's probably not awake enough to log anything that will help.

My best off the wall guess is if it worked with mint but not fedora, it's going to be because of differences in the firmware blobs the distros ship. Running "dmesg | grep firmware" might be helpful.
 
Back