Page 1 of 1
Liquorix vs cdemu
Posted: Thu Oct 17, 2024 1:06 am
by rambo919
Linked to the issues of this thread but more it's own thing I think. Sysinfo is unchanged from the previous thread only makedeb is still disabled so not relevant.
viewtopic.php?t=81422
The kernel update sequence needs a bit of tweaking I think. Every time there is a kernel update the same dependency problem appears and I have to remove cdemu, update the kernel and then reinstall cdemu.
Code: Select all
$ sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
linux-headers-6.10.12-1-liquorix-amd64 linux-image-6.10.12-1-liquorix-amd64
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up linux-headers-6.11.3-3-liquorix-amd64 (6.11-5~mx23ahs) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.11.3-3-liquorix-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.11.3-3-liquorix-amd64
Sign command: /lib/modules/6.11.3-3-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.11.3-3-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed
Building module:
Cleaning build area...
make -j12 KERNELRELEASE=6.11.3-3-liquorix-amd64...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.11.3-3-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/vhba/20240202/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.11.3-3-liquorix-amd64 failed!
run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
Failed to process /etc/kernel/header_postinst.d at /var/lib/dpkg/info/linux-headers-6.11.3-3-liquorix-amd64.postinst line 11.
dpkg: error processing package linux-headers-6.11.3-3-liquorix-amd64 (--configure):
installed linux-headers-6.11.3-3-liquorix-amd64 package post-installation script subprocess returned error exit status 1
Setting up linux-image-6.11.3-3-liquorix-amd64 (6.11-5~mx23ahs) ...
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.11.3-3-liquorix-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.11.3-3-liquorix-amd64
Sign command: /lib/modules/6.11.3-3-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.11.3-3-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed
Building module:
Cleaning build area...
make -j12 KERNELRELEASE=6.11.3-3-liquorix-amd64...(bad exit status: 2)
Error! Bad return status for module build on kernel: 6.11.3-3-liquorix-amd64 (x86_64)
Consult /var/lib/dkms/vhba/20240202/build/make.log for more information.
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.
dkms: autoinstall for kernel: 6.11.3-3-liquorix-amd64 failed!
run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
dpkg: error processing package linux-image-6.11.3-3-liquorix-amd64 (--configure):
installed linux-image-6.11.3-3-liquorix-amd64 package post-installation script subprocess returned error exit status 1
dpkg: dependency problems prevent configuration of linux-headers-liquorix-amd64:
linux-headers-liquorix-amd64 depends on linux-headers-6.11.3-3-liquorix-amd64 (= 6.11-5~mx23ahs); however:
Package linux-headers-6.11.3-3-liquorix-amd64 is not configured yet.
dpkg: error processing package linux-headers-liquorix-amd64 (--configure):
dependency problems - leaving unconfigured
dpkg: dependency problems prevent configuration of linux-image-liquorix-amd64:
linux-image-liquorix-amd64 depends on linux-image-6.11.3-3-liquorix-amd64 (= 6.11-5~mx23ahs); however:
Package linux-image-6.11.3-3-liquorix-amd64 is not configured yet.
dpkg: error processing package linux-image-liquorix-amd64 (--configure):
dependency problems - leaving unconfigured
Errors were encountered while processing:
linux-headers-6.11.3-3-liquorix-amd64
linux-image-6.11.3-3-liquorix-amd64
linux-headers-liquorix-amd64
linux-image-liquorix-amd64
E: Sub-process /usr/bin/dpkg returned an error code (1)
Re: Liquorix vs cdemu
Posted: Thu Oct 17, 2024 2:54 am
by Eadwine Rose
Be accomodating and share the QSI in THIS topic, so people don't have to go click links to hunt that down.
Re: Liquorix vs cdemu
Posted: Thu Oct 17, 2024 3:31 am
by rambo919
Eadwine Rose wrote: Thu Oct 17, 2024 2:54 am
Be accomodating and share the QSI in THIS topic, so people don't have to go click links to hunt that down.
righto
Code: Select all
System:
Kernel: 6.11.3-1-liquorix-amd64 [6.11-3~mx23ahs] arch: x86_64 bits: 64 compiler: gcc v: 12.2.0 clocksource: tsc
avail: hpet,acpi_pm parameters: audit=0 intel_pstate=disable
BOOT_IMAGE=/boot/vmlinuz-6.11.3-1-liquorix-amd64 root=UUID=<filter> ro quiet splash
Desktop: KDE Plasma v: 5.27.5 tk: Qt v: N/A info: frameworks v: 5.103.0 wm: kwin_x11 vt: 7
dm: SDDM Distro: MX-23.4_KDE_x64 Libretto July 31 2023 base: Debian GNU/Linux 12 (bookworm)
Machine:
Type: Desktop Mobo: Gigabyte model: Q370M D3H GSM PLUS serial: <superuser required>
uuid: <superuser required> UEFI-[Legacy]: American Megatrends v: F15 date: 11/11/2021
CPU:
Info: model: Intel Core i7-8700 bits: 64 type: MT MCP arch: Coffee Lake gen: core 8 level: v3
note: check built: 2018 process: Intel 14nm family: 6 model-id: 0x9E (158) stepping: 0xA (10)
microcode: 0xF8
Topology: cpus: 1x cores: 6 tpc: 2 threads: 12 smt: enabled cache: L1: 384 KiB
desc: d-6x32 KiB; i-6x32 KiB L2: 1.5 MiB desc: 6x256 KiB L3: 12 MiB desc: 1x12 MiB
Speed (MHz): avg: 3056 high: 4399 min/max: 800/3201 boost: enabled scaling:
driver: acpi-cpufreq governor: ondemand cores: 1: 4366 2: 4309 3: 4290 4: 4299 5: 4399 6: 4316
7: 3201 8: 800 9: 4296 10: 800 11: 800 12: 800 bogomips: 76799
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Vulnerabilities:
Type: gather_data_sampling mitigation: Microcode
Type: itlb_multihit status: KVM: VMX disabled
Type: l1tf mitigation: PTE Inversion; VMX: conditional cache flushes, SMT vulnerable
Type: mds mitigation: Clear CPU buffers; SMT vulnerable
Type: meltdown mitigation: PTI
Type: mmio_stale_data mitigation: Clear CPU buffers; SMT vulnerable
Type: reg_file_data_sampling status: Not affected
Type: retbleed mitigation: IBRS
Type: spec_rstack_overflow status: Not affected
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: IBRS; IBPB: conditional; STIBP: conditional; RSB filling;
PBRSB-eIBRS: Not affected; BHI: Not affected
Type: srbds mitigation: Microcode
Type: tsx_async_abort mitigation: TSX disabled
Graphics:
Device-1: NVIDIA GP107 [GeForce GTX 1050 Ti] vendor: Gigabyte driver: nvidia v: 560.35.03
non-free: 545.xx+ status: current (as of 2024-04; EOL~2026-12-xx) arch: Pascal code: GP10x
process: TSMC 16nm built: 2016-2021 pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.0
chip-ID: 10de:1c82 class-ID: 0300
Display: x11 server: X.Org v: 1.21.1.7 with: Xwayland v: 22.1.9 compositor: kwin_x11 driver: X:
loaded: nvidia unloaded: fbdev,modesetting,nouveau,vesa alternate: nv gpu: nvidia display-ID: :0
screens: 1
Screen-1: 0 s-res: 5760x1080 s-dpi: 93 s-size: 1573x292mm (61.93x11.50")
s-diag: 1600mm (62.99")
Monitor-1: DVI-D-0 pos: left res: 1920x1080 hz: 60 dpi: 102 size: 477x268mm (18.78x10.55")
diag: 547mm (21.54") modes: N/A
Monitor-2: HDMI-0 pos: primary,center res: 1920x1080 dpi: 93 size: 527x296mm (20.75x11.65")
diag: 604mm (23.8") modes: N/A
Monitor-3: HDMI-2 pos: right res: 1920x1080 hz: 60 dpi: 102 size: 476x268mm (18.74x10.55")
diag: 546mm (21.51") modes: N/A
API: EGL v: 1.5 hw: drv: nvidia platforms: device: 0 drv: nvidia device: 2 drv: swrast gbm:
drv: kms_swrast surfaceless: drv: nvidia x11: drv: nvidia inactive: wayland,device-1
API: OpenGL v: 4.6.0 vendor: nvidia v: 560.35.03 glx-v: 1.4 direct-render: yes renderer: NVIDIA
GeForce GTX 1050 Ti/PCIe/SSE2 memory: 3.91 GiB
API: Vulkan v: 1.3.250 layers: 11 device: 0 type: discrete-gpu name: NVIDIA GeForce GTX 1050 Ti
driver: nvidia v: 560.35.03 device-ID: 10de:1c82 surfaces: xcb,xlib device: 1 type: cpu
name: llvmpipe (LLVM 15.0.6 256 bits) driver: mesa llvmpipe v: 24.2.2-1~mx23ahs (LLVM 15.0.6)
device-ID: 10005:0000 surfaces: xcb,xlib
Audio:
Device-1: Intel Cannon Lake PCH cAVS vendor: Gigabyte driver: snd_hda_intel v: kernel
alternate: snd_soc_avs,snd_sof_pci_intel_cnl bus-ID: 00:1f.3 chip-ID: 8086:a348 class-ID: 0403
Device-2: NVIDIA GP107GL High Definition Audio vendor: Gigabyte driver: snd_hda_intel v: kernel
pcie: gen: 3 speed: 8 GT/s lanes: 16 bus-ID: 01:00.1 chip-ID: 10de:0fb9 class-ID: 0403
API: ALSA v: k6.11.3-1-liquorix-amd64 status: kernel-api tools: alsactl,alsamixer,amixer
Server-1: JACK v: 1.9.21 status: off tools: jack_control
Server-2: 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 Ethernet I219-LM vendor: Gigabyte driver: e1000e v: kernel port: N/A
bus-ID: 00:1f.6 chip-ID: 8086:15bb class-ID: 0200
IF: eth1 state: up speed: 100 Mbps duplex: full mac: <filter>
Device-2: Intel I211 Gigabit Network vendor: Gigabyte driver: igb v: kernel pcie: gen: 1
speed: 2.5 GT/s lanes: 1 port: 3000 bus-ID: 04:00.0 chip-ID: 8086:1539 class-ID: 0200
IF: eth0 state: down mac: <filter>
Info: services: NetworkManager,proftpd,smbd
Drives:
Local Storage: total: 9.55 TiB used: 4.6 TiB (48.2%)
SMART Message: Unable to run smartctl. Root privileges required.
ID-1: /dev/nvme0n1 maj-min: 259:0 vendor: Samsung model: SSD 980 1TB size: 931.51 GiB
block-size: physical: 512 B logical: 512 B speed: 31.6 Gb/s lanes: 4 tech: SSD serial: <filter>
fw-rev: 3B4QFXO7 temp: 34.9 C scheme: MBR
ID-2: /dev/sda maj-min: 8:0 vendor: Western Digital model: WD5000LPCX-24VHAT0 size: 465.76 GiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 5400 serial: <filter>
fw-rev: 1A01 scheme: MBR
ID-3: /dev/sdb maj-min: 8:16 vendor: Seagate model: ST2000DM001-9YN164 size: 1.82 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
fw-rev: CC4B scheme: MBR
ID-4: /dev/sdc maj-min: 8:32 vendor: Western Digital model: WD Blue SA510 2.5 1000GB
size: 931.51 GiB block-size: physical: 512 B logical: 512 B speed: 6.0 Gb/s tech: SSD
serial: <filter> fw-rev: 6100 scheme: MBR
ID-5: /dev/sdd maj-min: 8:48 vendor: Seagate model: ST2000DM001-1ER164 size: 1.82 TiB
block-size: physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter>
fw-rev: CC25 scheme: MBR
ID-6: /dev/sde maj-min: 8:64 vendor: Toshiba model: HDWE140 size: 3.64 TiB block-size:
physical: 4096 B logical: 512 B speed: 6.0 Gb/s tech: HDD rpm: 7200 serial: <filter> fw-rev: FP2A
scheme: GPT
Partition:
ID-1: / raw-size: 97.66 GiB size: 95.56 GiB (97.86%) used: 72.96 GiB (76.3%) fs: ext4
dev: /dev/sdc1 maj-min: 8:33
ID-2: /home raw-size: 720.86 GiB size: 708.98 GiB (98.35%) used: 170.36 GiB (24.0%) fs: ext4
dev: /dev/sdc2 maj-min: 8:34
Swap:
Kernel: swappiness: 15 (default 60) cache-pressure: 100 (default) zswap: yes compressor: lz4
max-pool: 20%
ID-1: swap-1 type: partition size: 12 GiB used: 0 KiB (0.0%) priority: -2 dev: /dev/sdc3
maj-min: 8:35
Sensors:
System Temperatures: cpu: 42.0 C pch: 55.0 C mobo: 37.0 C gpu: nvidia temp: 50 C
Fan Speeds (rpm): N/A gpu: nvidia fan: 0%
Repos:
Packages: 4997 pm: dpkg pkgs: 4933 libs: 2468 tools: apt, apt-get, aptitude, nala, synaptic
pm: rpm pkgs: 0 pm: flatpak pkgs: 64
No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/adoptium.list
1: deb https://packages.adoptium.net/artifactory/deb/ bookworm main
No active apt repos in: /etc/apt/sources.list.d/atom.list
Active apt repos in: /etc/apt/sources.list.d/brave-browser-release.list
1: deb [arch=amd64] https://brave-browser-apt-release.s3.brave.com/ bullseye main
No active apt repos in: /etc/apt/sources.list.d/deb-multimedia.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/element-io.list
1: deb [signed-by=/usr/share/keyrings/element-io-archive-keyring.gpg] https://packages.element.io/debian/ default main
No active apt repos in: /etc/apt/sources.list.d/freedownloadmanager.list
Active apt repos in: /etc/apt/sources.list.d/google-earth-pro.list
1: deb [arch=amd64] http://dl.google.com/linux/earth/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/lutris.list
1: deb [signed-by=/etc/apt/keyrings/lutris.gpg] https://download.opensuse.org/repositories/home:/strycore/Debian_12/ ./
Active apt repos in: /etc/apt/sources.list.d/makedeb.list
1: deb [signed-by=/usr/share/keyrings/makedeb-archive-keyring.gpg arch=all] https://proget.makedeb.org/ makedeb main
Active apt repos in: /etc/apt/sources.list.d/mx.list
1: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bookworm main non-free
2: deb http://mxlinux.mirrors.uk2.net/packages/mx/repo/ bookworm ahs
Active apt repos in: /etc/apt/sources.list.d/nvidia-drivers.list
1: deb [signed-by=/usr/share/keyrings/nvidia-drivers.gpg] https://developer.download.nvidia.com/compute/cuda/repos/debian12/x86_64/ /
Active apt repos in: /etc/apt/sources.list.d/onlyoffice.list
1: deb https://download.onlyoffice.com/repo/debian/ squeeze main
Active apt repos in: /etc/apt/sources.list.d/signal-xenial-added-by-mxpi.list
1: deb [arch=amd64] https://updates.signal.org/desktop/apt/ xenial main
Active apt repos in: /etc/apt/sources.list.d/vscode.list
1: deb [arch=amd64,arm64,armhf] https://packages.microsoft.com/repos/code/ stable main
Active apt repos in: /etc/apt/sources.list.d/webmin.list
1: deb [signed-by=/usr/share/keyrings/debian-webmin-developers.gpg] https://download.webmin.com/download/newkey/repository/ stable contrib
Active apt repos in: /etc/apt/sources.list.d/extrepo_librewolf.sources
1: deb [arch=amd64 arm64] https://repo.librewolf.net librewolf main
Active apt repos in: /etc/apt/sources.list.d/winehq-bookworm.sources
1: deb [arch=amd64 i386] https://dl.winehq.org/wine-builds/debian bookworm main
Info:
Memory: total: N/A available: 31.24 GiB used: 6.14 GiB (19.7%)
Processes: 388 Power: uptime: 2h 44m states: freeze,mem,disk suspend: deep avail: s2idle
wakeups: 0 hibernate: platform avail: shutdown, reboot, suspend, test_resume image: 12.44 GiB
services: org_kde_powerdevil,upowerd Init: SysVinit v: 3.08 runlevel: 5 default: graphical
tool: systemctl
Compilers: gcc: 12.2.0 Client: shell wrapper v: 5.2.15-release inxi: 3.3.34
Boot Mode: BIOS (legacy, CSM, MBR)
Re: Liquorix vs cdemu
Posted: Thu Oct 17, 2024 3:47 am
by Eadwine Rose
Thanks :)
Re: Liquorix vs cdemu
Posted: Thu Oct 17, 2024 4:38 am
by CatManDan
Could you also post the content of the file /var/lib/dkms/vhba/20240202/build/make.log that your initial log already mentions?
That should hopefully tell us what exactiy the compiler did not like.
Re: Liquorix vs cdemu
Posted: Thu Oct 17, 2024 5:03 am
by rambo919
CatManDan wrote: Thu Oct 17, 2024 4:38 am
Could you also post the content of the file /var/lib/dkms/vhba/20240202/build/make.log that your initial log already mentions?
That should hopefully tell us what exactiy the compiler did not like.
Uhm.... I already attached it.
Re: Liquorix vs cdemu
Posted: Thu Oct 17, 2024 5:24 am
by siamhie
rambo919 wrote: Thu Oct 17, 2024 5:03 am
CatManDan wrote: Thu Oct 17, 2024 4:38 am
Could you also post the content of the file /var/lib/dkms/vhba/20240202/build/make.log that your initial log already mentions?
That should hopefully tell us what exactiy the compiler did not like.
Uhm.... I already attached it.
No, you've posted your QSI (quick system information). Also post (in code tags) the make.log file.
Re: Liquorix vs cdemu
Posted: Thu Oct 17, 2024 5:31 am
by rambo919
siamhie wrote: Thu Oct 17, 2024 5:24 am
No, you've posted your QSI (quick system information). Also post (in code tags) the make.log file.
OK I am confused. It's right under the first code block I posted.... is there a reason to post it as a code block rather than attach it as a file I am missing?
Re: Liquorix vs cdemu
Posted: Thu Oct 17, 2024 5:53 am
by Eadwine Rose
Some people just don't like clicking random links. And the code block content is searchable on the forum.
Re: Liquorix vs cdemu
Posted: Thu Oct 17, 2024 6:00 am
by rambo919
OK
Code: Select all
DKMS make.log for vhba-20240202 for kernel 6.11.3-3-liquorix-amd64 (x86_64)
Thu 17 Oct 06:59:14 SAST 2024
make -C /lib/modules/6.11.3-3-liquorix-amd64/build M=/var/lib/dkms/vhba/20240202/build modules
make[1]: Entering directory '/usr/src/linux-headers-6.11.3-3-liquorix-amd64'
CC [M] /var/lib/dkms/vhba/20240202/build/vhba.o
/var/lib/dkms/vhba/20240202/build/vhba.c:1087:15: error: initialization of ‘void (*)(struct platform_device *)’ from incompatible pointer type ‘int (*)(struct platform_device *)’ [-Werror=incompatible-pointer-types]
1087 | .remove = vhba_remove,
| ^~~~~~~~~~~
/var/lib/dkms/vhba/20240202/build/vhba.c:1087:15: note: (near initialization for ‘vhba_platform_driver.<anonymous>.remove’)
cc1: all warnings being treated as errors
make[3]: *** [scripts/Makefile.build:244: /var/lib/dkms/vhba/20240202/build/vhba.o] Error 1
make[2]: *** [/usr/src/linux-headers-6.11.3-3-liquorix-amd64/Makefile:1937: /var/lib/dkms/vhba/20240202/build] Error 2
make[1]: *** [Makefile:224: __sub-make] Error 2
make[1]: Leaving directory '/usr/src/linux-headers-6.11.3-3-liquorix-amd64'
make: *** [Makefile:14: modules] Error 2
Re: Liquorix vs cdemu
Posted: Thu Oct 17, 2024 7:57 am
by dolphin_oracle
its not the kernel package that is forcing the warning to be treated as an error. the vhba module has a Makefile with the "ccflags-y := -DVHBA_VERSION=\"$(VHBA_VERSION)\" -Werror" in it. -Werror is forcing the error.
and so since errors aren't allowed during kernel configuration, it fails.
probably you could remove the -Werror from the Makefile.
the vhba c code actually has a problem. there is an updated source, maybe its been fixed, otherwise I would report the problem upstream.
Re: Liquorix vs cdemu
Posted: Thu Oct 17, 2024 8:00 am
by dolphin_oracle
Re: Liquorix vs cdemu
Posted: Thu Oct 17, 2024 8:20 am
by rambo919
Editing /var/lib/dkms/vhba/20240202/source/vhba.c with those changes allows the kernel to update.
However there are lots of warnings that I don't remember seeing in the past.
Code: Select all
$ sudo apt upgrade
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages were automatically installed and are no longer required:
linux-headers-6.10.12-1-liquorix-amd64 linux-image-6.10.12-1-liquorix-amd64
Use 'sudo apt autoremove' to remove them.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
4 not fully installed or removed.
After this operation, 0 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Setting up linux-headers-6.11.3-3-liquorix-amd64 (6.11-5~mx23ahs) ...
/etc/kernel/header_postinst.d/dkms:
dkms: running auto installation service for kernel 6.11.3-3-liquorix-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.11.3-3-liquorix-amd64
Sign command: /lib/modules/6.11.3-3-liquorix-amd64/build/scripts/sign-file
Binary /lib/modules/6.11.3-3-liquorix-amd64/build/scripts/sign-file not found, modules won't be signed
Building module:
Cleaning build area...
make -j12 KERNELRELEASE=6.11.3-3-liquorix-amd64...
Cleaning build area...
vhba.ko.zst:
Running module version sanity check.
Error! Module version 20240202 for vhba.ko.zst
is not newer than what is already found in kernel 6.11.3-3-liquorix-amd64 (20240917).
You may override by specifying --force.
depmod...
dkms: autoinstall for kernel: 6.11.3-3-liquorix-amd64.
Setting up linux-image-6.11.3-3-liquorix-amd64 (6.11-5~mx23ahs) ...
/etc/kernel/postinst.d/dkms:
dkms: running auto installation service for kernel 6.11.3-3-liquorix-amd64.
/usr/sbin/dkms.mx autoinstall --kernelver 6.11.3-3-liquorix-amd64
dkms: autoinstall for kernel: 6.11.3-3-liquorix-amd64.
/etc/kernel/postinst.d/initramfs-tools:
update-initramfs: Generating /boot/initrd.img-6.11.3-3-liquorix-amd64
I: The initramfs will attempt to resume from /dev/sdc3
I: (UUID=1a3ecd1e-bcaa-4a15-8f2a-efd91bebf6cf)
I: Set the RESUME variable to override this.
/etc/kernel/postinst.d/zz-update-grub:
Generating grub configuration file ...
Found theme: /boot/grub/themes/mx_linux/theme.txt
Warning: version_find_latest() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Found linux image: /boot/vmlinuz-6.11.3-3-liquorix-amd64
Found initrd image: /boot/initrd.img-6.11.3-3-liquorix-amd64
Warning: version_find_latest() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Found linux image: /boot/vmlinuz-6.11.3-1-liquorix-amd64
Found initrd image: /boot/initrd.img-6.11.3-1-liquorix-amd64
Warning: version_find_latest() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Found linux image: /boot/vmlinuz-6.10.12-1-liquorix-amd64
Found initrd image: /boot/initrd.img-6.10.12-1-liquorix-amd64
Warning: version_find_latest() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Found linux image: /boot/vmlinuz-6.9.12-amd64
Found initrd image: /boot/initrd.img-6.9.12-amd64
Warning: version_find_latest() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Found linux image: /boot/vmlinuz-6.6.15-amd64
Found initrd image: /boot/initrd.img-6.6.15-amd64
Warning: version_find_latest() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Warning: version_test_numeric() is deprecated. Use version_sort() instead.
Found linux image: /boot/vmlinuz-6.6.12-1-liquorix-amd64
Found initrd image: /boot/initrd.img-6.6.12-1-liquorix-amd64
Warning: version_find_latest() is deprecated. Use version_sort() instead.
Warning: version_test_gt() is deprecated. Use version_sort() instead.
Found linux image: /boot/vmlinuz-6.6.11-amd64
Found initrd image: /boot/initrd.img-6.6.11-amd64
Found Windows Recovery Environment on /dev/nvme0n1p1
Found Linux Mint 22 Wilma (22) on /dev/sda6
done
Setting up linux-headers-liquorix-amd64 (6.11-5~mx23ahs) ...
Setting up linux-image-liquorix-amd64 (6.11-5~mx23ahs) ...
Re: Liquorix vs cdemu
Posted: Thu Oct 17, 2024 11:03 pm
by Stevo
That would indicate that the Liquorix kernel is already including a vhba module. It is not present in the Debian 6.11 kernel, however.
I will backport vhba-dkms 20240917 from Debian testing for our test repos to remedy this.
Code: Select all
sudo modinfo vhba
filename: /lib/modules/6.11.3-1-liquorix-amd64/kernel/drivers/scsi/vhba/vhba.ko.xz
license: GPL
description: Virtual SCSI HBA
version: 20240917
author: Chia-I Wu
srcversion: EFB019563391FEE1BB3B3EE
depends:
retpoline: Y
intree: Y
name: vhba
vermagic: 6.11.3-1-liquorix-amd64 SMP preempt mod_unload
parm: can_queue:int
Re: Liquorix vs cdemu
Posted: Fri Oct 18, 2024 2:25 pm
by Stevo
For those that want to upgrade to the new test repo version of vhba-dkms, it will be necessary to remove the older MX 1:20240202 first. That one carried over a higher "1:" epoch versioning from deb-multimedia, and now that we can backport it from upstream Debian itself, the new version will get us back in sync.
Upon checking, the vanilla kernel source does not include the vhba driver. The Liquorix kernel "zen" patchset adds it, so the separate dkms driver is still necessary on Debian kernels.
Re: Liquorix vs cdemu
Posted: Fri Oct 25, 2024 2:14 am
by rambo919
Also worth noting, libmirage must also be explicitly removed and then reinstalled. Otherwise you are likely to run into problems where the daemon cannot start.
Re: Liquorix vs cdemu
Posted: Wed Apr 09, 2025 12:45 am
by rambo919
Stevo wrote: Thu Oct 17, 2024 11:03 pm
That would indicate that the Liquorix kernel is already including a vhba module. It is not present in the Debian 6.11 kernel, however.
I will backport vhba-dkms 20240917 from Debian testing for our test repos to remedy this.
Same kind of thing happened again. Kindly update vhba-module in test repo please.
Only useful hit I found on ddg search, indicates bug was fixed in specific updated release :
https://github.com/NixOS/nixpkgs/issues/393534
My make.log output
Code: Select all
DKMS make.log for vhba-20240917 for kernel 6.14.1-1-liquorix-amd64 (x86_64)
Wed 9 Apr 06:24:24 SAST 2025
make: Entering directory '/usr/src/linux-headers-6.14.1-1-liquorix-amd64'
make[1]: Entering directory '/var/lib/dkms/vhba/20240917/build'
CC [M] vhba.o
vhba.c:541:6: error: ‘struct scsi_host_template’ has no member named ‘tag_alloc_policy’; did you mean ‘tag_alloc_policy_rr’?
541 | .tag_alloc_policy = BLK_TAG_ALLOC_RR,
| ^~~~~~~~~~~~~~~~
| tag_alloc_policy_rr
vhba.c:541:25: error: ‘BLK_TAG_ALLOC_RR’ undeclared here (not in a function)
541 | .tag_alloc_policy = BLK_TAG_ALLOC_RR,
| ^~~~~~~~~~~~~~~~
make[3]: *** [/usr/src/linux-headers-6.14.1-1-liquorix-amd64/scripts/Makefile.build:207: vhba.o] Error 1
make[2]: *** [/usr/src/linux-headers-6.14.1-1-liquorix-amd64/Makefile:2004: .] Error 2
make[1]: *** [/usr/src/linux-headers-6.14.1-1-liquorix-amd64/Makefile:251: __sub-make] Error 2
make[1]: Leaving directory '/var/lib/dkms/vhba/20240917/build'
make: *** [Makefile:251: __sub-make] Error 2
make: Leaving directory '/usr/src/linux-headers-6.14.1-1-liquorix-amd64'
Re: Liquorix vs cdemu
Posted: Wed Apr 09, 2025 11:22 am
by Stevo
Why are you using vhba-dkms when it's already in the Liquorix kernel?
Re: Liquorix vs cdemu
Posted: Wed Apr 09, 2025 1:26 pm
by rambo919
Stevo wrote: Wed Apr 09, 2025 11:22 am
Why are you using vhba-dkms when it's already in the Liquorix kernel?
Tested now to be sure but cdemu-deamon requires it for running on system autostart. It's also one of the recommends of cdemu-daemon, probably for this specifically.
Get the error
Code: Select all
Daemon autostart failed. Error: g-io-error-quark: Error calling StartServiceByName for net.sf.cdemu.CDEmuDaemon: Timeout was reached (24)
Re: Liquorix vs cdemu [Solved]
Posted: Wed Apr 09, 2025 4:48 pm
by Stevo
vhba-module-update.zip
Here's the latest update attached:
Re: Liquorix vs cdemu
Posted: Thu Apr 10, 2025 1:36 am
by rambo919
Stevo wrote: Wed Apr 09, 2025 4:48 pm
vhba-module-update.zipHere's the latest update attached:
Many thanks.