You are not logged in.

#1 2019-06-19 20:25:10

Simaryp
Member
Registered: 2018-04-28
Posts: 141

Clean up UEFI

Hi,

I updated my UEFI tonight and did some CMOS resets together with it. Till then I had Windows 10 running in parallel to Arch with a typical UEFI grub installation.
After the update I had to reconfigure the boot priority and found beside Windows three entries for Fedora, which I used prior to arch.

Selecting them yields to nothing. So I think I know what to do to get it running, i.e. booting from stick mount all the partitions and decrypt them and finally chroot to the system and to a grub update. But I wonder how I can get rid of the old corpses and get it clean. Maybe you have some link to some tutorial or anything like that. Hopefully I can fix it tomorrow.

Best Simaryp

Last edited by Simaryp (2019-06-19 20:26:12)

Offline

#2 2019-06-19 20:27:47

loqs
Member
Registered: 2014-03-06
Posts: 17,372

Re: Clean up UEFI

Unified_Extensible_Firmware_Interface#efibootmgr
`man efibootmgr` details the syntax for deleting an entry.

Offline

#3 2019-06-19 20:43:46

Simaryp
Member
Registered: 2018-04-28
Posts: 141

Re: Clean up UEFI

Ah I remember that I used this tool some years ago. Thx.

Offline

#4 2019-06-20 20:05:54

SteffNC
Member
Registered: 2019-05-22
Posts: 14

Re: Clean up UEFI

Perfect, thanks.

Offline

#5 2019-06-22 17:45:26

Simaryp
Member
Registered: 2018-04-28
Posts: 141

Re: Clean up UEFI

So I think I might need some further help. I got it running again, but I stumbled over some issues in the process.
So efibootmgr seems to not work on this machine. It always says "No BootOrder is set; Firmware will attempt recovery."

But I managed to add an entry via efi shell from arch install media and could boot again into my installed system.

So maybe I need to go into some details about the installation. I have root on a lvm on an encrypted luks container. I have an EFI partition which also contains the windows bootloader. And I have an extra boot partition.

During installation I mounted the boot partition to /boot. This is also done on every boot with an existing entry in the fstab.
During installation I also mounted the EFI partition to /boot/EFI. But this seems to be missing in the fstab. Now this folder is always empty.
ls gives the following:
$ ls /boot
EFI                               initramfs-linux-lts.img
grub                              intel-ucode.img
initramfs-linux-fallback.img      lost+found
initramfs-linux.img               vmlinuz-linux
initramfs-linux-lts-fallback.img  vmlinuz-linux-lts

And grub contains:
$ ls /boot/grub
fonts  grub.cfg  grubenv  locale  themes  x86_64-efi

The EFI partition contains my grub folder a Microsoft Folder and a Boot Folder I don't know what the Boot folder is good for maybe it's windows too? Files there are BOOTIA32.EFI, bootx64.efi, fbia32.efi, and fbx64.efi.

So should I add the EFI partition to /boot/EFI via fstab in order that grub works flawlessly? Seems a bit strange that the mounting was only done once while installing grub. So far it wasn't a problem also my laptop which is installed the same way works perfectly fine. My idea why it is so would be that on the EFI partition only grub is installed and knows that the .cfg and the images are on the boot partition. So when I update the system or make changes on the kernel the grub install on the EFI partition has not to be touched. Is this correct?
Second should I be worried that efibootmgr is not working on this machine?

Offline

#6 2019-06-22 20:03:50

d_fajardo
Member
Registered: 2017-07-28
Posts: 1,568

Re: Clean up UEFI

Second should I be worried that efibootmgr is not working on this machine?

No you shouldn't worry. This is I believe a firmware issue. There is no problem with efibootmgr. Some firmware are just better implemented than others. I have the same problem as yours so I just resort to UEFI-Shell. One hardly touches the NVRAM anyway once everything is setup.

Your Boot Folder contains .efi files and those files link to your NVRAM. One of them would be needed by grub - I assume but not entirely sure -  bootx64.efi. (What is in the grub folder?) You can backup the other efi files then delete them one by one and see if booting is affected. Same with Windows Folder if you no longer need it.

There shouldn't be a need to add the /boot/EFI directory. /boot is your EFI partition (I assume it's vfat formatted) and your initrams are already there.

So when I update the system or make changes on the kernel the grub install on the EFI partition has not to be touched. Is this correct?

I believe this to be correct although I don't use grub. mkinitcpio only updates the initram images. The EFI directory won't be touched on system update. The only time it will be touched is when grub itself is updated.

Offline

#7 2019-06-22 20:37:47

Simaryp
Member
Registered: 2018-04-28
Posts: 141

Re: Clean up UEFI

I think I didn't explain the partition scheme well enough.
This is the partition scheme of my SSD:
Gerät             Anfang      Ende  Sektoren  Größe Typ
/dev/nvme0n1p1      2048   1023999   1021952   499M Windows-Wiederherstellungsum
/dev/nvme0n1p2   1024000   1228799    204800   100M EFI-System
/dev/nvme0n1p3   1228800   1261567     32768    16M Microsoft reserviert
/dev/nvme0n1p4   1261568 737282047 736020480   351G Microsoft Basisdaten
/dev/nvme0n1p5 737282048 739379199   2097152     1G Linux-Dateisystem
/dev/nvme0n1p6 739379200 976773134 237393935 113,2G Linux LVM

