Kernel panic in 7.0, works in 6.14

Support and Help
1

Hello there!

I have two systems, dual boot laptop (Windows/Ubuntu) and standalone PC (Ubuntu). SInce June, the default boot always stops at the Kernel Panic message of death.

I have recently noticed that I can use the Advanced option of the GNU GRUB startup menu to choose between the default kernel release 6.17 (Kernel Panic) and 6.14.0-37-generic (works fine, says Ubuntu 24.04.5 LTS).

I tried Software update but I still have the problem, the only change is that now, the default kernel release is 7.0 (also Kernel Panic), but I still have the option of kernel 6.14 


Do I understand that my only option is to use the Advanced menu on boot - or is there a recommended (and easy!) fix for my type of problem?

Thanks for help.

Kernel Panic because of DKMS
Ubuntu Weekly Newsletter Issue 961
2

Does the system do a routine update cleanly? Post the output of:

sudo dkms status
sudo apt dist-upgrade
3

sudo dkms status
tuxedo-yt6801/1.0.29tux0, 6.14.0-37-generic, x86_64: installed

(sorry some messages in French in the following
)

sudo apt dist-upgrade
Lecture des listes de paquets
 Fait
Construction de l’arbre des dĂ©pendances
 Fait
Lecture des informations d’état
 Fait
Calcul de la mise à jour
 Fait
Les paquets suivants ont été installés automatiquement et ne sont plus nécessaires :
libfwupd2 libwoff1
Veuillez utiliser « sudo apt autoremove » pour les supprimer.
Get more security updates through Ubuntu Pro with ‘esm-apps’ enabled:
libmagickcore-6.q16-7t64 libzvbi-common libglut-dev
libmagickcore-6.q16-7-extra python3-pip-whl gimp-data libcjson1
libopenexr-3-1-30 libpostproc57 libmbedcrypto7t64 libavcodec60
libgstreamer-plugins-bad1.0-0 libzvbi0t64 libavutil58 libswscale7
libgimp2.0t64 libswresample4 imagemagick-6-common libavformat60
gstreamer1.0-plugins-bad libglut3.12 freeglut3-dev libavfilter9
libmagickwand-6.q16-7t64
Learn more about Ubuntu Pro at Ubuntu Pro | Ubuntu
Les mises à jour suivantes ont été différées à cause du phasage :
power-profiles-daemon
0 mis à jour, 0 nouvellement installés, 0 à enlever et 1 non mis à jour.
5 partiellement installés ou enlevés.
AprĂšs cette opĂ©ration, 0 o d’espace disque supplĂ©mentaires seront utilisĂ©s.
Souhaitez-vous continuer ? [O/n] O
Paramétrage de linux-headers-7.0.0-31-generic (7.0.0-31.31~24.04.1) 

/etc/kernel/header_postinst.d/dkms:

  • dkms: running auto installation service for kernel 7.0.0-31-generic
    Sign command: /usr/bin/kmodsign
    Signing key: /var/lib/shim-signed/mok/MOK.priv
    Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area

