Mageia forum

Hello community!

The last months were just crazy and real life was busy. Now I am back and have again some more time for my hobby and Mageia, that btw runs just great like usual on my Thinkpad.

Now I bought, for the very first time, a Linux machine for my wife and I installed Mageia 8 with Plasma on it. It is a Slimbook Essential with a very modern, maybe too modern, AMD Ryzen 5500 processor. Actually it should come with a 5400 but it was out of stock so we received the newer one. It seems to be working fine with Mageia but the problem is with resume after suspend, especially on battery. Then it loses sound, Bluetooth and the control of the RGB backlight keyboard.

I have still no solution for it except for disabling suspend for now. I guess kernel 5.15 is too old for that hardware but I am not 100 per cent sure. On the Slimbook forum I have still no reply.

Has anybody by any chance experience with such Ryzen processors?

PS: The machine came with Kubuntu 20.04 because I wanted her to test drive it first with something more mainstream. No luck. It was worse. And it was a "supported" OEM install. For me personally I would not even buy it with any OS. Though I wanted to see how they handle it. I have to say I am not impressed.

From what I'm seeing, it supposedly works well with kernel 5.13 and above. Did you try configuring it in MCC?

Germ wrote:Did you try configuring it in MCC?

How should he configure suspend/resume in MCC? There are no settings for it

vinylninja wrote:problem is with resume after suspend, especially on battery. Then it loses sound, Bluetooth and the control of the RGB backlight keyboard.

sturmvogel wrote:How should he configure suspend/resume in MCC? There are no settings for it

Exactly. I mean I was in the MCC just in case to see if I could tackle some of the things there.

Today I got a support email telling me what to do on Kubuntu to solve the sound issue but I really would prefer to use Mageia on that machine. It runs smoother and it is what I use. The kernel is newer, Plasma is newer. Even if I fix the sound issue with a systemd script, I still have to solve Bluetooth and the RGB keyboard. It will be interesting.
I can see all the irony in buying hardware that is supposed to support Linux. Of course it could be that I just have to throw something bleeding edge on it but it is not for me, it is for my wife.

Germ wrote:From what I'm seeing, it supposedly works well with kernel 5.13 and above.

That is what I thought.

For me it sounds like that some components don't get the right signal to wake up again. Maybe you could look if there are some energy/suspend related settings in BIOS.

And maybe post the response from support regarding sound problem. Maybe it points somebody here in our forum in the right direction whats going on with Bluetoth and RGB.
Btw, does only the RGB lighting not work or the complete keyboard?

sturmvogel wrote:For me it sounds like that some components don't get the right signal to wake up again. Maybe you could look if there are some energy/suspend related settings in BIOS.

Will try that.

sturmvogel wrote:And maybe post the response from support regarding sound problem. Maybe it points somebody here in our forum in the right direction whats going on with Bluetoth and RGB.

I will post the solution later. I have to go back to work though the conversation itself was in Spanish.

sturmvogel wrote:Btw, does only the RGB lighting not work or the complete keyboard?

Only the lighting does not work.
Just moments ago all of a sudden she lost the Bluetooth connection on battery, not for the first time, and cannot reconnect. That is one example.

It might help if you could add some logs. After a clean boot, as root run

Code: Select all: journalctl -af

and leave that running in a terminal.
Then suspend your slimbook, wait a minute or so, and wake it up again. Wait a minute, then post the log excerpt here. And don't forget to mention the timestamp in your logs when you triggered suspend.

Although in general there seem to be some issues with the slimbooks:
https://www.reddit.com/r/slimbook/comme ... t_is_your/

You guys are great.

doktor5000 wrote:It might help if you could add some logs. After a clean boot, as root run

Will do that when I have access to the machine again.

First I will post the recommended solution from the Slimbook forums and they are determined to reproduce my issue on Kubuntu regarding Bluetooth and backlight, we will see.

For the sound issue under Kubuntu I should make a soundfix2.sh in /lib/systemd/system-sleep/ like this:

Code: Select all: #!bin/bash if [ "${1}" == "post" ]; then sleep 30 farts=`lspci -vvv | grep "Audio device" | cut -d " " -f1` for i in $farts do echo 1 > /sys/bus/pci/devices/0000:$i/remove done echo 1 > /sys/bus/pci/rescan fi

