/sci/ - Soyence and Technology

>lies lies lies lies lies
What's the point of this post?

>>10702
Post screenshots if it really did happen

>>10700
>>arch
>werked once and then started kernel panicking upon boot
You mean that the liveISO worked because it wasn't setup by you, but you fucked up the install so it failed (pebcak)

>>10700
Not my problem

first of all you didn't try the standard linux distro: slackware

second of all you should switch to BSD

>>10712
Cuck license, cucked operating system

imagine being so retarded that you manage to fuck up an installation wizard meant for retards somehow

>>10722
>blaming the user
typical gnukikery.
the default settings were used for every one, except for partitions where I selected btrfs

>>12464
Are you on UEFI or legacy bios?

>>12464
>btrfs
why would you use that meme
the developers themselves say its not production ready

>>12472
also this. try switching from UEFI to Legacy BIOS (or viceversa).
I remember once i spent many hours trying to install ubuntu on a machine and it would just fail every single time. I tried reflashing the USB several times, changing the things i chose in the wizard etc but it always failed.
then i switched from UEFI to Legacy BIOS and it worked like a charm.

People say Linux is good but the amount of troubleshooting you have to do is insane

>>12472
Clarifying it a little bit. If you are using UEFI/EFI and set your boot partition as anything but FAT32, your system would just not boot in 99% of the cases (some MB manufacturers support ntfw, but it's rare).
If you are on legacy BIOS than you have to make sure your partitions are MBR and not GPT. The installers probably should check it for you, but I'm not sure they do

>>12479
>ntfw
meant NTFS

>>10700
>kernel panic
re-run grub-mkconfig, you might have to re-run mkinitcpio, or just reinstall your kernel
pacman -S –overwrite "*" linux
and grub-mkconfig
if you use proprietary meme hardware that requires proprietary firmware, you should install linux-firmware as well as intel-ucode or amd-ucode, depending on what proprietary modern cpu you have
>all debian based garbage
well, this is why you dont use debian based distros.
>>12472
oh yeah, i forgot to mention that
UEFI (pronounced JewEFI) literally only exists to make installing lunix harder, and it WILL break shit.
this is not lunixes fault, but EFIs fault, and its not "unified" at all.
>>12474
>arch tranny had no idea what he was doing and installed a broken WIP file system thats known to cause FS corruptions
sounds like a you-problem, ext4 works perfectly fine.
>>12475
thats because UEFI is designed to be broken, there are thousands of proprietary implementations of it and every single fucking one is broken
>>12477
only if you have retarded hardware or pick insane bullshit options youre not supposed to use, like UEFI, btrfs, installing experimental shit, etc…
>>12479
BIOS boot supports GPT doe, you just have to make a boot partition on GPT
>how do they check it
list efivars, most installers just assume MBR for BIOS and GPT for UEFI, even tho you can use MBR for UEFI or GPT for most post-2000s BIOSes
there is a simpler solution to this problem btw, install coreboot/libreboot with a grub payload, and you wont even need a bootloader.
MBR and GPT will both work, and it will boot anything it finds, even without a boot partition, with an encrypted root partition, and if you want a boot partition you can encrypt that as well.
UEFI forcing you to make an additional 200M-4G boot partition is mental illness, really.

>>10700
INSTALL GENTOO YOU FUCKING NIGGER

NOW!