p1 is Windows stuff
p2 is EFI
p4 is Windows
p5 is /boot
p6 is /

During installation I mounted p5 to /boot.
I created a folder /boot/EFI and mounted p2 to /boot/EFI.

Currently on start up only p6 and p5 are mounted. Consequently the mount point /boot/EFI is empty.

The content of /boot is:
[jacob@LiDe ~]$ ls /boot
amd-ucode.img
grub
initramfs-linux.img
vmlinuz-linux
EFI
initramfs-linux-fallback.img
lost+found

The grub folder contains:
$ ls /boot/grub
fonts  grub.cfg  grubenv  locale  themes  x86_64-efi

If I temporally mount p2 I see that it contains the following:
$ ls /mnt/blub/
EFI  mach_kernel  System
$ ls /mnt/blub/EFI/
Boot  grub_uefi  Microsoft

Grub_uefi contains only grubx64.efi. On my laptop that only runs Arch there exists only one file on the EFI partition namely /EFI/grub_uefi/grubx64.efi.

I hope that makes the situation clearer.

Offline

#8 2019-06-22 22:01:38

d_fajardo
Member
Registered: 2017-07-28
Posts: 1,568

Re: Clean up UEFI

Ok I see what you mean. Your actual EFI folder is an entirely separate partition in which case for grub to see gruvx64.efi, it probably needs to be mounted. Did you create this separate partition or was it created by Windows?
Question is are you able to boot without mounting p2 or does grub look for the grub64.efi? If you can then I feel there's no need to mount it and just leave it quiet for Windows use (but you can probably delete fbia32.efi, and fbx64.efi as they look like from Fedora). If grub starts looking for the efi file, then an entry in fstab will probably be the good option.
An alternative to try is to copy the grub_uefi directory to the /boot/EFI you just created as mount point.

Offline

#9 2019-06-23 05:47:13

Simaryp
Member
Registered: 2018-04-28
Posts: 141

Re: Clean up UEFI

I think on this machine it's windows created, on my laptop I set it up with arch as it's single boot.

You are right, booting works without a problem. My idea was that running grub-install creates the grubx64.efi file with all the details where to find grub.cfg etc. And when I update now the machine and run grub mkconfig only the files on p5 are touched, which makes the permanent mounting unnecessary.

So today I want to install arch on a new machine. When I get it right I could in contrast to the other machines just create an efi partition and mount this to /boot?

Offline

#10 2019-06-23 06:09:30

d_fajardo
Member
Registered: 2017-07-28
Posts: 1,568

Re: Clean up UEFI

When I get it right I could in contrast to the other machines just create an efi partition and mount this to /boot?

Yes or /efi. It mentions in the wiki /efi is preferred if one has a bootloader. I personally use /boot with a bootloader and I don't have any issue.

Offline

#11 2019-06-23 06:25:36

Simaryp
Member
Registered: 2018-04-28
Posts: 141

Re: Clean up UEFI

Ah ok, but I think I will still need a seperate boot partition, because of the encryption. I guess it will not work if /boot is inside the luks encryption.

This is what I am refering to:
https://wiki.archlinux.org/index.php/Dm … VM_on_LUKS

Last edited by Simaryp (2019-06-23 06:51:52)

Offline

#12 2019-06-23 07:20:43

d_fajardo
Member
Registered: 2017-07-28
Posts: 1,568

Re: Clean up UEFI

Yes of course, just like what the wiki says , the ESP is mandatory to be a separate partition, must be in the main partition table and must have readable format (FAT) for the UEFI to see it. However I think mounting it in your LUKS /boot directory shouldn't be a problem.

Offline

#13 2019-06-23 07:29:05

Simaryp
Member
Registered: 2018-04-28
Posts: 141

Re: Clean up UEFI

Yes, but I guess if I would mount it to /efi then the images and grub config might be placed into /boot and if nothing is mounted to /boot then it will be on the encrypted device and not accessible. Or will everything boot related be on the esp if I mount it to /efi?

Offline

#14 2019-06-23 07:57:25

d_fajardo
Member
Registered: 2017-07-28
Posts: 1,568

Re: Clean up UEFI

First to be clear, the EFI won't be encrypted. I don't use LUKS and I use /boot as my mountpoint not /efi so I don't have a certain answer. I don't use grub neither. If I were you I would have a good read of:

https://wiki.archlinux.org/index.php/installation_guide
https://wiki.archlinux.org/index.php/Dm … VM_on_LUKS
https://wiki.archlinux.org/index.php/EF … _partition
https://wiki.archlinux.org/index.php/GRUB

Like I said, I mount mine in /boot with rEFInd and there's no problem, but grub might want to be mounted in /efi. Follow the wiki, install grub, let grub look after itself would be my main advice.

Offline

#15 2019-06-23 08:53:54