doktor5000 wrote:.
Although in general there seem to be some issues with the slimbooks:
https://www.reddit.com/r/slimbook/comme ... t_is_your/

Yep, I saw that post already and also in some other places. Suspend seems to be an issue most of the times.

First I will try to see the logs on Mageia before I dive back into Kubuntu trying the script. Mageia with Plasma is such a treat to use, really, and I am an Xfce user normally.

vinylninja wrote:For the sound issue under Kubuntu I should make a soundfix2.sh in /lib/systemd/system-sleep/ like this:

FWIW that's not specific to Kubuntu, it would work under any linux distro. So if your sound does not work after resume, it would help the same way under Mageia.

I know that. Thing is, sound in Mageia works.

I should have said trying the script and more because they consider Ubuntu more supported (preinstalled if you want) than e.g. Mageia even though the Slimbook is supposed to work with most Linux distributions as by the support forum.

That is why I think the response I got from them is not really doing anything right now.

I made some tests on battery and Mageia works just fine as far as we can see at the moment after resuming the laptop from suspend. I installed tlp on it before. But that seems to be the culprit. Though I installed it because Slimbook installed it before on Kubuntu and their battery tool is made on top of tlp. Could mean that without the battery tool or tlp it would also run fine under Kubuntu but there I already disabled the battery tool and it improved but then sound was lost again and Plasma had some bugs and apport immediately wanted stuff to report. Dolphin became unresponsive etc. It accumulated. The whole reason why I thought to install my distro of choice, Mageia, on my wife's Slimbook.

When I removed tlp on Mageia the Slimbook wakes up with sound, with a stable Bluetooth connection (she uses headphones) and no bugs or crashes at all. That is good news. The only thing that does not work is the backlight keyboard. The lights go on after a clean boot but are disabled after suspending. Though they are not customizable at all and only show one color. However this is an RGB keyboard. I have to figure that out. The software that Slimbook uses is officially not supported under Mageia. I wonder how they ship Fedora or openSUSE without such a PPA for the RGB keyboard? But then under Kubuntu it was never necessary to use the software to customize colors as the keyboard itself has keys for it and the software does just that, switching and nothing else or I am missing something.

I advised her to do some logging but I am not sure if it was successful. She might have stopped it too soon. I do not really see anything special there to explain why the keyboard lights fail.

At the end nothing happened when she copied the lines but after some minutes there were more messages. So it might be I have to repeat that.

Here it is:

