Clover General discussion

[Lucy183]

And with the USB drive, you also get stuck at "scanning devices..."? Cause in this case, it's not the HDD (since you don't boot Clover from it, but from the USB), and it's not Clover either, since the same Clover got you into the OS the first time, enough to switch ON/OFF FileVault...

 

Can you enter Clover UI without the HDD (from the USB drive)? As in... physically disconnected.

Yeah I can boot without the hdd.

I solved, thanks for your time, here is what I do:

I take hdd from laptop and put in my other hack when mac os is loaded(thanks to sata hotplug feature)

Then I run first aid on the mac partition from hdd and then I was able to boot clover with hdd installed.

Now I put hdd back in my laptop and decryption is continuing.

Sorry for off topic

 

Sent from my HTC One M9 using Tapatalk

[arsradu]

Yeah I can boot without the hdd.

I solved, thanks for your time, here is what I do:

I take hdd from laptop and put in my other hack when mac os is loaded(thanks to sata hotplug feature)

Then I run first aid on the mac partition from hdd and then I was able to boot clover with hdd installed.

Now I put hdd back in my laptop and decryption is continuing.

Sorry for off topic

 

Sent from my HTC One M9 using Tapatalk

 

Well, then that's the problem. It wasn't done yet.  Maybe... 

 

And as for the SATA hotplug feature, that's exactly what I was planning to exploit in an attempt to reinstall the OS from the USB.

 

Well, glad you fixed this one too.

[pkdesign]

What can I say, I'm a hoarder lol. I like to make sure I have backups :-)))

Yay gimme prize or title

Clover Collector

 

Sent from my SM-G930F using Tapatalk

Ha! I have even more than that!

Thanks but I solved my problem in another way, I injected EDID and checked PatchVBios and now I have full hd resolution at boot.

I have another problem but I don't think it's the right thread for it: The Built-in Display is detected as Projector.

I have never been able to get full resolution at boot no matter what I do. I tried injecting EDID and PatchVBios but it doesn’t work. I tried putting the Video ROM in the correct folder but that does nothing.

 

Do you mind me asking how you pulled your EDID?

[Lucy183]

Ha! I have even more than that!

 

I have never been able to get full resolution at boot no matter what I do. I tried injecting EDID and PatchVBios but it doesn’t work. I tried putting the Video ROM in the correct folder but that does nothing.

 

Do you mind me asking how you pulled your EDID?

From windows, but it's possible from Mac too, are much tutorial on the internet for this.

 

Sent from my HTC One M9 using Tapatalk

[CoBrA2168]

I'm not sure if this is a clover issue, but I believe it might be:

El Capitan 2017-003 Security Update for 10.11.6 has caused issues booting on one of my machines (others are starting to report this issue too). For me, I get stuck at the OsxAptioFixDrv screen (before loading OS X). For others, it restarts in an infinite loop. For me it just hangs.

 

Would this have something to do with the Clover configuration? I was on r4061 and I updated to the latest stable, still having those issues. Any help would be appreciated. Thanks.

[bronxteck]

if your using optiofix try optiofix2 or vice versa from clover installer option

[CoBrA2168]

if your using optiofix try optiofix2 or vice versa from clover installer option

Yep, I already tried that without any luck. It might have something specific with my hardware. Running an i5-4200u with HD4400 graphics.

[arsradu]

Ha! I have even more than that!

I have never been able to get full resolution at boot no matter what I do. I tried injecting EDID and PatchVBios but it doesn’t work. I tried putting the Video ROM in the correct folder but that does nothing.

 

Do you mind me asking how you pulled your EDID?

 

You can use Darwin Dumper to extract the EDID. One of the best tools I've ever used.

 

For as far as I know, Clover already detects and injects EDID by default. I could be wrong though...

 

But anyway, you do have the option to use your own, if you so desire. And Darwin Dumper is, in my opinion, the easiest way to get it on MacOS.

 

By the way, if the card in your signature is the one you want to use for this case, there might be another way to do it:

 

