Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30,171 posts in this topic

Recommended Posts

jamiethemorris
jamiethemorris
Posted
Posted

Thanks for the responses guys. Unfortunately my Z77-DS3H Bios has no CSM or GOP options that I can see. I guess I am stuck then. It is odd that it doesn't work with such a common display as the ACD. I would have thought a lot of people here would have encountered the problem, but I can't find any fixes on the forums anywhere...

The settings you are looking for are under BIOS Features:

-Windows 8 Features: Set to Windows 8 WHQL

-CSM Support: Disabled

-Boot mode selection: UEFI Only

If your BIOS does not have these features, see if the latest beta BIOS has them.

 

You also need to have a UEFI vbios (A.K.A. GOP as it is referred to for graphics cards) for your card. AFAIK EVGA does not have these avaiable for download on their website, but according to this, if you send them a request at support@evga.com they will send you the UEFI firmware.

 

 

If you can't get a hold of the proper UEFI BIOS for your mobo or graphics card, see if you can patch the vbios manually with NiBiTor and either load it or flash it. This has worked for me on AMD/ATI cards, I can't speak for if it works for Nvidia though. More information on how to add your resolution can be found here.

 

Hope that helps.

  • Like 1
Link to comment
Share on other sites
Stefan Milev
Stefan Milev
Posted
Posted

You also need to have a UEFI vbios (A.K.A. GOP as it is referred to for graphics cards) for your card. AFAIK EVGA does not have these avaiable for download on their website, but according to this, if you send them a request at support@evga.com they will send you the UEFI firmware.

 

 

Hope that helps.

 

It did help to me. Thats what I did an hour ago and solved full resolution in Clover on boot. 

 

Thanks for the tip. 

  • Like 1
Link to comment
Share on other sites
jamiethemorris
jamiethemorris
Posted
Posted

Yeah, that worked awesome on my 6850. No Nvidia support yet though.

Link to comment
Share on other sites
barren
barren
Posted
Posted

Hi,

 

I have a Samsung XP941 NGFF SSD on a PCI-E adaptor card. Clover boots fine both from UEFI and BIOS based boot USB. However only BIOS based boot can see the SSD. I can't get clover to see the SSD in UEFI mode. BIOS is set to WINDOWS 8 and I've tried CSM support on and off.

 

I installed Mavericks on the SSD via BIOS based boot and then reformatted the SSD EFI partition to FAT 32. 

 

If I boot a USB via BIOS based then Mavericks partition shows up in Clover

If I boot UEFI then clover doesn't see it.

 

Any help would be greatly appreciated.

 

Darwin dump attached

DarwinDumper_2.9.6_Clover_X64_2850_Mav_tomely.zip

prebootUEFI.txt

prebootBIOS.txt

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

Hi,

 

I have a Samsung XP941 NGFF SSD on a PCI-E adaptor card. Clover boots fine both from UEFI and BIOS based boot USB. However only BIOS based boot can see the SSD. I can't get clover to see the SSD in UEFI mode. BIOS is set to WINDOWS 8 and I've tried CSM support on and off.

 

I installed Mavericks on the SSD via BIOS based boot and then reformatted the SSD EFI partition to FAT 32. 

 

If I boot a USB via BIOS based then Mavericks partition shows up in Clover

If I boot UEFI then clover doesn't see it.

 

Any help would be greatly appreciated.

 

Darwin dump attached

See you. Thanks for the detailed report.

As I see in the case of UEFI boot Clover see no SATA devices at all. While with CloverEFI it does.

I have to explain the differencies.

A set of Sata drivers located in EFI implementation. There are two cases:

1. CloverEFI implementation (BIOS based boot)

2. UEFI implementation by American Megatrend. 

So the question. Why AMI UEFI doesn't see SATA devices?

Second question. What can we add to help it?

 

I may propose you to start Clover in UEFI mode when NO USB STICK INSERTED.

Thus EFI folder must be located in HDD (or SSD).

 

Otherwise if you can start CloverGUI and then start Shell.efi then you can dump Devices, Drivers, DH and many other things to investigate what is happen.

Link to comment
Share on other sites
dmazar
dmazar
Posted
Posted

It's additional PCI card and requires UEFI driver to work. I guess the driver is already on the card as option ROM, but maybe it is not enabled in BIOS. There should be some options like CSM Support, Boot Mode Selection, Storage Boot Option Control or similar.

Link to comment
Share on other sites
barren
barren
Posted
Posted

 

I may propose you to start Clover in UEFI mode when NO USB STICK INSERTED.

