The Linux Thread - The Autist's OS of Choice

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
Okay but, what if, all the retardation in Windows stems not from deliberate malice but from mass retardation of it's employees, and the reason systemd is so shit is not because Poettering does it out of deliberate malice, but because he's simply retarded? Have you ever thought about that? Hmm? No? Thought so.
Poettering's systemd is an attempt to play Saruman to Microsoft's Sauron. He has gazed into Mordor Windows and seen how everything is object orientated and has a centralised OO registry and is trying to turn Isenguard Linux into that.

The problem is that Linux never grew up with that. I actually prefer the Windows approach but everybody's heard the old joke about "you can't get there from here."

systemd.gif

I don't think it's malice, though, fwiw. I think the goals are sincere.
 
Poettering's systemd is an attempt to play Saruman to Microsoft's Sauron. He has gazed into Mordor Windows and seen how everything is object orientated and has a centralised OO registry and is trying to turn Isenguard Linux into that.

The problem is that Linux never grew up with that. I actually prefer the Windows approach but everybody's heard the old joke about "you can't get there from here."

View attachment 8184659

I don't think it's malice, though, fwiw. I think the goals are sincere.
The Windows approach may have been fine during the times of Ballmer and white engineers working on the OS. There was certainly no large-scale complaining. The downside of it is, once the rot sets in and your system is contaminated with brown hands, you cannot put the genie back in the bottle by changing some parts of your system because it's now a monolith. In the case of Linux, the good times aren't even around to attempt this in earnest. The competent people aren't there and the "system daemon" (that's aping MacOS rather than Windows to begin with) is in the hands of Poetteringers, trannies and the GNOME crowd - most known for WONTFIX, shitting on your pathetic use cases and incredibly autistic, self-serving design implementations.
 
Really dumb question since I'm thinking about doing this to an Android device and things can vary, but do you guys ever tinker with your CPU governor options anymore? I want to get as much battery out of my phone as I can, and I'm running a ROM that lets me mess with kernel stuff.
Thinking about using the "conservative" preset but I might fine-tune things more.
 
Very simple question:

Nobara for gaming? Yes or no?

Short term: Yes
Long term: No.

Yes, in that Nobara will get you up and running with the latest and greatest software, play all your games and emulators, and it’s able to do so without many issues.

No in that it’s a Fedora rebuild and the overwhelming majority of home consumer software (ie proprietary stuff that Windows developers ported to Linux) are built for Debian/Ubuntu clones, and also how Fedora is flirting with removing all 32 bit libraries still in their repositories which would bork Steam horribly.

TLDR: Mint’s good enough for gaming. Anything else is adequate but you’d need to have some acumen in manual troubleshooting
 

Got recommended this. The first half is just seething about all the things he hates about windows.

Really, I haven't cared much about linux potentially becoming a majority, or even just less of a minority of the desktop marketshare for a while.

But it does make me happy every time I see news about microsofts next big idea. Forcing AI integration? Plans to remove local accounts? Forcing onedrive, and scanning your users data? Large ammounts of indian vibe code?

Not because I think it will drive users to linux. It seems like barely anyone actually gets bothered enough to make the change. I like that the type of niggercattle that are fine with continuing to use their shit, have to deal with their changes. That a company showing you they don't care about you the user, they only want to squeeze you dry of every cent they can get from the data you give them.

If people are fine with using that companies software, I think they deserve to suffer. If they move to linux, thats cool, but I'm happy either way.
 
Sometimes, it's because you have no other choice than to use Windows because of the type of work you do on your computer and the type of software you need for it. You also have other alternatives to Windows that aren't Linux that could be a better fit, however they facilitate buying new hardware, so people may, again, be stuck with Windows.

Though from what I've seen the people that refuse to move also refuse to try and do anything to make their Windows experience less shit. Most people just want to complain and do nothing to make their lives better.

WinUtil is the simplest way to make Windows suck less, but even that is too much effort for people to do.
1763517711150.png
Even if there's a basic bitch description of how to run it with individual steps listed. Remember: people who bitch about Windows being shit and glorifying Linux can't even do these steps. Left click (copy launch command), right click (on the start menu button), left click (on the terminal option), left click (on the UAC prompt), right click (to paste the launch command), Enter. Get a simple GUI to fix things up. That's the level of nigger cattle we're talking about.

