Jump to content

Clover General discussion

ErmaC

By ErmaC,
in Clover

 Share
30960 posts in this topic

Recommended Posts

yapan4
yapan4
Posted
Posted (edited)

My hack from signature don't boot with r5115(r5114 all ok), debug say "Invalid device tree for kext injection". Preboot log attached. Together screenshot from Clover built-in embedded Theme with missed icon or badge.

 

Someone, upload please latest compiled BOOTX64.efi or CloverX64.efi for test.

 

Thank you.

preboot.log

screenshot0.png

Edited by yapan4
dragonmel
dragonmel
Posted
Posted

r5115 prebuilt release is actually working pretty good on a VERY OLD DX58so... I have had issues transitioning this board that was rock solid running clover 43xx and ElCap with a 660 graphics card.. more reliable than my MacBook but moving to a Vega and clover 5000+ has been.. well interesting

 

It has brought native NVRAM to this intel half baked EUFI that this board has.. but it broke the ability for the board to boot without manually hitting F10 every boot to get to the bios boot picker... clover added a Mac OS X header and my UEFI drive showed up there but if left to boot on its own would go black screen with a solid cursor and not boot into clover at all...  

The other day in the clover menu I decided to hit apply clover boot option to all volumes and boom.. now a whole bunch of boot.efi entries show up above the MAC OS X header and the board does auto boot them.. it unfortunately as mentioned does not respect the picked drive but will default to preboot.. so I removed all boot options, used clover to hide all but my macOS volume and recovery..  rebooted, added clover boot options to all which added boot.efi lines only for macOS and recovery.. and defualts to the first drive in line which is macOS.. so one issue solved

 

I too have noticed that i now get a cmos reset on reboot and sometimes even on start after full shutdown. I have a heavily patched DSDT and don't use clovers auto fix..  do 10.14.6 2020-002 change the RTC requirements and need a new patch?  

 

I have also lately decided to go split personality on the SMBIOS section.  I was running straight MacPro5,1 as the board and the W3680 are pretty damn close to a late 2012 Mac Pro ...  but now I put in JUST the board-id of the iMac-pro instead of injecting it as a shiki variable... I now have FULL 264 AND 265 encode/decode with the vega and at least DRM with prime video using just pikera and skikigva=80 args along with dart=0 and darkwake=no

 

is there a way like with open core to change a board-it without it showing up in iMessage debug?  like they are doing with real macpro5,1 and open core..?  doesn't really mater.. apple did kick my iMessage but signing out, rebooting and signing back in have SO FAR worked so even though  I am using macpro5,1 def, serial, firmware etc.. and the iMacpro1,1 board id... the rig works pretty damn good.

 

I can still only boot with one monitor connected at DP1 .. if I try and boot the HDMI monitor or have both on at boot, or boot the one and turn on the other after getting to the desktop, black screen and console logging GPU.restart .. 

so I have to boot single, sleep, wake and that wake is sometimes hit/miss.. but if it wakes.. the second monitor can now be on and subsequent sleep/wakes usually are reliable and both monitors can remain on.. I have yet to figure that out

 

I know that open core is the future and that a lot of development is focused there but I just don't think the x58 will work very well with it .. and with no way to use my modded DSDT I would have to figure out all the find and replaces and that is just way too far past my ability or paygraide.. 

 

keep up to good work boys... 

 

Matgen84
Matgen84
Posted
Posted
34 minutes ago, SergeNu said:

In what format? icns worked before i update clover with one of new 5100+ builds.

 

Now, Clover do not support icns format, only png rename too icns. In all cases, you can optimize your them via Clover.app

Matgen84
Matgen84
Posted
Posted

Hi @Slice and Clover Team

 

Sorry for Off-Topic:

 

I test r5115 (ce9538bb4) and r5115 (33a9cc85a) on my IvyBridge config (Mojave): I've a problem with Wifi connection

 

  • AirportBrcmFixUp 2.0.7 + Clover Fix Airport -----> don't work : 5GHz/40Mhz instead of 5GHz/80Mhz, wifi transmission speed 7Mb, Google drive won't connect, Safari too.
  • AirportBrcmFixUp 2.0.7 + without Clover Fix Airport ----> Idem
  • Only Clover Fix Airport: Wifi works, so Internet too.

Any ideas. Please.

Pene
Pene
Posted
Posted
2 hours ago, SergeNu said:

In what format? icns worked before i update clover with one of new 5100+ builds.

