Fedora new kernel module broken

Ask Fedora
, , ,
1

The new update released today had my kde desktop broken (I could open some apps) and mouse broken. I had to change to another kernel.
This is what I installed:

   Install  kernel-6.11.3-200.fc40.x86_64                    @updates
    Install  kernel-core-6.11.3-200.fc40.x86_64               @updates
    Install  kernel-devel-6.11.3-200.fc40.x86_64              @updates
    Install  kernel-modules-6.11.3-200.fc40.x86_64            @updates
    Install  kernel-modules-core-6.11.3-200.fc40.x86_64       @updates
    Install  kernel-modules-extra-6.11.3-200.fc40.x86_64      @updates
    Upgrade  fluidsynth-libs-2.3.6-2.fc40.x86_64              @updates
    Upgrade  kernel-devel-matched-6.11.3-200.fc40.x86_64      @updates
    Upgrade  kernel-headers-6.11.3-200.fc40.x86_64            @updates
    Upgrade  libmysofa-1.3.2-3.20240917git2297dd8.fc40.x86_64 @updates
    Upgrade  systemd-255.13-1.fc40.x86_64                     @updates
    Upgrade  systemd-libs-255.13-1.fc40.i686                  @updates
    Upgrade  systemd-libs-255.13-1.fc40.x86_64                @updates
    Upgrade  systemd-networkd-255.13-1.fc40.x86_64            @updates
    Upgrade  systemd-oomd-defaults-255.13-1.fc40.noarch       @updates
    Upgrade  systemd-pam-255.13-1.fc40.x86_64                 @updates
    Upgrade  systemd-resolved-255.13-1.fc40.x86_64            @updates
    Upgrade  systemd-rpm-macros-255.13-1.fc40.noarch          @updates
    Upgrade  systemd-udev-255.13-1.fc40.x86_64                @updates
    Upgraded kernel-6.10.10-200.fc40.x86_64                   @@System
    Upgraded kernel-core-6.10.10-200.fc40.x86_64              @@System
    Upgraded kernel-devel-6.10.10-200.fc40.x86_64             @@System
    Upgraded kernel-modules-6.10.10-200.fc40.x86_64           @@System
    Upgraded kernel-modules-core-6.10.10-200.fc40.x86_64      @@System
    Upgraded kernel-modules-extra-6.10.10-200.fc40.x86_64     @@System
    Upgraded fluidsynth-libs-2.3.6-1.fc40.x86_64              @@System
    Upgraded kernel-devel-matched-6.10.12-200.fc40.x86_64     @@System
    Upgraded kernel-headers-6.10.3-200.fc40.x86_64            @@System
    Upgraded libmysofa-1.2.1-7.fc40.x86_64                    @@System
    Upgraded systemd-255.12-1.fc40.x86_64                     @@System
    Upgraded systemd-libs-255.12-1.fc40.i686                  @@System
    Upgraded systemd-libs-255.12-1.fc40.x86_64                @@System
    Upgraded systemd-networkd-255.12-1.fc40.x86_64            @@System
    Upgraded systemd-oomd-defaults-255.12-1.fc40.noarch       @@System
    Upgraded systemd-pam-255.12-1.fc40.x86_64                 @@System
    Upgraded systemd-resolved-255.12-1.fc40.x86_64            @@System
    Upgraded systemd-rpm-macros-255.12-1.fc40.noarch          @@System
    Upgraded systemd-udev-255.12-1.fc40.x86_64                @@System

my system:

Operating System: Fedora Linux 40
KDE Plasma Version: 6.2.0
KDE Frameworks Version: 6.7.0
Qt Version: 6.7.2
Kernel Version: 6.10.12-200.fc40.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × Intel® Core™ i7-10700KF CPU @ 3.80GHz
Memory: 31,2 GiB of RAM
Graphics Processor: NVIDIA GeForce RTX 3070/PCIe/SSE2
Manufacturer: ASUS

I don’t know where to post

2

When hardware fails after an update, it is usually something in the kernel. If you can run dmesg while booted into the non-working kernel, there might be hints in there about what is going wrong.

3

Sorry, but now that I have it working, I’m not gonna risk it, But thanks.

4

You should be able to look at the logs of the previous boot (or whichever boot you had the issue in) from the current boot.

Take a look at this:

So, this should work:

journalctl --list-boots # list boots, see which one you want to see log of
journal -b <boot number> -k # kernel logs for that boot

If you leave out the -k, you’ll see all the logs—that’s also worth looking at if nothing useful comes up in the kernel logs.