Any specific event(s) caused you to suspect hardware?
The f-disk output did not provide any further clues
By the way, to omit all the loops with fdisk -l, try this command
sudo fdisk -l | sed -e '/Disk \/dev\/loop/,+5d'
1 Like
In my opinion, you are doing the only thing we can do in this situation.
-
Use Advance Options for Ubuntu to boot the last working kernel.
-
Update using the terminal and not Software Updater. In that way we do not lose the kernel that actually works when Software Updater brings in a new kernel and leaves us with two kernels that are broken.
-
Wait until update/upgrade brings in a kernel upgrade that does work.
We do not know if Linux kernel 7.0 will solve this. Ubuntu 24.04 LTS will be upgraded to Linux kernel 7.0 in July 2026 when it is backported to the Hardware Enablement Stack.
I, myself, was thinking video driver conflict. But you have Intel Iris Plus graphics and the driver is compiled into the Linux kernel. That cannot be the problem.
I have been in a similar situation. Thankful that I still had a working kernel and waiting patiently until a fix came down.
Regards
1 Like
The suspicion was raised mostly because of the persistent inability to boot none of the 6.17 kernels, plus obviosuly the blinking LED during the failed boots.
Thank you for the tip regarding the better fdisk -l command combo!
Thank you for sharing your opinion and reassuring that I’m doing the right thing! I was just starting to get worried for the safety of a system running on, by now months-old kernel, plus a worry whether I would be able to update to any newer kernel due to hardware limitations of my laptop, both of which might be a result of my lack of both general technical knowledge and understanding of operating systems.
Ok, so I created a live installation of first 24.04.4 and then 26.04, checking with both “Try or install Ubuntu” and the verdict is the following:
24.04.4 presumably running on a 6.17 kernel did not manage to boot at all, after the splash screen it just went blank and did the same as in the previous failed 6.17 kernel boots, which is to heat up, fans turning like crazy but nothing happens for 5 minutes until I turn it off manually.
26.04 on the other hand did boot and when I checked in the terminal with uname -r it did return 7.0.0-14-generic as expected. Bottom line being, as suspected by most, the issue is that my laptop has some problem with the 6.17 kernel.
Would be very interesting to know what is it. Has there been a significant change in how 6.17 works compared to previous kernels? Or could it be that it has some hardware compatibility issues in exceptional cases?
2 Likes
There it is, so it was just an issue with how the other tools identify such partitions. You could have run the originally proposed fdisk -l /dev/disk/by-id/<your nvme>, though, for a more compact output; close enough, though. 
You should file a bug report against the 6.17 kernel:
ubuntu-bug linux-generic-6.17
That program collects relevant system information and attaches it to your report for the maintainers to diagnose the issue.
1 Like
Sorry, I did not get which nvme to use with fdisk -l /dev/disk/by-id/, as any I try using returns a No such file or directory.
I did file a bug report, thanks for the suggestion! 
1 Like
OK, I might have skipped over a few steps there. You can get a listing of all the symbolic links there and where they point to by running this command:
ls -Al /dev/disk/by-id
Looks like this for me:
lrwxrwxrwx 1 root root 9 Mai 9 09:38 ata-CT1000MX500SSD1_2042E4B94DC3 -> ../../sda
lrwxrwxrwx 1 root root 10 Mai 9 09:38 ata-CT1000MX500SSD1_2042E4B94DC3-part1 -> ../../sda1
lrwxrwxrwx 1 root root 10 Mai 9 09:38 dm-name-nvme0n1p3_crypt -> ../../dm-0
lrwxrwxrwx 1 root root 10 Mai 9 09:38 dm-name-sata_crypt -> ../../dm-3
lrwxrwxrwx 1 root root 10 Mai 9 09:38 dm-name-vgsata-data -> ../../dm-4
lrwxrwxrwx 1 root root 10 Mai 9 09:38 dm-name-vgsata-swap_1 -> ../../dm-5
lrwxrwxrwx 1 root root 10 Mai 9 09:38 dm-name-vgubuntu-root -> ../../dm-1
lrwxrwxrwx 1 root root 10 Mai 9 09:38 dm-name-vgubuntu-swap_1 -> ../../dm-2
lrwxrwxrwx 1 root root 10 Mai 9 09:38 dm-uuid-CRYPT-LUKS2-07e7896fbfeb4404a357dfa4230a055c-nvme0n1p3_crypt -> ../../dm-0
lrwxrwxrwx 1 root root 10 Mai 9 09:38 dm-uuid-CRYPT-LUKS2-90fea7769a0648db98a72176f6c23c7f-sata_crypt -> ../../dm-3
lrwxrwxrwx 1 root root 10 Mai 9 09:38 dm-uuid-LVM-PA1uxe43Qo9fV1QbEUS7S7FfTZOYOeUmjgkehdxku0aRZuK8WfRpUV2W2Ge3gA15 -> ../../dm-1
lrwxrwxrwx 1 root root 10 Mai 9 09:38 dm-uuid-LVM-PA1uxe43Qo9fV1QbEUS7S7FfTZOYOeUmsRu9v5GgW46ceHGkNeykOvoiDNfXREAJ -> ../../dm-2
lrwxrwxrwx 1 root root 10 Mai 9 09:38 dm-uuid-LVM-rk1bTMBg487col26LCG2iHti0rI4gtmsGS80EWCOTIdFyLoZW6JyMPY7Wh7waP0O -> ../../dm-5
lrwxrwxrwx 1 root root 10 Mai 9 09:38 dm-uuid-LVM-rk1bTMBg487col26LCG2iHti0rI4gtmsZd2Tdn6wIqXOQrGHmsqcDHUgIOq4dXl3 -> ../../dm-4
lrwxrwxrwx 1 root root 10 Mai 9 09:38 lvm-pv-uuid-oD0PgP-t6Jb-q8rr-fMSd-W1Q4-rPc3-VvkWjg -> ../../dm-3
lrwxrwxrwx 1 root root 10 Mai 9 09:38 lvm-pv-uuid-ydV3jn-jbDd-uJGN-Zax3-p3T9-dtIk-mj8fbV -> ../../dm-0
lrwxrwxrwx 1 root root 13 Mai 9 09:38 nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 Mai 9 09:38 nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Mai 9 09:38 nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Mai 9 09:38 nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594-part3 -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 13 Mai 9 09:38 nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594_1 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 Mai 9 09:38 nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594_1-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Mai 9 09:38 nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594_1-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Mai 9 09:38 nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594_1-part3 -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 13 Mai 9 09:38 nvme-eui.0025388a91b2f992 -> ../../nvme0n1
lrwxrwxrwx 1 root root 15 Mai 9 09:38 nvme-eui.0025388a91b2f992-part1 -> ../../nvme0n1p1
lrwxrwxrwx 1 root root 15 Mai 9 09:38 nvme-eui.0025388a91b2f992-part2 -> ../../nvme0n1p2
lrwxrwxrwx 1 root root 15 Mai 9 09:38 nvme-eui.0025388a91b2f992-part3 -> ../../nvme0n1p3
lrwxrwxrwx 1 root root 9 Mai 9 09:38 scsi-0ATA_CT1000MX500SSD1_2042E4B94DC3 -> ../../sda
lrwxrwxrwx 1 root root 10 Mai 9 09:38 scsi-0ATA_CT1000MX500SSD1_2042E4B94DC3-part1 -> ../../sda1
lrwxrwxrwx 1 root root 9 Mai 9 09:38 scsi-1ATA_CT1000MX500SSD1_2042E4B94DC3 -> ../../sda
lrwxrwxrwx 1 root root 10 Mai 9 09:38 scsi-1ATA_CT1000MX500SSD1_2042E4B94DC3-part1 -> ../../sda1
lrwxrwxrwx 1 root root 9 Mai 9 09:38 scsi-3500a0751e4b94dc3 -> ../../sda
lrwxrwxrwx 1 root root 10 Mai 9 09:38 scsi-3500a0751e4b94dc3-part1 -> ../../sda1
lrwxrwxrwx 1 root root 9 Mai 9 09:38 scsi-SATA_CT1000MX500SSD1_2042E4B94DC3 -> ../../sda
lrwxrwxrwx 1 root root 10 Mai 9 09:38 scsi-SATA_CT1000MX500SSD1_2042E4B94DC3-part1 -> ../../sda1
lrwxrwxrwx 1 root root 9 Mai 9 09:38 wwn-0x500a0751e4b94dc3 -> ../../sda
lrwxrwxrwx 1 root root 10 Mai 9 09:38 wwn-0x500a0751e4b94dc3-part1 -> ../../sda1
And you only need to look at the beginning of the name, which is the interface type, so nvme in our case. That is usually followed by the manufacturer, model number and serial number, which makes the device name globally unique. In this example the command would thus be:
fdisk -l /dev/disk/by-id/nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594
(without -part*, because we want the whole device)
There is also the most important key in the terminal which nobody seems to mention to newbies: Tab can complete your “sentences” (command words, actually) for you, if it knows what you want. If the start of a word is unique, pressing Tab will complete the rest of it for you; if it’s not unique yet, just pressing it twice should show a list of possible words starting with what you already typed. So I never actually type all those commands; I’m hitting Tab all the time. 
In this case my typing would be: fdiTab-l /dev/disk/by-id/nvTabTabTab, then I’d see the suggestion and type STab and bingo:
fdisk -l /dev/disk/by-id/nvme-SAMSUNG_MZVLB512HBJQ-000L7_S4ENNF0MA09594
Well, that’s good news - looks like hardware is probably OK
It’s possible that Grub itself may be preventing the 6.17 kernels from booting on your PC?
I think that it would be a worthwhile exercise to make a USB stick with rEFInd and use the utility to try and boot the 6.17 kernel directly (in effect bypassing grub)
Information here
1 Like
Thanks for the walkthrough, now I got it! Not technically a newbie after 12+ years of using linux but obviously I never did a deep dive in the technicalities. 
This is the output:
sudo fdisk -l /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HBLR-000L2_S4DZNF0M884159
Disk /dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HBLR-000L2_S4DZNF0M884159: 953.87 GiB, 1024209543168 bytes, 2000409264 sectors
Disk model: SAMSUNG MZVLB1T0HBLR-000L2
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes
Disklabel type: gpt
Disk identifier: 8E6561F5-4592-44F2-8DD0-2F99DB555330
Device Start End Sectors Size Type
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HBLR-000L2_S4DZNF0M884159-part1 2048 2203647 2201600 1G EFI System
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HBLR-000L2_S4DZNF0M884159-part2 2203648 6397951 4194304 2G Linux filesystem
/dev/disk/by-id/nvme-SAMSUNG_MZVLB1T0HBLR-000L2_S4DZNF0M884159-part3 6397952 2000406527 1994008576 950.8G Linux filesystem
I completely forgot about the tab function in terminal, more precisely that it can complete a unique string, which is an important fact!
1 Like
Will do, I’ll report on the results.
Oh, one more rather important thing: you should consider installing the plain GA kernel (6.8), because 6.14 is EOL and will not get security upgrades anymore.
sudo apt install linux-generic
Then reboot, press Esc to get the GRUB bootloader menu, select advanced and then the menu entry containing the 6.8 kernel. If that works, you should stick to that kernel for the time being.
I am not quite sure if that selection will stick across reboots, though, so you should also check which kernel gets booted on subsequent boots with the uname -r command.
If that setting is not saved by default, this should ensure that it does:
sudo mkdir -p /etc/default/grub.d
sudo tee /etc/default/grub.d/zz-save_default.cfg >/dev/null <<EOF
GRUB_DEFAULT="saved"
GRUB_SAVEDEFAULT=true
EOF
sudo update-grub
You can copy the whole code block with the clipboard icon in the top right and CtrlShiftV and Enter in a terminal.
It creates a config snippet (drop-in) for the GRUB2 bootloader, which instructs it to save the last boot menu choice as the default.
Alternatively you could just purge the HWE kernel:
sudo apt purge linux-generic-hwe-2404
sudo apt autoremove
But only do that after confirming that you can boot with the 6.8 kernel.
1 Like
I did exactly that, installed kernel 6.8, which seems to work perfectly.
Is the following way of getting to load 6.8 kernel on boot by default equally legitimate?
By editing GRUB_DEFAULT in the grub config file in this way:
GRUB_DEFAULT=‘Advanced options for Ubuntu>Ubuntu, with Linux 6.8.0-117-generic’
That’s at least how I was keeping the 6.14 kernel to boot by default so far.
1 Like
Great! 
But that requires you to change that value on every kernel upgrade. I think the default saving option is the more convenient one; I’ve updated my last post on how to enable it, because the most important part, GRUB_SAVEDEFAULT=true, was missing.
2 Likes
This topic was automatically closed after 30 days. New replies are no longer allowed.