Code: Select all: feb 08 03:16:49 o2.box systemd[1]: Starting Suspend... feb 08 03:16:49 o2.box systemd-sleep[5872]: Suspending system... feb 08 03:16:49 o2.box kernel: PM: suspend entry (s2idle) feb 08 03:16:49 o2.box kernel: Filesystems sync: 0.004 seconds feb 08 03:18:10 o2.box kernel: Freezing user space processes ... (elapsed 0.001 seconds) done. feb 08 03:18:10 o2.box kernel: OOM killer disabled. feb 08 03:18:10 o2.box kernel: Freezing remaining freezable tasks ... (elapsed 0.000 seconds) done. feb 08 03:18:10 o2.box kernel: printk: Suspending console(s) (use no_console_suspend to debug) feb 08 03:18:10 o2.box kernel: wlo1: deauthenticating from f4:69:42:20:13:f2 by local choice (Reason: 3=DEAUTH_LEAVING) feb 08 03:18:10 o2.box kernel: ACPI: EC: interrupt blocked feb 08 03:18:10 o2.box kernel: ACPI: EC: interrupt unblocked feb 08 03:18:10 o2.box kernel: pci 0000:00:00.2: can't derive routing for PCI INT A feb 08 03:18:10 o2.box kernel: pci 0000:00:00.2: PCI INT A: no GSI feb 08 03:18:10 o2.box kernel: [drm] PCIE GART of 1024M enabled. feb 08 03:18:10 o2.box kernel: [drm] PTB located at 0x000000F400900000 feb 08 03:18:10 o2.box kernel: amdgpu 0000:05:00.0: amdgpu: SMU is resuming... feb 08 03:18:10 o2.box kernel: amdgpu 0000:05:00.0: amdgpu: dpm has been disabled feb 08 03:18:10 o2.box kernel: amdgpu 0000:05:00.0: amdgpu: SMU is resumed successfully! feb 08 03:18:10 o2.box kernel: [drm] DMUB hardware initialized: version=0x01000000 feb 08 03:18:10 o2.box kernel: r8169 0000:02:00.0 enp2s0: Link is Down feb 08 03:18:10 o2.box kernel: usb 3-4: reset high-speed USB device number 3 using xhci_hcd feb 08 03:18:10 o2.box kernel: [drm] VCN decode and encode initialized successfully(under DPG Mode). feb 08 03:18:10 o2.box kernel: [drm] JPEG decode initialized successfully. feb 08 03:18:10 o2.box kernel: amdgpu 0000:05:00.0: amdgpu: ring gfx uses VM inv eng 0 on hub 0 feb 08 03:18:10 o2.box kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.0 uses VM inv eng 1 on hub 0 feb 08 03:18:10 o2.box kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.0 uses VM inv eng 4 on hub 0 feb 08 03:18:10 o2.box kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.0 uses VM inv eng 5 on hub 0 feb 08 03:18:10 o2.box kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.0 uses VM inv eng 6 on hub 0 feb 08 03:18:10 o2.box kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.0.1 uses VM inv eng 7 on hub 0 feb 08 03:18:10 o2.box kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.1.1 uses VM inv eng 8 on hub 0 feb 08 03:18:10 o2.box kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.2.1 uses VM inv eng 9 on hub 0 feb 08 03:18:10 o2.box kernel: amdgpu 0000:05:00.0: amdgpu: ring comp_1.3.1 uses VM inv eng 10 on hub 0 feb 08 03:18:10 o2.box kernel: amdgpu 0000:05:00.0: amdgpu: ring kiq_2.1.0 uses VM inv eng 11 on hub 0 feb 08 03:18:10 o2.box kernel: amdgpu 0000:05:00.0: amdgpu: ring sdma0 uses VM inv eng 0 on hub 1 feb 08 03:18:10 o2.box kernel: amdgpu 0000:05:00.0: amdgpu: ring vcn_dec uses VM inv eng 1 on hub 1 feb 08 03:18:10 o2.box kernel: amdgpu 0000:05:00.0: amdgpu: ring vcn_enc0 uses VM inv eng 4 on hub 1 feb 08 03:18:10 o2.box kernel: amdgpu 0000:05:00.0: amdgpu: ring vcn_enc1 uses VM inv eng 5 on hub 1 feb 08 03:18:10 o2.box kernel: amdgpu 0000:05:00.0: amdgpu: ring jpeg_dec uses VM inv eng 6 on hub 1 feb 08 03:18:10 o2.box kernel: ata2: SATA link down (SStatus 0 SControl 300) feb 08 03:18:10 o2.box kernel: ata1: SATA link down (SStatus 0 SControl 300) feb 08 03:18:10 o2.box kernel: nvme nvme0: 8/0/0 default/read/poll queues feb 08 03:18:10 o2.box kernel: usb 3-3: reset full-speed USB device number 2 using xhci_hcd feb 08 03:18:10 o2.box kernel: OOM killer enabled. feb 08 03:18:10 o2.box kernel: Restarting tasks ... done. feb 08 03:18:10 o2.box kernel: PM: suspend exit feb 08 03:18:10 o2.box bluetoothd[848]: Endpoint unregistered: sender=:1.66 path=/MediaEndpoint/A2DPSink/sbc feb 08 03:18:10 o2.box systemd-sleep[5872]: System resumed. feb 08 03:18:10 o2.box bluetoothd[848]: Endpoint unregistered: sender=:1.66 path=/MediaEndpoint/A2DPSource/sbc feb 08 03:18:10 o2.box upowerd[891]: treating change event as add on /sys/devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-3 feb 08 03:18:10 o2.box systemd[1]: systemd-suspend.service: Succeeded. feb 08 03:18:10 o2.box systemd[1]: Finished Suspend. feb 08 03:18:10 o2.box systemd[1]: Stopped target Sleep. feb 08 03:18:10 o2.box systemd[1]: Reached target Suspend. feb 08 03:18:10 o2.box systemd[1]: Stopped target Suspend. feb 08 03:18:10 o2.box upowerd[891]: treating change event as add on /sys/devices/pci0000:00/0000:00:08.1/0000:05:00.4/usb3/3-3 feb 08 03:18:10 o2.box systemd[1]: Stopped target Bluetooth. feb 08 03:18:10 o2.box systemd-logind[884]: Operation 'sleep' finished. feb 08 03:18:10 o2.box plasmashell[3278]: file:///usr/lib64/qt5/qml/org/kde/plasma/extras/ExpandableListItem.qml:314: TypeError: Cannot read property 'width' of null feb 08 03:18:10 o2.box plasmashell[3278]: qt.svg: <input>:406:376: Could not add child element to parent element because the types are incorrect. feb 08 03:18:10 o2.box plasmashell[3278]: qt.svg: <input>:407:130: Could not add child element to parent element because the types are incorrect. feb 08 03:18:10 o2.box plasmashell[3278]: qt.svg: <input>:408:130: Could not add child element to parent element because the types are incorrect. feb 08 03:18:10 o2.box plasmashell[3278]: qt.svg: <input>:408:393: Could not add child element to parent element because the types are incorrect. feb 08 03:18:10 o2.box plasmashell[3278]: qt.svg: <input>:409:130: Could not add child element to parent element because the types are incorrect. feb 08 03:18:10 o2.box plasmashell[3278]: qt.svg: <input>:410:129: Could not add child element to parent element because the types are incorrect. feb 08 03:18:10 o2.box plasmashell[3278]: qt.svg: <input>:411:129: Could not add child element to parent element because the types are incorrect. feb 08 03:18:10 o2.box plasmashell[3278]: qt.svg: <input>:412:129: Could not add child element to parent element because the types are incorrect. feb 08 03:18:10 o2.box plasmashell[3278]: qt.svg: <input>:413:129: Could not add child element to parent element because the types are incorrect. feb 08 03:18:10 o2.box plasmashell[3278]: qt.svg: <input>:413:379: Could not add child element to parent element because the types are incorrect. feb 08 03:18:10 o2.box plasmashell[3278]: qt.svg: <input>:413:631: Could not add child element to parent element because the types are incorrect. feb 08 03:18:10 o2.box kscreenlocker_greet[5846]: Connecting to deprecated signal QDBusConnectionInterface::serviceOwnerChanged(QString,QString,QString) feb 08 03:18:10 o2.box kscreenlocker_greet[5846]: file:///usr/share/plasma/look-and-feel/org.kde.breeze.desktop/contents/components/VirtualKeyboard.qml:20:1: module "QtQuick.VirtualKeyboard" is not installed feb 08 03:18:11 o2.box ifplugd(wlo1)[2327]: Link beat lost. feb 08 03:18:13 o2.box kernel: Bluetooth: hci0: Bootloader revision 0.3 build 0 week 24 2017 feb 08 03:18:13 o2.box kernel: Bluetooth: hci0: Device revision is 1 feb 08 03:18:13 o2.box kernel: Bluetooth: hci0: Secure boot is enabled feb 08 03:18:13 o2.box kernel: Bluetooth: hci0: OTP lock is enabled feb 08 03:18:13 o2.box kernel: Bluetooth: hci0: API lock is enabled feb 08 03:18:13 o2.box kernel: Bluetooth: hci0: Debug lock is disabled feb 08 03:18:13 o2.box kernel: Bluetooth: hci0: Minimum firmware build 1 week 10 2014 feb 08 03:18:13 o2.box kernel: Bluetooth: hci0: Found device firmware: intel/ibt-20-1-3.sfi feb 08 03:18:13 o2.box systemd[3028]: Reached target Bluetooth. feb 08 03:18:13 o2.box systemd[1]: Reached target Bluetooth. feb 08 03:18:14 o2.box kernel: wlo1: authenticate with f4:69:42:20:13:ef feb 08 03:18:14 o2.box kernel: wlo1: send auth to f4:69:42:20:13:ef (try 1/3) feb 08 03:18:14 o2.box kernel: wlo1: authenticated feb 08 03:18:14 o2.box kernel: wlo1: associate with f4:69:42:20:13:ef (try 1/3) feb 08 03:18:14 o2.box kernel: wlo1: RX AssocResp from f4:69:42:20:13:ef (capab=0x431 status=0 aid=50) feb 08 03:18:14 o2.box kernel: wlo1: associated feb 08 03:18:15 o2.box ifplugd(wlo1)[2327]: Link beat detected. feb 08 03:18:15 o2.box kernel: Bluetooth: hci0: Waiting for firmware download to complete feb 08 03:18:15 o2.box kernel: Bluetooth: hci0: Firmware loaded in 1715777 usecs feb 08 03:18:15 o2.box kernel: Bluetooth: hci0: Waiting for device to boot feb 08 03:18:15 o2.box kernel: Bluetooth: hci0: Device booted in 14931 usecs feb 08 03:18:15 o2.box kernel: Bluetooth: hci0: Found Intel DDC parameters: intel/ibt-20-1-3.ddc feb 08 03:18:15 o2.box kernel: Bluetooth: hci0: Applying Intel DDC parameters completed feb 08 03:18:15 o2.box kernel: Bluetooth: hci0: Firmware revision 0.3 build 125 week 46 2021 feb 08 03:18:15 o2.box bluetoothd[848]: Endpoint registered: sender=:1.66 path=/MediaEndpoint/A2DPSink/sbc feb 08 03:18:15 o2.box bluetoothd[848]: Endpoint registered: sender=:1.66 path=/MediaEndpoint/A2DPSource/sbc feb 08 03:18:15 o2.box plasmashell[3278]: file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/FullRepresentation.qml:105:13: Unable to assign [undefined] to QQuickAction* feb 08 03:18:15 o2.box plasmashell[3278]: file:///usr/share/plasma/plasmoids/org.kde.plasma.bluetooth/contents/ui/DeviceItem.qml:32:5: Unable to assign [undefined] to bool

