Contribute
Register

[Guide] Dell XPS 9560 Mojave VirtualSMC, I2C Trackpad, Clover UEFI Hotpatch

Status
Not open for further replies.
@mazakiss

Don't be so modest now haha. You did a great job! I think AppleACPIACAdapter loading on ADP1 really helps. This should absolutely be included.

SSDT-BATC is not necessary as its purpose is to combine 2 batteries. You can remove and test, that BAT0 still shows but I don't think BAT0 does anything as nothing is loaded against it. You can read the disassembled file's comments for it at RehabMan's repo for the file. I compared the one you have and the original, they are identical.

VirtualSMC's way of using battery is actually really cool. Here's the description from Github
SMCBatteryManager implements a complete emulation layer of AppleSmartBattery of SMC and SMBus protocols

With that you can see our battery info in IOREG as so
AppleSmartBattery.png

I think we leave FileVault for now. Maybe I can tackle it later but I'm currently in no position to backup and restore data if I screw up. Some additional info if you're interested, from the repository, "VirtualSMC.efi the module is recommended for boot.efi compatibility when FileVault 2 is enabled. SMCHelper-64.efi is not compatible with VirtualSMC.efi and must be removed."

Thanks a lot for the VoltageShift explanation. This is great stuff, will link your post in the guide. Cooler is absolutely better. I was up late like you, reading and was confused. I did test your setting but did it manually, so nothing permanent. My idle temps for the first time ever I think is 37c, wow!

So if I'm understanding this right, users could test a bit and then build their custom valued kext and inject with Clover. Something if instability were to arise, we would still have a failsafe b/c we could disable the kext at the boot menu in Clover and the system would revert to unmodified.

I will updated the guide and a new clover folder later today. Thanks for contributing.
 
SSDT-BATC is not necessary as its purpose is to combine 2 batteries. You can remove and test, that BAT0 still shows but I don't think BAT0 does anything as nothing is loaded against it. You can read the disassembled file's comments for it at RehabMan's repo for the file. I compared the one you have and the original, they are identical.

You're totally right, BATC-SSDT was only needed with FakeSMC, thanks for the clarification

So if I'm understanding this right, users could test a bit and then build their custom valued kext and inject with Clover. Something if instability were to arise, we would still have a failsafe b/c we could disable the kext at the boot menu in Clover and the system would revert to unmodified.

I will updated the guide and a new clover folder later today. Thanks for contributing.

Correct. Known limits reported by many users are -130mV (CPU) -90mV (iGPU) -130mV (Cache). I've seen seen some extreme setups like -195mV for CPU but I won't go this far. The consensus is undervolt the lowest you can as long as it doesn't freeze lol

There is a very interesting thread on notebookreview forum where nice psychopaths are pushing the limit of cooling their XPS. Really interesting but way too crazy for me. There is even a guy who designed and built a custom heatsink using a CNC machine to reach lower temps lol You can find a chart made by the users there with all the different undervolting applied on their XPS, it's a good reference point.

What I'm looking at now is maybe is to find that mod that is sold on some Chinese sites or sometimes ebay, a 4 pipes, 2 copper stacked heatsink for the XPS 9560. but don't expect miracles you'll only gain 2°C.

But hey all in all, doing a whole repasting + undervolting is really good enough for me usually my temps are around 38°C/39°C at idle - nice.

The only thing I regret is that I feel we are reaching the end of this thread since so much improvement (thanks to you mainly) as been done and this laptop is near perfect now.

Yes, I'm that sentimental sometimes lol Hackintosh is a beautiful thing ;-)
 
Last edited:
Let me try that one! Am currently using one generated through the script, however that doesn't seem to place the laptop into sleep mode. Will report back.
Hi @Rhyswilliamsza. Yeah the issue is that even if your hack has the correct smsbios, the CPU you have isn't corresponding to any known macbook model. I am not saying this won't work at all, just that the script is based on an existing real mac SMBios, not your particular CPU.

