Announcement

Collapse
No announcement yet.

Windows 8 inaccessible after installing Kubuntu 12.10

Collapse
This topic is closed.
X
X
Collapse
 
  • Page of 8
  • Filter
  • Time
  • Show
Clear All
new posts
Previous 1 2 3 4 5 6 7 8 template Next
    #61
    longnosemonkey:

    I need Windows 8 for games and work. So I need to dual-boot.
    Really?

    Win7 is pretty recent. Do you really NEED Win8? Win7 can be run as a virtual machine on Linux, and if this is done on a multi-core machine with a fair bit of memory, Windows will run at near native speed (some even claim faster than native). WINE is another option if the Windows apps you need for work are supported by it.

    As I suggested earlier, you can also just run Linux on another machine. Hardware is cheap these days, and even a used machine a couple of years old will give excellent performance. Files can be kept in sync between the two machines in the cloud, or over a LAN with xcopy or rsync (rsync is available for Windows too). I've been doing that for years, though my days of needing to maintain a Windows box are long gone.

    Dual boot works on pre Win8 machines, but I find the annoyances beyond what I am willing to put up with.

    Frank.
    Linux: Powerful, open, elegant. Its all I use.
    • Top
    • Bottom

    Comment

      #62
      longnosemonkey:

      But are there any technical problems with this idea? Is it just a minor annoyance only? Can I do that instead of doing one system/hard drive, one OS?
      Sorry, I missed this part of your post the first time.

      As to technical problems, I don't know. As I said, I'm no Linux guru. Perhaps someone else can weigh in on this. Remember that Win8 is relatively new to all of us, so learning to work with it is going to take some time. What I shared with you here is just my limited experience.

      As to one drive / one OS, that is just my way of doing things. It has saved me a lot of grief, and I think it is of value. I have more machines lying around than I know what to do with, and I've learned how to keep them in sync with one another. For me this works well, and I don't dual boot. I just have a lot of machines.

      And, as mentioned in my previous answer, you can always run Windows as a guest OS in a virtual machine hosted on Linux. I've done that in the past, and it works very well.

      Frank.
      Linux: Powerful, open, elegant. Its all I use.
      • Top
      • Bottom

      Comment

        #63
        longnosemonkey: My apologies for missing your thread until now. The last several days have been unusually busy for me, and my presence on KFN has been almost none. I'm easing back into my normal routine now.

        First, please feel free to ignore whatever Toshiba tells you about Secure Boot. The Windows 8 certification requirements mandate that hardware OEMs provide a way to disable Secure Boot. Toshiba can claim they won't "support" you, but when's the last time you actually needed support from an OEM anyway? Windows will still boot fine, even the Windows that's installed by Toshiba at the factory. Disabling Secure Boot shouldn't stop the pre-installed Windows from running.

        Second, I took a quick look at that bootinfoscript thing and I'm not sure I trust it. First, computers running UEFI typically don't have MBRs. In fact, Windows in UEFI mode won't work with MBR-style bootable disks at all. It requires GPT. So for the script to claim that a boot loader is installed in the MBR is suspicious. Furthermore, I just ran it on my machine. I'm running in UEFI mode, no Windows, GPT disk, and -- importantly -- no GRUB. I boot the kernel directly from UEFI. Here's what bootinfoscript says about my machine:

        Code:
         => Grub2 (v1.99) is installed in the MBR of /dev/sda and looks at sector 
    408190672 of the same hard drive for core.img, but core.img can not be 
    found at this location.
        I can assure you that there is no MBR on my disk whatsoever! Furthermore, the indicated sector is not on a partition boundary but instead lies within my / partition. Therefore, I'm not sure how accurate your RESULTS1.txt really is.

        I am considering a number of options for you, one of which includes getting restore discs, paving everything, starting clean with Secure Boot switched off, and doing things the "right" way. But first, a bit more, if you don't mind.

        The reason you're seeing some boot loader choices is that your UEFI NVRAM boot variables are likely malformed at this point. I would like to have an accurate list of what your UEFI contains. Please boot into Kubuntu and run the following command:

        Code:
        sudo efibootmgr -v
        Reply here with the output. Then we can continue.
        • Top
        • Bottom

        Comment

          #64
          Hm. Apparently, uninstalling GRUB and using GDISK to "zap" all structures doesn't really wipe out an old MBR! After I posted the above, I decided to check the actual bits on my drive. I dumped the first 512 bytes, which constitute the MBR of an MBR-formatted disk, thusly:
          Code:
          sudo dd if=/dev/sda of=mbr.bin bs=512 count=1
          And then took a look, thusly:
          Code:
          od -Ad -tx1z mbr.bin
          Lo! What do I see?
          Code:
          steve@t520:~/junk$ [B]od -Ad -tx1z mbr.bin[/B]
