Github messages for voidlinux
 help / color / mirror / Atom feed
From: xtraeme <xtraeme@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [ISSUE] [CLOSED] linux: Kernel is missing modules required to boot LVM/LUKS
Date: Mon, 17 Feb 2020 06:07:09 +0100	[thread overview]
Message-ID: <20200217050709.8U5p4m18Gt1uuunYPiMouglVrW62rNNgoqZLQyVTWXU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-720@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 955 bytes --]

Closed issue by lluixhi on void-packages repository

https://github.com/void-linux/void-packages/issues/720

Description:
### System

* xuname:  
`Void 4.17.4 x86_64 GenuineIntel uptodate rrrmF`
* package:  
`linux-4.16_1`

### Expected behavior
At boot time, the kernel has the modules necessary to mount an LVM/LUKS system without issue.
### Actual behavior
At boot time, an error is thrown saying the module "dm_crypt" is not found, and dracut complains about missing AES functions, despite the "crypt" module being loaded and grub successfully decrypting the boot partition.
### Steps to reproduce the behavior
1. Install void linux to an encrypted root partition
2. Attempt to boot

Can the kernel that's distributed by void include the requisite modules? It's troublesome to have to compile a kernel manually in order to boot my system.

This issue was previously reported at https://github.com/voidlinux/void-packages/issues/15177

           reply	other threads:[~2020-02-17  5:07 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-720@inbox.vuxu.org>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200217050709.8U5p4m18Gt1uuunYPiMouglVrW62rNNgoqZLQyVTWXU@z \
    --to=xtraeme@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).