Jump to content
30960 posts in this topic

Recommended Posts

Posting here because I can't start a new topic.
 
I'm running Clover on a 4k monitor. In OS X, Retina/HiDPI mode is nice and dandy.
 
In Clover boot screen > Options > System Parameters > boot_args->flags menu, I notice an option for "HiDPI". Checking this option does nothing immediately, except change the boot_args->flags value from 0x0028 to 0x0002. Value returns to 0x0028 on reboot.
 
What does this flag do, and how can I enable it permanently?

 

That one for me Sherlocks?

Not sure.

You should check this list.

1. Back r3974, then check audio.

2. Use old AppleALC file with latest clover

3. Remember when you get to work audio(guess)

4. Consider 10.12.3 with r3974.

5. Etc...

 

나의 LG-F410S 의 Tapatalk에서 보냄

10.12.4 Public Beta 1 with Clover 3998 Audio is Gone (Codec is CX20590) Lenovo G580 Laptop Ivy Brigde Based

 

Sherlock can i use your Fix (v2) to get Audio Working again?

Please test and report

 

나의 LG-F410S 의 Tapatalk에서 보냄

It works! Thank You Sherlocks! Made my Day! :-*

Thank you.

Still need test for RTC, other pathes included in kext_inject.c from users

I'm waiting.

 

나의 LG-F410S 의 Tapatalk에서 보냄

It works! Thank You Sherlocks! Made my Day! :-*

 

please test again

 

thanks in advance

r3998fix v3.zip

  • Like 1

i updated rc script.

 

better reboot time after click restart button. The nvram file creation on the ESP partition no longer fails.

 

please test and report.

 

thanks in advance

 

v1.8 © 2017 syscl/lighting/Yating Zhou

Found ESP on disk0s1

Found Clover in /Volumes/ESP01/EFI/CLOVER

Target path: /Volumes/ESP01 - saved new values to NVRAM

>> End Script: /private/etc/rc.shutdown.d/80.save_nvram_plist.local

 

Supreme-MBP:~ supreme$ sudo /etc/rc.shutdown.d/80.save_nvram_plist.local

Password:

Supreme-MBP:~ supreme$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log

v1.8 © 2017 syscl/lighting/Yating Zhou

Found ESP on disk0s1

Found Clover in /Volumes/ESP01/EFI/CLOVER

Target path: /Volumes/ESP01 - saved new values to NVRAM

Supreme-MBP:~ supreme$ sudo /etc/rc.shutdown.d/80.save_nvram_plist.local

Supreme-MBP:~ supreme$ sudo cat /Library/Logs/CloverEFI/rc.shutdown.log

v1.8 © 2017 syscl/lighting/Yating Zhou

Found ESP on disk0s1

Found Clover in /Volumes/ESP01/EFI/CLOVER

Target path: /Volumes/ESP01 - no change values to NVRAM

Supreme-MBP:~ supreme$ 

80.save_nvram_plist.local-SherlocksV2.zip

  • Like 2

@sherlocks - ok - your 1.8 nvram script works...

 

BUT it does a few things that may need some further scrutiny - and of course is the reason I use the attached scripts.

 

Question:

do you use LogoutHook

or

as shutdown script in CloverDaemon sleep loop only run on shutdown?

 

The general logical flow of the script is:

 

1) fndESP

- loop to find all ESP partitions on all disks

- mount the ESP to check for EFI/CLOVER

- and if no EFI/CLOVER unmount since it is not needing nvram file.

 

2) dmpNVRAM

the loop on all the mounted ESP locations to write nvram.plist 

 

Questions/issues:

--------

1) _fndESP

 

your script will try to unmount an ESP if it is already mounted.

why bother to do this unmount?

 

- the mounting of the filesystem is the most time-consuming and resource intensive aspect, so

(A) why not use the existing mount?

 

- the unmount procedure - if busy - you revert to forced unmount -

 why risk corrupting the filesystem only to remount it in the next step?

 

(B) And then why remove the mount point with "rm -r"  - VERY UNSAFE action for a mount point

- "rmdir" is enough if you need to remove a directory and not the tree.

again, there is no need unmount ESP in the first place. 

 

2) _dmpNVRAM

 

(A) why write out the nvram file - then check to see if there is a change?

 

echo "${gNVRAMbuf}" > "${gTarPath}/${gNVRAMf}"

if [[ "${gOldNVRAM}" != "${gNVRAMbuf}" ]]; then