0000000 eb 63 90 00 00 00 00 00 00 00 00 00 00 00 00 00  >.c..............<
0000016 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  >................<
*
0000080 00 00 00 00 00 00 00 00 00 00 00 80 d0 7e 54 18  >.............~T.<
0000096 00 00 00 00 ff fa 90 90 f6 c2 80 74 05 f6 c2 70  >...........t...p<
0000112 74 02 b2 80 ea 79 7c 00 00 31 c0 8e d8 8e d0 bc  >t....y|..1......<
0000128 00 20 fb a0 64 7c 3c ff 74 02 88 c2 52 bb 17 04  >. ..d|<.t...R...<
0000144 80 27 03 74 06 be 88 7d e8 17 01 be 05 7c b4 41  >.'.t...}.....|.A<
0000160 bb aa 55 cd 13 5a 52 72 3d 81 fb 55 aa 75 37 83  >..U..ZRr=..U.u7.<
0000176 e1 01 74 32 31 c0 89 44 04 40 88 44 ff 89 44 02  >..t21..D.@.D..D.<
0000192 c7 04 10 00 66 8b 1e 5c 7c 66 89 5c 08 66 8b 1e  >....f..\|f.\.f..<
0000208 60 7c 66 89 5c 0c c7 44 06 00 70 b4 42 cd 13 72  >`|f.\..D..p.B..r<
0000224 05 bb 00 70 eb 76 b4 08 cd 13 73 0d f6 c2 80 0f  >...p.v....s.....<
0000240 84 d0 00 be 93 7d e9 82 00 66 0f b6 c6 88 64 ff  >.....}...f....d.<
0000256 40 66 89 44 04 0f b6 d1 c1 e2 02 88 e8 88 f4 40  >@f.D...........@<
0000272 89 44 08 0f b6 c2 c0 e8 02 66 89 04 66 a1 60 7c  >.D.......f..f.`|<
0000288 66 09 c0 75 4e 66 a1 5c 7c 66 31 d2 66 f7 34 88  >f..uNf.\|f1.f.4.<
0000304 d1 31 d2 66 f7 74 04 3b 44 08 7d 37 fe c1 88 c5  >.1.f.t.;D.}7....<
0000320 30 c0 c1 e8 02 08 c1 88 d0 5a 88 c6 bb 00 70 8e  >0........Z....p.<
0000336 c3 31 db b8 01 02 cd 13 72 1e 8c c3 60 1e b9 00  >.1......r...`...<
0000352 01 8e db 31 f6 bf 00 80 8e c6 fc f3 a5 1f 61 ff  >...1..........a.<
0000368 26 5a 7c be 8e 7d eb 03 be 9d 7d e8 34 00 be a2  >&Z|..}....}.4...<
0000384 7d e8 2e 00 cd 18 eb fe 47 52 55 42 20 00 47 65  >}.......GRUB .Ge<
0000400 6f 6d 00 48 61 72 64 20 44 69 73 6b 00 52 65 61  >om.Hard Disk.Rea<
0000416 64 00 20 45 72 72 6f 72 0d 0a 00 bb 01 00 b4 0e  >d. Error........<
0000432 cd 10 ac 3c 00 75 f4 c3 00 00 00 00 00 00 00 00  >...<.u..........<
0000448 01 00 ee fe ff ff 01 00 00 00 af 32 cf 1d 00 00  >...........2....<
0000464 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  >................<
*
0000496 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa  >..............U.<
0000512
          Why, it's left-over MBR and GRUB junk! A portion of the bootstrap area had been cleared, but not the full 440 bytes (0..439). Bytes 440..445, the MBR signature field, is blank, meaning that effectively I have no usable MBR. Furthermore, notice the single partition defined in bytes 446..461 of type EE -- this is the "protective MBR" that GPT defines across the entire disk, which instructs MBR-based utilities to stay away. Also, note the legacy 0xaa55 boot signature stuck in the last two bytes -- this marks the end of an MBR.

          As an experiment, since I had saved the MBR into a file, I decided to really blank it out by putting zeroes in the bootstrap area, thusly:
          Code:
          sudo dd if=/dev/zero of=/dev/sda bs=440 count=1
          Then I rebooted. As expected, the computer boots fine. I dumped the first sector again, and now you can see it's finally clean:
          Code:
          steve@t520:~/junk$ [B]od -Ad -tx1z nombr.bin[/B]
0000000 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  >................<
*
0000448 01 00 ee fe ff ff 01 00 00 00 af 32 cf 1d 00 00  >...........2....<
0000464 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00  >................<
*
0000496 00 00 00 00 00 00 00 00 00 00 00 00 00 00 55 aa  >..............U.<
0000512
          Now, after running bootinfoscript again, I see this:
          Code:
           => No boot loader is installed in the MBR of /dev/sda.
          So my mistrust of this script is perhaps misplaced. That's really the point of this follow-up post: to correct my earlier assertion, through experimentation.

          Still: I do need to see the output of that efibootmgr command on the OP's PC before we continue.
          Last edited by Snowhog; Dec 29, 2012, 12:19 PM. Reason: syntax correction
          • Top
          • Bottom

          Comment

            #65
            To those who don't like where Microsoft is going, I just want to bring your attention to this:

            Free Software Foundation Thinks It Can Stop SecureBoot

            The Free Software Foundation is now soliciting donations and signatures for a pledge in hopes that it can stop UEFI SecureBoot and other "restricted boot" systems from becoming too common.

            There was a posting to the Free Software Foundation's web-site on Thursday that was an appeal to sign their pledge not to purchase or recommend any computer hardware that employs SecureBoot or any other restricted boot techniques. The pledge is titled "Stand up for your freedom to install free software" and so far have received over 40,000 signatures and the support of just 50 organizations.

            Aside from asking for more signatures, they're also trying to get more individuals to donate at least $50 USD to the FSF in order to further their cause of stopping Secure Boot. They hope to stop Secure/Restricted Boot by building public support around their statement, fighting Microsoft's attempt to enforce Restricted Boot on ARM devices, working with manufacturers to ensure users can change the software running on their machine, working with computer vendors friendly towards GNU/Linux, and providing information about computers/components that are most compatible with free software. The Free Software Foundation also says they'll be releasing a new Secure Boot white-paper in January.

            While it's a nice thought to get rid of SecureBoot, it's a very tough challenge going against Microsoft especially with their mandate for Windows 8 PC certification be that UEFI SecureBoot is utilized. If SecureBoot is to be unseated, it's more likely it will be as a result of government (namely the EU) intervention rather than the FSF.

            For more information on this latest FSF effort, see their new posting.
            Here is the link to the FSF's drive to stop SecureBoot. If you think that SecureBoot takes away your rights and choices, as I do, from the last two weeks of struggle trying to get Linux and Windows 8 to co-exist on the same laptop, please sign the petition or donate some money to the Free Software Foundation.

            If you really think this is an important issue and have some extra cash, you might consider suing Microsoft over this practice. If I had any money, I'd do it myself.
            • Top
            • Bottom

            Comment

              #66
              SteveRiley, I'm glad that you're here at last. I feel like I've been waiting for Godot.

              I'm going to go run that script but first, since you referred to UEFI, I want to mention something. I thought that all new computers should be running UEFI which is supposed to be BIOS in a modern UI. But my laptop runs the old blue, 80s BIOS interface. So I don't know if I am running UEFI, BIOS or some hybrid.

              I'll go run that command and I'll be back with the results.
              • Top
              • Bottom

              Comment

                #67
                Hi SteveRiley. Here are the results you wanted:

                Code:
                BootCurrent: 0004
Timeout: 0 seconds
BootOrder: 0004,0005,2003,2001,2002
Boot0001* EFI Network 0 for IPv4 (08-9E-01-4C-16-A0)    ACPI(a0341d0,0)PCI(4,0)PCI(0,0)MAC(089e014c16a0,0)IPv4(0.0.0.0:0<->0.0.0.0:0,0, 0RC
Boot0002* EFI Network 0 for IPv6 (08-9E-01-4C-16-A0)    ACPI(a0341d0,0)PCI(4,0)PCI(0,0)MAC(089e014c16a0,0)030d3c000000000000000000000000000000000000000000000000000000000000000000000000000000004000000000000000000000000000000000RC
Boot0003* Windows Boot Manager  HD(2,e1800,82000,824f6ace-ed90-11e1-ad7d-b99d37917e0d)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot0004* Ubuntu        HD(2,e1800,82000,52ef751e-4993-11e2-9206-f0222b64ae2e)File(\EFI\ubuntu\grubx64.efi)RC
Boot0005* Windows Boot Manager  HD(2,e1800,82000,52ef751e-4993-11e2-9206-f0222b64ae2e)File(\EFI\Microsoft\Boot\bootmgfw.efi)WINDOWS.........x...B.C.D.O.B.J.E.C.T.=.{.9.d.e.a.8.6.2.c.-.5.c.d.d.-.4.e.7.0.-.a.c.c.1.-.f.3.2.b.3.4.4.d.4.7.9.5.}....................
Boot2001* EFI USB Device        RC
Boot2002* EFI DVD/CDROM RC
Boot2003* EFI Network   RC
                Last edited by SteveRiley; Dec 29, 2012, 04:47 PM.
                • Top
                • Bottom

                Comment

                  #68
                  Originally posted by longnosemonkey View Post
                  I thought that all new computers should be running UEFI which is supposed to be BIOS in a modern UI. But my laptop runs the old blue, 80s BIOS interface. So I don't know if I am running UEFI, BIOS or some hybrid.
                  Don't conflate the appearance of the firmware's configuration pages influence whether you think you're looking at BIOS or UEFI. While it's true that many UEFI machines have fancy graphical interfaces with mouse support and other gewgaws, UEFI firmware UIs can also be plain, boring, 80x25 white on blue/black text. The kind of UI you see is orthogonal to the kind of firmware you have.

                  It's obvious that your machine is UEFI-based, otherwise the command I had you typed (which I'll analyze in a moment) wouldn't have even worked. I do have one question for you: when you say you disable Secure Boot, are you certain that you're doing this? The reason I ask is that many UEFI firmwares can be switched into BIOS emulation mode. And since it's unfortunately common to think that UEFI and Secure Boot are the same thing (they aren't), I want to ensure that you're actually disabling Secure Boot as opposed to enabling BIOS compatibility mode. Please double-check the exact wording you see in your firmware's menus and let me know. Thanks.
                  • Top
                  • Bottom

                  Comment

                    #69
                    Originally posted by longnosemonkey View Post
                    Hi SteveRiley. Here are the results you wanted:
                    As I suspected, this looks to be malformed.

                    You have two entries for Windows, each one on a separate partition. Boot0003 points to the partition whose UUID begins with "824f6ace..." and Boot0005 points to the partition whose UUID begins with "52ef751e..."

                    You have one entry for (K)ubuntu, Boot0004, that's pointing to the same boot partition as the second Windows. This is to be expected: UEFI machines must have a dedicated FAT32 partition that contains the boot loaders for all installed operating systems.

                    Please show the output of these commands:
                    Code:
                    ll /dev/disk/by-partuuid

ll /dev/disk/by-uuid
                    Now here's something else I'd like you to consider. We can methodically work through repairing what you have, going back and forth on the forum here. It will be a learning experience for you, but likely to be uninteresting unless you dig this kind of low-level stuff. Alternately, since your computer is new, you have the option of a simpler route: pave the drive completely, disable Secure Boot, enable BIOS compatibility mode to simplify things further, and then install Windows and Kubuntu in the more traditional, MBR+BIOS way.

                    Yet another thing to consider would be to abandon dual boot completely, and instead install Kubuntu on the bare metal, and then install Windows into a virtual machine. Honestly, unless you want to go the geeky route (which I'm prepared to help you with), I'd recommend this final suggestion. Dual-boot is always somewhat fragile.
                    • Top
                    • Bottom

                    Comment

                      #70
                      I do have one question for you: when you say you disable Secure Boot, are you certain that you're doing this? The reason I ask is that many UEFI firmwares can be switched into BIOS emulation mode. And since it's unfortunately common to think that UEFI and Secure Boot are the same thing (they aren't), I want to ensure that you're actually disabling Secure Boot as opposed to enabling BIOS compatibility mode. Please double-check the exact wording you see in your firmware's menus and let me know. Thanks.
                      When I said I disabled SecureBoot, I meant that, upon turning on the laptop, I'd held down F12 until I reached what I think is the blue UI of the BIOS/UEFI. However, now that I look closely, at the top, it calls itself the InsydeH20 Setup Utility. That doesn't sound like BIOS.... if I've been doing this incorrectly all this time, I'm a fool. Anyhow, I switch over to the Security tab and on that page, I have the option of disabling or enabling "Secure Boot". And that is what I have been doing. If I disable Secure Boot, I boot to Windows 8 and if I enable it, I boot to Kubuntu.


                      SteveRiley, here is something you should know about my partitioning on this harddrive: The laptop came with
                      /dev/sda1 - 450 MiB system partition (NTFS)
                      /dev/sda2 - 260MiB Boot partition (FAT32)
                      /dev/sda3 - 128MiB 'msftres' partition (NTFS)
                      /dev/sda4 - 586GiB Windows 8 partition (NTFS)
                      /dev/sda5 - 9.18GiB Recovery partition (NTFS)

                      All this information was taken from GParted before I partitioned or installed Kubuntu.

                      I resized and partitioned the Windows 8 partition into
                      /dev/sda4 - 150GB Windows 8 partition (NTFS)
                      /dev/sda6 - 400GB Data partition (NTFS)
                      /dev/sda7 - 20GB Linux root partition (ext4)
                      /dev/sda8 - 16GB Linux swap partition

                      Then I installed Kubuntu. Perhaps all these partitions were part of the problem?

                      I like my games and so I need Windows. I can't play Skyrim or Far Cry 3 in Kubuntu or I would've ditched Windows. If Valve's Steam box Linux console takes off, 2013 may finally be the year of Linux, but until then I think I'll have to dual boot. I don't want to start my brand new laptop with corruptions, so if you'll assist me, I would like to restore this laptop to factory condition and then set up the laptop to dual boot Windows 8 and Kubuntu.
                      Last edited by SteveRiley; Dec 30, 2012, 06:34 PM. Reason: added partition names according to bootinfoscript (for reference purposes)
                      • Top
                      • Bottom

                      Comment

                        #71
                        I'm not sure what you meant by the "||" in front of those commands, but konsole didn't like them, so I tried entering the commands without them and tried two smaller case ls as well:

                        When I put in:
                        Code:
                        || /dev/disk/by-partuuid
                        I got:
                        Code:
                        syntax error near unexpected token `||'
                        So I tried
                        Code:
                        /dev/disk/by-partuuid
                        and got:
                        Code:
                        Is a directory
                        Then I tried:
                        Code:
                        ll /dev/disk/by-partuuid
                        and got:
                        Code:
                        total 0
