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
...how? why? That's literally never a problem on Mint, so how come Fedora can't handle it?
To be fair, I do this in any situation that involves dynamically compiled out-of-tree software (OpenZFS comes to mind) regardless of distro. Maybe Mint handles it better, I don't know. I hope so. I've abruptly booted into 640x480 safemode enough times that I've found it easier to just freeze the kernel version and not worry about it again.
 
Bash:
$ lsblk
NAME        MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda           8:0    0  12.7T  0 disk /mnt/dsk/1
sdb           8:16   0  12.7T  0 disk /mnt/dsk/3
sdc           8:32   0  14.6T  0 disk
└─sdc1        8:33   0  14.6T  0 part /mnt/dsk/5
sdd           8:48   0  14.6T  0 disk
└─sdd1        8:49   0  14.6T  0 part /mnt/dsk/6
sde           8:64   0  12.7T  0 disk /mnt/dsk/4
sdf           8:80   0  12.7T  0 disk /mnt/dsk/2
sdg           8:96   0 223.6G  0 disk /mnt/games
sdh           8:112  0 931.5G  0 disk /mnt/backup
sr0          11:0    1  1024M  0 rom 
nvme2n1     259:0    0 238.5G  0 disk
├─nvme2n1p1 259:9    0   100M  0 part
├─nvme2n1p2 259:10   0    16M  0 part
├─nvme2n1p3 259:11   0 237.9G  0 part
└─nvme2n1p4 259:12   0   509M  0 part
nvme0n1     259:1    0 953.9G  0 disk /mnt/wrk
nvme1n1     259:2    0 465.8G  0 disk
├─nvme1n1p1 259:3    0     1G  0 part /boot/efi
└─nvme1n1p2 259:4    0 464.7G  0 part /
cleaned up my drives a little. Looking at the free storage space on my server, I have *just* enough free space in my storage pool that i can take sdc drive offline, reformat it to remove the unneeded partition, then transfer sdd to it and repeat the process. it'll be a very time consuming process, however. I might as well just buy another drive to add to the pool.
 
...how? why? That's literally never a problem on Mint, so how come Fedora can't handle it?

Mint (and all Ubuntu LTS variants by extension) use the LTS releases of the kernel and assorted tooling. Fedora tracks upstream development very closely. Not as quickly as Arch, but much faster than openSUSE Tumbleweed or Debian Sid. Not just the kernel, but also Mesa, Xorg/Wayland, systemd, PipeWire, etc. Highly valuable if you're running cutting-edge hardware (re: an RX 9070 XT in my case), not so much if you have older hardware that can tolerate an LTS kernel.

NVIDIA binary drivers are the odd man out because AMD and Intel already provide FOSS kernel modules and directly contribute to upstream Mesa development. NVIDIA, for better or worse, decided to double and triple down on maintaining their proprietary stack for decades, only recently beginning the slow and painful process of gradually making more and more parts of their driver stack FOSS. I think right now, only the headers are open-source, but I digress.

Point is: until NVIDIA decides to stop giving Linus Torvalds a reason to flip them off, you'll always need some semblance of a hackish workaround to maintain stability. You'd do similar shit on Arch where you pin a bunch of stuff in Pacman for the NVIDIA drivers to make sure that a kernel, Wayland, Xorg, Mesa, or whatever update doesn't bork your system when you run sudo pacman -Syu.

>recommends Fedora to users new to Linux
>proceeds to mention arcane rituals needed to keep it working

Hey man, I did say that Mint >>> Fedora for normie's first Linux distro, I've said it like a billion times in this thread by now, and I told @Sprocket as much before writing up the stuff about Fedora. It was meant as "hey, if you wanna keep using Fedora, here's how you do it to minimise your pain." Sprocket himself literally chose it of his own volition because his grandson uses it. Not my place to say "drop Fedora altogether, use Mint instead" if he voluntarily chose to approach Fedora since someone with actual proximity to him is already using it. My biases ain't the same as his grandson, but I'm sympathetic enough to help him recover some of the sunken cost.

Also kinda irrelevant, more of historical trivia than anything else: Fedora used to be the distro that Linux For Dummies used to ship out in the 2000s (alongside Knoppix for hardware detection purposes). It's not unprecedented for newcomers from Windows to give Fedora a fair shake. One could argue that Fedora is more painful to use as a fresh newcomer to Linux, but not insurmountable if the user in question has the wherewithal roll up their sleeves and fiddle with their system. Yeah, I know: a lot of this shit ain't pleasant to deal with. Sprocket said as much when he was talking about losing his hair with Fedora the first time around.

