Hi yes it boots fine on 6.8.0-35
/boot/grub/grub.cfg does show some modifiications, namely some that I added trying to get ROCM to work correctly (and had forgotten about), which are all the same for all the installed kernels
Code:
linux /vmlinuz-6.8.0-35-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash radeon.cik_support=0 radeon.si_support=0 amdgp
u.cik_support=1 amdgpu.si_support=1 $vt_handoff
vs
Code:
linux /vmlinuz-6.11.0-061100-generic root=/dev/mapper/vgubuntu--mate-root ro quiet splash radeon.cik_support=0 radeon.si_support=0 amdgpu.c
ik_support=1 amdgpu.si_support=1 $vt_handoff
Everything disc related, the UUIDs disk options are the same.
#fdisk -l
Code:
Disk /dev/sda: 931.51 GiB, 1000204886016 bytes, 1953525168 sectors
Disk model: Samsung SSD 860
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: 8476D1F5-C544-4EFF-9AB1-D0DCE24B26DE
Device Start End Sectors SizeType
/dev/sda1 2048 1050623 1048576 512M EFI System
/dev/sda2 1050624 2549759 1499136 732M Linux filesystem
/dev/sda3 2549760 1953523711 1950973952 930.3G Linux filesystem
## Logical volumes seem fine (from live 6.8.0-35-generic
) :
Disk /dev/mapper/sda3_crypt: 930.28 GiB, 998881886208 bytes, 1950941184 sectors
Disk /dev/mapper/vgubuntu--mate-root: 929.32 GiB, 997854281728 bytes, 1948934144 sectors
Disk /dev/mapper/vgubuntu--mate-swap_1: 976 MiB, 1023410176 bytes, 1998848 sectors
#parted -l
$ ## has one discrepency:
Code:
Error: /dev/mapper/sda3_crypt: unrecognised disk label
Model: Linux device-mapper (crypt) (dm)
Disk /dev/mapper/sda3_crypt: 999GB
Sector size (logical/physical): 512B/512B
Partition Table: unknown
Disk Flags