[REQUEST] Debian 6.7 kernel [Solved]

[M0rn1n6St4r]

Will the Debian 6.7 kernel be available soon?

I am running MX-23 AHS (Debian 6.5 kernel) on a laptop with an Intel 13th-gen Core i7-13700HX CPU (8 p-cores/16t + 8 e-cores/8t). My system seems to be assigning simple background processes to the 2 fastest p-cores (5000 MHz), alternating between the two. As these processes are related to my animated desktop-wallpaper (a 10-fps 1920×1080 webp file), I believe these processes should be assigned to 1–2 e-cores (3700 MHz), instead.

According to the Linux news outlets I read or watch, the 6.7 kernel has major changes to better support Intel's p-core/e-core CPUs. According to DJ Ware (The Cyber Gizmo), he noticed that the Debian 6.5 kernel doesn't appear to distinguish between p-cores and e-cores, while running Proxmox VE 8.

I've been postponing a kernel upgrade, thinking, "Any day now, the 6.7 kernel will become available. Just be patient."

Do you have an ETA for the Debian 6.7 kernel? The latest I find in MX Package Installer is Debian 6.6.11. And I'm not interested in running the Liquourix 6.7.4-1 kernel.

Cheers,
M0rn1n6St4r

[M0rn1n6St4r]

I suspect the following may be related to the Debian 6.5 kernel I'm using. And may be resolved by upgrading to the Debian 6.7 kernel — with improved support for Intel's 13th-gen integrated graphics.

I keep getting "W: Possible missing firmware..." at the end of dkms upgrades:
On 09-DEC-2023

Code: Select all

W: Possible missing firmware /lib/firmware/i915/dg2_huc_gsc.bin for module i915
W: Possible missing firmware /lib/firmware/i915/mtl_huc_gsc.bin for module i915
W: Possible missing firmware /lib/firmware/i915/mtl_guc_70.bin for module i915

On 10-FEB-2024 — after an upgrade included a package with dg2_huc_gsc in the name

Code: Select all

W: Possible missing firmware /lib/firmware/i915/mtl_huc_gsc.bin for module i915
W: Possible missing firmware /lib/firmware/i915/mtl_guc_70.bin for module i915

Finally, when I look at inxi -G, I see the i915 driver's version is "kernel":

Code: Select all

Graphics:
  Device-1: Intel Alder Lake-HX GT1 [UHD Graphics 770] driver: i915 v: kernel
  Device-2: NVIDIA AD107M [GeForce RTX 4060 Max-Q / Mobile] driver: nvidia
    v: 525.147.05
  Device-3: Chicony Integrated Camera type: USB driver: uvcvideo
  Display: x11 server: X.Org v: 1.21.1.7 driver: X:
    loaded: modesetting,nvidia unloaded: fbdev,nouveau,vesa dri: iris gpu: i915
    resolution: 2560x1600
  API: OpenGL v: 4.6 Mesa 23.1.2-1~mx23ahs renderer: Mesa Intel UHD
    Graphics (ADL-S GT1)

Before I installed Nvidia's v525 drivers — i.e. while running nouveau — the missing firmware list looked like this:
On 23-NOV-2023 ← oldest list

Code: Select all

W: Possible missing firmware /lib/firmware/i915/dg2_huc_gsc.bin for module i915
W: Possible missing firmware /lib/firmware/i915/mtl_huc_gsc.bin for module i915
W: Possible missing firmware /lib/firmware/i915/mtl_guc_70.bin for module i915
W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_ahesasc.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_ahesasc.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_ahesasc.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_ahesasc.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_asb.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_asb.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_asb.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_asb.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/acr/ucode_unload.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/acr/ucode_unload.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/acr/ucode_unload.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/acr/ucode_unload.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/nvdec/scrubber.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/nvdec/scrubber.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/nvdec/scrubber.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/nvdec/scrubber.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/sec2/hs_bl_sig.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/sec2/sig.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/sec2/image.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga107/sec2/desc.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/sec2/hs_bl_sig.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/sec2/sig.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/sec2/image.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga106/sec2/desc.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/sec2/hs_bl_sig.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/sec2/sig.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/sec2/image.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga104/sec2/desc.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/sec2/hs_bl_sig.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/sec2/sig.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/sec2/image.bin for module nouveau
W: Possible missing firmware /lib/firmware/nvidia/ga103/sec2/desc.bin for module nouveau

[j2mcgreg]

A better choice for you might be the Liquorix 6.7.xxx kernel that is available via MXPI. Debian's implementation of the Nvidia driver has been having problems lately. See here:viewtopic.php?t=79288

[Stevo]

Debian's 6.7 was still in Experimental as of a few days ago.

