The Linux Thread - The Autist's OS of Choice

[BrieLarsonFan2004]

I'm a winnigger and I used xUbuntu as well as regular Ubuntu and they were both shit.
Tons of little problems, most prominent of which was the cursor glitching out and clipping across the screen.
Is this common with Linux or is Ubuntu just shit? I used Ubuntu since it's recommended the most to normalfaggots.
Performance isn't really an issue for me , I would only want to use Linux for privacy/l33t haXor "it looks cool" reasons, as well as just having something else tech related under my belt for career purposes.
What distro should I use, if I should use one at all?

 

[notafederalagent]

What distro should I use, if I should use one at all?

How old/new is the hardware? Is it running on intel or amd graphics?

 

[BrieLarsonFan2004]

How old/new is the hardware? Is it running on intel or amd graphics?

Intel. I built it in Jan2022 and I put a little over $2k into it.
It's a very good machine.

 

[Another Char Clone]

Not recommended - I once corrupted a filesystem by doing this. If you tell it to Boot before it's finishing Syncing, it will quite happily do this. It's safer just to hold down the off button.

True, common sense apply, wait for the disk to go idle and unmounted, with all processes except init dead. Holding down the power button should be enough time to get all disk cache flushed.

 

[ditto]

Zorin

No way I'd be letting Christopher Walken anywhere near my hard drive.

 

[notafederalagent]

Intel. I built it in Jan2022 and I put a little over $2k into it.
It's a very good machine

I'd recommend flashing Ventoy onto a USB stick. Download a bunch of different distros to test drive to the Ventoy stick. It makes it easy to test distros because you don't have to keep flashing a USB drive with a new image when you want to try the next one, just reboot. Any graphics issues like you experienced should be apparent when you boot into the live iso image from Ventoy (in my limited experience). Everyone's got their preference, I've been sticking with the Fedora Spin of Cinnamon DE for a while now and it's been rock solid on a 10 yo Dell business laptop. Plenty of more knowledgeable and experienced here can offer their advice, but Ventoy was a game changer when it came to running live/installing isos to determine what friends and family felt most comfortable running on their machines after the switch from Windows.

 

[BrieLarsonFan2004]

I'd recommend flashing Ventoy onto a USB stick. Download a bunch of different distros to test drive to the Ventoy stick. It makes it easy to test distros because you don't have to keep flashing a USB drive with a new image when you want to try the next one, just reboot. Any graphics issues like you experienced should be apparent when you boot into the live iso image from Ventoy (in my limited experience). Everyone's got their preference, I've been sticking with the Fedora Spin of Cinnamon DE for a while now and it's been rock solid on a 10 yo Dell business laptop. Plenty of more knowledgeable and experienced here can offer their advice, but Ventoy was a game changer when it came to running live/installing isos to determine what friends and family felt most comfortable running on their machines after the switch from Windows.

Wouldn't it be better to make a virtual machine instead of running everything off a flash drive? I'm curious.
Thank you for the advice/info.

 

[Heliantheae]

Wouldn't it be better to make a virtual machine instead of running everything off a flash drive? I'm curious.
Thank you for the advice/info.

You won't catch hardware related issues running it in a VM, for that liveboot testing is better. For trying out distros in general VMs are great.

 

[Another Char Clone]

I can't reply directly, but that just looks like the kernel configured to be verbose on boot and printing out board details.

 

[Rusty Metal Skull Gun]

@Dr. Geronimo, you probably want to censor that UUID - that's a good way to accidentally dox yourself.

 

[Knight of the Rope]

@Dr. Geronimo, you probably want to censor that UUID - that's a good way to accidentally dox yourself.

Is that actually a thing?

Not being facetious, by the way. I literally have no idea if it's possible, but my (uneducated) suspicion is that it would probably be very difficult at best, and I feel like if one of us pulled it off it would be one of the most impressive doxes this site has ever seen.

 

[Dr. Geronimo]

Is that actually a thing?

Not being facetious, by the way. I literally have no idea if it's possible, but my (uneducated) suspicion is that it would probably be very difficult at best, and I feel like if one of us pulled it off it would be one of the most impressive doxes this site has ever seen.