1. UEFI GOP VBIOS (if you don't already have it). Basically the video card's ROM (you can request it on manufacturer's forums, usually). You can check if you already have a "UEFI" ROM using GPU-Z on Windows (I'm not aware of a Mac tool that can do that, but there probably are).

2. Disable Windows CSM (Compatibility Support Module) in BIOS. You don't need it, unless you're planning on putting XP on that machine. Which... I don't know why would anyone want to do, but yeah, for newer versions of Windows, you certainly don't need it.

 

That should bring you full native resolution in preboot.

[apianti]

@LuCyr04,

 

Which filesystem drivers do you have? If you enable filevault but don't have HFSPlus.efi from Apple firmware then will get stuck trying to access the partition.

 

@pkdesign,

 

I have two different settings in the firmware setup menu, CSM and Option ROM preference. If CSM is enabled, the other option allows to select the preference of legacy or UEFI option ROM for devices. However, no matter what if I enable CSM then my resolution is limited to 1024x768 and 800x600. If CSM is disabled I get full range of resolutions.

[chris1111]

 

If CSM is disabled I get full range of resolutions.

Thank you thats Solved my Boot resolution issue 

[apianti]

Thank you thats Solved my Boot resolution issue 

 

Ah, yes, I should point out that you should probably make sure your GPU has a UEFI capable option ROM first, otherwise, you'll have no graphics and need to reset your firmware NVRAM from the motherboard hardware (if the motherboard has such a feature - a laptop likely does not).

[chris1111]

Ah, yes, I should point out that you should probably make sure your GPU has a UEFI capable option ROM first, otherwise, you'll have no graphics and need to reset your firmware NVRAM from the motherboard hardware (if the motherboard has such a feature - a laptop likely does not).

No probleme for Graphics, its verry good now at boot screen, my icons are all perfectly uniform

Do you remember how to recover the Windows 10 Logo at boot, I Lost , just have the spinning wheel

[Slice]

Ha! I have even more than that!

I have never been able to get full resolution at boot no matter what I do. I tried injecting EDID and PatchVBios but it doesn’t work. I tried putting the Video ROM in the correct folder but that does nothing.

 

Do you mind me asking how you pulled your EDID?

Even if you already know how to use Clover to set big resolution your nvidia card is limited to this list

static TABLE_0 nvda_res[RESOLUTIONS_NUMBER] = {
  {1280,  720},
  {1280,  800},
  {1360,  768},
  {1400, 1050},
  {1440,  900},
  {1600,  900},
  {1600, 1200},
  {1680, 1050},
  {1920, 1080},
  {1920, 1200},
  {2048, 1536}
};

Sorry, PatchVBios for Nvidia limited to this list.

[Matgen84]

No probleme for Graphics, its verry good now at boot screen, my icons are all perfectly uniform

Do you remember how to recover the Windows 10 Logo at boot, I Lost , just have the spinning wheel

 

Hi Chris

 

For windows boot logo at start, If your system is booting in legacy mode - you get Windows Logo

If your system in booting in UEFI mode - you get OEM logo

 

On my system, I've just Asus logo (my motherboard) with the spinning wheel

 

But if you want to custom logo: you can try this, https://github.com/Metabolix/HackBGRT/releases. Or using Windows ICD: https://msdn.microsoft.com/en-us/library/windows/hardware/mt683761(v=vs.85).aspx

[cecekpawon]

Hi Chris

 

For windows boot logo at start, If your system is booting in legacy mode - you get Windows Logo

If your system in booting in UEFI mode - you get OEM logo

 

On my system, I've just Asus logo (my motherboard) with the spinning wheel

 

But if you want to custom logo: you can try this, https://github.com/Metabolix/HackBGRT/releases. Or using Windows ICD: https://msdn.microsoft.com/en-us/library/windows/hardware/mt683761(v=vs.85).aspx

 

Try to disable fast boot logo display to get windows logo instead of oem & still uefi.

Edited July 22, 2017 by cecekpawon

[Badruzeus]

Even if you already know how to use Clover to set big resolution your nvidia card is limited to this list

static TABLE_0 nvda_res[RESOLUTIONS_NUMBER] = {
  ...
  {1360,  768},
  ...
};

Sorry, PatchVBios for Nvidia limited to this list.

Agree, also happened on Linux with Grub2 as well. Can't get proper native resolution on boot screen, so under Clover GUI set to 1360x768 w/o PatchVBios is enough for me. (Nvidia: Legacy)

 

 

2:747  0:000  === [ InitScreen ] ========================================
2:747  0:000  SetScreenResolution: 1360x768 - setting Mode 3
2:747  0:000  BV new mode: 3 1360x768
3:037  0:290  Video mode change to mode #3: Success
3:102  0:064  Console modes reported: 4, available modes:
3:102  0:000   - [01]: 80x25
3:102  0:000   - [03]: 100x31
3:102  0:000   - [04]: 170x40 (current mode)
3:102  0:000  SetScreenResolution: 1360x768 - already set 

 

 

[cecekpawon]

0x3E7 disables more protections than 0x67. (Sorry unfortunately I can't tell what the exact items are right now.)

Sist I have modified crstat here to be more csrutil like.. included binary to test.

 

Is anyone had graphic mode with apple logo while booting with active nvram boot-args "-v" & edit/delete it from Clover GUI supposed not to boot in verbose mode? Mine is just black. Starting boot.efi with StartEFILoadedImage + LoadOptions doesnt take effect? Thanks

[Sherlocks]

Agree, also happened on Linux with Grub2 as well. Can't get proper native resolution on boot screen, so under Clover GUI set to 1360x768 w/o PatchVBios is enough for me. (Nvidia: Legacy)

 

 

2:747  0:000  === [ InitScreen ] ========================================
2:747  0:000  SetScreenResolution: 1360x768 - setting Mode 3
2:747  0:000  BV new mode: 3 1360x768
3:037  0:290  Video mode change to mode #3: Success
3:102  0:064  Console modes reported: 4, available modes:
3:102  0:000   - [01]: 80x25
3:102  0:000   - [03]: 100x31
3:102  0:000   - [04]: 170x40 (current mode)
3:102  0:000  SetScreenResolution: 1360x768 - already set

I first see 1360x768. Is it correct 1366x768?

 

나의 LG-F800S 의 Tapatalk에서 보냄

[Badruzeus]

I first see 1360x768. Is it correct 1366x768?

Yup, 1360~ is near native reso for my Display with Nvidia. If using 1366~ I only get 1024~ (same results by using AutoDetect, PatchVBios does nothing on my case) as @Slice has said above. Below is my output if using 1366x768 on Clover GUI:

bootlog.NVDA-1366.txt

[chris1111]

Hi Chris

 

For windows boot logo at start, If your system is booting in legacy mode - you get Windows Logo

If your system in booting in UEFI mode - you get OEM logo

 

On my system, I've just Asus logo (my motherboard) with the spinning wheel

 

But if you want to custom logo: you can try this, https://github.com/Metabolix/HackBGRT/releases. Or using Windows ICD: https://msdn.microsoft.com/en-us/library/windows/hardware/mt683761(v=vs.85).aspx

I have two windows 10 UEFI in fact, on my PC the logo is present but on my laptop not 

I reinstalling Windows 10 UEFI in my laptop and now the Logo is the HP Logo  

Now is Updated in Progress 

[Gigamaxx]

Hey,

 

found maybe some new investigation regarding AMD no sleep problem.

 

Seems that the Intel HD Framebuffer only is required, so the intel gfx device is not detected, but the framebuffer (in my case azul) is loaded. The sleep then still works, so it seems that the azul / capri framebuffer kext alone are responsible for a working sleep mode for AMD gfx?

 

edit: I forgot to mention that sleep does not work, if you also remove the Intel framebuffer... so is it right to assume that the AMD gfx bios initialization theory is wrong, but instead there is some code in that framebuffer which makes sleepmode working for amd?

 

AMD sleep wake needs IGPU and connection to monitor.    If no monitor is connected to IGPU no Wake.    

 

I have been toying with a i3 7350K and have had issues getting HD 630 to work.   I used fake ID 0x19120001 for Skylake ( its J=Kaby Lake) and got some interesting results.    Mork may have encountered this before.    The PCI slot says 1 lane in About this Mac.

 

  

 

This is with IGPU partially supported.

 

Ioreg. RX 480 no igpu.zip

[artur_pt]

I have two windows 10 UEFI in fact, on my PC the logo is present but on my laptop not 

I reinstalling Windows 10 UEFI in my laptop and now the Logo is the HP Logo  

Now is Updated in Progress 

 

 

hello

 

the boot is the same

 

boot.efi

 

from Mac OS x

 

only thing is diff

 

is the efi.drivers

 

maybe not the same ... uefi and legacy boot

 

is a no sense telling someone boot in legacy with a efi bios ..

 

i see this many times here in this topic

 

good hack

[chris1111]

hello

 

the boot is the same

 

boot.efi

 

from Mac OS x

 

only thing is diff

 

is the efi.drivers

 

maybe not the same ... uefi and legacy boot

 

is a no sense telling someone boot in legacy with a efi bios ..

 

i see this many times here in this topic

 

good hack

Yes its correct

my HP Bios as

Legacy boot

CSM/UEFI or UEFI Only

 

Now all is good with UEFI Only

 

EDIT***

But UEFI native no CSM the verbose boot is deform , when the second stage boot apear the screen is perfect 

So I am return to CSM /UEFI, I need my verbose boot some times.

[oSxFr33k]

OsxAptioFixDrv64 from back around page 492, was there a fix for version 1 of this driver about the memory exceeding allocation relocation block?   AptioFix2 works fine but its using reloc block=no.  Does that make any difference?  I know my shutdown is way faster using the original driver versus aptiofix2 but it works fine.  I just wanted to know if there were versions out there for Aptiofix v1 that fixed this reloc block size?  Maybe bad searching on my part because i thought RehabMan had posted some different reloc block sizes?

 

This is for an Asus maximus VIII Hero Alpha, skylake Motherboard.

 

Thanks

 

Edited:

 

Should have searched better found the fix changed CsrActiveConfig from 0x3 to 0x67.  Was the original AptioFixDrv Reloc Allocation Relocation size increased then? 

 

Using AptioFIx2Drv sets reloc block to "yes" and AptioFixDrv original sets reloc block "no" is there any difference here?  Only difference I can observe is the original AptioFixDrv gives me much faster shutdown.

[apianti]

AptioFix2 does not relocate the allocation for the kernel, where AptioFix does. Use whichever works. There are modified versions, DO NOT USE THEM, because they free random regions of memory, you don't want this.