Display resolution after install

[johngx]

or you have multiple Kubuntu installs sharing the same EFI partition and one has overwritten the other

That may be so, I have looked at EFI partitions but cannot see anything in them. How would I verify what you suggest?

[johngx]

You don't have boot options in your BIOS? This is what i am referring to.

What do they look like? What would I do with them?

[claydoh]

I really am unsure

1. Maybe we can see your drives layout via lsblk (from 24.10, but can be from 24.04 or anything)
2. What your BIOS sees for boot entries via efibootmgr (from any Linux install )
3. Your 24.10's fstab contents, if you aren't working from 24.10

[johngx]

Here with:

$ blkid
/dev/sdb5: UUID="770ad7c8-b3f3-4d1a-ae86-724981bb8f47" TYPE="swap" PARTUUID="f98d8853-cc5e-4e8d-8cb2-340550ff8351"
/dev/sda7: UUID="fb20f2da-3fe2-4dfb-b684-780c1b871ccd" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="7b4c893f-1a59-4880-a4c9-1496f1c0ecc2"
/dev/nvme0n1p1: UUID="9990-7D06" BLOCK_SIZE="512" TYPE="vfat" PARTLABEL="Microsoft basic data" PARTUUID="ab6ac4bc-aa35-45eb-a0d4-46aaae4bd351"
/dev/nvme0n1p2: UUID="e53c07de-dcce-44ea-a369-13d81ce98e3b" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="fca36d1f-3b7e-4f9c-af6d-cb3b92a73a7e"
/dev/nvme0n1p3: LABEL="Kubuntu" UUID="9d381534-90b9-4a59-b226-21780decda48" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="062265cd-fe30-4161-bd32-8563912abbf6"
/dev/nvme0n1p4: UUID="119ffbb1-9d77-446e-b0f6-6ce49b752c24" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="Linux filesystem" PARTUUID="f52be82a-87ae-47e2-9c7b-b0112cc6dd57"
/dev/sda1: UUID="6CC6-EFCC" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="ffbb796f-9883-4d1a-8fdb-588a2d4ef0fd"
/dev/sda2: LABEL="Mint 17" UUID="ceaea2d2-aec6-47c6-969c-afc4eef20601" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="45d5f0ec-b0a2-4b9f-98cd-5a1bfccc192d"
/dev/sda3: LABEL="Mint 18" UUID="eea1ce64-e8a3-46eb-a902-78f41479508c" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="38329136-ecd9-4d8e-989a-d8094502f0f7"
/dev/sda4: LABEL="Kubuntu-24.10a" UUID="46fd6a8f-47b2-48d2-8767-b014e41be2d7" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="12043c9f-9ab0-44e2-8c62-c7677e64668f"
/dev/sda5: UUID="dfd7b7ab-57db-482f-b657-89de573d50be" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="4e4e3845-34e2-4538-a812-dc2e5c3f5be0"
/dev/sda6: LABEL="/opt" UUID="e641de16-8df1-40b8-a800-1a5070252811" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="35b22652-3002-4a08-af6c-f25e4f896067"
/dev/sdb1: UUID="075edf57-47e5-482f-aefd-9fa62b2fae47" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="d9c9543f-146c-435c-8d40-a8336e71c6ae"
/dev/sdb2: UUID="44103d1a-b093-475f-a72b-2101d1ea6525" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="KUBUNTU" PARTUUID="eed23315-a89d-4dab-a884-4d682117b38a"
/dev/sdb3: UUID="774B-F022" BLOCK_SIZE="512" TYPE="vfat" PARTUUID="de3cd42d-d633-42c4-b39e-6d3bcd2efd0a"
/dev/sdb4: UUID="c6af4e27-b56e-43f8-b19b-1cc65f618d1c" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="c71f2d60-315c-4dc7-85db-a347662adccf"
/dev/sdc1: UUID="e676fc59-0265-45c2-b992-68bd3730367c" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="5ab18820-8a41-43d5-a4ef-27e2be83cd89"
/dev/sdc2: UUID="585f9b5b-0739-4447-a2eb-c361e77762d3" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="657c7c6c-7e50-4e35-8653-de5de763f2ee"
/dev/sdc3: UUID="57d75c78-d55a-4b94-9a81-dd409d8e7718" TYPE="swap" PARTUUID="a3015e1a-51ee-4d66-af08-e81960abcd7a"
/dev/sdc4: LABEL="DATA" UUID="29fc84ba-0f62-4bad-9fc3-8e6d08bf99c3" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b1caf36d-5d40-45d8-93f7-cee35108333e"
/dev/sdc5: LABEL="DATA-misc" UUID="18becb8d-9f52-43b8-bbf2-8f200de68640" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="a3de04cf-3c5e-4677-bf94-664659199d4b"
/dev/sdc6: UUID="2621f64a-3517-4186-82c1-bcf5ae670101" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="25701504-e0a1-4b4b-895e-1782925a4613"
/dev/loop1: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop8: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop6: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop4: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop2: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop0: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop7: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop5: BLOCK_SIZE="131072" TYPE="squashfs"
/dev/loop3: BLOCK_SIZE="131072" TYPE="squashfs"

