RehabMan
Moderator
- Joined
- May 2, 2012
- Messages
- 181,111
- Motherboard
- Intel DH67BL
- CPU
- i7-2600K
- Graphics
- HD 3000
- Mac
- Mobile Phone
Hi, I am trying to patch a Xiaomi Mi Air 13.3’‘ Skylake-U 2016 running Mojave 10.14.2. I have the following very specific problems:
1. I am using @RehabMan hack-tools (really amazing toolkit) in order to generate a `LiluFriendLite.kext`. It seems that the `create_lilufriend.sh` does not take into account the `CPUFriendDataProvider.kext`. Do I need to add it manually in order to load it or `CPUFriend.kext` loads it since it is codeless?
2. When booting I am getting a lot messages of typepower supply unavailable, assuming successful power for XXYY of 750 mWWakePower and 0 mWSleepPower
. I inject USB power properties viaSSDT-USBX.aml
. What may be wrong:
Code:2019-01-03 18:03:32.566401+0200 0x77 Default 0x0 0 0 <AppleBusPowerController`AppleBusPowerController::requestStaticServicePowerLocked(IOService*, unsigned int&, unsigned int&)> kernel: (AppleBusPowerController) 000001.566394 AppleBusPowerController: AppleBusPowerController::requestStaticServicePowerLocked: power supply unavailable, assuming successful power for SS01 of 750 mWWakePower and 0 mWSleepPower 2019-01-03 18:03:32.573344+0200 0x77 Default 0x0 0 0 <AppleBusPowerController`AppleBusPowerController::requestStaticServicePowerLocked(IOService*, unsigned int&, unsigned int&)> kernel: (AppleBusPowerController) 000001.573338 AppleBusPowerController: AppleBusPowerController::requestStaticServicePowerLocked: power supply unavailable, assuming successful power for SS02 of 750 mWWakePower and 0 mWSleepPower 2019-01-03 18:03:32.573601+0200 0x77 Default 0x0 0 0 <AppleBusPowerController`AppleBusPowerController::requestStaticServicePowerLocked(IOService*, unsigned int&, unsigned int&)> kernel: (AppleBusPowerController) 000001.573596 AppleBusPowerController: AppleBusPowerController::requestStaticServicePowerLocked: power supply unavailable, assuming successful power for SS03 of 750 mWWakePower and 0 mWSleepPower 2019-01-03 18:03:32.573883+0200 0x77 Default 0x0 0 0 <AppleBusPowerController`AppleBusPowerController::requestStaticServicePowerLocked(IOService*, unsigned int&, unsigned int&)> kernel: (AppleBusPowerController) 000001.573878 AppleBusPowerController: AppleBusPowerController::requestStaticServicePowerLocked: power supply unavailable, assuming successful power for SS04 of 750 mWWakePower and 0 mWSleepPower 2019-01-03 18:03:32.574132+0200 0x65 Default 0x0 0 0 kernel: Waiting on <dict ID="0"><key>IOProviderClass</key><string ID="1">IOResources</string><key>IOResourceMatch</key><string ID="2">boot-uuid-media</string></dict> 2019-01-03 18:03:32.590052+0200 0x77 Default 0x0 0 0 <AppleBusPowerController`AppleBusPowerController::requestStaticServicePowerLocked(IOService*, unsigned int&, unsigned int&)> kernel: (AppleBusPowerController) 000001.590048 AppleBusPowerController: AppleBusPowerController::requestStaticServicePowerLocked: power supply unavailable, assuming successful power for SS03 of 750 mWWakePower and 0 mWSleepPower
3. When booting I am getting a lot of these messages related to the camera. My camera works. Is this something I need to worry?
Code:2019-01-03 18:03:41.027274+0200 0x1fc Default 0x0 0 0 kernel: Notice - new kext com.apple.driver.KextExcludeList, v14.0.3 matches prelinked kext but can't determine if executables are the same (no UUIDs). 2019-01-03 18:03:41.107540+0200 0x1fc Default 0x0 0 0 kernel: Matching service count = 14 2019-01-03 18:03:41.108071+0200 0x1fc Default 0x0 0 0 kernel: Matching service count = 21 2019-01-03 18:03:41.111504+0200 0x1fc Default 0x0 0 0 kernel: XiaoMi USB 2.0 Webcam: family specific matching fails 2019-01-03 18:03:41.111510+0200 0x1fc Default 0x0 0 0 kernel: AppleUSBInterface: family specific matching fails 2019-01-03 18:03:41.111514+0200 0x1fc Default 0x0 0 0 kernel: CDC Communications Control: family specific matching fails 2019-01-03 18:03:41.111517+0200 0x1fc Default 0x0 0 0 kernel: AppleUSBInterface: family specific matching fails 2019-01-03 18:03:41.111520+0200 0x1fc Default 0x0 0 0 kernel: Matching service count = 33 2019-01-03 18:03:41.113441+0200 0x1fc Default 0x0 0 0 kernel: XiaoMi USB 2.0 Webcam: family specific matching fails 2019-01-03 18:03:41.113445+0200 0x1fc Default 0x0 0 0 kernel: AppleUSBInterface: family specific matching fails 2019-01-03 18:03:41.113449+0200 0x1fc Default 0x0 0 0 kernel: CDC Communications Control: family specific matching fails 2019-01-03 18:03:41.113453+0200 0x1fc Default 0x0 0 0 kernel: AppleUSBInterface: family specific matching fails 2019-01-03 18:03:41.113455+0200 0x1fc Default 0x0 0 0 kernel: Matching service count = 35
4. And finally I get these messages that reference the battery and I am not sure if I am missing something:
Code:2019-01-03 18:03:42.482981+0200 0x200 Default 0x0 0 0 <IOPlatformPluginFamily`DebugPrint> kernel: (IOPlatformPluginFamily) High standby delay is not specified! Defaulting to 0x2a30 2019-01-03 18:03:42.482983+0200 0x200 Default 0x0 0 0 <IOPlatformPluginFamily`DebugPrint> kernel: (IOPlatformPluginFamily) High standby delay is not specified! Defaulting to 0x2a30 2019-01-03 18:03:42.482989+0200 0x200 Default 0x0 0 0 <IOPlatformPluginFamily`DebugPrint> kernel: (IOPlatformPluginFamily) Low battery threshold is not specified! Defaulting to 0x32 2019-01-03 18:03:42.482990+0200 0x200 Default 0x0 0 0 <IOPlatformPluginFamily`DebugPrint> kernel: (IOPlatformPluginFamily) Low battery threshold is not specified! Defaulting to 0x32
Thanks for you time even reading my post.
I attach the debugging info. on the ACPI/patched I include the source .dsl files with my comments.
Thanks Again!!!!
Off-topic.