Simaryp
Member
Registered: 2018-04-28
Posts: 141

Re: Clean up UEFI

I read through all of this already, but it's not completely clear. The Wiki regarding my encryption way quotes that I definitely need an extra boot partition which is not encrypted. This is obvious. The unclear question is, whether I can skip the creation of an extra boot partition and just mount esp to /boot do mkdir /boot/EFI and thats ist. Then the kernels and all grub stuff would be directly on esp and I would get rid of an extra partition. But the wiki says that for grub it would be common to mount esp to /efi. But then I would need /boot again I guess. At least I didn't read anywhere that /boot can be obsolete now.

Offline

#16 2019-06-23 13:12:31

d_fajardo
Member
Registered: 2017-07-28
Posts: 1,568

Re: Clean up UEFI

I'm still trying to understand what you mean. The non-encrypted, FAT32 partition will be the only partition you need to create assuming also that your disk partitioning is GPT.
If Grub wants to be in /efi, then mkdir efi (not another extra partition) on your root directory so you have /efi. Then mount the partition on /efi.

But the wiki also says:

Mount the EFI system partition and in the remainder of this section, substitute esp with its mount point.

So I would think if you want your mount point to be /boot, then it should work.

So the command the wiki describes:

# grub-install --target=x86_64-efi --efi-directory=esp --bootloader-id=GRUB

will mean:

# grub-install --target=x86_64-efi --efi-directory=/boot --bootloader-id=GRUB

I believe then after this command, it will be grub that will create the directory /boot/EFI and put everything in place so you won't need to do it by hand. At least that's how I understand it. Just make sure that the partition and mount point has an entry in fstab otherwise it won't be seen.

For rEFInd, my setup works the way I describe.

Last edited by d_fajardo (2019-06-23 13:16:58)

Offline

#17 2019-06-23 15:20:43

Simaryp
Member
Registered: 2018-04-28
Posts: 141

Re: Clean up UEFI

Hmm I don't know how to explain. Maybe the big problem is that the wiki explicitly says that for the used encryption way a extra boot partition is needed. Since it doesn't explicitly say it  can be identical to esp, I am a bit unsure about that point.

Maybe I should have a look on refind or other bootloaders too. Maybe it's even easier with them.

Last edited by Simaryp (2019-06-23 15:34:28)

Offline

#18 2019-06-29 16:43:10

Simaryp
Member
Registered: 2018-04-28
Posts: 141

Re: Clean up UEFI

I installed now arch on my wifes laptop but I am a bit struggeling with refind.
So I created an esp on /sdb1 and created an luks container on sdb2 with an lvm on it and the root partition as volgroup0/lv_root. I mounted esp to /boot and installed refind. I have an extra encrypted home partition but maybe that is not important yet.

The big problem that the kernel doesn't find the root partition. I tried to edit the refind_linux.conf to hand over the kernel parameter as I did with grub, but it doesn't work. I added something like: cryptdevice=/dev/sdb2:volgroup0 and cryptdevice=UUID=device-UUID:cryptlvm root=/dev/volgroup0/lv_root but neither worked.

I really don't understand the issue.

Offline

#19 2019-06-29 16:50:52

loqs
Member
Registered: 2014-03-06
Posts: 17,372

Re: Clean up UEFI

cryptdevice=UUID=device-UUID:cryptlvm root=/dev/volgroup0/lv_root

Have you checked device-UUID matches the UUID of the luks container?  What error is being produced?
What devices are opened when you are dropped to the rescue shell? (assuming boot reaches that point)

Offline

#20 2019-06-29 17:12:29

Simaryp
Member
Registered: 2018-04-28
Posts: 141

Re: Clean up UEFI

Yes it should be the same. See the following images that depict the situation. Unfortunately I can't use the rescue shell as my keyboard doesn't work at this point.
https://imgur.com/UgNkWfq
https://imgur.com/ILwYQAf

Offline

#21 2019-06-29 17:52:59

loqs
Member
Registered: 2014-03-06
Posts: 17,372

Re: Clean up UEFI

Mkinitcpio#Build_hooks is keyboard hook specified in mkinicpio.conf?  (to enable early keyboard usage)

Offline

#22 2019-06-29 17:55:40

SteffNC
Member
Registered: 2019-05-22
Posts: 14

Re: Clean up UEFI

I have not used UUID because I think it is easier to use:

NAME            MAJ:MIN RM   SIZE RO TYPE  MOUNTPOINT
sda               8:0    0 232,9G  0 disk  
├─sda1            8:1    0   512M  0 part  /boot
└─sda2            8:2    0 232,4G  0 part  
  └─main        254:0    0 232,4G  0 crypt 
    ├─main-swap 254:1    0     4G  0 lvm   [SWAP]
    └─main-root 254:2    0 228,4G  0 lvm   /

and my options are:

options cryptdevice=/dev/sda2:main:allow-discards root=/dev/mapper/main-root resume=/dev/mapper/main-swap root_trim=yes rw

Btw: I have used systemd-boot.

Offline

#23 2019-06-29 18:01:45

Simaryp
Member
Registered: 2018-04-28
Posts: 141

