New Dual Boot Installation of Mint 18.3 Cinammon boots to Windows 10 without workaround

[l2evenge]

I have installed 18.3 Cinammon on an HP Laptop that was originally shipped with Windows 8.1. The installation is a dual boot. I may access the Linux partition when I begin booting the Live USB distro, but exit the grub menu, enter 'exit' into the following menu, then I can select ubuntu and it will run.

I've attempted all of the troubleshooting methods described in the new installation document that was distributed for EFI issues. I've also run boot-repair but it still does not boot give me a menu to select the installation I want to run, it automatically goes to Windows 10.

I have noted that when I make changes in linux to the boot order, restart, and review the boot order in linux, the order has been changed by the system. I am supposing that media that is not booting is being moved to the rear of the boot order by the system?

I am a newbie with Linux, but I am trying to be as self-sufficient as I can.

The link below is the pastebin from my boot-repair run.
http://paste.ubuntu.com/26185516/

[Laurent85]

From your live session run the following commands and provide the results, copy paste each command into terminal:

Code: Select all

sudo mount -o ro /dev/sda1 /mnt
sudo find /mnt -iname "*.efi" -exec md5sum {} + | sort
sudo umount /mnt
sudo efibootmgr -v

[michael louwe]

@ l2evenge, .......

...

.
Please counter-check your installation steps with the following guide on dual-booting LM alongside Win 10/8.1 in UEFI and GPT-disk mode, please refer to .......
viewtopic.php?f=42&t=163126 (dual-booting UEFI computers)
http://linuxmint-installation-guide.rea ... en/latest/
https://sites.google.com/site/easylinux ... ct/windows
https://sites.google.com/site/easylinux ... nt-install
https://www.tecmint.com/install-linux-m ... uefi-mode/ (note step 17)
viewtopic.php?f=42&t=122276 (manual partitioning Tutorial for Legacy BIOS mode and ms-dos disks)

Ensure that Secure Boot, Fast Boot and CSM are disabled in BIOS setup, Fast Startup is disabled in Win 10/8.1(>Control Panel >Power options), the Live LM media(DVD or USB-stick) is booted in UEFI mode in BIOS setup.

To dual-boot, you only need to pre-shrink the Windows partition if you intend to use the manual "Something else" install method, ie no need to do so if you intend to use the automatic "install LM alongside Windows Boot Manager" method, which will be followed by the LM Installer auto-partitioning the disk and auto-installing the Linux Grub bootloader onto the Windows ESP. Only a root / and swap partition will be auto-created with a total default size of about 20GB. The user will be given the option to increase this default size by moving a slider on the colored Partition table, subject to the maximum available free space in the Windows partition.

For the "Something else" install method, manually partition the pre-shrink free space accordingly, eg 50GB for /, 1.5X RAM size for Swap(at the end of this space) and 200GB for Home; and ensure that the "Device for boot loader installation" is the Windows EFI System Partition(= ESP = fat32/about 104MB/mount point is /boot/efi) which is usually dev/sda1.

If you need to reinstall LM, use the "Something else" method, delete all the Linux partitions to create a new free space for the reinstall.

P S - Certain high-end OEM Win 8.x/10 computers, eg Acer, Asus and HP, have an obstructive or pro-M$ BIOS setting for "select an UEFI file as trusted for executing",(= Linux cannot boot) .......
https://itsfoss.com/no-bootable-device-found-ubuntu/
viewtopic.php?t=236560
... The above latest(= 2017) OEM laptops, eg Acer E and S series, may have even removed this BIOS setting(eg "No bootable device" after installing Linux and cannot be fixed), but may be restored by a new BIOS firmware update from the OEMs = update through Windows only. This was after many complaints from affected users. ...
viewtopic.php?f=46&t=254948

[l2evenge]

From your live session run the following commands and provide the results, copy paste each command into terminal:

Code: Select all

sudo mount -o ro /dev/sda1 /mnt
sudo find /mnt -iname "*.efi" -exec md5sum {} + | sort
sudo umount /mnt
sudo efibootmgr -v

Here is the output:

Code: Select all

