two thumbs and now building nvidia drivers by hand. waste of my opposable thumbs
two thumbs and now building nvidia drivers by hand. waste of my opposable thumbs
this time it failed for a good reason but i'm about to make it fail for horrifyingly nihilistic reasons again
OMG GUESS WHO HAS TWO THUMBS AND NEEDS TO COMPILE THEIR KERNEL FUCKING AGAIN AFTER UPDATING GCC
i'm about to literally fix all of this for everyone but i need to fix this to do everything else
the problem is never ever gcc's fault. the problem is your fucking tooling
sometimes the problem is gcc's fault
for those keeping track at home that will make 4 full compiles of the beautiful collaboration that interfaces with our hardware
i've decided to set the scheduler strategy to CONFIG_PREEMPT_VOLUNTARY over the linux-zen default of CONFIG_PREEMPT because this laptop has obnoxious specs and they describe CONFIG_PREEMPT as being like for embedded systems (and laptops) whereas CONFIG_PREEMPT_VOLUNTARY is singly characterized as for desktops and i have this thing plugged in 99% of the time
they are pretty clear in the docs for each of these choices why this can't be a dynamic setting because it's about compiling in explicit pre-emption points. kind of an interesting result for such a dynamic process like a scheduler
oh wow but you can change it on the kernel command line and they so it's a very small increase in code. compilers are amazing
i kinda wanna try LTOing this just to see if it will crash my system somehow
i think i'm gonna turn off things like profiling which i don't need right now
kexec is so cool lol
oh hell yes missed CONFIG_SCHED_AUTOGROUP before. linux very much does try to separate build jobs from desktop applications
A space for Bonfire maintainers and contributors to communicate