If the kext on post #316 doesn't work for you will have to generate your own.
Hopefully you can still have a proper CPUDataProvider.kext that matches your exact CPU by using ssdtPRgen from Piker Alpha.

You can refer to original PmHeart/Ancidanthera CPUFriend repo on github which has the instruction.

Or there is a very detailed guide on another spanish forum (but with english instructions) you can find by googling this: "[Guide] - SSDT with Pike's PM Script and use with CPUFriend".

Last it can also be implemented only via SSDT, without CPUDataprovider.kext (also explained in the above tutorial, 1st part).

Cheers.
 
Last edited:
Hi @Rhyswilliamsza. Yeah the issue is that even if your hack has the correct smsbios, the CPU you have isn't corresponding to any known macbook model. I am not saying this won't work at all, just that the script is based on an existing real mac SMBios, not your particular CPU.

If the kext on post #316 doesn't work for you will have to generate your own.
Hopefully you can still have a proper CPUDataProvider.kext that matches your exact CPU by using ssdtPRgen from Piker Alpha.

You can refer to original PmHeart/Ancidanthera CPUFriend repo on github which has the instruction.

Or there is a very detailed guide on another spanish forum (but with english instructions) you can find by googling this: "[Guide] - SSDT with Pike's PM Script and use with CPUFriend".

Last it can also be implemented only via SSDT, without CPUDataprovider.kext (also explained in the above tutorial, 1st part).

Cheers.

Thanks so much! Yip, using the script from 316 did the trick. Thanks so much, appreciate it.
 
Awesome! Thanks and credit to @williamctstaton for the contribution.

@Rhyswilliamsza don't hesitate to test and report stability/battery usage so @blazinsmokey can add this config for all 7300HQ owners like you.

Thanks.

Post 316 was already noted in the guide in the post install section, thought everyone would read that as it's kind of important.... Now that it's been confirmed from 2 people I think I will make it more apparent and include the i5 variant with the folder.

Now back to VoltageShift, when I finally wrap my head around all this I will update guide and put together something for release.

I'm still reading about it and I'm having a hard time believing it effects Windows as well. Clover as far as I know does nothing with kexts when booting Windows and Windows literally can't do anything with a macOS kernel extension.

This program does not provide a GUI interface because it loads the MSR driver only when apply, amend or read is done, after that the MSR driver will load and unload immediately for more security and lowest resource usage, after you test the settings well, you can use our tools to build the launchd for autorun on startup and maintaining the settings, please read below for more details.

The quote above from their VoltageShift's GitHub makes it seem that if it writes to MSR and if you didn't shutdown your laptop completely before booting into Windows the settings may have persisted. Can you test this? I don't have Windows installation anymore, like you I really believe in this Hackintosh, hahaha.

The is the update interval of the tool to check and change, the Default value is 160min, Hibernate (suspend to Disk) will reset the voltage setting, as sleep (suspend to memory) will not change the sleep value, it will scheduled check the setting in peroid, and amend if need.

Nothing in the documentations suggests that this would effect anything other than macOS because it's ran at macOS boot through launch daemons and can be set to check and to set it again in intervals b/c it loses these settings if the laptop goes into hibernation but not regular sleep as quoted above.

You can spot the daemon launchd (com.sicreative.VoltageShift.plist under /Library/LaunchDaemons). So I don't think we even need to inject the kext after the build. After running the buildlaunchd command you're set. The kext was only needed to build the launch daemon.

Also I found some comments here that seems informative for us. Specifically the one below and it was confirmed by a user as well.

Keep in mind that if you do undervolt, your 9560 won't be able to "sleep" normally. Most of the time, your computer will do a hard restart when trying to wake from sleep if you undervolt. This is because sleep uses minimal voltage state anyways, and undervolting cannot differentiate what mode you're in. So it goes below minimal voltage threshold and the laptop cannot maintain sleep mode.

Please don't take my questions as anything negative. I'm very happy we can use this, I just want to make sure we have the right information for us and for other users. I'm sorry to be a pain in the ass.

