| Commit message (Collapse) | Author | Age | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
The Gentoo Wiki [1] seems to be wrong about which firmware blobs are
needed for an up-to-date installation of linux-firmware, leading to
the following error and, subsequently, a crash at bootup:
kernel: amdgpu 0000:0d:00.0: Direct firmware load for amdgpu/gc_11_0_0_mes_2.bin failed with error -2
kernel: [drm] try to fall back to amdgpu/gc_11_0_0_mes.bin
Replacing amdgpu/gc_11_0_0_mes.bin with amdgpu/gc_11_0_0_mes_2.bin or at
least making the latter available makes it work again.
[1] https://wiki.gentoo.org/wiki/AMDGPU#Firmware
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
portage has removed the 'cgroup' feature as it was based on cgroups v1.
Instead, the 'pid-sandbox' feature (which is enabled by default) is used
to isolate the process space and enable cleanly killing all processes
spawned by an ebuild.
|
| | |
|
| |
|
|
|
| |
Using -march=native selects options specifically detected for the CPU,
and not only a lowest-common base for the entire Zen 3 lineup.
|
| |
|
|
|
|
|
| |
sys-kernel/linux-firmware overwrites the savedconfig file every time it
is installed. Since the sorting order there is different, the file
changes every time linux-firmware is installed. Revert to upstream
sorting so we don't have to deal with non-functional changes in there.
|
|
|
This is our new desktop system, replacing nabokov.
|