But I also detest this mentality where people in the Linux space just automatically assume that Windows users are complete and total retards who need all the painful parts abstracted or otherwise hidden away, clearly defined and idiot-proofed ways of doing X/Y/Z, guardrails upon guardrails, blah blah blah. Not to talk shit about abstractions and generally idiot-proofing Linux to make sure you don't bork your shit by following old StackOverflow comments from 2013, but like... learning should also be part of the process.

"Terminal" is scary when you're a brand new Linux user, I'm 100% sympathetic to the anxiety that a blinking cursor with green or white text poses to a newcomer. But I also won't infantilise someone by telling them "stick to the GUI tools" if I know those GUI tools aren't 100% idiot proof. You know what's worse than touching the terminal as a newcomer? Touching a graphical tool, having some success with it, and then the tool shits the bed without so much as an error code or a log output. Just "oops, we sharted, don't know why, figure it out mate." That's why I explained how to set up Fedora without talking down to him like he's some invalid tard.

Linux Mint takes the cake because almost everything in that distro is idiot proof. Your system updater is clearly defined, and properly tells you when to reboot. You have the driver manager that specifically outlines what NVIDIA binary driver you need for your specific graphics card, plus a one-click installer to get it going if it wasn't already auto-installed on your first boot. You can comfortably do just about anything in Linux Mint graphically across all its variants, and it's a smooth and seamless experience. But not all distributions come even 1/10th as close to Linux Mint in this department. For better or worse, UX is fucking awful on Linux as a general rule of thumb. There are excellent programs with wonderful UX, but they're diamonds in the rough.

If Sprocket wants to learn Linux Mint over Fedora because it's too much too soon, that's his call to make. As it stands, he wanted to make Fedora work, and apparently it's working for him now since NVIDIA drivers are (seemingly) correctly installed and his Steam games work well enough.
 
Last edited:
You should also add:

conv=fsync bs=1048576
You are very confidently wrong here. Just tested it and it's faster without. I guess in current GLIBC/kernel even a sync afterwards is unnecessary.

Code:
 # echo start ; date '+%s' ; time dd if=KF_JAM.zip of=/dev/sdc status=progress ; echo presync ; date '+%s' ; sync ; echo next ; date '+%s' ; time dd if=KF_JAM.zip of=/dev/sdc status=progress bs=1M conv=fsync
start
1767924323
1380536832 bytes (1.4 GB, 1.3 GiB) copied, 2 s, 690 MB/s
2724464+1 records in
2724464+1 records out
1394925749 bytes (1.4 GB, 1.3 GiB) copied, 843.568 s, 1.7 MB/s

real    14m3.569s
user    0m0.228s
sys     0m2.411s
presync
1767925167
next
1767925167
1330+1 records in
1330+1 records out
1394925749 bytes (1.4 GB, 1.3 GiB) copied, 994.1 s, 1.4 MB/s

real    16m34.101s
user    0m0.000s
sys     0m1.772s


And from our boy cat:

Code:
real    15m39.213s
user    0m0.000s
sys     0m1.368s

Right in the middle.

If writing an iso to a flash drive takes more than 2 minutes, spoiler alert, it’s not picking the correct block size.

1.4GB is a pretty normal size for a live image, but LOL. To be fair, here I am using my "old faithful" USB2 that's been through a wash and still not failed a bit yet, so that's pathological.
 
Last edited:
I have *just* enough free space in my storage pool that i can take sdc drive offline, reformat it to remove the unneeded partition, then transfer sdd to it and repeat the process. it'll be a very time consuming process, however. I might as well just buy another drive to add to the pool.
The only case under which I would not use partitions would be if I was using full disk encryption with LUKSv2 etc. You are not giving up any substantial amount of disk space. Why give up the ability to resize partitions and create new ones should you need to alter the actual use of a physical disk?
 