I guess I got lucky with my machine, I bought direct from Dell and they must of did a good job with the thermal paste on mine as I haven't modded it at all and was idling at around 40-42c. Are you the first owner of your machine?
 
Post 316 was already noted in the guide in the post install section, thought everyone would read that as it's kind of important.... Now that it's been confirmed from 2 people I think I will make it more apparent and include the i5 variant with the folder.

Hey @blazinsmokey,

Yeah - I had originally used the kext generator to generate my own CPUFriendDataProvider for my CPU. But it seems the kext in 316 is better than the generated kext. So all is well now.
 
Hey @blazinsmokey!

Quick answer concerning VoltageShift.

1) You are damn perfectly right: Settings will be applied on windows ONLY if you reboot from OSX. No windows cold boot will work undervolting CPU. I tested with XTU at cold boot, it were default voltages.

2) About sleep: I never experienced cold reboot waking up from sleep using Voltageshift.

From memory I read on @arehep thread to replace the default 160ms value by 1ms.

On the other hand, the issue I have and discovered while testing is that sleep doesn't fully work on my hack lol

Cosmetically it seems like it sleeps when I click menu -----> sleep or close the lid, meaning screen, keyboard backlight, power button and fans stops after 20 seconds making me believe it was working, but it's not from a system point of view.

When I type this command in terminal:

Code:
pmset -g assertions

I get this output:

Code:
desktop-fmkjaut:~ buzzyness$ pmset -g assertions
2019-05-26 12:50:13 +0200
Assertion status system-wide:
   BackgroundTask                 1
   ApplePushServiceTask           0
   UserIsActive                   1
   PreventUserIdleDisplaySleep    0
   PreventSystemSleep             0
   ExternalMedia                  0
   PreventUserIdleSystemSleep     1
   NetworkClientActive            0
Listed by owning process:
   pid 98(hidd): [0x0000001b00098024] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle.4294968128.3"
    Timeout will fire in 600 secs Action=TimeoutActionRelease
   pid 301(useractivityd): [0x00000073000180fc] 00:00:02 PreventUserIdleSystemSleep named: "BTLEAdvertisement"
    Timeout will fire in 57 secs Action=TimeoutActionTurnOff
   pid 313(sharingd): [0x00000050000180e8] 00:00:37 PreventUserIdleSystemSleep named: "Handoff"
   pid 201(mds_stores): [0x0000005b000b80f6] 00:00:26 BackgroundTask named: "com.apple.metadata.mds_stores.power"
No kernel assertions.
Idle sleep preventers: IODisplayWrangler

So now I'm investigating to see if a daemon is responsible for this, blocking sleep.
If other users can also test it is much appreciated!

Some users mentioned not using plugintype in config, didn't solve the issue. Same with resetting printers. I must investigate deeper. Also will disable VoltageShift daemon and see how it goes.

Even without VoltageShift uninstall via command ./voltageshift removelaunchd after cd to directory and cold boot doesn't solve the sleep issue and still have " PreventUserIdleSystemSleep 1" and "Idle sleep preventers: IODisplayWrangler"

Maybe there is nothing to worry about, i’ve seen a post from Rehabman explaining his Macbook Air was showing exactly the same, I don’t know.

EDIT: ok found the culprit. Handoff is preventing system to sleep! And this apparently has been reported on real macs too. You have to disable it if you want to set PreventUserIdleSystemSleep to 0.
More weird : when I re-enable handoff, hibernate mode change from 0 to 3 :problem:
I also found it is linked to Darkwake here, checking sleep in terminal gives me different result depending on the value. If darkwake=no Handoff will block sleep if enabled. Will test different values and report.


Side question do you have proximitywake set up to 0?

3) I also found that putting bootargs darkwake=0 instead of "no" has resolved the wake from lid screen flickering/flash.
Note: the sleep issue here is the same as with darkwake=no. No sleep issue doing this.