$ efibootmgr
BootCurrent: 0028
Timeout: 1 seconds
BootOrder: 0028,0029,0032,0033,002E,002F,0031,0034
Boot0028* Ubuntu HD(1,GPT,ffbb796f-9883-4d1a-8fdb-588a2d4ef0fd,0x4b000,0x7d000)/File(\EFI\ubuntu\shimx64.efi)
Boot0029* UEFI OS HD(1,GPT,ffbb796f-9883-4d1a-8fdb-588a2d4ef0fd,0x4b000,0x7d000)/File(\EFI\BOOT\BOOTX64.EFI)
Boot002E* HL-DT-ST DVDRAM GH22LS50 BBS(CDROM,,0x0)AMBO
Boot002F* ADATA SU630 BBS(HD,,0x0)AMBO
Boot0031* ST2000DM001-1CH164 BBS(HD,,0x0)AMBO
Boot0032* ubuntu HD(1,GPT,ffbb796f-9883-4d1a-8fdb-588a2d4ef0fd,0x4b000,0x7d000)/File(\EFI\Ubuntu\grubx64.efi)
Boot0033* UEFI: ADATA SP900 PciRoot(0x0)/Pci(0x1f,0x2)/Sata(1,65535,0)/HD(3,GPT,de3cd42d-d633-42c4-b39e-6d3bcd2efd0a,0x44000,0x1dc000)AMBO
Boot0034* ADATA SP900 BBS(HD,,0x0)AMBO

[claydoh]

oops, I really wanted lsblk not blkid as it gives mount points for the booted OS as well

sorry

[johngx]

How's this:

$ lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
loop0 7:0 0 4K 1 loop /snap/bare/5
loop1 7:1 0 55.4M 1 loop /snap/core18/2846
loop2 7:2 0 73.9M 1 loop /snap/core22/1663
loop3 7:3 0 73.9M 1 loop /snap/core22/1722
loop4 7:4 0 505.1M 1 loop /snap/gnome-42-2204/176
loop5 7:5 0 91.7M 1 loop /snap/gtk-common-themes/1535
loop6 7:6 0 44.3M 1 loop /snap/snapd/23258
loop7 7:7 0 44.4M 1 loop /snap/snapd/23545
loop8 7:8 0 93.2M 1 loop /snap/youtube-dl/4806
sda 8:0 0 223.6G 0 disk
├─sda1 8:1 0 250M 0 part /boot/efi
├─sda2 8:2 0 32.3G 0 part
├─sda3 8:3 0 36.1G 0 part
├─sda4 8:4 0 31.1G 0 part
├─sda5 8:5 0 57.9G 0 part
├─sda6 8:6 0 14.8G 0 part /home/sda6
└─sda7 8:7 0 51G 0 part /
sdb 8:16 0 119.2G 0 disk
├─sdb1 8:17 0 18.6G 0 part
├─sdb2 8:18 0 45.4G 0 part
├─sdb3 8:19 0 952M 0 part
├─sdb4 8:20 0 28.7G 0 part
└─sdb5 8:21 0 25.2G 0 part [SWAP]
sdc 8:32 0 1.8T 0 disk
├─sdc1 8:33 0 29.5G 0 part
├─sdc2 8:34 0 29.3G 0 part
├─sdc3 8:35 0 3.6G 0 part
├─sdc4 8:36 0 677.3G 0 part
├─sdc5 8:37 0 1.1T 0 part
└─sdc6 8:38 0 305M 0 part
sr0 11:0 1 1024M 0 rom
nvme0n1 259:0 0 931.5G 0 disk
├─nvme0n1p1 259:1 0 250M 0 part
├─nvme0n1p2 259:2 0 97.7G 0 part
├─nvme0n1p3 259:3 0 58.6G 0 part
└─nvme0n1p4 259:4 0 496G 0 part /home/nvme0n1p4

[claydoh]

So is this your 24,10 install, on /dev/sda7, then? This is what you are booted to

sda1 8:1 0 250M 0 part /boot/efi

and

sda7 8:7 0 51G 0 part /