Sorry, it's too much effort for them to even look information about utilities like this up. That's how useless these people are, they'll have the energy to create entire articles, forum posts and YouTube videos to bitch and moan, but won't do a rudimentary Google search to see if they could make things a little better for themselves now. Just assume that oh well, Windows is unfixable, I cannot do anything about it, Linux is the only way to save me, but at the same time I'll refuse to switch to any available distro like Mint and wait for an eternity for Valve to release SteamOS or some other excuse.

In the end these people would be incapable of even preparing a boot USB and launching from it, that is way above their skill level and the ability to learn new things. They don't have to suffer, they have all the options to not suffer at any moment, but they're too stupid for that. It goes beyond people willingly staying on Windows, that's just the surface symptom that tech enthusiasts see, blind to the reality that the average Windows user is dumber than their definition of dumb. There is no saving them, they're too stupid to live.
 
Speaking of stupid, are Windows users really this dumb?
2025-11-18_18-35.png
Good to see that the "curl X | sudo bash" malware vector works for Windows as well.
 
do you guys ever tinker with your CPU governor options anymore
Last time I did was the Nexus 5. I messed around with it on my S7 Edge that followed it, but I did not get superior results. Haven't bothered since. I try keep my phone dumb these days.
 
Steam machine getting fsr4 even if it's a worse implementation (~20% drop in performance compared to fsr 4 on a rdna 4 card and worse fidelity) is at least somewhat promising. It definitely a worthy tradeoff over using fsr 3.1.
Since AMD split RDNA 1/2 and RDNA 3/4 into their own drivers (causing a lot of screeching in the process), and they "leaked" the INT8 FSR4 code, and they have a lot of RDNA 3/3.5 iGPUs to support, it's likely that FSR4 ML-based upscaling will be officially released for RDNA3 products. Maybe before Steam Machine launches.

On the other hand, FSR "Redstone" will be RX 9000 only at launch.
 
The only "alternative" implementation I can think of is OSS, which was dead for a while now

I'm digging backward through highlights. Just wanted to point out the story about OSS.

When Linux was first rising to prominence in the early 1990s (i.e. the Softlanding Linux System days, early Debian, proto-Slackware, etc), there was only one sound card that everyone using Linux cared about: the Creative Sound Blaster 16. Drivers became available quickly, sound quality was allegedly excellent, this led to more people coming along to make drivers for other cards that "emulated" Sound Blasters. All these projects agglomerated together until they eventually morphed into the Open Sound System. No longer limited to Sound Blasters or Sound Blaster compatible, there was now an entire team writing up drivers for sound cards. They made 3 versions that were all libre, and it was "de facto" on all Unix-like environments from every Linux distribution at the time to the BSDs to Solaris and everything else in between.

