help-grub
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: problems dual booting Ubuntu 16.04 and Windows 10


From: David Collier
Subject: Re: problems dual booting Ubuntu 16.04 and Windows 10
Date: Sun, 13 May 2018 11:26:08 -0700

Pascal, thank you for your patience ;),

On Sun, May 13, 2018 at 12:40 AM Pascal Hambourg <address@hidden>
wrote:

> Le 12/05/2018 à 21:51, David Collier a écrit :
>  > at this point I decided to run grub-install from the locally built
> > directory,
>
> Didn't you say that you uninstalled the locally built GRUB ?


I uninstalled it from /usr/sbin but not removed the build products in the
source tree.


> Uninstall grub-legacy and check that you have at least grub2-common and
> grub-efi-amd64-bin installed. Or just install grub-efi-amd64.
> After EFI boot, run os-prober to check that Windows is detected.
> Run update-grub to include it in GRUB's menu.


I think I followed your instructions closer this time, here is what i get
inside chroot:

vvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvvv
address@hidden:/# dpkg -l  | grep grub
rc  grub                                       0.97-29ubuntu68
                amd64        GRand Unified Bootloader (Legacy version)
ii  grub-common                                2.02~beta2-36ubuntu3.17
                amd64        GRand Unified Bootloader (common files)
ii  grub-efi-amd64                             2.02~beta2-36ubuntu3.17
                amd64        GRand Unified Bootloader, version 2 (EFI-AMD64
version)
ii  grub-efi-amd64-bin                         2.02~beta2-36ubuntu3.17
                amd64        GRand Unified Bootloader, version 2 (EFI-AMD64
binaries)
rc  grub-pc                                    2.02~beta2-36ubuntu3.17
                amd64        GRand Unified Bootloader, version 2 (PC/BIOS
version)
ii  grub2-common                               2.02~beta2-36ubuntu3.17
                amd64        GRand Unified Bootloader (common files for
version 2)
address@hidden:/# os-prober
/dev/sdc2@/efi/Microsoft/Boot/bootmgfw.efi:Windows Boot Manager:Windows:efi
/dev/sde1:unknown Linux distribution:Linux:linux
grub-probe: error: cannot find a GRUB drive for /dev/sdf1.  Check your
device.map.
address@hidden:/# update-grub
Generating grub configuration file ...
Warning: Setting GRUB_TIMEOUT to a non-zero value when GRUB_HIDDEN_TIMEOUT
is set is no longer supported.
Found linux image: /boot/vmlinuz-4.13.0-41-generic
Found initrd image: /boot/initrd.img-4.13.0-41-generic
Found linux image: /boot/vmlinuz-4.13.0-39-generic
Found initrd image: /boot/initrd.img-4.13.0-39-generic
Found linux image: /boot/vmlinuz-4.13.0-38-generic
Found initrd image: /boot/initrd.img-4.13.0-38-generic
done
address@hidden:/#
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

note the error reported by os-prober. Now there is no grub menu at all
during boot, the machine boots directly into Ubuntu (was I supposed to run
grub-mkconfig at some point)?

(Also, in the command line grub now shows two partitions instead of one,
but my experiments with chainloading Windows all failed.)

BTW, I finally figured out how EFI vs legacy boot works - it turns out the
the BIOS in menu mode shows two options for the USB stick, one for legacy
boot and one for EFI boot. I did not pay attention earlier, they get buried
among other options there. I guess I would have saved myself a lot of
trouble if I installed ubuntu originally in EFI mode.

thank you,
-dc


>
_______________________________________________
> Help-grub mailing list
> address@hidden
> https://lists.gnu.org/mailman/listinfo/help-grub
>


reply via email to

[Prev in Thread] Current Thread [Next in Thread]