View Issue Details

Jump to NotesJump to History
IDProjectCategoryView StatusDate SubmittedLast Update
0007587Kali LinuxGeneral Bugpublic2022-02-17 02:322022-02-17 02:35
Reportertryingharder Assigned Tosteev  
PrioritynormalSeveritymajorReproducibilityalways
Status resolvedResolutionno change required 
Product Version2022.1 
Summary0007587: update-initramfs, cryptsetup: ERROR : Couldn't resolve device /dev/root, Pinebook Pro
Description

Using Kali rolling on Pinebook Pro, installed to internal emmc storage, kernel is not being updated.
Cryptsetup gives error, see below

$ uname -a
Linux kali 5.14.2 0000001 SMP PREEMPT Fri Sep 10 00:27:56 UTC 2021 aarch64 GNU/Linux

apt reinstall linux-image-5.15.0-kali3-arm64

Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 0 not upgraded.
Need to get 54.4 MB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 tor+http://ftp.halifax.rwth-aachen.de/kali kali-rolling/main arm64 linux-image-5.15.0-kali3-arm64 arm64 5.15.15-2kali1 [54.4 MB]
Fetched 54.4 MB in 1min 27s (622 kB/s)
(Reading database ... 322937 files and directories currently installed.)
Preparing to unpack .../linux-image-5.15.0-kali3-arm64_5.15.15-2kali1_arm64.deb ...
Unpacking linux-image-5.15.0-kali3-arm64 (5.15.15-2kali1) over (5.15.15-2kali1) ...
Setting up linux-image-5.15.0-kali3-arm64 (5.15.15-2kali1) ...
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-5.15.0-kali3-arm64
cryptsetup: ERROR: Couldn't resolve device /dev/root
cryptsetup: WARNING: Couldn't determine root device

Steps To Reproduce

apt reinstall linux-image-5.15.0-kali3-arm64 (or latest newest version available for Kali)

Additional Information

Seems more odd because install was not encrypted AFAIK.

Activities

steev

steev

2022-02-17 02:35

manager   ~0015757

This is to be expected, at the present time, we don't support using the kali kernel on the Pinebook Pro. It's in the works, and likely will happen with 2022.2.

Issue History

Date Modified Username Field Change
2022-02-17 02:32 tryingharder New Issue
2022-02-17 02:35 steev Assigned To => steev
2022-02-17 02:35 steev Status new => resolved
2022-02-17 02:35 steev Resolution open => no change required
2022-02-17 02:35 steev Note Added: 0015757