Latest (fc40 and fc41) few kernels fail to install

Ask Fedora
, ,
1

Hello,
New forum user but years-long happy fedora user here

I am having some problems updating kernels:

>>> Running post-transaction scriptlet: kernel-core-0:6.12.4-200.fc41.x86_64
>>> Non-critical error in post-transaction scriptlet: kernel-core-0:6.12.4-200.fc41.x86_64
>>> Scriptlet output:
>>> 
>>> Sign command: /lib/modules/6.12.4-200.fc41.x86_64/build/scripts/sign-file
>>> Signing key: /var/lib/dkms/mok.key
>>> Public certificate (MOK): /var/lib/dkms/mok.pub
>>> 
>>> Cleaning build area... done.
>>> Building module(s)...(bad exit status: 2)
>>> Failed command:
>>> make -j8 KERNELRELEASE=6.12.4-200.fc41.x86_64 all KERNEL_SRC=/lib/modules/6.12.4-200.fc41.x86_64/build
>>> 
>>> Error! Bad return status for module build on kernel: 6.12.4-200.fc41.x86_64 (x86_64)
>>> Consult /var/lib/dkms/anbox-ashmem/1/build/make.log for more information.
>>> 
>>> Sign command: /lib/modules/6.12.4-200.fc41.x86_64/build/scripts/sign-file
>>> Signing key: /var/lib/dkms/mok.key
>>> Public certificate (MOK): /var/lib/dkms/mok.pub
>>> 
>>> Cleaning build area... done.
>>> Building module(s)...(bad exit status: 2)
>>> Failed command:
>>> make -j8 KERNELRELEASE=6.12.4-200.fc41.x86_64 all INCLUDEDIR=/lib/modules/6.12.4-200.fc41.x86_64/build/include KVE
>>> 
>>> Error! Bad return status for module build on kernel: 6.12.4-200.fc41.x86_64 (x86_64)
>>> Consult /var/lib/dkms/evdi/1.11.0/build/make.log for more information.
>>> Autoinstall on 6.12.4-200.fc41.x86_64 failed for module(s) anbox-ashmem(10) evdi(10).
>>> 
>>> Error! One or more modules failed to install during autoinstall.
>>> Refer to previous errors for more information.
>>> /usr/lib/kernel/install.d/40-dkms.install failed with exit status 11.
>>> 
>>> [RPM] %posttrans(kernel-core-6.12.4-200.fc41.x86_64) scriptlet failed, exit status 11
Complete!

This happened to 6.11.11-200, and 6.11.11-300 as well. I am running 6.11.10-200 which is for fc40 while I already upgraded (scary move).

So;

  • can i keep running this kernel with the newer distro without problems?
  • how can I fix this? log:
$ cat /var/lib/dkms/anbox-ashmem/1/build/make.log
DKMS make.log for anbox-ashmem/1 for kernel 6.12.4-200.fc41.x86_64 (x86_64)
Mon 16 Dec 16:14:25 CET 2024
make -C /lib/modules/6.12.4-200.fc41.x86_64/build V=0 M=$PWD
make[1]: Entering directory '/usr/src/kernels/6.12.4-200.fc41.x86_64'
  CC [M]  /var/lib/dkms/anbox-ashmem/1/build/deps.o
  CC [M]  /var/lib/dkms/anbox-ashmem/1/build/ashmem.o
/var/lib/dkms/anbox-ashmem/1/build/deps.c:6:5: warning: no previous prototype for ‘shmem_zero_setup’ [-Wmissing-prototypes]
    6 | int shmem_zero_setup(struct vm_area_struct *vma)
      |     ^~~~~~~~~~~~~~~~
/var/lib/dkms/anbox-ashmem/1/build/ashmem.c: In function ‘ashmem_mmap’:
/var/lib/dkms/anbox-ashmem/1/build/ashmem.c:393:23: error: assignment of read-only member ‘vm_flags’
  393 |         vma->vm_flags &= ~calc_vm_may_flags(~asma->prot_mask);
      |                       ^~
/var/lib/dkms/anbox-ashmem/1/build/ashmem.c: In function ‘ashmem_init’:
/var/lib/dkms/anbox-ashmem/1/build/ashmem.c:877:9: error: implicit declaration of function ‘register_shrinker’; did you mean ‘register_chrdev’? [-Wimplicit-function-declaration]
  877 |         register_shrinker(&ashmem_shrinker);
      |         ^~~~~~~~~~~~~~~~~
      |         register_chrdev
/var/lib/dkms/anbox-ashmem/1/build/ashmem.c: In function ‘ashmem_exit’:
/var/lib/dkms/anbox-ashmem/1/build/ashmem.c:884:9: error: implicit declaration of function ‘unregister_shrinker’; did you mean ‘unregister_chrdev’? [-Wimplicit-function-declaration]
  884 |         unregister_shrinker(&ashmem_shrinker);
      |         ^~~~~~~~~~~~~~~~~~~
      |         unregister_chrdev