drwxr-xr-x 2 root root 200 Dec 29 14:21 ./
drwxr-xr-x 8 root root 160 Dec 29 14:21 ../
lrwxrwxrwx 1 root root  10 Dec 29 14:22 3d5f5260-b23f-4653-920e-323dfca68992 -> ../../sda8
lrwxrwxrwx 1 root root  10 Dec 29 14:22 52ef7516-4993-11e2-9206-f0222b64ae2e -> ../../sda1
lrwxrwxrwx 1 root root  10 Dec 29 14:22 52ef751e-4993-11e2-9206-f0222b64ae2e -> ../../sda2
lrwxrwxrwx 1 root root  10 Dec 29 14:22 52ef7520-4993-11e2-9206-f0222b64ae2e -> ../../sda3
lrwxrwxrwx 1 root root  10 Dec 29 14:22 52ef7528-4993-11e2-9206-f0222b64ae2e -> ../../sda4
lrwxrwxrwx 1 root root  10 Dec 29 14:22 52ef7530-4993-11e2-9206-f0222b64ae2e -> ../../sda5
lrwxrwxrwx 1 root root  10 Dec 29 14:22 55aae584-d178-4213-841f-4cc0c1fb3def -> ../../sda6
lrwxrwxrwx 1 root root  10 Dec 29 14:22 6468b9d8-d9dd-4374-be6d-59f830f40981 -> ../../sda7
                        Putting in
                        Code:
                        ll /dev/disk/by-uuid
                        produced:
                        Code:
                        total 0
