You are not logged in.
Pages: 1
Hi everyone, I've got a new problem to investigate. As I said some threads behind I did a new installation and currently finishing to set it up, but the today's kernel upgrade broke my system (or at least, I assume it was that, also the linux-headers, linux-firmware and util-linux upgraded alongside).
Journalctl -xb reported these errors:
systemd[1]: Failed to start Load Kernel Modules.
systemd-modules-load[215]: Failed to look up module alias 'crypto_user': Function not implemented
systemd-modules-load[215]: Failed to look up module alias 'sg': Function not implemented
systemd-modules-load[215]: Failed to look up module alias 'pkcs8_key_parses': Function not implemented
systemd[1]: Failed to mount /efi.dmesg | grep 'Failed'
systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'.
systemd[1]: Failed to start Load Kernel Modules.Dmesg doesn't report emerg, alert or critic messages.
Funny, this was one of the few times I've searched the net looking for information about the upgrade of these packages, willing to get serious about them. There was just a warning for util-linux, though, it was affecting a package I don't have installed.
At this moment I downgraded to linux-5.9.8 (both kernel and headers), the same also for linux-firmware and util-linux, now everything is normal again. No errors reported by journalctl.
Last edited by noreset (2020-11-20 01:37:58)
Offline
You were already provided with information to troubleshoot such an issue in https://bbs.archlinux.org/viewtopic.php?id=241639
See also search engine results for the query "Arch linux kernel mismatch"
Last edited by loqs (2020-11-19 21:15:19)
Offline
Funny, this was one of the few times I've searched the net looking for information
See, that's part of the problem.
Offline
You were already provided with information to troubleshoot such an issue in https://bbs.archlinux.org/viewtopic.php?id=241639
See also search engine results for the query "Arch linux kernel mismatch"
Thanks and sorry for bothering with an already asked question. Though I would like to ask another one for clarification.
Should the boot partition (using the systemd bootloader) live within /boot, /boot/efi or /efi (at root level like the /boot folder)?
Because according to the wiki page, for this bootloader it should be /boot, although, I'm not 100% sure I get it well.
Offline
The kernel will be installed to /boot. If the ESP which is all system-boot can read is not mounted to /boot you need to follow EFI_system_partition#Alternative_mount_points so that the kernel is placed on the ESP.
Offline
Ok, now I get it.
/boot/efi seems to do not have so much sense, so the desirable way is to make /efi the ESP and hold the kernel and initrsmfs (also the microcode) within /boot (Not the case if you use rEFInd though). Although, since the systemd bootloader isn't capable of reading files which lies outside the ESP (like you said) it is mandatory to use /boot as ESP, or follow the method you linked. What I'm wondering is: is there a deeper reason that isn't mere theory behind these different approaches?
BTW, Everything I went through was written in the 'Alternative mount point' section. Sometimes I tend to read superficially those paragraphs which I assume do not apply to me in that moment.
Last edited by noreset (2020-11-20 01:50:37)
Offline
Pages: 1