The only case under which I would not use partitions would be if I was using full disk encryption with LUKSv2 etc. You are not giving up any substantial amount of disk space. Why give up the ability to resize partitions and create new ones should you need to alter the actual use of a physical disk?
in what universe will i need to partiton a 14TB drive that is one of six drives put into a mergerfs pool on a server with currently 11 different drives installed (6x hdd, 2 sata ssds and 3x nvme ssds), and two of the drives (the sata ssds) not really being used?
And I still have room for two more 3.5" drives and i can probably stick another 2.5" drive somewhere
 
in what universe will i need to partiton a 14TB drive that is one of six drives put into a mergerfs pool on a server with currently 11 different drives installed (6x hdd, 2 sata ssds and 3x nvme ssds), and two of the drives (the sata ssds) not really being used?
And I still have room for two more 3.5" drives and i can probably stick another 2.5" drive somewhere
Just of the top of my head, if you were to decide that you needed another partition to shift OS's, or to have a fully separate partition for backup, or if you were to (gradually) move towards some sort of RAID/XFS setup that might give you some safety for the data you have stored without buying another six drives.

I'm sure it's worth eliminating that possibility to save a few kilobytes of HD space.
 
Just of the top of my head, if you were to decide that you needed another partition to shift OS's, or to have a fully separate partition for backup, or if you were to (gradually) move towards some sort of RAID/XFS setup that might give you some safety for the data you have stored without buying another six drives.

I'm sure it's worth eliminating that possibility to save a few kilobytes of HD space.
Or you can drop the whole disk into LVM unpartitioned and decide how you're going to use it later. The only reason I partition an LVM volume is if I want Microsoft to be able to read that drive.
 
Just of the top of my head, if you were to decide that you needed another partition to shift OS's, or to have a fully separate partition for backup, or if you were to (gradually) move towards some sort of RAID/XFS setup that might give you some safety for the data you have stored without buying another six drives.

I'm sure it's worth eliminating that possibility to save a few kilobytes of HD space.
none of those conditions will be applicable due to the nature of the server.

Everything that absolutely needs to be backed up is like 250gb at most. everything else *can* be re-downloaded, even if it takes a long time to do so. I'd probably take the opportunity to purge series and movies I have no interest in re-downloading.
 
Last edited:
Welcome to the fold, @Sprocket . A shame you've had issues with Fedora, but Linux Mint is just fine as well. StackOverflow and forums are your friend when it comes to troubleshooting issues; I'd also suggest several clean installs just to not be scared of breaking shit, but also to better understand what goes on with the distro, from beginning to end.

Also,


Zorin OS is also very comfy and noob-friendly, from what I've seen. Practically a drop-in replacement of Windoze.
 
Last edited:
As it stands, he wanted to make Fedora work
That's exactly it. As much I'm swearing like a pirate and keeping an eye on my blood pressure, when shit goes sideways that's when you learn - and you've been extremely helpful with that. I was going to jump ship and switch to mint, but then I figured if I hit that abort button, I won't learn anything.
 
Zorin OS is also very comfy and noob-friendly, from what I've seen. Practically a drop-in replacement of Windoze.
i always wonder what people mean by drop in replacement for windows
does it use a c:/ program files directory and %appdata% and all that
does it copy their settings menu
does it run adobe programs
does it have a taskbar and a start menu
 
I've been seeing videos recommended about Windows sucking and how gamers should go to Bazzite. These people have to realize normies are gonna have one look at the terminal, shit their pants, and want to go back to Windows. It doesn't help that it's immutable so installing applications outside of the bazaar is more difficult. They've got to stop shilling "gaming" distros and just recommend the popular ones that are easily accessible to Windows users like Linux Mint or Zorin.
 
I hate gigabyte motherboards so much you can't fucking believe. I bought a gigabyte motherboard and guess what. First things first the MANUAL that was given was not UPDATED for the motherboard I bought. It told me I had to SCREW in the NVME.. this board did not HAVE nvme screws it only has these weird fake little plastic things, trying to insert them in without help BROKE them easily as there WAY more fragile and honestly ALOT harder to use, My NVME drive is standing with NO screw support. Second thing the PCIE holder is extremely weak, the little clicker half broke off when carefully inserting the GPU. Then it came down to gaming. Which guess what. at first I thought that this was a linux issue but randomly either the ENTIRE COMPUTER would freeze and not come back. or it would GO black and then kick me back out to the home menu like the ENTIRE compositor/window manager DIED. Sometimes it would just go black and not come back. I later learned that this is because gigabytes motherboards are EVEN worse and when they are given the UEFI source code by AMI they add there own "Patches" that make it 1000% more unstable. This is NOT a linux thing but rather the UEFI firmware which im NOT going to blame AMI because This is 10000% a patch made by gigabyte to the code that they receive. Instead its a bug with HOW the UEFI firmware HANDLES amds Cstates and also the PSUS idle current. where it can send TO low of a voltage from my knowledge and cause it to SNAP... causing linux or windows or whatever to break... No im serious and yes this has probally been a issue for their motherboards for YEARS. Turning those off in the Bios FINALLY made it work.


