Jump to content

Clover General discussion


ErmaC
30,171 posts in this topic

Recommended Posts

1 minute ago, Dr. Hurt said:

It works now. The SetIntelBacklight key was #-out in the config. Didn't need that key with older Clover.

 

it's right. but we need to gather info after SetIntelBacklight.

can you upload log? i want to see your intel backlight info

Link to comment
Share on other sites

42 minutes ago, Sherlocks said:

 

it's right. but we need to gather info after SetIntelBacklight.

can you upload log? i want to see your intel backlight info

 

3:500  0:000  Intel GFX IntelBacklight

3:500  0:000    LEV2 = 0x80000000, LEVL = 0x1312, P0BL = 0x14E, GRAN = 0x0

3:500  0:000    LEVW = 0x80000000, LEVX = 0x13121312, LEVD = 0x13121312, PCHL = 0x80300302

3:500  0:000    FBLEVX: default 0x710

Link to comment
Share on other sites

I also has notebook with IvyBridge and HD4000 graphics. Dell E6430 in signature.

I am using follow config.plist

Снимок экрана 2018-10-10 в 21.11.34.png

 

Brightness works with feys F1/F2 and with slider

Снимок экрана 2018-10-10 в 21.08.34.png

 

PNLF in DSDT looks like

            Device (PNLF)
            {
                Name (_HID, EisaId ("APP0002"))  // _HID: Hardware ID
                Name (_CID, "backlight")  // _CID: Compatible ID
                Name (_UID, 0x0A)  // _UID: Unique ID
                Name (_STA, 0x0B)  // _STA: Status
            }

As it was created by Clover 1000--4000 revisions.

Device properties are

Снимок экрана 2018-10-10 в 21.18.57.png

 

Clover GUI looks like

screenshot5.png

 

ioreg

Снимок экрана 2018-10-10 в 20.49.13.png

 

What else?

Should I test something else?

 

 

Link to comment
Share on other sites

4 hours ago, Slice said:
I also has notebook with IvyBridge and HD4000 graphics. Dell E6430 in signature.
I am using follow config.plist
1537812683_2018-10-1021_11_34.png.229e58c4aaadaad82e4b89acaf8e8ca6.png
 
Brightness works with feys F1/F2 and with slider
499999354_2018-10-1021_08_34.png.2615a2a93677435272d45ea983a88f8a.png
 
