modules kernel

slcklnx · 05-24-2019, 03:26 PM

Hi, please tell me what you need to include in the Linux kernel to make kpartx work

Code:

kpartx -a -v Armbian_5.75_orangepi_win.img


/dev/mapper/control: open failed: no such device

failure to commnicate is available in the kernel
libdevmapper and kernel driver unknow version
device mapper prerequisites not met

[code]
I turned on

Code:

 --block devices [*]loopback device support

berndbausch · 05-24-2019, 06:57 PM

Something is wrong with device mapper. It looks like the version of the library used by kpartx is incompatible with the dm kernel module.

I doubt that you are reporting the precise error message. It has typos, and this sentence doesn’t make sense at all:

Code:

failure to commnicate is available in the kernel

Did you check the kernel message buffer?

slcklnx · 05-25-2019, 03:46 AM

Yes, there are typos. The flash drive was not mounted to transfer the file with the output. I do not know why it is so. so I wrote by hand.

Code:

Enable the block layer                                       
  │ │    -*-   Block layer SG support v4                                 │ │  
  │ │    []   Block layer SG support v4 helper lib                       │ │  
  │ │    []   Block layer data integrity support                         │ │  
  │ │    []   Zoned block device support                                 │ │  
  │ │    []   Block device command line partition parser                 │ │  
  │ │    []   Enable support for block device writeback throttling       │ │  
  │ │    []   Multiqueue writeback throttling                            │ │  
  │ │    []   Block layer debugging information in debugfs               │ │  
  │ │    []   Logic for interfacing with Opal enabled SEDs               │ │  
  │ │          Partition Types  --->

please tell me what contacts here need to be enabled for kpartx to work?

berndbausch · 05-25-2019, 07:03 AM

Quote:

Originally Posted by slcklnx

please tell me what contacts here need to be enabled for kpartx to work?

I am not sure what needs to be compiled into the kernel to enable device mapper. Perhaps CONFIG_BLK_DEV_DM=m? The kernel module is named dm_mod:

Code:

$ modinfo dm_mod
filename:       /lib/modules/3.10.0-957.12.1.el7.x86_64/kernel/drivers/md/dm-mod.ko.xz
license:        GPL
author:         Joe Thornber <dm-devel@redhat.com>
description:    device-mapper driver
alias:          devname:mapper/control
alias:          char-major-10-236
retpoline:      Y
rhelversion:    7.6
srcversion:     BA7CED77E4803DA1F325BC6
depends:
intree:         Y
vermagic:       3.10.0-957.12.1.el7.x86_64 SMP mod_unload modversions
signer:         CentOS Linux kernel signing key
sig_key:        2C:7C:17:70:5C:86:D4:20:80:50:D3:F5:54:56:9A:7B:D3:BF:D1:BF
sig_hashalgo:   sha256
...
$ ls -l /dev/mapper/control
crw-------. 1 root root 10, 236 May 25 11:14 /dev/mapper/control

Also, check the kernel message buffer. I am sure it contains more interesting information.