In Kubuntu 25.10 the EFI data seems to be stored in a "kubuntu" folder. Kubuntu used to store its EFI data in an "ubuntu" folder. I wondered if anyone knew when that change happened.
Announcement
Collapse
No announcement yet.
Kubuntu EFI folder.
Collapse
X
-
I have a tiny PC with a mostly vanilla 25.10 install, and the EFI folder is "ubuntu". If yours is indeed "kubuntu", I wonder how you achieved that.
What counts though, is the boot entry revealed by
Note that even if one uses efibootmgr to set a different directory, the path /EFI/ubuntu is coded inside the grubx64.efi executable.Code:sudo efibootmgr
Regards, John Little
- Top
- Bottom
Comment
-
I'm wondering that now myself. That was on my desktop. I didn't think to check my laptop. Checking efibootmgr on my laptop, Kubuntu 25.10 is indeed using the "ubuntu" folder. I multi-boot multiple Linux distros plus a windows install on desktop and laptop. I only discovered it, because I'd just installed CachyOS on my desktop for the first time and the OS finder for grub is switched off by default on CachyOS, so I used efibootmgr to go back to my previous grub menu. But my desktop now definitively seems to be using a grub from the EFI/Kubuntu folder not the EFI/ubuntu folder.Originally posted by jlittle View PostI have a tiny PC with a mostly vanilla 25.10 install, and the EFI folder is "ubuntu". If yours is indeed "kubuntu", I wonder how you achieved that.
So the only thing I can think is this. One of the first things I do after a Kubuntu install is go in and change /etc/default/grub and /etc/lsb-release and then update grub. I change any reference to "Ubuntu" to "Kubuntu" and then update-grub. So maybe what happened is that I installed another version of Kubuntu alongside 25.10, which would wipe out and replace the 25.10 grub. Then at some point I reinstalled the grub on 25.10 and on the reinstall it put it in the EFI/kubuntu folder leaving the other grub undeleted in the EFI/ubuntu folder.
- Top
- Bottom
Comment
-
It's ubuntu on mine also. Not sure what changed yours. But as long as it works I wouldn't worry too much about it.Dave Kubuntu 20.04 Registered Linux User #462608
Wireless Script: http://ubuntuforums.org/showthread.p...5#post12350385
- Top
- Bottom
Comment
-
Again, what is the full path to this directory while running Kubuntu?
The boot files have always been ubuntu and still are. Editing the contents in /etc/default/grub does not change any directory name or mount point.
What does efibootmgr actually show ?
Show us exactly what you see so we can be sure we are all on the same page. Especially as I myself tend to be in Lala land, and likely to be lost
I wonder if this is a drive or device name or label, not a physical directory. More so if you only see this from a different distro.
For example, the installer set my "/" (root) as "kubuntu_25.10":
If you click into the address bar, it should show the actual path, as seen in my first screenshot.
.Last edited by Snowhog; Today, 09:50 AM.
- Top
- Bottom
Comment
-
Sorry I've only just got back on my desktop, I was posting from laptop.Originally posted by claydoh View PostAgain, what is the full path to this directory while running Kubuntu?
The boot files have always been ubuntu and still are. Editing the contents in /etc/default/grub does not change any directory name or mount point.
What does efibootmgr actually show ?
So you are right there is no EFI/Kubuntu folder. I saw the entry labeled as "kubuntu" and just presumed that it must be in a EFI/kubuntu folder, because before Linux grub data had always been in folder with the same name as the efibootmgr label. Apologies for spreading FUD.Code:BootCurrent: 000C Timeout: 1 seconds BootOrder: 000C,0002,000D,0000,000E Boot0000* Windows Boot Manager HD(2,GPT,6887665d-8afc-4af1-9644-4f2727001055,0x109000,0x31800)/File(\EFI\MICROSOFT\BOOT\BOOTMGFW.EFI)57494e444f5753000100000088000000780000004200430044004f0042004a004500430054003d007b00390064006500610038003600320063002d0035006300640064002d0034006500370030002d0061006300630031002d006600330032006200330034003400640034003700390035007d00000074000100000010000000040000007fff0400 Boot0002* cachyos HD(1,GPT,5ed3ce8b-58ba-4e19-a586-e719bd8d8d41,0x800,0x186000)/File(\EFI\CACHYOS\GRUBX64.EFI) Boot000C* Kubuntu HD(1,GPT,5ed3ce8b-58ba-4e19-a586-e719bd8d8d41,0x800,0x186000)/File(\EFI\UBUNTU\SHIMX64.EFI) Boot000D* ubuntu HD(2,GPT,6887665d-8afc-4af1-9644-4f2727001055,0x109000,0x31800)/File(\EFI\UBUNTU\SHIMX64.EFI)0000424f Boot000E* debian HD(2,GPT,6887665d-8afc-4af1-9644-4f2727001055,0x109000,0x31800)/File(\EFI\DEBIAN\GRUBX64.EFI)0000424f
Last edited by Snowhog; Today, 09:52 AM.
- Top
- Bottom
Comment
-
IMO if you do that it's far more reliable to manually maintain an independent grub install and turn off the update-grub machinery where possible.Originally posted by Rich Oliver View PostI multi-boot multiple Linux distros plus a windows install on desktop and laptop.Regards, John Little
- Top
- Bottom
Comment







Comment