drwxr-xr-x 2 root root 220 Dec 29 14:22 ./
drwxr-xr-x 8 root root 160 Dec 29 14:21 ../
lrwxrwxrwx 1 root root  10 Dec 29 14:22 004048725864118E -> ../../sda6
lrwxrwxrwx 1 root root  10 Dec 29 14:22 3EB06FBBB06F77F3 -> ../../sdb1
lrwxrwxrwx 1 root root  10 Dec 29 14:22 6161609e-26d5-4432-84c0-f3c52f6d9293 -> ../../sda7
lrwxrwxrwx 1 root root  10 Dec 29 14:22 92CEB410CEB3EB1D -> ../../sda1
lrwxrwxrwx 1 root root  10 Dec 29 14:22 9EA4BCC6A4BCA267 -> ../../sda5
lrwxrwxrwx 1 root root  10 Dec 29 14:22 A6A4B9E6A4B9B8DF -> ../../sda4
lrwxrwxrwx 1 root root  10 Dec 29 14:22 ACDCB720DCB6E42C -> ../../sda3
lrwxrwxrwx 1 root root  10 Dec 29 14:22 B6B5-63F7 -> ../../sda2
lrwxrwxrwx 1 root root  10 Dec 29 14:22 c02dbeb8-cff5-493b-bd32-f894a9453e6b -> ../../dm-0
                        I have to leave now, but if you could leave some directions on the dual boot plan, I'll try to get it done tomorrow.
                        Last edited by SteveRiley; Dec 29, 2012, 08:56 PM.
                        • Top
                        • Bottom

                        Comment

                          #72
                          Originally posted by longnosemonkey View Post
                          it calls itself the InsydeH20 Setup Utility. That doesn't sound like BIOS
                          That is, in fact, the firmware setup utility.

                          One ongoing problem with the transition from BIOS to UEFI is that imprecise lexicon will no longer do. Once upon a time, the only firmware you could get was BIOS, and the only thing you could boot into was the "BIOS setup," so the word BIOS came to mean different things. But we all understood each other because of the context. Well, in the days of UEFI, it is no longer accurate to say "boot into the BIOS."

                          That's why it might appear in my UEFI-related posts that I'm something of stickler for precise terminology. It helps to avoid a lot of confusion.

                          The firmware in modern machines is now UEFI, and only UEFI. This can be run in one of two modes: UEFI or BIOS compatibility (sometimes CSM). The firmware setup utility allows you to configure, among other things, the mode the firmware runs in. When in UEFI mode, Secure Boot becomes an available optional feature.

                          InsydeH2O is a brand of firmware. Other brands include Phoenix, American Megatrends, Award, plus many others. Almost all of these are guilty of calling their UEFI firmware a "UEFI BIOS," which only adds to the confusion.

                          Originally posted by longnosemonkey View Post
                          I switch over to the Security tab and on that page, I have the option of disabling or enabling "Secure Boot". And that is what I have been doing.
                          Sounds right.

                          Originally posted by longnosemonkey View Post
                          If I disable Secure Boot, I boot to Windows 8 and if I enable it, I boot to Kubuntu.
                          Uh, this would appear to be the opposite of what you wrote in post #50. Please confirm.
                          Last edited by SteveRiley; Dec 29, 2012, 09:00 PM.
                          • Top
                          • Bottom

                          Comment

                            #73
                            I see you eventually figured it out... the two characters are "el el," not "bar bar."

                            Also, it's very helpful if you surround console output with CODE tags, not QUOTE tags.

                            What is the output of:
                            Code:
                            ll -R /boot/efi/EFI
                            (BTW, I'm reaching a conclusion here, but not quite yet ready to provide a recommendation. You do have some goofy stuff going on.)
                            • Top
                            • Bottom

                            Comment

                              #74
                              Uh, this would appear to be the opposite of what you wrote in post #50. Please confirm.
                              You are right of course. Post #50 is correct, I reversed the order here.

                              I put this command in
                              Code:
                              ll -R /boot/efi/EFI
                              and got.. hoo boy...

                              Code:
                              /boot/efi/EFI:
total 24
drwxr-xr-x 6 root root 4096 Dec 25 15:05 ./
drwxr-xr-x 3 root root 4096 Dec 31  1969 ../
drwxr-xr-x 2 root root 4096 Dec 18 21:10 Boot/
drwxr-xr-x 3 root root 4096 Dec 18 21:10 Microsoft/
drwxr-xr-x 3 root root 4096 Dec 18 21:10 toshiba/
drwxr-xr-x 2 root root 4096 Dec 25 15:05 ubuntu/

/boot/efi/EFI/Boot:
total 1332
drwxr-xr-x 2 root root    4096 Dec 18 21:10 ./
drwxr-xr-x 6 root root    4096 Dec 25 15:05 ../
-rwxr-xr-x 1 root root 1354480 Jul 25 21:57 bootx64.efi*

/boot/efi/EFI/Microsoft:
total 12
drwxr-xr-x  3 root root 4096 Dec 18 21:10 ./
drwxr-xr-x  6 root root 4096 Dec 25 15:05 ../
drwxr-xr-x 39 root root 4096 Dec 18 21:10 Boot/

/boot/efi/EFI/Microsoft/Boot:
total 4176
drwxr-xr-x 39 root root    4096 Dec 18 21:10 ./
drwxr-xr-x  3 root root    4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root   36864 Dec 29 12:03 BCD*
-rwxr-xr-x  1 root root   32768 Dec 18 21:10 BCD.LOG*
-rwxr-xr-x  1 root root       0 Dec 18 21:10 BCD.LOG1*
-rwxr-xr-x  1 root root       0 Dec 18 21:10 BCD.LOG2*
drwxr-xr-x  2 root root    4096 Dec 18 21:10 bg-BG/
-rwxr-xr-x  1 root root 1354480 Jul 25 21:57 bootmgfw.efi*
-rwxr-xr-x  1 root root 1350896 Jul 25 21:57 bootmgr.efi*
-rwxr-xr-x  1 root root   65536 Dec 18 21:10 BOOTSTAT.DAT*
-rwxr-xr-x  1 root root    4186 Jun 26  2012 boot.stl*
drwxr-xr-x  2 root root    4096 Dec 18 21:10 cs-CZ/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 da-DK/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 de-DE/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 el-GR/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 en-GB/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 en-US/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 es-ES/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 et-EE/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 fi-FI/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 Fonts/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 fr-FR/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 hr-HR/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 hu-HU/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 it-IT/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 ja-JP/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 ko-KR/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 lt-LT/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 lv-LV/
-rwxr-xr-x  1 root root 1263856 Jul 25 21:57 memtest.efi*
drwxr-xr-x  2 root root    4096 Dec 18 21:10 nb-NO/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 nl-NL/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 pl-PL/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 pt-BR/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 pt-PT/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 qps-ploc/
drwxr-xr-x  4 root root    4096 Dec 18 21:10 Resources/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 ro-RO/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 ru-RU/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 sk-SK/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 sl-SI/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 sr-Latn-CS/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 sv-SE/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 tr-TR/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 uk-UA/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 zh-CN/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 zh-HK/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 zh-TW/

/boot/efi/EFI/Microsoft/Boot/bg-BG:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 77040 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 77040 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/Microsoft/Boot/cs-CZ:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/da-DK:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 75504 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 75504 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/de-DE:
total 216
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 78576 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 78576 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45808 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/el-GR:
total 216
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 79600 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 79600 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 46320 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/en-GB:
total 152
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 73456 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 73456 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/Microsoft/Boot/en-US:
total 200
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 73456 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 73456 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/es-ES:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 77040 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 77040 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45808 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/et-EE:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 74480 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 74480 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/Microsoft/Boot/fi-FI:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/Fonts:
total 13080
drwxr-xr-x  2 root root    4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root    4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 3694080 Jun  2  2012 chs_boot.ttf*
-rwxr-xr-x  1 root root 3876772 Jun  2  2012 cht_boot.ttf*
-rwxr-xr-x  1 root root 1984228 Jun  2  2012 jpn_boot.ttf*
-rwxr-xr-x  1 root root 2371360 Jun  2  2012 kor_boot.ttf*
-rwxr-xr-x  1 root root  168212 Jun  2  2012 malgun_boot.ttf*
-rwxr-xr-x  1 root root  165764 Jun  2  2012 malgunn_boot.ttf*
-rwxr-xr-x  1 root root  134508 Jun  2  2012 meiryo_boot.ttf*
-rwxr-xr-x  1 root root  132888 Jun  2  2012 meiryon_boot.ttf*
-rwxr-xr-x  1 root root  154896 Jun  2  2012 msjh_boot.ttf*
-rwxr-xr-x  1 root root  152892 Jun  2  2012 msjhn_boot.ttf*
-rwxr-xr-x  1 root root  146228 Jun  2  2012 msyh_boot.ttf*
-rwxr-xr-x  1 root root  142124 Jun  2  2012 msyhn_boot.ttf*
-rwxr-xr-x  1 root root   36020 Jun  2  2012 segmono_boot.ttf*
-rwxr-xr-x  1 root root   77088 Jun  2  2012 segoen_slboot.ttf*
-rwxr-xr-x  1 root root   77404 Jun  2  2012 segoe_slboot.ttf*
-rwxr-xr-x  1 root root   47452 Jun  2  2012 wgl4_boot.ttf*

/boot/efi/EFI/Microsoft/Boot/fr-FR:
total 216
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 78576 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 78576 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45808 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/hr-HR:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/Microsoft/Boot/hu-HU:
total 216
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 78064 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 78064 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45808 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/it-IT:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/ja-JP:
total 188
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 67312 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 67312 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 42736 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/ko-KR:
total 188
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 66800 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 66800 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 42736 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/lt-LT:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 75504 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 75504 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/Microsoft/Boot/lv-LV:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 74992 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 74992 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/Microsoft/Boot/nb-NO:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 74992 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 74984 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45808 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/nl-NL:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 77552 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 77552 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/pl-PL:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 77552 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 77552 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45808 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/pt-BR:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/pt-PT:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45808 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/qps-ploc:
total 200
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 73456 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 73456 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/Resources:
total 36
drwxr-xr-x  4 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 18160 Jul 25 21:57 bootres.dll*
drwxr-xr-x  2 root root  4096 Dec 18 21:10 en-US/
drwxr-xr-x  2 root root  4096 Dec 18 21:10 fr-FR/

/boot/efi/EFI/Microsoft/Boot/Resources/en-US:
total 20
drwxr-xr-x 2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 4 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x 1 root root 11504 Jul 26 00:48 bootres.dll.mui*

/boot/efi/EFI/Microsoft/Boot/Resources/fr-FR:
total 20
drwxr-xr-x 2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 4 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x 1 root root 11504 Aug  3 13:03 bootres.dll.mui*

/boot/efi/EFI/Microsoft/Boot/ro-RO:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 75504 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 75504 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/Microsoft/Boot/ru-RU:
total 204
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 44784 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/sk-SK:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/Microsoft/Boot/sl-SI:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/Microsoft/Boot/sr-Latn-CS:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/Microsoft/Boot/sv-SE:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/tr-TR:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 74992 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 74992 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/uk-UA:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/Microsoft/Boot/zh-CN:
total 180
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 63728 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 63728 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 42224 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/zh-HK:
total 180
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 63728 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 63728 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 42224 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/Microsoft/Boot/zh-TW:
total 180
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 63728 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 63728 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 42224 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba:
total 12
drwxr-xr-x  3 root root 4096 Dec 18 21:10 ./
drwxr-xr-x  6 root root 4096 Dec 25 15:05 ../
drwxr-xr-x 39 root root 4096 Dec 18 21:10 Boot/

/boot/efi/EFI/toshiba/Boot:
total 4160
drwxr-xr-x 39 root root    4096 Dec 18 21:10 ./
drwxr-xr-x  3 root root    4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root   32768 Dec 18 21:11 BCD*
-rwxr-xr-x  1 root root   20480 Dec 18 21:10 BCD.LOG*
-rwxr-xr-x  1 root root       0 Dec 18 21:10 BCD.LOG1*
-rwxr-xr-x  1 root root       0 Dec 18 21:10 BCD.LOG2*
drwxr-xr-x  2 root root    4096 Dec 18 21:10 bg-BG/
-rwxr-xr-x  1 root root 1354480 Jul 25 21:57 bootmgfw.efi*
-rwxr-xr-x  1 root root 1350896 Jul 25 21:57 bootmgr.efi*
-rwxr-xr-x  1 root root   65536 Dec 18 21:10 BOOTSTAT.DAT*
-rwxr-xr-x  1 root root    4186 Jun 26  2012 boot.stl*
drwxr-xr-x  2 root root    4096 Dec 18 21:10 cs-CZ/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 da-DK/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 de-DE/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 el-GR/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 en-GB/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 en-US/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 es-ES/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 et-EE/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 fi-FI/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 Fonts/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 fr-FR/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 hr-HR/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 hu-HU/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 it-IT/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 ja-JP/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 ko-KR/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 lt-LT/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 lv-LV/
-rwxr-xr-x  1 root root 1263856 Jul 25 21:57 memtest.efi*
drwxr-xr-x  2 root root    4096 Dec 18 21:10 nb-NO/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 nl-NL/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 pl-PL/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 pt-BR/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 pt-PT/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 qps-ploc/
drwxr-xr-x  4 root root    4096 Dec 18 21:10 Resources/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 ro-RO/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 ru-RU/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 sk-SK/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 sl-SI/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 sr-Latn-CS/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 sv-SE/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 tr-TR/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 uk-UA/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 zh-CN/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 zh-HK/
drwxr-xr-x  2 root root    4096 Dec 18 21:10 zh-TW/

/boot/efi/EFI/toshiba/Boot/bg-BG:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 77040 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 77040 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/toshiba/Boot/cs-CZ:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/da-DK:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 75504 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 75504 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/de-DE:
total 216
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 78576 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 78576 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45808 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/el-GR:
total 216
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 79600 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 79600 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 46320 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/en-GB:
total 152
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 73456 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 73456 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/toshiba/Boot/en-US:
total 200
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 73456 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 73456 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/es-ES:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 77040 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 77040 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45808 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/et-EE:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 74480 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 74480 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/toshiba/Boot/fi-FI:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/Fonts:
total 13080
drwxr-xr-x  2 root root    4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root    4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 3694080 Jun  2  2012 chs_boot.ttf*
-rwxr-xr-x  1 root root 3876772 Jun  2  2012 cht_boot.ttf*
-rwxr-xr-x  1 root root 1984228 Jun  2  2012 jpn_boot.ttf*
-rwxr-xr-x  1 root root 2371360 Jun  2  2012 kor_boot.ttf*
-rwxr-xr-x  1 root root  168212 Jun  2  2012 malgun_boot.ttf*
-rwxr-xr-x  1 root root  165764 Jun  2  2012 malgunn_boot.ttf*
-rwxr-xr-x  1 root root  134508 Jun  2  2012 meiryo_boot.ttf*
-rwxr-xr-x  1 root root  132888 Jun  2  2012 meiryon_boot.ttf*
-rwxr-xr-x  1 root root  154896 Jun  2  2012 msjh_boot.ttf*
-rwxr-xr-x  1 root root  152892 Jun  2  2012 msjhn_boot.ttf*
-rwxr-xr-x  1 root root  146228 Jun  2  2012 msyh_boot.ttf*
-rwxr-xr-x  1 root root  142124 Jun  2  2012 msyhn_boot.ttf*
-rwxr-xr-x  1 root root   36020 Jun  2  2012 segmono_boot.ttf*
-rwxr-xr-x  1 root root   77088 Jun  2  2012 segoen_slboot.ttf*
-rwxr-xr-x  1 root root   77404 Jun  2  2012 segoe_slboot.ttf*
-rwxr-xr-x  1 root root   47452 Jun  2  2012 wgl4_boot.ttf*

/boot/efi/EFI/toshiba/Boot/fr-FR:
total 216
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 78576 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 78576 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45808 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/hr-HR:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/toshiba/Boot/hu-HU:
total 216
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 78064 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 78064 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45808 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/it-IT:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/ja-JP:
total 188
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 67312 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 67312 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 42736 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/ko-KR:
total 188
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 66800 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 66800 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 42736 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/lt-LT:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 75504 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 75504 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/toshiba/Boot/lv-LV:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 74992 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 74992 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/toshiba/Boot/nb-NO:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 74992 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 74984 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45808 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/nl-NL:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 77552 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 77552 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/pl-PL:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 77552 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 77552 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45808 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/pt-BR:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/pt-PT:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45808 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/qps-ploc:
total 200
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 73456 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 73456 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/Resources:
total 36
drwxr-xr-x  4 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 18160 Jul 25 21:57 bootres.dll*
drwxr-xr-x  2 root root  4096 Dec 18 21:10 en-US/
drwxr-xr-x  2 root root  4096 Dec 18 21:10 fr-FR/

/boot/efi/EFI/toshiba/Boot/Resources/en-US:
total 20
drwxr-xr-x 2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 4 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x 1 root root 11504 Jul 26 00:48 bootres.dll.mui*

/boot/efi/EFI/toshiba/Boot/Resources/fr-FR:
total 20
drwxr-xr-x 2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 4 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x 1 root root 11504 Aug  3 13:03 bootres.dll.mui*

/boot/efi/EFI/toshiba/Boot/ro-RO:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 75504 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 75504 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/toshiba/Boot/ru-RU:
total 204
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 44784 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/sk-SK:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/toshiba/Boot/sl-SI:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/toshiba/Boot/sr-Latn-CS:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/toshiba/Boot/sv-SE:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76016 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/tr-TR:
total 208
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 74992 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 74992 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 45296 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/uk-UA:
total 160
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 76528 Jul 25 21:56 bootmgr.efi.mui*

/boot/efi/EFI/toshiba/Boot/zh-CN:
total 180
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 63728 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 63728 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 42224 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/zh-HK:
total 180
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 63728 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 63728 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 42224 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/toshiba/Boot/zh-TW:
total 180
drwxr-xr-x  2 root root  4096 Dec 18 21:10 ./
drwxr-xr-x 39 root root  4096 Dec 18 21:10 ../
-rwxr-xr-x  1 root root 63728 Jul 25 21:56 bootmgfw.efi.mui*
-rwxr-xr-x  1 root root 63728 Jul 25 21:56 bootmgr.efi.mui*
-rwxr-xr-x  1 root root 42224 Jul 25 21:56 memtest.efi.mui*

/boot/efi/EFI/ubuntu:
total 128
drwxr-xr-x 2 root root   4096 Dec 25 15:05 ./
drwxr-xr-x 6 root root   4096 Dec 25 15:05 ../
-rwxr-xr-x 1 root root 122880 Dec 25 15:05 grubx64.efi*
                              I hope that answered every question you have about my system.
                              • Top
                              • Bottom

                              Comment

                                #75
                                I am actually in the process of trying to duplicate your setup on my spare PC. I completely blanked the hard drive and installed Windows 8, accepting only the defaults. Windows 8, of course, took the entire drive to itself. No problem. The results were four partitions:

                                1. 300 MB - NTFS - hidden recovery partition
                                2. 100 MB - FAT32 - EFI system partition
                                3. 128 MB - none - some kind of Microsoft reserved partition
                                4. 118 GB - NTFS - Windows 8, C:

                                Then I installed Kubuntu, accepting only the defaults. Kubuntu's partitioner in "guided" mode resized partition #4 to make space. The results were:

                                1-3. no change
                                4. 68 GB - NTFS - Windows 8, C:
                                5. 43 GB - ext4 - Linux /
                                6. 8 GB - swap - Linux swap

                                However, GRUB appears unable to detect Windows 8. I've seen other reports of this. I was able to manually overcome this and am now successfully dual booting.

                                I would like for you to try this. Ensure that Secure Boot is disabled -- I'm not going to let that get in our way. Open a Konsole. Then type
                                Code:
                                sudo nano /etc/grub.d/40_custom
                                At the bottom of this file add:
                                Code:
                                menuentry "Windows 8" {
  search --set=root --file /EFI/Microsoft/Boot/bootmgfw.efi
  chainloader /EFI/Microsoft/Boot/bootmgfw.efi
}
                                Press Ctrl+X to save and exit.

                                Now type
                                Code:
                                sudo nano /etc/default/grub
                                Find the two lines that begin with GRUB_HIDDEN and place a # in front of them. Press Ctrl+x to save and exit.

                                Now type
                                Code:
                                sudo update-grub
                                Reboot. Do you now have a "Windows 8" entry in GRUB? Will it boot? It might not, actually, because you have what looks like an erroneous entry in your UEFI boot variables. We can fix that next, if necessary.
                                • Top
                                • Bottom

                                Comment

                                Previous 1 2 3 4 5 6 7 8 template Next
                                Working...
                                X