Edit: On my Thinkpad I use tlp. It works great and it really extends the battery life. Just a side note. I think this Slimbook model is not very compatible with it.

You may want to check https://linrunner.de/tlp/support/troubleshooting.html if you want to keep using tlp.
It might be some common issue like broken USB autosuspend or PCIe power management which affects multiple devices.

For the keyboard, might help if you could add the output of

Code: Select all: lspcidrake -v

so we can see how the keyboard is connected internally.

Code: Select all: lspcidrake -v unknown : Advanced Micro Devices, Inc. [AMD]|FCH SATA Controller [AHCI mode] [STORAGE_SATA] (vendor:1022 device:7901 subv:1558 subd:a600) (rev: 81) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir Device 24: Function 5 [BRIDGE_HOST] (vendor:1022 device:144d) snd_pci_acp3x : Advanced Micro Devices, Inc. [AMD]|Raven/Raven2/FireFlight/Renoir Audio Processor [MULTIMEDIA_OTHER] (vendor:1022 device:15e2 subv:1558 subd:a600) (rev: 01) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir Internal PCIe GPP Bridge to Bus [BRIDGE_PCI] (vendor:1022 device:1635) i2c_piix4 : Advanced Micro Devices, Inc. [AMD]|FCH SMBus Controller [SERIAL_SMBUS] (vendor:1022 device:790b subv:1558 subd:a600) (rev: 51) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir Device 24: Function 7 [BRIDGE_HOST] (vendor:1022 device:144f) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir PCIe Dummy Host Bridge [BRIDGE_HOST] (vendor:1022 device:1632) unknown : Phison Electronics Corporation|PS5013 E13 NVMe Controller (vendor:1987 device:5013) (rev: 01) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir/Cezanne PCIe GPP Bridge [BRIDGE_PCI] (vendor:1022 device:1634) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir Device 24: Function 0 [BRIDGE_HOST] (vendor:1022 device:1448) Card:ATI Volcanic Islands and later (amdgpu): Advanced Micro Devices, Inc. [AMD/ATI]|Lucienne [DISPLAY_VGA] (vendor:1002 device:164c subv:1558 subd:a600) (rev: c2) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir/Cezanne PCIe GPP Bridge [BRIDGE_PCI] (vendor:1022 device:1634) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir Device 24: Function 2 [BRIDGE_HOST] (vendor:1022 device:144a) ccp : Advanced Micro Devices, Inc. [AMD]|Family 17h (Models 10h-1fh) Platform Security Processor [CRYPT_OTHER] (vendor:1022 device:15df subv:1558 subd:a600) unknown : Advanced Micro Devices, Inc. [AMD]|FCH SATA Controller [AHCI mode] [STORAGE_SATA] (vendor:1022 device:7901 subv:1558 subd:a600) (rev: 81) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir/Cezanne PCIe GPP Bridge [BRIDGE_PCI] (vendor:1022 device:1634) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir Device 24: Function 4 [BRIDGE_HOST] (vendor:1022 device:144c) xhci_pci : Advanced Micro Devices, Inc. [AMD]|Renoir/Cezanne USB 3.1 [SERIAL_USB] (vendor:1022 device:1639 subv:1558 subd:a600) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir Internal PCIe GPP Bridge to Bus [BRIDGE_PCI] (vendor:1022 device:1635 subv:00fc subd:0000) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir/Cezanne Root Complex [BRIDGE_HOST] (vendor:1022 device:1630 subv:1558 subd:a600) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir Device 24: Function 6 [BRIDGE_HOST] (vendor:1022 device:144e) snd_hda_intel : Advanced Micro Devices, Inc. [AMD]|Family 17h (Models 10h-1fh) HD Audio Controller [MULTIMEDIA_AUDIO_DEV] (vendor:1022 device:15e3 subv:1558 subd:a600) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir/Cezanne IOMMU (vendor:1022 device:1631 subv:1558 subd:a600) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir/Cezanne PCIe GPP Bridge [BRIDGE_PCI] (vendor:1022 device:1634) rtsx_pci : Realtek Semiconductor Co., Ltd.|RTS522A PCI Express Card Reader (vendor:10ec device:522a subv:1558 subd:a600) (rev: 01) unknown : Advanced Micro Devices, Inc. [AMD]|FCH LPC Bridge [BRIDGE_ISA] (vendor:1022 device:790e subv:1558 subd:a600) (rev: 51) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir PCIe Dummy Host Bridge [BRIDGE_HOST] (vendor:1022 device:1632) r8169 : Realtek Semiconductor Co., Ltd.|RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller [NETWORK_ETHERNET] (vendor:10ec device:8168 subv:1558 subd:a600) (rev: 15) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir Device 24: Function 1 [BRIDGE_HOST] (vendor:1022 device:1449) snd_hda_intel : Advanced Micro Devices, Inc. [AMD/ATI]|Renoir Radeon High Definition Audio Controller [MULTIMEDIA_AUDIO_DEV] (vendor:1002 device:1637 subv:1558 subd:a600) k10temp : Advanced Micro Devices, Inc. [AMD]|Renoir Device 24: Function 3 [BRIDGE_HOST] (vendor:1022 device:144b) xhci_pci : Advanced Micro Devices, Inc. [AMD]|Renoir/Cezanne USB 3.1 [SERIAL_USB] (vendor:1022 device:1639 subv:1558 subd:a600) unknown : Advanced Micro Devices, Inc. [AMD]|Renoir PCIe Dummy Host Bridge [BRIDGE_HOST] (vendor:1022 device:1632) iwlwifi : Intel Corporation|Wi-Fi 6 AX200 [NETWORK_OTHER] (vendor:8086 device:2723 subv:8086 subd:0084) (rev: 1a) hub : Linux 5.15.18-desktop-2.mga8 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002) usb_storage : USBest Technology|Intenso Rainbow Line [Mass Storage|SCSI|Bulk-Only] (vendor:1307 device:0165) hub : Linux 5.15.18-desktop-2.mga8 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0003) hub : Linux 5.15.18-desktop-2.mga8 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0002) btusb : Intel Corp.|AX200 Bluetooth [Wireless|Radio Frequency|Bluetooth] (vendor:8087 device:0029) uvcvideo : Sonix Technology Co., Ltd.|BisonCam,NB Pro [Video|Video Control] (vendor:5986 device:9102) hub : Linux 5.15.18-desktop-2.mga8 xhci-hcd|xHCI Host Controller [Hub|Unused|Full speed (or root) hub] (vendor:1d6b device:0003) hid_generic : FTCS1000:00 2808:0101