I think it was 2002, the maintainers of the OSS project decided to make OSSv4 proprietary software. That pissed off a lot of people, so a solution had to be made. The BSD and Solaris people decided "okay, we'll pick up where OSSv3 left off," and that's what powers all audio on the BSDs and commercial Unices like Solaris, HP-UX, AIX, and so on (a touch reductionist; each Unix-like OS does shit differently on some level, but they still contain an assload of OSSv3 code along with a hodgepodge of native stuff). Linux, for whatever reason, went in the polar opposite direction and decided to completely fucking rewrite the sound implementation. This gave us the "Advanced" Linux Sound Architecture... aka the ALSA that we all know, love, and loathe to this day. While ALSA is more than serviceable today, it should be remembered that ALSA in its infancy was fucking abysmal. The API was poorly documented at the time, tons of features from OSS were missing for a good long while (i.e. audio mixing), audio drivers had to be completely fucking rewritten because the API, ABI, or whatever the proper abbreviation is weren't compatible with whatever OSS had at the time. There was a nasty stretch of time in the mid-to-late 2000s where it was a real crapshoot as to whether or not your sound card (be it a dedicated DAC or your motherboard's built-in audio) would work properly. Tools like Jack and PulseAudio came to the "rescue," they solved tons of problems, but they also made tons of problems too.

I'm rather ambivalent on PipeWire as a replacement for tools like Jack and PulseAudio. I've been living with PipeWire for about a year since deciding to daily drive Linux again last year, and I honestly don't notice any conceivable difference. The last time I daily drove Linux like this was back in high school like 15 years ago during the Ubuntu 10.04-12.04 days, I'm running vastly different hardware now than I had back then, but there's one issue that persists to this day that won't ever fucking go away no matter what I try. It's an issue that PipeWire's fundamentally incapable of solving the same way Jack and PulseAudio failed: sound's bloody quiet innit mate?

What I mean is that both 15 years ago and today, the built-in sound on my motherboard is too fucking quiet, and it's an ALSA-specific issue that software layers like Jack, PulseAudio, and PipeWire all basically slap duct tape onto and say "job's done." I need to to boost my shit on Linux to like 40% to achieve what would easily be 20% on Windows. I know it's the same issue because the OEM sound on my old HP tower's motherboard and my current motherboard are recognised as some variation of snd_hda_intel, and the codec is the same damn thing: some Realtek garbage that has eleventy billion fucking variations split across dozens of OEMs. Technically, ALSA has the drivers for all of them. The problem is that ALSA always defaults to a shitty generic driver that just cuts off 27-30dB from the volume I'm capable of.

You can do all sorts of shit with hdajackretask to apply boot overrides that swaps your front sound with the rear sound jacks to get the gain to work better, you can run alsamixer -c 1 to unmute and boost all other channels to 100% while keeping the master volume relatively low, you can set alsa-base.conf to whatever OEM you have like options snd-hda-intel model=auto, reboot your PC, and pray like hell it works only to be bitterly disappointed when it doesn't. It's all one gigantic exercise in frustration, and it persists regardless of whether it's jack, PulseAudio, PipeWire, or whatever other newfangled thing Linux developers will adopt when PipeWire gets too tedious to maintain 10 years from now. It just fucking sucks, and you're only able to put so much mustard and hot sauce on a fucking turd sandwich before you gotta shove the thing down your gullet.

The only real solutions I have are suboptimal no matter which way I slice it:

a) Live with this suboptimal experience from my on-board sound as I have it now, with various tweaks and fixes that help but don't go the full nine yards.

b) Buy a new sound card, and pray that I actually did my research properly when I part with cash.

c) Use headphones and succumb to sweaty ear plague... because that's the #1 thing I've seen across LinuxQuestions, Yahoo Answers, Quora, and even Facebook. "Oh too bad for you mate, I use headphones and it's good good enough for me."

d) Roll the dice and see if I'm doing PipeWire wrong, switch to PulseAudio to see if that changes anything, git gud at learning Jack and its intricacies, or some other activity that puts my nose to the grindstone and still probably won't accomplish shit.

***

TLDR: Sound on Linux is garbo because ALSA itself was shit 20+ years ago and it's still shit now. You can only do so much with sound servers that run atop ALSA because ALSA itself is an unstable foundation. Oh and OSSv4 was later relicensed as free software, but no one gave a shit anymore because they all moved on.
 
Roll the dice and see if I'm doing PipeWire wrong, switch to PulseAudio to see if that changes anything, git gud at learning Jack and its intricacies, or some other activity that puts my nose to the grindstone and still probably won't accomplish shit
or you can just cut out the middle man and use alsa.

are you doing anything that actually needs pipewire, pulse or jack?
 
are you doing anything that actually needs pipewire, pulse or jack?

