Dear fellow fedora users,
upon updating and rebooting the new kernel refuses to boot or just hangs. How do I troubleshoot this issue? I have to boot 6.5.12-300 so I can use the computer.
Thanks in Advance,
Antonio
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
Dear fellow fedora users,
upon updating and rebooting the new kernel refuses to boot or just hangs. How do I troubleshoot this issue? I have to boot 6.5.12-300 so I can use the computer.
Thanks in Advance,
Antonio
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
--
I ran a command to check for the new updates:
kernel-modules-core-6.6.2-201.fc39.x86_64 kernel-core-6.6.2-201.fc39.x86_64 kernel-modules-6.6.2-201.fc39.x86_64 kernel-modules-extra-6.6.2-201.fc39.x86_64 kernel-headers-6.6.2-201.fc39.x86_64 kernel-devel-6.6.2-201.fc39.x86_64 olivares@fedora:~$ sudo dnf remove kernel-6.6* [sudo] password for olivares: Dependencies resolved. ================================================================================ Package Architecture Version Repository Size ================================================================================ Removing: kernel x86_64 6.6.2-201.fc39 @updates 0
Transaction Summary ================================================================================ Remove 1 Package
Freed space: 0 Is this ok [y/N]: n Operation aborted. olivares@fedora:~$
I see that the size of the kernel is 0. How is that possible?
Best Regards,
Antonio
Sent from ProtonMail, encrypted email based in Switzerland.
Sent with Proton Mail secure email.
On Wednesday, November 29th, 2023 at 9:28 AM, old sixpack13 sixpack13@online.de wrote:
...
olivares@fedora:~$ sudo dnf remove kernel-6.6*
...
you should use sudo dnf remove kernel-core-x.y.z
to get rid of all packages belonging to the kernel kernel-core is a meta package === I also own a RocketLake-S. No problems here
any error message during kernel install ?
Done!
Nov 29 09:02:16 fedora systemd[1]: Startup finished in 15.627s (firmware) + 9.754s (loader) + 1.195s (kernel) + 5.821s (initrd) + 32.093s (userspace) = 1min 4.493s. Nov 29 09:10:43 fedora sudo[3477]: olivares : TTY=pts/3 ; PWD=/home/olivares/Downloads/kerTeX/Documents/Documents/mptmp ; USER=root ; COMMAND=/bin/dnf remove kernel-headers-6.6.2-201.fc39.x86_64 kernel-devel-6.6.2-201.fc39.x86_64 kernel-modules-core-6.6.2-201.fc39.x86_64 kernel-core-6.6.2-201.fc39.x86_64 kernel-modules-6.6.2-201.fc39.x86_64 kernel-6.6.2-201.fc39.x86_64 kernel-modules-extra-6.6.2-201.fc39.x86_64 Nov 29 09:11:26 fedora sudo[3512]: olivares : TTY=pts/3 ; PWD=/home/olivares/Downloads/kerTeX/Documents/Documents/mptmp ; USER=root ; COMMAND=/bin/dnf remove kernel-6.6.2-201.fc39.x86_64 Nov 29 09:12:53 fedora sudo[3560]: olivares : TTY=pts/3 ; PWD=/home/olivares/Downloads/kerTeX/Documents/Documents/mptmp ; USER=root ; COMMAND=/bin/dnf remove kernel-core-6.6.2-201.fc39.x86_64
will run Linux fedora 6.5.12-300.fc39.x86_64 #1 SMP PREEMPT_DYNAMIC Mon Nov 20 22:44:24 UTC 2023 x86_64 GNU/Linux until a 6.6.X fedora kernel actually boots and works on this pc.
Best Regards,
Antonio
On Wed, 29 Nov 2023 14:28:02 +0000 olivares33561 via users users@lists.fedoraproject.org wrote:
Dear fellow fedora users,
upon updating and rebooting the new kernel refuses to boot or just hangs. How do I troubleshoot this issue? I have to boot 6.5.12-300 so I can use the computer.
It is possible that the kernel actually made it far enough in boot that the journal is started, but there is still a problem. In that case look at the boot log in journalctl, journalctl -b 0 or look at any other recent messages if it wasn't boot that caused the issue, journalctl -r
If that doesn't give anything useful, then turn off rhgb and quiet in the kernel command line so that the messages during boot show up. Then you can see where exactly it is failing, and might even see why.
On Wed, 2023-11-29 at 14:28 +0000, olivares33561 via users wrote:
Dear fellow fedora users,
upon updating and rebooting the new kernel refuses to boot or just hangs. How do I troubleshoot this issue? I have to boot 6.5.12-300 so I can use the computer.
Not enough information to go on. What actually happens? Do you see anything onscreen? What happens if you remove the rhgb parameter from the boot line?
poc
On Wednesday, November 29th, 2023 at 8:49 AM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Wed, 2023-11-29 at 14:28 +0000, olivares33561 via users wrote:
Dear fellow fedora users,
upon updating and rebooting the new kernel refuses to boot or just hangs. How do I troubleshoot this issue? I have to boot 6.5.12-300 so I can use the computer.
Not enough information to go on. What actually happens? Do you see anything onscreen? What happens if you remove the rhgb parameter from the boot line?
poc
I restart and boot with rhgb quiet removed I see [ OK ] ... . but at the end there is a line that says [ OK ] Reached target sysinit.target - System Initialization.
and it just stays there indefinitely. I will restart under previous kernel and remove this one. And retest when another comes by.
Best Regards,
Antonio
On Wed, Nov 29, 2023 at 11:01 AM olivares33561 via users < users@lists.fedoraproject.org> wrote:
On Wednesday, November 29th, 2023 at 8:49 AM, Patrick O'Callaghan < pocallaghan@gmail.com> wrote:
On Wed, 2023-11-29 at 14:28 +0000, olivares33561 via users wrote:
Dear fellow fedora users,
upon updating and rebooting the new kernel refuses to boot or just hangs. How do I troubleshoot this issue? I have to boot 6.5.12-300 so I can use the computer.
Not enough information to go on. What actually happens? Do you see anything onscreen? What happens if you remove the rhgb parameter from the boot line?
poc
I restart and boot with rhgb quiet removed I see [ OK ] ... . but at the end there is a line that says [ OK ] Reached target sysinit.target - System Initialization.
and it just stays there indefinitely. I will restart under previous kernel and remove this one. And retest when another comes by.
Have you looked at journalclt? 6.6.2-201.fc39.x86_64 works for many of us, so it could help to identify what is different about your system. The next step after "systemd[1]: Reached target sysinit.target - System Initialization." is attaching storage devices. Some storage devices have "quirks" that kernel usually works around. For example:
kernel: nvme nvme0: missing or invalid SUBNQN field.
I would take a close look at journalctl entries for a successful boot following the "sysiinit.target" line for informative messages. You can also check specific devices in the Linux Hardware Database -- some have comments that suggest kernel command-line options to enable dodgy hardware.
On Wed, Nov 29, 2023 at 10:28 AM olivares33561 via users < users@lists.fedoraproject.org> wrote:
Dear fellow fedora users,
upon updating and rebooting the new kernel refuses to boot or just hangs. How do I troubleshoot this issue? I have to boot 6.5.12-300 so I can use the computer.
Others have already asked for details from journalctl and removing "rhgb quiet". You can also use <Esc> when booting to see the messages.
Are you using non-free packages with akmods? One common issue with command-line updates is rebooting before the non-free package install is complete.
On Wednesday, November 29th, 2023 at 8:56 AM, George N. White III gnwiii@gmail.com wrote:
On Wed, Nov 29, 2023 at 10:28 AM olivares33561 via users users@lists.fedoraproject.org wrote:
Dear fellow fedora users,
upon updating and rebooting the new kernel refuses to boot or just hangs. How do I troubleshoot this issue? I have to boot 6.5.12-300 so I can use the computer.
Others have already asked for details from journalctl and removing "rhgb quiet". You can also use <Esc> when booting to see the messages.
Are you using non-free packages with akmods? One common issue with command-line updates is rebooting before the non-free package install is complete.
--
Your mail to 'users@lists.fedoraproject.org' with the subject
Re: kernel-6.6.2-201.fc39.x86_64 does not boot, process hangs
Is being held until the list moderator can review it for approval.
The message is being held because:
The message is larger than the 60 KB maximum size
Either the message will get posted to the list, or you will receive notification of the moderator's decision.
NOTE: If your message has been held due to size, please consider this a rejection and a friendly request to reduce the size and resend. The list moderators will not approve such messages.
If you are attaching logs or command output, please trim it to a minimal amount (we can ask for more context, if needed).
If you are attaching an image, please crop it to reduce their size.
Also keep in mind that attachments will be encoded by your mail client (usually via base64) and this encoding increases the size by as much as 33%.
output of command was big. No proprietary blobs in kernel. Using intel hdmi output. $ sudo lspci 00:00.0 PCI bridge: Intel Corporation Device 4c53 (rev 01) 00:02.0 VGA compatible controller: Intel Corporation RocketLake-S GT1 [UHD Graphics 730] (rev 04) 00:04.0 Signal processing controller: Intel Corporation Device 4c03 (rev 01) 00:08.0 System peripheral: Intel Corporation Device 4c11 (rev 01) 00:12.0 Signal processing controller: Intel Corporation Comet Lake PCH Thermal Controller 00:14.0 USB controller: Intel Corporation Comet Lake USB 3.1 xHCI Host Controller 00:14.2 RAM memory: Intel Corporation Comet Lake PCH Shared SRAM 00:14.3 Network controller: Intel Corporation Comet Lake PCH CNVi WiFi 00:15.0 Serial bus controller: Intel Corporation Comet Lake PCH Serial IO I2C Controller #0 00:16.0 Communication controller: Intel Corporation Comet Lake HECI Controller 00:17.0 RAID bus controller: Intel Corporation Comet Lake PCH-H RAID 00:1c.0 PCI bridge: Intel Corporation Device 06bc (rev f0) 00:1f.0 ISA bridge: Intel Corporation H470 Chipset LPC/eSPI Controller 00:1f.3 Audio device: Intel Corporation Device f1c8 00:1f.4 SMBus: Intel Corporation Comet Lake PCH SMBus Controller 00:1f.5 Serial bus controller: Intel Corporation Comet Lake PCH SPI Controller 02:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. Device 2600 (rev 21)
Everything just worked before 6.6 kernel.
Best Regards,
Antonio
-
George N. White III -
old sixpack13 -
olivares33561 -
Patrick O'Callaghan -
stan