Thus EFI folder must be located in HDD (or SSD).

 

Otherwise if you can start CloverGUI and then start Shell.efi then you can dump Devices, Drivers, DH and many other things to investigate what is happen.

 

 

 

I installed Clover on the FAT32 formatted EFI partition of the SSD:

 

Booted UEFI with/without CSD Boot rom Options

SATA device set to RAID

 

: No Boot Device found

 

Meanwhile here are Dumps from CloverUEFI EFIShell..

 

I emailed Gigabyte they said that Windows 8 should boot from this drive on this board with the current BIOS settings , So I wonder if its worth installing Windows 8 on a partition of the SSD to see if its boot manager will be picked up on UEFI boot..

 

 

 

 

you could try the nvmexpress drivers in edk2.

 

I'm not sure how I would deploy the NvmExpressDxe.inf driver, are you able to shine any light on how to do this?

pci.txt

dmpstor.txt

memmap.txt

dh.txt

post-659758-0-40858200-1409918353_thumb.png

post-659758-0-12857700-1409918362_thumb.png

Link to comment
Share on other sites
barren
barren
Posted
Posted

Copy /EFI/CLOVER/CLOVERX64.efi to

/EFI/BOOT/BOOTX64.efi

 

Thanks for the suggestions! 

 

Tried this using terminal to move and rename files, still getting flashing cursor, then: "Warning No bootable device is detected. System will enter the BIOS Setup Utility"

 

 

Here's a compiled version of NvmExpressDxe.efi.

 

(unpack the zip first)

 

load it via the shell and do map -r

 

rgds

 

Thanks for this. Added to UEFI64Drivers on a USB key: the SSD doesn't show up. If I manually load in UEFI Shell: Black screen/crash

 

Attached pre boot with NvmExpressDxe.efi driver loaded

preboot.txt

Link to comment
Share on other sites
ruki250
ruki250
Posted
Posted

error in clover compiler:

No nasm binary found in toolchain directory !
Build it with the buidnasm.sh script.
Cloverx64 release  ERROR!!

 

error in clover compiler:

No nasm binary found in toolchain directory !
Build it with the buidnasm.sh script.
Cloverx64 release  ERROR!!

 

ok solved by manual installation of nasm binary...........

Link to comment
Share on other sites
magnifico
magnifico
Posted
Posted

Thanks for the suggestions! 

 

Tried this using terminal to move and rename files, still getting flashing cursor, then: "Warning No bootable device is detected. System will enter the BIOS Setup Utility"

 

 

Thanks for this. Added to UEFI64Drivers on a USB key: the SSD doesn't show up. If I manually load in UEFI Shell: Black screen/crash

 

Attached pre boot with NvmExpressDxe.efi driver loaded

man..wich pci card have you?

Link to comment
Share on other sites
barren
barren
Posted
Posted

man..wich pci card have you?

 
its a
 
LYCOM DT-120 
PCIe 3.0 x4 Host Adapter for M.2 NGFF PCIe SSD installed in Main Board
 
 
Heres some more info I grabbed from RW-Everything:
 
Bus 01, Device 00, Function 00 - sanyo AHCI Controller (PCIE)
 ID=A800144D, SID=A811144D, Int Pin=INTA, IRQ=10
 MEM=DEDFE000  IO=None

SSD Controller info1.txt

Link to comment
Share on other sites
Slice
Slice
Posted
Posted

 

 
its a
 
LYCOM DT-120 
PCIe 3.0 x4 Host Adapter for M.2 NGFF PCIe SSD installed in Main Board
 
 
Heres some more info I grabbed from RW-Everything:
 
Bus 01, Device 00, Function 00 - sanyo AHCI Controller (PCIE)
 ID=A800144D, SID=A811144D, Int Pin=INTA, IRQ=10
 MEM=DEDFE000  IO=None

 

As I see this is device of class 010601 = SATA Controller. So why CloverEFI works as well as for any other SATA controllers.

Just wonder why AMI UEFI can't works with it.

NvmExpress has no relation to this case.

Link to comment
Share on other sites
magnifico
magnifico
Posted
Posted

its a

 

LYCOM DT-120 

PCIe 3.0 x4 Host Adapter for M.2 NGFF PCIe SSD installed in Main Board

 

http://www.lycom.com.tw/DT-120.htm

 

Heres some more info I grabbed from RW-Everything:

 

Bus 01, Device 00, Function 00 - sanyo AHCI Controller (PCIE)

 ID=A800144D, SID=A811144D, Int Pin=INTA, IRQ=10

 MEM=DEDFE000  IO=None

