Jump to content

Dell Latitude E6410 - no UEFI entry for Clover


PlutoDelic
 Share

18 posts in this topic

Recommended Posts

Hi lads,

 

I've managed to install mavericks with a usb and clover, with all the material in this thread, i am able to actually boot the successfully installed mavericks on it straight away, though my BIOS does not seem to find or create a string in the UEFI strings list (boot order), where as it detects the USB straight away.

 

i've tried a lot, trying to enter all the possible directories with both types of slashes, and none boots to the disc. I've checked the folder and file names just to avoid any confusion and typed them as they are, nothing!!!

 

What am i missing??? I am actually writing from the system and it works pretty well...

Link to comment
Share on other sites

The first thing is that you need to install Clover to EFI partition of your GPT disk. Meaning: mount EFI parttion in OSX and copy EFI/Clover folder from USB stick to EFI partition into EFI/Clover folder.

 

Then:

 

1. Standard procedure:

- reboot into Clover USB stick

- Clover will detect installation on GPT disk and you will have some menu in tools section (Clover boot options?) where you can select "Add as UERI boot option"

- this should add Clover as first entry in boot options

- then restart and Clover should start

- you can also check if Clover appears as boot option in BIOS/UEFI

 

But sometimes this does not work. Usually on laptops, which are ment to be used with Windows only and then have some kind of protection against having first boot option other then Windows. Then ...

 

2. bootx64.efi way

- mount EFI partition and copy /EFI/Clover/Cloverx64.efi to /EFI/BOOT/Bootx64.efi

- reboot and see if this will add that drive as UEFI boot option

 

And if this does not work, then ...

 

3. Clover masked as windows boot manager

- mount EFI partition

- if there is /efi/microsoft/boot/bootmgfw.efi (if UEFI windows is installed), then rename it to /efi/microsoft/boot/bootmgfw-orig.efi

- and copy /EFI/Clover/Cloverx64.efi to /efi/microsoft/boot/bootmgfw.efi

- reboot and see if this will add that drive as UEFI boot option

  • Like 1
Link to comment
Share on other sites

None of the methods work, had to install clover on ESP as usual but boot through legacy mode which seems to work, although i had to copy the clover settings from the one in the USB drive, nevertheless i updated clover just in case.

 

I kept on loosing Audio, so i install the VoodooHDA kext rather then leaving it injected in /EFI/Clover/kexts/10.9, this fixed the issue, but had to do it again since i updated to 10.9.5 (and boy i love it when a hackie can update like a mackie)

 

right now, i dont have VGA, and probably DP as well which i cant test right now, any idea how to fix them?

Link to comment
Share on other sites

You can do this:

1) copy cloverx64.efi to /efi/boot/bootx64.efi

2)rename bootmgfw.efi to bootmgfwA.efi

3)use clover configurator > Gui > add a new entry:

■ path: \efi\microsoft\boot\bootmgfwA.efi

■ Name : you name it whatever you want

■ Type : Windows

Save and reboot ;)

Link to comment
Share on other sites

  • 4 weeks later...

I'm curious how you set up the install USB, since the guide was built for myHack.  Did you install it using myHack or Clover?  I've got a functioning myHack/Chameleon booted Mavericks system but I want to try and switch to Clover and upgrade to Yosemite.(which I'm using for my desktop).  I'm tempted to try and take the kext files from the Extra/Extensions folder from the myHack guide and inject them using Clover, but I'm worried that will cause kernel panics if there are OEM kexts that need to be deleted.

Link to comment
Share on other sites

Sorry for the uber-delay.

 

I went all Clover stock. Made a USB Installer, put clover on it, gathered necessary kexts and dsdt from the osxlatitude guys.

 

I am on 10.10 right now, everything working except sleep, there is an unreliable battery and sd card, but most of the necessary stuff work. Even VGA and DisplayPort work, though you may need to FN + F8 before OS X boots, otherwise doing it during system crashes it.

 

for UEFI, i have found a hidden boot manager in dells, which outputs a lot of more information then the GUI BIOS and actually detects EFI files :). just as POST finishes, start pressing the Left Arrow Key, and you should enter a Menu similar to an old looking bios. However, so far, i have not managed to make it UEFI bootable.

 

I highly recommend you clover, from my 6 years into building, helping, troubleshooting hackies, i have never found a better way and idea then clover.

