Jump to content

SMC The place to be, definitely!


modbin
 Share

40 posts in this topic

Recommended Posts

Could this be used with Clover??

 

Seems very interesting to have the ability to port certain kexts into efi drivers, and so interacting with Mac OS X on a firmware level, not on a kext level, and possibly making the boot process faster and more reliable and certainly more Vanilla :D

  • Like 1
Link to comment
Share on other sites

Usage ⥤ Clover

possible or not?

 

Could this be used with Clover??

 

Linux, Win, OS X or in Shell

 

So, it works in all OSes and within UEFI (Shell)... but Clover is the exception, of course. ;)

 

Seems very interesting to have the ability to port certain kexts into efi drivers

 

You cannot port just any kext. This is a virtual device, not a device driver.

  • Like 4
Link to comment
Share on other sites

Interesting nonetheless. I am a bit more clarified now about efi drivers. But isn't there a way to take some kexts' functions and put them into an efi driver that could be loaded with Clover and/or Ozmosis in an earlier stage of boot than kexts do?

Link to comment
Share on other sites

Hi modbin .. glad to see u again

 

just curious applicated in driver64uefi in clover

 

0:283  0:000  Loading FSInject-64.efi  status=Success
0:284  0:001  Loading OsxAptioFixDrv-64.efi  status=Success
0:285  0:000  Loading OsxFatBinaryDrv-64.efi  status=Success
0:286  0:000  Loading SMCUTIL.EFI  status=Success

 

and this I get with Fakesmc (slice version)

 

picos-Mac-Pro:~ pico$ bdmesg | grep fakesmc
1:354  0:015     fakesmc-key-NATi-ui16:00 00
1:354  0:000     fakesmc-key-NATJ-ui8:00
1:355  0:000     fakesmc-key-NTOK-ui8:01
1:356  0:000     fakesmc-key-CLKT-ui32:00 00 EB E0
1:357  0:000     fakesmc-key-CLKH-{clh:00 00 70 80 00 01 19 40
1:358  0:000     fakesmc-key-LsBA-ui8:90
1:359  0:000     fakesmc-key-HI0N-ui8:04
1:359  0:000     fakesmc-key-MSDW-ui8:00
1:360  0:000     fakesmc-key-LSSS-ui16:02 00

Link to comment
Share on other sites

I was going a little further...

 

I renamed the FakeSMC.kext to FakeSMC.kext.org in /EFI(Clover/kexts/other while putting the smcutil.efi to /EFI/Clover/drivers64UEFI.

After reboot, right before the clover boot menu is shown, I got the following message:

post-638272-0-63824700-1469187875_thumb.jpg

 

The OSX boot itself seemed to start fine but never finished to the login screen.

Does anybody know about this applesec.efi mentioned in the screenshot?

Link to comment
Share on other sites

Smcutil is the app to dump thr keys etc (as can be seen in the pic), not the Virtual Device creator.

Interesting nonetheless. I am a bit more clarified now about efi drivers. But isn't there a way to take some kexts' functions and put them into an efi driver that could be loaded with Clover and/or Ozmosis in an earlier stage of boot than kexts do?

Some kexts' functions, like what?
  • Like 1
Link to comment
Share on other sites

The question should be what to do with those dumped keys from the screenshot.

 

BTW: If I use "smcutil.efi -dumpinfo" in Clovers EFI-Shell, I get the same message as I posted before, regarding a missing "applesec.efi".

Does this means, that the app currently only works in OZM Shell?

Link to comment
Share on other sites

  • 2 months later...
 Share

×
×
  • Create New...