Pedro Mendes
gepasi@fediscience.org
<p><a href="https://fediscience.org/tags/Biochemist" class="mention hashtag" rel="tag">#<span>Biochemist</span></a>, <a href="https://fediscience.org/tags/ComputerScientist" class="mention hashtag" rel="tag">#<span>ComputerScientist</span></a>, <a href="https://fediscience.org/tags/SystemsBiology" class="mention hashtag" rel="tag">#<span>SystemsBiology</span></a>, <a href="https://fediscience.org/tags/Professor" class="mention hashtag" rel="tag">#<span>Professor</span></a>, <a href="https://fediscience.org/tags/Photographer" class="mention hashtag" rel="tag">#<span>Photographer</span></a>, <a href="https://fediscience.org/tags/EVdriver" class="mention hashtag" rel="tag">#<span>EVdriver</span></a>, <a href="https://fediscience.org/tags/Programmer" class="mention hashtag" rel="tag">#<span>Pr
Posts
-
View post
how to fix copy.fail in #slackware : fortunately #slackware kernels (even huge) have the offending code as a module (algif_aead.ko). So, until you upgrade the kernel you can disable this module with echo &quot;blacklist algif_aead&quot; &gt; /etc/modprobe.d/copy-fail.conf (make sure it is not currently in memory with lsmod | grep aead) I&#39;ve done this on machines where I want to keep using the official packages, but on other ones I switched to kernel 6.18.26