There is a way to get genuine help from a Linux forum.
Say “Fuck this, I’m going back to Windows”.
I guess you could say Linux fanboys’ silliness is…
…terminal.
I swear it feels like for a lot of the things I do on Linux there’s a GUI app for it, but then if I wanna do something as basic as adjust my fan speed I gotta use the freaking terminal.
Like it’s always at the worst possible time.
Edit: I’ve installed a distro on my gaming PC that I really liked, used it on my laptop. Sensors and fans were fully supported. Did not work at all on my PC so I told it to fuck off. It’s just too much of a pain to set up.
I prefer using my scripts, but I understand everyone isn’t insane.
I’ve noticed over the years a LOT of Linux users do no have their system sensors / CPUs setup properly. Mostly missing fan information, missing / incorrect sensors and most importantly improper AMD CPU PSTATE and governors. For example, the past few years I’ve had to ensure I had correct kernel drivers and boot kernels parameters for my AMD 5950x to properly use the correct governor and idle at 500mhz and for correct sensor information and control for my viii dark hero MB.
Thanks for this, I was wondering why Linux was using more power (on my UPS) compared to Windows.
I just added amd_pstate=passive
to grub and it brought it down ~15 watts, there’s other options but I believe they require kernel 6.3 or higher. More info here.
Also I was using this before but for other people, if your it87 based sensors aren’t showing up, frankcrawford maintains an updated it87 module.
Not sure if you’re being sarcastic or serious. I’ve been using computers for decades and not once adjusted fan speeds, so that function doesn’t seem very basic to me.
When building a system yourself, setting up a custom curve is how you get the best balance between cooling and noise.
I try to choose motherboards that support doing that in the bios, so I never have to worry about it on the OS level.
Fan curves are easy. Set them to always run at 100% and put on a noise canceling headset.
There’s coreCTRL for AMD and apparently nvidia-setting for Nvidia?
AMD GPUs got more tools due to them being open source, while Nvidia’s isn’t and you are beholden to Nvidia bothering to implement support, which they often don’t.
Also, idk if I would call fan curves that basic, haha. For the vast majority the default curve is sufficient.
This is part of the reason I haven’t gone back to Linux for my gaming PC. I had zero desire to try to set a fan curve in the terminal.
Who need GUI apps when you can do these things on CLI:
- view image:
imcat my-image.png
- watch video, even YouTube:
mpv --vo=tct "https://youtube.com/watch?v=BBJa32lCaaY"
- browse the web using modern Firefox engine:
browsh
- listen to your Spotify playlists:
spt play --name "Your Playlist" --playlist --random
and perhaps many more I’m not currently aware of…
While this is not a serious post I’m going to take it seriously, so here are some of the reasons:
Nobody can easily remember the precise file name and if you don’t get the first letters right you’re screwed(did I mention capital letters matter?)
Wtf is --vo=tct? No sane person is remembering all of that (same goes for the rest 10000 parameters and options)
Again, waaayyy too many parameters, who remembers their playlist name? There is no autocomplete here, you’re on your sad own in your sad little room with your sad little feelings, because there’s no one there to tell you the song’s precise name, because computers are assholes and don’t hate you.
So why GUIs? Because they make computers seem like friendly fellas which actually care about you and give you options, tell you the available functions(without deciphering a 50 pages manual if done well)
If you take it seriously, then at least your complaints should be reasonable, not meme-worthy.
Autocomplete is a standard feature in CLI nowadays, so no need to remember everything.
And parameters usually have names chosen to make the most sense and to be memorable (e.g. vo
= video output).
Serious person here.
Can autocomplete fill in a YouTube URL or Spotify playlist name? Can I browse the list of what’s available and filter, drill down, poke around according to my whimsy?
Or if I’m accessing a local file, how do I find that one video of my cat named VID-004326.MP4
?
Can I autocomplete the parameters themselves, which are betimes lengthy and unwieldy to type out?
Even if it’s possible, and I’ve mastered every arcane parameter necessary to do it, is it really faster / more convenient than doing it through a GUI?
Maybe there are good answers to the above questions—I don’t know and would love to find out—but they and many more like them are surely reasonable and far from meme-worthy, or else I’m missing something huge.
Here is an alternative Piped link(s): https://piped.video/watch?v=BBJa32lCaaY
Piped is a privacy-respecting open-source alternative frontend to YouTube.
I’m open-source, check me out at GitHub.
Imcat is awesome, Debian and had a news reader with the same name.
MPV refuses to play any YouTube for me I suspect it has something to do with their new restrictions on YouTube DL.
Browsh looks absolutely magnificent until I actually try to use it, It seems like submitting form pages or maybe JavaScript is broken
You’ can try installing yt-dlp
. That one is still actively maintained. YouTube also actively trying to broke it, so the one available in debian repo might be out of date.
looks like it is using DLP backend, didn’t read the whole error
[ytdl_hook] ERROR: [youtube] BBJa32lCaaY: Unable to extract uploader id; please report this issue on https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using yt-dlp -U
[ytdl_hook] youtube-dl failed: unexpected error occurred
Failed to recognize file format.
Let’s hope youtube hasn’t finally ground the project permanently
And remember kids, if it is a command, you can automate it and never do it again.
Exactly! Takes so much of the pain away. And you know what would be really useful? If those scripts were accessible easily through simple buttons or sliders on which you could click, or something like along those lines.
For basic functionality I agree, but I don’t think any dev would put the time and effort to implement buttons (much less pipe into another totally different software) for my extremely specific use cases. In the command line I’m presented with a toolset where I can do so myself.