This only seems to be your touchpad

vinylninja wrote:
Code: Select all
lspcidrake -v hid_generic : FTCS1000:00 2808:0101

For the installation of the driver for the keyboard, have a look at https://github.com/slimbook/keyboard/bl ... all_rgb.sh
The driver is based on https://bitbucket.org/tuxedocomputers/c ... rc/master/ and https://github.com/dariost/clevo-xsm-wmi

Although the source code for the control app does not seem to be available directly. You would need to grab the debian package from
https://ppa.launchpadcontent.net/slimbo ... bkeyboard/ and convert it to an RPM.
We may need to check that, because a fixed version of alien (which is used for the conversion from .deb to RPM) is only available from https://bugs.mageia.org/show_bug.cgi?id=28607

doktor5000 wrote:For the installation of the driver for the keyboard, have a look at https://github.com/slimbook/keyboard/bl ... all_rgb.sh
The driver is based on https://bitbucket.org/tuxedocomputers/c ... rc/master/ and https://github.com/dariost/clevo-xsm-wmi

Cool. I will try that. Thank you very much for your help and kind advise.

We really do not need the software for it to work if unnecessary. The hardware switches would be sufficient. Will see what I can do over the weekend.

I also found this with a section for other distros than Ubuntu:

https://github.com/slimbook/keyboard