We've had 6.7 Liquorix kernels in our repos for weeks now, if you count the time they spent in our "ahs-staging" repositories. I've been running them since building the first set.

[M0rn1n6St4r]

A better choice for you might be the Liquorix 6.7.xxx kernel that is available via MXPI. Debian's implementation of the Nvidia driver has been having problems lately. See here:viewtopic.php?t=79288

Cheers, @j2mcgreg .

I am not running the 6.1.0-18 kernel, though. I'm running 6.5.0-1mx-ahs-amd64. And the "W: Possible missing firmware..." which mentions Nvidia — those only appeared while I was running the nouveau driver.

There are only 2 remaining warnings — both for i915 (Intel integrated) graphics.

[M0rn1n6St4r]

Debian's 6.7 was still in Experimental as of a few days ago.

We've had 6.7 Liquorix kernels in our repos for weeks now, if you count the time they spent in our "ahs-staging" repositories. I've been running them since building the first set.

Cheers, @Stevo .

I noticed the same on tracker.debian.org.

I've been reluctant to try the Liqourix kernels. I've heard they are not as stable as Debian kernels. And the performance improvement over Debian kernels is negligible.

You recommend them? Keep in mind, I'm not trying to game on my PC. I'm trying to overcome process-allocation issues, ACPI errors, and (possible) software-related issues; e.g. Blender doesn't recognize that I have a GPU-compute compatible NVIDIA device

But, I may need the latest nvidia-driver (v 545.x.x) to resolve the Blender issue. I have an RTX 4060 Max-Q / Mobile — paired with v 525.147.05 of nvidia-driver.

[M0rn1n6St4r]

Debian's 6.7 was still in Experimental as of a few days ago.

We've had 6.7 Liquorix kernels in our repos for weeks now, if you count the time they spent in our "ahs-staging" repositories. I've been running them since building the first set.

e.g. Blender doesn't recognize that I have a GPU-compute compatible NVIDIA device

But, I may need the latest nvidia-driver (v 545.x.x) to resolve the Blender issue. I have an RTX 4060 Max-Q / Mobile — paired with v 525.147.05 of nvidia-driver.

Ok. I'm an idiot. I didn't realize that nvidia-cuda-toolkit (+ dependencies) must be installed to enable GPU-compute in Blender. In fairness, I assumed installing nvidia-driver (+ dependencies) included all packages for all use-cases.

I assumed incorrectly. After installing the missing packages, I understand why they are not included by default. The list starts long — and gets longer, after installing the "recommended" packages. I skipped the "suggested" packages.

The "recommended" packages also have their own "recommended" and "suggested". I chose to skip those, too.

After restarting my system, I was happy to find that Blender recognized (and enabled) my RTX 4060 Max-Q / Mobile — for CUDA compute. I was surprised, however, that it also lists "13th Gen Intel Core i7-13700HX" as an option under CUDA.

Does my CPU have CUDA cores? I don't believe it does. According to r/Intel, however, "Yes, You Can Run NVIDIA CUDA On Intel GPUs and Libraries...". Hmm.

Using CPU-compute, my system (previously) completed classroom.blend in ≈4 minutes (on AC-power; tlp→performance). Using GPU-compute, after the 1st-run (which takes a couple of minutes to load the kernel modules), I completed a 2nd-run. GPU-compute completed classroom.blend in only 45 seconds (on DC-power; tlp→powersave)!

[Stevo]

The Liquorix kernels are constantly being upgraded, and may have regressions at times...a bit more often than the Debian 6.1.0-18 kernel just had with Nvidia. But that's why a known working kernel should always be kept for a backup boot.

But Liquorix really is better when low latency is required, such as in audio and video creation work. That's why AVLinux ships with it. It is also configured with more driver support than the more conservative Debian kernels.

[M0rn1n6St4r]

The Liquorix kernels are constantly being upgraded, and may have regressions at times...a bit more often than the Debian 6.1.0-18 kernel just had with Nvidia. But that's why a known working kernel should always be kept for a backup boot.

But Liquorix really is better when low latency is required, such as in audio and video creation work. That's why AVLinux ships with it. It is also configured with more driver support than the more conservative Debian kernels.

Cheers, @Stevo

Wow... I haven't seen or heard anyone mention AVLinux in years.

I actually considered trying both AVLinux and Ubuntu Studio. But, I decided I didn't want to leave MX Linux (19–19.4). I had put far too much work into customization of the system and the DE (KDE Plasma, installed before the KDE-spin released; the version was still 19.0 or 19.1). Many changes were ad hoc — spread throughout the file-system — so I couldn't just copy my home directory.

I wish I had known more about symlinks, in 2019.

I guess I'll give the Liquorix kernel(s) a try. I can always rollback. Thanks again.