It was discontinued around 5109 or so.

Icons should be in png format. They can be .icns extension (for compatibility) but content must be png format.

  • Like 1
Slice
Slice
Posted
Posted
1 hour ago, Matgen84 said:

Hi @Slice and Clover Team

 

Sorry for Off-Topic:

 

I test r5115 (ce9538bb4) and r5115 (33a9cc85a) on my IvyBridge config (Mojave): I've a problem with Wifi connection

 

  • AirportBrcmFixUp 2.0.7 + Clover Fix Airport -----> don't work : 5GHz/40Mhz instead of 5GHz/80Mhz, wifi transmission speed 7Mb, Google drive won't connect, Safari too.
  • AirportBrcmFixUp 2.0.7 + without Clover Fix Airport ----> Idem
  • Only Clover Fix Airport: Wifi works, so Internet too.

Any ideas. Please.

Brcm WiFi depends on Board-ID in SMBIOS which probably also fixed by AirportBrcmFixUp other way.

  • Like 1
Matgen84
Matgen84
Posted
Posted (edited)
3 hours ago, Slice said:

Brcm WiFi depends on Board-ID in SMBIOS which probably also fixed by AirportBrcmFixUp other way.

 

@Slice

On Catalina (Aorus Master rig),  AirportBrcmFixUp 2.0.7 + Clover Fix Airport works fine ( r5115 33a9cc85a). On Mojave (IvyBridge), AirportBrcmFixUp 2.0.7 or 2.0.6 + Clover Fix Airport don't work ( r5115 33a9cc85a). I don't see any changes on Board-ID detection from  AirportBrcmFixUp repo. Maybe I mistaken: it was WhateverGreen who use Board-ID.

 

 

debug.log

preboot.log

Edited by Matgen84
yapan4
yapan4
Posted
Posted

Two more remarks:
1) bot argument -v still does not work in version 5114
2) The BIOS DSDT.aml file is 740KB on my motherboard and is probably too big for Clover.

 

 DSDT length out of range

 

Probably fix is available and need be applied(I don't known, I'm not developer) - https://github.com/CloverHackyColor/CloverBootloader/blob/master/rEFIt_UEFI/Platform/FixBiosDsdt.cpp#L5389

 

Thank you

Matgen84
Matgen84
Posted
Posted
7 minutes ago, Jief_Machak said:

I thought it was fixed, but is it in the 5114 version... not sure. Anyone knows ?

 

13 minutes ago, yapan4 said:

Two more remarks:
1) bot argument -v still does not work in version 5114

 

The boot arg -v is fixed at least since r5114 (commit: 67e496d6e). Doesn't exist in r5115 Release.

  • Like 1
Slice
Slice
Posted
Posted
2 hours ago, yapan4 said:

Two more remarks:
1) bot argument -v still does not work in version 5114
2) The BIOS DSDT.aml file is 740KB on my motherboard and is probably too big for Clover.

 

 DSDT length out of range

 

Probably fix is available and need be applied(I don't known, I'm not developer) - https://github.com/CloverHackyColor/CloverBootloader/blob/master/rEFIt_UEFI/Platform/FixBiosDsdt.cpp#L5389

 

Thank you

I am not interesting in bugs already resolved in new commits. Thanks.

  • Like 1
  • Haha 2
vector sigma
vector sigma
Posted
Posted (edited)
23 minutes ago, Slice said:

2) The BIOS DSDT.aml file is 740KB on my motherboard and is probably too big for Clover.

@SliceThis is different story? 

if ((DsdtLen < 20) || (DsdtLen > 400000)) { //fool proof (some ASUS dsdt > 300kb?)
    MsgLog("DSDT length out of range\n");
    return;
  }

 

Edited by vector sigma
  • Like 2
yapan4
yapan4
Posted
Posted (edited)
3 hours ago, vector sigma said:

Are you talking about github release or you try to compile last source? 

Github release. I will be grateful if someone attaches the compiled Clover.efi with the latest changes (aka beta testing)

 

In the end, I'm in no hurry and can wait for the next release ...

Edited by yapan4
  • Like 1
Slice
Slice
Posted
Posted
19 minutes ago, yapan4 said:

Github release. I will be grateful if someone attaches the compiled Clover.efi with the latest changes (aka beta testing)

 

In the end, I'm in no hurry and can wait for the next release ...

This one

 

CLOVERX64.efi.zip

  • Thanks 1
 Share
Go to topic listing
×
×
  • Create New...