but why not ask for advice before buying, this is not mac compatible, there are no drivers for this.

Link to comment
Share on other sites
barren
barren
Posted
Posted

but why not ask for advice before buying, this is not mac compatible, there are no drivers for this.

 

 

http://forums.macrumors.com/showthread.php?t=1685821

 

"Base Mac Pro Test Platform:

  • 2009 Mac Pro, Intel x58 based platform
  • Intel 990x CPU, 6-core, 3.46Ghz
  • 32GB 1066 RAM.
  • nvidia 680GTX 2GB(slot 1)
  • Lycom 4x NGFF PCI 3.0 adapter (slot 2)
  • Apricorn Velocity X2 - slot 3 & 4

Initial Results

The SSD appears as a Boot device, OS X installed without a problem."

 

 

http://www.barefeats.com/hard183.html

 

"We tested with both the Bplus and Lycom M.2 (NGFF) -> PCIe Adapters. There was no difference in the transfer speeds."

Link to comment
Share on other sites
barren
barren
Posted
Posted

Interesting quote from AnandTech Review:

 

OS Installation

A topic that has arisen on forums since the launch is whether the M.2 drives can be used as boot drives. For UEFI installation, the detection algorithm in the firmware has to be active to see the drive at the install prompt, however for Legacy installation the drive needs to implement its own firmware at POST. As the XP941 does not have initialization drivers, my Legacy Windows 7 install that I normally do for reviews, while it saw the drive at the OS installation screen, it was unable to hook the drive in to install. This is for both the M.2 x2 and M.2 x4 slots on the ASRock motherboard. Placing the drive into an ASUS motherboard showed no drive at all for Legacy installation, however Kristian has been in contact and confirmed that they are working on enabling UEFI installation for M.2 in a future BIOS update, as should all the manufacturers be if they have not already.

When the motherboard manufacturers have updated UEFIs, the following table should be relevant:

                                                     

                                                           Legacy OS Install         UEFI OS Install

 

M.2 without M.2 POST Firmware
(e.g. Samsung XP941)                            No                               Yes

 

M.2 with M.2 POST Firmware
(e.g. Plextor M6e)                                   Yes                               Yes

 

So perhaps AMI UEFI needs an update from Gigabyte..

Link to comment
Share on other sites
magnifico
magnifico
Posted
Posted

still do not have time to install osx on my new build, asrock Z97 extreme 6 + xp samsung 941, I'm waiting I get the ati 270x r9 .... just have a day off, headlight 'this installation, but what you I can say that asrock see the samsung in ahci , then I should not find problems.

 

Regard

Link to comment
Share on other sites
ericChng
ericChng
Posted
Posted

still do not have time to install osx on my new build, asrock Z97 extreme 6 + xp samsung 941, I'm waiting I get the ati 270x r9 .... just have a day off, headlight 'this installation, but what you I can say that asrock see the samsung in ahci , then I should not find problems.

 

Reg

 

Look forward to the fun when you start to build it.

Link to comment
Share on other sites
the_gael
the_gael
Posted
Posted (edited)

I have just run into an issue with boot timeout not working and wonder if there is something else that can override what I set in my config.plist.

 

I used the tool for applying a theme in Clover Configurator and I suspect that the issue cropped up as a result of doing that.

 

Anyway what I am faced with now is that the config.plist on my machine has the timeout specified but when I boot I have to manually press return to boot.

 

<key>Boot</key>
<dict>
<key>CustomLogo</key>
<string>None</string>
<key>DefaultVolume</key>
<string>Macintosh HD</string>
<key>Legacy</key>
<string>PBR</string>
<key>Log</key>
<false/>
<key>Secure</key>
<false/>
<key>Timeout</key>
<integer>2</integer>
<key>XMPDetection</key>
<string>Yes</string>
</dict>
 
 
What could be overriding this setting?
 
EDITED TO ADD - Resolved. 
I could not understand why everything appeared to be setup correctly and this did not work I looked at the debug log and the timeout was definitely being set. So I looked to see what else could be causing the issue. I guess I was looking for a technical reason why it did not work but then after looking at a Backup of the drive I realised that the volume name had changed - how I did it I don't know but the "t" in Macintosh was missing - looking back through the backups the issue started when the name changed. So as Clover could not find the default volume it was not applying the timeout. With the name restored all works again :-) 
Edited by the_gael
  • Like 1
Link to comment
Share on other sites
 Share
Go to topic listing
×
×
  • Create New...