Results 1 to 4 of 4

Thread: Dualboot can reach windows anymore

  1. #1
    Join Date
    Jun 2013
    Beans
    2

    Dualboot can reach windows anymore

    Hi all,


    I hope someone can help me with this problem of mine.

    I´ve got a Lenove y500 preinstalled with Windows 8. Installed Ubuntu 13 on it this weekend which went reasanbly smooth after some initial issues. Both are installed in UEFI mode.

    Current issue: I can´t start Windows up (after a change, i think it was made by the Grub Customizer).

    What do I see: at startup the multiboot screen appears. Which looks ok to me. It contains several Windows and Ubuntu options.
    If I choose for one of the windows-options i get a message which contains something like: ¨Secure boot forbids loading module from (hd0,gpt9)/boot/grub/x86_64-efi/ntfs.mod...reading sector...failed.. no such device..can find drivemap, invalid EFI file path¨

    I ran the boot-repair application which results in the next log: http://paste.ubuntu.com/5771063/

  2. #2
    Join Date
    Apr 2011
    Location
    3rd Rock from the Sun
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Dualboot can reach windows anymore

    Did Boot-Repair fix your issue? what happens when you boot after running Boot Repair?
    "Evolution is Nature's way of issuing upgrades."


  3. #3
    Join Date
    Jun 2013
    Beans
    2

    Re: Dualboot can reach windows anymore

    Quote Originally Posted by fantab View Post
    Did Boot-Repair fix your issue? what happens when you boot after running Boot Repair?
    No it did not. After runnning boot repair it gave me the above log and results.

    It did do something though. My menu looked a little bit different.

  4. #4
    Join Date
    Jun 2009
    Location
    Chicago Suburbs
    Beans
    Hidden!
    Distro
    Ubuntu 14.04 Trusty Tahr

    Re: Dualboot can reach windows anymore

    It looks looks like Boot-Repair did the convert to signed kernel and renamed Windows boot file to allow the grub shim file that has the Microsoft key to work with secure boot on.

    The standard os-prober Windows entries will not work, but the new entries that Boot-Repair adds to 25_custom should boot Windows with secure boot on. Or if your system allows booting Windows with secure boot off.

    grub2's os-prober creates wrong style (BIOS) chain boot entry
    https://bugs.launchpad.net/ubuntu/+s...2/+bug/1024383
    type of entry from Boot-Repair that should work.
    menuentry "Windows UEFI bkpbootmgfw.efi" {
    menuentry "Windows Boot UEFI loader" {
    Type of entry that does not work:
    'Windows ...) (on /dev/sdXY)'
    Some info in Post #3 on cleaning up menus, if desired.
    http://ubuntuforums.org/showthread.php?t=2085530

    Boot-Repair also has done this:

    Boot-Repair - Updated Jan 1, 2013 to not rename first time, but rename if first time Windows does not boot. Post 706 and 711
    http://ubuntuforums.org/showthread.p...769482&page=71
    Boot-Repair copied /EFI/ubuntu/grubx64.efi to /EFI/Boot/bootx64.efi (in case the BIOS is hard-coded to boot into /EFI/Boot/bootx64.efi or secure boot signed GRUB file shimx64.efi.
    Renamed files:
    /EFI/Boot/bkpbootx64.efi
    /EFI/Microsoft/Boot/bkpbootmgfw.efi
    For info on UEFI boot install & repair - Updated Mar 2015:
    http://ubuntuforums.org/showthread.php?t=2147295
    Please use Thread Tools above first post to close thread when/if answered completely.







Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •