srs5694 - after doing some research on the possible existence of multiple Mint kernels, I can tell you that I only have one. I do have two choices for Linux on the rEFInd menu, as well as the windows 8. So, selected the "other" one, to see what I could find. rEFInd tries to boot into BusyBox v 220.127.116.11. During the process of learning what I could and could not do with EFI, I created a live CD of BusyBox, but never installed it. Somehow it placed the kernel where rEFInd can find it. The boot never completes, as the OS is not "complete".
Any tips on how I can remove this? I am about to update rEFInd to the latest (4-25-13 release). Just in case you want to know what version I am working with.
srs5694 wrote:If that's not the case, or if you want to override the behavior, there are ways to change how it works, but I can't provide specifics without specific details, like what rEFInd displays as the filename and volume name for each of the options.
Ok, here is what is displayed...
For windows 8:
Boot EFI\Microsoft\bootmgfw.efi from 259 MiB FAT volume
For Mint 14:
Boot boot\vmlunuz-3.5.0-17generic from 74GiB ext4 volume
For possible BusyBox:
Boot vmlinuz from 74 Gib ext4 volume
Sorry I didn't include that before.