make[3]: *** [scripts/Makefile.build:229: /var/lib/dkms/anbox-ashmem/1/build/ashmem.o] Error 1
make[2]: *** [/usr/src/kernels/6.12.4-200.fc41.x86_64/Makefile:1976: /var/lib/dkms/anbox-ashmem/1/build] Error 2
make[1]: *** [Makefile:236: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/kernels/6.12.4-200.fc41.x86_64'
make: *** [Makefile:12: all] Error 2

thanks,

1 Like
2

On my system, DKMS was installed for the displaylink driver, which I haven’t used in years. I was able to remove the displaylink package (which additionally removed dkms, and kernel-devel-matched), and then re-install the kernel-core package. It seemed to work, and didn’t throw any errors this time, although I haven’t rebooted yet.

3

Hi
I got a similar message, but I don’t have any displaylink.
So I only have 6.11.10-300 which runs now, 6.11.11 and 6.11.12 are both not booting anymore, so next update has to work otherwise I am left without bootable kernel…
Which logfiles should I provide for more info (tomorrow tho…)?

Thank you very much for your help!

1 Like
4

Hello,
same problem here, no Displaylink, just a “regular” install on a T14 AMD Gen1 without any additional drivers.

>>> Sign command: /lib/modules/6.12.4-200.fc41.x86_64/build/scripts/sign-file
>>> Signing key: /var/lib/dkms/mok.key
>>> Public certificate (MOK): /var/lib/dkms/mok.pub
>>> 
>>> Cleaning build area... done.
>>> Building module(s)...(bad exit status: 2)
>>> Failed command:
>>> make -j16 KERNELRELEASE=6.12.4-200.fc41.x86_64 -C /lib/modules/6.12.4-200.fc41.x86_64/build M=/var/lib/dkms/acpi_call/1.1.0/build
>>> 
>>> Error! Bad return status for module build on kernel: 6.12.4-200.fc41.x86_64 (x86_64)
>>> Consult /var/lib/dkms/acpi_call/1.1.0/build/make.log for more information.
>>> Autoinstall on 6.12.4-200.fc41.x86_64 failed for module(s) acpi_call(10).
>>> 
>>> Error! One or more modules failed to install during autoinstall.
>>> Refer to previous errors for more information.
>>> /usr/lib/kernel/install.d/40-dkms.install failed with exit status 11.

and I also needed to boot a FC40 kernel. So far I can reproduce the error by reinstalling the kernel. Please let me know if I should provide the log for more information.

1 Like
5

Running post-transaction scriptlet: kernel-core-0:6.12.5-200.fc41.x86_64
Non-critical error in post-transaction scriptlet: kernel-core-0:6.12.5-200.fc41.x86_64
Scriptlet output:

Sign command: /lib/modules/6.12.5-200.fc41.x86_64/build/scripts/sign-file
Signing key: /var/lib/dkms/mok.key
Public certificate (MOK): /var/lib/dkms/mok.pub

Cleaning build area… done.
Building module(s)…(bad exit status: 2)
Failed command:
make -j16 KERNELRELEASE=6.12.5-200.fc41.x86_64 LINUX_SRCDIR=/lib/modules/6.12.5-200.fc41.x86_64/build

Error! Bad return status for module build on kernel: 6.12.5-200.fc41.x86_64 (x86_64)
Consult /var/lib/dkms/linux-gpib/4.2.0-2.20190107svn1809.fc30/build/make.log for more information.
Autoinstall on 6.12.5-200.fc41.x86_64 failed for module(s) linux-gpib(10).

Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
/usr/lib/kernel/install.d/40-dkms.install failed with exit status 11.

[RPM] %posttrans(kernel-core-6.12.5-200.fc41.x86_64) scriptlet failed, exit status 11

still not working… What would you need to debug the issue, unfortunately I am at a loss how to proceed, but could assist in fault finding :slight_smile:

6

I suggest removing one or both of the kernels that won’t boot before you do another update.
Then if the update kernel does not work you will still have 6.11.10-300 to use.

No idea about the underlying issue, sorry.

7

Just an update:
I removed the not booting ones and ran the update and the newest kernel seems to have installed and booted up without a hitch so far:

~$ uname -a
Linux fedora 6.12.5-200.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Sun Dec 15 16:48:23 UTC 2024 x86_64 GNU/Linux

I am not sure what the problem with the 6.11 series was…

1 Like
8

and 6.12.6-200 didn’t build this morning, so I removed it. On, off :slight_smile:

9

6.12.6-200.fc41 works for me. So much thanks for all involved so far :wink: I had to remove all up to 6.12.5.200-fc41 to even dare to try. You seem to be right about the on/off feature called kernel updates