Hello, 
We have had not any issues with qc71 module and kernel 7.0.. we will look into it
In the meantime:
Could you post the output of `slimbookctl get-kbd-backlight`? As that is what slimbookrgbkeyboard does to get the backlight value
Is there also in dmesg related to the qc71 module?

Regards,

slimbookctl get-kbd-backlight

/usr/include/c++/15/bits/stl_vector.h:1263: std::vector<_Tp, _Alloc>::reference std::vector<_Tp, _Alloc>::operator[](size_type) [with _Tp = std::__cxx11::basic_string<char>; _Alloc = std::allocator<std::__cxx11::basic_string<char> >; reference = std::__cxx11::basic_string<char>&; size_type = long unsigned int]: Assertion '__n < this->size()' failed.

Aborted                    (core dumped) slimbookctl get-kbd-backlight

I should also add that when I upgraded to 7.0.11, the GRUB menu stopped appearing at startup, and I had to install it manually. Then I was able to load 7.0.10, and the module started working again. However, if I boot into 7.0.11 or 7.0.12, the module stops working.

Hello, 
The logs show that the module itself isn't signed... which shouldn't be the case since we introduced module signing a while ago
Could you reinstall slimbook-qc71-kmod?

 Could you also show the output of `slimbookctl info`? That will show if the module is loaded or not

Regards,

Before I reinstalled the module, this was the result of slimbookctl info:

uptime: 0h 2m 57s

kernel: Linux version 7.0.12-100.fc43.x86_64 (mockbuild@d87f766b04bc44ca8931a8bd5ae4950a) (gcc (GCC) 15.2.1 20260123 (Red Hat 15.2.1-7), GNU ld version 2.45.1-4.fc43) #1 SMP PREEMPT_DYNAMIC Tue Jun  9 19:12:44 UTC 2026

memory free/total: 21.51 GB/30.63 GB

disk free/total: / 99.59 GB/464.17 GB

disk free/total: /home 99.59 GB/464.17 GB

disk free/total: /boot 228.20 MB/973.42 MB

disk free/total: /boot/efi 213.14 MB/598.81 MB

boot mode: UEFI

product: CREA15-A8-RTX

sku: CREA15-A8-RTX

vendor: SLIMBOOK

bios: N.1.09GOS00

EC: 1.16

serial: GM5HG7A2244502680

cpu: AMD Ryzen 7 8845HS w/ Radeon 780M Graphics x 16

memory device: 16384 MB 5600 MT/s

memory device: 16384 MB 5600 MT/s

UMA Framebuffer: 512.00 MB

ac: Offline

battery info: 98% Discharging 48020 mAh

primary fan speed: 1962 RPM

secondary fan speed: 1965 RPM

model:0x20001

platform:0x100

family:creative

module loaded:yes

fn lock: yes

super key lock: no

profile: unknown

After reinstalling the module, this is the result of slimbookctl info:

uptime: 0h 8m 32s

kernel: Linux version 7.0.12-100.fc43.x86_64 (mockbuild@d87f766b04bc44ca8931a8bd5ae4950a) (gcc (GCC) 15.2.1 20260123 (Red Hat 15.2.1-7), GNU ld version 2.45.1-4.fc43) #1 SMP PREEMPT_DYNAMIC Tue Jun  9 19:12:44 UTC 2026

memory free/total: 20.34 GB/30.63 GB

disk free/total: / 99.58 GB/464.17 GB

disk free/total: /home 99.58 GB/464.17 GB

disk free/total: /boot 228.20 MB/973.42 MB

disk free/total: /boot/efi 213.14 MB/598.81 MB

boot mode: UEFI

product: CREA15-A8-RTX

sku: CREA15-A8-RTX

vendor: SLIMBOOK

bios: N.1.09GOS00

EC: 1.16

serial: GM5HG7A2244502680

cpu: AMD Ryzen 7 8845HS w/ Radeon 780M Graphics x 16

memory device: 16384 MB 5600 MT/s

memory device: 16384 MB 5600 MT/s

UMA Framebuffer: 512.00 MB

ac: Offline

battery info: 97% Discharging 47530 mAh

primary fan speed: 1970 RPM

secondary fan speed: 0 RPM

model:0x20001

platform:0x100

family:creative

module loaded:yes

fn lock: yes

super key lock: no

profile: unknown

I'm still getting no functionality even after reinstalling the module.

 Hi,

  I'm experiencing a related but slightly different issue on a Slimbook EVO15-AI9-STP running Pop!_OS 24.04 with kernel 7.0.11-76070011-generic.

  The qc71_laptop module loads and works partially — fan control, fn-lock, performance modes, and turbo all work fine. However, the battery submodule (and led_lightbar, led_keyboard, debugfs) fail at every boot with error -19 (ENODEV):

  qc71_laptop/main: qc71_laptop_module_init: project id: 26

  qc71_laptop/main: qc71_laptop_module_init: platform id: 72

  qc71_laptop/features: check_features_bios: BIOS version string: 'N.1.20GOS04'

  qc71_laptop/main: qc71_laptop_module_init: supported features: super-key-lock fan-boost fn-lock silent-mode turbo-mode

  qc71_laptop/main: qc71_laptop_module_init: failed to initialize battery submodule: -19

  qc71_laptop/main: qc71_laptop_module_init: failed to initialize led_lightbar submodule: -19

  qc71_laptop/main: qc71_laptop_module_init: failed to initialize led_keyboard submodule: -19

  qc71_laptop/main: qc71_laptop_module_init: failed to initialize debugfs submodule: -19

  The practical consequence is that /sys/class/power_supply/BAT0/charge_control_start_threshold and charge_control_end_threshold are never exposed, so no software charge limiting is possible. I've just updated to BIOS N.1.20GOS04 / EC 1.29 —

  the failure persists.

  I've worked around this by setting "Battery Maximum Limit" to 80% directly in BIOS Advanced, but there's no separate resume threshold exposed there either, which raises a micro-cycling concern.

  Has anyone resolved the battery submodule failure on this model? Is this a known EC register mismatch with the EVO15 firmware? Any pointer to a patch or workaround would be much appreciated.

  Thanks

There is a https://github.com/Slimbook-Team/qc71_laptop PR with the fix, at least for me.