I had no idea what it was so I deleted the post out of safety. Considering I literally named my user Gero I don't think I'll be hiding this install lol.

 

[Rusty Metal Skull Gun]

Is that actually a thing?

Not being facetious, by the way. I literally have no idea if it's possible, but my (uneducated) suspicion is that it would probably be very difficult at best, and I feel like if one of us pulled it off it would be one of the most impressive doxes this site has ever seen.

It's random, so not in the way you're thinking of. I was thinking that if Dr. Geronimo asked for help on Stack Overflow or wherever, even if he changed the username and hostname it'd tie it back to here. And this might be many years in the future, long after this thread has been forgotten.

 

[Dr. Geronimo]

It's random, so not in the way you're thinking of. I was thinking that if Dr. Geronimo asked for help on Stack Overflow or wherever, even if he changed the username and hostname it'd tie it back to here. And this might be many years in the future, long after this thread has been forgotten.

Whatever the thoughts are on this subject, I do appreciate the concern.

 

[Knight of the Rope]

I was thinking that if Dr. Geronimo asked for help on Stack Overflow or wherever, even if he changed the username and hostname it'd tie it back to here.

That's fair. Although for the record, coming across a StackOverflow post and thinking "Hey, I recognize that hex-string!" and tracing it back would still be an unbelievably impressive feat of autism.

 

[Rusty Metal Skull Gun]

That's fair. Although for the record, coming across a StackOverflow post and thinking "Hey, I recognize that hex-string!" and tracing it back would still be an unbelievably impressive feat of autism.

The reverse is more likely. Coming across a UUID on KF and Googling it to find out where else it's been used. Also, trannies.

 

[Markass the Worst]

That's fair. Although for the record, coming across a StackOverflow post and thinking "Hey, I recognize that hex-string!" and tracing it back would still be an unbelievably impressive feat of autism.

I think it's still good to be cautious of opsec when asking for help, anywhere. After all one of the reasons Ross Ulbricht got found by the feds was because he asked about using PHP and Tor and stuff on StackOverflow under his own name.

 

[Dr. Geronimo]

Okay I don't know what's up the but 2 minute boot time and the udev issue came back. Whenever the udev thing happens I have to do a force shutdown. Restarted and did the journalctl thing

Spoiler: code