Finally the worst of all I learned that SWITCHING DISPLAYPORT CABLES would break the entire thing. if you put in a new displayport cable into your GPU the vendor UEFI code would NOT bring the display to the monitor ... and you would just get a "No signal" screen on your monitor. And worst of all Linux and im assuming ALSO windows would NOT recieve a power on signal to the monitor so you CANT GET ANYTHING ON YOUR DISPLAY. You want to know the solution .... you have to reset the cmos and then UNPLUG AND THEN REINSERT YOUR GPU INTO THE SLOT and then put in ALL YOUR SETTINGS AGAIN. im not fucking joking THAT IS WHAT YOU HAVE TO DO. Like this is fucking LAWSUIT bad.. Like its fucking ABSURD.. Imagine being a kid who got a prebuilt pc using gigabyte and you plug in a NEW displayport cable. REPLACING YOUR DISPLAYPORT CABLE FORCES YOU TO RESEAT YOUR ENTIRE GPU!!!

What to know something even more funny. Lets take a LOOK at the what might be DECADE old reshared code they use. First things when turning on this motherboard which is late AM4 mind you. You see this if you monitor kicks in fast enough

1767976069225.png
This implys that they are using LEGACY emulation code first thing. As that symbol is a remnant of old VGA REAL mode emulation that obviously my new GPU barely supports.

