| View previous topic :: View next topic |
| Author |
Message |
vcmota
Guru
Joined: 19 Jun 2017
Posts: 369
|
 Posted: Mon May 31, 2021 10:16 pm Post subject: |
 |
|
| When exactly does the kernel enters? It is before or after unlocking the LUKS partition? If it is before, than ok, it might be the kernel. If it is after,than it is the initrmfs, right? |
|
| Back to top |
|
 |
vcmota
Guru
Joined: 19 Jun 2017
Posts: 369
|
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54418
Location: 56N 3W
|
| Posted: Mon May 31, 2021 10:37 pm Post subject: |
|
|
vcmota,
From an earlier post.
| Code: | Disco /dev/nvme0n1: 476,94 GiB, 512110190592 bytes, 1000215216 setores
Modelo de disco: IM2P33F3A NVMe ADATA 512GB |
The first problem is that the kernel and initrd between them are not loading the hardware driver for /dev/nvme0n1, which is where your install it.
Please put your /usr/src/linux/.config file onto a pastebin site.
Get back into your chroot.
| Code: | emerge wgetpaste
wgetpaste /usr/src/linux/.config |
Then post the URL that wgetpaste gives you.
At the same time, tell us the command line that you use to build your kernel.
We know its but we need it all.
It will be in your back buffer. Type genke then press PageUp, to step back through matches.
For a quick look try | Code: | | grep NVME /usr/src/linux/.config[ |
| Code: | $ grep NVME /usr/src/linux/.config
# NVME Support
# CONFIG_BLK_DEV_NVME is not set |
is the wrong answer.
=m or =y is OK.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
vcmota
Guru
Joined: 19 Jun 2017
Posts: 369
|
| Posted: Tue Jun 01, 2021 3:03 am Post subject: |
|
|
Thank you NeddySeagoon.
| NeddySeagoon wrote: |
Get back into your chroot.
| Code: | emerge wgetpaste
wgetpaste /usr/src/linux/.config |
Then post the URL that wgetpaste gives you.
|
Here it goes.
| NeddySeagoon wrote: |
At the same time, tell us the command line that you use to build your kernel.
We know its but we need it all.
It will be in your back buffer. Type genke then press PageUp, to step back through matches. |
Here they are, both for the kernel and the initramfs:
| Code: |
(chroot) ubuntu-mate /usr/src/linux # make menuconfig
WARNING: unmet direct dependencies detected for ADI_AXI_ADC
Depends on [n]: IIO [=m] && HAS_IOMEM [=y] && OF [=n]
Selected by [m]:
- AD9467 [=m] && IIO [=m] && SPI [=y]
configuration written to .config
*** End of the configuration.
*** Execute 'make' to start the build or try 'make help'.
(chroot) ubuntu-mate /usr/src/linux # make menuconfig
WARNING: unmet direct dependencies detected for ADI_AXI_ADC
Depends on [n]: IIO [=m] && HAS_IOMEM [=y] && OF [=n]
Selected by [m]:
- AD9467 [=m] && IIO [=m] && SPI [=y]
*** End of the configuration.
*** Execute 'make' to start the build or try 'make help'.
(chroot) ubuntu-mate /usr/src/linux # genkernel --luks --lvm --busybox all
* Gentoo Linux Genkernel; Version 4.2.1
* Using genkernel configuration from '/etc/genkernel.conf' ...
* Running with options: --luks --lvm --busybox all
* Working with Linux kernel 5.10.27-gentoo-x86_64 for x86_64
* Using kernel config file '/etc/kernels/kernel-config-5.10.27-gentoo-x86_64' ...
*
* Note: The version above is subject to change (depends on config and status of kernel sources).
* kernel: >> Initializing ...
* >> Previous config backed up to .config--2021-05-31--21-27-32.bak
* >> Running 'make mrproper' ...
* >> Running 'make oldconfig' ...
* >> Compiling 5.10.27-gentoo-x86_64 bzImage ...
* >> Compiling 5.10.27-gentoo-x86_64 modules ...
* >> Installing 5.10.27-gentoo-x86_64 modules (and stripping) ...
* >> Generating module dependency data ...
* >> Saving config of successful build to '/etc/kernels/kernel-config-5.10.27-gentoo-x86_64' ...
* initramfs: >> Initializing ...
* >> Appending devices cpio data ...
* >> Appending base_layout cpio data ...
* >> Appending util-linux cpio data ...
* >> Appending eudev cpio data ...
* >> Appending devicemanager cpio data ...
* >> Appending auxiliary cpio data ...
* >> Appending busybox cpio data ...
* >> Appending luks cpio data ...
* >> Appending lvm cpio data ...
* >> Appending modprobed cpio data ...
* >> Appending modules cpio data ...
* >> Appending linker cpio data ...
* >> Deduping cpio ...
* >> Pre-generating initramfs' /etc/ld.so.cache ...
* >> Compressing cpio data (.xz) ...
* Kernel compiled successfully!
*
* --no-bootloader set; Skipping bootloader update ...
*
* Required kernel parameter:
*
* root=/dev/$ROOT
*
* Where $ROOT is the device node for your root partition as the
* one specified in /etc/fstab
* If you require Genkernel's hardware detection features, you MUST
* tell your bootloader to use the provided initramfs file '/boot/initramfs-5.10.27-gentoo-x86_64.img'.
* WARNING... WARNING... WARNING...
* Additional kernel parameters that *may* be required to boot properly:
* - Add "dolvm" for LVM support
* - Add "crypt_root=<device>" for LUKS-encrypted root
* - Add "crypt_swap=<device>" for LUKS-encrypted swap
* Do NOT report kernel bugs as genkernel bugs unless your bug
* is about the default genkernel configuration...
*
* Make sure you have the latest ~arch genkernel before reporting bugs.
(chroot) ubuntu-mate /usr/src/linux # genkernel --luks --lvm --busybox --install initramfs
* Gentoo Linux Genkernel; Version 4.2.1
* Using genkernel configuration from '/etc/genkernel.conf' ...
* Running with options: --luks --lvm --busybox --install initramfs
* Working with Linux kernel 5.10.27-gentoo-x86_64 for x86_64
* Using kernel config file '/etc/kernels/kernel-config-5.10.27-gentoo-x86_64' ...
* initramfs: >> Initializing ...
* >> Appending devices cpio data ...
* >> Appending base_layout cpio data ...
* >> Appending util-linux cpio data ...
* >> Appending eudev cpio data ...
* >> Appending devicemanager cpio data ...
* >> Appending auxiliary cpio data ...
* >> Appending busybox cpio data ...
* >> Appending luks cpio data ...
* >> Appending lvm cpio data ...
* >> Appending modprobed cpio data ...
* >> Appending modules cpio data ...
* >> Appending linker cpio data ...
* >> Deduping cpio ...
* >> Pre-generating initramfs' /etc/ld.so.cache ...
* >> Compressing cpio data (.xz) ...
*
* You will find the initramfs in '/boot/initramfs-5.10.27-gentoo-x86_64.img'.
* WARNING... WARNING... WARNING...
* Additional kernel parameters that *may* be required to boot properly:
* - Add "dolvm" for LVM support
* - Add "crypt_root=<device>" for LUKS-encrypted root
* - Add "crypt_swap=<device>" for LUKS-encrypted swap
* Do NOT report kernel bugs as genkernel bugs unless your bug
* is about the default genkernel configuration...
*
* Make sure you have the latest ~arch genkernel before reporting bugs.
(chroot) ubuntu-mate /usr/src/linux #
|
| NeddySeagoon wrote: |
For a quick look try | Code: | | grep NVME /usr/src/linux/.config[ |
| Code: | $ grep NVME /usr/src/linux/.config
# NVME Support
# CONFIG_BLK_DEV_NVME is not set |
is the wrong answer.
=m or =y is OK. |
I did that, and in fact NVME seems to have been enabled already. |
|
| Back to top |
|
|
vcmota
Guru
Joined: 19 Jun 2017
Posts: 369
|
| Posted: Tue Jun 01, 2021 11:09 am Post subject: |
|
|
There is a little more weirdness here. When I run "make menuconfig" and set the parameters I want and hit save, I can see that in /usr/src/linux/.config they have been saved. However, just after running "genkernel --luks --lvm --busybox all" I look into /usr/src/linux/.config and the parameters have been changed! Is that supposed to happen?
Here is my .config just after running "make menuconfig" and saving the changes:
| Code: |
(chroot) ubuntu-mate /usr/src/linux # grep "NVME" .config
# NVME Support
CONFIG_NVME_CORE=y
CONFIG_BLK_DEV_NVME=y
CONFIG_NVME_MULTIPATH=y
CONFIG_NVME_HWMON=y
CONFIG_NVME_FABRICS=y
CONFIG_NVME_FC=y
CONFIG_NVME_TCP=y
# CONFIG_NVME_TARGET is not set
# end of NVME Support
CONFIG_RTC_NVMEM=y
CONFIG_NVMEM=y
CONFIG_NVMEM_SYSFS=y
(chroot) ubuntu-mate /usr/src/linux #
|
But here it is just after running "genkernel --luks --lvm --busybox all"
| Code: |
(chroot) ubuntu-mate /usr/src/linux # grep "NVME" .config
# NVME Support
CONFIG_NVME_CORE=m
CONFIG_BLK_DEV_NVME=m
CONFIG_NVME_MULTIPATH=y
CONFIG_NVME_HWMON=y
CONFIG_NVME_FABRICS=m
CONFIG_NVME_RDMA=m
CONFIG_NVME_FC=m
CONFIG_NVME_TCP=m
CONFIG_NVME_TARGET=m
CONFIG_NVME_TARGET_PASSTHRU=y
CONFIG_NVME_TARGET_LOOP=m
CONFIG_NVME_TARGET_RDMA=m
CONFIG_NVME_TARGET_FC=m
CONFIG_NVME_TARGET_FCLOOP=m
CONFIG_NVME_TARGET_TCP=m
# end of NVME Support
CONFIG_RTC_NVMEM=y
CONFIG_NVMEM=y
CONFIG_NVMEM_SYSFS=y
(chroot) ubuntu-mate /usr/src/linux #
|
|
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54418
Location: 56N 3W
|
| Posted: Tue Jun 01, 2021 12:18 pm Post subject: |
|
|
vcmota,
| Code: | | genkernel --luks --lvm --busybox all |
looks OKish
| Code: | * >> Running 'make mrproper' ...
* >> Running 'make oldconfig' ... |
Destroys all of the existing binary files and replaces the .config with a genkernel default configuration.
That should be OK.
It does the kernel build ...
| Code: | * >> Compiling 5.10.27-gentoo-x86_64 bzImage ...
* >> Compiling 5.10.27-gentoo-x86_64 modules ...
* >> Installing 5.10.27-gentoo-x86_64 modules (and stripping) ...
* >> Generating module dependency data ...
* >> Saving config of successful build to '/etc/kernels/kernel-config-5.10.27-gentoo-x86_64' |
That last file is the configuration file actually used to build your kernel.
Its there that you need NVME set.
The initrd look good too. In particular | Code: | * >> Appending luks cpio data ...
* >> Appending lvm cpio data ...
|
I don't know what | Code: | | * --no-bootloader set; Skipping bootloader update ... |
means.
A couple of things. Your kernel has
| Code: | CONFIG_NVME_CORE=m
CONFIG_BLK_DEV_NVME=m |
so NVME support is a loadable module but you don't have /dev/nvme* in the initrd.
The help on CONFIG_BLK_DEV_NVME says | Code: | │ To compile this driver as a module, choose M here: the │
│ module will be called nvme. |
Boot your gentoo into the shell again and look for your /dev/nvme* devices.
If they are missing, run
It will either work, and you will get the prompt back with no message or there will be an error.
Post images of the error and the end of the output.
If all is well check for /dev/nvme* again now.
If your have your /dev/nvme* entries, we know that the module leading went wrong for some reason. If not we have the error messages that will tell the reasons.
Should /dev/nvme* exist, run
That might just work.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
vcmota
Guru
Joined: 19 Jun 2017
Posts: 369
|
| Posted: Tue Jun 01, 2021 2:10 pm Post subject: |
|
|
| NeddySeagoon wrote: | vcmota,
| Code: | | genkernel --luks --lvm --busybox all |
looks OKish
| Code: | * >> Running 'make mrproper' ...
* >> Running 'make oldconfig' ... |
Destroys all of the existing binary files and replaces the .config with a genkernel default configuration.
That should be OK.
It does the kernel build ...
| Code: | * >> Compiling 5.10.27-gentoo-x86_64 bzImage ...
* >> Compiling 5.10.27-gentoo-x86_64 modules ...
* >> Installing 5.10.27-gentoo-x86_64 modules (and stripping) ...
* >> Generating module dependency data ...
* >> Saving config of successful build to '/etc/kernels/kernel-config-5.10.27-gentoo-x86_64' |
That last file is the configuration file actually used to build your kernel.
Its there that you need NVME set.
The initrd look good too. In particular | Code: | * >> Appending luks cpio data ...
* >> Appending lvm cpio data ...
|
I don't know what | Code: | | * --no-bootloader set; Skipping bootloader update ... |
means.
A couple of things. Your kernel has
| Code: | CONFIG_NVME_CORE=m
CONFIG_BLK_DEV_NVME=m |
so NVME support is a loadable module but you don't have /dev/nvme* in the initrd.
The help on CONFIG_BLK_DEV_NVME says | Code: | │ To compile this driver as a module, choose M here: the │
│ module will be called nvme. |
Boot your gentoo into the shell again and look for your /dev/nvme* devices.
If they are missing, run
It will either work, and you will get the prompt back with no message or there will be an error.
Post images of the error and the end of the output.
If all is well check for /dev/nvme* again now.
If your have your /dev/nvme* entries, we know that the module leading went wrong for some reason. If not we have the error messages that will tell the reasons.
Should /dev/nvme* exist, run
That might just work. |
Just before your post I started compiling it without NVME as a module, following what the wiki seems to suggest. For this, I had to run the following commands:
| Code: |
(chroot) ubuntu-mate /usr/src/linux # genkernel --luks --lvm --busybox --menuconfig all
* Gentoo Linux Genkernel; Version 4.2.1
* Using genkernel configuration from '/etc/genkernel.conf' ...
* Running with options: --luks --lvm --busybox --menuconfig all
* Working with Linux kernel 5.10.27-gentoo-x86_64 for x86_64
* Using kernel config file '/etc/kernels/kernel-config-5.10.27-gentoo-x86_64' ...
*
* Note: The version above is subject to change (depends on config and status of kernel sources).
* kernel: >> Initializing ...
* >> Running 'make mrproper' ...
* >> Running 'make oldconfig' ...
* >> Invoking menuconfig ...
WARNING: unmet direct dependencies detected for ADI_AXI_ADC
Depends on [n]: IIO [=m] && HAS_IOMEM [=y] && OF [=n]
Selected by [m]:
- AD9467 [=m] && IIO [=m] && SPI [=y]
WARNING: unmet direct dependencies detected for ADI_AXI_ADC
Depends on [n]: IIO [=m] && HAS_IOMEM [=y] && OF [=n]
Selected by [m]:
- AD9467 [=m] && IIO [=m] && SPI [=y]
* >> Re-running 'make oldconfig' due to changed kernel options ...
* >> Compiling 5.10.27-gentoo-x86_64 bzImage ...
* >> Compiling 5.10.27-gentoo-x86_64 modules ...
* >> Installing 5.10.27-gentoo-x86_64 modules (and stripping) ...
* >> Generating module dependency data ...
* >> Saving config of successful build to '/etc/kernels/kernel-config-5.10.27-gentoo-x86_64' ...
* initramfs: >> Initializing ...
* >> Appending devices cpio data ...
* >> Appending base_layout cpio data ...
* >> Appending util-linux cpio data ...
* >> Appending eudev cpio data ...
* >> Appending devicemanager cpio data ...
* >> Appending auxiliary cpio data ...
* >> Appending busybox cpio data ...
* >> Appending luks cpio data ...
* >> Appending lvm cpio data ...
* >> Appending modprobed cpio data ...
* >> Appending modules cpio data ...
* >> Appending linker cpio data ...
* >> Deduping cpio ...
* >> Pre-generating initramfs' /etc/ld.so.cache ...
* >> Compressing cpio data (.xz) ...
* Kernel compiled successfully!
*
* --no-bootloader set; Skipping bootloader update ...
*
* Required kernel parameter:
*
* root=/dev/$ROOT
*
* Where $ROOT is the device node for your root partition as the
* one specified in /etc/fstab
* If you require Genkernel's hardware detection features, you MUST
* tell your bootloader to use the provided initramfs file '/boot/initramfs-5.10.27-gentoo-x86_64.img'.
* WARNING... WARNING... WARNING...
* Additional kernel parameters that *may* be required to boot properly:
* - Add "dolvm" for LVM support
* - Add "crypt_root=<device>" for LUKS-encrypted root
* - Add "crypt_swap=<device>" for LUKS-encrypted swap
*
* With support for several ext* filesystems available, it may be needed to
* add "rootfstype=ext3" or "rootfstype=ext4" to the list of boot parameters.
* Do NOT report kernel bugs as genkernel bugs unless your bug
* is about the default genkernel configuration...
*
* Make sure you have the latest ~arch genkernel before reporting bugs.
(chroot) ubuntu-mate /usr/src/linux #
(chroot) ubuntu-mate /usr/src/linux # genkernel --luks --lvm --install --busybox --kernel-config=/etc/kernels/kernel-config-5.10.27-gentoo-x86_64 initramfs
* Gentoo Linux Genkernel; Version 4.2.1
* Using genkernel configuration from '/etc/genkernel.conf' ...
* Running with options: --luks --lvm --install --busybox --kernel-config=/etc/kernels/kernel-config-5.10.27-gentoo-x86_64 initramfs
* Working with Linux kernel 5.10.27-gentoo-x86_64 for x86_64
* Using kernel config file '/etc/kernels/kernel-config-5.10.27-gentoo-x86_64' ...
* initramfs: >> Initializing ...
* >> Appending devices cpio data ...
* >> Appending base_layout cpio data ...
* >> Appending util-linux cpio data ...
* >> Appending eudev cpio data ...
* >> Appending devicemanager cpio data ...
* >> Appending auxiliary cpio data ...
* >> Appending busybox cpio data ...
* >> Appending luks cpio data ...
* >> Appending lvm cpio data ...
* >> Appending modprobed cpio data ...
* >> Appending modules cpio data ...
* >> Appending linker cpio data ...
* >> Deduping cpio ...
* >> Pre-generating initramfs' /etc/ld.so.cache ...
* >> Compressing cpio data (.xz) ...
*
* You will find the initramfs in '/boot/initramfs-5.10.27-gentoo-x86_64.img'.
* WARNING... WARNING... WARNING...
* Additional kernel parameters that *may* be required to boot properly:
* - Add "dolvm" for LVM support
* - Add "crypt_root=<device>" for LUKS-encrypted root
* - Add "crypt_swap=<device>" for LUKS-encrypted swap
*
* With support for several ext* filesystems available, it may be needed to
* add "rootfstype=ext3" or "rootfstype=ext4" to the list of boot parameters.
* Do NOT report kernel bugs as genkernel bugs unless your bug
* is about the default genkernel configuration...
*
* Make sure you have the latest ~arch genkernel before reporting bugs.
(chroot) ubuntu-mate /usr/src/linux # make install
sh ./arch/x86/boot/install.sh 5.10.27-gentoo-x86_64 arch/x86/boot/bzImage \
System.map "/boot"
(chroot) ubuntu-mate /usr/src/linux # grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Imagem Linux encontrada: /boot/vmlinuz-5.10.27-gentoo-x86_64
Imagem initrd encontrada: /boot/initramfs-5.10.27-gentoo-x86_64.img
Imagem Linux encontrada: /boot/vmlinuz-5.10.27-gentoo-x86_64.old
Imagem initrd encontrada: /boot/initramfs-5.10.27-gentoo-x86_64.img
Aviso: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
concluído
(chroot) ubuntu-mate /usr/src/linux #
|
since my impression is that genkernel was ignoring my sets made though a separate and prior "make menuconfig" command. The result was he same, with the same error. After that I entered shell and tried modprobe nvme, which, as you can see here, shows that there is no such module. It makes sense: if the above kernel compilation procedure worked as intended, nvme should not have been added as module. But if that is correct, why the error persisted?
Well, after that I read you post and now I am recompiling the kernel with nvme as module, by setting
| Code: |
Device Drivers →
NVME Support →
<M> NVM Express block device
|
to follow your exact steps and look at demesg.
Thank you again. |
|
| Back to top |
|
|
vcmota
Guru
Joined: 19 Jun 2017
Posts: 369
|
| Posted: Tue Jun 01, 2021 3:23 pm Post subject: |
|
|
Its just weird by now. I recompiled the kernel with nvme as module:
| Code: |
(chroot) ubuntu-mate /usr/src/linux # genkernel --luks --lvm --busybox --menuconfig all
* Gentoo Linux Genkernel; Version 4.2.1
* Using genkernel configuration from '/etc/genkernel.conf' ...
* Running with options: --luks --lvm --busybox --menuconfig all
* Working with Linux kernel 5.10.27-gentoo-x86_64 for x86_64
* Using kernel config file '/etc/kernels/kernel-config-5.10.27-gentoo-x86_64' ...
*
* Note: The version above is subject to change (depends on config and status of kernel sources).
* kernel: >> Initializing ...
* >> Running 'make mrproper' ...
* >> Running 'make oldconfig' ...
* >> Invoking menuconfig ...
WARNING: unmet direct dependencies detected for ADI_AXI_ADC
Depends on [n]: IIO [=m] && HAS_IOMEM [=y] && OF [=n]
Selected by [m]:
- AD9467 [=m] && IIO [=m] && SPI [=y]
* >> Compiling 5.10.27-gentoo-x86_64 bzImage ...
* >> Compiling 5.10.27-gentoo-x86_64 modules ...
* >> Installing 5.10.27-gentoo-x86_64 modules (and stripping) ...
* >> Generating module dependency data ...
* >> Saving config of successful build to '/etc/kernels/kernel-config-5.10.27-gentoo-x86_64' ...
* initramfs: >> Initializing ...
* >> Appending devices cpio data ...
* >> Appending base_layout cpio data ...
* >> Appending util-linux cpio data ...
* >> Appending eudev cpio data ...
* >> Appending devicemanager cpio data ...
* >> Appending auxiliary cpio data ...
* >> Appending busybox cpio data ...
* >> Appending luks cpio data ...
* >> Appending lvm cpio data ...
* >> Appending modprobed cpio data ...
* >> Appending modules cpio data ...
* >> Appending linker cpio data ...
* >> Deduping cpio ...
* >> Pre-generating initramfs' /etc/ld.so.cache ...
* >> Compressing cpio data (.xz) ...
* Kernel compiled successfully!
*
* --no-bootloader set; Skipping bootloader update ...
*
* Required kernel parameter:
*
* root=/dev/$ROOT
*
* Where $ROOT is the device node for your root partition as the
* one specified in /etc/fstab
* If you require Genkernel's hardware detection features, you MUST
* tell your bootloader to use the provided initramfs file '/boot/initramfs-5.10.27-gentoo-x86_64.img'.
* WARNING... WARNING... WARNING...
* Additional kernel parameters that *may* be required to boot properly:
* - Add "dolvm" for LVM support
* - Add "crypt_root=<device>" for LUKS-encrypted root
* - Add "crypt_swap=<device>" for LUKS-encrypted swap
*
* With support for several ext* filesystems available, it may be needed to
* add "rootfstype=ext3" or "rootfstype=ext4" to the list of boot parameters.
* Do NOT report kernel bugs as genkernel bugs unless your bug
* is about the default genkernel configuration...
*
* Make sure you have the latest ~arch genkernel before reporting bugs.
(chroot) ubuntu-mate /usr/src/linux # genkernel --luks --lvm --install --busybox --kernel-config=/etc/kernels/kernel-config-5.10.27-gentoo-x86_64 initramfs
* Gentoo Linux Genkernel; Version 4.2.1
* Using genkernel configuration from '/etc/genkernel.conf' ...
* Running with options: --luks --lvm --install --busybox --kernel-config=/etc/kernels/kernel-config-5.10.27-gentoo-x86_64 initramfs
* Working with Linux kernel 5.10.27-gentoo-x86_64 for x86_64
* Using kernel config file '/etc/kernels/kernel-config-5.10.27-gentoo-x86_64' ...
* initramfs: >> Initializing ...
* >> Appending devices cpio data ...
* >> Appending base_layout cpio data ...
* >> Appending util-linux cpio data ...
* >> Appending eudev cpio data ...
* >> Appending devicemanager cpio data ...
* >> Appending auxiliary cpio data ...
* >> Appending busybox cpio data ...
* >> Appending luks cpio data ...
* >> Appending lvm cpio data ...
* >> Appending modprobed cpio data ...
* >> Appending modules cpio data ...
* >> Appending linker cpio data ...
* >> Deduping cpio ...
* >> Pre-generating initramfs' /etc/ld.so.cache ...
* >> Compressing cpio data (.xz) ...
*
* You will find the initramfs in '/boot/initramfs-5.10.27-gentoo-x86_64.img'.
* WARNING... WARNING... WARNING...
* Additional kernel parameters that *may* be required to boot properly:
* - Add "dolvm" for LVM support
* - Add "crypt_root=<device>" for LUKS-encrypted root
* - Add "crypt_swap=<device>" for LUKS-encrypted swap
*
* With support for several ext* filesystems available, it may be needed to
* add "rootfstype=ext3" or "rootfstype=ext4" to the list of boot parameters.
* Do NOT report kernel bugs as genkernel bugs unless your bug
* is about the default genkernel configuration...
*
* Make sure you have the latest ~arch genkernel before reporting bugs.
(chroot) ubuntu-mate /usr/src/linux # make install
sh ./arch/x86/boot/install.sh 5.10.27-gentoo-x86_64 arch/x86/boot/bzImage \
System.map "/boot"
(chroot) ubuntu-mate /usr/src/linux # grub-mkconfig -o /boot/grub/grub.cfg
Generating grub configuration file ...
Imagem Linux encontrada: /boot/vmlinuz-5.10.27-gentoo-x86_64
Imagem initrd encontrada: /boot/initramfs-5.10.27-gentoo-x86_64.img
Imagem Linux encontrada: /boot/vmlinuz-5.10.27-gentoo-x86_64.old
Imagem initrd encontrada: /boot/initramfs-5.10.27-gentoo-x86_64.img
Aviso: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
concluído
(chroot) ubuntu-mate /usr/src/linux # grep "NVME" /etc/kernels/kernel-config-5.10.27-gentoo-x86_64
# NVME Support
CONFIG_NVME_CORE=m
CONFIG_BLK_DEV_NVME=m
CONFIG_NVME_MULTIPATH=y
CONFIG_NVME_HWMON=y
CONFIG_NVME_FABRICS=m
CONFIG_NVME_RDMA=m
CONFIG_NVME_FC=m
CONFIG_NVME_TCP=m
CONFIG_NVME_TARGET=m
CONFIG_NVME_TARGET_PASSTHRU=y
CONFIG_NVME_TARGET_LOOP=m
CONFIG_NVME_TARGET_RDMA=m
CONFIG_NVME_TARGET_FC=m
CONFIG_NVME_TARGET_FCLOOP=m
CONFIG_NVME_TARGET_TCP=m
# end of NVME Support
CONFIG_RTC_NVMEM=y
CONFIG_NVMEM=y
CONFIG_NVMEM_SYSFS=y
(chroot) ubuntu-mate /usr/src/linux #
|
and then restarted. The issue persisted, and than I typed modprobe nvme. As you can see here, no errors, meaning (I guess) the module has been loaded. However still no sign of them under /dev, and, as you can see here, ho sign of errors in dmesg output either. I will try to fully photograph dmesg output and put it here.
Update: Here is the complete output of dmesg. Sorry for the photos but I dont know other way of sharing this.
Thank you for your attention. |
|
| Back to top |
|
|
alamahant
Advocate
Joined: 23 Mar 2019
Posts: 3882
|
| Posted: Tue Jun 01, 2021 3:47 pm Post subject: |
|
|
| Code: |
When exactly does the kernel enters? It is before or after unlocking the LUKS partition? If it is before, than ok, it might be the kernel. If it is after,than it is the initrmfs, right?
|
| Code: |
efi-> grub -> kernel and initrd loaded from /boot to memory -> luks decrypt -> mounting / and filesystem, starting services etc and booting.
|
I think the initrd premounts the fs temporarily and then remounts it at /
Now as for your trouble I encourage you to use dracut to creae your initramfs.
In /etc/default/grub
comment out the Linux line and append
| Code: |
GRUB_CMDLINE_LINUX="cryptdevice=UUID=9c4d9bcb-3248-4214-9bbb-851df8ff6a1f:luks root=/dev/mapper/vg0-lvol1 rootfstype=ext4"
|
then run
| Code: |
emerge -av dracut
dracut -H --force --kver 5.10.27-gentoo-x86_64
#### check exact naming by running "ls /lib/modules"
grub-mkconfig -o /boot/grub/grub.cfg
reboot
|
Dracut is fantastic.
Smart fast and boots anything if it is bootable.
Also in your fstab you do NOT need uuid for your root and swap.Better use lvm naming.
_________________
Last edited by alamahant on Tue Jun 01, 2021 5:09 pm; edited 2 times in total |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54418
Location: 56N 3W
|
| Posted: Tue Jun 01, 2021 4:21 pm Post subject: |
|
|
vcmota,
You may be able to save files to a USB stick from the initrd shell. Using your root filesystem is not possible as it can't be mounted.
Looking through your images ...
Your running kernel was built on 1 June at 10:57. That's important. It looks like your newest kernel.
Do not use the kernel NTFS driver. Its harmless but its really read only support. At time 1.66669
device-mapper loads around 1.2066 sec.
At 1.347401 sec You have Run /init as init process.
With Arguments /init
dolvm
with environment ...
At 1.479770 sec your network card is discovered. There is a thing called a netconsole, that may be another way oy gettinig data out.
Your genkernel advertises itself as Gentoo Linux Genkernel; Version 4.2.1, which has been removed from the tree.
Do you actually have version 4.2.1 or version 4.2.1-r1?
Update genkernel if you need to and rebuild your kernel.
Grasping at straws ... have you ever edited the kernel .config file with $EDITOR ?
This used to justwork .
-- edit --
Please post your There may be a driver for your nwme hardware interface missisg.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
vcmota
Guru
Joined: 19 Jun 2017
Posts: 369
|
| Posted: Tue Jun 01, 2021 5:06 pm Post subject: |
|
|
| NeddySeagoon wrote: |
You may be able to save files to a USB stick from the initrd shell. Using your root filesystem is not possible as it can't be mounted.
|
Thank you again for your attention. I managed to do that. This is the full output of dmesg, and this is the file gksosreport.txt provided by the shell upon login.
| NeddySeagoon wrote: |
Do you actually have version 4.2.1 or version 4.2.1-r1?
|
I am chroot the system again and I will write it here.
| NeddySeagoon wrote: |
lspci -nnk
|
I am chroot the system again and I will write it here. |
|
| Back to top |
|
|
vcmota
Guru
Joined: 19 Jun 2017
Posts: 369
|
| Posted: Tue Jun 01, 2021 5:22 pm Post subject: |
|
|
| NeddySeagoon wrote: |
At 1.479770 sec your network card is discovered. There is a thing called a netconsole, that may be another way oy gettinig data out.
Your genkernel advertises itself as Gentoo Linux Genkernel; Version 4.2.1, which has been removed from the tree.
Do you actually have version 4.2.1 or version 4.2.1-r1?
Update genkernel if you need to and rebuild your kernel. |
Is the version in the stable tree:
| Code: |
(chroot) ubuntu-mate / # equery list genkernel
* Searching for genkernel ...
[IP-] [ ] sys-kernel/genkernel-4.2.1-r1:0
(chroot) ubuntu-mate / #
|
| NeddySeagoon wrote: |
lspci -nnk |
Here is the lspci --nnk provided by the Ubuntu hosting the chroot:
| Code: |
ubuntu-mate@ubuntu-mate:~/Desktop$ sudo lspci -nnk
0000:00:00.0 Host bridge [0600]: Intel Corporation Device [8086:9a14] (rev 01)
Subsystem: Dell Device [1028:0a03]
0000:00:02.0 VGA compatible controller [0300]: Intel Corporation Device [8086:9a49] (rev 01)
DeviceName: Onboard - Video
Subsystem: Dell Device [1028:0a03]
Kernel driver in use: i915
Kernel modules: i915
0000:00:04.0 Signal processing controller [1180]: Intel Corporation Device [8086:9a03] (rev 01)
Subsystem: Dell Device [1028:0a03]
Kernel driver in use: proc_thermal
Kernel modules: processor_thermal_device
0000:00:06.0 System peripheral [0880]: Intel Corporation Device [8086:09ab]
0000:00:07.0 PCI bridge [0604]: Intel Corporation Device [8086:9a23] (rev 01)
Kernel driver in use: pcieport
0000:00:0a.0 Signal processing controller [1180]: Intel Corporation Device [8086:9a0d] (rev 01)
Subsystem: Dell Device [1028:0a03]
0000:00:0d.0 USB controller [0c03]: Intel Corporation Device [8086:9a13] (rev 01)
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
0000:00:0d.2 USB controller [0c03]: Intel Corporation Device [8086:9a1b] (rev 01)
Subsystem: Device [2222:1111]
Kernel driver in use: thunderbolt
Kernel modules: thunderbolt
0000:00:0e.0 RAID bus controller [0104]: Intel Corporation Volume Management Device NVMe RAID Controller [8086:9a0b]
Subsystem: Dell Volume Management Device NVMe RAID Controller [1028:0a03]
Kernel driver in use: vmd
Kernel modules: vmd
0000:00:12.0 Serial controller [0700]: Intel Corporation Device [8086:a0fc] (rev 20)
Subsystem: Dell Device [1028:0a03]
Kernel driver in use: intel_ish_ipc
Kernel modules: intel_ish_ipc
0000:00:14.0 USB controller [0c03]: Intel Corporation Device [8086:a0ed] (rev 20)
Kernel driver in use: xhci_hcd
Kernel modules: xhci_pci
0000:00:14.2 RAM memory [0500]: Intel Corporation Device [8086:a0ef] (rev 20)
Subsystem: Dell Device [1028:0a03]
0000:00:14.3 Network controller [0280]: Intel Corporation Device [8086:a0f0] (rev 20)
Subsystem: Intel Corporation Device [8086:42a4]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi
0000:00:15.0 Serial bus controller [0c80]: Intel Corporation Device [8086:a0e8] (rev 20)
Subsystem: Dell Device [1028:0a03]
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
0000:00:15.1 Serial bus controller [0c80]: Intel Corporation Device [8086:a0e9] (rev 20)
Subsystem: Dell Device [1028:0a03]
Kernel driver in use: intel-lpss
Kernel modules: intel_lpss_pci
0000:00:16.0 Communication controller [0780]: Intel Corporation Device [8086:a0e0] (rev 20)
Subsystem: Dell Device [1028:0a03]
Kernel driver in use: mei_me
Kernel modules: mei_me
0000:00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:a0bc] (rev 20)
Kernel driver in use: pcieport
0000:00:1c.7 PCI bridge [0604]: Intel Corporation Device [8086:a0bf] (rev 20)
Kernel driver in use: pcieport
0000:00:1f.0 ISA bridge [0601]: Intel Corporation Device [8086:a082] (rev 20)
Subsystem: Dell Device [1028:0a03]
0000:00:1f.3 Multimedia audio controller [0401]: Intel Corporation Device [8086:a0c8] (rev 20)
Subsystem: Dell Device [1028:0a03]
Kernel driver in use: sof-audio-pci
Kernel modules: snd_hda_intel, snd_sof_pci
0000:00:1f.4 SMBus [0c05]: Intel Corporation Device [8086:a0a3] (rev 20)
Subsystem: Dell Device [1028:0a03]
Kernel driver in use: i801_smbus
Kernel modules: i2c_i801
0000:00:1f.5 Serial bus controller [0c80]: Intel Corporation Device [8086:a0a4] (rev 20)
Subsystem: Dell Device [1028:0a03]
0000:2b:00.0 3D controller [0302]: NVIDIA Corporation GP108M [GeForce MX330] [10de:1d16] (rev a1)
Kernel driver in use: nouveau
Kernel modules: nvidiafb, nouveau
0000:2c:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:0a03]
Kernel driver in use: r8169
Kernel modules: r8169
10000:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:9a09] (rev 01)
Kernel driver in use: pcieport
10000:e1:00.0 Non-Volatile memory controller [0108]: ADATA Technology Co., Ltd. Device [1cc1:33f3] (rev 03)
Subsystem: ADATA Technology Co., Ltd. Device [1cc1:33f3]
Kernel driver in use: nvme
Kernel modules: nvme
ubuntu-mate@ubuntu-mate:~/Desktop$
|
And here is the lspci --nnk provided by the chroot:
| Code: |
(chroot) ubuntu-mate / # lspci -nnk
0000:00:00.0 Host bridge [0600]: Intel Corporation 11th Gen Core Processor Host Bridge/DRAM Registers [8086:9a14] (rev 01)
Subsystem: Dell 11th Gen Core Processor Host Bridge/DRAM Registers [1028:0a03]
lspci: Unable to load libkmod resources: error -2
0000:00:02.0 VGA compatible controller [0300]: Intel Corporation Iris Xe Graphics [8086:9a49] (rev 01)
DeviceName: Onboard - Video
Subsystem: Dell Iris Xe Graphics [1028:0a03]
Kernel driver in use: i915
0000:00:04.0 Signal processing controller [1180]: Intel Corporation Device [8086:9a03] (rev 01)
Subsystem: Dell Device [1028:0a03]
Kernel driver in use: proc_thermal
0000:00:06.0 System peripheral [0880]: Intel Corporation Device [8086:09ab]
0000:00:07.0 PCI bridge [0604]: Intel Corporation Tiger Lake-LP Thunderbolt 4 PCI Express Root Port #0 [8086:9a23] (rev 01)
Kernel driver in use: pcieport
0000:00:0a.0 Signal processing controller [1180]: Intel Corporation Device [8086:9a0d] (rev 01)
Subsystem: Dell Device [1028:0a03]
0000:00:0d.0 USB controller [0c03]: Intel Corporation Tiger Lake-LP Thunderbolt 4 USB Controller [8086:9a13] (rev 01)
Kernel driver in use: xhci_hcd
0000:00:0d.2 USB controller [0c03]: Intel Corporation Tiger Lake-LP Thunderbolt 4 NHI #0 [8086:9a1b] (rev 01)
Subsystem: Device [2222:1111]
Kernel driver in use: thunderbolt
0000:00:0e.0 RAID bus controller [0104]: Intel Corporation Volume Management Device NVMe RAID Controller [8086:9a0b]
Subsystem: Dell Volume Management Device NVMe RAID Controller [1028:0a03]
Kernel driver in use: vmd
0000:00:12.0 Serial controller [0700]: Intel Corporation Tiger Lake-LP Integrated Sensor Hub [8086:a0fc] (rev 20)
Subsystem: Dell Tiger Lake-LP Integrated Sensor Hub [1028:0a03]
Kernel driver in use: intel_ish_ipc
0000:00:14.0 USB controller [0c03]: Intel Corporation Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller [8086:a0ed] (rev 20)
Kernel driver in use: xhci_hcd
0000:00:14.2 RAM memory [0500]: Intel Corporation Tiger Lake-LP Shared SRAM [8086:a0ef] (rev 20)
Subsystem: Dell Tiger Lake-LP Shared SRAM [1028:0a03]
0000:00:14.3 Network controller [0280]: Intel Corporation Wi-Fi 6 AX201 [8086:a0f0] (rev 20)
Subsystem: Intel Corporation Wi-Fi 6 AX201 [8086:42a4]
Kernel driver in use: iwlwifi
0000:00:15.0 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #0 [8086:a0e8] (rev 20)
Subsystem: Dell Tiger Lake-LP Serial IO I2C Controller [1028:0a03]
Kernel driver in use: intel-lpss
0000:00:15.1 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP Serial IO I2C Controller #1 [8086:a0e9] (rev 20)
Subsystem: Dell Tiger Lake-LP Serial IO I2C Controller [1028:0a03]
Kernel driver in use: intel-lpss
0000:00:16.0 Communication controller [0780]: Intel Corporation Tiger Lake-LP Management Engine Interface [8086:a0e0] (rev 20)
Subsystem: Dell Tiger Lake-LP Management Engine Interface [1028:0a03]
Kernel driver in use: mei_me
0000:00:1c.0 PCI bridge [0604]: Intel Corporation Device [8086:a0bc] (rev 20)
Kernel driver in use: pcieport
0000:00:1c.7 PCI bridge [0604]: Intel Corporation Tiger Lake-LP PCI Express Root Port #8 [8086:a0bf] (rev 20)
Kernel driver in use: pcieport
0000:00:1f.0 ISA bridge [0601]: Intel Corporation Tiger Lake-LP LPC Controller [8086:a082] (rev 20)
Subsystem: Dell Tiger Lake-LP LPC Controller [1028:0a03]
0000:00:1f.3 Multimedia audio controller [0401]: Intel Corporation Tiger Lake-LP Smart Sound Technology Audio Controller [8086:a0c8] (rev 20)
Subsystem: Dell Tiger Lake-LP Smart Sound Technology Audio Controller [1028:0a03]
Kernel driver in use: sof-audio-pci
0000:00:1f.4 SMBus [0c05]: Intel Corporation Tiger Lake-LP SMBus Controller [8086:a0a3] (rev 20)
Subsystem: Dell Tiger Lake-LP SMBus Controller [1028:0a03]
Kernel driver in use: i801_smbus
0000:00:1f.5 Serial bus controller [0c80]: Intel Corporation Tiger Lake-LP SPI Controller [8086:a0a4] (rev 20)
Subsystem: Dell Tiger Lake-LP SPI Controller [1028:0a03]
0000:2b:00.0 3D controller [0302]: NVIDIA Corporation GP108M [GeForce MX330] [10de:1d16] (rev a1)
Kernel driver in use: nouveau
0000:2c:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:0a03]
Kernel driver in use: r8169
10000:e0:06.0 PCI bridge [0604]: Intel Corporation 11th Gen Core Processor PCIe Controller [8086:9a09] (rev 01)
Kernel driver in use: pcieport
10000:e1:00.0 Non-Volatile memory controller [0108]: ADATA Technology Co., Ltd. Device [1cc1:33f3] (rev 03)
Subsystem: ADATA Technology Co., Ltd. Device [1cc1:33f3]
Kernel driver in use: nvme
(chroot) ubuntu-mate / #
|
Finally, the chroot see the disks properly I guess:
| Code: |
(chroot) ubuntu-mate / # fdisk -l
.
.
.
Disco /dev/nvme0n1: 476,94 GiB, 512110190592 bytes, 1000215216 setores
Modelo de disco: IM2P33F3A NVMe ADATA 512GB
Unidades: setor de 1 * 512 = 512 bytes
Tamanho de setor (lógico/físico): 512 bytes / 512 bytes
Tamanho E/S (mínimo/ótimo): 512 bytes / 512 bytes
Tipo de rótulo do disco: gpt
Identificador do disco: EE371963-AFCB-C04D-B3D3-9E3E5F26E840
Dispositivo Início Fim Setores Tamanho Tipo
/dev/nvme0n1p1 2048 1050623 1048576 512M Sistema EFI
/dev/nvme0n1p2 1050624 1000215182 999164559 476,4G Linux sistema de arquivos
.
.
.
|
but it is running another kernel:
| Code: |
(chroot) ubuntu-mate / # uname -r
5.8.0-43-generic
(chroot) ubuntu-mate / #
|
|
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54418
Location: 56N 3W
|
| Posted: Tue Jun 01, 2021 5:56 pm Post subject: |
|
|
vcmota,
Your genkernel version is good.
Here are the key lines from lspci.
| Code: | 10000:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:9a09] (rev 01)
Kernel driver in use: pcieport
10000:e1:00.0 Non-Volatile memory controller [0108]: ADATA Technology Co., Ltd. Device [1cc1:33f3] (rev 03)
Subsystem: ADATA Technology Co., Ltd. Device [1cc1:33f3]
Kernel driver in use: nvme |
With pcieport and nvme loaded, the initrd should list
| Code: | /dev/nvme0n1
/dev/nvme0n1p1
/dev/nvme0n1p2 |
That's the whole device and the two partitions.
After that appears, the LUKS container on /dev/nvme0n1p2 can be unlocked.
It all looks good, it just doesn't work. Which brings me back to my question about using a text editor on the kernel .config file?
Did you ever do that?
It often produces a broken hard to diagnose kernel problem because some kernel symbols force as many as 10 other symbols. The config system does that. You are unlikely to get that right in a text editor.
-- edit --
| Code: | | [ 2021-06-01 16:55:55.064250 ] [!!] Could not find the root in . |
Is very telling for what it does not say.
Just before the full stop should be a list of every block device the kernel can see. You have an empty list.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
vcmota
Guru
Joined: 19 Jun 2017
Posts: 369
|
| Posted: Tue Jun 01, 2021 6:29 pm Post subject: |
|
|
Thank you NeddySeagoon for your reply.
| NeddySeagoon wrote: |
It all looks good, it just doesn't work. Which brings me back to my question about using a text editor on the kernel .config file?
Did you ever do that?
It often produces a broken hard to diagnose kernel problem because some kernel symbols force as many as 10 other symbols. The config system does that. You are unlikely to get that right in a text editor.
|
I dont understand your questions. You are asking if I tried to change myself the .config file directly, "by hand"? Or are you questioning if I know how to do it? The answer for both questions would be no.
| NeddySeagoon wrote: |
-- edit --
| Code: | | [ 2021-06-01 16:55:55.064250 ] [!!] Could not find the root in . |
Is very telling for what it does not say.
Just before the full stop should be a list of every block device the kernel can see. You have an empty list. |
Take a look an what I just did here. I booted the computer with a gentoo minimal install usb, which, as shown in the picture, has the same kernel that I am trying to install in the new machine. However, you can see here (the output of lspci -nnk) that the liveusb DOES NOT recognize my NVME disks either. Then I tiped "modprobe nvme", which returned no errors. And this is the output of lspci -nnk AFTER entering the modprobe nvme command. Again, it does not even see the nvme disks. Does that indicates that this is a compatibility issue between this kernel and the precise model of the disks I have? And if so, trying an older kernel, maybe the same 5.8 that is packed in the ubuntu liveusb, wouldn't be a possible solution?
Thank you again for your attention. |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54418
Location: 56N 3W
|
| Posted: Tue Jun 01, 2021 7:40 pm Post subject: |
|
|
vcmota,
Yes, I was asking if you had edited the kernel .config by hand as I have seen that produce this sort of error.
is used to produce the Gentoo live media kernel. So whatever the problem is, I'm not suprised that your genkernel kernel and the live media kernel behave the same.
However, we have learned something.
| tail of working lspci: | 0000:2c:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:0a03]
Kernel driver in use: r8169
Kernel modules: r8169
10000:e0:06.0 PCI bridge [0604]: Intel Corporation Device [8086:9a09] (rev 01)
Kernel driver in use: pcieport
10000:e1:00.0 Non-Volatile memory controller [0108]: ADATA Technology Co., Ltd. Device [1cc1:33f3] (rev 03)
Subsystem: ADATA Technology Co., Ltd. Device [1cc1:33f3]
Kernel driver in use: nvme
Kernel modules: nvme |
Compared with
| tail of failing lspci: | 2c:00.0 Ethernet controller [0200]: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [10ec:8168] (rev 15)
Subsystem: Dell RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [1028:0a03]
Kernel driver in use: r8169
Kernel modules: r8169 |
The genkernel kernel only shows PCI domain zero but your nvme is in domain 10000. So the genkernel kernel is not showing all of your PCI domains.
The numbers at the left mean | Code: | | [<domain>:]<bus>:<dev>.<func> |
-- edit --
Random thought. There are lots of kernel parameters that can affect PCI behaviour. Boot the working ubuntu kernel and post the kernel command line from its dmesg.
Lets see if it posses anything special to the kernel at boot time.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail.
Last edited by NeddySeagoon on Tue Jun 01, 2021 8:04 pm; edited 1 time in total |
|
| Back to top |
|
|
vcmota
Guru
Joined: 19 Jun 2017
Posts: 369
|
| Posted: Tue Jun 01, 2021 7:57 pm Post subject: |
|
|
| Thank you NeddySeagoon for your reply. But there was some edition error and I can not understand what you have typed. Could you please make it readable? |
|
| Back to top |
|
|
Whissi
Retired Dev
Joined: 12 Jan 2011
Posts: 222
|
| Posted: Tue Jun 01, 2021 7:59 pm Post subject: |
|
|
Please run | Code: | | genkernel --kernel-config=default --kernel-append-localversion=-clean1 all |
which should create a new kernel/initramfs forcing genkernel's default kernel.config and will create new /lib/modules/$KV dir just in case...
_________________
Regards,
Whissi |
|
| Back to top |
|
|
NeddySeagoon
Administrator
Joined: 05 Jul 2003
Posts: 54418
Location: 56N 3W
|
| Posted: Tue Jun 01, 2021 8:06 pm Post subject: |
|
|
vcmota,
What Whissi said. He knows genkernel very well.
_________________
Regards,
NeddySeagoon
Computer users fall into two groups:-
those that do backups
those that have never had a hard drive fail. |
|
| Back to top |
|
|
vcmota
Guru
Joined: 19 Jun 2017
Posts: 369
|
| Posted: Tue Jun 01, 2021 8:21 pm Post subject: |
|
|
| Thank you Whissi and NeddySeagoon for your help. The compilation in running right now. After that I just run "genkernel --luks --lvm --busybox --install initramfs" and "grub-mkconfig"? |
|
| Back to top |
|
|
Whissi
Retired Dev
Joined: 12 Jan 2011
Posts: 222
|
| Posted: Tue Jun 01, 2021 8:23 pm Post subject: |
|
|
| vcmota wrote: | | Thank you Whissi and NeddySeagoon for your help. The compilation in running right now. After that I just run "genkernel --luks --lvm --busybox --install initramfs" and "grub-mkconfig"? |
No! If you need LUKS and LVM support (busybox is enabled by default) just do
| Code: | | genkernel --luks --lvm --kernel-config=default --kernel-append-localversion=-clean1 all |
This will install by default and "all" will create kernel and initramfs in one run.
_________________
Regards,
Whissi |
|
| Back to top |
|
|
vcmota
Guru
Joined: 19 Jun 2017
Posts: 369
|
| Posted: Tue Jun 01, 2021 8:44 pm Post subject: |
|
|
OK, thank you Whissi. Just to be sure, the next steps will be simply:
[1] make install
[2] grub-mkconfig -o /boot/grub/grub.cfg
Is that correct? Thank you again. |
|
| Back to top |
|
|
Whissi
Retired Dev
Joined: 12 Jan 2011
Posts: 222
|
| Posted: Tue Jun 01, 2021 9:17 pm Post subject: |
|
|
No, genkernel will take care of "make install" if you do not specify "--no-install".
You can even tell genkernel to update grub (set bootloader in /etc/genkernel.conf). If you haven't done that yet, just manually update grub with shown grub command.
tl;dr
Do not run [1] but [2] if you haven't set bootloader in /etc/genkernel.conf.
_________________
Regards,
Whissi |
|
| Back to top |
|
|
vcmota
Guru
Joined: 19 Jun 2017
Posts: 369
|
| Posted: Tue Jun 01, 2021 11:08 pm Post subject: |
|
|
It did not solve the problem. And again, even after calling "modprobe nvme", showing no errors, the disk does not appears under /dev. Also, I could not plug a USB, I tried all 4 that I have without any live iso on it and the shell did not recognize them. I try formating as ext4, ext2, etc... and nothing, probably the kernel built has no USB support but this is just a guess. What I did was photograph the entire /run/initramfs/gkosreport.txt, so please accept my apologies in advance for the large number of photos. Here they are.
Any idea would be very welcome, and thank you again for your attention. |
|
| Back to top |
|
|
vcmota
Guru
Joined: 19 Jun 2017
Posts: 369
|
| Posted: Wed Jun 02, 2021 12:32 am Post subject: |
|
|
Look what I just found out:
https://bbs.archlinux.org/viewtopic.php?id=257375
Although it is in archlinux it seems related, and apparently has been solved through a firmware update. Also, as stated in the beggining of their thread, it started to break after kernel 5.6.
-----
Update
The same package used in the solution for arch exists for gentoo, fwupd, but I cant make it work:
| Code: |
(chroot) ubuntu-mate / # fwupdmgr get-devices
Authorization not available. Check if polkit service is running or see debug message for more information.
Failed to connect to daemon: Não foi possível conectar: Arquivo ou diretório inexistente
(chroot) ubuntu-mate / # rc-service fwupd start
* WARNING: fwupd is already starting
(chroot) ubuntu-mate / # fwupdmgr get-devices
Authorization not available. Check if polkit service is running or see debug message for more information.
Failed to connect to daemon: Não foi possível conectar: Arquivo ou diretório inexistente
|
It seems that I have to setup selinux to do so, but I am pretty sure this requires a reboot, which has been made impossible due to the main issue. |
|
| Back to top |
|
|
vcmota
Guru
Joined: 19 Jun 2017
Posts: 369
|
| Posted: Wed Jun 02, 2021 2:45 am Post subject: |
|
|
| I just tried an older kernel, 5.4;109, the first on the stable tree before 5.10.27, and did not work. Same problem, still nothing under /dev. |
|
| Back to top |
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
Installing Gentoo
