Hi - I got a Kernel issue. My computer (HP Dragonfly Folio Gen 3) is not booting anymore with newer Kernel versions. The last Kernel, that did allow me to boot is 6.11.10. With 6.12.4 and 6.11.11 the device is stuck in the booting process. Is there any way to make the newer Kernels work with my device? Am not sure, how to go on here.
Where is the boot stuck on the newer kernels?
Have you tried editing the grun boot for the new kernel to remove the ârhgb quietâ options so you can see where it was stuck?
Let us know what you find.
Sorry - but how can I remove the ârhgb quietâ option?
You havenât mentioned if booting gets you to the grub2 menu that has a list of available kernels. If you get the menu you can use the editor:
Quoting Grub2 Manual â Menu entry editor
14.3 Editing a menu entry
The menu entry editor looks much like the main menu interface, but the lines in the menu are individual commands in the selected entry instead of entry
names.If an ESC is pressed in the editor, it aborts all the changes made to the configuration entry and returns to the main menu interface.
Each line in the menu entry can be edited freely, and you can add new lines by pressing RET at the end of a line. To boot the edited entry, press Ctrl-x.
Although GRUB unfortunately does not support undo, you can do almost the same thing by just returning to the main menu using ESC.
Yes - I do get to the grub2 menu, where I can choose from the list of available Kernels after shutting down the computer, when its stuck. Still - I have to admit, that I never interacted with grub and am also not capable to enter any editing menu there. I would be further not aware, what I would have to do in the menu interface.
Select the entry you want to edit and type e.
If you look at the bottom of the screen when grub helpfully puts instruction about what you can do.
Now you can use the cursor keys to move within the lines of the grub boot commands.
Move to the line that start linux. Move to text rhgb quiet and use the Del key or <- key to delete it in the normally text editing way.
Once that is done type Ctrl-X to boot with your changes.
Again grub helpfully puts instruction on the bottom of the screen.
Edits you make are not permanent, so do not worry if you make a mistake with the edit. Just reboot and try again.
The command sudo grubby --remove-args='rhgb quiet' --update-kernel=$(uname -r) will remove those args for the current kernel. To restore the options use sudo grubby --args='rhgb quiet' --update-kernel=$(uname -r)
Of course rebooting after making the change will show the results.
That worked, but it ends in a black screen - so I unfortunatelly cannot give you any answers here
Nope - it created an error response, that the old Kernel I use is not valuable
A black screen sounds like an issue you graphics drivers.
When you get to the black screen type Ctrl-Alt-F3.
You should get to a login prompt and be able to login.
If that works we can get you run commands to find out what is wrong.
1 Like
You also might add the option nomodeset at the same time as you remove the rhgb quiet.
Another thing that has helped many with the 6.11.11 kernel is to edit the /etc/environment file and add another variable there. (the default file is empty)
sudo nano /etc/environment to open it then add a single line that reads
GSK_RENDERER=ngl which has worked for many. With older systems it may be necessary to replace ânglâ with âglâ
You mentioned âolder kernelâ. What kernel are you using at present?
Adding the wording under etc/environment did not help - at the moment only kernel 6.11.10 works on my machineâŚ
Also inserting nomodeset brought no visible result
Unfortunatelly not reaction hereâŚ
Iâm wondering if the keyboard isnât working properly when you get to the grub menu. You seem to be able to use arrow keys to select the boot entry, but then e doesnât get you the grub editor. If you arenât using a US English keyboard there could be a (new!) bug not properly translating keystrokes.
If your keyboard has CapsLock and Numlock lights, do they respond when other keys donât generate responses?
It would be helpful to have the output from running inxi -Fzxx in a terminal (post the output as pre-formatted text using the </> button from the top line of the text entry panel).
About the black screen issue after grub menu, I faced the same problem after a kernel update. I realized itâs not related to the boot process; the kernel works fine, but the NVIDIA driver was causing issues with multiple monitor outputs. I tried using only a DP connection, and it works now. You could try using Nouveau or simplify your setup to avoid similar issues.
Pressing e was taking me to the grub menue - I was able to edit the recomended line there. But its true - I am using a german keyboard layout.
System:
Kernel: 6.11.10-300.fc41.x86_64 arch: x86_64 bits: 64 compiler: gcc
v: 2.43.1-2.fc41
Desktop: GNOME v: 47.2 tk: GTK v: 3.24.43 wm: gnome-shell dm: GDM
Distro: Fedora Linux 41 (Workstation Edition)
Machine:
Type: Laptop System: HP product: HP Dragonfly Folio 13.5 inch G3 2-in-1
Notebook PC v: SBKPF serial: <superuser required> Chassis: type: 10
serial: <superuser required>
Mobo: HP model: 8A05 v: KBC Version 16.6E.00 serial: <superuser required>
part-nu: 6W4N8AA#ABA UEFI: HP v: U93 Ver. 01.12.01 date: 07/30/2024
Battery:
ID-1: BAT0 charge: 45.7 Wh (94.8%) condition: 48.2/53.2 Wh (90.6%)
volts: 8.1 min: 7.7 model: Hewlett-Packard Primary serial: <filter>
status: discharging
CPU:
Info: 10-core (2-mt/8-st) model: 12th Gen Intel Core i7-1265U bits: 64
type: MST AMCP arch: Alder Lake rev: 4 cache: L1: 928 KiB L2: 6.5 MiB
L3: 12 MiB
Speed (MHz): avg: 657 min/max: 400/4800:3600 cores: 1: 657 2: 657 3: 657
4: 657 5: 657 6: 657 7: 657 8: 657 9: 657 10: 657 11: 657 12: 657
bogomips: 64512
Flags: avx avx2 ht lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx
Graphics:
Device-1: Intel Alder Lake-UP3 GT2 [Iris Xe Graphics]
vendor: Hewlett-Packard driver: i915 v: kernel arch: Gen-12.2 ports:
active: eDP-1 empty: DP-1, DP-2, DP-3, DP-4, HDMI-A-1 bus-ID: 00:02.0
chip-ID: 8086:46a8
Display: wayland server: X.org v: 1.21.1.14 with: Xwayland v: 24.1.4
compositor: gnome-shell driver: gpu: i915 display-ID: 0
Monitor-1: eDP-1 model: Samsung 0x4160 res: 3000x2000 dpi: 267
diag: 343mm (13.5")
API: OpenGL v: 4.6 vendor: intel mesa v: 24.2.8 glx-v: 1.4 es-v: 3.2
direct-render: yes renderer: Mesa Intel Graphics (ADL GT2)
device-ID: 8086:46a8 display-ID: :0.0
API: EGL Message: EGL data requires eglinfo. Check --recommends.
Audio:
Device-1: Intel Alder Lake Imaging Signal Processor vendor: Hewlett-Packard
driver: intel-ipu6 bus-ID: 00:05.0 chip-ID: 8086:465d
Device-2: Intel Alder Lake PCH-P High Definition Audio
vendor: Hewlett-Packard driver: sof-audio-pci-intel-tgl bus-ID: 00:1f.3
chip-ID: 8086:51c8
API: ALSA v: k6.11.10-300.fc41.x86_64 status: kernel-api
Server-1: JACK v: 1.9.22 status: off
Server-2: PipeWire v: 1.2.7 status: active with: 1: pipewire-pulse
status: active 2: wireplumber status: active 3: pipewire-alsa type: plugin
Network:
Device-1: Intel Alder Lake-P PCH CNVi WiFi driver: iwlwifi v: kernel
bus-ID: 00:14.3 chip-ID: 8086:51f0
IF: wlp0s20f3 state: up mac: <filter>
IF-ID-1: wwan0 state: down mac: N/A
Bluetooth:
Device-1: Intel AX211 Bluetooth driver: btusb v: 0.8 type: USB rev: 2.0
speed: 12 Mb/s lanes: 1 bus-ID: 3-10:2 chip-ID: 8087:0033
Report: btmgmt ID: hci0 rfk-id: 1 state: up address: <filter> bt-v: 5.3
lmp-v: 12
Drives:
Local Storage: total: 953.87 GiB used: 129.92 GiB (13.6%)
ID-1: /dev/nvme0n1 vendor: Micron model: MTFDKBA1T0TFH-1BC1AABHA
size: 953.87 GiB speed: 63.2 Gb/s lanes: 4 serial: <filter> temp: 39.9 C
Partition:
ID-1: / size: 952.28 GiB used: 129.56 GiB (13.6%) fs: btrfs
dev: /dev/nvme0n1p3
ID-2: /boot size: 973.4 MiB used: 343 MiB (35.2%) fs: ext4
dev: /dev/nvme0n1p2
ID-3: /boot/efi size: 598.8 MiB used: 19.3 MiB (3.2%) fs: vfat
dev: /dev/nvme0n1p1
ID-4: /home size: 952.28 GiB used: 129.56 GiB (13.6%) fs: btrfs
dev: /dev/nvme0n1p3
Swap:
ID-1: swap-1 type: zram size: 8 GiB used: 0 KiB (0.0%) priority: 100
dev: /dev/zram0
Sensors:
System Temperatures: cpu: 26.0 C mobo: N/A
Fan Speeds (rpm): N/A
Info:
Memory: total: 32 GiB note: est. available: 30.92 GiB used: 3.21 GiB (10.4%)
Processes: 440 Power: uptime: 0m wakeups: 0 Init: systemd v: 256
target: graphical (5) default: graphical
Packages: pm: rpm pkgs: N/A note: see --rpm pm: flatpak pkgs: 54
Compilers: N/A Shell: Bash v: 5.2.32 running-in: gnome-terminal inxi: 3.3.36
heiko@folio:~$
Dont know, if this applies to me, since my device has no nvidia chip inside
Okay, sorry, I misunderstood. I recently faced a similar issue, but your situation might go beyond just a driver or monitor issue. Could you share your grub menu boot options, especially the linuxefi line you access with the âeâ key, along with the updated kernel version? Maybe it could help figure things out. Good luck with that!
There are other reports with issues for Xe graphics. There is a very new xe module, but it is âwork in progressâ. You should be able to get details using journalctl in a terminal to view entries for a boot that failed. It may take some work to become familiar with man journalctl options, as it collects massive amounts of detail.
You will need to identify the number of a boot that failed. Easiest way is to attempt booting 6.12.4 (or later), then boot a working kernel and use the -b -1 option. I would start with journalctl --no-hostame -b -<N> (<N>=1 for previous boot) and scroll around to get familiar with the data. You can use /<search_string>, but xe is an unfortunate name so you may want to try search strings like<space>xe. If you can identify a suitable search string, use journalctl --no-hostname -b -<N> -g <search_string> |cat to get text with wrapped lines suitable for posting as pre-formatted text.
If you are pressed for time, you may prefer to wait for updates to vendor firmware or new kernels that fix your issue, but in the long run you will find that learning to use journalctl is very helpful â you may want to play with it in spare time.
I have the same problem after the kernel update today.
I can not boot the 6.12.x kernels, I always get an error that the imageramfs files are missing.
As you can also see here:
insgesamt 164426
-rw-râr-- 1 root root 277977 5. Dez 01:00 config-6.11.11-300.fc41.x86_64
-rw-râr-- 1 root root 279698 9. Dez 01:00 config-6.12.4-200.fc41.x86_64
-rw-râr-- 1 root root 279619 15. Dez 01:00 config-6.12.5-200.fc41.x86_64
drwx------. 4 root root 1024 19. Jul 02:00 efi
drwxr-xr-x. 2 root root 5120 10. Nov 11:47 extlinux
drwx------. 6 root root 1024 21. Dez 18:11 grub2
-rw------- 1 root root 37784483 14. Sep 2013 initramfs-0-rescue-69d27b356a94476da859461d3a3bc6fd.img
-rw------- 1 root root 37862247 14. Dez 14:50 initramfs-6.11.11-300.fc41.x86_64.img
-rw-rârâ. 1 root root 561014 26. Nov 2016 initrd-plymouth.img
drwxr-xr-x 3 root root 1024 22. Nov 2018 loader
drwx------. 2 root root 12288 19. Jan 2013 lost+found
-rw-râr-- 1 root root 155992 12. Nov 01:00 memtest86+x64.bin
-rw-râr-- 1 root root 182804 14. Dez 14:50 symvers-6.11.11-300.fc41.x86_64.xz
-rw-râr-- 1 root root 9975775 5. Dez 01:00 System.map-6.11.11-300.fc41.x86_64
-rw-râr-- 1 root root 10931886 9. Dez 01:00 System.map-6.12.4-200.fc41.x86_64
-rw-râr-- 1 root root 10934115 15. Dez 01:00 System.map-6.12.5-200.fc41.x86_64
-rw-râr-- 1 root root 155302 3. Mär 2024 tboot.gz
-rw-râr-- 1 root root 14742 3. Mär 2024 tboot-syms
-rwxr-xr-x 1 root root 9323208 10. Nov 2019 vmlinuz-0-rescue-69d27b356a94476da859461d3a3bc6fd
-rwxr-xr-x 1 root root 16312680 5. Dez 01:00 vmlinuz-6.11.11-300.fc41.x86_64
-rwxr-xr-x 1 root root 16652648 9. Dez 01:00 vmlinuz-6.12.4-200.fc41.x86_64
-rwxr-xr-x 1 root root 16652648 15. Dez 01:00 vmlinuz-6.12.5-200.fc41.x86_64
Looks like a problem with the grub update script.
Best regards Uwe