#[solved] I did something, now after booting, system is slow af

1 messages · Page 1 of 1 (latest)

potent scarab
#

did you figure it out arni?

#

which iwlwifi chipset do you have?

#

some of the wifi 5 iwlwifi chipsets are buggy

#

have you ever degredation tested your cpu?

potent scarab
#

if your build config resembles this fellows build config that's perhaps explainable

tawdry shadow
#

My guess is the wifi firmware did not load. It might be missing in initramfs

potent scarab
#

that fella has never updated bios, never uses uefi, forces getbinpkg and consequentially has tons of use flag omissions

#

a recepie for system instability and inconsistency

#

a very old gentoo dev that mentored me ~20+ years ago shared a phrase

#

I enabled it because it looked cool

#

it's fun to have experiments until you have to rely on an experiment

#

my resolution to that build could be move it to it;s own btrfs subvolume and build a stable reliable gentoo build

#

subvolume multiboot

#

there's a windows util that tests the cpu

#

forcing lto with -O3 and graphite maybe was going to be very unpredictable

tawdry shadow
#

I RMA'd my Intel cpu last month

potent scarab
#
EMERGE_DEFAULT_OPTS="--jobs=4 --load-average=24 -b"```
#

choose one ;)

tawdry shadow
#

The Intel tool was not helpful

potent scarab
#

too many build jobs also can cause build errors or buggy shared libraries

#

EMERGE_DEFAULT_OPTS="--jobs=4 --load-average=24 -b" or the other one

#

MAKEOPTS="-j18"

#

kiss philosophy works well for gentoo

tawdry shadow
#

I'd be scared to build the entire system with those fancy optimizations

potent scarab
#

if you reported a bug with that build the dev's would review your emerge info and likely tag the bug as wontfix

#

experiments :)

#

either way the boot bug result is the summary of the build config being what it is

#

if you want a reliable build that wont be

#

check your cpu if you can just to be certain

#

icarus said the same thing after attempting a full git gentoo build

#

i'll most certainly help if it;s a benefit with a reliable build you can fun with

#

prob the most updated

#

or if you insist on openrc

#

keep it simple stupid :)

tawdry shadow
#

It took me months to prove that the cpu was defective. I could run that Intel IPT tool for hours without errors

potent scarab
#

i've only learned of it somewhat recently from helping some folks on pcmr discord

#

figured it was more promising than the usual "just use DDU" recommendation everyone seems to be fed from a straw lol

tawdry shadow
#

For me it was very subtle. Every now and again gcc would fail with an internal compiler error, or emerge itself would crash in the python interpreter. It would happen rarely, like once a month, but became more frequent

#

Of course running the same thing again would work

full venture
#

I did something, now after booting, system is slow af