Jump to content
30960 posts in this topic

Recommended Posts

Obviously, Apple uses the term "kernel flag" loosely, as some of those flags actually are handled by boot.efi.

 

 

I use it all the time to correct the situation when AppleHDA falls of out kernel cache (when using AppleHDA injector with symlink).

It works.

 

If you don't want to/don't think you need it, just don't use it. I really don't care.

 

Chameleon doesn't use boot.efi, so that flag would never have done anything if not handled by boot.efi. Also it's not present in boot.efi, check with strings command line tool, in fact I see no flags.

 

EDIT: I tried to post the results but it apparently contains square brackets so it disabled the ability for me to post, I had to leave and come back.

EDIT2: Don't get me wrong I have no problem with getting something to work but we had this discussion like five years ago at least on projectosx, and we came to the consensus that it did not work without implementing it to block when -f was in boot args, which then we decided to move to a bit flags style system for determining the boot actions.

EDIT3: I have attached the output of the ASCII and Unicode strings from boot.efi. In order for it to have any effect in boot.efi, there would need to be the unicode string -f, which there is not.

boot.efi.strings.txt

boot.efi.strings.Unicode.txt

  • Like 1
Is it possible to use nvram reset in gui?

I have made a suggestion once before, but I suggest it again.

This capability is a function in Ozmosis.

cecekpawon has previously applied this ability to clover.

Adding this feature makes it possible to reset the remaining nvda_drv = 1 options in nvram for nvidia graphics or the keys left in hibernation or etc, which can be useful in many situations.

 

in his github

here is commit link

 

thanks in advance

  • Like 2

Chameleon doesn't use boot.efi, so that flag would never have done anything if not handled by boot.efi. Also it's not present in boot.efi, check with strings command line tool, in fact I see no flags.

 

EDIT: I tried to post the results but it apparently contains square brackets so it disabled the ability for me to post, I had to leave and come back.

EDIT2: Don't get me wrong I have no problem with getting something to work but we had this discussion like five years ago at least on projectosx, and we came to the consensus that it did not work without implementing it to block when -f was in boot args, which then we decided to move to a bit flags style system for determining the boot actions.

EDIT3: I have attached the output of the ASCII and Unicode strings from boot.efi. In order for it to have any effect in boot.efi, there would need to be the unicode string -f, which there is not.

All I know is that -f works for my purpose.

Therefore it is parsed/handled somewhere in the system. I have no need to determine specifically where.

 

Getting "boot without caches" to work "like it does in older OS X" (eg. for getting the system to not load/start kexts in kernel cache), is something I never attempted to fix as I have no need for it.

 

Is it possible to use nvram reset in gui?
I have made a suggestion once before, but I suggest it again.
This capability is a function in Ozmosis.
cecekpawon has previously applied this ability to clover.
Adding this feature makes it possible to reset the remaining nvda_drv = 1 options in nvram for nvidia graphics or the keys left in hibernation or etc, which can be useful in many situations.
 
in his github
here is commit link
 
thanks in advance

 

 

If you can find it look at the source code for the supposed to exist EFI shell command "default". I see it documented but don't see it implemented anywhere and it doesn't work in virtualbox or my actual firmware. You can always try to iterate through every variable and set every size to zero to remove it and see if that resets it to default when you restart or immediately, or if you then have to actually reset your CMOS.

 

EDIT: Just merge his changes into the main repo dude, I see you mean only the variables clover would ever change and not your whole nvram.

 

All I know is that -f works for my purpose.

Therefore it is parsed/handled somewhere in the system. I have no need to determine specifically where.

 

Getting "boot without caches" to work "like it does in older OS X" (eg. for getting the system to not load/start kexts in kernel cache), is something I never attempted to fix as I have no need for it.

 

But the problem is that there are all of us saying that it doesn't work because we developed this and went through this, and just you saying it does. I am just trying to figure out why man, I'm not attacking you or anything. But evidence and stuff. Science. I'm asking for why it works, the evidence.

  • Like 1

But the problem is that there are all of us saying that it doesn't work because we developed this and went through this, and just you saying it does. I am just trying to figure out why man, I'm not attacking you or anything. But evidence and stuff. Science. I'm asking for why it works, the evidence.

Depends on expectations for what you mean by "works".

I think different people have different expectations for it.

 

If you implement audio with an AppleHDA injector (with symlink) + Clover patches, you would eventually run into a situation where you need "-f, rebuild cache, reboot," to restore lost audio. It is super common with that particular technique for implementing audio (which admittedly is a bit sketchy) and the -f flag (followed by rebuild caches) works every time to fix it. As for the "why", no certainty on it... Lack of time and interest... other things higher priority.

If you use some other method to implement audio, you would likely want "without caches" to do what it used to do, as you're probably looking to prevent a kext that is in cache from starting (because it is crashing), and of course that doesn't work in current macOS/OS X with Clover as written, but requires other methods to removoe the kernel cache or reset it.

  • Like 1

@Sherlocks According to source Clover will do that job for you as long as you have gSettings.NvidiaWeb leave unset. Isnt it?

I see. I didn't look code in detail that you take a link before.

I just saw that someone reported nvram issue related nvda_drv=1 in nvram before in this thread. He always kept nvda_drv=1 in his nvram storage. Not sure. I can' test. Now i don't have any nvidia graphic. i just suggested nvram reset. Also in various situation, seems your commit is usefull. Can we use nvram reset features for latest clover?

 

나의 LG-F800S 의 Tapatalk에서 보냄

I see. I didn't look code in detail that you take a link before.

I just saw that someone reported nvram issue related nvda_drv=1 in nvram before in this thread. He always kept nvda_drv=1 in his nvram storage. Not sure. I can' test. Now i don't have any nvidia graphic. i just suggested nvram reset. Also in various situation, seems your commit is usefull. Can we use nvram reset features for latest clover?

 