Re: Clean up UEFI

Yes Keyboard is far in the beginning. Hooks is like this HOOKS=(base udev autodetect keyboard keymap modconf block encrypt lvm2 filesystems fsck)

I don't know whether defining it over uuid or names makes a big difference right now. The problem is that kernel waits for the device but doesn't trigger decryption.

Last edited by Simaryp (2019-06-29 18:06:29)

Offline

#24 2019-06-29 18:21:08

loqs
Member
Registered: 2014-03-06
Posts: 17,372

Re: Clean up UEFI

I suspect the inability to use the keyboard is related to /lib/modules/4.19.56-1-lts/modules.devname
What is the output of

lsinitcpio /boot/initramfs-linux-lts.img

Offline

#25 2019-06-29 18:40:54

Simaryp
Member
Registered: 2018-04-28
Posts: 141

Re: Clean up UEFI

Output is:

buildconfig
config
keymap.bin
keymap.utf8
hooks
hooks/lvm2
hooks/encrypt
hooks/keymap
hooks/udev
init
init_functions
VERSION
lib64
sbin
bin
lib
usr
usr/lib64
usr/sbin
usr/bin
usr/bin/fsck
usr/bin/fsck.ext3
usr/bin/fsck.ext2
usr/bin/fsck.ext4
usr/bin/thin_trim
usr/bin/thin_rmap
usr/bin/thin_restore
usr/bin/thin_repair
usr/bin/thin_metadata_size
usr/bin/thin_ls
usr/bin/thin_dump
usr/bin/thin_delta
usr/bin/thin_check
usr/bin/cache_restore
usr/bin/cache_repair
usr/bin/cache_metadata_size
usr/bin/cache_dump
usr/bin/cache_check
usr/bin/pdata_tools
usr/bin/dmsetup
usr/bin/lvmetad
usr/bin/lvm
usr/bin/cryptsetup
usr/bin/systemd-tmpfiles
usr/bin/udevadm
usr/bin/switch_root
usr/bin/mount
usr/bin/blkid
usr/bin/modinfo
usr/bin/modprobe
usr/bin/lsmod
usr/bin/rmmod
usr/bin/insmod
usr/bin/depmod
usr/bin/kmod
usr/bin/yes
usr/bin/xz
usr/bin/xxd
usr/bin/which
usr/bin/wget
usr/bin/wc
usr/bin/vi
usr/bin/uptime
usr/bin/unzip
usr/bin/unshare
usr/bin/unlink
usr/bin/uniq
usr/bin/uname
usr/bin/umount
usr/bin/udhcpc6
usr/bin/udhcpc
usr/bin/truncate
usr/bin/true
usr/bin/touch
usr/bin/tftp
usr/bin/test
usr/bin/telnet
usr/bin/tee
usr/bin/tcpsvd
usr/bin/tar
usr/bin/tail
usr/bin/tac
usr/bin/sync
usr/bin/strings
usr/bin/stat
usr/bin/sort
usr/bin/sleep
usr/bin/shuf
usr/bin/sha512sum
usr/bin/sha256sum
usr/bin/sha1sum
usr/bin/sh
usr/bin/setfont
usr/bin/setfattr
usr/bin/seq
usr/bin/sed
usr/bin/run-init
usr/bin/route
usr/bin/rmdir
usr/bin/rm
usr/bin/resume
usr/bin/reboot
usr/bin/realpath
usr/bin/readlink
usr/bin/pwd
usr/bin/ps
usr/bin/printf
usr/bin/poweroff
usr/bin/ping6
usr/bin/ping
usr/bin/pidof
usr/bin/pgrep
usr/bin/paste
usr/bin/partprobe
usr/bin/openvt
usr/bin/nuke
usr/bin/nslookup
usr/bin/nsenter
usr/bin/nproc
usr/bin/nologin
usr/bin/netstat
usr/bin/nc
usr/bin/mv
usr/bin/mountpoint
usr/bin/mktemp
usr/bin/mkpasswd
usr/bin/mknod
usr/bin/mkfifo
usr/bin/mkdir
usr/bin/md5sum
usr/bin/lzop
usr/bin/lsscsi
usr/bin/ls
usr/bin/losetup
usr/bin/loadkmap
usr/bin/loadfont
usr/bin/ln
usr/bin/link
usr/bin/less
usr/bin/killall
usr/bin/kill
usr/bin/kbd_mode
usr/bin/iptunnel
usr/bin/iprule
usr/bin/iproute
usr/bin/ipneigh
usr/bin/iplink
usr/bin/ipaddr
usr/bin/ip
usr/bin/install
usr/bin/init
usr/bin/ifconfig
usr/bin/hexedit
usr/bin/hexdump
usr/bin/head
usr/bin/halt
usr/bin/gzip
usr/bin/grep
usr/bin/getopt
usr/bin/fsync
usr/bin/fstrim
usr/bin/fsfreeze
usr/bin/free
usr/bin/fatattr
usr/bin/false
usr/bin/fallocate
usr/bin/expr
usr/bin/env
usr/bin/echo
usr/bin/du
usr/bin/dmesg
usr/bin/dirname
usr/bin/df
usr/bin/dd
usr/bin/cut
usr/bin/cttyhack
usr/bin/cpio
usr/bin/cp
usr/bin/clear
usr/bin/chroot
usr/bin/chown
usr/bin/chmod
usr/bin/chgrp
usr/bin/cat
usr/bin/bzip2
usr/bin/blkdiscard
usr/bin/bc
usr/bin/basename
usr/bin/base64
usr/bin/awk
usr/bin/ash
usr/bin/arch
usr/bin/[
usr/bin/busybox
usr/lib
usr/lib/libe2p.so.2
usr/lib/libcom_err.so.2
usr/lib/libext2fs.so.2
usr/lib/libstdc++.so.6
usr/lib/libexpat.so.1
usr/lib/libncursesw.so.6
usr/lib/libreadline.so.8
usr/lib/libaio.so.1
usr/lib/libdevmapper-event.so.1.02
usr/lib/libgcc_s.so.1
usr/lib/libpopt.so.0
usr/lib/firmware
usr/lib/firmware/cavium
usr/lib/firmware/cavium/cnn55xx_se.fw
usr/lib/firmware/qat_c3xxx.bin
usr/lib/firmware/qat_c3xxx_mmp.bin
usr/lib/firmware/qat_c62x.bin
usr/lib/firmware/qat_c62x_mmp.bin
usr/lib/firmware/qat_895xcc.bin
usr/lib/firmware/qat_895xcc_mmp.bin
usr/lib/firmware/cxgb4
usr/lib/firmware/cxgb4/t4fw.bin
usr/lib/firmware/cxgb4/t5fw.bin
usr/lib/firmware/cxgb4/t6fw.bin
usr/lib/modprobe.d
usr/lib/modprobe.d/systemd.conf
usr/lib/udev
usr/lib/udev/scsi_id
usr/lib/udev/ata_id
usr/lib/udev/rules.d
usr/lib/udev/rules.d/69-dm-lvm-metad.rules
usr/lib/udev/rules.d/11-dm-initramfs.rules
usr/lib/udev/rules.d/95-dm-notify.rules
usr/lib/udev/rules.d/13-dm-disk.rules
usr/lib/udev/rules.d/11-dm-lvm.rules
usr/lib/udev/rules.d/10-dm.rules
usr/lib/udev/rules.d/80-drivers.rules
usr/lib/udev/rules.d/64-btrfs.rules
usr/lib/udev/rules.d/60-persistent-storage.rules
usr/lib/udev/rules.d/50-udev-default.rules
usr/lib/libm.so.6
usr/lib/libudev.so.1
usr/lib/libunistring.so.2
usr/lib/libgpg-error.so.0
usr/lib/libjson-c.so.4
usr/lib/libargon2.so.1
usr/lib/libssl.so.1.1
usr/lib/libdevmapper.so.1.02
usr/lib/libuuid.so.1
usr/lib/libattr.so.1
usr/lib/liblz4.so.1
usr/lib/libidn2.so.0
usr/lib/libseccomp.so.2
usr/lib/libip4tc.so.2
usr/lib/libgcrypt.so.20
usr/lib/libcryptsetup.so.12
usr/lib/libcap.so.2
usr/lib/libacl.so.1
usr/lib/libkmod.so.2
usr/lib/systemd
usr/lib/systemd/libsystemd-shared-242.so
usr/lib/systemd/systemd-udevd
usr/lib/librt.so.1
usr/lib/libmount.so.1
usr/lib/libblkid.so.1
usr/lib/libdl.so.2
usr/lib/libpthread.so.0
usr/lib/libcrypto.so.1.1
usr/lib/libz.so.1
usr/lib/liblzma.so.5
usr/lib/ld-linux-x86-64.so.2
usr/lib/libc.so.6
usr/lib/libcrypt.so.1
usr/lib/modules
usr/lib/modules/4.19.56-1-lts
usr/lib/modules/4.19.56-1-lts/modules.devname
usr/lib/modules/4.19.56-1-lts/modules.builtin.bin
usr/lib/modules/4.19.56-1-lts/modules.symbols.bin
usr/lib/modules/4.19.56-1-lts/modules.softdep
usr/lib/modules/4.19.56-1-lts/modules.alias.bin
usr/lib/modules/4.19.56-1-lts/modules.dep.bin
usr/lib/modules/4.19.56-1-lts/kernel
usr/lib/modules/4.19.56-1-lts/kernel/libcrc32c.ko
usr/lib/modules/4.19.56-1-lts/kernel/serio.ko
usr/lib/modules/4.19.56-1-lts/kernel/twofish_generic.ko
usr/lib/modules/4.19.56-1-lts/kernel/cmac.ko
usr/lib/modules/4.19.56-1-lts/kernel/dm-snapshot.ko
usr/lib/modules/4.19.56-1-lts/kernel/virtio.ko
usr/lib/modules/4.19.56-1-lts/kernel/serpent_generic.ko
usr/lib/modules/4.19.56-1-lts/kernel/cast6_generic.ko
usr/lib/modules/4.19.56-1-lts/kernel/md4.ko
usr/lib/modules/4.19.56-1-lts/kernel/chtls.ko
usr/lib/modules/4.19.56-1-lts/kernel/cast5_generic.ko
usr/lib/modules/4.19.56-1-lts/kernel/ansi_cprng.ko
usr/lib/modules/4.19.56-1-lts/kernel/ecdh_generic.ko
usr/lib/modules/4.19.56-1-lts/kernel/serio_raw.ko
usr/lib/modules/4.19.56-1-lts/kernel/usb-storage.ko
usr/lib/modules/4.19.56-1-lts/kernel/echainiv.ko
usr/lib/modules/4.19.56-1-lts/kernel/cast6-avx-x86_64.ko
usr/lib/modules/4.19.56-1-lts/kernel/dm-thin-pool.ko
usr/lib/modules/4.19.56-1-lts/kernel/sr_mod.ko
usr/lib/modules/4.19.56-1-lts/kernel/chacha20poly1305.ko
usr/lib/modules/4.19.56-1-lts/kernel/algif_skcipher.ko
usr/lib/modules/4.19.56-1-lts/kernel/lrw.ko
usr/lib/modules/4.19.56-1-lts/kernel/aegis256.ko
usr/lib/modules/4.19.56-1-lts/kernel/xhci-pci.ko
usr/lib/modules/4.19.56-1-lts/kernel/cast_common.ko
usr/lib/modules/4.19.56-1-lts/kernel/aegis128-aesni.ko
usr/lib/modules/4.19.56-1-lts/kernel/crc32c_generic.ko
usr/lib/modules/4.19.56-1-lts/kernel/crypto_engine.ko
usr/lib/modules/4.19.56-1-lts/kernel/michael_mic.ko
usr/lib/modules/4.19.56-1-lts/kernel/aes_ti.ko
usr/lib/modules/4.19.56-1-lts/kernel/af_alg.ko
usr/lib/modules/4.19.56-1-lts/kernel/ccp.ko
usr/lib/modules/4.19.56-1-lts/kernel/jbd2.ko
usr/lib/modules/4.19.56-1-lts/kernel/rmd128.ko
usr/lib/modules/4.19.56-1-lts/kernel/dm-log.ko
usr/lib/modules/4.19.56-1-lts/kernel/ccm.ko
usr/lib/modules/4.19.56-1-lts/kernel/virtio_crypto.ko
usr/lib/modules/4.19.56-1-lts/kernel/ghash-clmulni-intel.ko
usr/lib/modules/4.19.56-1-lts/kernel/sm4_generic.ko
usr/lib/modules/4.19.56-1-lts/kernel/camellia_generic.ko
usr/lib/modules/4.19.56-1-lts/kernel/deflate.ko
usr/lib/modules/4.19.56-1-lts/kernel/arc4.ko
usr/lib/modules/4.19.56-1-lts/kernel/crc32_generic.ko
usr/lib/modules/4.19.56-1-lts/kernel/uas.ko
usr/lib/modules/4.19.56-1-lts/kernel/qat_c3xxxvf.ko
usr/lib/modules/4.19.56-1-lts/kernel/poly1305_generic.ko
usr/lib/modules/4.19.56-1-lts/kernel/ccree.ko
usr/lib/modules/4.19.56-1-lts/kernel/poly1305-x86_64.ko
usr/lib/modules/4.19.56-1-lts/kernel/qat_c62x.ko
usr/lib/modules/4.19.56-1-lts/kernel/cdrom.ko
usr/lib/modules/4.19.56-1-lts/kernel/vmac.ko
usr/lib/modules/4.19.56-1-lts/kernel/aegis128l-aesni.ko
usr/lib/modules/4.19.56-1-lts/kernel/serpent-avx2.ko
usr/lib/modules/4.19.56-1-lts/kernel/serpent-avx-x86_64.ko
usr/lib/modules/4.19.56-1-lts/kernel/cbc.ko
usr/lib/modules/4.19.56-1-lts/kernel/crc32c-intel.ko
usr/lib/modules/4.19.56-1-lts/kernel/padlock-aes.ko
usr/lib/modules/4.19.56-1-lts/kernel/seed.ko
usr/lib/modules/4.19.56-1-lts/kernel/rtsx_pci_sdmmc.ko
usr/lib/modules/4.19.56-1-lts/kernel/dm-cache-smq.ko
usr/lib/modules/4.19.56-1-lts/kernel/tgr192.ko
usr/lib/modules/4.19.56-1-lts/kernel/twofish-x86_64-3way.ko
usr/lib/modules/4.19.56-1-lts/kernel/async_xor.ko
usr/lib/modules/4.19.56-1-lts/kernel/cts.ko
usr/lib/modules/4.19.56-1-lts/kernel/sha256-mb.ko
usr/lib/modules/4.19.56-1-lts/kernel/mbcache.ko
usr/lib/modules/4.19.56-1-lts/kernel/morus640_glue.ko
usr/lib/modules/4.19.56-1-lts/kernel/algif_rng.ko
usr/lib/modules/4.19.56-1-lts/kernel/async_pq.ko
usr/lib/modules/4.19.56-1-lts/kernel/842_decompress.ko
usr/lib/modules/4.19.56-1-lts/kernel/pcbc.ko
usr/lib/modules/4.19.56-1-lts/kernel/hid.ko
usr/lib/modules/4.19.56-1-lts/kernel/mmc_core.ko
usr/lib/modules/4.19.56-1-lts/kernel/tls.ko
usr/lib/modules/4.19.56-1-lts/kernel/sha1-mb.ko
usr/lib/modules/4.19.56-1-lts/kernel/ext4.ko
usr/lib/modules/4.19.56-1-lts/kernel/padlock-sha.ko
usr/lib/modules/4.19.56-1-lts/kernel/842.ko
usr/lib/modules/4.19.56-1-lts/kernel/xcbc.ko
usr/lib/modules/4.19.56-1-lts/kernel/firewire-sbp2.ko
usr/lib/modules/4.19.56-1-lts/kernel/crypto_simd.ko
usr/lib/modules/4.19.56-1-lts/kernel/mcryptd.ko
usr/lib/modules/4.19.56-1-lts/kernel/dm-bio-prison.ko
usr/lib/modules/4.19.56-1-lts/kernel/n5pf.ko
usr/lib/modules/4.19.56-1-lts/kernel/des3_ede-x86_64.ko
usr/lib/modules/4.19.56-1-lts/kernel/lz4hc.ko
usr/lib/modules/4.19.56-1-lts/kernel/dm-mirror.ko
usr/lib/modules/4.19.56-1-lts/kernel/qat_dh895xccvf.ko
usr/lib/modules/4.19.56-1-lts/kernel/qat_c3xxx.ko
usr/lib/modules/4.19.56-1-lts/kernel/crc16.ko
usr/lib/modules/4.19.56-1-lts/kernel/anubis.ko
usr/lib/modules/4.19.56-1-lts/kernel/cryptd.ko
usr/lib/modules/4.19.56-1-lts/kernel/morus640-sse2.ko
usr/lib/modules/4.19.56-1-lts/kernel/dm-cache.ko
usr/lib/modules/4.19.56-1-lts/kernel/raid6_pq.ko
usr/lib/modules/4.19.56-1-lts/kernel/ehci-hcd.ko
usr/lib/modules/4.19.56-1-lts/kernel/firewire-core.ko
usr/lib/modules/4.19.56-1-lts/kernel/crct10dif-pclmul.ko
usr/lib/modules/4.19.56-1-lts/kernel/morus1280.ko
usr/lib/modules/4.19.56-1-lts/kernel/xhci-hcd.ko
usr/lib/modules/4.19.56-1-lts/kernel/dm-crypt.ko
usr/lib/modules/4.19.56-1-lts/kernel/dm-mod.ko
usr/lib/modules/4.19.56-1-lts/kernel/tea.ko
usr/lib/modules/4.19.56-1-lts/kernel/qat_dh895xcc.ko
usr/lib/modules/4.19.56-1-lts/kernel/rng-core.ko
usr/lib/modules/4.19.56-1-lts/kernel/mmc_block.ko
usr/lib/modules/4.19.56-1-lts/kernel/virtio_blk.ko
usr/lib/modules/4.19.56-1-lts/kernel/sm3_generic.ko
usr/lib/modules/4.19.56-1-lts/kernel/morus1280-sse2.ko
usr/lib/modules/4.19.56-1-lts/kernel/aegis128.ko
usr/lib/modules/4.19.56-1-lts/kernel/rtsx_pci.ko
usr/lib/modules/4.19.56-1-lts/kernel/camellia-aesni-avx2.ko
usr/lib/modules/4.19.56-1-lts/kernel/aesni-intel.ko
usr/lib/modules/4.19.56-1-lts/kernel/async_tx.ko
usr/lib/modules/4.19.56-1-lts/kernel/crypto_user.ko
usr/lib/modules/4.19.56-1-lts/kernel/aegis256-aesni.ko
usr/lib/modules/4.19.56-1-lts/kernel/rmd320.ko
usr/lib/modules/4.19.56-1-lts/kernel/camellia-x86_64.ko
usr/lib/modules/4.19.56-1-lts/kernel/glue_helper.ko
usr/lib/modules/4.19.56-1-lts/kernel/des_generic.ko
usr/lib/modules/4.19.56-1-lts/kernel/libahci.ko
usr/lib/modules/4.19.56-1-lts/kernel/ccp-crypto.ko
usr/lib/modules/4.19.56-1-lts/kernel/ehci-pci.ko
usr/lib/modules/4.19.56-1-lts/kernel/pcrypt.ko
usr/lib/modules/4.19.56-1-lts/kernel/chacha20_generic.ko
usr/lib/modules/4.19.56-1-lts/kernel/twofish_common.ko
usr/lib/modules/4.19.56-1-lts/kernel/blowfish_generic.ko
usr/lib/modules/4.19.56-1-lts/kernel/lz4.ko
usr/lib/modules/4.19.56-1-lts/kernel/lz4_compress.ko
usr/lib/modules/4.19.56-1-lts/kernel/fscrypto.ko
usr/lib/modules/4.19.56-1-lts/kernel/intel_qat.ko
usr/lib/modules/4.19.56-1-lts/kernel/crc32-pclmul.ko
usr/lib/modules/4.19.56-1-lts/kernel/dm-bufio.ko
usr/lib/modules/4.19.56-1-lts/kernel/twofish-x86_64.ko
usr/lib/modules/4.19.56-1-lts/kernel/xts.ko
usr/lib/modules/4.19.56-1-lts/kernel/cfb.ko
usr/lib/modules/4.19.56-1-lts/kernel/sha1-ssse3.ko
usr/lib/modules/4.19.56-1-lts/kernel/ahci.ko
usr/lib/modules/4.19.56-1-lts/kernel/fcrypt.ko
usr/lib/modules/4.19.56-1-lts/kernel/sha512-ssse3.ko
usr/lib/modules/4.19.56-1-lts/kernel/rmd256.ko
usr/lib/modules/4.19.56-1-lts/kernel/twofish-avx-x86_64.ko
usr/lib/modules/4.19.56-1-lts/kernel/sd_mod.ko
usr/lib/modules/4.19.56-1-lts/kernel/wp512.ko
usr/lib/modules/4.19.56-1-lts/kernel/aes-x86_64.ko
usr/lib/modules/4.19.56-1-lts/kernel/libata.ko
usr/lib/modules/4.19.56-1-lts/kernel/sha256-ssse3.ko
usr/lib/modules/4.19.56-1-lts/kernel/aegis128l.ko
usr/lib/modules/4.19.56-1-lts/kernel/tcrypt.ko
usr/lib/modules/4.19.56-1-lts/kernel/atkbd.ko
usr/lib/modules/4.19.56-1-lts/kernel/serpent-sse2-x86_64.ko
usr/lib/modules/4.19.56-1-lts/kernel/async_memcpy.ko
usr/lib/modules/4.19.56-1-lts/kernel/chcr.ko
usr/lib/modules/4.19.56-1-lts/kernel/usbhid.ko
usr/lib/modules/4.19.56-1-lts/kernel/dm-persistent-data.ko
usr/lib/modules/4.19.56-1-lts/kernel/rmd160.ko
usr/lib/modules/4.19.56-1-lts/kernel/i8042.ko
usr/lib/modules/4.19.56-1-lts/kernel/khazad.ko
usr/lib/modules/4.19.56-1-lts/kernel/cxgb4.ko
usr/lib/modules/4.19.56-1-lts/kernel/chacha20-x86_64.ko
usr/lib/modules/4.19.56-1-lts/kernel/keywrap.ko
usr/lib/modules/4.19.56-1-lts/kernel/crc-itu-t.ko
usr/lib/modules/4.19.56-1-lts/kernel/algif_aead.ko
usr/lib/modules/4.19.56-1-lts/kernel/camellia-aesni-avx-x86_64.ko
usr/lib/modules/4.19.56-1-lts/kernel/algif_hash.ko
usr/lib/modules/4.19.56-1-lts/kernel/842_compress.ko
usr/lib/modules/4.19.56-1-lts/kernel/authenc.ko
usr/lib/modules/4.19.56-1-lts/kernel/blowfish_common.ko
usr/lib/modules/4.19.56-1-lts/kernel/async_raid6_recov.ko
usr/lib/modules/4.19.56-1-lts/kernel/morus1280-avx2.ko
usr/lib/modules/4.19.56-1-lts/kernel/scsi_mod.ko
usr/lib/modules/4.19.56-1-lts/kernel/qat_c62xvf.ko
usr/lib/modules/4.19.56-1-lts/kernel/sha3_generic.ko
usr/lib/modules/4.19.56-1-lts/kernel/xor.ko
usr/lib/modules/4.19.56-1-lts/kernel/libps2.ko
usr/lib/modules/4.19.56-1-lts/kernel/virtio_ring.ko
usr/lib/modules/4.19.56-1-lts/kernel/salsa20_generic.ko
usr/lib/modules/4.19.56-1-lts/kernel/morus1280_glue.ko
usr/lib/modules/4.19.56-1-lts/kernel/sha512-mb.ko
usr/lib/modules/4.19.56-1-lts/kernel/morus640.ko
usr/lib/modules/4.19.56-1-lts/kernel/authencesn.ko
usr/lib/modules/4.19.56-1-lts/kernel/lz4hc_compress.ko
usr/lib/modules/4.19.56-1-lts/kernel/dm-region-hash.ko
usr/lib/modules/4.19.56-1-lts/kernel/blowfish-x86_64.ko
usr/lib/modules/4.19.56-1-lts/kernel/cast5-avx-x86_64.ko
usr/local
usr/local/sbin
usr/local/bin
usr/local/lib
etc
etc/ld.so.cache
etc/lvm
etc/lvm/lvm.conf
etc/modprobe.d
etc/ld.so.conf
etc/initrd-release
etc/fstab
etc/mtab
var
var/run
tmp
run
dev
sys
proc
new_root

Offline

Board footer

Powered by FluxBB