mint@mint ~ $ sudo mount -o ro /dev/sda1 /mnt
mint@mint ~ $ sudo find /mnt -iname "*.efi" -exec md5sum {} + | sort
0d3b7f7fe348fb82369ede32a6c3bcd7  /mnt/boot-repair/log/20171213_032114/sda2/bootx64.efi
0d3b7f7fe348fb82369ede32a6c3bcd7  /mnt/boot-repair/log/20171214_160956/sda1/bootx64.efi
0d3b7f7fe348fb82369ede32a6c3bcd7  /mnt/EFI/Boot/bkpbootx64.efi
0d3b7f7fe348fb82369ede32a6c3bcd7  /mnt/EFI/Microsoft/Boot/bootmgfw.efi
1b8c0684ede8539ccc205cf7a750eca3  /mnt/EFI/HP/BIOSUpdate/CryptRSA32.efi
1b8c0684ede8539ccc205cf7a750eca3  /mnt/EFI/HP/SystemDiags/CryptRSA32.efi
255f811199c3d5a80eb9ef69df35c63a  /mnt/EFI/HP/boot/memtest.efi
292c1710ae7a50e511bade04b44db178  /mnt/EFI/HP/boot/bootmgr.efi
2da563a53028797f842285b3c9725828  /mnt/EFI/HP/BIOSUpdate/HpBiosUpdate.efi
36b02950fe65ed74866160fbbdf4337f  /mnt/EFI/HP/BIOSUpdate/HpBiosUpdate32.efi
3aef9c72ad50faa8db576c01f85a0915  /mnt/EFI/Boot/bootx64.efi
3aef9c72ad50faa8db576c01f85a0915  /mnt/EFI/ubuntu/shimx64.efi
3edef759f1523a1bc1f56af80604612a  /mnt/EFI/HP/SystemDiags/SystemDiags32.efi
545dcba4a688aba17d3c44ac43d5d9e6  /mnt/EFI/Microsoft/Boot/memtest.efi
5692b49c53b4401e76a43c82d7d496de  /mnt/EFI/HP/boot/bootmgfw.efi
6488d391f74263c9da3c3d47dffa6212  /mnt/EFI/HP/BIOSUpdate/CryptRSA.efi
6488d391f74263c9da3c3d47dffa6212  /mnt/EFI/HP/SystemDiags/CryptRSA.efi
7ac06cc534d41e22fdf5025a01a1bb8a  /mnt/EFI/HP/EFI/Boot/bootx64.efi
8657f5cacc66add291f314c0e5076abd  /mnt/EFI/Microsoft/Boot/bootmgr.efi
86c694d1a08384cd060c2d405b88336c  /mnt/EFI/ubuntu/fwupx64.efi
bb5d5e5f542cefd0d616f8c84397b27b  /mnt/EFI/HP/EFI/Microsoft/Boot/memtest.efi
bf39cf9416a9403d40a9b69541486e74  /mnt/EFI/ubuntu/mmx64.efi
c1e916878afa06b268779e406cd20224  /mnt/EFI/HP/SystemDiags/SystemDiags.efi
e6c2df7a845ec00a2bc4a0d1a6b5baf0  /mnt/EFI/ubuntu/grubx64.efi
mint@mint ~ $ sudo umount /mnt
mint@mint ~ $ sudo efibootmgr -v
BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 2001,0001,0003,0000,3000,0002,2002,2004
Boot0000* Windows Boot Manager	HD(2,GPT,3117800f-93ce-4e04-bd08-ffe17cf36c83,0xc8800,0x82000)/File(\EFI\Microsoft\Boot\bootmgfw.efi)RC
Boot0001* Network Adapter (IPv4 UEFI)	PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)/MAC(fc15b406326f,0)/IPv4(0.0.0.0:0<->0.0.0.0:0,0,0)RC
Boot0002* ubuntu	HD(1,GPT,3117800f-93ce-4e04-bd08-ffe17cf36c83,0xc8800,0x82000)/File(\EFI\ubuntu\shimx64.efi)
Boot0003* Network Adapter (IPv6 UEFI)	PciRoot(0x0)/Pci(0x1c,0x2)/Pci(0x0,0x0)/MAC(fc15b406326f,0)/IPv6([::]:<->[::]:,0,0)RC
Boot0004* USB Hard Drive (UEFI) - PNY     USB 3.0 FD	PciRoot(0x0)/Pci(0x14,0x0)/USB(1,0)/HD(1,MBR,0x96,0x800,0x7367800)RC
Boot2001* EFI USB Device	RC
Boot2002* EFI DVD/CDROM	RC
Boot3000* Internal Hard Disk or Solid State Disk	RC

[Laurent85]

The computer EFI firmware is buggy, it ignores changes of the efi boot loader priority.

Install rEFInd Boot Manager this way from your live session and configure rEFInd in fallback mode as a workaround.

Answer "No" when rEFInd offers to "Automatically install rEFInd to the ESP" :

Code: Select all

sudo add-apt-repository ppa:rodsmith/refind
apt update
apt install refind

Download my installation script :

Code: Select all

wget http://cdimage.tux.ovh/lebd/refind-boot-fix
sudo chmod 755 refind-boot-fix

First run of the installation script configures rEFInd in priority mode :

Code: Select all

sudo ./refind-boot-fix

Installation script output:

Code: Select all

Install rEFInd Boot Manager, confirm "Y" to proceed:
y
Installing rEFInd...

rEFInd Boot Manager set in priority mode...

IF REFIND DOES NOT LOAD ON NEXT STARTUP
RE-RUN THE INSTALLATION PROGRAM TO CONFIGURE
REFIND IN FALLBACK MODE.

Fallback mode should allow rEFInd to load
on computers with buggy EFI firmware.

Installation complete, press return to exit.

Now to configure rEFInd in fallback mode you need to run the installation script anew:

Code: Select all

sudo ./refind-boot-fix

Installation script output:

Code: Select all

Install rEFInd Boot Manager, confirm "Y" to proceed:
Y
Installing rEFInd...

rEFInd Boot Manager set in Fallback mode...

Fallback mode should allow rEFInd to load
on computers with buggy EFI firmware.

Re-run the installation program to configure
rEFInd in priority mode (default mode).

Installation complete, press return to exit.

Reboot normally when done, rEFInd boot Manager should load and offer to boot available EFI boot loaders.