Well one of those options affected my ability to connect to my monitor. The issue was not resolved though, and I don't feel like clearing my cmos again to see which setting exactly caused the monitor issue.
KrispeeIguana
joined 2 years ago
None of the settings have worked, but I did find 2 interesting settings hanging out in bios.
Would either changing the South Bridge speed or turning on the Compatibility Support Module (CSM) do anything?
I took a short look, but all the slots were on auto. My options were all pcie gen 1, 2, 3, or 4. My motherboard is an ASUS TUF Gaming X570 Plus Wifi, and I'm not really sure if the 2 M.2 slots eat my 2 PCIE x1 slots or not.
6.13.1-arch1-1 for x86_64
The firmware package is the upd72020x-fw (AUR only) package which is required by the mkinitcpio-firmware package. I have tried reinstalling both packages using both pacman and paru in case one gave extra errors.
Should be the most recent given that I run a recently updated Arch installation.
My Arch system stays on until a firmware package needs an update. Then i cry and scream bc it's only been a month since the last one. Also I just updated a bunch of those, so my system has not been on long.
My issue is that I can never remember "a couple more commands" for the life of me. And I use Arch BTW, so the likelihood of me needing those is a bit higher than usual.
He can be an asshole, but I believe finding bugs is part of his job.
Would you rather have him find them and complain to a community who might know what they could be, or someone else who will just complain and buy a MacBook instead?
It's definitely great for the mainstream. Think of Linus Sebastian who has somehow broken every OS except for SteamOS.
It's not great for me who uses Arch Linux btw with the expectation that if the system doesn't break on its own, then I will break it myself.
Some of the stuff I would do if my system was held together by more than literally just hopes and dreams.
Shit you might be right. I might just be extremely stupid.
view more: next โบ
From what I remember, it's much more difficult to accidentally leak memory in Rust. Combined with the drop-in compatibility with C and the somewhat more intuitive (imo) syntax, I can see its popularity as unsurprising.
I think the biggest thing is that there aren't really that many reasons not to use Rust.