4) I had my first Kernel Panic ever Whaoooooh! lol I was trying to understand @auguzanellato IOReg because he is one of the only user I can remember who as TB3 dock/devices to test and has issues with USB2 and TB3 (see post #355).

Here's the KP report:
Code:
Anonymous UUID:       29727AE6-BE70-D4DB-38D6-55DE9A2E9ACF

Sun May 26 01:54:37 2019

*** Panic Report ***
panic(cpu 6 caller 0xffffff801660592a): "a freed zone element has been modified in zone kalloc.16: expected 0xc0ffee16646663d2 but found 0xc0ffee1664666308, bits changed 0xda, at offset 0 of 16 in element 0xffffff807549c0a0, cookies 0x3f001196112fa602 0x53521646b0f83b3"@/BuildRoot/Library/Caches/com.apple.xbs/Sources/xnu/xnu-4903.261.4/osfmk/kern/zalloc.c:1206
Backtrace (CPU 6), Frame : Return Address
0xffffff83d2c3b840 : 0xffffff80165aea2d
0xffffff83d2c3b890 : 0xffffff80166e9e95
0xffffff83d2c3b8d0 : 0xffffff80166db70a
0xffffff83d2c3b940 : 0xffffff801655bb40
0xffffff83d2c3b960 : 0xffffff80165ae447
0xffffff83d2c3ba80 : 0xffffff80165ae293
0xffffff83d2c3baf0 : 0xffffff801660592a
0xffffff83d2c3bb50 : 0xffffff8016605163
0xffffff83d2c3bba0 : 0xffffff8016603b01
0xffffff83d2c3bcd0 : 0xffffff80165baea4
0xffffff83d2c3bd40 : 0xffffff8016bcd25c
0xffffff83d2c3bd60 : 0xffffff8016bcd2c2
0xffffff83d2c3bd80 : 0xffffff8016c4306c
0xffffff83d2c3bdd0 : 0xffffff8016c44ae6
0xffffff83d2c3be00 : 0xffffff8016c3bb72
0xffffff83d2c3be60 : 0xffffff8016c38cf3
0xffffff83d2c3beb0 : 0xffffff8016c46698
0xffffff83d2c3bee0 : 0xffffff8016c385f9
0xffffff83d2c3bf30 : 0xffffff8016c56362
0xffffff83d2c3bf70 : 0xffffff8016c558bc
0xffffff83d2c3bfa0 : 0xffffff801655b0ce

BSD process name corresponding to current thread: kernel_task
Boot args: darkwake=no brcmfx-country=#a dart=0

Mac OS version:
18F132

Kernel version:
Darwin Kernel Version 18.6.0: Thu Apr 25 23:16:27 PDT 2019; root:xnu-4903.261.4~2/RELEASE_X86_64
Kernel UUID: 7C8BB636-E593-3CE4-8528-9BD24A688851
Kernel slide:     0x0000000016200000
Kernel text base: 0xffffff8016400000
__HIB  text base: 0xffffff8016300000
System model name: MacBookPro14,1 (Mac-B4831CEBD52A0C4C)

System uptime in nanoseconds: 12902942885555
last loaded kext at 12901654387097: com.apple.driver.AppleXsanScheme    3 (addr 0xffffff7f9aa89000, size 32768)
last unloaded kext at 12855701332143: com.sicreative.VoltageShift    1.1 (addr 0xffffff7f9a4ce000, size 16384)
loaded kexts:
com.paragon-software.filesystems.ntfs    19.4.15
com.intel.driver.EnergyDriver    3.5.5
com.alexandred.VoodooI2CHID    1
com.no-one.BrcmPatchRAM2    2.2.10
com.no-one.BrcmFirmwareStore    2.2.10
org.rehabman.voodoo.driver.PS2Trackpad    1.9.2
org.rehabman.voodoo.driver.PS2Keyboard    1.9.2
at.obdev.nke.LittleSnitch    5284
org.rehabman.driver.FakePCIID    1.3.15
com.alexandred.VoodooI2C    2.1.6
org.coolstar.VoodooGPIO    1.1
org.rehabman.voodoo.driver.PS2Controller    1.9.2
as.vit9696.AppleALC    1.3.8
as.lvs1974.HibernationFixup    1.2.5
as.lvs1974.AirportBrcmFixup    2.0.0
org.vanilla.driver.CPUFriend    1.1.7
ru.usrsse2.SMCBatteryManager    1
as.vit9696.VirtualSMC    1.0.4
as.lvs1974.BT4LEContiunityFixup    1.1.2
as.vit9696.WhateverGreen    1.2.9
as.vit9696.Lilu    1.3.6
com.XPS.VerbStub    1.0.3
com.alexandred.VoodooI2CServices    1
com.apple.iokit.SCSITaskUserClient    408.250.3
com.apple.filesystems.msdosfs    1.10
com.apple.filesystems.smbfs    3.3.2
com.apple.driver.AudioAUUC    1.70
com.apple.fileutil    20.036.15
com.apple.filesystems.autofs    3.0
com.apple.filesystems.ntfs    3.13
com.apple.driver.ApplePlatformEnabler    2.7.0d0
com.apple.driver.AGPM    110.25.10
com.apple.driver.X86PlatformShim    1.0.0
com.apple.driver.AppleHDA    282.54
com.apple.driver.AppleUpstreamUserClient    3.6.5
com.apple.driver.AppleMCCSControl    1.5.9
com.apple.driver.AppleGraphicsDevicePolicy    3.40.16
com.apple.driver.AppleOSXWatchdog    1
com.apple.driver.AppleIntelPCHPMC    2.0.1
com.apple.private.KextAudit    1.0
com.apple.AGDCPluginDisplayMetrics    3.40.16
com.apple.driver.eficheck    1
com.apple.driver.AppleIntelKBLGraphics    12.0.9
com.apple.driver.AppleHV    1
com.apple.iokit.IOUserEthernet    1.0.1
com.apple.iokit.IOBluetoothSerialManager    6.0.12f1
com.apple.driver.pmtelemetry    1
com.apple.Dont_Steal_Mac_OS_X    7.0.0
com.apple.driver.AppleLPC    3.1
com.apple.driver.AppleSMCLMU    212
com.apple.driver.AppleIntelKBLGraphicsFramebuffer    12.0.9
com.apple.driver.AppleIntelSlowAdaptiveClocking    4.0.0
com.apple.driver.AppleTopCaseHIDEventDriver    138.3
com.apple.filesystems.apfs    945.260.7
com.apple.driver.AppleVirtIO    2.1.3
com.apple.filesystems.hfs.kext    407.200.4
com.apple.AppleFSCompression.AppleFSCompressionTypeDataless    1.0.0d1
com.apple.BootCache    40
com.apple.AppleFSCompression.AppleFSCompressionTypeZlib    1.0.0
com.apple.AppleSystemPolicy    1.0
com.apple.driver.AirPort.Brcm4360    1400.1.1
com.apple.driver.AirPort.BrcmNIC    1400.1.1
com.apple.driver.AppleAHCIPort    329.260.5
com.apple.driver.AppleSmartBatteryManager    161.0.0
com.apple.driver.AppleACPIEC    6.1
com.apple.driver.AppleACPIButtons    6.1
com.apple.driver.AppleRTC    2.0
com.apple.driver.AppleHPET    1.8
com.apple.driver.AppleBacklight    170.12.11
com.apple.driver.AppleSMBIOS    2.1
com.apple.driver.AppleAPIC    1.7
com.apple.nke.applicationfirewall    201
com.apple.security.TMSafetyNet    8
com.apple.driver.AppleXsanScheme    3
com.apple.driver.usb.cdc    5.0.0
com.apple.driver.AppleUSBAudio    315.6
com.apple.driver.usb.IOUSBHostHIDDevice    1.2
com.apple.driver.usb.AppleUSBHub    1.2
com.apple.iokit.IOAVBFamily    740.1
com.apple.plugin.IOgPTPPlugin    740.2
com.apple.iokit.IOEthernetAVBController    1.1.0
com.apple.iokit.IOSkywalkFamily    1
com.apple.iokit.BroadcomBluetoothHostControllerUSBTransport    6.0.12f1
com.apple.iokit.IOBluetoothHostControllerUSBTransport    6.0.12f1
com.apple.iokit.IOBluetoothHostControllerTransport    6.0.12f1
com.apple.kext.triggers    1.0
com.apple.driver.DspFuncLib    282.54
com.apple.kext.OSvKernDSPLib    528
com.apple.driver.AppleSMBusController    1.0.18d1
com.apple.driver.AppleGraphicsControl    3.40.16
com.apple.driver.X86PlatformPlugin    1.0.0
com.apple.driver.AppleSSE    1.0
com.apple.driver.AppleHDAController    282.54
com.apple.iokit.IOHDAFamily    282.54
com.apple.driver.IOPlatformPluginFamily    6.0.0d8
com.apple.iokit.IOAcceleratorFamily2    404.9
com.apple.iokit.IOSurface    255.5.4
com.apple.AppleGPUWrangler    3.40.16
com.apple.AppleGraphicsDeviceControl    3.40.16
com.apple.iokit.IOSlowAdaptiveClockingFamily    1.0.0
com.apple.driver.AppleActuatorDriver    2450.1
com.apple.driver.AppleHSBluetoothDriver    138.3
com.apple.driver.IOBluetoothHIDDriver    6.0.12f1
com.apple.iokit.IOBluetoothFamily    6.0.12f1
com.apple.driver.AppleMultitouchDriver    2450.1
com.apple.driver.AppleInputDeviceSupport    2440.2
com.apple.iokit.IOAudioFamily    206.5
com.apple.vecLib.kext    1.2.0
com.apple.driver.usb.networking    5.0.0
com.apple.driver.usb.AppleUSBHostCompositeDevice    1.2
com.apple.iokit.IOSerialFamily    11
com.apple.filesystems.hfs.encodings.kext    1
com.apple.driver.AppleUSBHostMergeProperties    1.2
com.apple.iokit.IONVMeFamily    2.1.0
com.apple.driver.usb.AppleUSBHostPacketFilter    1.0
com.apple.iokit.IO80211Family    1200.12.2
com.apple.driver.mDNSOffloadUserClient    1.0.1b8
com.apple.driver.corecapture    1.0.4
com.apple.iokit.IOUSBFamily    900.4.2
com.apple.iokit.IOAHCIFamily    288
com.apple.driver.usb.AppleUSBXHCIPCI    1.2
com.apple.driver.usb.AppleUSBXHCI    1.2
com.apple.driver.AppleEFINVRAM    2.1
com.apple.driver.AppleEFIRuntime    2.1
com.apple.iokit.IOHIDFamily    2.0.0
com.apple.driver.AppleBacklightExpert    1.1.0
com.apple.iokit.IONDRVSupport    530.51
com.apple.iokit.IOGraphicsFamily    530.66
com.apple.security.quarantine    3
com.apple.security.sandbox    300.0
com.apple.kext.AppleMatch    1.0.0d1
com.apple.iokit.IOSMBusFamily    1.1
com.apple.driver.DiskImages    493.0.0
com.apple.driver.AppleFDEKeyStore    28.30
com.apple.driver.AppleEffaceableStorage    1.0
com.apple.driver.AppleKeyStore    2
com.apple.driver.AppleUSBTDM    456.260.3
com.apple.driver.AppleMobileFileIntegrity    1.0.5
com.apple.iokit.IOUSBMassStorageDriver    145.200.2
com.apple.iokit.IOSCSIBlockCommandsDevice    408.250.3
com.apple.iokit.IOSCSIArchitectureModelFamily    408.250.3
com.apple.iokit.IOStorageFamily    2.1
com.apple.kext.CoreTrust    1
com.apple.driver.AppleCredentialManager    1.0
com.apple.driver.KernelRelayHost    1
com.apple.iokit.IOUSBHostFamily    1.2
com.apple.driver.usb.AppleUSBCommon    1.0
com.apple.driver.AppleBusPowerController    1.0
com.apple.driver.AppleSEPManager    1.0.1
com.apple.driver.IOSlaveProcessor    1
com.apple.iokit.IOReportFamily    47
com.apple.iokit.IOTimeSyncFamily    740.2
com.apple.iokit.IONetworkingFamily    3.4
com.apple.driver.AppleACPIPlatform    6.1
com.apple.driver.AppleSMC    3.1.9
com.apple.iokit.IOPCIFamily    2.9
com.apple.iokit.IOACPIFamily    1.4
com.apple.kec.pthread    1
com.apple.kec.Libm    1
com.apple.kec.corecrypto    1.0

EOF
Model: MacBookPro14,1, BootROM 194.0.0.0.0, 4 processors, Intel Core i7, 2,81 GHz, 32 GB, SMC 2.43f6
Graphics: kHW_IntelHDGraphics630Item, Intel HD Graphics 630, spdisplays_builtin
Memory Module: BANK 0/DIMM0, 16 GB, DDR4, 2667 MHz, Micron Technology, 16ATF2G64HZ-2G6E1
Memory Module: BANK 1/DIMM0, 16 GB, DDR4, 2667 MHz, Crucial Technology, CT16G4SFD8266.C16FD1
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x623), Broadcom BCM43xx 1.0 (7.77.61.2 AirPortDriverBrcmNIC-1305.8)
Bluetooth: Version 6.0.12f1, 3 services, 18 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
PCI Card: sppci_expresscard_name, XHCI
USB Device: USB 3.0 Bus
USB Device: Integrated_Webcam_HD
USB Device: BCM20702A0
USB Device: USB 3.1 Bus
USB Device: USB 2.0 Hub
USB Device: Ultra
Thunderbolt Bus:

So I was comparing my device tree with his, had only USB device to test with my adapter, and after the 3rd reconnect (single USB3 device connect to Type-C/TB/HDMI4K adpater), boom KP !! lol I removed TB-SSDT9560.aml and didn't get the issue anymore. Hard to spot the issue. Tested with original 3.2 Clover folder without any mod.

I just read a bunch of thread of user on Mojave who succeed in hotpluging Type-C and TB but didn't find a lead to track on this. @au1986 implemented this in various ways on his hack but TB only works at cold boot before sleep. Heard about this kext (seems to date a bit now): IOElectrify. See @au1986 's blog for details: http://rockjesus.cn/2019/01/11/tb/

5) Does anyone used this SD Card kext from Sinetek (@syscl used it with success apparently on his hack): https://github.com/sinetek/Sinetek-rtsx/commit/1f6a32688b35390591649ff1fc77a9850d3abd5a

Keep y'all posted!
 
Last edited:
Good morning all,

I've been doing some testing on my end - I seem to experience that when my laptop fans ramp up as I am working/watching a video/etc, they don't ramp DOWN. I use iStat Menus to review CPU temps, and even when the temps across the board seem to be back in the lower ranges (42C) the fans are still at the highest RPM they hit while I was working. Has anyone else experienced this? I swapped from VirtualSMC back to FakeSMC to see if this impacted it, but it appears not.
 
Good morning all,

I've been doing some testing on my end - I seem to experience that when my laptop fans ramp up as I am working/watching a video/etc, they don't ramp DOWN. I use iStat Menus to review CPU temps, and even when the temps across the board seem to be back in the lower ranges (42C) the fans are still at the highest RPM they hit while I was working. Has anyone else experienced this? I swapped from VirtualSMC back to FakeSMC to see if this impacted it, but it appears not.
On battery or with Adapter? I have this mainly with Adapter, on Battery it is really silent with fan blasting on very rare occasion with 80+ chrome tabs opened.
 
Status
Not open for further replies.
Back
Top