Link to comment
Share on other sites

  • 3 months later...

i think i got sleep to work once with chameleon as the error showed cannot wake from Secure Image.

 

still working on how to fix intel HD arrandale 1st gen video in dsdt and FrameBuffer.

 

soon ill try clover

 

 

had 10.9.4 working fine no sleep .. but its pointing to the power management of intel HD and possibly LPT /COM and docking + OSID if less than 0x20 (vista) it returns generic rather if win7 returns different (VID) 0x20000 or 0x800000 Address and status in DSDT

 

the DP and DP2  and DVI in is in  _DOD and  has too many entries.. VGA is not supported..

Link to comment
Share on other sites

  • 1 month later...

I managed to get a lot of things working, Dual Display with VGA and DP, but Sleep and UEFI remain a treasure.

 

I think you've managed to get sleep working from the Intel version, i have the nVidia NVS 3100M GPU so that is the sole reason of lack of sleep function.

 

Anyhow, you can find my input Here

Link to comment
Share on other sites

  • 3 weeks later...

I screwed up my Clover lately, just to find out that Clover ISO's are available in case your left with windows.

 

I ended up wiping a GPT USB into an MBR (windows :() and flashed the ISO, just to find out, UEFI detects it. I tried "dd"-ing the iso on the EFI of a GPT drive, unsuccessful. What is happening here? what point would there be to do UEFI but no GPT?

Link to comment
Share on other sites

@PlutoDelic,

 

Have you set the fast boot option in your BIOS to auto or thorough instead of minimal?

 

USB install media for UEFI installations can be MBR formatted as long as they have a FAT32 boot partition.  See the AIO guide: Installing Yosemite using Clover (UEFI).

 

Also have a look at

 

You might be able to manipulate your UEFI boot entries in Windows using the EasyUEFI tool.

Link to comment
Share on other sites

Thanks for that Fusion, my fast boot options is to thorough, i've read something about that before. I am going to try the resources, but i do hope i dont have to do an MBR disk in the hard drive, that doesnt suit my needs at all, GPT has been a life saver for me.

 

I know pretty well that on a GPT layout, the EFI partition is FAT32, i even went further and made sure i reformat it to FAT32, but none of these scenarios gave me a bootable GPT at UEFI :(.

 

Will report back shortly...

 

Thanks again mate.

Link to comment
Share on other sites

It seems GPT is not the problem after all. Since the above AIO guide for UEFI mimics the EFI environment in MBR, i did the same thing in a GPT partitioned USB drive.

 

Initially, i tried the classic way and copied Clover to original EFI partition in the USB, with no success. Then i thought i'd do the same just like in the MBR scenario, create another partition that mimics EFI, guess what, it works, it's detected.

 

I know the problem is the UEFI implementation from Dell, and even the EFI partition is not really counted as a partition in Disk Utility, but of course in command line it is a different question. So how come the real EFI is not being detected?

 

Here's the GPT layout...

/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *15.9 GB    disk2
   1:       Microsoft Basic Data EFI                     209.7 MB   disk2s1 (wont boot here)
   2:       Microsoft Basic Data CLOVER                  299.9 MB   disk2s2 (boots here)
   3:                  Apple_HFS USB                     15.3 GB    disk2s3

I think due to the partition size, they are formatted in FAT16 and not FAT32, so that is not the case either.

I can only point at something that handles the EFI drive differently, and what could that be?

Link to comment
Share on other sites

@PlutoDelic,

 

It looks like you have a corrupted EFI partition....instead of "Microsoft Basic Data", a real EFI partition should show as "EFI" under the partition TYPE column when you run "diskutil list".

 

I recommend you download and run GPT FDisk/"GDisk" to fix the partition type code and attributes - see my post#359 part III  in the AIO guides.  Gdisk can also verify your disk for other GPT errors (option v).

 

PS:  The EFI partition is FAT32 not FAT16.  When you create a GUID disk with OSX Disk Utility, it automatically creates a valid 200MB FAT32 EFI partition....maybe you corrupted the EFI partition by formatting it with some other program?

 

Edit 04/17/15

Glad you got it working. 

 

Maybe the problem is that your system is only happy with a single hard disk EFI partition...just give boot priority to disk 1 and boot Clover from its EFI ---> load either UEFI Windows or OSX.  As they say, if its working, don't fix it :).

Link to comment
Share on other sites

This may be just my machine, but Disk Utility reports FAT16, and i have the debug stuff enabled. Remember, i have done this whole partitioning all in OS X/Disk Utility, but i just tried DiskMakerX and noticed it reports it as FAT32. Even "diskutil list" now reports EFI as it should.

/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *15.9 GB    disk2
   1:                        EFI EFI                     209.7 MB   disk2s1
   2:                  Apple_HFS Yosemite Install Dis... 15.6 GB    disk2s2

But it didnt work, no boot success. Fusion it definitely seems that DELL just screwed up, this notebook must be one of the first that implemented UEFI from them. It seems it will be a race for a workaround rather then a solution.

 

I am trying GPT fdisk in a bit, and thanks a lot for your support fusion71au, you have been immensely helpful mate :).

 

EDIT: GDisk reports MBR Protective and GPT Present, i think thats the optimal GPT scenario, i just cant figure this out :(.

 

EDIT2: i've researched a bit on how to remove EFI completely, and whatever deletion one does, Disk Utility will add the EFI again no matter how many partitions you plan to add after. So i've deleted the whole GPT-ed drive, including the EFI, booted into a live Ubuntu, used GParted to create a FAT32 500MB partition at the beginning where the original EFI was. To my surprise, it was not bootable/detected. 

/dev/disk2
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *15.9 GB    disk2
   1:       Microsoft Basic Data EFI                     536.9 MB   disk2s1
   2:                  Apple_HFS OS X Base System        15.3 GB    disk2s2

Whatever i do, i just cant seem to reverse engineer this issue.

Link to comment
Share on other sites

Well well well, the more i dig, the weirder the issue becomes.

 

After getting the UEFI USB to show up, i installed Yosemite, all well. Copied clover just in case in EFI, no results, but fortunately i also created a FAT32 300MB partition just after the EFI, precisely the same procedure as in the USB.

 

Well, it didn't work, no sign of UEFI detection, no sign of booting while adding EFI entries (even though it sees the DISK when trying to add).

 

Pissed off as i was, i had the idea to use the EFI of my freshly UEFI Installed Windows 10, copied Clover right next to the Microsoft one (only the Clover folder), added the entry...AND IT WORKED!!! that got me even more pissed, there is nothing more painful than doing something right and having no idea why it's working.

 

So i started comparing the EFI of my OS X Installation, which is standard GPT with EFI at the beginning and with the one from the Windows implementation (mind you, both disks are GPT) and boy am i being thrown with stuff...look at this, notice the EFI location:

/dev/disk0
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *500.1 GB   disk0
   1:                        EFI EFI                     209.7 MB   disk0s1
   2:       Microsoft Basic Data CLO                     314.6 MB   disk0s2
   3:                  Apple_HFS Yose                    99.1 GB    disk0s3
   4:                 Apple_Boot Recovery HD             650.0 MB   disk0s4
   5:                  Apple_HFS Data                    399.7 GB   disk0s5
/dev/disk1
   #:                       TYPE NAME                    SIZE       IDENTIFIER
   0:      GUID_partition_scheme                        *320.1 GB   disk1
   1: DE94BBA4-06D1-4D40-A16A-BFD50179D6AC               314.6 MB   disk1s1
   2:                        EFI NO NAME                 104.9 MB   disk1s2
   3:         Microsoft Reserved                         134.2 MB   disk1s3
   4:       Microsoft Basic Data Windows10               107.9 GB   disk1s4
   5:       Microsoft Basic Data WinData                 211.6 GB   disk1s5

I am not surprised that the Dell's UEFI adapted to Microsoft, but this does not look standard to me from Mi$crosoft, what are they doing here?

 

DISK 0 is obviously OS X, with EFI at the beginning of the disk (ignore the CLO partition, i was trying to get Clover there like in the USB).

 

DISK 1 has 3 partitions in the beginning, the first one i read is an MRP (Microsoft Recovery Partition), the second is the EFI (?????) and the third is is an MSR (Microsoft Reserved Partition). All the apps that mounted that EFI in OS X reported unknown identifier stuff, but i could copy Clover there.

 

Why the hell is this so weird? Why does it work to begin with?

Link to comment
Share on other sites

 Share

×
×
  • Create New...