What are on the other partitions?

I think I am completely lost. We are gonna need a map, a compass and maybe a GPS
Or an expert.

[johngx]

According to GParted the drive order is nvme01, sda, sdb,sdc. My normal OS is Kubuntu 24.04 on sda7. Other OS are Mint 17 on sda2, Mint 18 on sda3, and Kubuntu 24.10 on sda4 (small partition used to validate i915 driver). It is the Kubuntu 24.10 on nvme0n1p3 that won't boot. All other partitions are data.

[jlittle]

I understand the "hd0,gpt4" system, it just does not appear to have a nvme version...

FWIW, this system's NVMe appears as (hd3) in grub, after the SATA connected drives in hd0, hd1, and hd2.

[johngx]

So I set Grub Customizer to:

insmod part_gpt
insmod ext2
set root='hd3,gpt3'
linux /boot/vmlinuz-6.11.0-8-generic root=9d381534-90b9-4a59-b226-21780decda48 ro quiet splash $vt_handoff
initrd /boot/initrd.img-6.11.0-8-generic

On reboot, grub reported hd3, gpt3 not found

[claydoh]

It is the Kubuntu 24.10 on nvme0n1p3 that won't boot.

I thought it booted, but had bad resolution?

so, which EFI partition is it using? Look at its /etc/fstab file, which you should be able to access from any other Linux install.


And note that when editing something with grub customizer (or manually) you are only editing the grub menu the the OS that is booted.

This is why I keep repeatedly suggesting to try using a different boot option from your bios. Maybe the grub for 24.10 is perfectly fine, it is just the grub you are using and editing is borked,

Without knowing what the 24.10 install is using, or if it boots (or not) via the BIOS selection we can't really say what the next steps will be.

But some scenarios (and f*** forget grub-customizer for the moment):


if the 24.10 was installed using sda1 as the EFI, that is still OK, we can re-install its grub to nvme partition if necessary. This is not difficult, and the process is well documented, but does take a few steps. It can even be done from your currently running OS instead of a live USB session. This will keep the two *buntu installs from re-writing/replacing things with every kernel update, which I suspect is what has happened (they are unfortunately using the exact same boot loader directory layouts and files and have no idea that there are two separate OS installs) This sort of situation can happen with your Mint installs as well, if they too share an EFI partition.

If 24.10 IS using the more appropriate EFI partition, on the nvme drive, then maybe it is the specific custom Grub menu entry for it that is borked.. Try booting the 24.10 install using your computer's boot hotkey. My HP uses <esc> for a full menu of options, and <f9> for a one-time boot selection, for example. Or you can change the order in your BIOS settings. If that boots fine, you can look at its grub file (/boot/grub/grub.cfg) and compare its entries to your edits in grub customizer-- when booted back to your 24.04, which I assume is the grub you are editing.


Or just keep the 24.10 as the boot option if its menu boots all your other OS installs.

[johngx]

Kubuntu 24.10 on nvme0n1p3 does not boot naturally, with a bit of luck hitting the keyboard, it sometimes boots in low resolution mode. Kubuntu 24.10 on sda4 boots normally in hi resolution

The Kubuntu 24.10 on nvme0n1p3 fstab contains only

# <file system> <mount point> <type> <options> <dump> <pass>
UUID=9d381534-90b9-4a59-b226-21780decda48 / ext4 defaults 0 1
/swapfile swap swap defaults 0 0
tmpfs /tmp tmpfs defaults,noatime,mode=1777 0 0

UUID=9d381534-90b9-4a59-b226-21780decda48 being /dev/nvme0n1p3

To be blunt, I know not if 24.10 is installed using sda1 as the EFI

If I reboot and hold the F12 on the keyboard I get a list of devices, the nvme is not one of them. Does that suggest a set up problem?

[claydoh]

your fstab indicates it isn't even using a boot loader there is no efi partition declared in the fstab, because one wasn't set up and assigned when installing the OS.
The BIOS reads info from all the special EFI partitions , so your BIOS not showing the nvme also indicates there isn't any boot info and files for it.

that's not a bad thing as you can use other boot loaders to do the job, as you are seeing.

I just don't know how to fix yours for a proper boot entry.

But setting up the an EFI partition, adding it to your fstab and then installing grub there is another option.

[johngx]

Thank you claydoh. I really appreciate the help you have been giving me. I'm about to leave on holiday for a couple of weeks. I would like to investigate your last option, can I resume on return?

[claydoh]

it should be easy enough to create a proper menu entry as you are currently attempting., but someone who knows this better is needed.
it probably just needs to point to the correct location for the kernels.

jlittle , what say you?