CentOSThis forum is for the discussion of CentOS Linux. Note: This forum does not have any official participation.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm quite new to the process of setting up linux installations (especially configured as dual boot). I try to set it up on my Vaio Pro 13 via usb install medium.
Basically, I've tried two approaches so far:
1. http://www.tecmint.com/install-centos-7-dual-boot-with-windows-8-uefi-firmware/
Summation: run live usb-stick, create partitioning on my own, result in two efi-boot-partitions.
2. https://www.youtube.com/watch?v=9QzbX8o7pSY
Summation: run live-usb-stick, create partitioning on my own, but select former windows efi-boot-partition and mount it under /boot/efi
The first try left me with a functioning CentOs, but it killed my windows boot entry. Trying to configure a custom boot entry for windows like in the link described or using grub2-probe failed.
The second version ran as smoothly, but after reboot it directly started windows again. I could not get CentOs to run by editing the boot-load with EasyBCD.
As I'm trying for a while, there are a few threads I read, and things that might be important: during installation of CentOs I were not able to decide where the bootloader should go to (at least I think so). Furthermore, although I was able to mount the windows partition in (1), I wasn't able to recreate the boot entry.
I hope for some new directions (or old ones, if you have an indicator what I might have done wrong), as I'd like to get the dual boot to run quite soon. If I missed any information, please ask, and I'll attach it!
As is M$ofts wont, they refuse to acknowledge the rest of the world. Hence such bullshit as safe-boot.
I haven't looked at EasyBCD in a while, but I'd be avoiding it for UEFI.
Hopefully you can get into the UEFI boot selection screen from power-up - find the right key; <Esc>, <F10>, <F12>, ...who knows. From there, you should be able to select Centos. Have a look around, and make sure things look ok - particularly /boot/EFI.
From there you can use efibootmgr to change the default boot entry - see the manpage. Been a while since I looked at CentOS, so I'm not sure what repo efibootmgr will be in.
why are people still trying to use a VERY BAD IDEA from 10 years ago
as above
set the computer to not use Microsoft bastard child Monster of UEFI -- the unholy MONSTER known as "secureboot"
( Boris Karloff needed to narrate that above line )
turn it off
then you can boot into Cent
but you will have to turn it on again to boot into win10
thanks for the help, I now found and resolved the problem.
The problem consisted of my Sony Vaio Pro 13 automatically replacing the EFI-Bootloader by a predefined version (most likely due to the manufacturer created partition, though not tested).
Therefore, CentOs hasn't been able to install itself effectivily as an EFI-entry. I used a dirty hack to make the dual boot run. I copied the Windows-Efi, renamed it, and replaced the original one with the shipped shim.efi. By copying the installed grubx64.efi and a valid grub.cfg, I enabled a grub2-bootloader to get started. I had to replace the windows 10-efi-entry within the grub.cfg with the renamed one, but after that everything goes fine.
Disadvantage: no energy-saving/hibernation anymore; and a grub-update/some windows updates/windows disk and repair might corrupt the boot loader. Make sure to have a copy of the working efis or a live-os with you to repair in such situation.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.