I am trying to dual boot ubuntu-14.04 with osx 10.7.5 (Lion) on my macmini 2,1
This macmini 2,1 has a 32-bit EFI but 64-bit processor.
I am following the guide at http://www.rodsbooks.com/ubuntu-efi/ but got stuck at step 12.
After reboot, Linux option is shown but it fails to boot linux when selected
rEFInd - Booting OS
Starting vmlinuz-3.16.0-33-generic
Using load options 'ro root=/dev/sda5 initrd=initrd.img-3.16.0-33-generic' Invalid loader file!
Error: Not Found while loading vmlinuz-3.16.0-33-generic
* Hit any key to continue *
The Invalid loader file message indicates that the EFI is not recognizing the kernel as a valid EFI program. The most likely reason for this is if you installed a distribution of the wrong bit depth -- a 64-bit distribution on a 32-bit EFI or a 32-bit distribution on a 64-bit EFI. It could be a bug in the EFI or in the kernel, though. I recommend you double-check your EFI's bit depth by looking on the rEFInd "About" page, and check that against the bit depth of the distribution you've installed.
Another possibility is filesystem corruption on whatever filesystem is holding the kernel. This seems unlikely on a fresh OS installation, though.
Oh, also, I just noticed that you're trying to use a manual boot stanza. Those are notoriously tricky to use correctly. A tiny typo can produce exactly the symptoms you're seeing. Manual boot stanzas are almost never worth using; instead, you should rely on rEFInd's auto-detection features unless you have a very compelling reason to use a manual boot stanza. If auto-detection is not working, then chances are a manual boot stanza won't work, either, and you must diagnose why auto-detection isn't working. If that's why you created a manual boot stanza, I'd start by looking at your EFI filesystem driver configuration; with no or the wrong driver installed, you won't be able to read the kernel.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I am trying to dual boot ubuntu-14.04 with osx 10.7.5 (Lion) on my macmini 2,1
This macmini 2,1 has a 32-bit EFI but 64-bit processor.
I am following the guide at http://www.rodsbooks.com/ubuntu-efi/ but got stuck at step 12.
After reboot, Linux option is shown but it fails to boot linux when selected
rEFInd - Booting OS
Starting vmlinuz-3.16.0-33-generic
Using load options 'ro root=/dev/sda5 initrd=initrd.img-3.16.0-33-generic'
Invalid loader file!
Error: Not Found while loading vmlinuz-3.16.0-33-generic
* Hit any key to continue *
// refind-0.10.2
//
// partition guids
partition4: 4E7C7D44-209A-44BD-80A7-2808C22D6E83
partition5: 8014E4B2-CF90-4531-AE4F-789B4F8A6E43
// from gdisk
Number Start (sector) End (sector) Size Code Name
1 40 409639 200.0 MiB EF00 EFI System Partition
2 409640 117597135 55.9 GiB AF00 Customer <--- OSX Lion
3 117597136 118866671 619.9 MiB AB00 Recovery HD <--- recovery HD
4 119130112 120104959 476.0 MiB 8300 <--- ubuntu /boot
5 120104960 136105983 7.6 GiB 8300 <--- ubuntu /
6 136105984 144105471 3.8 GiB 8200 <--- ubuntu swap
7 144105472 234440703 43.1 GiB 8300 <--- ubuntu /home
99 118866672 119128815 128.0 MiB EF02 BIOS boot partition
// image: ubuntu-mate-14.04.2-LTS-desktop-amd64+mac
// boot partition: /dev/sda4
// root partition: /dev/sda5
// swap : /dev/sda6
// home partition: /dev/sda7
// refind.conf
menuentry Ubuntu {
icon EFI/refind/icons/os_linux.png
volume 4E7C7D44-209A-44BD-80A7-2808C22D6E83
loader vmlinuz-3.16.0-33-generic
initrd initrd.img-3.16.0-33-generic
options "ro root=/dev/sda5"
}
The
Invalid loader file
message indicates that the EFI is not recognizing the kernel as a valid EFI program. The most likely reason for this is if you installed a distribution of the wrong bit depth -- a 64-bit distribution on a 32-bit EFI or a 32-bit distribution on a 64-bit EFI. It could be a bug in the EFI or in the kernel, though. I recommend you double-check your EFI's bit depth by looking on the rEFInd "About" page, and check that against the bit depth of the distribution you've installed.Another possibility is filesystem corruption on whatever filesystem is holding the kernel. This seems unlikely on a fresh OS installation, though.
Oh, also, I just noticed that you're trying to use a manual boot stanza. Those are notoriously tricky to use correctly. A tiny typo can produce exactly the symptoms you're seeing. Manual boot stanzas are almost never worth using; instead, you should rely on rEFInd's auto-detection features unless you have a very compelling reason to use a manual boot stanza. If auto-detection is not working, then chances are a manual boot stanza won't work, either, and you must diagnose why auto-detection isn't working. If that's why you created a manual boot stanza, I'd start by looking at your EFI filesystem driver configuration; with no or the wrong driver installed, you won't be able to read the kernel.