He did not change the license, you can always merge downstream commits back upstream.

Depends on expectations for what you mean by "works".

I think different people have different expectations for it.

 

If you implement audio with an AppleHDA injector (with symlink) + Clover patches, you would eventually run into a situation where you need "-f, rebuild cache, reboot," to restore lost audio. It is super common with that particular technique for implementing audio (which admittedly is a bit sketchy) and the -f flag (followed by rebuild caches) works every time to fix it. As for the "why", no certainty on it... Lack of time and interest... other things higher priority.

If you use some other method to implement audio, you would likely want "without caches" to do what it used to do, as you're probably looking to prevent a kext that is in cache from starting (because it is crashing), and of course that doesn't work in current macOS/OS X with Clover as written, but requires other methods to removoe the kernel cache or reset it.

 

But you are rebuilding the caches... So don't you think that's what is solving your issue? Have you tried not using -f and just rebuilding caches? If -f was working, the kext would have loaded and you should have working audio on that boot... No?

  • Like 1

Can we use nvram reset features for latest clover?

 

You can take whatever you want from there. You can start to merge all known variable  set by Clover here with mine, and list em all into GUI with checkbox / set a combo key for that.

 

He did not change the license, you can always merge downstream commits back upstream.

 

Please dont, Im afraid it will screwed up current Clover. Just take some with carefully while merging. Maybe including this hacky way to block individual kext from prelinked to help Rehabman.

You can take whatever you want from there. You can start to merge all known variable  set by Clover here with mine, and list em all into GUI with checkbox / set a combo key for that.

 

 

Please dont, Im afraid it will screwed up current Clover. Just take some with carefully while merging. Maybe including this hacky way to block individual kext from prelinked to help Rehabman.

 

Lol, I didn't mean actually merge the commits into the current repo, I just meant that yes he can take downstream commits and implement them. Plus there would be no way to solve the merge conflicts since you are using a git repo and the official is svn, and yours is based off like 1000 revisions behind too, so yes that would be not good.

 

EDIT: Ok only like 500.

Depends on expectations for what you mean by "works".

I think different people have different expectations for it.

 

If you implement audio with an AppleHDA injector (with symlink) + Clover patches, you would eventually run into a situation where you need "-f, rebuild cache, reboot," to restore lost audio. It is super common with that particular technique for implementing audio (which admittedly is a bit sketchy) and the -f flag (followed by rebuild caches) works every time to fix it. As for the "why", no certainty on it... Lack of time and interest... other things higher priority.

If you use some other method to implement audio, you would likely want "without caches" to do what it used to do, as you're probably looking to prevent a kext that is in cache from starting (because it is crashing), and of course that doesn't work in current macOS/OS X with Clover as written, but requires other methods to removoe the kernel cache or reset it.

I use a patched AppleHDA and also lose the sound after an update, but after rebuilding the cache and restart it works again without any boot flags.

I use a patched AppleHDA and also lose the sound after an update, but after rebuilding the cache and restart it works again without any boot flags.

Yes, sometimes only a rebuild cache is needed.

Except when it doesn't work.

 

Switch off Fusion drive then install High Sierra and then switch on Fusion drive again.

Sorry for the delay, I'm in a test week in college.

 

Would doing this make me lose all my files and programs? The intention would be to be able to upgrade from 10.13 to 10.13.1 and in future updates too, without starting from 0. If do not lose any files and programs, how can I do this turn off, turn on ? Command lines in the terminal?.

 

No! Don't mount the virtualized core storage volume, that gets you nowhere. Inspect the individual volumes on the disks themselves, they should have multiple partitions. That's why I said terminal, because Finder will only allow you to see the core storage volume. I believe there is a preboot volume that contains the actual loaders, they are in some weird named folders, they might have changed the folders. Your boot.log section where it says your disks/volumes would be nice too cause it should say in that as well.

I formatted the Fusion Drive. First I installed the updates on the notebook HD, then I cloned the HD image to Fusion Drive. Just this way I'm getting the system updated, the problem is that I lose all files and programs. But I had to do this to deliver a college project.

 

 

When I formatted it, I took some photos to try to solve the problem.

This is the correct path that OsxAptioFix2Drv takes to make the update successful (I took this picture when I updated the notebook's HD system)

post-748259-0-32316000-1510281193_thumb.jpg

 

This is the path that OSXAptionFix takes to upgrade via Fusion Drive. So I guess it is not finding the installation location properly.

 

How do I fix this path? Is it possible to fix this in a future clover update?
post-748259-0-62375600-1507264577_thumb.jpg

You should read the comment by fusion71au, a few back, it fully answers your question and how to solve it. I have no idea if it's fixed yet or not, it's weird that it would just stop working all the sudden because that's the same method that it was using previously so I'm not sure why it failed unless it had to do with another fix for the installer fusion71au sugguested.

  • Like 1

Clover r4295 build in High Sierra and Clover r4296 built in Sierra.

attachicon.gifScreen Shot 2017-11-10 at 3.11.16 pm.png

Why is Sierra's list alphabetised but High Sierra is not?

 

I think this happens if you compile Clover in High Sierra with APFS file system.  My compile of Clover r4293 in High Sierra with HFS+ file system (attached to post#15271) is in alphabetical order ...

 

post-846696-0-23543100-1510300585_thumb.png

  • Like 2

i have strange behavior on High Sierra. I can't boot 10.13 os and installer, when aptiofixdrv2 start to override boot.efi the system shutdown and turn on.. No problem under sierra. Thanks in advance.

Change SMBIOS model

×
×
  • Create New...