Booting 6.6 or 6.7 kernels with Ventoy [Solved]

[fehlix]

@fehlix I started from scratch. First I wiped out the partitions ventoy creates with gparted and left the thumb drive blank.

Maybe, use "-g" for gpt, when installing Ventoy.
At least, that's what I always do. It might make it easier for the PC-UEFI system in order to avoid mix of MBR/dos and GPT type of partition tables. In theory it may not needed, but OEM's might handle / testing legacy MBR + UEFI/GPT not always properly.

[siamhie]

Maybe, use "-g" for gpt, when installing Ventoy.
At least, that's what I always do. It might make it easier for the PC-UEFI system in order to avoid mix of MBR/dos and GPT type of partition tables. In theory it may not needed, but OEM's might handle / testing legacy MBR + UEFI/GPT not always properly.

Still errors with the 6.7.2 kernel (didn't test it with the 6.6.11 kernel).

At least the quick fix for ventoy users is to install a 6.5 kernel from the repo and tell MX Snapshot to use that for it's live kernel image.

[fehlix]

Seems to work here:
installed kernel all mx-build and installed from mx-repos:

Code: Select all

demo@mx1: ~/Desktop
$ dpkg -l | grep ^i | grep linux-im
ii  linux-image-6.6.11-amd64-unsigned     6.6.11-1~mx23ahs 
ii  linux-image-6.6.12-1-liquorix-amd64   6.6-16~mx23ahs   
ii  linux-image-6.7.1-1-liquorix-amd64    6.7-1~mx23ahs    
ii  linux-image-liquorix-amd64            6.7-1~mx23ahs    

booting kernel is linux-image-6.6.11-amd64-unsigned
on ventoy with snapshot-iso::

Code: Select all

demo@mx1: ~/Desktop
$ lsblk -f  /dev/loop0 /dev/sda
NAME       FSTYPE   FSVER LABEL   UUID
loop0      squashfs 4.0
sda
├─sda1     exfat    1.0   Ventoy  8F66-4F40
│ └─ventoy
├─sda2     vfat     FAT16 VTOYEFI 3F32-27F5
└─sda3     exfat    1.0   exFAT   A23D-7E12

neofetch:

Code: Select all

demo@mx1: ~/Desktop
$ neofetch
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@   demo@mx1
@@@@@@@@@@@@%*+--:------=+*%@@@@@@@@@@@@   --------
@@@@@@@@@#=. .-+#%@@@@@%#*+--=#@@@@@@@@@   OS: MX x86_64
@@@@@@@+. .=%@@@@@@@@@@@@@@@@*-:+@@@@@@@   Host: KVM/QEMU (Standard PC (Q35 + ICH9, 20
@@@@@*.  *@@@@@@@@@@@@@@@@@@@@@%-.*@@@@@   Kernel: 6.6.11-amd64
@@@@-  -@@@@@@@@@@@@@@@@@@@@@@@#:  -@@@@   Uptime: 20 mins
@@@:  -@@@@@@@=.*@@@@@@@@@@@@%-   = :@@@   Packages: 2389 (dpkg)
@@=  .@@@@@@@@%- :%@@@@@@@@@+   -%@# =@@   Shell: bash 5.2.15
@%   +@@@@@@@@@@#. =@@@@@@*.  .*@@@@. %@   Resolution: 1600x900
@+   *@@@@@@*..*@@+  *@@%-   =@@@@@@- +@   DE: Xfce 4.18
@=   *@@@@%-    -%@@- :=   -%@@@@@@@: +@   WM: Xfwm4
@+   :@@@=        +@@=   .#@@@@@@@@%  *@   WM Theme: mx-comfort
@%    +*.          .:     *@@#: +@@:  @@   Theme: mx-comfort [GTK2], Adwaita [GTK3]
@@+                   :%@- :-    ::  +@@   Icons: Papirus-mxblue-darkpanes [GTK2], Adw
@@@-                  .=@@=         -@@@   Terminal: xfce4-terminal
@@+.                     .           +@@   Terminal Font: Liberation Mono 11
%=..:.................::...........:..-%   CPU: Intel Xeon E3-1240 V2 (4) @ 3.403GHz
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@   GPU: 00:02.0 Red Hat, Inc. QXL paravirtual

Maybe I'm doing something differently, need to figure out to reproduce the show stopper you are seeing.

[fehlix]

This with is Ventoy boot with linux-image-6.7.2-1-liquorix-amd64 / 6.7-2.1~bookworm (directly from liquorix repo)

Code: Select all

$ neofetch
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@   demo@mx1
@@@@@@@@@@@@%*+--:------=+*%@@@@@@@@@@@@   --------
@@@@@@@@@#=. .-+#%@@@@@%#*+--=#@@@@@@@@@   OS: MX x86_64
@@@@@@@+. .=%@@@@@@@@@@@@@@@@*-:+@@@@@@@   Host: KVM/QEMU (Standard PC (Q35 + ICH9,
@@@@@*.  *@@@@@@@@@@@@@@@@@@@@@%-.*@@@@@   Kernel: 6.7.2-1-liquorix-amd64
@@@@-  -@@@@@@@@@@@@@@@@@@@@@@@#:  -@@@@   Uptime: 25 mins
@@@:  -@@@@@@@=.*@@@@@@@@@@@@%-   = :@@@   Packages: 2391 (dpkg)
@@=  .@@@@@@@@%- :%@@@@@@@@@+   -%@# =@@   Shell: bash 5.2.15
@%   +@@@@@@@@@@#. =@@@@@@*.  .*@@@@. %@   Resolution: 1600x900
@+   *@@@@@@*..*@@+  *@@%-   =@@@@@@- +@   DE: Xfce 4.18
@=   *@@@@%-    -%@@- :=   -%@@@@@@@: +@   WM: Xfwm4
@+   :@@@=        +@@=   .#@@@@@@@@%  *@   WM Theme: mx-comfort
@%    +*.          .:     *@@#: +@@:  @@   Theme: mx-comfort [GTK2], Adwaita [GTK3]
@@+                   :%@- :-    ::  +@@   Icons: Papirus-mxblue-darkpanes [GTK2],
@@@-                  .=@@=         -@@@   Terminal: xfce4-terminal
@@+.                     .           +@@   Terminal Font: Liberation Mono 11
%=..:.................::...........:..-%   CPU: Intel Xeon E3-1240 V2 (4) @ 3.403GH
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@   GPU: 00:02.0 Red Hat, Inc. QXL paravirtu

installed kernels:

Code: Select all

demo@mx1: ~/Desktop
$ dpkg -l | grep linux-image
ii  linux-image-6.6.11-amd64-unsigned     6.6.11-1~mx23ahs
ii  linux-image-6.6.12-1-liquorix-amd64   6.6-16~mx23ahs
ii  linux-image-6.7.1-1-liquorix-amd64    6.7-1~mx23ahs
ii  linux-image-6.7.2-1-liquorix-amd64    6.7-2.1~bookworm
ii  linux-image-liquorix-amd64            6.7-1~mx23ahs

booted the snapshot iso on Ventoy with toram, so the squashfs is mounted in ram:

Code: Select all

demo@mx1: ~/Desktop
$ lsblk -f /dev/loop0 /dev/sda
NAME       FSTYPE   FSVER LABEL   UUID
loop0      squashfs 4.0
sda
├─sda1     exfat    1.0   Ventoy  8F66-4F40
│ └─ventoy
├─sda2     vfat     FAT16 VTOYEFI 3F32-27F5
└─sda3     exfat    1.0   exFAT   A23D-7E12

Maybe it boots here b/c the snapshot is created from booted iso on ventoy, so any by ventoy used additional kernel modules are detected and added to the initrd of the snapshot - but need to verify this theory.
And if so, we may just add the missing modules, before creating the snapshot on a non-veantoy booted system.

[fehlix]

OK, great I have now also an non-booting snaspshot with liqorix kernel on Ventoy:

Liquorix-device-mapper-driver-mssing.jpg

which means I have two snaphot's with the identical kernel one boots the other not.
Now, I need only to figure out what's missing on the one which does not boot with Ventoy.
and why it was not added as in the other snapshot which boots.
So, I guess I have a Sunday riddle to figure out.

[siamhie]

I'm going to try two other distros that use the 6.6 kernel by default. AVL-MXe 23.2 and something called Redcore Linux Hardened 2401.

I'll report what I find out.

[siamhie]

OK, great I have now also an non-booting snaspshot with liqorix kernel on Ventoy:
Liquorix-device-mapper-driver-mssing.jpg
which means I have two snaphot's with the identical kernel one boots the other not.
Now, I need only to figure out what's missing on the one which does not boot with Ventoy.
and why it was not added as in the other snapshot which boots.
So, I guess I have a Sunday riddle to figure out.

I was getting the same message about the missing device-mapper in the kernel.

[siamhie]

No issues with these three ISO's and the 6.6 kernel.


MX-23.2 ahs

mx-23.2.png

AVL-MXe 23.2

avl-mxe.jpg

some distro named Redcore

redcore.png

[fehlix]

I was getting the same message about the missing device-mapper in the kernel.

Maybe try this build on MX23: mx-snapshot_24.01.01_amd64.deb
which should avoid the Ventoy show stopper.
Pls confirm, so we can push it to the repos.
Thanks

[siamhie]

I was getting the same message about the missing device-mapper in the kernel.

Maybe try this build on MX23: mx-snapshot_24.01.01_amd64.deb
which should avoid the Ventoy show stopper.
Pls confirm, so we can push it to the repos.
Thanks

Worked like a charm @fehlix .

I created a new snapshot with liquorix 6.7.2 as the live kernel and it booted up to the desktop with no issues. Thank you for the fix.