but my uname -r equals to 5.10.90-1.qubes.x86_64 and the folder /usr/src/kernels/5.10.90-1.qubes.x86_64 doesn’t exist, only the folder /usr/src/kernels/5.10.112-1.fc32.qubes.x86_64
You’re booting with old kernel 5.10.90-1.qubes.x86_64 in dom0 instead new 5.10.112-1.fc32.qubes.x86_64.
Check your grub config to see if the new kernel is there or not.
If you’ve installed Qubes in BIOS mode then check this file: /boot/grub2/grub.cfg
For UEFI check this file: /boot/efi/EFI/qubes/grub.cfg
If the new kernel is missing in boot menu options then try to regenerate grub in dom0: grub2-mkconfig -o /boot/grub2/grub.cfg
or grub2-mkconfig -o /boot/efi/EFI/qubes/grub.cfg
UPD:
If you really need to use old kernel then you can install kernel-devel package for older kernel like this: sudo qubes-dom0-update kernel-devel-1000:5.10.90-1.fc32.qubes
Then you’re using BIOS mode and you need to run this command to regenerate your grub: sudo grub2-mkconfig -o /boot/grub2/grub.cfg
Did you reboot your Qubes after running grub2-mkconfig?
If not then reboot and check if you have new kernel now: uname -r
I did sudo qubes-dom0-update dkms kernel-devel
it said kernel-devel-1000:5.10.112.1.fc32.qubes.x86_64 is already installed
then I did sudo grub2-mkconfig -o /boot/grub2/grub.cfg
it said
generating grub configuration files ...
found theme: /boot/grub2/themes/qubes/theme.txt
found linux image /boot/vmlinuz-5.10.90-1.fc32.qubes.x86_64
found initrd image: /boot/initramfs-5.10.90-1.fc32.qubes.x86_64.img
found linux image /boot/vmlinuz-5.10.90-1.fc32.qubes.x86_64
found initrd image: /boot/initramfs-5.10.90-1.fc32.qubes.x86_64.img
done
then I did sudo reboot and after reboot uname -r and it’s still 5.10.90-1.fc32.qubes.x86_64
make[1]: *** No rule to make target 'arch/x86/entry/syscalls/syscall_32.tbl', needed by 'arch/x86/include/generated/uapi/asm/unistd_32.h'. Stop.
make: *** [arch/x86/Makefile:217: archheaders] Error 2