But you know what. Gigabyte has a HISTORY of making BAD firmware implementations that I don't think many people know about... I just want to share you the HISTORY of gigabytes extremely piss poor firmware.
Gigabyte has for years in what is almost forgotten by PC gamers delivered buggy motherboards/Firmware
During 2011 The world was switching to UEFI. Moving away from legacy bios. This FIRST shift was kind of buggy buy generally it could have gone ALOT worse(https://wiki.osdev.org/Broken_UEFI_implementations). It was not the WORST thing in the world and most boards DID have a smooth transition.

However Gigabyte was one of the "Slow adopters" still using AWARD BIOS FROM THE 1980S.
1767976601609.png
For those who do not know the word "Award Bios" you have definitely seen it. Here

1767976601633.png

To put into perspective how OLD award bios is.
  • Its so OLD that the LAST known version of it still supported MSDOS and used MICROSOFT MASM to compile.
  • its so old that it does not have a SINGLE line of C code, Rather Its ALL assembly.
  • Its so old that it runs in EGA 8x14 mode and uses a bunch of hacks to render that Energy star image.(https://www.youtube.com/watch?v=uAHGKanqO6s)
Its important to know that in 1998 Award software had been merged with Phoenix International and ALL FUTURE copies of award bios would now be known as Phoenix bios and be built to support alot more from the semi ground up. Award was discontinued in 1998...

This means that from 1998-2011 Gigabyte had kept the SAME PIECE OF SOURCE CODE and just kept adding vendor patches to it and refusing to upgrade. Giving consumers a WORSE experience.
But now with Windows 8 wanting users to move to UEFI and the rise of Disks ABOVE 2tbs. Gigabyte was facing a problem. If they wanted to continue and keep up with the trends they would have to FINALLY move from the 1998 award bios that they were holding on and finally bury it and move to something like AMI or Phoenix, This move would BARELY be that expensive and would be LITERAL PENNIES for them.

Instead they decided to KEEP using their copy of Award bios that they got in 1998 and make what they called "Hybrid-EFI" that would run ON TOP of the dying aging bios. What was Hybrid EFI? Well lets read what OSDEV says(https://wiki.osdev.org/Broken_UEFI_implementations#GIGABYTE_Hybrid_EFI)
These motherboards claim to support other os, however it is notpossible to use efibootmgr to write to nvram. Further, fdisk gptpartitioned drives with the standard efi system partition type and allknown good default names will not be able to find a stub kernelimage. Strangely they are able to find the /efi/boot/bootx64.efi imagewhen it is located on a MBR formatted disk (which is how it waspossible to run efibootmgr in the first place). These issues may berelated to issues described here:http://www.rodsbooks.com/gb-hybrid-efi/.

Another commenter adds: "Hybrid EFI" is gigabyte's name forrunning an x64 uefi emulator on top of bios, which does not work atall well. Some boards with Hybrid EFI offer a beta real EFI upgradeas a firmware download, which fixes most of the serious issues, butnot all. Seehttp://www.gigabyte.com/products/product-page.aspx?pid=3979#ov for anexample of such a board. Version F7 is "Hybrid Efi" and doesn't work,U1G is the real thing but is marked beta.
Its literally just a EMULATOR that poorly EMULATES the functions of UEFI.... As such it lead to well ALOT of bugs..
1767977429107.png
(https://www.youtube.com/watch?v=KvI4ZIgTmoI In case you want to see the trainwreck for yourself)
This is LITERALLY JUST AWARD with likely a separate module like system running on top....

And yes that copyright info says 2014.. UP TO 2014.. Although Ive seen motherboards that had support up to 2017!!!!...
1767977559597.png
Yes they did not even BOTHER to update the copyright information, With the previous screenshot saying 2014 and the setup screen saying 2012..

FINALLY in 2013 ALL new gigabyte motherboards would use AMIs UEFI bios. But even that had its downside. Having the UGLIEST UI design you will EVER see that is of course VENDOR coded in by Gigabyte
1767977671919.png
Well.. EVEN if the code is buggy as shit. At least you can't get hacked.
1767977811389.png
1767977853981.png
1767977897114.png
https://www.wired.com/story/gigabyte-motherboard-firmware-backdoor/
oh...
Its important to know that with UEFI, it still manages stuff for the operating system WAY after it has booted up. Never truly going away. If its poorly implemented than the ENTIRE computer will have issues NOT just with the UEFI setup.
Part of the reason WHY the Linux Kernel is so "Huge" is because of FIRMWARE issues that were not properly handled by UEFI. You can find this again
1767979629499.png
and again
1767979698220.png
and again
1767979730022.png
and again
1767979792174.png
and again
1767979834684.png
and you get the point
ALOT of times when Linux has serious issues. Its because of the poorly implemented UEFI implementations(Say that 5 times fast). With Kernel panics for most tried and tested distros they happen for only ONE of two reasons.
  1. Hardware Fault/fail
  2. UEFI firmware implementation issue from the motherboard
When you see someone whose having trouble using linux for the first time there is a VERY good chance its because of a BAD UEFI implementation.
Thank you for this time reading this brief history lesson... Remember FUCK gigabyte.
 

Attachments

  • 1767977817489.png
    1767977817489.png
    321.7 KB · Views: 22
Last edited:
  • Its so OLD that the LAST known version of it still supported MSDOS and used MICROSOFT MASM to compile.
  • its so old that it does not have a SINGLE line of C code, Rather Its ALL assembly.
  • Its so old that it runs in EGA 8x14 mode and uses a bunch of hacks to render that Energy star image.(https://www.youtube.com/watch?v=uAHGKanqO6s)
based

But yes, gigabyte are shit-tier. The only computer of mine that had insurmountable stability problems was on a gigabyte motherboard. I hated that thing, but I suffered with it just long enough that I couldn't warranty return it and they refused to accept it had actual problems. It eventually had an unexplained failure by way of a hammer repeatedly falling on it.
 
Zorin OS is also very comfy and noob-friendly, from what I've seen. Practically a drop-in replacement of Windoze.
I always get Zorin confused with Deepin, that chinese spyware linux distro.

this board did not HAVE nvme screws it only has these weird fake little plastic things, trying to insert them in without help BROKE them easily as there WAY more fragile and honestly ALOT harder to use
But SAAR screwing in NVME drives are TOO HARD for retards. They keep REDEEMING BENDING THE BLODDY BENCHODE DRIVE! YOU NEED TO SUFFER FOR IT!
 
The thing about Zorin is they could have just been another Cinnamon based distribution but with their own opinionated takes, Gnome devs blindside their users (read: not necessarily FANS) with all kinds of pretentious bullshit that throws a wrench in user accessibility.
 
Back
Top Bottom