[00:01] Hello! I am trying to install Kubuntu, but got some problems. I want to make DualBoot with Windows 11. Windows installed on one disk, Kubuntu on other, i have installed Kubuntu with manual partitioning, setting /boot/efi 500mb with boot flag, /root and /home encrypted. But when i start and choose the Kubuntu disk its going to grub rescue. [00:01] boot-repair didn't help and chroot into kubuntu and grub-install and grub-update didn't work too, what else do i need, to make this work? [00:03] Kubuntu 24.04 [00:04] what do you mean by "when i start and choose the Kubuntu disk"? where do you choose the disk from, what does it present itself to you as? [00:04] do you boot windows and kubuntu in both uefi mode (did you install kubuntu in uefi mode)? [00:05] does your bios support uefi booting with multiple efi partitions? [00:06] Windows is on /dev/nvme (First disk) with EFI, Kubuntu on /dev/sdb (Second disk) with his EFI. in UEFI on system start i press f11 and choose /dev/sdb instead or /dev/nvme and it shows me grub rescue [00:07] Yes it support that, and i have disabled secure boot [00:08] normally there's only one EFI filesystem on a computer, is this the 'best' way to have installed it? [00:08] If you want to ask did i install Kubuntu EFI into Windows  EFI on /dev/nvme. No i didn't install it there [00:09] Looked at some forums, the guys recommend not to touch windows EFI, and so i have installed it on other disk [00:10] But there is something interesting [00:10] /dev/sdb is a Linux device path, what does the F11 boot menu display the kubuntu boot option as? [00:11] I made some experiments and when i choose my disk, and tap on Erase disk -> next -> and install, it works normally, grub does not enter the rescue terminal, but when i make /boot/efi myself it just don't work [00:12] It shows first device windows boot manager [00:13] Second is my drive where i installed kubuntu, and some third one, not sure what is that, but it enters grub rescue too [00:16] my suspicion is that your "(uefi) bios" is not actually booting the efi bootloader on the esp you have on the (second) "kubuntu disk", but boots from that disk in bios mode, finding an old grub installation on an MBR or bios-grub partition there. [00:16] Maybe i am missing some flags, or some other partition? As i said i am using boot/efi on /dev/sdb1 with FAT32 boot flag 500mb, / on /dev/sdb2 LUKS2 without flags 40gb, and /home on /dev/sdb3 without flags 70gb [00:16] that's why i'm asking what the F11 menu presents the kubuntu boot option like [00:17] let me reconnect to be sure what F11 shows [00:17] Chatting from live usb :) [00:20] an efi system partition needs a GUID of C12A7328-F81F-11D2-BA4B-00A0C93EC93B - does the one on the second disk have that? [00:21] an efi system partition needs a GUID of C12A7328-F81F-11D2-BA4B-00A0C93EC93B - does the one on the second disk have that? [00:21] I am back [00:22] welcome back [00:23] I think i made some bad things with my Grub config so the menu added one extra duplicate, but this is not the problem. As i remember i had 3 elements in menu: 1- Windows Boot Manager (HYPERPC-SSD512) 2- Ubuntu (P0: Apacer AS350 120GB) 3- ubuntu(HYPERPC-SSD512) [00:25] I am not sure about your GUID, if i am right and fdisk -l /dev/sdb shows me identifier ither than you give me 91f1199d etc [00:25] okay, if it says "ubuntu" then it's trying to uefi boot this, that's fine. [00:27] --list-details will show UIIDs [00:28] type uuid on /dev/sdb1 shows exactly your guid [00:29] efibootmgr --verbose will show where the "uefi bios" thinks it can load boot loaders from [00:30] yep shows me my f11 menu [00:30] but ultimately, if it's uefi booting grub off the kubuntu designated disk'S ESP, the issue must be with the grub configuration there. [00:30] The Ubuntu Apacer one shows me \EFI\Kubuntu\shimx64.efi [00:31] The HyperPC SSD512 one shows me \EFI\ubuntu\shimx64.efi [00:31] Windows boot manager \EFI\Microsoft etc [00:32] and the disk path before that seem to be correct as well and match the fdisk --list-verbose output for the partition uuids? [00:32] let me mount that boot disk and check [00:32] no need to mount anything, fdisk can tell [00:33] unless you mean to inspect the grub configuration [00:33] fdisk does not show me any path, so i mounted /dev/sdb1 into /mnt and checked /EFI/ubuntu and Kubuntu [00:33] Looks good there [00:34] i think i understand what you mean [00:35] The Apacer uuid looks good [00:35] But the HyperPC ssd-512 does not match [00:36] Apacer with /dev/sdb1 [00:36] So the actual line is the Apacer with \EFI\Kubuntu\shimx64.efi [00:37] sudo fdisk --list-details /dev/sdb should list the GPT Type-UUID ("GUID") you had checked previously - indicating what partition type (similar to MBR "flags") it is, and a "UUID" for each partition, which is the partition UUID you should also see in the efibootmgr --verbose output [00:37] Yes i checked that [00:39] and ls -l /dev/disk/by-partuuid/THAT_UUID_GOES_HERE says this is sdb1? [00:39] The interesting part, is why Erase disk work fine, and Manual partitioning works that bad :) when i choose Erase it results 2 items, one EFI system FAT32 and other the root ext4, but when i click encrypt it adds ext4 kubuntu_boot, don't know what that means [00:39] let me check that [00:41] No such file or directory [00:41] I am not in chroot, just live usb [00:43] should not matter, did you replace THAT_UUID_GOES_HERE by the UUID seen on efibootmgr --verbose for kubuntu ESP? [00:44] It's just case sensitive [00:44] Yes there is this uuid [00:44] I found it [00:44] But in lower case :) [00:44] and its /sdb1 [00:48] I think Luks2 make the trouble here [00:48] Because in grub i see some text like cryptomount or cryptouuid [00:49] maybe he just can't make luksopen on root for booting [00:49] Not sure [00:50] Or maybe i need to move the /boot on separate partition to avoid encrypting [00:51] Will try to reinit that disk with boot on other partition [00:52] i think the current ubuntu installer supports two approaches for doing disk encryptio, one is the classic approach with unencrypted /boot, the other depends on tpm and secureboot [00:53] i'm not sure what kubuntu supports there. [00:54] i got a warning "A separate boot partition was set up together with an encrypted root partition, but the boot partition is not encrypted. [00:54] There are security concerns with this kind of setup, because important system files are kept on an unencrypted partition. [00:54] You may continue if you wish, but filesystem unlocking will happen later during system startup. [00:54] To encrypt the boot partition, go back and recreate it, selecting Encrypt in the partition creation window." [00:54] not sure about that but i need to try without encryption, to be sure that it's the problem here [00:54] grub can decrypt an encrypted disk under some conditions with a specific configuration, but the "classic approach" is to have grub boot linux off unencrypted /boot, and have the initrd decrypt the / file system [00:56] Maybe the warning is not that much critical for unencrypted /boot anyway luks2 on the remain disk [00:58] whether or not you consider one or the other setup to be critical will depends on your own requirements / interpretation of the security hardening the two approaches provide [00:58] different people have different opinions there [01:00] installer failed to create a partition table, great [01:02] I understand you, but like i see, for now the main hypothesis is the boot encrypted and grub can't decrypt it [01:02] But it would be nice to make it encrypted too :) [01:03] i assume you're trying to make the installer set something up which it does not support [01:04] nah just forgot to make umount for /dev/sdb1 [01:09] Will reboot and reconnect to here after try to check system startup [01:19] Ok i am back, and it started successfully [01:19] So the grub could not decrypt the boot and that's why i got the grub rescue terminal [01:20] Thank you for your help tomreyn [01:20] the encryption of boot will be my headache for tomorrow, i don't want to do that in 5 am :) [02:39] Hello, is anyone active here? [02:40] active? [02:40] this is a help chan, so if you ask your question, someone will try to help [02:40] if you want to chat, #kubuntu-offtopic is there for you [02:41] Ah, I see. My apologies; I just downloaded Konversation and it booted up this channel. I'm not familiar with IRC so I thought I'd send a message and see if anyone would respond. [02:41] New to Linux in general. I don't need help at this time though. Many thanks for responding. [02:42] welcome! [02:42] and konvi <3 [02:43] my favorite since I first tried it [02:43] it makes me happy that people are still discovering IRC [02:43] my favorite "social media" [04:00] * VanUnamed is angry at updates [04:00] i did update today, rendered my pc useless [04:01] aaaa === Lord_of_Life_ is now known as Lord_of_Life [08:46] Hello. When I made an upgrade from kubuntu 22 to 24 all my desktop links stopped working. I use a normal folder view with symbols for a few important programs and I want to keep it that way. Any idea how I can get things to work again? I've read that this is a problem with a certain library in KDE and that it basically cannot be fixed. In that [08:46] case, I have to stop using KDE altogether, because this is a basic functionality and an absolute must for me. Please refrain from any comments why I should want something else like an empty desktop or so, I am not interested. Manys thanks, Hendrik [11:47] Hi all [15:50] also, for some reason, when i start up the pc for a while, after 10 minutes as i set, the screen dims then shut off [15:51] after a while, it does no longer do it [15:51] and remains on non stop [15:51] why [16:59] Hi.. [17:00] My Bluetooth stopped working [17:00] like it doesnt detect any devices [17:00] Any fix? [17:13] Nvm, everyone useless, the issue fixed. === Unit193 is now known as Montresor === WrathOfAchilles is now known as IchabodCrane [22:19] How did you fix the BT?