vinylninja wrote:We really do not need the software for it to work if unnecessary. The hardware switches would be sufficient.

Yeah sure but it's usually cheaper to omit those hardware switches and implement that in software ...

Actually I successfully converted the Slimbook keyboard app to an RPM package and installed it afterwards though ist does not work either.

I think for now I will give up on it. The laptop works just perfectly even though the RGB lights are not but I guess we will wait until it resolves itself in the future. I lost my patience and my wife needs it for work so I cannot take the laptop anymore and try to solve issues for hours or while I have no access to the machine.

doktor5000 wrote:This only seems to be your touchpad
vinylninja wrote:
Code: Select all
lspcidrake -v hid_generic : FTCS1000:00 2808:0101

For the installation of the driver for the keyboard, have a look at https://github.com/slimbook/keyboard spacebar test /blob/main/install_rgb.sh
The driver is based on https://bitbucket.org/tuxedocomputers/c ... rc/master/ and https://github.com/dariost/clevo-xsm-wmi

Although the source code for the control app does not seem to be available directly. You would need to grab the debian package from
https://ppa.launchpadcontent.net/slimbo ... bkeyboard/ and convert it to an RPM.
We may need to check that, because a fixed version of alien (which is used for the conversion from .deb to RPM) is only available from https://bugs.mageia.org/show_bug.cgi?id=28607

Source file is still not appearing in the other link

If you want that, then you'd probably need to ask the authors of the drivers or the laptop vendors to provide the source code.

Mageia forum

(partially solved) Ryzen 5500 Slimbook

(partially solved) Ryzen 5500 Slimbook

Re: Ryzen 5500 Slimbook

Re: Ryzen 5500 Slimbook

Re: Ryzen 5500 Slimbook

Re: Ryzen 5500 Slimbook

Re: Ryzen 5500 Slimbook

Re: Ryzen 5500 Slimbook

Re: Ryzen 5500 Slimbook

Re: Ryzen 5500 Slimbook

Re: Ryzen 5500 Slimbook

Re: Ryzen 5500 Slimbook

Re: Ryzen 5500 Slimbook

Re: Ryzen 5500 Slimbook

Re: Ryzen 5500 Slimbook

Re: Ryzen 5500 Slimbook

Re: Ryzen 5500 Slimbook

Re: Ryzen 5500 Slimbook

Re: Ryzen 5500 Slimbook

Re: (partially solved) Ryzen 5500 Slimbook