On Wed, Dec 28, 2016 at 1:55 PM, Ron Leach <ronleach@xxxxxxxxx> wrote:
Here are the installation details. We have a new laptop with Windows 7 pre-installed, which we'd configured for use, and backed up. The BIOS is set for UEFI with legacy settings.
I don't know what this 2nd sentence means. If you can take a cell photo so the exact context can be determined, it might help understand better. If this is a "legacy boot" option, as in a compatiblity support module to present a faux-BIOS to the OS, this can be problematic. Was this enabled by default (by the manufacturer)? The rest of your description sounds like the firmware is UEFI and both OS's see it as UEFI, not legacy/BIOS.
Since W7 had occupied the whole SSD we've upgraded the SSD (cloning the W7 SSD onto the new SSD using dd) and then rechecked, and tested, W7 running on the lower 228GB of the new SSD; all was fine. We installed F24/Xfce/64 from its 'live' spin onto the the remaining (approx 250 GB) segment of the SSD, allowing it to auto-partition. Installation proceeded without error; gparted showed that F24 had created 2 more partitions above the W7 partitions. On reboot, Grub starts fine, the F24 selection boots perfectly into F24, but selecting Windows just causes the machine to 'hang', showing a constant cursor in the top left corner of the screen.
What version of GRUB is installed? And what do you get for the following commands:
efibootmgr -v
sudo tree -L 3 /boot/efi
In the meantime if you have a version less than grub2-2.02-0.38 you could try updating and see if that fixes the problem. And even before that I'd check the manufacturer's web site for firmware updates. There's ass tons of UEFI firmware bugs, and ass tons do get fixed but you have to apply the update to get them.
--
Chris Murphy
_______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
