[SOLVED] installed fedora-24; unable to boot into windows-10
Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.
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.
installed fedora-24; unable to boot into windows-10
[asus vivomini vm65] hi, i had to hack around with the bios in order to get it to boot up the live-usb. when i restarted fedora, the grub menu didnt list windows-10. here are my partitions:
Code:
[schneidz@xbmc ~]$ sudo fdisk -l
Disk /dev/sda: 931.5 GiB, 1000204886016 bytes, 1953525168 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 4096 bytes
I/O size (minimum/optimal): 4096 bytes / 4096 bytes
Disklabel type: gpt
Disk identifier: 264C98CF-FCEF-4ED6-B98A-E99A835AB90D
Device Start End Sectors Size Type
/dev/sda1 2048 206847 204800 100M EFI System
/dev/sda2 206848 239615 32768 16M Microsoft reserved
/dev/sda3 239616 314812415 314572800 150G Microsoft basic data
/dev/sda4 314812416 315836415 1024000 500M Windows recovery environment
/dev/sda5 315836416 417372159 101535744 48.4G Microsoft basic data
/dev/sda6 417372160 417374207 2048 1M BIOS boot
/dev/sda7 417374208 1953495039 1536120832 732.5G Linux filesystem
And when you canīt boot into Windows, then you should check grub.cfg.
thanks,:
Code:
[schneidz@xbmc ~]$ cat /boot/grub2/grub.cfg
#
# DO NOT EDIT THIS FILE
#
# It is automatically generated by grub2-mkconfig using templates
# from /etc/grub.d and settings from /etc/default/grub
#
### BEGIN /etc/grub.d/00_header ###
set pager=1
if [ -s $prefix/grubenv ]; then
load_env
fi
if [ "${next_entry}" ] ; then
set default="${next_entry}"
set next_entry=
save_env next_entry
set boot_once=true
else
set default="${saved_entry}"
fi
if [ x"${feature_menuentry_id}" = xy ]; then
menuentry_id_option="--id"
else
menuentry_id_option=""
fi
export menuentry_id_option
if [ "${prev_saved_entry}" ]; then
set saved_entry="${prev_saved_entry}"
save_env saved_entry
set prev_saved_entry=
save_env prev_saved_entry
set boot_once=true
fi
function savedefault {
if [ -z "${boot_once}" ]; then
saved_entry="${chosen}"
save_env saved_entry
fi
}
function load_video {
if [ x$feature_all_video_module = xy ]; then
insmod all_video
else
insmod efi_gop
insmod efi_uga
insmod ieee1275_fb
insmod vbe
insmod vga
insmod video_bochs
insmod video_cirrus
fi
}
terminal_output console
if [ x$feature_timeout_style = xy ] ; then
set timeout_style=menu
set timeout=5
# Fallback normal timeout code in case the timeout_style feature is
# unavailable.
else
set timeout=5
fi
### END /etc/grub.d/00_header ###
### BEGIN /etc/grub.d/01_users ###
if [ -f ${prefix}/user.cfg ]; then
source ${prefix}/user.cfg
if [ -n "${GRUB2_PASSWORD}" ]; then
set superusers="root"
export superusers
password_pbkdf2 root ${GRUB2_PASSWORD}
fi
fi
### END /etc/grub.d/01_users ###
### BEGIN /etc/grub.d/10_linux ###
menuentry 'Fedora (4.5.5-300.fc24.x86_64) 24 (Workstation Edition)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-4.5.5-300.fc24.x86_64-advanced-395bacc1-79e4-45bb-857a-d81bdb298b9f' {
load_video
set gfxpayload=keep
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt7'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt7 --hint-efi=hd0,gpt7 --hint-baremetal=ahci0,gpt7 --hint='hd0,gpt7' 395bacc1-79e4-45bb-857a-d81bdb298b9f
else
search --no-floppy --fs-uuid --set=root 395bacc1-79e4-45bb-857a-d81bdb298b9f
fi
linux16 /boot/vmlinuz-4.5.5-300.fc24.x86_64 root=UUID=395bacc1-79e4-45bb-857a-d81bdb298b9f ro rhgb quiet LANG=en_US.UTF-8
initrd16 /boot/initramfs-4.5.5-300.fc24.x86_64.img
}
menuentry 'Fedora (0-rescue-7f1c1f2b158e4b66845117471292ebcd) 24 (Workstation Edition)' --class fedora --class gnu-linux --class gnu --class os --unrestricted $menuentry_id_option 'gnulinux-0-rescue-7f1c1f2b158e4b66845117471292ebcd-advanced-395bacc1-79e4-45bb-857a-d81bdb298b9f' {
load_video
insmod gzio
insmod part_gpt
insmod ext2
set root='hd0,gpt7'
if [ x$feature_platform_search_hint = xy ]; then
search --no-floppy --fs-uuid --set=root --hint-bios=hd0,gpt7 --hint-efi=hd0,gpt7 --hint-baremetal=ahci0,gpt7 --hint='hd0,gpt7' 395bacc1-79e4-45bb-857a-d81bdb298b9f
else
search --no-floppy --fs-uuid --set=root 395bacc1-79e4-45bb-857a-d81bdb298b9f
fi
linux16 /boot/vmlinuz-0-rescue-7f1c1f2b158e4b66845117471292ebcd root=UUID=395bacc1-79e4-45bb-857a-d81bdb298b9f ro rhgb quiet
initrd16 /boot/initramfs-0-rescue-7f1c1f2b158e4b66845117471292ebcd.img
}
### END /etc/grub.d/10_linux ###
### BEGIN /etc/grub.d/20_linux_xen ###
### END /etc/grub.d/20_linux_xen ###
### BEGIN /etc/grub.d/20_ppc_terminfo ###
### END /etc/grub.d/20_ppc_terminfo ###
### BEGIN /etc/grub.d/30_os-prober ###
### END /etc/grub.d/30_os-prober ###
### BEGIN /etc/grub.d/40_custom ###
# This file provides an easy way to add custom menu entries. Simply type the
# menu entries you want to add after this comment. Be careful not to change
# the 'exec tail' line above.
### END /etc/grub.d/40_custom ###
### BEGIN /etc/grub.d/41_custom ###
if [ -f ${config_directory}/custom.cfg ]; then
source ${config_directory}/custom.cfg
elif [ -z "${config_directory}" -a -f $prefix/custom.cfg ]; then
source $prefix/custom.cfg;
fi
### END /etc/grub.d/41_custom ###
i tried running grub2-mkconfig but it doesnt pick up anything windows related.
edit:
i manually added this to grub.cfg:
Code:
menuentry 'Microsoft Windows 10' { set root='hd0,gpt1' chainloader /EFI/Microsoft/Boot/bootmgfw.efi boot }
but when i select it grub instantly highlights the 1st choice (fedora 24) and restarts the countdown.
[asus vivomini vm65] hi, i had to hack around with the bios in order to get it to boot up the live-usb...
a little clarification, the bios menu was very confusing but i think i had to disable secure boot, and enable legacy mode and csm compatibility modes in order for the pc to boot from a usb. the windows-10 came pre-installed from the oem but it is not able to be booted now (even when i try to reset the settings in the bios). although i am able to mount the partitions in fedora.
What exactly were you doing? Why were you booting a Live usb, to install Fedora? You have mixed an MBR and EFI install and this is the result. You show an EFI partition (sda1) which should contain both your windows and Fedora efi boot files. You also have a BIOS boot partition (sda6) which is used when you use GPT without EFI. Mount the EFI partition and take a look at what is there, Fedora and windows files? If not and you were just installing Fedora, it would be simpler to reinstall using EFI. There might be some other way to change this, I don't know.
the only method i know how to install fedora (linux) is using a live-usb. everytime i tried to boot the live-usb on the pc it would go directly into windows. i had to experiment by toggling various switches in the bios for it to recognize the fedora live-usb as a bootable drive.
the only thing thats different this time i installed fedora was that it complained that it needed a 1 mb efi-boot partition because it saw something about efi so i had to create it manually.
If not and you were just installing Fedora, it would be simpler to reinstall using EFI.
none of the screens in the install menu said anything about installing an efi (unless i missed something). do you know what command is needed to install linux using efi ?
ok, with a little more web searching i think the correct question i would want to ask is how to boot up a linux live-usb (particularly fedora-24) in uefi mode.
From your last post, does that mean you have no directory or files referencing Fedora in the EFI directory?
What hardware as some manufacturers do not comply with EFI standard on booting? Check the link below at the Fedora Project for details on booting UEFI.
ok, so i re-installed fedora this time making sure there was a directory named /sys/firmware/efi before running the live-usb's install process.
this is the first pc i bought in 7 years so i had no idea there was such a split between normal bios booting and efi booting. also there is no mention in the pc's manual-booklet or the on screen post messages about selecting a drive to boot. it says 'hit f2 or del to enter bios'. i read an amazon review about a similar pc and the poster said in order to install linux one must repeatedly hit f8 to get to the boot menu to select the usb (i actually tried all the function keys before but none worked -- hitting f2/del/f8 works about half the time).
the problem i am having now is that the first time i rebooted the pc, it gave me the grub menu. i selected windows-10 to verify it works and it did. but when i tried to test if fedora-24 would boot, it no longer shows grub (it boots directly into windows) ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.