Problem adding a manual entry for alternative kernel

[Chris Duston]

Hey all,
I want to use a different kernel for my Slackware install, and use an initial RAM disk. I believe that the initrd was created correctly, so I edited the refind.conf file (installed on OSX) and added the following:

     menuentry "Slackware 14.2 (generic)" {
          icon /EFI/refind/icons/os_arch.png
          #volume 2735d68c-f448-4077-880d-d48f3cfbaffb                          
          volume 735d68C-F448-4077-880D-D48F3CFBAFFB
          loader /boot/vmlinuz-generic-4.4.14
          initrd /boot/initrd.gz
          options "root=/dev/sda6 ro"
}

(That second volume tag is there because I tried to simply capitalize the GUID, to no avail). After selecting this option in refind, the boot screen looks something like this:

Starting vmlinuz-generic-4.4.14
Using load options "root=/dev/sda6 ro initird=\boot\initrd.gz"
Invalid Loader FIle!
Error: Not found while loading vmlinuz-generic-4.4.14

So those forward slashes are actually there, but I'm guessing don't matter. I can't quite tell if it's telling me it can't find the loader at all, or if it finds the loader but there is something wrong with it.

Any thoughts? Thanks guys!

[Roderick W. Smith]

There's a bug in rEFInd 0.11.1 that causes the volume specification to be ignored. This was an easy fix, and the source code is already available in git. If you need the binary, it's available in the Ubuntu PPA and from my Web site:

• http://www.rodsbooks.com/refind-bin-0.11.1.1.zip
• http://www.rodsbooks.com/refind_0.11.1.1-0ppa1_amd64.deb

I'd hoped to do a bit more work on rEFInd and release a 0.11.2 version this past weekend, but I got caught up in other things, so that will have to wait a few more days.

[Chris Duston]

Hey, that's great thanks so much for doing that, now I'm easily booting into my new kernel :-)

Great job!