Skip to content
New issue

Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.

#

By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? # to your account

Jump to bottom

[PopOS 21.10] No longer able to boot PopOS's stock kernel #436

Closed
Aisyk opened this issue Feb 13, 2022 · 10 comments
Closed

[PopOS 21.10] No longer able to boot PopOS's stock kernel #436

Aisyk opened this issue Feb 13, 2022 · 10 comments

Comments

@Aisyk
Copy link

Aisyk commented Feb 13, 2022

Hi,

I have the same problem than this bug related to Fedora 35.

When i uninstall linux-tkg with synaptic. The next reboot is in emergency mode :
You are in rescue mode. After logging in, type journalctl -xb to view system logs, "systemctl reboot" to reboot, "systemctl default" or “exit to boot into default mode (or press Control-D to continue): _

This is my journalctl related to my last boot error (command journalctl -p err).
https://pastebin.com/wLq4Bu0U

I try to go to /etc/selinux/ to see if the /etc/selinux/config could help me, but it doesn't exist on my distribution.
@AdelKS
Copy link
Collaborator

AdelKS commented Feb 14, 2022

It looks like stock kernel doesn't provide some additional modules: what's happening here is that systemd load additional modules on boot and doesn't find some.

What's the output of tail /etc/modules-load.d/* ?

@Aisyk
Copy link
Author

Aisyk commented Feb 15, 2022 •
edited
Loading

Hi,

Thanks for your response,
Here is the result of the command (with 5.16.9-tkg-pds loaded) :

==> /etc/modules-load.d/cups-filters.conf <==
# Parallel printer driver modules loading for cups
# LOAD_LP_MODULE was 'yes' in /etc/default/cups
lp
ppdev
parport_pc

==> /etc/modules-load.d/modules.conf <==
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.

@AdelKS
Copy link
Collaborator

AdelKS commented Feb 15, 2022

Alright, given your logs (I will attach them here for posterity):

-- Boot 79cf37deec574c3386f1df808564609c --
févr. 13 10:58:16 pop-os systemd[1]: Failed to start Load Kernel Modules.
févr. 13 10:58:16 pop-os systemd-modules-load[534]: Failed to look up module alias 'lp': Function not implemented
févr. 13 10:58:16 pop-os systemd-modules-load[534]: Failed to look up module alias 'ppdev': Function not implemented
févr. 13 10:58:16 pop-os systemd-modules-load[534]: Failed to look up module alias 'parport_pc': Function not implemented
févr. 13 10:58:16 pop-os systemd-modules-load[534]: Failed to look up module alias 'ecryptfs': Function not implemented
févr. 13 10:58:16 pop-os systemd-modules-load[534]: Failed to look up module alias 'msr': Function not implemented
févr. 13 10:58:16 pop-os systemd[1]: Failed to mount Mount unit for core, revision 11993.
févr. 13 10:58:16 pop-os systemd[1]: Failed to mount Mount unit for core, revision 12603.
févr. 13 10:58:16 pop-os systemd-modules-load[614]: Failed to look up module alias 'lp': Function not implemented
févr. 13 10:58:16 pop-os systemd-modules-load[614]: Failed to look up module alias 'ppdev': Function not implemented
févr. 13 10:58:16 pop-os systemd-modules-load[614]: Failed to look up module alias 'parport_pc': Function not implemented
févr. 13 10:58:16 pop-os systemd-modules-load[614]: Failed to look up module alias 'ecryptfs': Function not implemented
févr. 13 10:58:16 pop-os systemd-modules-load[614]: Failed to look up module alias 'msr': Function not implemented
févr. 13 10:58:16 pop-os systemd[1]: Failed to start Load Kernel Modules.
févr. 13 10:58:16 pop-os systemd[1]: Failed to mount /boot/efi.
févr. 13 10:58:16 pop-os systemd[1]: Failed to mount /recovery.
févr. 13 11:03:01 pop-os /usr/bin/kernelstub[14772]: kernelstub.Drive     : ERROR    Could not find a block device for the a partition. This is a critical error and we cannot continue.
                                                      Traceback (most recent call last):
                                                        File "/usr/lib/python3/dist-packages/kernelstub/drive.py", line 56, in __init__
                                                          self.esp_fs = self.get_part_dev(self.esp_path)
                                                        File "/usr/lib/python3/dist-packages/kernelstub/drive.py", line 94, in get_part_dev
                                                          raise NoBlockDevError('Couldn\'t find the block device for %s' % path)
                                                      kernelstub.drive.NoBlockDevError: Couldn't find the block device for /boot/efi
