Ok, so my first attempt at the install with the deb package did not work. I created all partitions needed for linux and installed mint. Updated mint, and rebooted. It booted just fine. I then cloned the drive just in case. Booted back into Mint (BIOS still in CSM mode), and went to install rEFInd, and here is the message I get:
Selecting previously unselected package refind.
(Reading database ... 138689 files and directories currently installed.)
Unpacking refind (from .../refind_0.6.8-1_amd64.deb) ...
Setting up refind (0.6.8-1) ...
/var/lib/dpkg/info/refind.postinst: line 4: efibootmgr: command not found
Installing rEFInd on Linux....
//boot/efi doesn't seem to be on a VFAT filesystem. The ESP must be
mounted at //boot or //boot/efi and it must be VFAT! Aborting!
dpkg: error processing refind (--install):
subprocess installed post-installation script returned error exit status 1
Errors were encountered while processing:
A little more info after spending some time on your website:
Per: http://www.rodsbooks.com/efi-bootloader ... ation.html
Code: Select all
yeep@yeep-Satellite-L855 ~ $ sudo parted /dev/sda print
[sudo] password for yeep:
Model: ATA TOSHIBA MQ01ABD0 (scsi)
Disk /dev/sda: 750GB
Sector size (logical/physical): 512B/512B
Partition Table: gpt
Number Start End Size File system Name Flags
1 1049kB 473MB 472MB ntfs Ba hidden
2 473MB 746MB 273MB fat32 Ba boot
3 746MB 880MB 134MB ntfs Ba msftres
4 880MB 324GB 323GB ntfs
7 324GB 334GB 10.0GB linux-swap(v1)
8 334GB 414GB 80.0GB ext4
9 414GB 525GB 111GB ext4
5 525GB 740GB 215GB ntfs
6 740GB 750GB 10.0GB ntfs Ba hidden
Code: Select all
yeep@yeep-Satellite-L855 ~ $ sudo mount /dev/sda1 /boot/efi
fuse: failed to access mountpoint /boot/efi: No such file or directory
Also, no efi, just grub stuff (Which I will hopefully be able to get rid of after this is done)
Code: Select all
yeep@yeep-Satellite-L855 / $ cd boot
yeep@yeep-Satellite-L855 /boot $ dir
A quote from you on previous pages:
It's almost always possible to convert a BIOS-mode install to boot in EFI mode; however, it requires jumping through some hoops to get it to work right. FWIW, I've just released version 0.6.3 of rEFInd, which includes an install.sh script that's designed to do some of that hoop-jumping for you. In theory, it should work like this:
- Install Windows in EFI mode (or start with a Windows 8 PC).
- Ensure that Secure Boot is disabled.
- Install Mint in BIOS mode and boot into it in BIOS mode.
- Mount your ESP at /boot/efi.
- Install rEFInd by installing the Debian package or by running the install.sh script from the binary zip file.
In theory, when you reboot in EFI mode, rEFInd should come up and let you boot either OS. It does this, though, by installing itself in the Windows boot loader's position, moving the Windows boot loader down one level in the hierarchy. It's possible that Windows will notice this and attempt to "fix" it. To guard against this, you can use the mvrefind.sh script that's new with rEFInd 0.6.3:
Code: Select all
sudo mvrefind.sh /boot/efi/EFI/Microsoft/Boot /boot/efi/EFI/refind
Obviously, step 4 is my problem. Not sure what my ESP is, still trying to hunt down what it means. However, from reading through your site, is sounds like actually trying to find boot/efi is a waste of time if you are booted in bios mode... Which is most likely why I have that error. Anyway, any tips you have would be great. I am not even going to try to boot up into windows, or take this off of CSM (BIOS) mode in the firmware, until I see what you have to say. I do not want winwods trying to fix anything.
According to this: http://www.rodsbooks.com/efi-bootloader ... ation.html
These could be my options:
the command is useless if you're currently booted in BIOS mode—for instance, if you installed Linux in BIOS mode but want to switch to EFI booting. Thus, you may want to use another method to specify the boot loader. I know of several other possibilities:
If you can reach an EFI shell prompt (which typically reads fs0:), you can navigate to the directory in which your boot loader file exists and launch it by typing its name. The EFI shell prompt is similar to a DOS or Bash prompt and takes similar commands.
You can install the boot loader using the default boot loader's location (EFI/BOOT/bootx64.efi on x86-64 systems), as described earlier.
You can install the boot loader under the name used by Microsoft's boot loader, EFI/Microsoft/Boot/bootmgfw.efi. This approach works only if the firmware is hard-coded to look for this file, as some seem to be. (See the next option, though.)
You can use the firmware's own user interface to locate the boot loader file and either add it to the menu or launch the boot loader on a one-time basis.
You can create a startup script, startup.nsh in the ESP's root directory, that does nothing but launch your desired boot loader. This script may optionally begin with a disk specification (usually fs0:) and should use backslashes (\) as directory separators. Thus, such a script might resemble:
This example launches ELILO as the default boot loader. This method will work only if the firmware is configured to launch an EFI shell if other boot options fail. Most EFIs don't do this, though.
Definately need help.