make -j16 KERNELRELEASE=7.0.0-31-generic -C /lib/modules/7.0.0-31-generic/build M=/var/lib/dkms/tuxedo-yt6801/1.0.29tux0/build
(bad ex
it status: 2)
ERROR: Cannot create report: [Errno 17] File exists: ‘/var/crash/tuxedo-yt6801.0.crash’
Error! Bad return status for module build on kernel: 7.0.0-31-generic (x86_64)
Consult /var/lib/dkms/tuxedo-yt6801/1.0.29tux0/build/make.log for more information.
dkms autoinstall on 7.0.0-31-generic/x86_64 failed for tuxedo-yt6801(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.

  • dkms: autoinstall for kernel 7.0.0-31-generic
    
fail!
    run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
    dpkg: erreur de traitement du paquet linux-headers-7.0.0-31-generic (–configure) :
    le sous-processus paquet linux-headers-7.0.0-31-generic script post-installation installĂ© a renvoyĂ© un Ă©tat de sortie d’erreur 11
    Paramétrage de linux-image-7.0.0-31-generic (7.0.0-31.31~24.04.1) 

    Paramétrage de linux-headers-6.17.0-20-generic (6.17.0-20.20~24.04.1) 

    /etc/kernel/header_postinst.d/dkms:
  • dkms: running auto installation service for kernel 6.17.0-20-generic
    Sign command: /usr/bin/kmodsign
    Signing key: /var/lib/shim-signed/mok/MOK.priv
    Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area

make -j16 KERNELRELEASE=6.17.0-20-generic -C /lib/modules/6.17.0-20-generic/build M=/var/lib/dkms/tuxedo-yt6801/1.0.29tux0/build
(bad
exit status: 2)
ERROR: Cannot create report: [Errno 17] File exists: ‘/var/crash/tuxedo-yt6801.0.crash’
Error! Bad return status for module build on kernel: 6.17.0-20-generic (x86_64)
Consult /var/lib/dkms/tuxedo-yt6801/1.0.29tux0/build/make.log for more information.
dkms autoinstall on 6.17.0-20-generic/x86_64 failed for tuxedo-yt6801(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.

  • dkms: autoinstall for kernel 6.17.0-20-generic
    
fail!
    run-parts: /etc/kernel/header_postinst.d/dkms exited with return code 11
    dpkg: erreur de traitement du paquet linux-headers-6.17.0-20-generic (–configure) :
    le sous-processus paquet linux-headers-6.17.0-20-generic script post-installation installĂ© a renvoyĂ© un Ă©tat de sortie d’erreur 11
    dpkg: des problĂšmes de dĂ©pendances empĂȘchent la configuration de linux-headers-generic-hwe-24.04 :
    linux-headers-generic-hwe-24.04 dépend de linux-headers-7.0.0-31-generic; cependant :
    Le paquet linux-headers-7.0.0-31-generic n’est pas encore configurĂ©.

dpkg: erreur de traitement du paquet linux-headers-generic-hwe-24.04 (–configure) :
problÚmes de dépendances - laissé non configuré
dpkg: des problĂšmes de dĂ©pendances empĂȘchent la configuration de linux-generic-hwe-24.04 :
linux-generic-hwe-24.04 dépend de linux-headers-generic-hwe-24.04 (= 7.0.0-31.31~24.04.1); cependant :
Le paquet linux-headers-generic-hwe-24.04 n’est pas encore configurĂ©.

dpkg: erreur de traitement du paquet linux-generic-hwe-24.04 (–configure) :
problÚmes de dépendances - laissé non configuré
Traitement des actions diffĂ©rĂ©es (« triggers ») pour linux-image-7.0.0-31-generic (7.0.0-31.31~24.04.1) 

Aucun rapport « apport » n’a Ă©tĂ© crĂ©Ă© car le message d’erreur indique une erreur consĂ©cutive Ă  un Ă©chec prĂ©cĂ©dent.
Aucun rapport « apport
» écrit car MaxReports a déjà été atteint
/etc/kernel/postinst.d/dkms:

  • dkms: running auto installation service for kernel 7.0.0-31-generic
    Sign command: /usr/bin/kmodsign
    Signing key: /var/lib/shim-signed/mok/MOK.priv
    Public certificate (MOK): /var/lib/shim-signed/mok/MOK.der

Building module:
Cleaning build area

make -j16 KERNELRELEASE=7.0.0-31-generic -C /lib/modules/7.0.0-31-generic/build M=/var/lib/dkms/tuxedo-yt6801/1.0.29tux0/build
(bad ex
it status: 2)
ERROR: Cannot create report: [Errno 17] File exists: ‘/var/crash/tuxedo-yt6801.0.crash’
Error! Bad return status for module build on kernel: 7.0.0-31-generic (x86_64)
Consult /var/lib/dkms/tuxedo-yt6801/1.0.29tux0/build/make.log for more information.
dkms autoinstall on 7.0.0-31-generic/x86_64 failed for tuxedo-yt6801(10)
Error! One or more modules failed to install during autoinstall.
Refer to previous errors for more information.

  • dkms: autoinstall for kernel 7.0.0-31-generic
    
fail!
    run-parts: /etc/kernel/postinst.d/dkms exited with return code 11
    dpkg: erreur de traitement du paquet linux-image-7.0.0-31-generic (–configure) :
    le sous-processus paquet linux-image-7.0.0-31-generic script post-installation installĂ© a renvoyĂ© un Ă©tat de sortie d’erreur 11
    Aucun rapport « apport » écrit car MaxReports a déjà été atteint
    Des erreurs ont Ă©tĂ© rencontrĂ©es pendant l’exĂ©cution :
    linux-headers-7.0.0-31-generic
    linux-headers-6.17.0-20-generic
    linux-headers-generic-hwe-24.04
    linux-generic-hwe-24.04
    linux-image-7.0.0-31-generic
    E: Sub-process /usr/bin/dpkg returned an error code (1)
4

more information from /var/crash/tuxedo-yt6801.0.crash

ProblemType: Package
DKMSBuildLog:
DKMS make.log for tuxedo-yt6801-1.0.29tux0 for kernel 7.0.0-31-generic (x86_64)
sam. 12 sept. 2026 13:27:29 CEST
make : on entre dans le répertoire « /usr/src/linux-headers-7.0.0-31-generic »
make[1] : on entre dans le répertoire « /var/lib/dkms/tuxedo-yt6801/1.0.29tux0/build »
warning: the compiler differs from the one used to build the kernel
The kernel was built by: x86_64-linux-gnu-gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0
You are using: gcc-13 (Ubuntu 13.3.0-6ubuntu2~24.04.1) 13.3.0
warning: pahole version differs from the one used to build the kernel
The kernel was built with: 125
You are using: 0
CC [M] fuxi-gmac-common.o
CC [M] fuxi-gmac-desc.o
CC [M] fuxi-gmac-ethtool.o
CC [M] fuxi-gmac-hw.o
CC [M] fuxi-gmac-net.o
CC [M] fuxi-gmac-pci.o
CC [M] fuxi-gmac-phy.o
CC [M] fuxi-efuse.o
CC [M] fuxi-gmac-ioctl.o

(
)

fuxi-gmac-net.c:3199:86: warning: suggest braces around empty body in an ‘if’ statement [-Wempty-body]
3199 | DPRINTK(“dev_read rx back to normal and incomplete cnt=%u\n”, cnt_incomplete);
| ^
cc1: some warnings being treated as errors
make[3]: *** [/usr/src/linux-headers-7.0.0-31-generic/scripts/Makefile.build:289 : fuxi-gmac-phy.o] Erreur 1
make[3]: *** Attente des tùches non terminées

make[2]: *** [/usr/src/linux-headers-7.0.0-31-generic/Makefile:2134 : .] Erreur 2
make[1]: *** [/usr/src/linux-headers-7.0.0-31-generic/Makefile:248 : __sub-make] Erreur 2
make[1] : on quitte le répertoire « /var/lib/dkms/tuxedo-yt6801/1.0.29tux0/build »
make: *** [Makefile:248 : __sub-make] Erreur 2
make : on quitte le répertoire « /usr/src/linux-headers-7.0.0-31-generic »
DKMSKernelVersion: 7.0.0-31-generic
Date: Sat Sep 12 13:27:32 2026
DuplicateSignature: dkms:tuxedo-yt6801:1.0.29tux0:fuxi-gmac-phy.c:433:34: error: implicit declaration of function ‘from_timer’; did you>
Package: tuxedo-yt6801 1.0.29tux0
PackageVersion: 1.0.29tux0
SourcePackage: tuxedo-yt6801
Title: tuxedo-yt6801 1.0.29tux0: tuxedo-yt6801 kernel module failed to build

5

The kernel panic happens because your new kernels are not fully installed: linux-image-7.0.0-31-generic aborted during installation, so its initramfs was never built properly.
When GRUB tries to boot the kernel without an initramfs, it panics immediately with “VFS: Unable to mount root fs”.

The root cause is the tuxedo-yt6801 DKMS module. Version 1.0.29 fails to compile against kernel 6.17 and 7.0 headers, causing the kernel post-install hook to exit with code 11.

First, check if you actually have this Motorcomm network card:

lspci -nnk | grep -i net -A3

If you do not have this hardware (or don’t need this Ethernet driver), simply purge the broken DKMS package and finish configuring the kernel:

sudo apt remove --purge tuxedo-yt6801
sudo apt install -f
sudo dpkg --configure -a

Once dpkg finishes configuring linux-image-7.0.0-31-generic and building the initramfs, rebooting into 7.0 will work without panic.

If you actually need this driver, share the compiler errors from

cat /var/lib/dkms/tuxedo-yt6801/1.0.29tux0/build/make.log

6

THANKS !

It seems I do have the motorcomm :

sudo lspci -nnk | grep -i net -A3

pcilib: Error reading /sys/bus/pci/devices/0000:00:08.3/label: Operation not permitted
02:00.0 Ethernet controller [0200]: Motorcomm Microelectronics. YT6801 Gigabit Ethernet Controller [1f0a:6801] (rev 01)
DeviceName: Realtek
Subsystem: Tongfang Hongkong Limited YT6801 Gigabit Ethernet Controller [1d05:7011]
Kernel driver in use: yt6801
Kernel modules: yt6801
03:00.0 SD Host controller [0805]: Genesys Logic, Inc Device [17a0:9767] (rev 03)

04:00.0 Network controller [0280]: Intel Corporation Wi-Fi 6 AX200 [8086:2723] (rev 1a)
Subsystem: Intel Corporation Wi-Fi 6 AX200NGW [8086:0084]
Kernel driver in use: iwlwifi
Kernel modules: iwlwifi

compiler error : I just posted /var/crash/tuxedo-yt6801.0.crash
it’s basically the same as the make.log

7

Do you actively use the wired Ethernet cable on this laptop, or do you connect exclusively via Wi-Fi?

If you only use Wi-Fi, you can simply remove tuxedo-yt6801

sudo apt remove --purge tuxedo-yt6801 && sudo apt install -f

But if you do need the wired Ethernet port, it would be a longer and different story :slight_smile:

8

thank you steelf

Yes, I did weigh that in but I have put too much effort in maximizing network speed on my network to be ready to forget about the wired Ethernet port. I am ready for the longer story :wink:

10

That package does not come from the Ubuntu archive, we can not support it here, the code in it will likely need to get updated to support newer kernels to make it build, you should file an issue where you got that module source from to have its upstream fix it and hold back the kernel update to 7.x for the time being until they can provide you a fixed version when you actually require this module.

1 Like
11

If your Ethernet still gives you problems (even after any excellent help from @steelf and @ogra), consider purchasing a USB/Ethernet adapter as a hardware backup

1 Like
12

If you can get tuxedo-yt6801/1.0.29tux0 removed from your system sudo dkms uninstall tuxedo-yt6801/1.0.29tux0, the 7.0 should work fine with your ethernet device as support for the Motorcomm YT6801 was added

2 Likes
13

@Jeremy31 is right, kernel 7.0 has native in-tree support

Just make sure to completely purge the package with apt rather than dkms uninstall, otherwise the kernel post-install hook will keep trying to build the broken source and fail the initramfs.

If you still need Ethernet on kernel 6.14, TUXEDO already fixed this with version 1.0.31-8 in their Noble repository.

1 Like
14

ogra, tea-for-one, Jeremy31 : thanks all !!!

steelf:

  • do you mean I should do
    sudo apt remove --purge tuxedo-yt6801 && sudo apt install -f
    instead of
    sudo dkms uninstall tuxedo-yt6801/1.0.29tux0
    ?
  • I now have Ethernet on kernel 6.14, I only need it for these fixes, but if Ethernet works on kernel 7.0 and no longer works on kernel 6.14, it’s OK for me - and I’lls still have wifi anyway if I need to go back to this backup kernel. Do I understand this right ?
  • after removal of tuxedo-yt6801, do I still have to do : sudo apt dist-upgrade ?

thank you all for your speedy and comprehensive response
 and for bearing with my poor English and poor knowledge of LInux vocabulary


1 Like
15

I don’t have this card myself, but
 your logs+drivers sources =

  1. Yes: run sudo apt remove --purge tuxedo-yt6801 && sudo dpkg --configure -a. You need apt purge because dkms uninstall leaves broken source files that fail the build.
  2. Yes: your plan is solid. Kernel 7.0 has in-tree support (dwmac-motorcomm), and you still have Wi-Fi on 6.14 as backup.
  3. No: you do not need dist-upgrade.

Just check that the initramfs exists before rebooting:

ls -lh /boot/initrd.img-7.0*

16

Just dovetailing on all of this because I’m familiar with what you’re seeing.

The Tuxedo repository tends to override everything in the Ubuntu repos. I highly suggest doing the following:

sudo nano /etc/apt/preferences.d/tuxedo

and paste the following:

Package: *
Pin: origin deb.tuxedocomputers.com
Pin-Priority: -1

Package: tuxedo-*
Pin: origin deb.tuxedocomputers.com
Pin-Priority: 500

Then save and exit (ctrl-x and y).

That will keep your device drivers and what-not while making everything else in there off-limits.

If you need help with anything inside that repository, seek help from Tuxedo Computers.

1 Like
17

steelf, eeikmeyer : thank you so much!

a dream come true : system works on kernel 7.0 and on first default system start, and the fix was easy with all your help !

JJ

for your interest, but I doubt you need this, my console output (I also did the eeikmeyer’s nano tuxedo stuff
), here it is:

sudo apt remove --purge tuxedo-yt6801 && sudo dpkg --configure -a
[sudo] Mot de passe de useradmin :
Lecture des listes de paquets
 Fait
Construction de l’arbre des dĂ©pendances
 Fait
Lecture des informations d’état
 Fait
Les paquets suivants seront ENLEVÉS :
tuxedo-yt6801*
0 mis à jour, 0 nouvellement installés, 1 à enlever et 1 non mis à jour.
5 partiellement installés ou enlevés.
AprĂšs cette opĂ©ration, 750 ko d’espace disque seront libĂ©rĂ©s.
Souhaitez-vous continuer ? [O/n] O
(Lecture de la base de données
 257705 fichiers et répertoires déjà installés.)
Suppression de tuxedo-yt6801 (1.0.29tux0) 

Module tuxedo-yt6801-1.0.29tux0 for kernel 6.14.0-37-generic (x86_64).
Before uninstall, this module version was ACTIVE on this kernel.

yt6801.ko.zst:

  • Uninstallation

    • Deleting from: /lib/modules/6.14.0-37-generic/updates/dkms/

  • Original module

    • No original module was found for this module on this kernel.
    • Use the dkms install command to reinstall any previous module version.
      depmod

      Deleting module tuxedo-yt6801-1.0.29tux0 completely from the DKMS tree.
      (Re)load module if possible
      Paramétrage de linux-headers-7.0.0-31-generic (7.0.0-31.31~24.04.1) 

      /etc/kernel/header_postinst.d/dkms:

  • dkms: running auto installation service for kernel 7.0.0-31-generic

  • dkms: autoinstall for kernel 7.0.0-31-generic
    
done.
    Paramétrage de linux-image-7.0.0-31-generic (7.0.0-31.31~24.04.1) 

    Paramétrage de linux-headers-6.17.0-20-generic (6.17.0-20.20~24.04.1) 

    /etc/kernel/header_postinst.d/dkms:

  • dkms: running auto installation service for kernel 6.17.0-20-generic

  • dkms: autoinstall for kernel 6.17.0-20-generic
    
done.
    Paramétrage de linux-headers-generic-hwe-24.04 (7.0.0-31.31~24.04.1) 

    Paramétrage de linux-generic-hwe-24.04 (7.0.0-31.31~24.04.1) 

    Traitement des actions diffĂ©rĂ©es (« triggers ») pour linux-image-7.0.0-31-generic (7.0.0-31.31~24.04.1) 

    /etc/kernel/postinst.d/dkms:

  • dkms: running auto installation service for kernel 7.0.0-31-generic

  • dkms: autoinstall for kernel 7.0.0-31-generic
    
done.
    /etc/kernel/postinst.d/initramfs-tools:
    update-initramfs: Generating /boot/initrd.img-7.0.0-31-generic
    /etc/kernel/postinst.d/zz-update-grub:
    Sourcing file `/etc/default/grub’
    Generating grub configuration file 

    Found linux image: /boot/vmlinuz-7.0.0-31-generic
    Found initrd image: /boot/initrd.img-7.0.0-31-generic
    Found linux image: /boot/vmlinuz-6.14.0-37-generic
    Found initrd image: /boot/initrd.img-6.14.0-37-generic
    Found memtest86+ 64bit EFI image: /boot/memtest86+x64.efi
    Warning: os-prober will be executed to detect other bootable partitions.
    Its output will be used to detect bootable binaries on them and create new boot entries.
    Found Windows Boot Manager on /dev/nvme1n1p1@/efi/Microsoft/Boot/bootmgfw.efi
    Adding boot menu entry for UEFI Firmware Settings 

    done

ls -lh /boot/initrd.img-7.0*
-rw-r–r-- 1 root root 78M sept. 13 17:01 /boot/initrd.img-7.0.0-31-generic

3 Likes
18

:partying_face: :confetti_ball: :birthday_cake:
“The sound of a champagne cork popping” :grinning_face:

2 Likes
19

Glad to hear it!

Don’t forget to mark the solution so others can benefit from this. :slight_smile:

3 Likes
20

WAIT! don’t drink that Champagne yet


I trusted the icons in the top right corner: Ethernet was ON, WiFi was ON

But a few moments later, no Ethernet : connect → network activation failure

As for WiFi, I had to re-enter the network key, annoying but ok, it’s a one-off


I do need to fix this, I’ll try to contact https://tuxedocomputers.com/

any other idea welcome !

21

more on this : I rebooted on kernel 6.14 - as expected wired Ethernet was absent.

I rebooted on kernel 7.0 : wired Ethernet is now connected OK. It must have been a transient problem ( after sleep mode ?)

Let’s have those bubbles after all


1 Like