févr. 13 11:03:01 pop-os /usr/bin/kernelstub[14775]: kernelstub.Drive     : ERROR    Could not find a block device for the a partition. This is a critical error and we cannot continue.
                                                      Traceback (most recent call last):
                                                        File "/usr/lib/python3/dist-packages/kernelstub/drive.py", line 56, in __init__
                                                          self.esp_fs = self.get_part_dev(self.esp_path)
                                                        File "/usr/lib/python3/dist-packages/kernelstub/drive.py", line 94, in get_part_dev
                                                          raise NoBlockDevError('Couldn\'t find the block device for %s' % path)
                                                      kernelstub.drive.NoBlockDevError: Couldn't find the block device for /boot/efi
févr. 13 11:04:10 pop-os /usr/bin/kernelstub[29143]: kernelstub.Drive     : ERROR    Could not find a block device for the a partition. This is a critical error and we cannot continue.
                                                      Traceback (most recent call last):
                                                        File "/usr/lib/python3/dist-packages/kernelstub/drive.py", line 56, in __init__
                                                          self.esp_fs = self.get_part_dev(self.esp_path)
                                                        File "/usr/lib/python3/dist-packages/kernelstub/drive.py", line 94, in get_part_dev
                                                          raise NoBlockDevError('Couldn\'t find the block device for %s' % path)
                                                      kernelstub.drive.NoBlockDevError: Couldn't find the block device for /boot/efi
févr. 13 11:04:10 pop-os /usr/bin/kernelstub[29146]: kernelstub.Drive     : ERROR    Could not find a block device for the a partition. This is a critical error and we cannot continue.
                                                      Traceback (most recent call last):
                                                        File "/usr/lib/python3/dist-packages/kernelstub/drive.py", line 56, in __init__
                                                          self.esp_fs = self.get_part_dev(self.esp_path)
                                                        File "/usr/lib/python3/dist-packages/kernelstub/drive.py", line 94, in get_part_dev
                                                          raise NoBlockDevError('Couldn\'t find the block device for %s' % path)
                                                      kernelstub.drive.NoBlockDevError: Couldn't find the block device for /boot/efi
févr. 13 11:04:24 pop-os systemd-cryptsetup[29239]: device-mapper: remove ioctl on cryptswap  failed: Device or resource busy

and this stackoverflow issue I found, you can try to comment out the lines in /etc/modules-load.d/cups-filters.conf to prevent systemd from loading lp, ppdev and parport_pc. I don't even know if you need them for printing (you can test your printer if the kernel loads after that change)

@Aisyk
Copy link
Author

Aisyk commented Feb 15, 2022 •
edited
Loading

Ok, so no problem for printing with the changes in /etc/modules-load.d/cups-filters.conf with 5.16.9-tkg-pds loaded (after reboot).

In the error message (mine and below), there are 2 other modules :

févr. 13 10:58:16 pop-os systemd-modules-load[614]: Failed to look up module alias '**ecryptfs**': Function not implemented
févr. 13 10:58:16 pop-os systemd-modules-load[614]: Failed to look up module alias '**msr**': Function not implemented

Is it matter ?

@AdelKS
Copy link
Collaborator

AdelKS commented Feb 15, 2022 •
edited
Loading

According to the manual, systemd-modules-load looks up for modules to load in the following paths:

/etc/modules-load.d/*.conf
/run/modules-load.d/*.conf
/usr/lib/modules-load.d/*.conf

See if ecryptfs and msr is in one of these folders in a .conf file, you can see which package owns that file.

Basically, linux-tkg seems to be providing extra kernel modules that are not in the original official Ubuntu image: this is normal as it is newer. But I do not understand how config files got automatically edited to load new kernel modules.

@AdelKS
Copy link
Collaborator

AdelKS commented Apr 18, 2022

Hello, I went through this issue again: have you tried sudo update-initramfs -k all ? Actually now that I think of it, maybe that's the problem 🤔

@rpatterson
Copy link

According to the manual, systemd-modules-load looks up for modules to load in the following paths:

In case this helps someone else find this, the above also helped me "dual booting" my Pop!_OS install under Microsoft's WSL.

@AdelKS
Copy link
Collaborator

AdelKS commented Nov 15, 2023

Hello, now that I think of it, did you have SELinux enabled on Ubuntu ?

@Aisyk
Copy link
Author

Aisyk commented Nov 16, 2023

Hello, now that I think of it, did you have SELinux enabled on Ubuntu ?

I no longer remember how I resolved my concerns (last year, and sorry for the silence). Maybe an install / uninstall kernels. I switch to Xanmod rather than TKG kernels.

I think it was related to the fact that the TKG kernel uses Selinux rules or modules from Fedora's specific configurations.

@Aisyk
Copy link
Author

Aisyk commented Nov 16, 2023

Too old, and this problem seems to be resolved (tkg -> xanmod kernels).

@Aisyk Aisyk closed this as completed Nov 16, 2023
# for free to join this conversation on GitHub. Already have an account? # to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@rpatterson @Aisyk @AdelKS