You are not logged in.
Hello!
I've been trying to get rEFInd to use a custom volume badge icon, but I can't seem to get it to work (it continues to show the default disk icon).
The manual says that I need to put the .VolumeBadge.png file into 'the root directory of a partition.' While it's not clear which partition it's referring to, I've tried both the root '/' and the EFI partition '/boot/efi' and neither seem to pick it up. I also tried '/boot' to no avail.
As a test, I put the .VolumeBadge.png into the EFI partition of a boot-able usb drive, and it was able to pick it up.
Any idea why the volume badge won't appear for an internal EFI partition?
I don't want to modify the refind.conf file. I'm trying to figure out how customize the icons and badges with auto-discovery. I want to put other OSs with different badges into play.
I did mange to get a custom OS icon working by labeling the root partition and creating a matching 'os_custom.png' in the refind/icons folder.
For some reason, I can't get the .VolumeBadge.png to load.
Last edited by hobwell (2025-10-25 19:41:36)
Offline
hi. Demonsration:
/dev/sda1(EFI)
'--->/.VolumeBadge.png
/dev/sda2(arch)
'--->/.VolumeBadge.png
/dev/sda3(ubuntu)
'--->/.VolumeBadge.png
so on.
Any idea why the volume badge won't appear for an internal EFI partition?
Because it is intented behaviour?. it is look at removable attribute?(my speculation)
if you test different distros frequently and want automate badge setting;
then write a script that parses output of "file vmlinuzes" (it contains strings such like debian, arch linux, mint ...)
then move related badges to its place and add entries to refind.conf automatically.
Or other way around parse refind.conf then ... same. up to you that which one is fits you.
"The manual says that I need to put the .VolumeBadge.png file into 'the root directory of a partition."
I am interprets this such that you should NOT put VolumeBadge.png into EFI.
PS: if parts is on GPT. GPT provides a label other than 0x8300(linux fs) as 0x8304(linux X86_64 root)
maybe refind clever too much and expects 0x8304 as root label.
Last edited by unixman (2025-10-22 10:10:29)
Offline
Thank you!
I did some experimentation and it looks like the volume badge is intended to go into the EFI partition. I installed another distro onto another drive and if I put the volume badge into the efi partition, it shows up in the rEFInd boot menu.
So I moved the volume badge for this installation into the EFI partiton, but it still doesn't find it.
I wonder if it might be related to the fact that I installed onto a btrfs file partition, where the root is a sub-volume (@). Maybe this makes the 'appropriate' path to the volume badge '@/boot/EFI', but rEFInd is looking at '/boot/EFI' and so doesn't find it?
I had to edit my refind_linux.conf to point to '@/boot/' in order to load the appropriate initramfs for zen, which is what makes me think this might be the case.
Offline
So after a little more experimentation, I've got it working.
In some cases, it will find the volume badge in the EFI partition, but it can also find it in the root of the partition with the OS. There seems to be some criteria I'm not aware of as I've had each location work exclusively from the other, but I don't really know why.
In this case, the issue was that I was putting the volume badge into the root sub-volume, rather than the partition root.
So I mounted the top level root:
sudo mount -o subvolid=5 /dev/sdxxn /mnt/root
then copied the file there:
sudo cp /.VolumeBadge.png /mnt/root/
Upon reboot, the badge appeared!
Offline