Page 1 of 1
Booting 6.6 or 6.7 kernels with Ventoy
Posted: Fri Jan 26, 2024 12:58 pm
by siamhie
Currently the latest version of Ventoy (1.0.97 released 2024-01-24) will not boot snapshots made with the 6.6 or 6.7 kernels.
(tested using Debian 6.6.11, Liquorix 6.6.13 and Liquorix 6.7.2)
Here's a workaround until Ventoy catches up. Install ANY 6.5 kernel from the repo be it Debian 6.5.13 or Liquorix 6.5.11.
When you open MX Snapshot, go to the bottom and click on Change live kernel and select the 6.5 kernel.
Then proceed with creating your snapshot.
ventoy2.jpg
*Note: snapshots flashed with MX Live USB Maker DO work with the 6.6 and 6.7 kernels as another option.
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Fri Jan 26, 2024 2:12 pm
by Stevo
We do have a set of Liquorix 6.7 in our ahs-staging section, and we have confirmed we have working rtl-8XXX-dkms, Nvidia, broadcom-sta-dkms, and at least virtualbox 7.0.14 (probably 7.0.10, too) packages for it.
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Fri Jan 26, 2024 6:05 pm
by fehlix
Just checked and updated the Ventoy-usb key with latest version1.0.97
Seems to work with snapshot and current 6.6.12 liquorix kernel from ahs-repo:
neofetch:
mx-23.2-ahs-isoboot-ventoy.jpg
lsblk with ventoys partitions
mx-23.2-ahs-isoboot-ventoy-lsblk.jpg
and also with MX-Snapshot with next 6.7.1 liquorix kernel available probably shortly
at the mx-ahs repo's:
mx-23.2-ventoy.jpg
mx-23.2-ventoy-lsblk.jpg
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Fri Jan 26, 2024 7:11 pm
by siamhie
Stevo wrote: Fri Jan 26, 2024 2:12 pm
We do have a set of Liquorix 6.7 in our ahs-staging section, and we have confirmed we have working rtl-8XXX-dkms, Nvidia, broadcom-sta-dkms, and at least virtualbox 7.0.14 (probably 7.0.10, too) packages for it.
Good to hear.
This is a regard to Ventoy users (just as myself).
As long as the user knows that they will need to use MX Live USB Maker to create their snapshots OR install an ISO that uses the 6.6-6.7 kernel.
*side note: I plan on adding a SATA SSD to my system so I can install
AVL-MXe which uses the 6.6 kernel by default.
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Fri Jan 26, 2024 7:32 pm
by siamhie
fehlix wrote: Fri Jan 26, 2024 6:05 pm
Just checked and updated the Ventoy-usb key with latest version1.0.97
@felixq78 How does one do that? (update the key)?
I'm generally curious.
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Fri Jan 26, 2024 7:54 pm
by fehlix
siamhie wrote: Fri Jan 26, 2024 7:32 pm
fehlix wrote: Fri Jan 26, 2024 6:05 pm
Just checked and updated the Ventoy-usb key with latest version1.0.97
@felixq78 How does one do that? (update the key)?
I'm generally curious.
* get latest tar.gz release file from Ventoy
* checksum (sha256sum) verify and extract the Ventoy archive
* open terminal within the extracted directory of the Ventoy archive
* plugin the existing Ventoy USB-key/-stick
* get the device name e.g like /dev/sdf, of the Ventoy USB-key
lsblk -nrd -o LABLE,TRAN,NAME
* run the provided Ventoy2Disk.sh :
-> first list existing version on existing USB-device
./Ventoy2Disk.sh -l /dev/sdf
-> upgrade/update to the new version
sudo ./Ventoy2Disk.sh -u /dev/sdf
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Sat Jan 27, 2024 12:26 pm
by siamhie
fehlix wrote: Fri Jan 26, 2024 7:54 pm
* run the provided Ventoy2Disk.sh :
-> first list existing version on existing USB-device
./Ventoy2Disk.sh -l /dev/sdf
-> upgrade/update to the new version
sudo ./Ventoy2Disk.sh -u /dev/sdf
@fehlix I did that at first when I saw I had version 1.0.94 installed. I just now double checked and I'm on the 1.0.97 version.
Code: Select all
sudo ./Ventoy2Disk.sh -l /dev/sdb
[sudo] password for siamhie:
**********************************************
Ventoy: 1.0.97 x86_64
longpanda admin@ventoy.net
https://www.ventoy.net
**********************************************
Ventoy Version in Disk: 1.0.97
Disk Partition Style : MBR
Secure Boot Support : YES
What I could do is just reinstall ventoy to my thumb drive and try again. It only has one snapshot and all three MX-23.2 desktop ISO's on it,
so I can move those off the thumb drive and on to my hard drive for the time being.
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Sat Jan 27, 2024 12:56 pm
by siamhie
Reinstalling ventoy (1.0.97) didn't work.
Code: Select all
╔═[siamhie@flux23]═[09:30 27/01/24]═════════════════════════════════════[~/Downloads/ventoy-1.0.97]
╚═> sudo ./Ventoy2Disk.sh -I /dev/sdb
**********************************************
Ventoy: 1.0.97 x86_64
longpanda admin@ventoy.net
https://www.ventoy.net
**********************************************
Disk : /dev/sdb
Model: Kingston DataTraveler 3.0 (scsi)
Size : 28 GB
Style: MBR
Attention:
You will install Ventoy to /dev/sdb.
All the data on the disk /dev/sdb will be lost!!!
Continue? (y/n) y
All the data on the disk /dev/sdb will be lost!!!
Double-check. Continue? (y/n) y
Create partitions on /dev/sdb by parted in MBR style ...
Done
Wait for partitions ...
partition exist OK
create efi fat fs /dev/sdb2 ...
mkfs.fat 4.2 (2021-01-31)
success
Wait for partitions ...
/dev/sdb1 exist OK
/dev/sdb2 exist OK
partition exist OK
Format partition 1 /dev/sdb1 ...
mkexfatfs 1.3.0
Creating... done.
Flushing... done.
File system created successfully.
mkexfatfs success
writing data to disk ...
sync data ...
esp partition processing ...
Install Ventoy to /dev/sdb successfully finished.
╔═[siamhie@flux23]═[09:30 27/01/24]═════════════════════════════════════[~/Downloads/ventoy-1.0.97]
╚═>
v1.jpg
v2.jpg
v3.jpg
v4.jpg
Let me know if you want me to add any error logs.
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Sat Jan 27, 2024 1:17 pm
by fehlix
siamhie wrote: Sat Jan 27, 2024 12:56 pm
Reinstalling ventoy (1.0.97) didn't work.
Code: Select all
╔═[siamhie@flux23]═[09:30 27/01/24]═════════════════════════════════════[~/Downloads/ventoy-1.0.97]
╚═> sudo ./Ventoy2Disk.sh -I /dev/sdb
You didn't Re-install but just a forced Install.
Code: Select all
./Ventoy2Disk.sh --help
**********************************************
Ventoy: 1.0.97 x86_64
longpanda admin@ventoy.net
https://www.ventoy.net
**********************************************
Usage: Ventoy2Disk.sh CMD [ OPTION ] /dev/sdX
CMD:
-i install Ventoy to sdX (fails if disk already installed with Ventoy)
-I force install Ventoy to sdX (no matter if installed or not)
-u update Ventoy in sdX
-l list Ventoy information in sdX
OPTION: (optional)
-r SIZE_MB preserve some space at the bottom of the disk (only for install)
-s/-S enable/disable secure boot support (default is enabled)
-g use GPT partition style, default is MBR (only for install)
-L Label of the 1st exfat partition (default is Ventoy)
-n try non-destructive installation (only for install)
Also I have only tested with MX provided liquorix kernel:
Code: Select all
==> /live/to-ram/antiX/vmlinuz.ver <==
KERNEL_VERSION="6.7.1-1-liquorix-amd64 [6.7-1~mx23ahs] 2024-01-24"
==> /live/to-ram/antiX/vmlinuz1.ver <==
KERNEL_VERSION="6.6.12-1-liquorix-amd64 [6.6-16~mx23ahs] 2024-01-18"
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Sat Jan 27, 2024 2:24 pm
by siamhie
@fehlix I started from scratch. First I wiped out the partitions ventoy creates with gparted and left the thumb drive blank.
gparted.jpg
Now I installed ventoy 1.0.97.
Code: Select all
╔═[siamhie@flux23]═[10:39 27/01/24]═════════════════════════════════════[~/Downloads/ventoy-1.0.97]
╚═> sudo ./Ventoy2Disk.sh -i /dev/sdb
[sudo] password for siamhie:
**********************************************
Ventoy: 1.0.97 x86_64
longpanda admin@ventoy.net
https://www.ventoy.net
**********************************************
Disk : /dev/sdb
Model: Kingston DataTraveler 3.0 (scsi)
Size : 28 GB
Style: MBR
Attention:
You will install Ventoy to /dev/sdb.
All the data on the disk /dev/sdb will be lost!!!
Continue? (y/n) y
All the data on the disk /dev/sdb will be lost!!!
Double-check. Continue? (y/n) y
Create partitions on /dev/sdb by parted in MBR style ...
Done
Wait for partitions ...
partition exist OK
create efi fat fs /dev/sdb2 ...
mkfs.fat 4.2 (2021-01-31)
success
Wait for partitions ...
/dev/sdb1 exist OK
/dev/sdb2 exist OK
partition exist OK
Format partition 1 /dev/sdb1 ...
mkexfatfs 1.3.0
Creating... done.
Flushing... done.
File system created successfully.
mkexfatfs success
writing data to disk ...
sync data ...
esp partition processing ...
Install Ventoy to /dev/sdb successfully finished.
╔═[siamhie@flux23]═[10:40 27/01/24]═════════════════════════════════════[~/Downloads/ventoy-1.0.97]
╚═>
I then created three snapshots changing the live kernel each time. (liquorix 6.7.2 kernel, debian 6.6.11 and liquorix 6.5.11)
quickshot_240127_104323.jpg
The liquorix 6.7.2 kernel and debian 6.6.11 kernel both error with this message.
error.jpg
The liquorix 6.5.11 kernel boots up.
Code: Select all
System:
Kernel: 6.7.2-1-liquorix-amd64 [6.7-2.1~bookworm] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 parameters: audit=0
intel_pstate=disable rcupdate.rcu_expedited=1 BOOT_IMAGE=/boot/vmlinuz-6.7.2-1-liquorix-amd64
root=UUID=<filter> ro quiet splash init=/lib/systemd/systemd
Desktop: Fluxbox v: 1.3.7 info: tint2 vt: 7 dm: LightDM v: 1.26.0 Distro: MX-23.2_fluxbox_x64
Libretto January 21 2024 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop Mobo: Micro-Star model: B550-A PRO (MS-7C56) v: 2.0 serial: <superuser required>
UEFI: American Megatrends LLC. v: A.F0 date: 10/11/2023
CPU:
Info: model: AMD Ryzen 9 5950X bits: 64 type: MT MCP arch: Zen 3+ gen: 4 level: v3 note: check
built: 2022 process: TSMC n6 (7nm) family: 0x19 (25) model-id: 0x21 (33) stepping: 2
microcode: 0xA20120E
Topology: cpus: 1x cores: 16 tpc: 2 threads: 32 smt: enabled cache: L1: 1024 KiB desc: d-16x32
KiB; i-16x32 KiB L2: 8 MiB desc: 16x512 KiB L3: 64 MiB desc: 2x32 MiB
Speed (MHz): avg: 2223 high: 2800 min/max: 2200/5083 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 2200 2: 2200 3: 2200 4: 2225 5: 2196 6: 2200
7: 2200 8: 2200 9: 2242 10: 2800 11: 2200 12: 2236 13: 2200 14: 2200 15: 2200 16: 2200 17: 2200
18: 2200 19: 2200 20: 2200 21: 2200 22: 2200 23: 2250 24: 2200 25: 2200 26: 2200 27: 2200
28: 2200 29: 2200 30: 2200 31: 2200 32: 2200 bogomips: 217593
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 sse4a ssse3 svm
Vulnerabilities:
Type: gather_data_sampling status: Not affected
Type: itlb_multihit status: Not affected
Type: l1tf status: Not affected
Type: mds status: Not affected
Type: meltdown status: Not affected
Type: mmio_stale_data status: Not affected
Type: retbleed status: Not affected
Type: spec_rstack_overflow mitigation: Safe RET
Type: spec_store_bypass mitigation: Speculative Store Bypass disabled via prctl
Type: spectre_v1 mitigation: usercopy/swapgs barriers and __user pointer sanitization
Type: spectre_v2 mitigation: Retpolines, IBPB: conditional, IBRS_FW, STIBP: always-on, RSB
filling, PBRSB-eIBRS: Not affected
Type: srbds status: Not affected
Type: tsx_async_abort status: Not affected
Graphics:
Device-1: AMD Navi 22 [Radeon RX 6700/6700 XT/6750 XT / 6800M/6850M XT] vendor: Tul / PowerColor
driver: amdgpu v: kernel arch: RDNA-2 code: Navi-2x process: TSMC n7 (7nm) built: 2020-22 pcie:
gen: 4 speed: 16 GT/s lanes: 16 ports: active: DP-3 empty: DP-1,DP-2,HDMI-A-1 bus-ID: 2d:00.0
chip-ID: 1002:73df class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 compositor: Compton v: 1 driver: X: loaded: amdgpu
unloaded: fbdev,modesetting,radeon,vesa dri: radeonsi gpu: amdgpu display-ID: :0.0 screens: 1
Screen-1: 0 s-res: 2560x1440 s-dpi: 96 s-size: 677x381mm (26.65x15.00") s-diag: 777mm (30.58")
Monitor-1: DP-3 mapped: DisplayPort-2 model: HP X27q serial: <filter> built: 2021
res: 2560x1440 hz: 165 dpi: 109 gamma: 1.2 size: 597x336mm (23.5x13.23") diag: 685mm (27")
ratio: 16:9 modes: max: 2560x1440 min: 720x400
API: OpenGL v: 4.6 Mesa 22.3.6 renderer: AMD Radeon RX 6700 XT (navi22 LLVM 15.0.6 DRM 3.56
6.7.2-1-liquorix-amd64) direct-render: Yes
Audio:
Device-1: AMD Navi 21/23 HDMI/DP Audio driver: snd_hda_intel v: kernel pcie: gen: 4
speed: 16 GT/s lanes: 16 bus-ID: 2d:00.1 chip-ID: 1002:ab28 class-ID: 0403
Device-2: AMD Starship/Matisse HD Audio vendor: Micro-Star MSI driver: snd_hda_intel v: kernel
pcie: gen: 4 speed: 16 GT/s lanes: 16 bus-ID: 2f:00.4 chip-ID: 1022:1487 class-ID: 0403
API: ALSA v: k6.7.2-1-liquorix-amd64 status: kernel-api tools: alsamixer,amixer
Server-1: PipeWire v: 1.0.0 status: active with: 1: pipewire-pulse status: active
2: wireplumber status: active 3: pipewire-alsa type: plugin 4: pw-jack type: plugin
tools: pactl,pw-cat,pw-cli,wpctl
Network:
Device-1: Intel Wi-Fi 6 AX210/AX211/AX411 160MHz driver: iwlwifi v: kernel pcie: gen: 2
speed: 5 GT/s lanes: 1 bus-ID: 05:00.0 chip-ID: 8086:2725 class-ID: 0280
IF: wlan0 state: up mac: <filter>
Device-2: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Micro-Star MSI
driver: r8169 v: kernel pcie: gen: 1 speed: 2.5 GT/s lanes: 1 port: f000 bus-ID: 2a:00.0
chip-ID: 10ec:8168 class-ID: 0200
IF: eth0 state: down mac: <filter>
Bluetooth:
Device-1: Intel AX210 Bluetooth type: USB driver: btusb v: 0.8 bus-ID: 1-2.3:4 chip-ID: 8087:0032
class-ID: e001
Report: rfkill ID: hci0 rfk-id: 1 state: down bt-service: N/A rfk-block: hardware: no
software: no address: see --recommends
Drives:
Local Storage: total: 8.19 TiB used: 887.71 GiB (10.6%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:3 vendor: Western Digital model: WDS500G1X0E-00AFY0
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 63.2 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 613000WD temp: 36.9 C scheme: GPT
ID-2: /dev/nvme1n1 maj-min: 259:0 vendor: Western Digital model: WDS500G3XHC-00SJG0
size: 465.76 GiB block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 type: SSD
serial: <filter> rev: 102000WD temp: 32.9 C scheme: GPT
ID-3: /dev/sda maj-min: 8:0 vendor: SanDisk model: ST8000DM004-2CX188 size: 7.28 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s type: HDD rpm: 5425 serial: <filter>
rev: 0001 scheme: GPT
Partition:
ID-1: / raw-size: 465 GiB size: 456.63 GiB (98.20%) used: 11.1 GiB (2.4%) fs: ext4
dev: /dev/nvme0n1p2 maj-min: 259:5
ID-2: /boot/efi raw-size: 128 MiB size: 126 MiB (98.45%) used: 274 KiB (0.2%) fs: vfat
dev: /dev/nvme0n1p1 maj-min: 259:4
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default)
ID-1: swap-1 type: partition size: 65 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/nvme1n1p1
maj-min: 259:1
Sensors:
System Temperatures: cpu: 38.4 C mobo: N/A gpu: amdgpu temp: 47.0 C mem: 50.0 C
Fan Speeds (RPM): N/A gpu: amdgpu fan: 751
Repos:
Packages: pm: dpkg pkgs: 2133 libs: 1141 tools: apt,apt-get,aptitude,nala,synaptic pm: rpm
pkgs: 0
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/debian-stable-updates.list
1: deb http://deb.debian.org/debian bookworm-updates main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/debian.list
1: deb http://deb.debian.org/debian bookworm main contrib non-free non-free-firmware
2: deb http://security.debian.org/debian-security bookworm-security main contrib non-free non-free-firmware
Active apt repos in: /etc/apt/sources.list.d/librewolf.list
1: deb [arch=amd64] http://deb.librewolf.net bookworm main
Active apt repos in: /etc/apt/sources.list.d/liquorix.list
1: deb [arch=amd64 signed-by=/etc/apt/keyrings/liquorix-keyring.gpg] https://liquorix.net/debian bookworm main
2: deb-src [arch=amd64 signed-by=/etc/apt/keyrings/liquorix-keyring.gpg] https://liquorix.net/debian bookworm main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://la.mxrepo.com/mx/repo/ bookworm main non-free
Active apt repos in: /etc/apt/sources.list.d/nordvpn.list
1: deb https://repo.nordvpn.com/deb/nordvpn/debian stable main
Info:
Processes: 617 Uptime: 8m wakeups: 0 Memory: 31.27 GiB used: 1.8 GiB (5.7%) Init: systemd v: 252
target: graphical (5) default: graphical tool: systemctl Compilers: gcc: 12.2.0 alt: 12
Client: shell wrapper v: 5.2.15-release inxi: 3.3.26
Boot Mode: UEFI
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Sat Jan 27, 2024 2:51 pm
by fehlix
siamhie wrote: Sat Jan 27, 2024 2:24 pm
@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.
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Sat Jan 27, 2024 3:48 pm
by siamhie
fehlix wrote: Sat Jan 27, 2024 2:51 pm
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.
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Sat Jan 27, 2024 4:39 pm
by 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.
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Sat Jan 27, 2024 5:50 pm
by 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.
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Sat Jan 27, 2024 7:14 pm
by 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.
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Sat Jan 27, 2024 8:41 pm
by 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.
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Sat Jan 27, 2024 8:44 pm
by siamhie
fehlix wrote: Sat Jan 27, 2024 7:14 pm
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.
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Sat Jan 27, 2024 9:26 pm
by 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
Re: Booting 6.6 or 6.7 kernels with Ventoy [Solved]
Posted: Sun Jan 28, 2024 9:35 am
by fehlix
siamhie wrote: Sat Jan 27, 2024 8:44 pm
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
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Sun Jan 28, 2024 9:51 am
by siamhie
fehlix wrote: Sun Jan 28, 2024 9:35 am
siamhie wrote: Sat Jan 27, 2024 8:44 pm
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.
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Sun Jan 28, 2024 9:58 am
by fehlix
siamhie wrote: Sun Jan 28, 2024 9:51 am
fehlix wrote: Sun Jan 28, 2024 9:35 am
siamhie wrote: Sat Jan 27, 2024 8:44 pm
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.
Thanks for confirming.
@Adrian send a PR with a Ventoy fix.
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Sun Jan 28, 2024 10:34 am
by siamhie
fehlix wrote: Sun Jan 28, 2024 9:58 am
Thanks for confirming.
@Adrian send a PR with a Ventoy fix.
How long do PR's typically take?
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Sun Jan 28, 2024 12:35 pm
by fehlix
siamhie wrote: Sun Jan 28, 2024 10:34 am
How long do PR's typically take?
The typical time span is characterized by patience,
and depends "typically" by the repo-mirrors involved, on the spare time of those involved to go through the steps from source, to prepare new build, to prepare to get those build and sources into the master mirror and finally on the schedule the mirrors involved are synced. But in this case something about 3 hours to show up at the Salt Lake City repo may be realistic.
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Sun Jan 28, 2024 4:21 pm
by siamhie
fehlix wrote: Sun Jan 28, 2024 12:35 pm
siamhie wrote: Sun Jan 28, 2024 10:34 am
How long do PR's typically take?
The typical time span is characterized by patience,
and depends "typically" by the repo-mirrors involved, on the spare time of those involved to go through the steps from source, to prepare new build, to prepare to get those build and sources into the master mirror and finally on the schedule the mirrors involved are synced. But in this case something about 3 hours to show up at the Salt Lake City repo may be realistic.
OK, thanks.
I saw the update for mx-snapshot come through nala, so I applied it even though both file names where the same.
Re: Booting 6.6 or 6.7 kernels with Ventoy
Posted: Sun Jan 28, 2024 4:32 pm
by fehlix
siamhie wrote: Sun Jan 28, 2024 4:21 pm
I saw the update for mx-snapshot come through nala, so I applied it even though both file names where the same.
Yes, these are fresh builds, and apt also seems to compare the sha256 checksums of the package and sees the ones from the repo as an upgrade because the checksum have changed even though the version number is identical.