nvram -x -p >"${gTarPath}/${gNVRAMf}"

...

fi

 

(B) why leave ESP mounted? 

this is ok if this script is used in CloverDaemon as a shutdown script 

but if it used in a LogoutHook - the ESP should not be left mounted.

 

 

---------------------

please review the attached script

 

1) cleaned up aspects

- removed all extra variables and items not needed

- remove redirects to log file - doesn't work well when called from CloverDaemon - loses synchronous output.

 

2) fndESP feature

- uses current ESP mount in stead of unmount / mount

 

3) dmpNVRAM feature

- ONLY writes to / of OS, if there is NO ESP found

- writes the current nvram settings if there is a CLOVER directory. Note: there is no "win" in checking the file to see if there is no change. meaning there is no performance gain - so just write out current nvram to the file.

- finally, try to unmount ESP  -  if it fails to unmount (busy) that's ok.  to avoid, busy upon write, the best practice here is to put .metadata_never_index in the ESP.

 

Note: I use LogoutHook (CloverDaemon-stopservice) instead of use the original CloverDaemon sleep loop.

 

 

nvram_v1.9.zip

  • Like 1

@sherlocks - ok - your 1.8 nvram script works...

 

BUT it does a few things that may need some further scrutiny - and of course is the reason I use the attached scripts.

 

Question:

do you use LogoutHook

or

as shutdown script in CloverDaemon sleep loop only run on shutdown?

 

The general logical flow of the script is:

 

 

 

 

 

 

 

1) fndESP

- loop to find all ESP partitions on all disks

- mount the ESP to check for EFI/CLOVER

- and if no EFI/CLOVER unmount since it is not needing nvram file.

2) dmpNVRAM

the loop on all the mounted ESP locations to write nvram.plist

Questions/issues:

--------

1) _fndESP

 

 

 

 

 

 

your script will try to unmount an ESP if it is already mounted.

why bother to do this unmount?

- the mounting of the filesystem is the most time-consuming and resource intensive aspect, so

(A) why not use the existing mount?

- the unmount procedure - if busy - you revert to forced unmount -

why risk corrupting the filesystem only to remount it in the next step?

(B) And then why remove the mount point with "rm -r" - VERY UNSAFE action for a mount point

- "rmdir" is enough if you need to remove a directory and not the tree.

again, there is no need unmount ESP in the first place.

2) _dmpNVRAM

 

 

 

 

 

 

(A) why write out the nvram file - then check to see if there is a change?

echo "${gNVRAMbuf}" > "${gTarPath}/${gNVRAMf}"

if [[ "${gOldNVRAM}" != "${gNVRAMbuf}" ]]; then

nvram -x -p >"${gTarPath}/${gNVRAMf}"

...

fi

(B) why leave ESP mounted?

this is ok if this script is used in CloverDaemon as a shutdown script

but if it used in a LogoutHook - the ESP should not be left mounted.

---------------------

please review the attached script

 

1) cleaned up aspects

- removed all extra variables and items not needed

- remove redirects to log file - doesn't work well when called from CloverDaemon - loses synchronous output.

 

2) fndESP feature

- uses current ESP mount in stead of unmount / mount

 

3) dmpNVRAM feature

- ONLY writes to / of OS, if there is NO ESP found

- writes the current nvram settings if there is a CLOVER directory. Note: there is no "win" in checking the file to see if there is no change. meaning there is no performance gain - so just write out current nvram to the file.

- finally, try to unmount ESP - if it fails to unmount (busy) that's ok. to avoid, busy upon write, the best practice here is to put .metadata_never_index in the ESP.

 

Note: I use LogoutHook (CloverDaemon-stopservice) instead of use the original CloverDaemon sleep loop.

I use clover daemon(i dont touch clover script(ESP)). Im not prefer to touch other script.

 

I tested your script(r3998). But shown fail case. I did try to find fail case. Your script still has problem. I attached fact pic previous reply before.

 

So i returned unmount method. I did test 1.8 to find fail case. 1.8 never shown fail case. I did debug to check each parts

 

I will check 1.9 and test. If 1.9 never has fail, we can select more better.

 

Thank you.

 

나의 LG-F410S 의 Tapatalk에서 보냄

@sherlocks - ok. thanks for reviewing.

 

when you say fail case, i am not sure what that means exactly. the previous pictures were not explaining anything to me. 

what part of the script fails? 

failure to mount ESP?

failure to write to ESP?

failure to unmount ESP?

×
×
  • Create New...