Description of the issue (screenshots if relevant):
I can’t boot with kernel 6.14, it gets stuck almost instantly, but I can reboot by hitting ctrl alt del, 6.13 works fine
To get evidence for why kernel-desktop-6.14.0-3 is not booting: Boot in to this kernel, then when you boot in to kernel-desktop-6.13.7-1 open Konsole or other terminal and run:
journalctl -b -1 > journal-no-boot.txt
The -b -1 options show the journal of the previous boot attempt. Post the journal-no-boot.txt file here. The journal log will tell us any kernel errors produced.
You could also try booting in to regular Plasma6 desktop instead of using this, maybe some module is missing form kernel 6.14.0. If so would be good to find out now.
Edit: To my knowledge it is not common for these to be installed unless you need them I would remove them.
First thing I see is this 6.14.0-desktop-0.rc7.2omv2590, If I remember correctly that one does not work plus it is a kernel-desktop-rc (release candidate) and should not be on your system. I think that kernel got pulled in somehow by hfs and hfs is something ancient and also should be removed unless you know you need it for something. sudo dnf rm kernel-desktop-rc hfs should do it.
kernel-desktop-6.14.0-3 is the one we want to work with for problem solving, at least until we get a newer kernel version.
Mar 31 14:22:06 openmandriva64 kernel: Realtek Internal NBASE-T PHY r8169-0-700:00: attached PHY driver (mii_bus:phy_addr=r8169-0-700:00, irq=MAC)
Mar 31 14:22:06 openmandriva64 kernel: r8169 0000:07:00.0 eno1: Link is Down
Mar 31 14:22:06 openmandriva64 systemd-coredump[1070]: Process 1036 (adb) of user 0 dumped core.
Stack trace of thread 1036:
#0 0x00007f83b5e9fe8c __pthread_kill_implementation (libc.so.6 + 0x94e8c)
#1 0x00007f83b5e4b0e2 raise (libc.so.6 + 0x400e2)
#2 0x00007f83b5e33ef5 abort (libc.so.6 + 0x28ef5)
#3 0x000056136441dee5 _ZN7android4base14DefaultAborterEPKc (/usr/bin/adb + 0x14cee5)
#4 0x000056136441e157 _ZN7android4base10LogMessageD2Ev (/usr/bin/adb + 0x14d157)
#5 0x00005613643b563f _Z24adb_get_android_dir_pathB5cxx11v (/usr/bin/adb + 0xe463f)
#6 0x00005613643cd514 _ZL17get_user_key_pathB5cxx11v (/usr/bin/adb + 0xfc514)
#7 0x00005613643d1e2d _Z15adb_server_mainiRKNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPKci (/usr/bin/adb + 0x100e2d)
#8 0x00005613643da0a4 _Z15adb_commandlineiPPKc (/usr/bin/adb + 0x1090a4)
#9 0x00007f83b5e35b28 __libc_start_call_main (libc.so.6 + 0x2ab28)
#10 0x00007f83b5e35be5 __libc_start_main (libc.so.6 + 0x2abe5)
#11 0x0000561364382ee1 _start (/usr/bin/adb + 0xb1ee1)
Stack trace of thread 1065:
#0 0x00007f83b5f1bc49 __clone3 (libc.so.6 + 0x110c49)
ELF object binary architecture: AMD x86-64
Mar 31 14:22:06 openmandriva64 systemd[1]: systemd-coredump@0-1069-0.service: Deactivated successfully.
Mar 31 14:22:06 openmandriva64 systemd[1]: systemd-coredump@0-1069-0.service: Consumed 86ms CPU time, 65.8M memory peak.
Mar 31 14:22:06 openmandriva64 adb[997]: ADB server didn't ACK
That is definitely something. What the heck is adb doing there? Isn’t that android debug bridge? On a pc?
I suggest we try this again, being sure to use kernel-desktop-6.14.0-3 using this command:
journalctl -b -1 > journal-no-boot-2.txt
and we want to get all the data. If you need to do files for 2nd file rename it journal-no-boot-3.txt so are files have different names and we can keep thing straight.
Note: I believe devs removed hfs from the system package list for OMLx systems recently because it is obsolete.
Thanks for the suggestions, I’ll try them when I get home, I installed adb tools so I can flash bootloaders on my phone, I don’t know how an RC kernel got on my system, I did the OS install from one of the spins
Edit: So I did have a RC kernel installed, it was just called kernel-rc-desktop, not kernel-desktop-rc, I also reinstalled 6.14, but it still gets stuck on boot, it doesn’t even make it to the loading ramdisk text, but now when I run journalctl -b -1 > journal-no-boot.txt it prints the boot log from kernel 6.13.7 despite the previous boot attempt being from 6.14
Everyone hold tight. @bero is swapping us back to 6.13.9 and it is compiling now. It will probably be a couple hours and a dsyc will get everyone back to normal.
So for now boot using kernel-desktop-6.13.7 and remove any kernel 6.14 versions you have currently.
If anyone wants to install something right now you can download kernel-desktop-6.13.8 from here and install that. Don’t forget kernel-headers-6.13.8 or kernel-desktop-devel–6.13.8 if you happen to use one of those.
Edit: I just installed 6.13.8 and removed 6.14 on my hardware Cooker and ROME systems. Another problem we had seen with 6.14 was not Virtual Terminals or VT’s and that is a blocker. (Ctrl>Alt>F3, ect. gotta have it)
So I received the 6.13.9 update and it doesn’t boot either, it just displays the loading kernel text for about 30 seconds before rebooting, it doesn’t even make it to the loading initial ramdisk text, and I can’t provide a log either because journalctl -b -1 > journal-no-boot.txt shows the log from 6.13.7, its like systemd has no recollection of ever booting 6.13.9 or 6.14
In my case 6.14-rc come with update right after fresh install.
@ben79, I would like to suggest to place -rc kernels in “testing” repo, because they are intended for testing, and to not to pollute the main repository.
And 6.14 work flawlessly for me, and I was very surprised when it dissapear from repo, because it important for me as Intel ARC GPU owner.