I'm not entirely sure to be blunt. I just watch YouTube, listen to local music, watch local videos, play vidya, and so on. I've only gotten this deep in the weeds and not knowing entirely where I am because I wanna fix that goddamn -27-30dB issue on the rear audio jack of my motherboard. I don't know anything about them other than "okay, apparently I can attempt to fix issue X by using audio server Y. Here's how i'm supposed to do it. Let's see if it works (9/10 it fucking doesn't)."

Also, I'm 90% sure that the issue I'm having is with ALSA. How would running ALSA directly help?
 
I'm not entirely sure to be blunt. I just watch YouTube, listen to local music, watch local videos, play vidya, and so on. I've only gotten this deep in the weeds and not knowing entirely where I am because I wanna fix that goddamn -27-30dB issue on the rear audio jack of my motherboard. I don't know anything about them other than "okay, apparently I can attempt to fix issue X by using audio server Y. Here's how i'm supposed to do it. Let's see if it works (9/10 it fucking doesn't)."

Also, I'm 90% sure that the issue I'm having is with ALSA. How would running ALSA directly help?
I won't say it will help. Because I don't know for sure. But you can just adjust things directly in alsa, which could possibly fix it.

Otherwise, I think it would be worth just trying without the extra layer slapped on top. At least in my use, I get absolutely no benefit from using pulseaudio, and pipewire. In fact, it's basically the opposite, when I have had audio problems on linux, it was while I was using either of those. But also I don't have to have a userland client running, that picks up the audio device, or makes it's own fake version of one. And deal with whatever extra nonsense it's doing on top of alsa. For me the set up to have alsa work, is put my user into the audio group. and add a file in either /etc/asound.conf or ~/.asoundrc to point to the card you want to use if it's not using the right one by default.

4 Library configuration


that and installing alsa-utils to get amixer to set my key-binds to, and alsamixer.

IDK in my time using all three. I have never ran into anything that made me think pulse or pipewire gave me anything extra. At least as far as audio goes. Neither are easier to configure, if anything they make it more confusing, at least with modern alsa. The only time I chose to use either, is if I'm currently using a program often that has some kind of hard requirement on a pulse client (which is an automatic negative in my book against that project). Or for wayland, if I want to record my screen, then obviously you will have to use pipewire.
 

It helps to laugh through the pain.

I won't say it will help. Because I don't know for sure. But you can just adjust things directly in alsa, which could possibly fix it.

Here's the rundown of my specific hardware situation. Bear in mind that I'm still daily driving Fedora 43 Workstation (i.e. GNOME Shell) on a portable hard drive. Whenever I decide to boot back into Linux Mint, I'll probably see what I can do.

I'm deliberately challenging myself to live with GNOME Shell, Wayland, and systemd for a month to see if it's tolerable. I know it's entirely self-inflicted, fie upon me for running Poetterware, I know better, yadda yadda yadda. I specifically wanna tell the Poetterware simps "I lived with your crap for a month straight, and I can precisely detail why your shit sucks on my hardware." I really miss Artix-OpenRC with Cinnamon

  1. The audio codec for my motherboard's sound is extremely common for OEMs and other hardware vendors: it's a variation of snd_hda_intel using some Realtek thing.

  2. I specifically have to set up an alsa-base.conf file to correctly order all my audio devices, identify them, and load the correct implementation for the on-board sound.

  3. Windows does a ton of extra shit that ALSA does not do. Mostly niceties like hardware boost, EQ, and stuff along those lines.

  4. For the rear motherboard audio jack, ALSA deliberately cuts 25dB-30dB because the default setting is extremely conservative. This is why shit's barely audible for me on a fresh install of any Linux distro.

  5. ALSA, for whatever reason, doesn't arbitrarily cut 25-30dB from my front headphone jack.

  6. So the "fix" is to use hdajackretask(once I correctly identify it) and apply a boot override that treats my motherboard's rear audio out as "Headphones" instead of "Line Out."

  7. This actually does work, but it's basically a bandage over an axe wound. Most desktop environments have piss-poor volume controls that are hideously imprecise, but GNOME Shell takes the fucking cake. I need to resort to alsamixer -c whatever to control my master volume because 20% in GNOME Shell damn sure ain't the same as 20% in alsamixer

  8. This is basically as good as it gets for me on my current hardware without buying a new sound card altogether.

It doesn't matter if it's PipeWire, PulseAudio, or Jack that I'm fiddling with because the real problem for my specific hardware is ALSA.
 
Last edited:
I'm deliberately challenging myself to live with GNOME Shell, Wayland, and systemd for a month to see if it's tolerable. I know it's entirely self-inflicted, fie upon me for running Poetterware, I know better, yadda yadda yadda. I specifically wanna tell the Poetterware simps "I lived with your crap for a month straight, and I can precisely detail why your shit sucks on my hardware." I really miss Artix-OpenRC with Cinnamon
But that's incredibly unfair to systemd (and wayland I guess, but I'm less willing to die on that hill). GNOME is utterly horrid, but systemd genuinely does work very well. And while Wayland is missing a lot of features still, on KDE it's perfectly pleasant to use as long as you're not screensharing. You're going to conclude all three of these things suck, when really it's just GNOME (and to a lesser extent Wayland) that sucks
 
Back
Top Bottom