PNLF in DSDT looks like

            Device (PNLF)           {               Name (_HID, EisaId ("APP0002"))  // _HID: Hardware ID               Name (_CID, "backlight")  // _CID: Compatible ID               Name (_UID, 0x0A)  // _UID: Unique ID               Name (_STA, 0x0B)  // _STA: Status           }
 

As it was created by Clover 1000--4000 revisions.
Device properties are
2002677707_2018-10-1021_18_57.png.68fb12060734e94035fbfee8a5a8a7d5.png
 
Clover GUI looks like
screenshot5.thumb.png.e1568537af9e5c0baa90d1ca438b3bb9.png
 
ioreg
1939930080_2018-10-1020_49_13.png.0e9dc4876a7d203925205de7e3774a91.png
 
What else?
Should I test something else?
 
 

thanks. seems your laptop has almost same max value like ivy framebuffer 0x710.
there is 0x710 in framebuffer and _UID 14 and match AppleBacklight backlight Level(0%~100%) in ivy realmac.
long time ago, ex. like Dr.Hurt case, he has brightness issue between at boot and after wakeup. so we need to match LEVX and framebuffer backlight max value.

if you don't have AppleBacklightinjector, it doen't matter _UID 10 or 14.

EDIT1

here realmac mbp9,1 hd 4000 dump



나의 LG-F800S 의 Tapatalk에서 보냄
 

IOReg.txt.zip

Edited by Sherlocks
Link to comment
Share on other sites

Is there a way we can make clover detect between FakeSMC.kext and VirtualSMC.kext and if VirtualSMC.kext is found/detected the installer will not keep selecting SMCHelper.efi? (Not needed for VirtualSMC.kext i believe (well i'm not using it without any issues)).

And then obviously if FakeSMC.kext is detected/found then select SMCHelper.efi, if it's ever required by FakeSMC.kext that is.

Screen Shot 2018-10-11 at 9.07.36 am.png

  • Like 1
Link to comment
Share on other sites

@Sherlocks

A small update to support MP51 (from Mojave 10.14.0 installer). But I can't say if there is a newer ver just like for other models have September dates (ex. 180917) 

Look at 10.14.1 builds if you can, plz

BiosVersion:      MP51.88Z.F000.B00.1807300628

 

 

 

Снимок экрана 2018-10-11 в 3.02.38.png

Edited by Moorre
  • Like 1
Link to comment
Share on other sites

10 hours ago, Sherlocks said:

thanks. seems your laptop has almost same max value like ivy framebuffer 0x710.
there is 0x710 in framebuffer and _UID 14 and match AppleBacklight backlight Level(0%~100%) in ivy realmac.
long time ago, ex. like Dr.Hurt case, he has brightness issue between at boot and after wakeup. so we need to match LEVX and framebuffer backlight max value.

if you don't have AppleBacklightinjector, it doen't matter _UID 10 or 14.

EDIT1

here realmac mbp9,1 hd 4000 dump



나의 LG-F800S 의 Tapatalk에서 보냄
 

IOReg.txt.zip

I don't have AppleBacklightinjector. Is it needed as we set backlight from Clover?

  • Like 2
Link to comment
Share on other sites

I don't have AppleBacklightinjector. Is it needed as we set backlight from Clover?

not at all. most of laptop with only single iGPU has lower brightness(i remember it start since sandy bridge HD 3000). so we use PNLF SSDT to match framebuffer brightness max value. if someone has lower brightness, we have to set intelmaxbacklight in clover or use PNLF SSDT.

your system has similiar brightness of framebuffer. seems you don't need setintelmaxbacklight. but if you want to accurately match brightness with framebuffer on your system, you can use.

 

AppleBacklightInjector just need exact brightness lengh(0~100%) when decrease brightness or increase brightness. you can see data in AppleBacklight's info file

 

backlight lower issue

- PNLF or SetIntelBacklight with IntelMaxBacklight.

 

AppleBacklightInjector

- want or not.

if want, get more exact backlight length.

 

 

sorry for my bad english.

 

 

 

 

나의 LG-F800S 의 Tapatalk에서 보냄

 

 

 

 

Link to comment
Share on other sites

@Sherlocks (sorry, removed my prev. confusing post lol)

#Question: If we have two Backlight values on NVRAM, which one will be used by System?

Anyway, with NVDA discrete graphics I use "AsusACPIBackLightPanel" 3rd party kext. Thanks.

Screenshot 1.png

Edited by Badruzeus
Link to comment
Share on other sites

[mention=980913]Sherlocks[/mention] (sorry, removed my prev. confusing post lol)
#Question: If we have two Backlight values on NVRAM, which one will be used by System?
Anyway, with NVDA discrete graphics I use "AsusACPIBackLightPanel" 3rd party kext. Thanks.
16529654_Screenshot1.png.728095017b6b890953a714d452db647b.png
i first see your case. did you set 0xFFFF in config?
then you use AsusBacklight kext? what is your kext?

나의 LG-F800S 의 Tapatalk에서 보냄

  • Thanks 1
Link to comment
Share on other sites

1 minute ago, Sherlocks said:

i first see your case. did you set 0xFFFF in config?
then you use AsusBacklight kext? what is your kext?

나의 LG-F800S 의 Tapatalk에서 보냄
 

I leave "Backlight Level" as Empty on config.plist

Link to comment
Share on other sites

[mention=980913]Sherlocks[/mention]
A small update to support MP51 (from Mojave 10.14.0 installer). But I can't say if there is a newer ver just like for other models have September dates (ex. 180917) 
Look at 10.14.1 builds if you can, plz
BiosVersion:      MP51.88Z.F000.B00.1807300628

 
 
 
983110840_2018-10-113_02_38.png.db5ed477bcc0de613b77cdcc682103d3.png

MP5,1 not support mojave right? did you get mp5,1.fd from 10.14 official installer?
i updated biosversion from mojave 10.14.1 beta3. the most of updated models support mojave.


나의 LG-F800S 의 Tapatalk에서 보냄

  • Like 1
Link to comment
Share on other sites

5 hours ago, Sherlocks said:

MP5,1 not support mojave right? did you get mp5,1.fd from 10.14 official installer?
i updated biosversion from mojave 10.14.1 beta3. the most of updated models support mojave.


나의 LG-F800S 의 Tapatalk에서 보냄
 

 

I found that, if it can serve.

 

https://forums.macrumors.com/threads/mp5-1-mojave-10-14-1-dp3-bootrom-140-0-0-0-0-has-native-nvme-support.2132317/

Link to comment
Share on other sites

9 hours ago, Sherlocks said:

MP5,1 not support mojave right? did you get mp5,1.fd from 10.14 official installer?
i updated biosversion from mojave 10.14.1 beta3. the most of updated models support mojave.

It is supporting MP51.

The latest ver is

MP51.88Z.F000.B00.1809191555
EFI Version:  140.0.0.0.0
Quote

Apple released 10.14.1 DP3 and 140.0.0.0.0 Mac Pro BootROM.

  • NVMe EFI module added and it's different than the one from MP61,
  • PCIe drives still recognised as external,
  • Same 29 & 31 microcodes from May,
  • No boot screens for UEFI cards.

Apple released 10.14.1 DP1 and 139.0.0.0.0 Mac Pro BootROM.

  • No boot screens for UEFI cards,
  • no NVMe EFI module added,
  • no FileVault2,
  • same microcodes,
  • still safe to insert the NVMe EFI module.

 

Link to comment
Share on other sites

is FSInject-64 not mandatory anymore for UEFI? Its already installed on my system but when I update to new clover its show uncheck. I tried to install with check its installing but in every new update normally clover choosing efi's automatically but FSInject-64 always show uncheck. it is some kind of bug or it's not mandatory anymore and Clover toggle off automatically for us each new update?

Link to comment
Share on other sites

1 minute ago, telepati said:

is FSInject-64 not mandatory anymore for UEFI? Its already installed on my system but when I update to new clover its show uncheck. I tried to install with check its installing but in every new update normally clover choosing efi's automatically but FSInject-64 always show uncheck. it is some kind of bug or it's not mandatory anymore and Clover toggle off automatically for us each new update?

That means that you uncheck it once, maybe by cases. If you want to start with fresh preferences delete /Library/Preferences/com.projectosx.clover.installer.plist

  • Like 3
  • Thanks 1
Link to comment
Share on other sites

3 hours ago, vector sigma said:

That means that you uncheck it once, maybe by cases. If you want to start with fresh preferences delete /Library/Preferences/com.projectosx.clover.installer.plist

 

 

'cause every new update I am choosing it but next update it shows uncheck. Ok I will try that trick thank you :thumbsup_anim:

Link to comment
Share on other sites

16 minutes ago, Andrey1970 said:

I confirm a bug.
On 4695 works well.

 

Make sure SetIntelBacklight is also set to true. This seems like a rather annoying new requirement.

  • Like 1
Link to comment
Share on other sites

15 hours ago, arimuras said:

ApfsDriverLoader.efi

APFS Format Fusion Drive Support ?

Clover Scan Entries stuck

Not boot

 

Manualy add apfs.efi

Boot Ok

 

---

Mojave 10.14.0

Clover 4705

ApfsDriverLoader AppleSupport v2.0.4

What if you choose ApfsDriverLoader and other efi drivers from Clover release 4700 package? Exclude outer drivers like AppleSupport.

  • Like 1
Link to comment
Share on other sites

13 minutes ago, Slice said:

What if you choose ApfsDriverLoader and other efi drivers from Clover release 4700 package? Exclude outer drivers like AppleSupport. 

 

Clover release 4700 package

Same problem

Clover Scan Entries stuck

 

attach, efi driver

 

sorry for my bad english.

2018-10-14 15.20.20.png

  • Like 1
Link to comment
Share on other sites

51 minutes ago, arimuras said:

 

Clover release 4700 package

Same problem

Clover Scan Entries stuck

 

attach, efi driver

 

sorry for my bad english.

2018-10-14 15.20.20.png

 

Did ApfsDriverLoader.efi work before? For compatibility with Fusion, I think you have to ask @savvas

Link to comment
Share on other sites

×
×
  • Create New...