gero@gero-Z390-GAMING-X:~$ journalctl -o short-precise -k
Jan 27 22:43:53.253020 gero-Z390-GAMING-X kernel: microcode: microcode updated >
Jan 27 22:43:53.253035 gero-Z390-GAMING-X kernel: Linux version 5.15.0-58-gener>
Jan 27 22:43:53.253041 gero-Z390-GAMING-X kernel: Command line: BOOT_IMAGE=/boo>
Jan 27 22:43:53.253046 gero-Z390-GAMING-X kernel: KERNEL supported cpus:
Jan 27 22:43:53.253050 gero-Z390-GAMING-X kernel: Intel GenuineIntel
Jan 27 22:43:53.253054 gero-Z390-GAMING-X kernel: AMD AuthenticAMD
Jan 27 22:43:53.253059 gero-Z390-GAMING-X kernel: Hygon HygonGenuine
Jan 27 22:43:53.253063 gero-Z390-GAMING-X kernel: Centaur CentaurHauls
Jan 27 22:43:53.253067 gero-Z390-GAMING-X kernel: zhaoxin Shanghai
Jan 27 22:43:53.253071 gero-Z390-GAMING-X kernel: x86/fpu: Supporting XSAVE fea>
Jan 27 22:43:53.253075 gero-Z390-GAMING-X kernel: x86/fpu: Supporting XSAVE fea>
Jan 27 22:43:53.253079 gero-Z390-GAMING-X kernel: x86/fpu: Supporting XSAVE fea>
Jan 27 22:43:53.253083 gero-Z390-GAMING-X kernel: x86/fpu: Supporting XSAVE fea>
Jan 27 22:43:53.253088 gero-Z390-GAMING-X kernel: x86/fpu: Supporting XSAVE fea>
Jan 27 22:43:53.253094 gero-Z390-GAMING-X kernel: x86/fpu: xstate_offset[2]: 5>
Jan 27 22:43:53.253099 gero-Z390-GAMING-X kernel: x86/fpu: xstate_offset[3]: 8>
Jan 27 22:43:53.253103 gero-Z390-GAMING-X kernel: x86/fpu: xstate_offset[4]: 8>
Jan 27 22:43:53.253107 gero-Z390-GAMING-X kernel: x86/fpu: Enabled xstate featu>
Jan 27 22:43:53.253111 gero-Z390-GAMING-X kernel: signal: max sigframe size: 20>
Jan 27 22:43:53.253116 gero-Z390-GAMING-X kernel: BIOS-provided physical RAM ma>
Jan 27 22:43:53.253120 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x00000000000>
Jan 27 22:43:53.253124 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x00000000000>
Jan 27 22:43:53.253128 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x00000000000>
lines 1-23...skipping...
Jan 27 22:43:53.253020 gero-Z390-GAMING-X kernel: microcode: microcode updated early to revision 0xf0, date = 2021-11-16
Jan 27 22:43:53.253035 gero-Z390-GAMING-X kernel: Linux version 5.15.0-58-generic (buildd@lcy02-amd64-101) (gcc (Ubuntu 11.3.0-1ubuntu1~22.04) 11.3.0, GNU ld (GNU Binutils for Ubuntu) 2.3 #64-Ubuntu SMP Thu Jan 5 11:43:13 UTC 2023 (Ubuntu 5.15.0-58.64-generic 5.15.74)
Jan 27 22:43:53.253041 gero-Z390-GAMING-X kernel: Command line: BOOT_IMAGE=/boot/vmlinuz-5.15.0-58-generic root=UUID=NIGGER ro quiet splash
Jan 27 22:43:53.253046 gero-Z390-GAMING-X kernel: KERNEL supported cpus:
Jan 27 22:43:53.253050 gero-Z390-GAMING-X kernel: Intel GenuineIntel
Jan 27 22:43:53.253054 gero-Z390-GAMING-X kernel: AMD AuthenticAMD
Jan 27 22:43:53.253059 gero-Z390-GAMING-X kernel: Hygon HygonGenuine
Jan 27 22:43:53.253063 gero-Z390-GAMING-X kernel: Centaur CentaurHauls
Jan 27 22:43:53.253067 gero-Z390-GAMING-X kernel: zhaoxin Shanghai
Jan 27 22:43:53.253071 gero-Z390-GAMING-X kernel: x86/fpu: Supporting XSAVE feature 0x001: 'x87 floating point registers'
Jan 27 22:43:53.253075 gero-Z390-GAMING-X kernel: x86/fpu: Supporting XSAVE feature 0x002: 'SSE registers'
Jan 27 22:43:53.253079 gero-Z390-GAMING-X kernel: x86/fpu: Supporting XSAVE feature 0x004: 'AVX registers'
Jan 27 22:43:53.253083 gero-Z390-GAMING-X kernel: x86/fpu: Supporting XSAVE feature 0x008: 'MPX bounds registers'
Jan 27 22:43:53.253088 gero-Z390-GAMING-X kernel: x86/fpu: Supporting XSAVE feature 0x010: 'MPX CSR'
Jan 27 22:43:53.253094 gero-Z390-GAMING-X kernel: x86/fpu: xstate_offset[2]: 576, xstate_sizes[2]: 256
Jan 27 22:43:53.253099 gero-Z390-GAMING-X kernel: x86/fpu: xstate_offset[3]: 832, xstate_sizes[3]: 64
Jan 27 22:43:53.253103 gero-Z390-GAMING-X kernel: x86/fpu: xstate_offset[4]: 896, xstate_sizes[4]: 64
Jan 27 22:43:53.253107 gero-Z390-GAMING-X kernel: x86/fpu: Enabled xstate features 0x1f, context size is 960 bytes, using 'compacted' format.
Jan 27 22:43:53.253111 gero-Z390-GAMING-X kernel: signal: max sigframe size: 2032
Jan 27 22:43:53.253116 gero-Z390-GAMING-X kernel: BIOS-provided physical RAM map:
Jan 27 22:43:53.253120 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x0000000000000000-0x000000000009d3ff] usable
Jan 27 22:43:53.253124 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x000000000009d400-0x000000000009ffff] reserved
Jan 27 22:43:53.253128 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x00000000000e0000-0x00000000000fffff] reserved
Jan 27 22:43:53.253133 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x0000000000100000-0x0000000031f83fff] usable
Jan 27 22:43:53.253137 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x0000000031f84000-0x0000000031f84fff] ACPI NVS
Jan 27 22:43:53.253142 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x0000000031f85000-0x0000000031f85fff] reserved
Jan 27 22:43:53.253146 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x0000000031f86000-0x000000003cafffff] usable
Jan 27 22:43:53.253150 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x000000003cb00000-0x000000003dfc2fff] reserved
Jan 27 22:43:53.253154 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x000000003dfc3000-0x000000003e14dfff] usable
Jan 27 22:43:53.253158 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x000000003e14e000-0x000000003e586fff] ACPI NVS
Jan 27 22:43:53.253162 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x000000003e587000-0x000000003eefdfff] reserved
Jan 27 22:43:53.253166 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x000000003eefe000-0x000000003eefefff] usable
Jan 27 22:43:53.253171 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x000000003eeff000-0x000000003fffffff] reserved
Jan 27 22:43:53.253175 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x00000000e0000000-0x00000000efffffff] reserved
Jan 27 22:43:53.253179 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x00000000fe000000-0x00000000fe010fff] reserved
Jan 27 22:43:53.253184 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x00000000fec00000-0x00000000fec00fff] reserved
Jan 27 22:43:53.253188 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x00000000fee00000-0x00000000fee00fff] reserved
Jan 27 22:43:53.253192 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x00000000ff000000-0x00000000ffffffff] reserved
Jan 27 22:43:53.253196 gero-Z390-GAMING-X kernel: BIOS-e820: [mem 0x0000000100000000-0x00000008bdffffff] usable
Jan 27 22:43:53.253201 gero-Z390-GAMING-X kernel: NX (Execute Disable) protection: active
Jan 27 22:43:53.253207 gero-Z390-GAMING-X kernel: SMBIOS 3.1.1 present.
Jan 27 22:43:53.253211 gero-Z390-GAMING-X kernel: DMI: Gigabyte Technology Co., Ltd. Z390 GAMING X/Z390 GAMING X-CF, BIOS F10 11/05/2021
Jan 27 22:43:53.253217 gero-Z390-GAMING-X kernel: tsc: Detected 3600.000 MHz processor
Jan 27 22:43:53.253221 gero-Z390-GAMING-X kernel: e820: update [mem 0x00000000-0x00000fff] usable ==> reserved
Jan 27 22:43:53.253226 gero-Z390-GAMING-X kernel: e820: remove [mem 0x000a0000-0x000fffff] usable
Jan 27 22:43:53.253231 gero-Z390-GAMING-X kernel: last_pfn = 0x8be000 max_arch_pfn = 0x400000000
Jan 27 22:43:53.253236 gero-Z390-GAMING-X kernel: x86/PAT: Configuration [0-7]: WB WC UC- UC WB WP UC- WT
Jan 27 22:43:53.253240 gero-Z390-GAMING-X kernel: last_pfn = 0x3eeff max_arch_pfn = 0x400000000
Jan 27 22:43:53.253245 gero-Z390-GAMING-X kernel: found SMP MP-table at [mem 0x000fce30-0x000fce3f]
lines 1-49

 

[seri0us]

I think it's still good to be cautious of opsec when asking for help, anywhere. After all one of the reasons Ross Ulbricht got found by the feds was because he asked about using PHP and Tor and stuff on StackOverflow under his own name.

And the final blow being that he left his (unencrypted) laptop unattended, letting the feds snatch it.

 

[Aidan]

And the final blow being that he left his (unencrypted) laptop unattended, letting the feds snatch it.

I thought the laptop was encrypted.
The story I remember is that they found out he would go to a library to use their wifi while doing darknet stuff and they needed his laptop without him locking the screen to really put being the Silk Road admin on him. To do this they distracted him and then went to his laptop when he got up without locking it; arresting him then and there as he was signed into The Silk Road as Dread Pirate Roberts, the admin account.

I don't remember him being a Tails user or using another live OS but that would make sense. He woulda gotten away with it if he used other anonymous accounts to post about tor-related stuff. or at least lasted a bit longer